9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [sources] 20070410: % cat
Date: Thu, 12 Apr 2007 14:16:28 -0400	[thread overview]
Message-ID: <ee9e417a0704121116j40b360d4p1fb24bd34191eee8@mail.gmail.com> (raw)
In-Reply-To: <509071940704121100h26ba7cfejed87a87cbbfaebaa@mail.gmail.com>

On 4/12/07, Anthony Sorace <anothy@gmail.com> wrote:
> I'm having trouble understanding the motivation behind /cfg, as
> compared to /sys/lib/sysconfig. The later seems much more general
> (although i'm not clear on the pxe case specifically), as well as
> having the aesthetic benefit of not needlessly cluttering root.
>
> Am I missing something?

To start with, Plan 9 can handle as many things in the
root as you like.  It is not constrained by the size
of an rk05 or the time to fsck the root partition.

At the time, /cfg was deemed shorter to type.
There is no real difference, except that there
are programs that actually use /cfg and nothing
ever used /sys/lib/sysconfig.  It's too late to
turn back now.  I didn't really like /cfg at the
time, but I've gotten used to it, and I do believe
that part of why it gets used is the much
shorter name.

Russ


  reply	other threads:[~2007-04-12 18:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
2007-04-12 15:14 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF Uriel
2007-04-12 15:32   ` Devon H. O'Dell
2007-04-12 15:48     ` erik quanstrom
2007-04-12 16:03       ` Devon H. O'Dell
2007-04-12 16:05       ` Russ Cox
2007-04-12 15:56     ` Uriel
2007-04-12 16:08       ` Devon H. O'Dell
2007-04-12 17:42         ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:00           ` Anthony Sorace
2007-04-12 18:16             ` Russ Cox [this message]
2007-04-12 18:57               ` Anthony Sorace
2007-04-13  4:04           ` Lucio De Re
2007-04-13  4:58             ` geoff
2007-04-12 18:25       ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF ron minnich
2007-04-12 18:38         ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:43           ` Devon H. O'Dell
2007-04-12 18:40         ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF erik quanstrom
2007-04-12 18:50           ` Francisco J Ballesteros
2007-04-12 18:41         ` Russ Cox
2007-04-13  4:18           ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13  4:59             ` geoff
2007-04-12 18:48         ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF andrey mirtchovski
     [not found] <12a554de22f1992874430323d774bd88@plan9.bell-labs.com>
2007-04-13  6:00 ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13 14:25   ` Devon H. O'Dell
2007-04-13 14:56     ` erik quanstrom
2007-04-13 18:22       ` Lyndon Nerenberg
2007-04-13 21:39         ` Paweł Lasek
2007-04-14 14:51           ` Russ Cox
2007-04-13 15:00     ` Lucio De Re

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=ee9e417a0704121116j40b360d4p1fb24bd34191eee8@mail.gmail.com \
    --to=rsc@swtch.com \
    --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).