home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!usc!sdd.hp.com!ncr-sd!crash!cwr
- From: cwr@crash.cts.com (Will Rose)
- Subject: Re: Another MacMINIX 'suggestion'
- Organization: CTS Network Services (crash, ctsnet), El Cajon, CA
- Date: 23 Jan 93 15:04:44 PST
- Message-ID: <1993Jan23.150444.16610@crash>
- References: <1jqrr5INNbbo@usenet.INS.CWRU.Edu>
- Lines: 31
-
- James Abendschan (bf795@cleveland.Freenet.Edu) wrote:
- :
- : >Date: Fri Jan 22 08:05:47 1993
- : >From: jimlynch@netcom.com (Jim Lynch)
- : >Subject: Re: Things I Wish Were In MINIX
- : >To: bf795@cleveland.Freenet.Edu
- : >Newsgroups: comp.os.minix
-
- [lines omitted]
-
- : >On longer names: the files limits.h, unistd.h and ar.h all have a
- : >#define whose name contains NAME_MAX. Can I increase this value
- : >without screwing things up? Specifically, would I then have a different
- : >flavor of directory entry (and therefore a different flavor of
- : >filesystem?)
- :
- : Actually, I think 13 chars is a POSIX requirement or some such. I
- : don't know about this. It should work though, I suppose.
-
- NAME_MAX is the maximum length of a filename; depending on how it is
- used in application programs or the kernel, changing it could blow
- away the filesytem on which the resultant programs are run. Minix
- uses short filenames of 14 characters because a 14 character filename
- and a 16 bit inode number fit into a 16 byte directory entry. You
- can write filesystems with very_long_names, and I think it's been
- done for Minix, but I wouldn't just change NAME_MAX and recompile
- if I were you...
-
- Good luck - Will
- cwr@crash.cts.com
-
-