From: drew@cs.colorado.edu (Drew Eckhardt) Subject: Re: OK, OK, I get the message! Date: 13 Feb 1992 00:41:24 GMT
In article <1992Feb10.155653.1@cc.curtin.edu.au> nmurrayr@cc.curtin.edu.au writes:
> OK, enough already! Thanks to all those who replied; I now understand all
>about long file names!
>
> I guess I could see the uses of longer filenames before I posted the
>original message; what I DIDN'T know about was the filename completion
>available with the TAB key in bash. The book I have on Unix, while otherwise
>quite useful, is really about Berkeley Unix and doesn't seem to mention
>filename completion at all. I suppose the man page on bash talks about it, but
>I haven't read it all (who reads documentation anyway?).
tcsh, bash, newer versions of csh, ksh all do file name completion. Standard
Bourne Shell does not. Filename completion is not a standard 'Unix' thing -
although all of the more popular shells support it.
>
> Changing the subject (nothing up my sleeve ...), I get strange problems
>using Linux v0.12 (BTW, is it pronounced line'-ux or linn'-ux?). One problem
>occurs when I've been working in a subdirectory (eg to compile mtools), then
>remove all files in the directory, go up a level, and try to rmdir the
>subdirectory. Linux will often refuse, claiming I'm not the owner. Now as
>far as I understand it, the superuser should be able to do most anything, so
If the working directory of any process is that directory, it cannot
be removed. You just aren't getting the correct error message.
>it does seem abnormal. Using chmod to change the file permissions doesn't
>seem to make much difference either -- the permissions get changed, but I
>still can't remove the directory. If I either reboot or logout, I can remove
>the directory with no problems. What's going on?
>
> .....Ron
Rebooting will kill off the process that has that directory as its wd.
Logging out should cause all of your foreground process to be killed,
and if that's what's in the directory...