9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installed Plan 9, now what?
Date: Tue,  9 Dec 2003 06:23:25 -0500	[thread overview]
Message-ID: <b98781ee47ca5ee4a4bb694749148854@9srv.net> (raw)
In-Reply-To: <200312090454.hB94skl24638@augusta.math.psu.edu>

i'm with dan on this point, i think. my concerns here, however, come
from being a plan 9 administrator. we ran our own file server, and did
overlays on top of 1127's files when we wanted something changed, just
doing binds where we wanted them. it worked great, for the most part; a
real testament to the strength of the architecture. 

the problems came when 1127 changed things. well, of *course* they did;
it's a research system! our system of binds helped us manage local
changes in a way that was easy to manage and track, but it required
duplicating whole files (not to mention a /lib/namespace that was
several hundred lines long!). it was frustrating when, once or twice a
year, i'd have to track down some config file that'd changed and port
the new changes in 1127's version into our version, when all we
typically wanted was setting some variable differently than 1127 had.

if "local" files exist (whatever they're called), they should all ship
empty, or simply not exist. if something's not working right after
some upgrade, it's easy to figure out if it's local site mods that're
causing the error, and easy to tell where the changes - both from the
"vendor" and the local user - are.

i have to professionally (that is, i'm paid for it; saying nothing
about the manner in which i do it) manage a hadfull of unix boxes,
with some collection of GNU or other third-party software, and the
mess around config and site localization there is horrid. i'd very
much like to avoid duplicating that. but the current situation - which
is, as dan said, essentially ignoring the issue - is far from ideal,
too. things now are an order of magnitude easier to follow than in the
linux/GNU world, but could be better still.
ア


  parent reply	other threads:[~2003-12-09 11:23 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 12:48 David Presotto
2003-12-08 15:10 ` andrey mirtchovski
2003-12-08 16:21   ` David Presotto
2003-12-08 19:30   ` Dan Cross
2003-12-08 21:14     ` david presotto
2003-12-08 22:20       ` Dan Cross
2003-12-09  0:55         ` David Presotto
2003-12-09  1:20           ` Russ Cox
2003-12-09  1:29             ` Dan Cross
2003-12-09  1:36               ` Russ Cox
2003-12-09  3:00                 ` Dan Cross
2003-12-09  4:02                   ` Geoff Collyer
2003-12-09  3:44                     ` mirtchov
2003-12-09  4:10                     ` Scott Schwartz
2003-12-07  9:59                       ` Charles Forsyth
2003-12-07 10:28                         ` Charles Forsyth
2003-12-09  4:33                       ` Geoff Collyer
2003-12-09  4:54                     ` Dan Cross
2003-12-09  7:47                       ` okamoto
2003-12-09 11:23                       ` a [this message]
2003-12-09 12:12                         ` boyd, rounin
2003-12-09 18:33                       ` splite
2003-12-09 19:23                         ` Brantley Coile
  -- strict thread matches above, loose matches on Subject: below --
2003-12-09  7:55 YAMANASHI Takeshi
2003-12-09 13:49 ` David Presotto
2003-12-08 11:36 Tiit Lankots
2003-12-08 14:51 ` ron minnich
2003-12-08 15:00 ` Russ Cox
2003-12-08 10:08 Sujan Gautam
2003-12-08 13:53 ` mirtchov

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=b98781ee47ca5ee4a4bb694749148854@9srv.net \
    --to=a@9srv.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).