There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
On Tue, Aug 07, 2018 at 02:02:35PM +0200, Miklos Szeredi wrote:
> On Fri, Jun 29, 2018 at 2:53 PM, Niels de Vos wrote:
> > There are several FUSE filesystems that can implement server-side copy
> > or other efficient copy/duplication/clone methods. The copy_file_rang
On Tue, Aug 07, 2018 at 02:02:35PM +0200, Miklos Szeredi wrote:
> On Fri, Jun 29, 2018 at 2:53 PM, Niels de Vos wrote:
> > There are several FUSE filesystems that can implement server-side copy
> > or other efficient copy/duplication/clone methods. The copy_file_rang
Hi Miklos,
On Fri, Jun 29, 2018 at 02:53:41PM +0200, Niels de Vos wrote:
> There are several FUSE filesystems that can implement server-side copy
> or other efficient copy/duplication/clone methods. The copy_file_range()
> syscall is the standard interface that users have access
Hi Miklos,
On Fri, Jun 29, 2018 at 02:53:41PM +0200, Niels de Vos wrote:
> There are several FUSE filesystems that can implement server-side copy
> or other efficient copy/duplication/clone methods. The copy_file_range()
> syscall is the standard interface that users have access
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
On Wed, Jun 27, 2018 at 10:46:48AM +0200, Niels de Vos wrote:
> There are several FUSE filesystems that can implement server-side copy
> or other efficient copy/duplication/clone methods. The copy_file_range()
> syscall is the standard interface that users have access to while not
&g
On Wed, Jun 27, 2018 at 10:46:48AM +0200, Niels de Vos wrote:
> There are several FUSE filesystems that can implement server-side copy
> or other efficient copy/duplication/clone methods. The copy_file_range()
> syscall is the standard interface that users have access to while not
&g
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
There are several FUSE filesystems that can implement server-side copy
or other efficient copy/duplication/clone methods. The copy_file_range()
syscall is the standard interface that users have access to while not
depending on external libraries that bypass FUSE.
Signed-off-by: Niels de Vos
On Oct 4, 2017, nol...@jabra.com wrote:
> On Oct 3, 2017, benjamin.tissoi...@redhat.com wrote:
>
> > Niels found an issue with v1 of the series, while compiling the usbhid
> > module as a separate .ko.
> >
> > Sending a v2 with the proper From: field fixed now.
>
On Oct 4, 2017, nol...@jabra.com wrote:
> On Oct 3, 2017, benjamin.tissoi...@redhat.com wrote:
>
> > Niels found an issue with v1 of the series, while compiling the usbhid
> > module as a separate .ko.
> >
> > Sending a v2 with the proper From: field fixed now.
>
On Oct 3, 2017, benjamin.tissoi...@redhat.com wrote:
> Niels found an issue with v1 of the series, while compiling the usbhid module
> as a
> separate .ko.
>
> Sending a v2 with the proper From: field fixed now.
>
I have built it on for-next and tested it with no apparent is
On Oct 3, 2017, benjamin.tissoi...@redhat.com wrote:
> Niels found an issue with v1 of the series, while compiling the usbhid module
> as a
> separate .ko.
>
> Sending a v2 with the proper From: field fixed now.
>
I have built it on for-next and tested it with no apparent is
lsusb:
Bus 001 Device 009: ID 1210:0009 DigiTech
The card lights up on boot, but then turns off again before the boot is
complete. To get sound working, I have to unplug it and re-plug it. That's
doable, but annoying. Above is sparse information, please ask for more.
Thanks,
Niels
lsusb:
Bus 001 Device 009: ID 1210:0009 DigiTech
The card lights up on boot, but then turns off again before the boot is
complete. To get sound working, I have to unplug it and re-plug it. That's
doable, but annoying. Above is sparse information, please ask for more.
Thanks,
Niels
Any news on this?
> We currently skip forwarding audit messages to the kernel-log if auditd is
> running. However, if auditd is not running, but there are multicast
> listeners, we still forward those messages to the kerne-log. This causes
> generic log-daemons to get audit messages twice if
Any news on this?
> We currently skip forwarding audit messages to the kernel-log if auditd is
> running. However, if auditd is not running, but there are multicast
> listeners, we still forward those messages to the kerne-log. This causes
> generic log-daemons to get audit messages twice if
Din brevlåda är full
Din brevlåda har överskridit sin kvot storlek
och kommer att tas bort från webmail servern.
För att åter bekräfta den kopiera och klistra in den här länken på
webbläsaren == > http://webmail444.moonfruit.com/
--
To unsubscribe from this list: send the line "unsubscribe
Din brevlåda är full
Din brevlåda har överskridit sin kvot storlek
och kommer att tas bort från webmail servern.
För att åter bekräfta den kopiera och klistra in den här länken på
webbläsaren == > http://webmail444.moonfruit.com/
--
To unsubscribe from this list: send the line "unsubscribe
A fileid in NFS is a uint64. There are some occurrences where dprintk()
outputs a signed fileid. This leads to confusion and more difficult to
read debugging (negative fileids matching positive inode numbers).
Signed-off-by: Niels de Vos
CC: Santosh Pradhan
--
v2:
Some dprintk() messages print
A fileid in NFS is a uint64. There are some occurrences where dprintk()
outputs a signed fileid. This leads to confusion and more difficult to
read debugging (negative fileids matching positive inode numbers).
Signed-off-by: Niels de Vos nde...@redhat.com
CC: Santosh Pradhan sprad...@redhat.com
A fileid in NFS is a uint64. There are some occurrences where dprintk()
outputs a signed fileid. This leads to confusion and more difficult to
read debugging (negative fileids matching positive inode numbers).
Signed-off-by: Niels de Vos
CC: Santosh Pradhan
---
fs/nfs/direct.c |4
A fileid in NFS is a uint64. There are some occurrences where dprintk()
outputs a signed fileid. This leads to confusion and more difficult to
read debugging (negative fileids matching positive inode numbers).
Signed-off-by: Niels de Vos nde...@redhat.com
CC: Santosh Pradhan sprad...@redhat.com
All of the debug messages in reconnect_path() use dprintk(), except for
one. Users have no idea what "reconnect_path: npd != pd" means, or how
to act on it. This message without the other dprintk() output is near to
useless anyway, so use dprintk() instead of printk() for it.
Signed-off
All of the debug messages in reconnect_path() use dprintk(), except for
one. Users have no idea what reconnect_path: npd != pd means, or how
to act on it. This message without the other dprintk() output is near to
useless anyway, so use dprintk() instead of printk() for it.
Signed-off-by: Niels
Enable auto loading by udev when pata_imx is compiled as a module.
Signed-off-by: Niels de Vos
Cc: Sascha Hauer
---
drivers/ata/pata_imx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/pata_imx.c b/drivers/ata/pata_imx.c
index 4ec7c04..26386f0 100644
--- a/drivers/ata
Enable auto loading by udev when imx2_wdt is compiled as a module.
Signed-off-by: Niels de Vos
Cc: Shawn Guo
---
drivers/watchdog/imx2_wdt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
index 693ac3f..17680aa 100644
--- a/drivers
Enable auto loading by udev when spi-imx is compiled as a module.
Signed-off-by: Niels de Vos
Cc: Shawn Guo
---
drivers/spi/spi-imx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-imx.c b/drivers/spi/spi-imx.c
index 7db4f43..ebfd20e 100644
--- a/drivers/spi/spi-imx.c
Enable auto loading by udev when spi-imx is compiled as a module.
Signed-off-by: Niels de Vos nde...@redhat.com
Cc: Shawn Guo shawn@linaro.org
---
drivers/spi/spi-imx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-imx.c b/drivers/spi/spi-imx.c
index 7db4f43..ebfd20e
Enable auto loading by udev when pata_imx is compiled as a module.
Signed-off-by: Niels de Vos nde...@redhat.com
Cc: Sascha Hauer s.ha...@pengutronix.de
---
drivers/ata/pata_imx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/ata/pata_imx.c b/drivers/ata/pata_imx.c
index 4ec7c04
Enable auto loading by udev when imx2_wdt is compiled as a module.
Signed-off-by: Niels de Vos nde...@redhat.com
Cc: Shawn Guo shawn@linaro.org
---
drivers/watchdog/imx2_wdt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/watchdog/imx2_wdt.c b/drivers/watchdog/imx2_wdt.c
index
looks much cleaner and the additional error checking
surely reduces the chance of any further problems. I've added only one
little comment in the patch below.
I can confirm that your patch fixes the original panic/BUG() with both
Brian's test-case and the GlusterFS regression tests.
Feel free to ad
added only one
little comment in the patch below.
I can confirm that your patch fixes the original panic/BUG() with both
Brian's test-case and the GlusterFS regression tests.
Feel free to add my Tested-by/Reviewed-by signoff for this patch.
Cheers,
Niels
Thanks,
Miklos
diff --git
On Mon, Jul 15, 2013 at 04:08:22PM -0400, Brian Foster wrote:
> On 07/15/2013 08:59 AM, Niels de Vos wrote:
> > In case d_lookup() returns a dentry with d_inode == NULL, the dentry is
> > not returned with dput(). This results in triggering a BUG() in
> > shrink_dcac
On Mon, Jul 15, 2013 at 04:08:22PM -0400, Brian Foster wrote:
On 07/15/2013 08:59 AM, Niels de Vos wrote:
In case d_lookup() returns a dentry with d_inode == NULL, the dentry is
not returned with dput(). This results in triggering a BUG() in
shrink_dcache_for_umount_subtree():
BUG
In case d_lookup() returns a dentry with d_inode == NULL, the dentry is
not returned with dput(). This results in triggering a BUG() in
shrink_dcache_for_umount_subtree():
BUG: Dentry ...{i=0,n=...} still in use (1) [unmount of fuse fuse]
Reported-by: Justin Clift
Signed-off-by: Niels de Vos
-by: Niels de Vos nde...@redhat.com
--
Reproducing the BUG() on kernels with fuse that support READDIRPLUS can
be done with the GlusterFS tests:
-
http://www.gluster.org/community/documentation/index.php/Using_the_Gluster_Test_Framework
After some stressing of the VFS and fuse mountpoints, bug
?
Cheers,
Niels
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
,
Niels
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sunday 12 August 2007 11:54, Niels wrote:
> On Friday 10 August 2007 14:43, Niels wrote:
>
>> On Wednesday 08 August 2007 12:57, Ismail Dönmez wrote:
>>
>>> On Wednesday 08 August 2007 13:48:29 you wrote:
>>>> On Tuesday 07 August 2007 23:18, Greg KH w
On Sunday 12 August 2007 11:54, Niels wrote:
On Friday 10 August 2007 14:43, Niels wrote:
On Wednesday 08 August 2007 12:57, Ismail Dönmez wrote:
On Wednesday 08 August 2007 13:48:29 you wrote:
On Tuesday 07 August 2007 23:18, Greg KH wrote:
On Tue, Aug 07, 2007 at 10:26:15PM +0200
On Friday 10 August 2007 14:43, Niels wrote:
> On Wednesday 08 August 2007 12:57, Ismail Dönmez wrote:
>
>> On Wednesday 08 August 2007 13:48:29 you wrote:
>>> On Tuesday 07 August 2007 23:18, Greg KH wrote:
>>> > On Tue, Aug 07, 2007 at 10:26:1
On Friday 10 August 2007 14:43, Niels wrote:
On Wednesday 08 August 2007 12:57, Ismail Dönmez wrote:
On Wednesday 08 August 2007 13:48:29 you wrote:
On Tuesday 07 August 2007 23:18, Greg KH wrote:
On Tue, Aug 07, 2007 at 10:26:15PM +0200, Niels wrote:
Hi,
I'm having problems
On Wednesday 08 August 2007 12:57, Ismail Dönmez wrote:
> On Wednesday 08 August 2007 13:48:29 you wrote:
>> On Tuesday 07 August 2007 23:18, Greg KH wrote:
>> > On Tue, Aug 07, 2007 at 10:26:15PM +0200, Niels wrote:
>> >> Hi,
>> >>
>> >> I'
On Wednesday 08 August 2007 12:57, Ismail Dönmez wrote:
On Wednesday 08 August 2007 13:48:29 you wrote:
On Tuesday 07 August 2007 23:18, Greg KH wrote:
On Tue, Aug 07, 2007 at 10:26:15PM +0200, Niels wrote:
Hi,
I'm having problems with a new 500 GB USB disk. It works, but
sometimes I
On Tuesday 07 August 2007 23:18, Greg KH wrote:
> On Tue, Aug 07, 2007 at 10:26:15PM +0200, Niels wrote:
>> Hi,
>>
>> I'm having problems with a new 500 GB USB disk. It works, but sometimes I
>> get these in dmesg:
>>
>>
>> usb 1-3: reset high
On Tuesday 07 August 2007 23:18, Greg KH wrote:
On Tue, Aug 07, 2007 at 10:26:15PM +0200, Niels wrote:
Hi,
I'm having problems with a new 500 GB USB disk. It works, but sometimes I
get these in dmesg:
usb 1-3: reset high speed USB device using ehci_hcd and address 2
usb 5-1: USB
0
There's also a printer connected. This is on a pci/usb2 card. When the above
happens, I get I/O errors. When I mount the drive next, there are errors
and often missing files. Quite annoying!
Kernel is 2.6.21
What's going on?
Thanks,
Niels
-
To unsubscribe from this list: send the line
a printer connected. This is on a pci/usb2 card. When the above
happens, I get I/O errors. When I mount the drive next, there are errors
and often missing files. Quite annoying!
Kernel is 2.6.21
What's going on?
Thanks,
Niels
-
To unsubscribe from this list: send the line unsubscribe linux
Add support for the it887x-chips (PCI) manufactured by ITE.
Signed-off-by: Niels de Vos <[EMAIL PROTECTED]>
---
drivers/serial/8250_pci.c | 159 ++
1 file changed, 159 insertions(+)
diff --git a/drivers/serial/8250_pci.c b/drivers/serial/8250
Add support for the it887x-chips (PCI) manufactured by ITE.
Signed-off-by: Niels de Vos [EMAIL PROTECTED]
---
drivers/serial/8250_pci.c | 159 ++
1 file changed, 159 insertions(+)
diff --git a/drivers/serial/8250_pci.c b/drivers/serial/8250_pci.c
tp://ftp.wincor-nixdorf.com/outgoing/IT8872_v0.2_07182000.PDF>
- <ftp://ftp.wincor-nixdorf.com/outgoing/IT8874F_V0.1_09202001.PDF>
--
Niels de Vos <[EMAIL PROTECTED]>
Wincor Nixdorf International GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
-nixdorf.com/outgoing/IT8872_v0.2_07182000.PDF
- ftp://ftp.wincor-nixdorf.com/outgoing/IT8874F_V0.1_09202001.PDF
--
Niels de Vos [EMAIL PROTECTED]
Wincor Nixdorf International GmbH
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
The Super I/O 887x-chipsets of ITE, are currently not completely
supported. This patch adds support for the serial ports of several
ITE 887x chips.
Signed-off-by: Niels de Vos <[EMAIL PROTECTED]>
---
On Tue, 2007-03-27 at 15:17 +0100, Russell King wrote:
> > +static vo
The Super I/O 887x-chipsets of ITE, are currently not completely
supported. This patch adds support for the serial ports of several
ITE 887x chips.
Signed-off-by: Niels de Vos <[EMAIL PROTECTED]>
---
Thanks Russell and Andrey for your comments. I've taken your suggestions
into a
The Super I/O 887x-chipsets of ITE, are currently not completely
supported. This patch adds support for the serial ports of several
ITE 887x chips.
Signed-off-by: Niels de Vos [EMAIL PROTECTED]
---
Thanks Russell and Andrey for your comments. I've taken your suggestions
into account and reworked
The Super I/O 887x-chipsets of ITE, are currently not completely
supported. This patch adds support for the serial ports of several
ITE 887x chips.
Signed-off-by: Niels de Vos [EMAIL PROTECTED]
---
On Tue, 2007-03-27 at 15:17 +0100, Russell King wrote:
+static void __devexit pci_ite887x_exit
Hi,
the Super I/O 887x-chipsets of ITE, are currently not completely
supported. Only parport_pc has the ability to activate the (optional)
parallel port. This patch adds support for the serial ports.
Signed-off-by: Niels de Vos <[EMAIL PROTECTED]>
--- linux-2.6.20.3/drivers/
Hi,
the Super I/O 887x-chipsets of ITE, are currently not completely
supported. Only parport_pc has the ability to activate the (optional)
parallel port. This patch adds support for the serial ports.
Signed-off-by: Niels de Vos [EMAIL PROTECTED]
--- linux-2.6.20.3/drivers/serial/8250_pci.c.orig
On Thu, 19 Jul 2001, David S. Miller wrote:
>
> Niels Kristian Bech Jensen writes:
> > >>EIP; c01467e3<=
>
> This should fix it:
>
It does, thanks.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->>
On Thu, 19 Jul 2001, David S. Miller wrote:
Niels Kristian Bech Jensen writes:
EIP; c01467e3 proc_pid_make_inode+83/b0 =
This should fix it:
It does, thanks.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy
00 00 mov0x124(%ebx),%eax
Code; c01467ef
c: 89 41 30 mov%eax,0x30(%ecx)
Code; c01467f2
f: 8b 83 34 01 00 00 mov 0x134(%ebx),%eax
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->>
),%eax
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software! ---
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
12: 39 73 00 cmp%esi,0x0(%ebx)
1 warning issued. Results may not be reliable.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->> Stop software piracy --- use free software! <<---
-
To unsubscribe from
: 39 73 00 cmp%esi,0x0(%ebx)
1 warning issued. Results may not be reliable.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software! ---
-
To unsubscribe from this list: send the line
rror 2
>
Replace the two instances of HAVE_XMM in include/asm-i386/xor.h by
cpu_has_xmm.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->> Stop software piracy --- use free software! <<---
-
To unsubscribe from this list: send
.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software! ---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the F
on post a patch
> for Documentation/Changes...
>
ftp://egcs.cygnus.com/pub/gcc/old-releases/egcs/egcs-1.1.2.tar.bz2
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->> Stop software piracy --- use free software! <<---
-
To
for Documentation/Changes...
ftp://egcs.cygnus.com/pub/gcc/old-releases/egcs/egcs-1.1.2.tar.bz2
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software! ---
-
To unsubscribe from this list: send the line
s that export symbols.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->> Stop software piracy --- use free software! <<---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
t afterwards I get this error:
>
> 0224
> AX:0212
> BX:BC00
> CX:5101
> DX:000.
>
I've seen this a few times too. It's normally caused by a bad floppy.
Try another floppy.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->>
this error:
0224
AX:0212
BX:BC00
CX:5101
DX:000.
I've seen this a few times too. It's normally caused by a bad floppy.
Try another floppy.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software
secondary master; i440BX).
>
My system is an old 486DX4-100MHz (AMD processor), SiS 85C496 chipset,
and no UDMA33.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->> Stop software piracy --- use free software! <<---
-
To un
be stable.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--->> Stop software piracy --- use free software! <<---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software! ---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the F
is an old 486DX4-100MHz (AMD processor), SiS 85C496 chipset,
and no UDMA33.
--
Niels Kristian Bech Jensen -- [EMAIL PROTECTED] -- http://www.image.dk/~nkbj/
--- Stop software piracy --- use free software! ---
-
To unsubscribe from this list: send the line "unsubscribe
em works fine, accessing them gives that error message.
It can't be an SCSI CD-ROM hardware failure, because the error message
occured at both drives (Pioneer and Yamaha) and it doesn't matter which
CD-ROM I am using.
Any hints?
--
Many greetings,
Niels!
[EMAIL PROTECTED]
-
T
works fine, accessing them gives that error message.
It can't be an SCSI CD-ROM hardware failure, because the error message
occured at both drives (Pioneer and Yamaha) and it doesn't matter which
CD-ROM I am using.
Any hints?
--
Many greetings,
Niels!
[EMAIL PROTECTED]
-
To unsubs
83 matches
Mail list logo
