Messages in this thread | | | From | "Anthony Barbachan" <> | Subject | Re: Questions on CDROM support | Date | Mon, 11 Oct 1999 02:26:18 -0400 |
| |
> > currently open on the CDROM. I don't want to be called away from > > programming to find out why a CDROM from a CDROM server refuses to > > eject/open a CDROM, when the usual case is that some shell or process just > > happens to currently be in its mount directory or one of the decending ones. > > As far as I'm converned this is not a desirable behaviour. Something like > lsof will allow you to work out what the offending process is. Processes > generally don't like their cwd disappearing from beneath them. > > Ian
The indented setup for this use is mostly for CDROMs shared by samba servers to DOS/Windows clients. In this setup DOS/Windows easily handle disappearing cwd as those OS's generally expect that CD's may be ejected. And under Linux I know that at least bash deals with a lost cwd well. And thats the main one that I'd be concerned about under Linux. In the current setup one running shell, probably just left minimized somewhere or on a forgotten login that happened to have its cwd somewhere under /cdrom creates the administrative headache of having to track the offending process(es) down and correct the situation. Nowhere near userfriendly and creates extra administrative work.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |