Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!bionet!csd4.milw.wisc.edu!leah!rpi!crdgw1!ge-dab!peora!ucf-cs!farbmac!goldfarb
From: goldfarb@farbmac.UUCP (Benjamin I. Goldfarb)
Newsgroups: comp.unix.questions
Subject: Re: Directory File Inode Structure
Summary: Unix filenames CAN exceed 14 characters.
Keywords: Inodes
Message-ID: <186@farbmac.UUCP>
Date: 1 Jun 89 10:36:30 GMT
References: <5434@ingr.com> <1545@doctor.ATT.COM>
Organization: Longwood FL
Lines: 21

In article <1545@doctor.ATT.COM>, bmadhyan@doctor.ATT.COM (Bharat Madhyani ) writes:
> Every directory entry is 16 bytes long. First 2 bytes are for the inode#
> and the rest of the bytes (i.e 14) are for the filename. In Unix no
> filename can exceed more than 14 characters. If the filename is less
> than 14 characters , it is appended by null characters.

Funny.  I was just sitting here on my Berkeley 4.3 system editing a file
called ThisGuysGotANarrowViewOfUnix, which sorta exceeds 14 characters,
and when I did an ls it sorta appeared in its entirety.  Is my UNIX
brain-damaged?  (All right, guys...no comebacks about Berkeley bogosity!)

For your enlightenment, Bharat: Berkeley has allowed 255 character file names
since 4.2 whether anybody likes it or not.  Portability is obviously compromised
when file names longer than 14 characters are used but that still doesn't
validate your incorrect statement.

-- 
------------------------------------------------------------------------------
Ben Goldfarb			uucp: {decvax,peora}!ucf-cs!farbmac!goldfarb
Department of Computer Science	Internet: goldfarb%farbmac.uucp@ucf-cs.ucf.edu
University of Central Florida	BITNET: GOLDFARB@UCF1VM