[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Is grub perfect? (was Re: Does LXDE really require lightdm?)



On Mon, Jun 30, 2014 at 10:53 AM, Steve Litt <slitt@troubleshooters.com> wrote:
> On Mon, 30 Jun 2014 12:24:41 +0200
> berenger.morel@neutralite.org wrote:
>>
>> Otherwise, if you do not like grub, there are other boot loaders.
>> LILO at least works fine, and seems to be ok for your requirements: a
>> single easy text file as configuration.
>> It's what I'm doing, excepted at work for 2 reasons: it does not
>> seems to support the new crap named... how is it named? Secure boot?
>> Something like that. The fun thing about that is that the grub
>> installation did not allowed me to have a dual boot with the original
>> windows, so I could be using LILO right now it would not change
>> anything. The other reason is that I do prefer mainstream stuff on
>> computers that I do not want to tinker. Never had any problem with
>> LILO, but just in case...
>
> Thanks for the great suggestion. I had originally ruled out LILO (which
> I used back in the 20th century) because it can't deal with EFI boot,
> as I remember. But (let's all take some time to laugh), my boot disk is
> a 250 SSD with an MRB partition, so EFI (and secure boot) is a
> non-issue.

There's elilo. I've never used it so I have no idea how close it is to
lilo config-wise.

There are also gummiboot and refind.

Neither are packaged for Debian but they're both good efi boot managers.

If you don't like systemd you might not like gummiboot because it's
developed by Kay Sievers. It's what I use on my laptop. Another reason
that you might not like it is that you have to have your kernel and
initramfs on the efi partition.

refind on the other hand is slightly more complex and understands some
filesystems so you don't need to mount the efi partition as "/boot" or
copy the kernel and initramfs to "/boot/efi".

They're both boot managers not bootloaders so you have to ensure that
the efi stub is compiled into the kernel.


Reply to: