lkml.org 
[lkml]   [1999]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Questions on CDROM support
> > 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.

Question, is it possible to have the kernel tell the process that it's cwd
is / ?

--
Lab tests show that use of micro$oft causes cancer in lab animals

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.053 / U:0.820 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site