From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] some light reading
Date: Thu, 19 Aug 2004 01:52:36 +0200 [thread overview]
Message-ID: <023a01c4857e$7068daf0$73587d50@SOMA> (raw)
In-Reply-To: <Pine.BSI.4.58.0408181339080.23447@malasada.lava.net>
> Yes, it is inefficient, but no more so than if you have a shell
> which searches $PATH each time it runs a command.
nonsense. $PATH involves an O(n) number of exec(2)'s
and syscalls are expensive and n is usually not small. on
plan 9 n is 2 -- . and /bin and these two execs do all
the hard work in the kernel.
put the cache in the kernel, if such a thing is needed,
rather than replicating it badly n times in some horror
like bash.
next prev parent reply other threads:[~2004-08-18 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 19:46 andrey mirtchovski
2004-08-18 23:44 ` Tim Newsham
2004-08-18 23:52 ` boyd, rounin [this message]
2004-08-19 0:00 ` andrey mirtchovski
2004-08-19 6:24 ` Boris Maryshev
2004-08-19 18:39 ` Roman Shaposhnick
2004-08-19 22:37 ` Charles Forsyth
2004-08-19 22:38 ` boyd, rounin
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='023a01c4857e$7068daf0$73587d50@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.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).