From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sed crash
Date: Thu, 5 Feb 2009 23:56:25 +0100 [thread overview]
Message-ID: <5d375e920902051456m525f79a6sc1c417c5690a53ac@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0902050927n7782427cx86eb3f4bcf55f0a8@mail.gmail.com>
Cool, thanks again!
uriel
On Thu, Feb 5, 2009 at 6:27 PM, Russ Cox <rsc@swtch.com> wrote:
>> P.S.: Silly question, why is du(1) not built by default in p9p? The
>> code already there seems to work as far as I can tell..
>
> It's a long story, dating back to when the standard mode of
> operation was to put $PLAN9/bin ahead of the system binaries
> in your $PATH. In that context it didn't make sense to include
> tools like du, dd, and grep, because too many programs
> expected to get the standard tool rather than the Plan 9 one.
>
> The 9 script made it easier to live with $PLAN9/bin at the
> end of the $PATH, so now there's no harm in having those.
> I've re-enabled dd and du.
>
> Russ
>
>
prev parent reply other threads:[~2009-02-05 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 2:28 Uriel
2009-02-05 2:59 ` Pietro Gagliardi
2009-02-05 3:08 ` Pietro Gagliardi
2009-02-05 3:45 ` Pietro Gagliardi
2009-02-05 3:51 ` Akshat Kumar
2009-02-05 3:58 ` andrey mirtchovski
2009-02-05 4:39 ` Pietro Gagliardi
2009-02-05 11:14 ` Iruata Souza
2009-02-05 13:16 ` erik quanstrom
2009-02-05 14:31 ` Joel C. Salomon
2009-02-05 14:44 ` erik quanstrom
2009-02-05 21:02 ` Pietro Gagliardi
2009-02-05 21:13 ` erik quanstrom
2009-02-07 0:21 ` Derek Fawcus
2009-02-05 21:21 ` john
2009-02-05 23:02 ` Akshat Kumar
2009-02-05 23:11 ` hiro
2009-02-05 23:18 ` Akshat Kumar
2009-02-05 4:15 ` Russ Cox
2009-02-05 14:41 ` Uriel
2009-02-05 17:27 ` Russ Cox
2009-02-05 22:56 ` Uriel [this message]
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=5d375e920902051456m525f79a6sc1c417c5690a53ac@mail.gmail.com \
--to=uriel99@gmail.com \
--cc=9fans@9fans.net \
/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).