From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how is it done on sources?
Date: Fri, 4 Jul 2003 00:38:12 -0400 [thread overview]
Message-ID: <f13c0715d730f2d7f20b3241a32bed98@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307030853030.18814-100000@fbsd.cpsc.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
they're not all sys/sys on sources.
do an ls -l and you'll see. they're sys/sys
in the replica logs, which is what gets used
to update your own machines.
run replica/pull as a special user that is a
member of group sys and drop the -u flag.
that's the easiest way to update a fossil
system.
the second easiest is to allocate an allowed
console using srv -A.
[-- Attachment #2: Type: message/rfc822, Size: 3038 bytes --]
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] how is it done on sources?
Date: Thu, 3 Jul 2003 08:56:29 -0600 (MDT)
Message-ID: <Pine.LNX.4.44.0307030853030.18814-100000@fbsd.cpsc.ucalgary.ca>
how do you manage to change all file owners to sys/sys on sources without
running fossil in 'allow' mode?
also, what is the difference between 755 and 644, as illustrated in this
replica/pull snippet (why does 644 work, while 755 doesn't):
a 386/bin/xmr 775 sys sys 1039758616
warning: cannot set uid on /n/boot/386/bin/xmr
a 386/bin/xms 775 sys sys 1039758617
warning: cannot set uid on /n/boot/386/bin/xms
a 386/bin/yacc 775 sys sys 1045538096
warning: cannot set uid on /n/boot/386/bin/yacc
a 386/bin/zip 775 sys sys 1045538096
warning: cannot set uid on /n/boot/386/bin/zip
a 386/include/ape/float.h 664 sys sys 969656988
a 386/include/ape/math.h 664 sys sys 1046282351
a 386/include/ape/stdarg.h 664 sys sys 944946040
a 386/include/ape/ureg.h 664 sys sys 944946041
a 386/include/u.h 664 sys sys 1042604326
a 386/include/ureg.h 664 sys sys 944946012
thanx, andrey
prev parent reply other threads:[~2003-07-04 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 14:56 andrey mirtchovski
2003-07-03 15:09 ` Fco.J.Ballesteros, nemo
2003-07-03 15:24 ` andrey mirtchovski
2003-07-04 2:07 ` boyd, rounin
2003-07-04 2:44 ` andrey mirtchovski
2003-07-04 3:01 ` Scott Schwartz
2003-07-04 4:38 ` Russ Cox [this message]
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=f13c0715d730f2d7f20b3241a32bed98@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).