9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Joshua Wood <josh@utopian.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] CPU Server
Date: Thu, 27 Dec 2007 19:09:41 -0800	[thread overview]
Message-ID: <A1AA9B77-932C-4C30-A9D4-1136151D62EE@utopian.net> (raw)

I think you are under-reading Erik's comment above about the  
flexibility of these facilities ((/cfg/$sysname/ /bin/)^cpurc[.local]  
and friends) being mere rc. I also think the suggested changes are  
rather narrowly focused on the procedure described in the wiki for  
constructing an `all-in one' cpu/auth/terminal. I'm not sure you've  
given the same consideration to the many ways of distributing Plan 9  
that has been given to the default scripts in the distribution. (This  
is not to say those default scripts can't be improved.)

The suggested changes are really documentation (that's why they are  
all commented) for building a very particular sort of `combo' Plan 9  
system; IMO you should maybe change the wiki but not the scripts.

--
Josh


             reply	other threads:[~2007-12-28  3:09 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28  3:09 Joshua Wood [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-22 23:12 "Rodolfo \"kix\" Garci­a"
2007-12-22 23:15 ` Iruata Souza
2007-12-23  3:13 ` John Soros
2007-12-23  3:35   ` erik quanstrom
2007-12-27 16:16     ` "Rodolfo \"kix\" Garci­a"
2007-08-15 22:13 Rodolfo (kix)
2007-08-16  1:26 ` geoff
2007-08-16 13:18   ` rob
2007-08-16 13:29     ` erik quanstrom
2004-02-07  0:24 [9fans] cpu server vdharani
2004-02-06 22:50 ` Jim Choate
2004-02-07  3:41   ` Bruce Ellis
2004-02-07 14:48     ` Jim Choate
2004-02-07 15:21       ` Bruce Ellis
2004-02-07 16:05         ` Jim Choate
2004-02-07 19:54           ` Charles Forsyth
2004-02-07 22:26             ` a
2004-02-07 23:16               ` andrey mirtchovski
2004-02-09 17:47                 ` rog
2004-02-09 18:19                   ` andrey mirtchovski
2004-02-09 18:43                     ` rog
2004-02-09 18:49                       ` andrey mirtchovski
2004-02-09 18:49                     ` rog
2004-02-09 18:50                       ` andrey mirtchovski
2004-02-09 19:32                     ` 9nut
2004-02-09 18:44                       ` andrey mirtchovski
2004-02-10  1:38                     ` Kenji Okamoto
2004-02-10  1:40                       ` David Presotto
2004-02-10  1:50                       ` boyd, rounin
2004-02-10  1:11                         ` andrey mirtchovski
2004-02-10  3:03                           ` Lyndon Nerenberg
2004-02-10  5:00                           ` Geoff Collyer
2004-02-11  3:14                             ` Jack Johnson
2004-02-08  1:04               ` Taj Khattra
2004-02-08  1:20             ` Jim Choate
2004-02-08  2:56               ` Bruce Ellis
2004-02-08  2:40           ` Bruce Ellis
2004-02-07  8:18   ` andrey mirtchovski
2004-02-07 11:12     ` Bruce Ellis
2004-02-07 11:33     ` a
2004-02-07 13:30     ` boyd, rounin
2004-02-07 13:38     ` boyd, rounin
2004-02-07 14:51     ` Jim Choate
1998-07-13 15:46 [9fans] CPU Server Franklin

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=A1AA9B77-932C-4C30-A9D4-1136151D62EE@utopian.net \
    --to=josh@utopian.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).