From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <9ab217670704120903i340bea51s7987f3afab10bc33@mail.gmail.com> Date: Thu, 12 Apr 2007 12:03:18 -0400 From: "Devon H. O'Dell" 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 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9ab217670704120832k37d6e734u7d2b7edd9a6e4be0@mail.gmail.com> Topicbox-Message-UUID: 456c501e-ead2-11e9-9d60-3106f5b1d025 2007/4/12, erik quanstrom : > > > > 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