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:14:17 +0200 [thread overview]
Message-ID: <1fc101b28f88ae9c8ae5f3d6d39ffd63@plan9.escet.urjc.es> (raw)
In-Reply-To: <2ef416da7a38fe8f42e837d136339654@plan9.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 765 bytes --]
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. We use something like this:
#!/boot/rc -m /boot/rcmain
cpuserver=yes
...
echo mirror once /dev/sdC0/once /dev/sdD0/once >/dev/fs/ctl
echo mirror fossil /dev/sdC0/fossil /dev/sdD0/fossil >/dev/fs/ctl
echo mirror other /dev/sdC0/other /dev/sdD0/other >/dev/fs/ctl
echo mirror other1 /dev/sdD0/other1 /dev/sdC0/other1 >/dev/fs/ctl
...
venti -w -c /env/venticonf -a tcp!127.1!17034 &
sleep 10
venti=tcp!127.1!17034
fossil -c '. /env/fossilconf'
Where both fossilconf and venticonf refer to /dev/fs/{once,fossil,other,other1}.
[-- Attachment #2: Type: message/rfc822, Size: 1772 bytes --]
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: [9fans] 9pcf + devfs
Date: Tue, 14 Oct 2003 10:43:48 -0600
Message-ID: <2ef416da7a38fe8f42e837d136339654@plan9.ucalgary.ca>
Is the pcf kernel at all compatible with booting from /dev/fs? I
can't find any script associated with it that I can edit and put my
devfs configuration in...
Any pointers? Or should I just stick with the 'pcfl' kernels?
next prev parent reply other threads:[~2003-10-15 7:14 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 [this message]
2003-10-15 7:23 ` mirtchov
2003-10-15 7:43 ` Fco.J.Ballesteros
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=1fc101b28f88ae9c8ae5f3d6d39ffd63@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).