home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
- Newsgroups: comp.os.linux
- Subject: Re: Short filenames under Linux
- Date: 25 Dec 1992 11:16:32 -0600
- Organization: Kansas State University
- Lines: 29
- Message-ID: <1hfflgINN8hm@matt.ksu.ksu.edu>
- References: <9235714.11059@mulga.cs.mu.OZ.AU> <1992Dec26.020222.349@plasma.apana.org.au>
- NNTP-Posting-Host: matt.ksu.ksu.edu
- Keywords: The number fourteen
-
- mph@plasma.apana.org.au (Martin Peter Howell) writes:
-
- >cdillon@muse.cs.mu.OZ.AU (Craig Dillon) writes:
-
- >>Now, I know that there is one standard form of Un*x that has 14 character
- >>filenames - but lets face it - who uses it and is happy? So I know I can't
- >>complain - I'm not. Linux (apart from the filename length) is great, but I
- >>do have the following questions:
-
- >>(2) Does anyone know how to get around the problem? I looked into the
- >> kernel source, but not being knowledgeable on these things, I can't
- >> be sure that it would be an easy change or not. I presume not,
- >> otherwise other people would have done it already. Any clues?
-
- >Has anyone tried recompiling the minix fs with, say, 40 character filenames,
- >is this just a matter of changing a #define? Since I am about to install
- >a new linux system on my second machine and dont care about the backward
- >compatibility, I would love to do this and still maintain the performance
- >benefits of the minix fs over the extfs.
-
- >-Martin.
- >mph@plasma.apana.org.au
-
- The problem with doing this, is that no binaries that access the files will
- work anymore. Stuff like ls, bash, make.... will all be broken. You would
- need to make a new fs, and then recompile all those binaries to use it before
- actually making a fs on something.
-
- James
-