Date: Tue, 22 Aug 1995 08:35:36 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: bde@zeta.org.au (Bruce Evans) Cc: bde@zeta.org.au, msmith@atrad.adelaide.edu.au, hackers@freebsd.org Subject: Re: Using space in a DOS filesystem Message-ID: <199508221535.IAA27053@ref.tfs.com> In-Reply-To: <199508221526.BAA13856@godzilla.zeta.org.au> from "Bruce Evans" at Aug 23, 95 01:26:05 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> >But if the slab _is_ the boot device, how do we read the tools from it? > >> > >> With difficulty. Don't boot from it. > > >That more or less rules that approach out completely. We're trying to > >do an ersatz partition that can do everything a "real" partition does. > >That's going to have to include booting. > > The standard boot loader isn't going to work on it unless it is partition > (within another partition :-(). for a demo that doesn't matter because you would be booting from DOS anyhow.... just have a kernel that uses the dosfs code to find it's partition, instead of using the disklable code to do the same thing. > > >> It would be relatively easy to check the partition once you have located > >> it. You might be able to boot from the DOS file system, run some > > >I can understand that. How would you feel about being able to recognise > >one of these ersatz partitions if the info were passed in to the kernel > >at bootstrap time? > > The mount of root would probably fail if the partition was invalid. I > guess you could put the partition boundaries in the data for the program > replaces the standard boot loader. How are you going to select where > to boot from? Standard boot managers should be able to handle the > partition within a partition method (:-(). > > Bruce >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508221535.IAA27053>