Re: BE Loader Menu (was Re: rcs)
On Oct 21, 2013, at 6:32 AM, Kris Moore wrote: > On 10/20/2013 20:58, Julian Elischer wrote: >> Kris. exactly what features need to be added to the boot process to >> allow >> what you want to do, but without using grub? >> > > Here's a list of the features we are using from grub: > > For install medium: > > * Hybrid DVD ISO/USB image in same file I've been using ISOLINUX for that functionality since 2006. My DRUID installer is shipped as a hybrid ISO using ISOLINUX. > * BIOS / UEFI loaders on same image Haven't played with UEFI yet. > * Graphics support ISOLINUX has that. Can we compare screens? I really like the way ISOLINUX's vesamenu.c32 module allows you to even go so far as to customize the scrollbar coloring (e.g., in the below image, notice how I've given the scrollbar a blue color so it completes the theme). http://twitpic.com/17z5yi Compare that to the same menu, but previously themed in blue: http://twitpic.com/17xas6 I wonder if grub lets you do that (scrollbar color, hilite color, and color of header/footer text as well). > For installed system: > > * Script-able ZFS BE menus This can be achieved in loader(8) with some basic work, building upon what we already have. Around this time last year, I actually added code to allow scripting of the loader(8) menu, but said functionality is still unused (waiting for some userland tool or some C code integrated directly into loader(8) to actually start scripting the menu-system. Until that happens... it's just my little secret that the Forth menus are actually scriptable from a higher language. (been trying for years it seems to find someone whom cares to sit down and show them how it works -- maybe at vBSDcon). > * Options for setting default timeouts / default BEs to load, etc I don't see why this too couldn't be done with loader(8). We already have a timeout system for booting with defaults... and I gather that whatever scripting there is to change the loaded defaults would take place prior to reboot (some tool munges loader.conf and then reboots; current defaults are displayed and after the configured timeout, it boots with the displayed configuration). > * Script-able menu to boot other OS's, such as Windows / Linux Well, I use SYSLINUX for that. SYSLINUX is the same product as the aforementioned ISOLINUX, except that it's focused on system versus install media. Of course... in your case, grub loads FreeBSD directly. When I use syslinux as a bootloader, I get the FreeBSD Forth beastie menu after selecting FreeBSD from the syslinux vesamenu. > * Loads before kernel Yeah, I got patches for our menu to follow suit. http://druidbsd.cvs.sf.net/viewvc/druidbsd/forth_zfs/ (thinking abut committing it already) > * Graphics support (I.E. countdown indicator, wallpapers, arrow-key > support, etc) > Well, I don't think the countdown indicator is going to get anyone all too excited (I believe we've had that for years). The wallpapers of course... can't do those as a default, but I think there's a graphical loader project -- but of course that won't service serial boot. I've thought about using arrow keys to navigate before... It involves implementing a whole new layer on top of the menu. One that would use some static character (e.g., ">") to show you which item you are "over" (or in the case of color... we could *maybe* use ANSI reverse). Definitely not easy. New state machine would be required. New rendering code would be required as well. The good news though is that it would get rid of the number prefixes). > If the native loader is able to handle the ZFS BE stuff, then I don't > see a reason why I can't make it an option in the installer, even > without graphics and the other niceties that grub brings. Is this > working in the stable/10 branch now? > No... just the patchset I pointed to... http://druidbsd.cvs.sf.net/viewvc/druidbsd/forth_zfs/ Which produces the following: http://twitpic.com/dhv2b6 Which achieves: a. Don't load kernel before menu b. Scripting of selections can be done via $kernels in loader.conf What we are lacking at the moment is... Root Device selection menu. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
On 10/20/2013 20:58, Julian Elischer wrote: > Kris. exactly what features need to be added to the boot process to > allow > what you want to do, but without using grub? > Here's a list of the features we are using from grub: For install medium: * Hybrid DVD ISO/USB image in same file * BIOS / UEFI loaders on same image * Graphics support For installed system: * Script-able ZFS BE menus * Options for setting default timeouts / default BEs to load, etc * Script-able menu to boot other OS's, such as Windows / Linux * Loads before kernel * Graphics support (I.E. countdown indicator, wallpapers, arrow-key support, etc) If the native loader is able to handle the ZFS BE stuff, then I don't see a reason why I can't make it an option in the installer, even without graphics and the other niceties that grub brings. Is this working in the stable/10 branch now? -- Kris Moore PC-BSD Software iXsystems ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
Kris. exactly what features need to be added to the boot process to allow what you want to do, but without using grub? On 10/19/13 3:39 AM, Teske, Devin wrote: On Oct 10, 2013, at 9:42 AM, Julian Elischer wrote: On 10/11/13 12:39 AM, Teske, Devin wrote: On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic BE menus for selecting the root device. yeah it always pisses me of when the menu comes up after the kernel is loaded because 99% of the time, I'm in the menu because I want to boot a DIFFERENT kernel.. Same thought I had about 7 years ago. After hearing that others (especially you, Julian) think the same thoughts... I'm happily ready to merge a patch from VICOR to achieve this. PLEASE!.. put it up for review somewhere... Done... http://druidbsd.cvs.sf.net/viewvc/druidbsd/forth_zfs/ All new code. Had to make it programmable: http://twitpic.com/dhv2b6 See that the patch adds documentation for loader.conf(5). It also clarifies a horrible description of "start" versus "initialize" in loader.4th(8). I wonder if we can we get a reviewboard instance for the project some time? Do let me know what you think. I went all-out on this one. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
On Oct 10, 2013, at 9:42 AM, Julian Elischer wrote: > On 10/11/13 12:39 AM, Teske, Devin wrote: >> On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: >> >>> On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic BE menus for selecting the root device. >>> yeah it always pisses me of when the menu comes up after the kernel is >>> loaded because 99% of the time, I'm in the menu because I want to boot a >>> DIFFERENT kernel.. >>> >> Same thought I had about 7 years ago. After hearing that others >> (especially you, Julian) think the same thoughts... >> >> I'm happily ready to merge a patch from VICOR to achieve this. > PLEASE!.. put it up for review somewhere... > Done... http://druidbsd.cvs.sf.net/viewvc/druidbsd/forth_zfs/ All new code. Had to make it programmable: http://twitpic.com/dhv2b6 See that the patch adds documentation for loader.conf(5). It also clarifies a horrible description of "start" versus "initialize" in loader.4th(8). > I wonder if we can we get a reviewboard instance for the project some time? > Do let me know what you think. I went all-out on this one. -- Devin P.S. I probably hadn't have put so much thought into this one if it hadn't been specifically you asking ;D but I think you know that. _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
from Juergen Lock: > If you mean it loads the kernel but then crashes instead of booting it > then your grub2 version is missing this fix: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002 > >I used Super Grub2 Disk image on the System Rescue CD written to USB stick. > A super grub disk beta version with the mentioned fix is here: > https://forja.cenatic.es/frs/?group_id=204 > (2.00s1b6, it also has fixed autodetection of FreeBSD installs.) I did the download, now will copy it to the System Rescue CD USB stick and make the appropriate entry in syslinux.cfg . I don't think the Super Grub2 Disk was able to load the kernel. It led to a prompt like what I get when I escape from the boot menu to loader prompt. My image resulting from mkrescue in sysutils/grub2 built from FreeBSD ports worked on FreeBSD 10-head, now 10-stable. But I got the same failure on FreeBSD 9.2. I copied /boot/kernel/kernel from the hard-drive installation to /boot/kernel/kernel92 on the USB-stick installation. Then I was able to boot the USB stick, escape to loader prompt, then unload boot /boot/kernel/kernel92 -a -s (or without -s for regular boot, but I was upgrading from 9.2-prerelease). Now uname -a shows FreeBSD amelia2 9.2-STABLE FreeBSD 9.2-STABLE #19 r256095M: Tue Oct 8 08:57:11 UTC 2013 root@amelia2:/usr/obj/usr/src/sys/SANDY amd64 Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
In article <59.81.16944.C6136525@cdptpa-oedge02> you write: >Sorry for previous typo in From: line, missing right angle bracket at end. >Then, in a finger error, I resent that message just before finding the error >and making the needed correction. > >from Devin Teske: > >> I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > >> Both problems can be solved. >> The loading of the kernel *after* choosing your boot device is trivial. >> We've been doing it at $work for *years* (almost a decade?) > >> I can put that in, whenever. Probably at the same time as implementing >> the live/dynamic BE menus for selecting the root device. > >I'd like to know how to boot FreeBSD >= 9.1 with grub2. > >Following the instructions under $PORTSDIR/sysutils/grub2 > >insmod ufs2 >set root=(hd0,gpt3) >kfreebsd /boot/loader >boot > >stopped working around FreeBSD 9.1-stable. > If you mean it loads the kernel but then crashes instead of booting it then your grub2 version is missing this fix: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699002 >I used Super Grub2 Disk image on the System Rescue CD written to USB stick. > A super grub disk beta version with the mentioned fix is here: https://forja.cenatic.es/frs/?group_id=204 (2.00s1b6, it also has fixed autodetection of FreeBSD installs.) >Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System >Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't >tested that yet. > >What is the method you or PC-BSD uses? > PC-BSD uses (more or less?) the sysutils/grub2 port that has the above fix. (as well as zfs patches etc.) >I want to use it on FreeBSD 9.2 and 10-current. > >I tried visiting pcbsd.org website but couldn't find any details. > >Tom > HTH, :) Juergen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
On 10/11/13 12:39 AM, Teske, Devin wrote: On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic BE menus for selecting the root device. yeah it always pisses me of when the menu comes up after the kernel is loaded because 99% of the time, I'm in the menu because I want to boot a DIFFERENT kernel.. Same thought I had about 7 years ago. After hearing that others (especially you, Julian) think the same thoughts... I'm happily ready to merge a patch from VICOR to achieve this. PLEASE!.. put it up for review somewhere... I wonder if we can we get a reviewboard instance for the project some time? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
On Oct 10, 2013, at 9:06 AM, Julian Elischer wrote: > On 10/10/13 1:05 AM, Teske, Devin wrote: >> >> I'm late to the party again ;D (didn't realize the rcs thread had turned BE) >> >> Both problems can be solved. >> The loading of the kernel *after* choosing your boot device is trivial. >> We've been doing it at $work for *years* (almost a decade?) >> >> I can put that in, whenever. Probably at the same time as implementing >> the live/dynamic BE menus for selecting the root device. > > yeah it always pisses me of when the menu comes up after the kernel is loaded > because 99% of the time, I'm in the menu because I want to boot a DIFFERENT > kernel.. > Same thought I had about 7 years ago. After hearing that others (especially you, Julian) think the same thoughts... I'm happily ready to merge a patch from VICOR to achieve this. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
On 10/10/13 1:05 AM, Teske, Devin wrote: I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic BE menus for selecting the root device. yeah it always pisses me of when the menu comes up after the kernel is loaded because 99% of the time, I'm in the menu because I want to boot a DIFFERENT kernel.. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
On 10/10/2013 00:47, Thomas Mueller wrote:
> Sorry for previous typo in From: line, missing right angle bracket at end.
> Then, in a finger error, I resent that message just before finding the error
> and making the needed correction.
>
> from Devin Teske:
>
>> I'm late to the party again ;D (didn't realize the rcs thread had turned BE)
>> Both problems can be solved.
>> The loading of the kernel *after* choosing your boot device is trivial.
>> We've been doing it at $work for *years* (almost a decade?)
>> I can put that in, whenever. Probably at the same time as implementing
>> the live/dynamic BE menus for selecting the root device.
> I'd like to know how to boot FreeBSD >= 9.1 with grub2.
>
> Following the instructions under $PORTSDIR/sysutils/grub2
>
> insmod ufs2
> set root=(hd0,gpt3)
> kfreebsd /boot/loader
> boot
>
> stopped working around FreeBSD 9.1-stable.
>
> I used Super Grub2 Disk image on the System Rescue CD written to USB stick.
>
> Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the
> System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but
> haven't tested that yet.
>
> What is the method you or PC-BSD uses?
>
> I want to use it on FreeBSD 9.2 and 10-current.
>
> I tried visiting pcbsd.org website but couldn't find any details.
>
> Tom
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
We use the same port, but have some custom grub.d/ scripts which builds
our /boot/grub/grub.cfg files.
https://github.com/pcbsd/pcbsd/tree/master/src-sh/pc-extractoverlay/ports-overlay/usr/local/etc/grub.d
The scripts do basic stuff like parsing output of "beadm" and creating a
list of Boot-Environment menus to build. Along with parsing
/boot/loader.conf, /boot/device.hints and friends. Lastly it even has
code to mount each of your BEs and copy the resulting grub.cfg file into
each, so that you have a unified menu regardless of which BE you are
currently booting.
One thing that I really want to fix is detecting which kernel modules
have what depends. Currently I have to ensure that /boot/loader.conf has
both the target module + depends in order for GRUB to load them properly.
If anybody wants to help hack on these and make them more "FreeBSD
generic" I think it could eventually go into the ports tree for everybody.
When grub-mkconfig is run, it generates a ZFS / BE specific boot-script,
with entries that look like this:
---
submenu "PC-BSD (default) - 2013-08-27 14:23" {
menuentry "Normal Bootup" {
insmod zfs
search -s -l tank1
kfreebsd /ROOT/default/@/boot/kernel/kernel
kfreebsd_module /ROOT/default/@/boot/zfs/zpool.cache
type=/boot/zfs/zpool.cache
set kFreeBSD.vfs.root.mountfrom=zfs:tank1/ROOT/default
kfreebsd_module_elf /ROOT/default/@/boot/kernel/siis.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/sdhci.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/geom_journal.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/geom_mirror.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/geom_eli.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/aesni.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/zfs.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/tmpfs.ko
kfreebsd_module_elf /ROOT/default/@/boot/modules/nvidia.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/dummynet.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/ipfw_nat.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/ipdivert.ko
kfreebsd_module_elf /ROOT/default/@/boot/modules/vboxdrv.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/zlib.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/opensolaris.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/linux.ko
kfreebsd_module_elf /ROOT/default/@/boot/kernel/crypto.ko
set kFreeBSD.hint.fdc.0.at=isa
set kFreeBSD.hint.fdc.0.port=0x3F0
set kFreeBSD.hint.fdc.0.irq=6
set kFreeBSD.hint.fdc.0.drq=2
set kFreeBSD.hint.fd.0.at=fdc0
set kFreeBSD.hint.fd.0.drive=0
set kFreeBSD.hint.fd.1.at=fdc0
set kFreeBSD.hint.fd.1.drive=1
set kFreeBSD.hint.atkbdc.0.at=isa
set kFreeBSD.hint.atkbdc.0.port=0x060
set kFreeBSD.hint.atkbd.0.at=atkbdc
set kFreeBSD.hint.atkbd.0.irq=1
set kFreeBSD.hint.psm.0.at=atkbdc
set kFreeBSD.hint.psm.0.irq=12
set kFreeBSD.hint.sc.0.at=isa
set kFreeBSD.hint.sc.0.flags=0x100
set kFreeBSD.hint.uart.0.at=isa
set kFreeBSD.hint.uart.0.port=0x3F8
set kFreeBSD.hint.uart.0.flags=0x10
set kFreeBSD.hint.uart.0.irq=4
set kFreeBSD.hint.uart.1.at=isa
set kFreeBSD.hint.uart.1.port=0x2F8
set kFreeBSD.hint.uart.1.irq=3
set kFreeBSD.hint.ppc.0.at=isa
set kFreeBSD.hint.ppc.0.irq=7
set kFreeBSD.hint.atrtc.0.at=isa
set kFreeBS
Re: BE Loader Menu (was Re: rcs)
Sorry for previous typo in From: line, missing right angle bracket at end. Then, in a finger error, I resent that message just before finding the error and making the needed correction. from Devin Teske: > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. I'd like to know how to boot FreeBSD >= 9.1 with grub2. Following the instructions under $PORTSDIR/sysutils/grub2 insmod ufs2 set root=(hd0,gpt3) kfreebsd /boot/loader boot stopped working around FreeBSD 9.1-stable. I used Super Grub2 Disk image on the System Rescue CD written to USB stick. Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. What is the method you or PC-BSD uses? I want to use it on FreeBSD 9.2 and 10-current. I tried visiting pcbsd.org website but couldn't find any details. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
from Devin Teske: > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. I'd like to know how to boot FreeBSD >= 9.1 with grub2. Following the instructions under $PORTSDIR/sysutils/grub2 insmod ufs2 set root=(hd0,gpt3) kfreebsd /boot/loader boot stopped working around FreeBSD 9.1-stable. I used Super Grub2 Disk image on the System Rescue CD written to USB stick. Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. What is the method you or PC-BSD uses? I want to use it on FreeBSD 9.2 and 10-current. I tried visiting pcbsd.org website but couldn't find any details. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: BE Loader Menu (was Re: rcs)
from Devin Teske: > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) > Both problems can be solved. > The loading of the kernel *after* choosing your boot device is trivial. > We've been doing it at $work for *years* (almost a decade?) > I can put that in, whenever. Probably at the same time as implementing > the live/dynamic BE menus for selecting the root device. I'd like to know how to boot FreeBSD >= 9.1 with grub2. Following the instructions under $PORTSDIR/sysutils/grub2 insmod ufs2 set root=(hd0,gpt3) kfreebsd /boot/loader boot stopped working around FreeBSD 9.1-stable. I used Super Grub2 Disk image on the System Rescue CD written to USB stick. Recently, I built sysutils/grub2, ran mkrescue, wrote that image to the System Rescue USB stick and made the entry in /syslinux/syslinux.cfg, but haven't tested that yet. What is the method you or PC-BSD uses? I want to use it on FreeBSD 9.2 and 10-current. I tried visiting pcbsd.org website but couldn't find any details. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
BE Loader Menu (was Re: rcs)
On Oct 9, 2013, at 9:42 AM, Kris Moore wrote: > On 10/09/2013 12:33, Allan Jude wrote: >> On 2013-10-09 12:23, Freddie Cash wrote: >>> On Wed, Oct 9, 2013 at 9:12 AM, Freddie Cash wrote: >>> On Wed, Oct 9, 2013 at 6:41 AM, Julian Elischer wrote: > On 10/9/13 2:35 AM, Freddie Cash wrote: > >> On Tue, Oct 8, 2013 at 9:09 AM, Alfred Perlstein wrote: >> >> You're right on the money, to be honest this is one of the reasons why >>> I've switched to using OSX as my desktop OS. >>> >>> zsh, vim, screen by default. and upgrades work. At the end of the day >>> I'm spending time doing work, not mucking about my workspace to make it >>> usable for development. >>> >>> I think this was brought up at BSDCan in the discussion about making >>> FreeBSD a more featured development platform. >>> >>> Speaking of... has anyone tried PCBSD? >>> >> PC-BSD isn't much different from FreeBSD. The installer is GUI and >> support >> ZFS, there are some GUI setup tools on first boot for X, there are some >> GUI >> tools to select binary drivers for X, and there are working pkgng repos >> available. >> >> I had a lot of issues with PC-BSD 9.0 and 9.1 as I was trying to do >> things >> "the FreeBSD way" which broke a lot of things that were done "the PC-BSD >> way" (aka don't manually edit config files used for booting). >> >> Switching to the "rolling-release" (aka PC-BSD 9-STABLE) and moving all >> my >> config file edits into .conf.local fixed my issues. Things >> have >> been running smooth, and I finally understand the beauty and simplicity >> of >> freebsd-update + pkg. OS gets updated once per month, packages get >> updated >> twice per month, no more compiling things from source. It's like using >> Ubuntu/Debian but with the power and features of FreeBSD. :) >> >> > When they went to a ZFS-only system, using GRUB, with no alternative, > then I'm afraid they lost me. > I want a root filesystem on UFS for reliabailty and simpleness. I can > debug it's media if needed. > Before then I really liked it (though ther eis not enough information on > how it works interneally if you want to use it. > hopefully that will come.. and I LIKE PBIs FreeBSD should adopt PBIs for > sure. > With PBIs you could make even quite base items separately installable. > versioning problems go away. > There's no GRUB in a default install of PC-BSD 9.0, 9.1, or 9.2. Even on a ZFS-only setup (which is what I run). It's using the FreeBSD loader, with custom artwork and menus. >>> Hrm, it seems they've changed things with the 9.2 installer. It does use >>> GRUB2 (e!) for the boot loader, and integrates support for ZFS boot >>> environments (via beadm) into it. :( Shame they didn't use the BE support >>> in the FreeBSD loader for this. Wonder if my 9-STABLE-based PC-BSD install >>> will get "upgraded" to GRUB? >>> >> The reason they went to grub2, is that the way the freebsd loader menus >> work, it loads the kernel before it draws the menu. This means if there >> is a problem with your kernel (probably the most valuable time to have >> boot environments) then the menu never comes up, and you cannot select >> which BE to boot from. Grub doesn't rely on a FreeBSD kernel until after >> you select which BE to boot from. >> >> Kris and I discussed it at length with Devin Teske, and while he has >> demonstrated being able to populate a lower menu with the ZFS datasets, >> I am not sure if the other issue can be resolved. >> > I'm late to the party again ;D (didn't realize the rcs thread had turned BE) Both problems can be solved. The loading of the kernel *after* choosing your boot device is trivial. We've been doing it at $work for *years* (almost a decade?) I can put that in, whenever. Probably at the same time as implementing the live/dynamic BE menus for selecting the root device. > Yea, GRUB is not my first choice, but ATM this is the "cleanest" way we > can do ZFS BE's. However if you don't like ZFS / GRUB, you can always > use regular FreeBSD and just grab our toolchain from > sysutils/pcbsd-utils* in ports or use our PKGNG repo: > > http://wiki.pcbsd.org/index.php/Turn_FreeBSD_into_PC-BSD%C2%AE > > I'm planning on using GRUB to do UEFI booting for 10.0 as well. But when > the FreeBSD loader matures to the point of having support for all these > features, I'll gladly move us back. > I had not been pushing hard on finishing the BE Forth because I knew that it would be a greater value add if we actually had "Boot from ZFS" finished first. Would be easier to test, that is, if I actually had a system booting from ZFS -- which is what Allan, jmg, and myself are hopefully working toward for FreeBSD 10.0-R. (smiles) -- Devin _ The information contained in this message
