From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil shutdown
Date: Fri, 7 Oct 2005 12:02:48 -0400 [thread overview]
Message-ID: <ee9e417a0510070902h7527e226pdd011c3e5bee5108@mail.gmail.com> (raw)
In-Reply-To: <16703.1128700175@piper.nectar.cs.cmu.edu>
> A couple times I have wondered if it would make sense to
> chmod the .../data files once services are running...
> or maybe they should start off non-writable and startups
> should embody a pattern like this?
>
> chmod 664 /dev/sdC0/fossil
> fossil -f /dev/sdC0/fossil
> chmod 444 /dev/sdC0/fossil
On non-terminals, the problem goes away because only
hostowner has read/write access to them. Making the disks
read-only by default would just frustrate people who actually
have legitimate use for the disks! All the programs that
access disks (think dossrv, 9660srv, fdisk, prep, etc.) would
then try to chmod +w, making the permissions somewhat
useless if you're running as hostowner.
Of course, one could put a chmod -w /dev/sd*/data in termrc
if one is worried about making mistakes.
Russ
next prev parent reply other threads:[~2005-10-07 16:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 8:01 fgergo
2005-09-22 14:15 ` David Leimbach
2005-09-22 14:19 ` Charles Forsyth
2005-09-22 14:53 ` David Leimbach
2005-10-07 3:51 ` Thomas Miller
2005-10-07 4:11 ` Russ Cox
2005-10-07 10:21 ` Charles Forsyth
2005-10-07 15:49 ` Dave Eckhardt
2005-10-07 16:02 ` Russ Cox [this message]
2005-09-22 14:19 ` Russ Cox
2005-09-22 14:23 ` David Leimbach
2005-09-22 14:38 ` David Leimbach
2005-09-22 16:11 ` Dave Eckhardt
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=ee9e417a0510070902h7527e226pdd011c3e5bee5108@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).