Slashdot Mirror


LILO Bootloader Development To End

An anonymous reader writes: For any longtime Linux users, you probably remember the LILO bootloader from Linux distributions of many years ago. This bootloader has been in development since the 90's but development is finally ending. A homepage message reads, "I plan to finish development of LILO at 12/2015 because of some limitations (e.g. with BTFS, GPT, RAID). If someone want to develop this nice software further, please let me know ..."

24 of 135 comments (clear)

  1. LI by Anonymous Coward · · Score: 5, Informative

    fucked up partition table

  2. Well now Patrick will have to make a change by Bob+the+Super+Hamste · · Score: 3, Insightful

    Well it looks like Patrick will have to make a change.

    --
    Time to offend someone
    1. Re: Well now Patrick will have to make a change by armanox · · Score: 4, Informative

      Slackware team offered to help. They might fork it

      --
      I'm starting to think GNU is the problem with "GNU/Linux" these days.
    2. Re: Well now Patrick will have to make a change by resfilter · · Score: 4, Insightful

      it's perfectly ok for a really mature peice of software to stay in a distrubution, even in a relatively unmaintained state.

      you don't have to 'change' something just because new features aren't being added anymore, until the lack of a new feature prevents it from being installed on more than a few edge cases, or a substantial bug is found that makes its use unsafe.

      i doubt either of these will be the case with lilo for many years.

    3. Re:Well now Patrick will have to make a change by DarkOx · · Score: 3, Informative

      Nope, and he basically already said he does not plan to do so. New systems are going to be EFI more and more which means they will use ELILO, not LILO for systems using BIOS the current release of LILO will probably be fine and remain so.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    4. Re: Well now Patrick will have to make a change by mlts · · Score: 2

      LILO has been a fundamental piece of the OS for many years, and has worked quite well. GRUB has eclipsed it for most uses, but for applications where every byte of storage is at a premium, it still has a place.

      It is something that is well maintained, and can probably be retired, but still be useful, mainly since BIOS booting won't have the security changed and enhancements that UEFI comes with, so there isn't much that may change with the old BIOS based process in the future.

      I'm grateful that it has been well maintained for so long. It is a piece of software taken for granted... but yet essential to the function of a machine.

    5. Re: Well now Patrick will have to make a change by omnichad · · Score: 4, Funny

      the fundamental nature of how our computers boot is always up for GRUBs.

    6. Re: Well now Patrick will have to make a change by JWSmythe · · Score: 2

      From Patrick himself...

      http://www.linuxquestions.org/questions/slackware-14/lilo-developer-stepping-down-ending-the-project-4175552274/#post5413967

      "As long as it works, we'll include it."

      I've always preferred LILO over Grub. It's simplicity has always been great.

      --
      Serious? Seriousness is well above my pay grade.
    7. Re: Well now Patrick will have to make a change by Darinbob · · Score: 2

      It didn't really need to understand new file systems. As I recall it kept a list of blocks that were a part of the boot image. Ultimately things are complex enough that you need multiple boot loader stages but originally LILO had to be very small and compact. If it works on a computer it'll keep working unless something radical changes (such as someone turning the boot device into a RAID system).

      Also none of this is really about a fundamental nature of how computers boot, it's about the how the very strange ad-hoc design of the PC boots.

  3. Nice work developers! by nycsubway · · Score: 5, Insightful

    Thanks for maintaining LILO all these years. I certainly do remember LILO loading on my first installations of Linux. I tried to install it on an IBM PS/2 and the biggest challenge was their micro channel architecture. I don't think I was successful at all, but I learned quickly what the LIL... meant.

    1. Re:Nice work developers! by KGIII · · Score: 2

      I've pondered if there should be an open standard and just having a boot loader embedded in the BIOS that can be changed to boot to different partitions, disks, networked drives, etc... It could even allow you to setup a boot menu to select your OS of choice. In my mind it's the perfect spot to put it and I've yet to find a GOOD reason for this to not be the case.

      A simple pointer, or pointers for those who multi-boot, and an optional menu would be fairly trivial and it's not like it makes a giant security hole that I can think of. I can already select a boot device, why not make it partitions, network, etc? I've been wondering why it's not in the BIOS for years. I really can't think of a reason for it not to be and stripping the function as a requirement for the OS would make things much simpler in my opinion.

      I'm frequently opting to boot from a USB drive or a CD drive (while not wanting to change the default orders) as it is so I'm already using a menu to do that. It seems like it would be fairly trivial to make it recognize partitions and throw a simple menu up on the screen. They could still have an additional boot loader for things that need it or those who wish to customize it but they'd not need to and I'd think it would make things much simpler.

      Yes, yes I have been pondering this for a while. No, no I can't really think of any drawbacks or anything that makes it painfully difficult - even if it doesn't read partitions and only works with separate physical disks. Instead of ESC or F2 during boot it could have a nice optional menu brought up to select it or go to the default.

      This needn't be turned on by default so the average user would not even notice unless they went poking. Reading partition tables wouldn't be all that difficult either - I don't think though we may need to insist on some standards and those should be open and free. I doubt that even Microsoft would protest it or sabotage it.

      Seriously, I've been pondering this since the mid 1990s at least when I wanted to dual boot. Oddly, I think it was with LILO at the time and I think I was trying to dual boot an early RedHat install that I'd picked up at a store similar to Best Buy though it may not have been RedHat. It might have been Knoppix. Those brain cells have long since been formatted and overwritten with random content.

      --
      "So long and thanks for all the fish."
  4. there's still a healthy user base.. by resfilter · · Score: 5, Interesting

    .. of slackware people.

    as a slackware user myself, i have no real problem with grub and i use it on a few machines where it's advantageous, but most of my systems still boot with lilo, and i don't see any need to change them around in the near future.

    1. Re:there's still a healthy user base.. by Anonymous Coward · · Score: 3, Informative

      I'm on Gentoo. With a lot of the systematic (ahem) churn nowadays, I feel a bit of kinship with the Slackware people.

      When Grub got grubby (v2.0), I held off as long as I could with Grub 1. Then I found Syslinux and have never looked back. It *is* a little bit odd since you have to have the kernel in the same partition as extlinux, but this is not so strange if you are using a separate boot partition anyway. In my preferred setup, I have a statically linked Busybox and scripts in that partition so that it can serve both as the boot partition and a rescue partition (and I use the same kernel for both). I also have it set up so that early userspace is here--using a real file system instead of an initrd or initramfs. Why early userspace? I use LVM with the root partition on LVM. You don't *have* to use LVM, of course, the setup would work nicely, with normal partitions also.

  5. Simple but functional by UbuntuniX · · Score: 3, Interesting

    I was using LILO for quite a while recently, as my newest PC has a terrible UEFI system and the Debian installer couldn't configure GRUB by itself. It served me well in the interim.

  6. Mostly troll posts by Psychotria · · Score: 5, Insightful

    The current comments are mostly trolls and brain-dead idiocy. As typical for the new /.

    It wasn't until around 1999-2000 (I think) that distros started replacing LILO with GRUB as the default bootloader. GRUB offered many new powerful features that certainly helped its adoption. That is not to say, though, that LILO didn't have benefits as well (and in some circumstances it still does). It's sad to see that such a pinnacle piece of software contributing to Linux's success is going to be discontinued by the project's primary developer. LILO is such an important part of Linux history that it deserves a place is some kind of "hall of fame". But, it's open sourced so maybe -- just maybe -- someone will pick up the project so that it doesn't die. If not then it will be fondly remembered by those of us who were using Linux back in the olden days (1994 was my first install). Even if it's not continued the source code is informative, but the trolls will not understand that and just keep on using whatever their bootloader and praising whatever it is without understanding wtf it actually does and how the boot process actually works.

    1. Re:Mostly troll posts by starworks5 · · Score: 2

      maybe it will get picked up by systemD to replace the Grub bootloader ;-)

  7. I'd like to take a moment to express appreciation by hey! · · Score: 4, Interesting

    for the maintainers. The bootloader is a not particularly glamorous problem to work on, but it's critical to everyone and because it involves differing interpretations of standards by manufacturers and various OS developers it had to have been a headache.

    Of course later projects had the luxury of a clean sheet, hindsight, and more hardware resources, but without a solid bootloader in the early says of Linux, history would have been very different.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  8. It's good to have an end rather just withering awa by unimacs · · Score: 2

    I used it a very long time ago and countless people have used it before and since. It's far better to have a definite end date rather than just sporadic updates that grow farther apart and less significant, - leaving people to wonder if it's being maintained or not.

    Instead of the maintainer feeling the occasional pang of guilt over not doing anything, they can feel good about what was accomplished during the life of the project and move on to the next thing.

  9. What can I say? by Anonymous Coward · · Score: 2, Informative

    I've used it recently in some distro I tried (maybe a Slackware derivative) and I was surprised it still worked well after all these years (it's an old machine, but anyway...).

    I can only say thanks... to Werner, John and Joachim. These three guys have been in the forefront of the good battle and millions of people owe them at least a lot of respect.

    I wonder whether there are any scenarios where LILO works and Grub won't...

    LILO - Grub, Xfree86 - Xorg, SysV - Systemd, Fvwm - KDE & Xfce, OpenOffice.org - Libreoffice, lots of change for me all these years.

    To all you which made the world lighter for others, next time you take a sip of your favorite beverage (wine, beer, tea, whatever), please make a toast to yourselves in my name. Please know there's someone somewhere on this Earth that is very grateful to you and thinks you're the best.

    PS: All the other folks in software I didn't mention, you're in this one, too. (mc, Gimp, Konqueror, Kwin, Inkscape, Audacity, the kernel, GNU, etc. etc.)

  10. Re:Is it weird? by interval1066 · · Score: 2

    Naw, back in the day lilo was the shit.

    --
    Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
  11. Re:The endless repetition of history by sjames · · Score: 2

    Not really. Grub didn't try to replace su, login, getty, etc etc etc. It confined itself to being a bootloader. It didn't attempt to force changes on the kernel that would prevent LILO from working, so it was also a genuine choice.

  12. systemd by El_Muerte_TDS · · Score: 2, Funny

    Can't simply replace LILO with systemd?

    1. Re:systemd by rubycodez · · Score: 2, Insightful

      Can't simply replace Poeterring with an indoor manure spreader?

  13. Re:Sad by Anrego · · Score: 2

    Look into extlinux, it's what I switched to when grub totally went off the rails.