Maxim Sobolev writes:
> "Michael C . Wu" wrote:
> > On Fri, Oct 13, 2000 at 07:22:20AM -0500, Mike Meyer scribbled:
> > | Just curious - now that the kernel has moved into /boot/kernel/kernel,
> > | does anyone know how well would it work to put /boot in it's own
> > | partition (possibly in it's own slice)?
> > I do not think loader can see stuff in other partitions.
> Nope, the loader can load stuff from other partitions, even from some strange
> ones like msdos ;), so theoretically it should be possible to have /boot, or
> even /boot/kernel, on another partition (it may require to tweak loader config
> files, though), but I really do not see any reasons behind such weird setup.
Since you implied a question...
This is a standard setup for Linux, so Linux people dealing with
problems with the root file system try and make it work in -stable
(with no luck). The best example would be to make /boot one file
system so you can get vinum loaded and running, then have everything
else on a vinum disk. This minimizes the set of things you don't have
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message