From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] fmt and unicode text In-Reply-To: Your message of "Sun, 16 Nov 2003 12:29:24 MST." <6a245736ff4fa6f1dcf7d9b2303482bd@plan9.ucalgary.ca> From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25020.1069017815.1@t40.swtch.com> Message-Id: Date: Sun, 16 Nov 2003 16:23:35 -0500 Topicbox-Message-UUID: 8b484c38-eacc-11e9-9e20-41e7f4b1d025 > 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