From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9pcf + devfs
Date: Wed, 15 Oct 2003 09:43:50 +0200 [thread overview]
Message-ID: <9bb7494ef2d6e29b6fec9d422ee8f189@plan9.escet.urjc.es> (raw)
In-Reply-To: <a418ff0f128146031ddf3623a8a3e3a8@plan9.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
I think I included code in devfs to let it read the config
from somewhere in a disk, but just don't remember what
happen to that.
If there's no boot script it's likely you just can't config fs
prior to starting fossil.
[-- Attachment #2: Type: message/rfc822, Size: 2481 bytes --]
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9pcf + devfs
Date: Wed, 15 Oct 2003 01:23:03 -0600
Message-ID: <a418ff0f128146031ddf3623a8a3e3a8@plan9.ucalgary.ca>
> You'd need to edit the boot script (/sys/lib/sysconfig/fl/boot if I remember well)
> to setup your fs dev before starting fossil. Take a look at the bootdir section
> of the config file, where your boot script is mentioned.
that's the default for pcfl kernels, but not for pcf -- as far as I
could tell there's no script specified in the pcf configuration file.
I have pcfl running fine (thanx to your suggestions a few months ago
regarding devfs), and have booted 9pcf in a single-disk environment.
My question was prompted by my inability to find any configuration
file or a script in which to specify that a particular 9pcf kernel
should boot using devfs (#k).
andrey
ps: by the way, /sys/lib/sysconfig/fl/ has been empty for some time
now, the files it contained disappeared on the 18th of September,
according to my venti...
next prev parent reply other threads:[~2003-10-15 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 16:43 mirtchov
2003-10-15 7:14 ` Fco.J.Ballesteros
2003-10-15 7:23 ` mirtchov
2003-10-15 7:43 ` Fco.J.Ballesteros [this message]
2003-10-15 14:18 ` 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=9bb7494ef2d6e29b6fec9d422ee8f189@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).