From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fmt and unicode text
Date: Sun, 16 Nov 2003 16:23:35 -0500 [thread overview]
Message-ID: <E1ALUMw-0006Va-Lw@t40.swtch.com> (raw)
In-Reply-To: Your message of "Sun, 16 Nov 2003 12:29:24 MST." <6a245736ff4fa6f1dcf7d9b2303482bd@plan9.ucalgary.ca>
> ps: the patch(1) system isn't operational still..
i don't know what to do about that.
i don't want to get rid of the write
group on sources. the write group lets me not
worry too much about getting the permissions right
since the fs is r/o for the vast majority of users.
i could change the logs to be 444 and override their
modes in the proto file, but there might still be
775 directories or just plain mistakes. the write
group makes those mistakes not costly.
since users and groups are per-fossil and not per-file system,
i'd have to set up another server (either on the same machine
running on an alternate port/ip, or on an alternate machine
entirely). but then i'd have to worry about adding new users
to both the sources /adm/users and the patches /adm/users.
the addition of new users is already clumsy enough without
worrying about doing it in two places.
so instead i'm doing nothing and waiting for a better idea
to come along. probably what will happen is enough time will
go by that i come to terms with the fact that:
- patches must be another, small, file server
- we need a programmatic way to issue
console commands and get responses
and i will implement that programmatic way, set up the
small file server on an alternate ip address running on
the same machine that now hosts sources, and we'll be
happy.
but all that is a lot more work than it was to write
the patch(1) system to start with, and i have not gotten
to it.
what little time i have to work on plan 9 i've been
spending trying to make venti faster and fossil better.
russ
next prev parent reply other threads:[~2003-11-16 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 19:29 mirtchov
2003-11-16 21:23 ` Russ Cox [this message]
2003-11-16 21:51 ` mirtchov
2003-11-16 22:22 ` Russ Cox
2003-11-16 23:22 ` Lyndon Nerenberg
2003-11-16 23:39 ` Russ Cox
2003-11-16 21:28 ` David Presotto
2003-11-16 21:34 ` David Presotto
2003-11-16 21:52 ` mirtchov
2003-11-16 21:51 ` 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=E1ALUMw-0006Va-Lw@t40.swtch.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).