Thanks for the patience. vger.timpanogas.org is back up. The upgrade
took a little longer than expected. We apologize for any
inconveniance.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at ht
Thanks again.
> > > Ok, does /proc/sys/dev/cdrom/info list DVD-RAM as a capability?
> > CD-ROM information, Id: cdrom.c 3.12 2000/10/22
> >
> > Can write DVD-RAM: 1
>
> So far, so good.
:-)
> > Should I set any flags to permit write a DVD-RAM media ?
>
> No, as I said it should detect
On Sun, Oct 29 2000, Hisaaki Shibata wrote:
> > Ok, does /proc/sys/dev/cdrom/info list DVD-RAM as a capability?
>
> Yes.
> I think it seems good.
>
> # more info
> CD-ROM information, Id: cdrom.c 3.12 2000/10/22
>
> Can write DVD-RAM: 1
So far, so good.
> Should I set any flags to permi
Thank you, again.
> On Sat, Oct 28 2000, Hisaaki Shibata wrote:
> > > > But I could not mkudf nor mkext2fs to my ATAPI 9.4GB new DVD-RAM drive.
> > >
> > > What do you mean? What happened? strace of mke2fs of mkudf would
> > > be nice to have.
> >
> > My system said it is not permited because i
This patch against 2.4.0-test10-pre6 implements LINK_FIRST and
LINK_LAST to fix the problem with usb initialization order. The patch
*only* affects drivers/usb because that is the only Makefile that
specifies LINK_FIRST. All the other Makefiles still rely on the kludge
where the link order is im
On Sat, Oct 28, 2000 at 10:03:00PM -0400 Frank Davis wrote:
> I compiled 2.4.0-test10-6 finemodules and all, and for some reason I
> can't mount my root partition on boot..I get a VFS kernel panic.
> #
> # Automatically generated make config: don't edit
> #
[..]
> #
> # ATA/IDE/MFM/RLL suppo
Hello,
I compiled 2.4.0-test10-6 finemodules and all, and for some reason I can't
mount my root partition on boot..I get a
VFS kernel panic. I thought it might have something to do with devfs, but I disabled
it, and it still doesn't work. I'm using loadlin 1.6a..I haven't tried a boot di
Bartlomiej Zolnierkiewicz wrote:
>
> I have ported ide-patch to 2.2.18-17 and I'm now backporting
> 2.4.0 changes. New VIA, SLC, OSB4 drivers and MANY other things
> are already there.I hope that final 2.2.18-ide-patch will have
> IDE functionality equal to this in 2.4.0-test10...
>
> Here is a
Hi all,
I am testing out a modem driver module that works fine on 2.2.14 and
2.2.16. On 2.4.0-test9 I can insmod it with no problem.
When I open up minicom to test out some AT commands I get the kernel oops
below right away, and the system hangs.
System info:
Kernel 2.4.0-test9, gcc version
On Sat, Oct 28, 2000 at 01:15:58PM +0200, Dominik Kubla wrote:
> Even simpler: "gcc -V 2.7.2.3" or "gcc -V 2.95.2" or whatever...
Which was a nice idea, but it doesn't actually work. Changes
in spec file format between versions makes this fall over.
r~
-
To unsubscribe from this list: send the
On Sat, 28 Oct 2000, Bartlomiej Zolnierkiewicz wrote:
>...
> I don't use 2.2.x kernels anymore so I don't do ide-patches for pre
> kernels. But there will be patches for stable 2.2.x. (Although it's
> a real pain - I hate doing backporting instead of new stuff).
I have modified your patch to app
Recently I got a "Professional Workstation" - a 486DX33
with 82596 on board ethernet and NCR(?) on board SCSI.
It was not very difficult to get the 82596 to work
(I put something that works on
ftp.XX.kernel.org/pub/linux/kernel/people/aeb/lp486e.c
comments are welcome)
The 82596 itself is
[EMAIL PROTECTED] (Stephen Harris) said:
> A lot of talk here has been about syslog and DNS blocking, but the
> original message mentioned:
>
> > If you send SIGSTOP to syslogd on a Red Hat 6.2 system (glibc 2.1.3,
> > kernel 2.2.x), within a few minutes you will find your entire machine
> > grin
> >In fact, if you did leave the read queued in a daemon using select()
> >before, you'd keep looping endlessly taking all CPU and never idle
> >because there would always be read data available.
That would be a programming error on the part of the application.
Any application using a level-tr
kernel 2.4.0-test10-pre6, but this has been here as long as I can
remember.
starting wine triggers the bug, C: points to /win2k which is an NTFS
filesystem.
The offending code..
/* It's fscking broken. */
static int ntfs_get_block(struct inode *inode, long block, struct buffer_head *bh
> This problem that you are addressing is caused when solaris sends a
> zero length write (I assume to implement the "access" system call, but
> I haven't checked).
more likely a long standing bug in Solaris that hasn't been stomped.
Tony, you might let Sun know that you have a way to reproduce
vger.timpanogas.org will be down for about 1 hour to upgrade to 2.2.18
and to add more mirroed storage for ISO image space. ftpshut has been
set for 30 minutes, then the server will be down for about an hour. we
apologize for any inconveniance and will have the system back up in
about 1 hour.
Remi Turk wrote:
> > Ok, the problem is that you have an interrupt router table for your Ali
> > 1533, but no interrupt router entry for your IDE device. That's why
> > pci_enable_device is failing.
> >
> > Would you mind testing two kernel patches for me? Both of these changes
> > should be att
On Sat, 28 Oct 2000, Alan Cox wrote:
> Treat this one with care. The LRU corruption fix is one of those 'clearly
> right but makes a mess if its not so clear as it seems' kind of fixes.
>
> Alan
And one kitchen sink...sheesh
Have you reconsidered the suspended backort of ATA by me that Bart is
Jeff Garzik wrote:
>
> Attached below is a message I just sent to someone else who is having
> the same problem as you. Would it be possible for you to try the stuff
> I suggest in the message as well?
>
> Thanks,
>
> Jeff
>
> Subject: Re: No IRQ known for interrupt pin A of device 00
Treat this one with care. The LRU corruption fix is one of those 'clearly
right but makes a mess if its not so clear as it seems' kind of fixes.
Alan
Must fix stuff left to do for 2.2.18final
- New megaraid patch
- Fix the ps/2 misdetect bug that has appeared
- Get to the bott
On Sat, 28 Oct 2000, Heinz J. Mauelshagen wrote:
> > OK, good. I guess that means that the lvmutils (even the
> > patched version in the RPM) are heavily broken ...
>
> As i mentioned before: i wasn't able to reproduce your problem on any of
> my systems. It work just fine with 0.8final and in 0
On Sat, Oct 28 2000, Hisaaki Shibata wrote:
> > > But I could not mkudf nor mkext2fs to my ATAPI 9.4GB new DVD-RAM drive.
> >
> > What do you mean? What happened? strace of mke2fs of mkudf would
> > be nice to have.
>
> My system said it is not permited because it is read only.
[snip]
Ok, does
On Sat, Oct 28 2000, Lorenzo Allegrucci wrote:
> I've got this while trying to play an audio CD by cdplay.
[snip]
> NOTE:
> 2.4.0-test9 works without problems.
2.2.18-pre-latest will do then, could you try that?
--
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
-
To unsubscribe from this list:
Red Hat 7.0, i686, gcc-20001027 (Yes, I know. Just to flush out bugs on
both sides).
abs() is used at least in:
arch/i386/kernel/time.c
drivers/md/raid1.c
drivers/sound/sb_ess.c
gcc warns about use of a non-declared function each time.
No definition for the function is to be found (grep over a
I understand you are in charge of this per MAINTAINERS, it not, I
apologize for bothering you.
Red Hat 7, i686, gcc-20001027 (from CVS) complains about '??)' trigraphs at
lines 1278 and 6367. Should that be just '(?)', or perhaps 'xx'? (egcs-1.1.2
keeps quiet).
[Yes, trigraphs are bletcherous. P
A lot of talk here has been about syslog and DNS blocking, but the
original message mentioned:
> If you send SIGSTOP to syslogd on a Red Hat 6.2 system (glibc 2.1.3,
> kernel 2.2.x), within a few minutes you will find your entire machine
> grinds to a halt. For example, nobody can log in.
Has t
I've got this while trying to play an audio CD by cdplay.
hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdc: packet command error: error=0x54
ATAPI device hdc:
Error: Illegal request -- (Sense key=0x05)
Invalid command operation code -- (asc=0x20, ascq=0x00)
The
Alan Cox wrote:
>
> > In this case, Debian (or any organization who isn't big enough not to fear
> > M-systems) may not ship the standard kernel because it has additional patent
> > restrictions.
>
> Why. There are no distribution restrictions
>
> > There is a clear ability here for the autho
Jeff Garzik wrote:
>
> Remi Turk wrote:
> >
> > Jeff Garzik wrote:
> > >
> > > Ok, after fixing a bad interaction where the Web server was trying to
> > > run dump_pirq as a CGI script, dump_pirq can be retrieved from
> > >
> > > http://gtf.org/garzik/kernel/files/dump_pirq
> >
> > :-)
>
Jeff Garzik wrote:
>
> Remi Turk wrote:
> > Uniform Multi-Platform E-IDE driver Revision: 6.31
> > ide: Assuming 33MHz system bus speed for PIO modes; override with
> > idebus=xx
> > ALI15X3: IDE controller on PCI bus 00 dev 78
> > PCI: No IRQ known for interrupt pin A of device 00:0f.0. Please t
contact [EMAIL PROTECTED]
On Wed 25-10-00 17:19:21, [EMAIL PROTECTED] wrote:
>
>
> On Tue, 24 Oct 2000, Brian Gerst wrote:
>
> > [EMAIL PROTECTED] wrote:
> > >
> > > I just switched from 2.2.17pre9 to 2.4.0pre9, and my joystick won't work
> > > anymore. It's an analog joystick connected to a
Date:Sat, 28 Oct 2000 14:44:03 -0400 (EDT)
From: David Eger <[EMAIL PROTECTED]>
I see nowhere else in do_fork() where sig is set, either. What
gives?
fork.c, around line 560:
*p = *current
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the li
I don't believe that v1.09 (as in Red Hat Linux 7) has this problem, but
does have fixes over-and-above 1.07 (particularly, 1.07 and v1.08 touch
user-space inappropriately, 1.09 fixes). If PeterJ can't get to it before
2.2.18final, Alan, would you consider putting in the v1.09 driver?
Thanks,
Ma
I've been looking at the code for do_fork() / copy_sighand() and am
mystified by the following. It seems that copy_sighand() only sets the
new task's sig member if it is not CLONEd from the parent.
If the signal_struct is CLONEd from the parent, it increments the parent's
signal_struct's refe
On Fri, Oct 27, 2000 at 11:55:03AM -0200, Rik van Riel wrote:
> On Fri, 27 Oct 2000, Andrea Arcangeli wrote:
> > On Fri, Oct 27, 2000 at 11:32:06AM -0200, Rik van Riel wrote:
> > > Have you checked if the CONTENT of the snapshot is indeed
> > > the right LV and not the other one?
> >
> > laser:~
Remi Turk wrote:
> Uniform Multi-Platform E-IDE driver Revision: 6.31
> ide: Assuming 33MHz system bus speed for PIO modes; override with
> idebus=xx
> ALI15X3: IDE controller on PCI bus 00 dev 78
> PCI: No IRQ known for interrupt pin A of device 00:0f.0. Please try
> using pci=biosirq.
test10-pr
> In this case, Debian (or any organization who isn't big enough not to fear
> M-systems) may not ship the standard kernel because it has additional patent
> restrictions.
Why. There are no distribution restrictions
> There is a clear ability here for the author of the driver and m-systems to
>
On Sat, Oct 28, 2000 at 05:24:19PM +0100, Alan Cox wrote:
> The authors of the NTFL layer dont place any additional restrictions on your
> use of the code either. They are merely warning you that if you use it in
> some ways you are going to get your ass kicked by a third party. WHats the
> differ
There is even one more Andrew :-) Here is the full patch:
--- ./net/ipv4/ip_gre.c.~1~ Thu Aug 24 18:48:54 2000
+++ ./net/ipv4/ip_gre.c Sat Oct 28 09:59:43 2000
@@ -1266,7 +1266,9 @@
#ifdef MODULE
register_netdev(&ipgre_fb_tunnel_dev);
#else
+ rtnl_lock();
register_ne
Thought some people here might be interested in this too... Description
quoted below.
--
Jeff Garzik | "Mind if I drive?" -Sam
Building 1024 | "Not if you don't mind me clawing at the
MandrakeSoft| dash and screaming like a cheerleader."
Hi,
I just saw this warning when booting:
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
ALI15X3: IDE controller on PCI bus 00 dev 78
PCI: No IRQ known for interrupt pin A of device 00:0f.0. Please try
using pci=biosi
Andrew Morton wrote:
>
> I think it's more expedient at this time to convert
> acquire_fl_sem/release_fl_sem into lock_kernel/unlock_kernel
> (so we _can_ sleep) and to fix the above alleged deadlock
> via the creation of __posix_unblock_lock()
I agree with me. Could you please test the scalabi
Yep - known problem. AMI have one more pre patch to sort it our Im going back
to the older driver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
> Now firstly, let's eliminate the ISDN red-herring from consideration
> because the authors of the code do not place any additional restrictions
> on the GPL whatsoever, they simply bring it to your attention that using
> an un-certified ISDN stack may be illegal in some countries.
The authors o
LINUX KERNEL PROBLEM REPORT
[1.] Megaraid driver in Linux 2.2.18pre17 hangs on boot
[2.] Full description of the problem:
The Megaraid driver in Linux 2.2.18pre17 (labelling itself as "1.11") hangs
completely
on loading/boot on a DELL 6300, after detecting the DELL PERC adapter
("Found a...")
> I've noticed that sys_read() and sys_write() don't grab the big kernel lock.
> As file descriptors may be shared, must device drivers provide SMP safe
> read() and write() methods ?
Yes. This is true in 2.2 as well although the inode lock provides some protection
on writes.
-
To unsubscribe fr
Brian Gerst wrote:
>
> With or without your patch, the network ioctls are unsafe, since they
> don't currently do refcounting at all. Adding it in the layer above the
> driver is the easier and cleaner solution.
As long as the drivers use unregister_netdevice() then that's
fairly easy to fix wi
I'd guess this is because of a bug that crept into test9,
where a TD is now leaked ... you can get rid of the slab
BUG warning by commenting out the line at the top of
drivers/usb/usb-ohci.c that #defines OHCI_MEM_SLAB.
That TD leak prevents the kmem_cache from getting freed,
and hence prevents t
Andrew Morton wrote:
> --- linux-2.4.0-test10-pre5/fs/locks.c Tue Oct 24 21:34:13 2000
> +++ linux-akpm/fs/locks.c Sun Oct 29 02:31:10 2000
> @@ -125,10 +125,9 @@
> #include
> #include
>
> -DECLARE_MUTEX(file_lock_sem);
> -
> -#define acquire_fl_sem() down(&file_lock_sem)
> -#def
Hi Benson,
On Fri, Oct 27, 2000 at 06:25:45PM -0600, Benson Chow wrote:
> Anyone know if Tekram's DC315/DC395 SCSI driver will be incorporated
> into the kernel distribution? I think their driver is GPL, or was there
> some other reason it wasn't incorporated?
>
> Their source code is on their
I've been looking at the MTD (memory technology device) additions to the
linux 2.4.0 kernels. In particular I'm very interested in the DiskOnChip
2000 and NFTL drivers. However, as terribly useful as this driver is, was
I the only one who caught the following notice at the top of the driver
sour
Philipp Rumpf wrote:
>
> On Sat, Oct 28, 2000 at 09:55:21AM -0400, Brian Gerst wrote:
> > Yes, but they can be called (and sleep) with module refcount == 0. This
> > is because the file descripter used to perform the ioctl isn't directly
> > associated with the network device, thereby not increm
On Sun, Oct 29, 2000 at 02:46:14AM +1100, Andrew Morton wrote:
> [EMAIL PROTECTED] wrote:
> >
> > Change the following two macros:
> > acquire_fl_sem()->lock_kernel()
> > release_fl_sem()->unlock_kernel()
> > then
> > 5192 Req/s @8cpu is got. It is same as test8 within fluctuation
James Lewis Nance <[EMAIL PROTECTED]> writes:
> On an unrelated note, is it possible for a process in 2.4 to see more
> than 2G of address space? They seem to be limited to 2G for me. I
> was hoping that the HIMEM stuff had removed that limit.
You have 3GB user space address space. 1 GB is
[EMAIL PROTECTED] wrote:
>
> Change the following two macros:
> acquire_fl_sem()->lock_kernel()
> release_fl_sem()->unlock_kernel()
> then
> 5192 Req/s @8cpu is got. It is same as test8 within fluctuation.
hmm.. BKL increases scalability. News at 11.
The big question is: why i
On Saturday 28 October 2000 16:43, you wrote:
> > I've noticed that sys_read() and sys_write() don't grab the big kernel
> > lock. As file descriptors may be shared, must device drivers provide SMP
> > safe read() and write() methods ?
>
> no. FD's refer to files; block drivers don't, and the non
On Sat, Oct 28, 2000 at 09:55:21AM -0400, Brian Gerst wrote:
> Yes, but they can be called (and sleep) with module refcount == 0. This
> is because the file descripter used to perform the ioctl isn't directly
> associated with the network device, thereby not incrementing the
> refcount on open.
Hi,
I've noticed that sys_read() and sys_write() don't grab the big kernel lock.
As file descriptors may be shared, must device drivers provide SMP safe
read() and write() methods ?
TIA
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
> I have a question - Why does the PLIP driver does consume so much CPU ?
> I tried it today, and when i did ping -s 16000 dst_ip, the kernel consumed
> about 50% of the CPU time ( /proc/cpuinfo and /proc/interrupts follow).
> Any ideas ?
It has to bang on the parallel port controller the hard
Thanks, Axboe
> > But I could not mkudf nor mkext2fs to my ATAPI 9.4GB new DVD-RAM drive.
>
> What do you mean? What happened? strace of mke2fs of mkudf would
> be nice to have.
My system said it is not permited because it is read only.
execve("/sbin/mke2fs", ["/sbin/mke2fs", "/dev/hdc"], [/*
Andrew Morton wrote:
>
> "Stephen E. Clark" wrote:
> >
> > When I configure in Tunneling I get the following error message. Is this
> > normal? This with 2.4test9pre5
> >
> > GRE over IPv4 tunneling driver
> > RTNL: assertion failed at devinet.c(775):inetdev_event
>
> The rtnetlink lock needs to
On Fri, 27 Oct 2000, Benson Chow wrote:
> Anyone know if Tekram's DC315/DC395 SCSI driver will be incorporated
> into the kernel distribution? I think their driver is GPL, or was there
> some other reason it wasn't incorporated?
The driver will not be included until its maintainer, currently Ku
Philipp Rumpf wrote:
>
> On Sat, Oct 28, 2000 at 09:37:28AM -0400, Brian Gerst wrote:
> > Philipp Rumpf wrote:
> > > - you can't copy_(from|to)_user in the module exit function (which would
> > > be copies from/to rmmod anyway)
> >
> > Unfortunately, you need to be able to use copy_*_user() from
On Sat, Oct 28, 2000 at 09:37:28AM -0400, Brian Gerst wrote:
> Philipp Rumpf wrote:
> > - you can't copy_(from|to)_user in the module exit function (which would
> > be copies from/to rmmod anyway)
>
> Unfortunately, you need to be able to use copy_*_user() from the network
> ioctls, and this is
Philipp Rumpf wrote:
>
> On Fri, Oct 27, 2000 at 10:49:53PM +1100, Andrew Morton wrote:
> > Look, this modules stuff is really bad. Phillip Rumpf proposed
> > a radical alternative a while back which I felt was not given
>
> While it might be a "radical alternative", it doesn't require any chan
On Fri, Oct 27, 2000 at 10:49:53PM +1100, Andrew Morton wrote:
> Look, this modules stuff is really bad. Phillip Rumpf proposed
> a radical alternative a while back which I felt was not given
While it might be a "radical alternative", it doesn't require any changes
to the subsystems that have be
I have a question - Why does the PLIP driver does consume so much CPU ?
I tried it today, and when i did ping -s 16000 dst_ip, the kernel consumed
about 50% of the CPU time ( /proc/cpuinfo and /proc/interrupts follow).
Any ideas ?
shtajga:~# cat /proc/cpuinfo
processor : 0
vendor_id
>The Becker's driver from ftp://ftp.scyld.com/pub/network/eepro100.c cures
>the error messages, but the network still stalls, and worse yet, seems to
>stall forever (as opposed to few minutes with 2.2.18pre17 driver).
this eepro100.c works for me
asus/dual piii-800 133mhz/768ram ecc/mylex-170/2x
On Fri, 27 Oct 2000 13:01:32 +0200,
Markus hennig <[EMAIL PROTECTED]> wrote:
>config.c:311: #error "HiSax: No cards configured"
>su.c:75: asm/oplib.h: No such file or directory
>su.c:77: asm/ebus.h: No such file or directory
>newport.c:11: asm/gfx.h: No such file or directory
>newport.c:12: asm/n
"Stephen E. Clark" wrote:
>
> When I configure in Tunneling I get the following error message. Is this
> normal? This with 2.4test9pre5
>
> GRE over IPv4 tunneling driver
> RTNL: assertion failed at devinet.c(775):inetdev_event
The rtnetlink lock needs to be taken around
register_netdevice().
On Mon, Oct 23, 2000 at 11:22:53PM -0400, Burton Windle wrote:
> Sorry if this is user-error, but after about 20min of using
> 2.4.0-test10-pre5, my Debian Woody system dropped out of X with this
> message in syslog:
>
> [drm:drm_release] *ERROR* Process 256 dead, freeing lock for context 1
>
>
Linus,
This patch allows a (ptrace) parent to unambiguously distinguish between a
child ptrace stop following a PTRACE_SYSCALL due to a system call and a ptrace
stop due to delivery of a SIGTRAP.
Currently, when PTRACE_SYSCALL is being used, it's not possible to tell for
certain why a particular
On Sat, 28 Oct 2000 11:02:04 +0100 (BST),
Alan Cox <[EMAIL PROTECTED]> wrote:
>> of get_module_symbol this weekend. The inter-object registration code
>> will allow two objects to pass data to each other, it will not matter
>> whether the objects are both modules, one module and one built in (in
> Linus wants get_module_symbol removed.
> http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg08791.html
Looks to me like Linus asks if some stuff can go away. I don't see a Linus
comment on the rest of the discussion about why removing it is bad at all.
And by Linus own rules. Its too
> of get_module_symbol this weekend. The inter-object registration code
> will allow two objects to pass data to each other, it will not matter
> whether the objects are both modules, one module and one built in (in
> either order) or both built in. When modules are involved there will
> be full
On Sat, 28 Oct 2000 05:40:28 -0400 (EDT),
Alan Cox <[EMAIL PROTECTED]> wrote:
>> cc list trimmed. Nobody has come up with a "must have" reason for
>> get_module_symbol and that interface is broken as designed. I will be
>
>Nobody has come up with a 'must break existing sane code' reason either.
> cc list trimmed. Nobody has come up with a "must have" reason for
> get_module_symbol and that interface is broken as designed. I will be
Nobody has come up with a 'must break existing sane code' reason either.
> will allow two objects to pass data to each other, it will not matter
> whether
Jonathan Hudson wrote:
> In article <[EMAIL PROTECTED]>,
> "Jeff V. Merkey" <[EMAIL PROTECTED]> writes:
>
> JVM> Grab the pcmcia off sourceforge. It seems to build and work. The stuff
> JVM> in 2.4 at present is still somewhat broken. I worked on this until 2:00
> JVM> last night getti
Hi Alan.
This patch simply corrects a couple of comments in the said file to
reflect what the code actually does rather than (presumably) what the
code used to do at some time in the distant past.
In my case, I've been working on a patch for the kernel that uses
these facilities, and was getting
On Sat, Oct 28 2000, Andre Hedrick wrote:
> > This is not necessary, the ide-cd driver will set the read-only
> > flag appropriately depending on the device type detected.
>
> This may not be the best option as the default.
> If a dvd-ram is used for backup you may not always want it in RW mode.
On Sat, 28 Oct 2000, Jens Axboe wrote:
> This is not necessary, the ide-cd driver will set the read-only
> flag appropriately depending on the device type detected.
This may not be the best option as the default.
If a dvd-ram is used for backup you may not always want it in RW mode.
Just a thoug
82 matches
Mail list logo
