From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <5d375e920902050641p78dc58f8uc97a98984a507b83@mail.gmail.com> References: <5d375e920902041828p173f0f3etdd5fabd3a65bc330@mail.gmail.com> <5d375e920902050641p78dc58f8uc97a98984a507b83@mail.gmail.com> Date: Thu, 5 Feb 2009 09:27:21 -0800 Message-ID: Subject: Re: [9fans] sed crash From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 9740fd0c-ead4-11e9-9d60-3106f5b1d025 > 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