Follow Slashdot stories on Twitter

 


Forgot your password?
Close
typodupeerror
×
BSD Operating Systems

New Bootloader for FreeBSD 49

Posted by michael from the hopefully-we'll-live-to-see-the-day-that-acpi-works dept.
Dan writes "FreeBSD Release Engineering team's Scott Long has written a bootloader front-end script that allows one to enable/disable acpi, boot single users, etc. His primary motivation was to allow users to easily disable ACPI, since so many problems are popping up these days with it. He is hoping to have this be on at least the i386 bootcd for FreeBSD 5.1 scheduled for release June 2nd, and is looking for feedback."
This discussion has been archived. No new comments can be posted.

New Bootloader for FreeBSD More

New Bootloader for FreeBSD

Comments Filter:

  • It's not a bootloader (Score:5, Informative)

    by ciaran_o_riordan ( 662132 ) on Tuesday May 27, 2003 @05:13PM (#6051987) Homepage
    Heh, great research. He's written a "bootloader front-end script that allows one to enable/disable acpi". Not a boot loader.

    He says later that "[if] the script cannot start, it might leave your loader unable to load the kernel".

    For people interested in actual boot loaders, GRUB is looking for people to work on the BSD loading code (it works but needs some updating).

    Ciaran O'Riordan

    • Re:It's not a bootloader (Score:5, Interesting)

      by Arandir ( 19206 ) on Tuesday May 27, 2003 @05:34PM (#6052189) Homepage Journal
      Read the article again. It's not a "bootloader" front-end script, but a "bootloader front-end script". Notice the difference in quotes. One is a bootloader, and the other is a front-end script to a bootloader.

      p.s. Please people, take him up on his offer of working on the BSD loading code for GRUB. It's seriously out of date. I've got my own projects on the front burner so I can't at the moment.
      • huh? Read my post again :p

        I never said it was a: "bootloader" front-end script
        Like you, I said it was a: "bootloader front-end script"

        (My disagreement was with the title of the article)

        anyway...
        I forgot to also include a URL in my first post for the GRUB BSD hackers request, so here it is [gnu.org].

        Ciaran O'Riordan

    • Re:It's not a bootloader (Score:4, Informative)

      by shlong ( 121504 ) on Tuesday May 27, 2003 @07:15PM (#6052961) Homepage
      Dude, give the editors a break on this one. I purposely made the subject of my announcement abiguous in order to attract attention. Which sounds better, "New Bootloader!", or "My attempt to enhance the user experience with 100 lines of Forth".
      Anyways, this is just a start. Hopefully I'll have some time to do cool stuff, like have the loader scan for kernels and present you with a choice, control the serial console, etc. While GRUB is cool and all, editing configuration files is still a turn-off to many people.

    • GRUB is looking for people to work on the BSD loading code

      Well, considering that the project is hosted on gnu.org, I think it's safe to assume the project is GPL-licensed. Why would any BSD-ers be interested in grub if it isn't BSD-licensed? It seems that most are barely willing to grudgingly accept the GPL'd pieces they already do (which is why I believe Tendra will get plenty of support, and eventually replace gcc in the BSDs).

      Besides license issues (which are very significant), I don't know why anyon

      • Get a clue dude! BSD folk (like me) don't want to write GPLd software, don't want to link to GPLd software, and don't want to put GPLd software in the base system if we can help it, but we have no problem with *using* GPLd software if its worthwhile. Use the best tool for the job.

        GRUB is not part of any BSD's base system. It's part of the ports collection. The user can choose to use GRUB or not, just as they can choose to use bash or not. No recipient of a BSD system is going to encumbered by GRUB.

        There a

        • Get a clue dude! BSD folk (like me) don't want to write GPLd software, don't want to link to GPLd software, and don't want to put GPLd software in the base system if we can help it, but we have no problem with *using* GPLd software if its worthwhile.

          Just so you know, you are lecturing someone who is typing this message on a notebook with OpenBSD 3.3 installed, using an OpenBSD 3.2/Alpha fileserver as a foot-rest, and has a FreeBSD 4.7 box to my left.

          don't want to write GPLd software

          Well the parent wants

          • Wonderful. I was asking what exactly those features are.

            The most useful feature fo grub is the way that removing the partition which contains your bootloader makes your system unbootable. Particularly useful if you frequently install new OSes... (although I've stopped trying to find a decent Linux distro now I've installed FreeBSD.)

          • GRUB's not bad (Score:3, Interesting)

            by siskbc ( 598067 )
            Wonderful. I was asking what exactly those features are... I would especially like to hear what incredible features make it worth the effort of doing the coding work, and worth the hassle of actually using the GRUB command-line, which is more cumbersome than any other boot-loader (with a command-line) that I've used. Saying "It's so great dude!" isn't exactly going to change my mind.

            First, to disclose, I'm a linux user (Hey! stop throwing things!) though I'm thinking of trying some *BSD flavor. I used to

            • I used to use LILO, it really sucks (I'm sure you guys are really going to argue that one, huh?), so I tried GRUB. It doesn't.

              I wouldn't say that Lilo is great, but I think it's a step up from Grub. If I have to use Linux, I stick with Lilo.

              it has no cylinder issues or boot partition size issues like some boot loaders (ahem: LILO!).

              Hasn't been a problem for lilo since before grub was even created.

              you don't have to reinstall the loader when you make a configuration change

              You've got one there, but I d

              • Hasn't been a problem for lilo since before grub was even created.

                I'm not so sure that has been completely fixed, or maybe it was my BIOS. I had a partition that LILO completely puked on, GRUB had NO problem with it. And my LILO config was fine - I could boot other partitions fine, just not the 20 GB one. Could be that GRUB, being a bit higher-level, was able to overcome this, I don't know. Or maybe I missed a LILO trick (though I tried everything I could think of, like LBA stuff). Either way, after a

        • There are times when GPLd software does make sense for the base system (from the FreeBSD perspective). That's when the software is clearly the best of breed and won't encumber anything else. A good example is GNU tar.

          Funny that you mention GNU tar. The NetBSD folks have had problems with tar files generated by GNU tar which couldn't later be unpacked by NetBSD's pax, and, no, it wasn't PAX's fault, but this annoying 'embrace and extend' trend in GNU software.

      • Re:It's not a bootloader (Score:1, Informative)

        by Anonymous Coward
        I don't know why anyone would WANT grub. When using linux, I much prefer lilo, despite it's faults, for the simplicity and power it has. The BSD loaders are already rather powerful, so unless some masochists out there are dying to look at a graphical menu for 5 seconds before their system boots, what would grub even have to offer, even if it worked on the BSDs?

        things i like about grub:

        1. netboot
        2. lock entries by password
        3. netboot
        4. pass args to linux kernels (if it just could for the bsds as well)
        5. ne

  • Ahem (Score:2, Interesting)

    by Anonymous Coward
    It's not a new boot loader. It's a new interactive script that runs on the existing boot loader. The FICL (Forth-Inspired Command Language) based loader has always allowed you to do things like this. It's a nice addition anyway, although I'll probably disable it on my machine if it gets committed.
  • Does this new boot loader finally allows to install FreeBSD on an extended dos partition ?

    I don't understand why BSD never solved that issue. This is a serious showstopper for people who want to try FreeBSD and whoose hard disk already has other operating systems. I really don't want to backup and reinstall every partition of my hard disk just to see what FreeBSD 5 looks like.

  • I really, really hate it when they post those slashdot bsd articles with links to bsdforums. We do not need this useless layer of indirection. Bsdforums do not have any ifnormation, just a link to the mailing list archive post. If I wanted to read basforums I would. I read slashdot and want a pointer to content, not to a place which has link to the content. This is breeding carma whores.

  • ACPI (Score:2)

    by meshko ( 413657 )
    I'm not too clear on what does this do. My CURRENT is a couple of weeks old and I can just do unset load_acpi and it won't load it. The bigger problem is that boot process just hangs if I don't have ACPI loaded.
  • From the BSD ACPI page:

    Almost everything in ACPI is transparent, until it does not work. That is usually when you as a user will know there is something not working properly.

    Maybe more effort on diagnosis tools, rather than a script to turn it off, is needed.

  • Because I only have one OS and don't reboot it, you, insensitive clod!

Slashdot Top Deals

Let's organize this thing and take all the fun out of it.

Close