From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: <38CEF120-B324-41A1-8EB1-781E01CFC57A@gmail.com> Content-Transfer-Encoding: quoted-printable From: Anthony Sorace Date: Thu, 15 Nov 2007 19:38:40 -0500 To: 9fans@cse.psu.edu Subject: [9fans] Venti config for booting from fs(3) Topicbox-Message-UUID: fc1e54ba-ead2-11e9-9d60-3106f5b1d025 I'd like to set up my spiffy new cpu server to boot from a venti =20 using at least mirrored arenas via fs(3). A few questions on this: =95 I'm mirroring the arenas to insure against drive failure. = Does it =20 make sense to also interleave the indexes? Both of them? =95 I've got three disks. The venti arenas will be on two. Will = the =20 indexes benefit significantly from either being interleaved across =20 three, or only on the third (with the fossil)? I understand that this =20= is somewhat usage-dependent; I guess the real question is how =20 sensitive are the indexes to write times? =95 The venti would be used for the fossil boot partition, so = needs to =20 be there at startup. fs(3) suggests sticking the config on a floppy =20 (!). This seems like not the most reliable option. Where are others =20 sticking their fs(3) configs for boot? =95 Once there's an fsconfig var, how does the rest of the = startup go? =20 I don't see it pulling that in anywhere. This needs to be well before =20= cpurc, right? Will this require a custom boot? Anthony