![]() | |||||||||||||
Messages in this thread |
On Tue, Feb 03 2004, Richard B. Johnson wrote: > On Tue, 3 Feb 2004, [iso-8859-1] Måns Rullgård wrote: > > > John Bradford <john@grabjohn.com> writes: > > > > > Regardless of specs, I don't know what the majority of devices in the > > > real world actually do. Maybe Jens and Alan, (cc'ed), can help. > > > > Just tested with an ASUS SCB-2408 in my laptop. It gives read errors > > after doing a fast erase, just like it should. > > > > -- > > Måns Rullgård > > mru@kth.se > > - > > I had to borrow a R/W CDROM because most everybody uses CR-R only > here. That's why it took so long to check. With SCSI, Linux 2.4.24, > cdrecord fails to umount the drive before it burns it. The result > is that the previous directory still remains at the mount-point. > This, even though cdrecord ejected the drive to "re-read" its > status. > > Bottom line: If the CDROM isn't umounted first, you can still > get a directory entry even though the CDROM has been written with > about 500 magabytes of new data. So what? Just because you can do it, doesn't mean it's a valid thing to do. You can literally come up with thousands of similar weird things, if you wanted to. This whole discussion is silly and pointless. -- Jens Axboe - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:00 [W:0.377 / U:0.000 seconds] ©2003-2008 Jasper Spaans | |||||||||||||