LILO Bootloader Development To End 135
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 ..."
LI (Score:5, Informative)
fucked up partition table
Re: (Score:2)
makes me wonder what percentage of slashdotters still understand your reference...
LI oh shit oh shit oh shit LO phew
also, who the f thought RED was the best default colour for a boot menu? it looks like a freaking error before you even start booting up the OS. personally, i find lilo just as uncomfortable to use as grub2. to me, grub 1 was the pinnacle of bootloader usability (blue colour, yay!)
thanks (Score:1)
RIP thanks for the memories
Well now Patrick will have to make a change (Score:4, Insightful)
Re: Well now Patrick will have to make a change (Score:5, Informative)
Re: Well now Patrick will have to make a change (Score:5, 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.
Re: (Score:1)
Re: Well now Patrick will have to make a change (Score:5, Funny)
the fundamental nature of how our computers boot is always up for GRUBs.
Re: (Score:2)
This pun hurt. Oh, but it hurt so good...
Re: (Score:2)
One of the big advantages of grub1 over lilo was that you didn't have to run anything when you made a change in the config. You could also *easily* edit the config at boot time if needs be (typos etc...). The option to edit at boot time still exists in grub2 but that horrific, bloated configuration file is almost meaningless to anyone who is not a grub developer; not to mention having to run grub-install to affect changes.
grub2 see
Re: (Score:3)
Re: (Score:1)
Re: (Score:2)
Re: (Score:3)
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 w
Re: (Score:2)
I liked LILO, because of the simple fact that is was so much simpler than GRUB. If you are booting a single partition system (plus swap) from ext3, there is not much wizbang you need. But then I also just use what the distro uses by default, since it works out of the box.
Re: (Score:3)
From Patrick himself...
http://www.linuxquestions.org/questions/slackware-14/lilo-developer-stepping-down-ending-the-project-4175552274/#post5413967 [linuxquestions.org]
"As long as it works, we'll include it."
I've always preferred LILO over Grub. It's simplicity has always been great.
Re: (Score:2)
Too many well's there, I thing, but LILO works well
Re:Well now Patrick will have to make a change (Score:4, 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.
Nice work developers! (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.
Re: (Score:1)
I haven't noticed LILO in years. GRUB is mostly the default these days - from what I've seen. If it has been in a distro then it is in so deep that I did not notice. Add to that things like boot-repair and I've not even had to play with GRUB manually either. I don't actually remember the last time I saw LILO? I've not tried them all but I've not seen a distro with it in ages - at least not one that I noticed.
Re: (Score:2)
I haven't noticed LILO in years.
Same here, with grub and loadlin [linux.sh] available, and I know grub is actively maintained, I can't say I've missed anything. Plus with EFI now, well, it seems like a solution looking for a problem.
Re: (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 h
Re: (Score:1)
Nice and thank you for the information. I had no idea it was in the spec, or at least partially. A nice handy GUI for it that one can optionally load would be nifty too. Is the EFI available in user-land so that one could develop a GUI for it? Heck, it needn't even be GUI - just a menu would work as well as some ability to customize it to select a default, have a set wait time, etc...
Re: (Score:2)
Re: (Score:2)
I still use LILO because some old motherboards won't boot with GRUB in 64-bit mode.
you can probably emulate those old systems on a modern $300 computer
Re: (Score:2)
you can probably emulate those old systems on a modern $300 computer
It's not about emulation, as these are plain x86-64 machines, not some old architecture. It's about cost. I paid closer to $30 than $300 for these machines, and they get the job done until I find a good reason to invest a few hundred in something more modern.
Re: (Score:1)
You may have paid $30 for the machine itself, but you continue to pay every year for it in terms of power, maintenance, occupied space, and if your hobby time is limited, engineering time figuring out hacks to make it continue working.
Particularly if these are x86-64 machines that don't work with grub, suggesting that they were from around the first generation. If you recall that
Re: (Score:2)
You may have paid $30 for the machine itself, but you continue to pay every year for it in terms of power, maintenance, occupied space, and if your hobby time is limited, engineering time figuring out hacks to make it continue working.
Particularly if these are x86-64 machines that don't work with grub, suggesting that they were from around the first generation. If you recall that time in the 90's, those cpus were huge power hogs. I'd never encountered power supplies burning out (without a discrete graphics card) until I met those first gen 64s. Nowadays, you can easily power a magnitude more compute power with the same electrical power cost.
I understand the general sentiment, I was kind of expecting this. I'm rather power conscious in general, and all of my machines, including these old ones, have "laptop" CPUs in small form factor mobos (if not actual laptops). The old ones have a similar TDP to modern laptop ones. One of these mobos runs off a 80 W PicoPSU; the others have heavy discrete GPUs, so they have semi-regular (though fanless) PSUs.
I'm well aware that modern CPUs are more efficient, and I could actually use modern mobos with more
Re: (Score:1)
That's an interesting use for it. I've not had GRUB not work in a very long time - I recall it breaking once when I'd been dual booting Linux and XP. I can't actually remember any other issues with it and that happened after an update? On the other mitt, I've had LILO flake a few more times. I seem to recall it trashing my MBR bad enough that an MBR repair did not work and I had issues re-installing on any partition and was forced to actually reformat the drive - I think I may have even had to do a low-leve
there's still a healthy user base.. (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.
Re: (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 i
Same here (Score:2)
I still use lilo on all 3 of my boxes. I don't need a pre boot "enviroment" or however grub is described, I just want the OS booted and up and running ASAP. If there's a problem with booting I'll just grab a live DVD , I'm not going to wrestle with a load of cryptic bootloader commands to try and solve the problem.
Simple but functional (Score:3, Interesting)
Re: (Score:2)
Re: (Score:3)
Mostly troll posts (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.
Re: (Score:2)
...it will be fondly remembered by those of us who were using Linux back in the olden days
There is no need (yet) to be nostalgic about LILO: I (ex slackware, now gentoo) am still using LILO, and probably many others are using it too. If it ain't broken, why replace it?
Re: (Score:3)
maybe it will get picked up by systemD to replace the Grub bootloader ;-)
Re: (Score:2)
maybe it will get picked up by systemD to replace the Grub bootloader ;-)
In other news, LILO is being replace with STITCH.
Re: (Score:2)
I'd like to take a moment to express appreciation (Score:5, 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.
Re: (Score:2)
Re: (Score:2)
Entirely this. In my opinion grub 2 is where they really went off the rails. When you have a set of configuration files that configure the set of scripts that generate the _actual_ configuration, something has gone horribly, horribly wrong.
Personally I use extlinux and have been very happy with it. You get the classic "single and really simple configuration file" feel of LILO with the subset of bells and whistles that you actually need.
Re: (Score:2)
Entirely this. In my opinion grub 2 is where they really went off the rails. When you have a set of configuration files that configure the set of scripts that generate the _actual_ configuration, something has gone horribly, horribly wrong.
Those scripts and configuration files sprang into existence well before GRUB 0.97 even. In GRUB 2, they're still not required and the configuration file is not hard to hand-write if you don't want the auto-OS detection and config generation said scripts provide :P
It's good to have an end rather just withering awa (Score:3)
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.
Re: (Score:2)
I wonder how long it is til systemd decides that the linux kernel is too confusing for people who just use x86-64 and replaces the kernel.
What can I say? (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 - L
Re: (Score:2)
Get a room, faggot.
I had no idea XBOX LIVE and /. were merging...
Re: (Score:2)
Re: (Score:2)
Do one thing and do it well.
Yes, GRUB is an improvement over LILO. But it still just does the one thing: Loads and boots a selected O/S. It doen't break other systems or apps. In that sense, it's adoption is nothing like systemd.
Re: (Score:3)
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.
Re: (Score:2)
LILO Dallas Multipass (Score:2)
Yes, I'm sorry.
Re: (Score:2)
Yes, now that's it's 2015 things are so much more advanced with grub and we instead have hang with
GRUB loading stage2...
staring at you
Re: (Score:2)
GRUB doesn't do stages anymore. That would be a "rescue>" prompt. It's a little better, and can usually help to save from minor configuration mishaps, though not useful for more major oopses (maybe you changed file systems and forgot to update GRUB, now the boot.img doesn't understand how to read the file system...). It also gives a lot of pause to the thought of "Oh crap, what are GRUB's commands?"
Re: (Score:2)
Sad. Grub is too complicated. I like lilo for the simple configuration file. Great power
Apple II is very simple, thus great power.
Re: (Score:3)
Look into extlinux, it's what I switched to when grub totally went off the rails.
Software that works (Score:2)
My personal/playpen Linux box at work is Slackware. It uses LILO. Of course.
There is always a place for software that works. Software that does one thing, does exactly what it's supposed to do, and does it well.
...laura
systemd (Score:3, Funny)
Can't simply replace LILO with systemd?
Re: (Score:3, Insightful)
Can't simply replace Poeterring with an indoor manure spreader?
LIL? (Score:1)
LIL-
Oh no! (Score:1)
First init, and now this? Where will it end?
LILO ftw (Score:1)
I only switched to GRUB because of installed defaults and my laziness. LILO was, imo, always simpler, cleaner, made more sense.
GRUB works, but it feels like it's been engineered to be way more than it needs to be, and, in the process, it starts to suck. As an example, I started looking into GRUB theming (hey, a pretty boot screen would be nice). Turns out I could never convince GRUB to use a TTF font and display the table (and items in the table) correctly. That's a feature that may as well not be in there
... BootLoader to be incorporated in SystemD (Score:1)
Stating that LILO and GRUB were "confusing and broken", Lennart Poettering has announced that SystemD will take over MBR management. "It's just a small step towards complete system domination", the great leader was heard to muse, "After all, PulseAudio did so well and everyone is loving how much easier SystemD is than init scripts. What could possibly go wrong?".
Re: (Score:2)
...only sausage has two [youtube.com]!
How many ends does a circle have?
Re: (Score:2)
What about a circular sausage?
Re: (Score:2)
they're a pain in the ass
Re: (Score:2)
I used it like people use locks on their homes, I had a boot floppy with LILO and no MBR on the fixed disk, so the floppy had to be in the computer to boot as it literally booted from LILO installed on a floppy disk, then LILO found the kernel on the fixed disk and the OS loaded. Take the floppy out and the computer doesn't boot.
Obviously this wasn't going to keep out people that knew what they were doing and came prepared with their own bootable media, but it kept out roommates and their friends.
Re: (Score:1)
Same for me. My computer booted to Windows95, unless you had the mystery floppy in the drive (1 of hundreds scattered about) -- Then it would boot to linux. What did I use this secret installation for? Nothing useful at the time. I just missed the unix machines I had access to in college.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)