From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A short PPPOE configuration guide
Date: Mon, 29 Aug 2005 18:02:55 -0400 [thread overview]
Message-ID: <16673.1125352975@piper.nectar.cs.cmu.edu> (raw)
In-Reply-To: <ee9e417a05082904547e7709e5@mail.gmail.com>
>> Disable permissions checking:
> Put yourself in group sys instead. This "invent
> root by another name" meme has lasted long enough.
I started to respond to this but halfway through
realized where this meme was coming from, at least
in my mind.
I was feeling nervous about running in group sys
because, well, I could accidentally destroy the
whole file system, right? Oh.... the worst I
could do would be to destroy *today's* *version*
of the file system, and yesterday's is still there,
and the day before's, and ...
Dave Eckhardt
next prev parent reply other threads:[~2005-08-29 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 7:49 Vester Thacker
2005-08-29 11:24 ` [9fans] " Vester Thacker
2005-08-29 11:54 ` [9fans] " Russ Cox
2005-08-29 13:25 ` Vester Thacker
2005-08-29 13:26 ` Enache Adrian
2005-08-29 13:28 ` Russ Cox
2005-08-29 22:02 ` Dave Eckhardt [this message]
2005-08-30 1:39 ` kokamoto
2005-08-30 1:56 ` kokamoto
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=16673.1125352975@piper.nectar.cs.cmu.edu \
--to=davide+p9@cs.cmu.edu \
--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).