Newsgroups: comp.os.minix
Subject: Re: _POSIX_NAME_MAX in Minix
From: no@spam.com (Michael Henry)
References: <8f11ai$i9j$1@news.roedu.net>
Organization: NEIS Pty. Ltd.
Message-ID: <8F2E64802MichaelHenryneiscoma@203.2.194.51>
User-Agent: Xnews/Y2K-SE
Lines: 28
NNTP-Posting-Host: 203.102.220.66
X-Trace: ozemail.com.au 957743342 203.102.220.66 (Mon, 08 May 2000 09:49:02 EST)
NNTP-Posting-Date: Mon, 08 May 2000 09:49:02 EST
Distribution: world
Date: Sun, 07 May 2000 23:49:02 GMT
Path: news.adfa.oz.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!intgwpad.nntp.telstra.net!newsfeed.berkeley.edu!newsfeed.concentric.net!newsfeed.ozemail.com.au!ozemail.com.au!not-for-mail
Xref: news.adfa.oz.au comp.os.minix:35232

>I've discovered one header file called LIMITS.H in which I've found this
>: 
>        #define _POSIX_NAME_MAX        14
>Could this be all that is to be done ? I mean if I recompile the kernel
>with this limit modified, the file system should work with let's say, 20
>chars file names ?

I just finished "The Design and Implementation of the 4.4 BSD Operating
System", which includes a section on how they allowed filenames up to
255 characters. This involved adding another field to the directory
entry which is the length of the name.

ie.

+-------+------+-----+-------+------+----------------+-----------
|Inode #|Length|a.out|Inode #|Length|A-very-long-name|
+-------+------+-----+-------+------+----------------+-----------
           |         ^          |                    ^
           |         |          |                    |
           +---------+          +--------------------+

There's more to it than that, of course, but that's the gist of it.

Hope this helps,
    	
    	Michael


