Re: /boot partition?
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. I could have a 40G /, and not worry about the cylinder spanning problem, if my /boot were in a seperate (low) partition. I could have a / that was of an FS type not understood by the kernel, until after a module defining the FS type had been loaded. I could have a / that was on a controller for which I did not have a device comiled into my kernel, and only loaded it as a module from an FS type that it _did_ understand. Terry Lambert [EMAIL PROTECTED] --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
On Tue, 17 Oct 2000, Terry Lambert wrote: I could have a 40G /, and not worry about the cylinder spanning problem, if my /boot were in a seperate (low) partition. I could have a / that was of an FS type not understood by the kernel, until after a module defining the FS type had been loaded. I could have a / that was on a controller for which I did not have a device comiled into my kernel, and only loaded it as a module from an FS type that it _did_ understand. Terry Lambert [EMAIL PROTECTED] Garth, I think that was a haiku. -- Brandon D. Valentine [EMAIL PROTECTED] "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
On Fri, Oct 13, 2000 at 07:18:05PM +0300, Maxim Sobolev wrote: 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. Our IA-64 offering may end up having /boot as a native partition (ie, vfat32) as their firmware understands it. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
David O'Brien writes: On Fri, Oct 13, 2000 at 07:18:05PM +0300, Maxim Sobolev wrote: 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. Our IA-64 offering may end up having /boot as a native partition (ie, vfat32) as their firmware understands it. Solaris 8 uses this setup. One partition of about 10meg for booting, mount as /boot after the system comes up. BTW, kudos to the FreeBSD install team. Much as the FreeBSD install may be maligned, it's much more intuitive, flexible and in general better than what Sun is doing with for Solaris 8. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
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 on vinum. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
On Fri, Oct 13, 2000 at 12:39 -0500, Mike Meyer wrote: [ ... separate /boot partition ... ] 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 on vinum. Since you bring the Linux analogy in ... There's a mechanism used by some Linux distros (strictly speaking: available to all Linux users, but rarely used by default) to have a ramdisk with the kernel and essential drivers. This ramdisk can be handled by many boot managers and the effect is that - you don't need all the drivers you need for booting in the kernel itself -- they can be modules, too - you can have all your fses in software raid configuration and yet survive the boot stage, since the boot kernel won't have a need to touch and handle the raid configuration But I feel that a separate /boot partition will never work when you can't reach the / fs -- where are you going to mount the /boot fs? The idea is always that you have to bring in everything you need to get over the initial steps. Without vinum drivers and setup tools you cannot access vinum volumes. And when the tools live on a vinum volume themselves, you're trapped. That's when you need a separate "selfcontained" mechanism -- like a mfs or ramdisk thing. BTW: One of the most commonly seen failures is to compile a new kernel and not updating the ramdisk needed for booting ... virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
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. The loader also resides in /boot. Besides, if you can't mount / (including /etc), there really is no point to keep /boot somewhere else. -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
"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. The loader also resides in /boot. Besides, if you can't mount / (including /etc), there really is no point to keep /boot somewhere else. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /boot partition?
"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. Is it possible to boot from very large disks? If not, then somebody might want to have a small /boot and the entire rest of the disk as / Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
