It seems that the constant is in /usr/sys/sys/mount.h.
The limit is already there since the initial import in
1995. (From 4.4BSD?)
I want to know what is the root cause preventing a
larger value.
PS: I have found some interesting links about
MNAMELEN:
http://leaf.dragonflybsd.org/mailarchive/kernel/2003-08/msg00194.html
http://www.secnetix.de/~olli/FreeBSD/mnamelen.hawk
>From Compaq(HP) Tru64 UNIX 5.1 man pages, it seems
that Tru64 UNIX also have a restriction of 90
chars.(They also based on BSD?)
http://h30097.www3.hp.com/docs/base_doc/DOCUMENTATION/V51B_HTML/MAN/MAN2/0114____.HTM
_________________________________________________________
必殺技、飲歌、小星星...
浪漫鈴聲 情心連繫
http://us.rd.yahoo.com/evt=22281/*http://ringtone.yahoo.com.hk/
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hacke...@freebsd.org"
> On Wednesday 04 August 2004 17:40, Patrick Dung wrote:
> > Hi
> >
> > It seems that the constant is in /usr/sys/sys/mount.h.
> > The limit is already there since the initial import in
> > 1995. (From 4.4BSD?)
> > I want to know what is the root cause preventing a
> > larger value.
> >
> > PS: I have found some interesting links about
> > MNAMELEN:
> >
> > http://leaf.dragonflybsd.org/mailarchive/kernel/2003-08/msg00194.html
> >
> > http://www.secnetix.de/~olli/FreeBSD/mnamelen.hawk
I recall bringing this up on the FreeBSD lists a while ago (1-2 years?) and
IIRC, the reason this is tough to change is that we use this constant in a
lot of internal structures, and changing the constant will change the
structure sizes which will break a lot of things.
>From what I've seen in the Linux code, they never store a "char
blah[MNAMELEN]" in their structures, but rather, a pointer to that data
element (in the name cache, I think). Thus, they are free to change the
size of the element without affecting the majority of structures that use
it.
--
Matt Emmerton