From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: quoted-printable Message-Id: <0C23F343-DE66-4749-B798-4AD966035999@utopian.net> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed To: 9fans@cse.psu.edu From: Joshua Wood Subject: RE: [9fans] Venti config for booting from fs(3) Date: Thu, 15 Nov 2007 17:10:46 -0800 Topicbox-Message-UUID: fc2786f2-ead2-11e9-9d60-3106f5b1d025 > =95 The venti would be used for the fossil boot partition, so needs = to > be there at startup. fs(3) suggests sticking the config on a floppy > (!). This seems like not the most reliable option. Where are others > sticking their fs(3) configs for boot? The wiki page for mirroring under venti and fossil: http://plan9.bell-labs.com/wiki/plan9/=20 Mirroring_with_Fossil_and_Venti/index.html Suggests storing the fs config in an 'fscfg' parition on the local =20 (hard) disk, similar to the conf headers for venti or fossil themselves. > =95 Once there's an fsconfig var, how does the rest of the =20 > startup go? > I don't see it pulling that in anywhere. This needs to be well before > cpurc, right? Will this require a custom boot? And then one can set 'fsonfig=3D' in plan9.ini to the partition created =20= above to start devfs with it at boot. The rest of your questions I'm experimenting with myself & am very =20 interested in the experience of others and yours; I do know Russ Cox =20 has some informative comments about venti and fossil caching (in =20 memory) at the end of the venti-rescue paper. The big hint for a =20 single-machine fossil+venti, I thought, is that fossil caches venti =20 blocks, too. -- Josh=