From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] changing file ownership with fossil?
Date: Tue, 14 Oct 2003 23:09:59 -0400 [thread overview]
Message-ID: <E1A9c2z-000Ihh-W5@t40.swtch.com> (raw)
In-Reply-To: Your message of "Tue, 14 Oct 2003 22:36:15 EDT." <20031015023615.GA12630@nerds.cs.umd.edu>
> 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
next prev parent reply other threads:[~2003-10-15 3:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 0:19 Tim Fraser
2003-10-14 2:24 ` jmk
2003-10-15 2:36 ` Tim Fraser
2003-10-15 3:09 ` Russ Cox [this message]
2003-10-15 5:43 ` Charles Forsyth
2003-10-15 14:25 ` Russ Cox
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=E1A9c2z-000Ihh-W5@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).