From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF
Date: Thu, 12 Apr 2007 12:03:18 -0400 [thread overview]
Message-ID: <9ab217670704120903i340bea51s7987f3afab10bc33@mail.gmail.com> (raw)
In-Reply-To: <cb1dd43730862547dcd09096b990434b@coraid.com>
2007/4/12, erik quanstrom <quanstro@coraid.com>:
> >
> > We need to have something automatically create /cfg for peoples
> > fossils when they upgrade then. You can't just mkdir /cfg.
> >
>
> how about (by $user in group sys)
>
> mount -c /srv/boot /n/fs
> mkdir /n/fs/cfg
>
> you can issue this at the fossil (or fileserver) console, too
> create cfg sys sys 755 d
>
> i think the man page for fossilcons is missing the [dla] final
> option to create in the summary at the top.
>
> - erik
My point was more, if this is something that's in the default
distribution, we are going to need to have a way to get it in there,
and you can't just do that with replica/pull. Maybe putting that in
the cpurc manpage would work. ``For CPU-specific startup, create
/cfg/$sysname/blah.'' If your point is that it doesn't need to be, or
shouldn't be automatically created, that's a different issue
altogether, and one that I can see as reasonable, since most people
probably don't use this convention right now.
However, /cfg/$sysname/* is referenced in other places as well, so
perhaps it's be a good idea to have a manpage with more global
information. (namespace, perhaps)
--dho
next prev parent reply other threads:[~2007-04-12 16:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
2007-04-12 15:14 ` Uriel
2007-04-12 15:32 ` Devon H. O'Dell
2007-04-12 15:48 ` erik quanstrom
2007-04-12 16:03 ` Devon H. O'Dell [this message]
2007-04-12 16:05 ` Russ Cox
2007-04-12 15:56 ` Uriel
2007-04-12 16:08 ` Devon H. O'Dell
2007-04-12 17:42 ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:00 ` Anthony Sorace
2007-04-12 18:16 ` Russ Cox
2007-04-12 18:57 ` Anthony Sorace
2007-04-13 4:04 ` Lucio De Re
2007-04-13 4:58 ` geoff
2007-04-12 18:25 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF ron minnich
2007-04-12 18:38 ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:43 ` Devon H. O'Dell
2007-04-12 18:40 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF erik quanstrom
2007-04-12 18:50 ` Francisco J Ballesteros
2007-04-12 18:41 ` Russ Cox
2007-04-13 4:18 ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13 4:59 ` geoff
2007-04-12 18:48 ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF andrey mirtchovski
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=9ab217670704120903i340bea51s7987f3afab10bc33@mail.gmail.com \
--to=devon.odell@gmail.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).