9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs administration: how do people update multi-user fs?
Date: Fri, 14 Feb 2003 09:16:50 -0800	[thread overview]
Message-ID: <3E4D2482.3020204@nas.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302140818210.1630-100000@carotid.ccs.lanl.gov>

Ronald G. Minnich wrote:
> A few things I've noticed in recent years, esp. on Linux
> - you need to be root more than you used to
> - more priveleged ports, not less

I know this is off-topic for this list, but would you be willing to
elaborate a bit?

I agree with you in the other areas, but it seems that we're trading
services, not necessarily adding services.  SSH for telnet and ftp, so
yes, maybe setuid-root, but we add a privileged port and drop two.  We
might add Samba or netatalk to a system that already has NFS shares, but
the reasons they're privileged ports seem to be outside the hands of the
Linux community, and most of the added privileged ports seem to be
running as unique users now, instead of all running as root.

It also seems like increased usage of chrooted/jailed services has made
things slightly better, even though it's still privileged, and yes,
still a mess.

Are there better ways?  Sure, but you're not likely to see them widely
implemented anytime soon.  As long as Linux continues to accrete
functionality to accomodate Someone Else's OS the prevalent services
will always be less than desired, but I don't see it as any worse than
it was five years ago, just more of the same.

I'm always suprised that there isn't more prevalent bootstrapping going
on in the client world for halfway decent services.  I wouldn't mind
seeing an SFS client for Windows, or heck, even Java.  Though I think
OSX will let you have WebDAV home directories now, there should be some
facility for arbitrary-service-home-directory for PAM.

(Is the 9P on Python project still in existence?)

-Jack




  reply	other threads:[~2003-02-14 17:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14 15:02 Axel Belinfante
2003-02-14 15:16 ` Russ Cox
2003-02-14 15:20   ` Ronald G. Minnich
2003-02-14 17:16     ` Jack Johnson [this message]
2003-02-14 17:28       ` andrey mirtchovski
2003-02-14 17:42         ` Ronald G. Minnich
2003-02-14 18:04           ` northern snowfall
2003-02-16 22:28         ` Roman V. Shaposhnick
2003-02-14 17:47       ` Ronald G. Minnich
2003-02-14 15:33   ` Lucio De Re
2003-02-14 15:37     ` Russ Cox
2003-02-14 16:08     ` [9fans] chown in fossil Fco.J.Ballesteros
2003-02-14 16:17       ` Russ Cox
2003-02-14 16:20         ` Fco.J.Ballesteros
2003-02-14 16:23           ` Russ Cox
2003-02-14 16:27             ` Fco.J.Ballesteros
2003-02-15  2:56     ` [9fans] fs administration: how do people update multi-user fs? Christopher Nielsen
2003-02-15  3:03       ` Geoff Collyer
2003-02-15  4:38         ` Christopher Nielsen
2003-02-15  3:13       ` Scott Schwartz
2003-02-15  4:39         ` Christopher Nielsen
2003-02-15  4:48         ` Andrew
2003-02-15 16:20           ` Dan Cross
2003-02-15  9:49       ` Lucio De Re
2003-02-15 14:18         ` Russ Cox
2003-02-15 15:29           ` Lucio De Re
2003-02-16 14:20             ` Russ Cox
2003-02-16 14:30               ` Lucio De Re
2003-02-16 14:36                 ` Russ Cox
2003-02-15 15:53       ` Kenji Arisawa
2003-02-15 16:00         ` Lucio De Re
2003-02-15 16:22           ` Dan Cross
2003-02-15 17:58           ` Russ Cox
2003-02-14 16:16   ` Dan Cross

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=3E4D2482.3020204@nas.com \
    --to=fragment@nas.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).