From: Donn Cave <donn@milton.u.washington.edu>
To: rc@archone.tamu.edu
Subject: f.c.
Date: Mon, 1 Jul 1991 15:33:04 -0500 [thread overview]
Message-ID: <9107012033.AA24199@milton.u.washington.edu> (raw)
I'm posting this from a system with 6910 entries in /etc/passwd. We used
a hashed passwd data base to speed things up. Would a "/u" approach be
feasible here - searching a single directory with ca. 7K symbolic-link
entries? Maybe we could make a tree - instead of "/u/donn", say "/u/d/o/n/n".
Donn Cave, University Computing Services, University of Washington
donn@cac.washington.edu
next reply other threads:[~1991-07-01 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-07-01 20:33 Donn Cave [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-07-01 19:04 f.c Byron Rakitzis
1991-07-01 21:04 ` f.c Mark-Jason Dominus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9107012033.AA24199@milton.u.washington.edu \
--to=donn@milton.u.washington.edu \
--cc=rc@archone.tamu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).