From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] changing file ownership with fossil? In-Reply-To: Your message of "Tue, 14 Oct 2003 22:36:15 EDT." <20031015023615.GA12630@nerds.cs.umd.edu> From: "Russ Cox" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <71899.1066187399.1@t40.swtch.com> Message-Id: Date: Tue, 14 Oct 2003 23:09:59 -0400 Topicbox-Message-UUID: 6ed157de-eacc-11e9-9e20-41e7f4b1d025 > Thank you for your rapid response. I re-ran replica/pull around > 22:00EST on 14 October 2003 and was happy to see the new fossil binary > and sources download. Unfortunately, I was once again unable to use > the -W flag. A transcript: Did you recompile the kernel? Fossil is compiled into the kernel and started at boot time, so you'd have to rebuild the kernel to get it going. cd /sys/src/9/pc mk 'CONF=pcf' 9pcf 9fat: cp 9pcf /n/9fat/9pcf2 acme -c1 /n/9fat/plan9.ini and find the line bootfile=sdC0!9fat!9pcf and add bootfile=sdC0!9fat!9pcf2 then when you boot you'll be asked which kernel you want. > I have also experienced another problem that may be related: While > using the 29 September and 12 October versions of fossil in -AP mode, > in addition to warnings about failures to set uids, I also witnessed > warnings like this one: > > warning: cannot set mtime on /mnt/admin/sys/src/cmd/fossil/9srv.c That's weird. Are you sure it was in -AP mode? Can you use touch successfully on those files? > (This problem seems to be confined to source files, not binaries.) > > At the time, I wasn't too concerned. But, when I did my latest > replica/pull to acquire your changes to fossil, I found replica > refusing to update some files: > > sys/src/cmd/fossil/9user.c: locally modified; will not update > > I have not modified these files. Is this refusal the result of > replica/pull's earlier failure to set the mtimes on these files? Yes. Russ