From: Tim Fraser <tfraser@cs.umd.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] changing file ownership with fossil?
Date: Tue, 14 Oct 2003 22:36:15 -0400 [thread overview]
Message-ID: <20031015023615.GA12630@nerds.cs.umd.edu> (raw)
In-Reply-To: <088fc247f7aef86fe0e0e5fe1b5c5f06@plan9.bell-labs.com>
jmk> An oversight. I've tried to fix it (untested) and correct the man
jmk> page. New source and man page on sources.
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:
term% con /srv/fscons
prompt: fsys main
main: srv -APW admin
usage: srv [-Adp] [service]
main: srv -AP admin
main: >>> q
term% mount /srv/admin /mnt/admin
term% lc -l /mnt/admin/386/bin/fossil/fossil
--rwxrwxr-x M 36 glenda sys 345764 Oct 13 22:22 fossil
term% chgrp -o sys /mnt/admin/386/bin/fossil/fossil
chgrp: can't wstat /mnt/admin/386/bin/fossil/fossil: wstat -- not owner
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
(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?
Once again, thank you for your assistance!
Tim Fraser / U. Maryland Institute for Advanced Computer Studies
next prev parent reply other threads:[~2003-10-15 2:36 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 [this message]
2003-10-15 3:09 ` Russ Cox
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=20031015023615.GA12630@nerds.cs.umd.edu \
--to=tfraser@cs.umd.edu \
--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).