Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[BLU] Re: Linux/Unix naming conventions...



On Thu, 23 Dec 1999, Seth Gordon wrote:

> "John Chambers,,,781-647-1813" wrote:
> 
> > The only characters that have special meaning
> > to the Unix file system are slash and null.
> 
> Not to disagree, but to supplement: some utilities assume, by default, that file
> names don't have any spaces in them.  (For example, they will interpret a group of
> words separated by spaces as a group of filenames.)  Therefore, creating files
> with embedded spaces is Generally Not Done, although it's technically possible,
> and there are ways to coerce the rest of Unix into treating them properly.

Also files beginning with a period are treated special by some parts of
UNIX and some applications.  However, you are right in that the
kernel/filesystem don't care.

-------------------------------------------------------------------
DDDD   David Kramer                   http://kramer.ne.mediaone.net
DK KD  
DKK D  It is better to be defeated on principal than to win on lies
DK KD  
DDDD                                                 Arthur Calwell



-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org