From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <73ba4d335ae0f6d0eee24fefa24843bf@ladd.quanstro.net> References: <73ba4d335ae0f6d0eee24fefa24843bf@ladd.quanstro.net> Date: Mon, 7 Dec 2009 17:48:47 +0100 Message-ID: <8ccc8ba40912070848p302f23b9u575478c818b8556a@mail.gmail.com> From: Francisco J Ballesteros To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] ideas for helpful system io functions Topicbox-Message-UUID: abd05154-ead5-11e9-9d60-3106f5b1d025 the idea is that if fs knows enough to handle partitions like we are accustomed to, then partitioning code can be removed from everywhere else (but for compat) and existing tools used to handle partitions (e.g., fdisk) very much like they are used now. Either way, It's not standalone, in one case you require loop, in the other= fs. both can load their configs and both require help to learn which partitions to use at boot time. On Mon, Dec 7, 2009 at 5:24 PM, erik quanstrom wrot= e: > On Mon Dec =C2=A07 11:16:04 EST 2009, nemo@lsub.org wrote: >> It seems that changing a bit fs(3) can suffice and is generic >> enough for all usages required. In the end it might result in code >> removed instead of adding code, but time will tell. As of today, it's >> only an experiment. > > not everyone who uses usb disks also uses fs. > i also like the idea of a stand-alone device. > i can also put the entire configuration of a > loop device in plan9.ini. > > - erik > >