Re: [techtalk] ejecting the #$%#$! cdrom

2000-05-30 Thread Adriana Gonzalez
sara korhonen wrote: > > > Once in a while Linux (RH 6.2) will insist that a cdrom is busy and > > thus will not let me umount it and thus will not let me eject it. After > > what quite often happens to me is that i've done cd /mnt/cdrom (or where > ever you have mounted your cdrom) and i've t

Re: [techtalk] ejecting the #$%#$! cdrom

2000-05-30 Thread Jeff Dike
> Once in a while Linux (RH 6.2) will insist that a cdrom is busy and > thus will not let me umount it and thus will not let me eject it. Another handy thing is lsof. lsof | grep /mnt/cdrom will tell you what processes have open files in /mnt/cdrom (I think - my system seems not to have lsof

Re: [techtalk] ejecting the #$%#$! cdrom

2000-05-30 Thread moebius
Hey Samantha, Does Gnome automount the CD? If so then "device busy" would be appropriate. Does this happen in command line only? You can check in Gnome to see if it's mounted by opening up an xterm and typing the command 'mount'. That will show you all the filesystems that are currently mounted.

Re: [techtalk] ejecting the #$%#$! cdrom

2000-05-30 Thread Telsa Gwynne
On Tue, May 30, 2000 at 01:50:02AM +0800 or thereabouts, Samantha Atkins wrote: > Once in a while Linux (RH 6.2) will insist that a cdrom is busy and > thus will not let me umount it and thus will not let me eject it. After I know the feeling. I meet this occasionally with RH 6.1. > looking a

Re: [techtalk] ejecting the #$%#$! cdrom

2000-05-30 Thread sara korhonen
> Once in a while Linux (RH 6.2) will insist that a cdrom is busy and > thus will not let me umount it and thus will not let me eject it. After what quite often happens to me is that i've done cd /mnt/cdrom (or where ever you have mounted your cdrom) and i've tried to umount it -- of course wi

[techtalk] ejecting the #$%#$! cdrom

2000-05-30 Thread Samantha Atkins
Once in a while Linux (RH 6.2) will insist that a cdrom is busy and thus will not let me umount it and thus will not let me eject it. After looking all over the system, bring down X and looking again, I am convinced I have no process active that has any business hanging on to this thing. And no