Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!blake!ogccse!littlei!omepd!merlyn
From: merlyn@intelob.intel.com (Randal L. Schwartz @ Stonehenge)
Newsgroups: comp.unix.wizards
Subject: inodes (was Re: unix question: files per directory)
Message-ID: <4290@omepd.UUCP>
Date: 11 Apr 89 23:22:28 GMT
References: <24110@beta.lanl.gov> <4822@macom1.UUCP>
Sender: news@omepd.UUCP
Reply-To: merlyn@intelob.intel.com (Randal L. Schwartz @ Stonehenge)
Followup-To: comp.unix.wizards
Distribution: na
Organization: Stonehenge; netaccess via BiiN, Hillsboro, Oregon, USA
Lines: 21
In-reply-to: rikki@macom1.UUCP (R. L. Welsh)

In article <4822@macom1.UUCP>, rikki@macom1 (R. L. Welsh) writes:
| From article <24110@beta.lanl.gov>, by dxxb@beta.lanl.gov (David W. Barts):
| > 
| > How many files can there be in a single UNIX directory
| ...
| 
| You will undoubtedly run out of inodes before you reach any theoretical
| limit.  Every new file you create will use up one inode.

Not quite.  Try 'ln a b >a'.  Only uses one inode, but two directory
slots.  Do that enough (pragmatically determined :-) times, and you
can (theoretically) run out of directory (or disk) room before running
out of inodes.

Just a lurking guru,
(okay, did I blow it this time too..? :-)
-- 
/=====Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095========\
{        on contract to BiiN (for now :-) Hillsboro, Oregon, USA.             }
{<@intel-iwarp.arpa:merlyn@intelob.intel.com> ...!uunet!tektronix!biin!merlyn }
\=====Cute quote: "Welcome to Oregon... home of the California Raisins!"======/