[Slackbuilds-users] grub_legacy worth keeping in the repo?

fsLeg fsleg at t-rg.ws
Fri Jul 17 08:19:19 UTC 2026


The only reason to use grub-legacy AFAIK is the `map` command that allows you to do some things which aren't possible with grub2. But you'd usually use grub4dos as the purpose of this command is to boot from images for which loop mounting isn't enough, and it's usually done from removable media. The only meaningful difference between grub-legacy and grub4dos is filesystem support, unless I'm mixing things up and mapping is exclusive to grub4dos (it's been a long time since I used old grub). Obviously, it's only useful for deprecated images on deprecated hardware.

On July 17, 2026 10:28:31 GMT+03:00, "B. Watson" <urchlay at slackware.uk> wrote:
>
>These are just guesses... I'm trying to justify not removing
>grub_legacy from the repo (as its maintainer is MIA).


More information about the SlackBuilds-users mailing list