Package Details: grub-legacy 0.97-25

Git Clone URL: (read-only)
Package Base: grub-legacy
Description: A GNU multiboot boot loader
Upstream URL:
Licenses: GPL
Conflicts: grub
Submitter: pressh
Maintainer: tuckerboniface
Last Packager: felix.s
Votes: 84
Popularity: 0.003371
First Submitted: 2012-07-20 09:42
Last Updated: 2017-08-02 15:24

Latest Comments

JonnyJD commented on 2016-04-17 13:29

I am getting
undefined reference to `__stack_chk_fail'
on current Arch

which I could fix with adding " -fno-stack-protector" to CFLAGs in the PKGBUILD

Anonymous comment on 2013-08-10 11:55

I need to have grub2 and grub-legacy installed side-by-side.

Due to file conflicts, I assume the easiest way is to have grub-legacy installed in separate directory, say /usr/share/grub-legacy (which would serve as a / for this package).

Could somebody please advise me how to do it with minimal effort, i.e. so that scripts, configurations, etc. would still work relative to new root? Specifically, I was looking into using "PREFIX", but I do not understand how the entire build chain works.

mhellwig commented on 2013-06-04 20:51

oh. I found what the problem was, had to do with using the SOL (serial over lan) from a Supermicro-board .. for the menu.lst, that means you should NOT specify terminal serial .. because that apparently doesn't work. after removing that line, it now works. yay!

ava1ar commented on 2013-06-04 20:12


I was in same situation some time ago during previous update of grub-legacy package. Spent some time trying to fix it and gave up finally - migrated to grub2. Actually I planned this migration earlier, because going to upgrade my laptop to something modern, which will came with EFI I suspect. So, maybe go with grub2 too?

mhellwig commented on 2013-06-04 20:05

so I've (re)installed this _after_ doing the filesystem switch, figuring then the symlinks for /bin and /sbin already exist and so installing there wouldn't be so bad since then it'd just get written to /usr/bin anyway.

First attempt to boot: imagine my surprise when the system wouldn't come up because grub-legacy upon installation uses its own menu.lst and moved mine to menu.lst.pacsave. So wrong root, no cryptdevices and so forth. After fixing that manually (hitting "e" in the grub menu, typing in what I had written down somewhere) the system came up.

Then I figured I want this to boot by itself (obviously) so I moved my old menu.lst.pacsave to menu.lst and hit reboot. And now this thing won't boot. Like, at all. It hangs at
"GRUB loading stage 1.5

GRUB loading, please wait...
<blinking cursor>"

And that's it.

So next step I got myself a grml iso (live-CD) and powercycled and used my ipmi console to mount that virtually and boot from it (yeah, it's a remote server ..)

Mounted my ARCH system, chrooted to it, re-ran grub-install to /dev/sda, that went through without error.

Reboot, system still won't come up, same error as above. Hangs at the "loading grub..." stage, no error code.

What could be wrong? This system needs to be up half an hour ago ...

kalib commented on 2013-06-04 17:45

Worked just fine now. ;] thanks

kalib commented on 2013-06-04 17:25

Am I the only one who can't get it to work?

clocal-1.13/substnot.m4' '/usr/share/aclocal-1.13/tar.m4' 'acinclude.m4' --trace='AC_DEFUN:$f::$n::${::}%' --trace='AC_DEFUN_ONCE:$f::$n::${::}%' --trace='AU_DEFUN:$f::$n::${::}%' --trace='_AM_AUTOCONF_VERSION:$f::$n::${::}%' --trace='AC_CONFIG_MACRO_DIR_TRACE:$f::$n::${::}%' --trace='AC_CONFIG_MACRO_DIR:$f::$n::${::}%' --trace='_AM_CONFIG_MACRO_DIRS:$f::$n::${::}%' --trace='grub_CHECK_USCORE_END_SYMBOL:$f::$n' --trace='grub_ASM_PREFIX_REQUIREMENT:$f::$n' --trace='_AM_DEPENDENCIES:$f::$n' --trace='grub_DEFINE_FILE:$f::$n' --trace='AM_SET_DEPDIR:$f::$n' --trace='_AM_MANGLE_OPTION:$f::$n' --trace='AM_PROG_INSTALL_STRIP:$f::$n' --trace='grub_CHECK_EDATA_SYMBOL:$f::$n' --trace='_AM_PROG_TAR:$f::$n' --trace='_AM_SUBST_NOTMAKE:$f::$n' --trace='AM_AUX_DIR_EXPAND:$f::$n' --trace='AM_AUTOMAKE_VERSION:$f::$n' --trace='grub_CHECK_USCORE_START_SYMBOL:$f::$n' --trace='AM_SANITY_CHECK:$f::$n' --trace='AM_DEP_TRACK:$f::$n' --trace='AM_SILENT_RULES:$f::$n' --trace='AM_MAINTAINER_MODE:$f::$n' --trace='AM_MAKE_INCLUDE:$f::$n' --trace='AM_SET_LEADING_DOT:$f::$n' --trace='_AM_IF_OPTION:$f::$n' --trace='grub_PROG_OBJCOPY_ABSOLUTE:$f::$n' --trace='AM_SET_CURRENT_AUTOMAKE_VERSION:$f::$n' --trace='AM_MISSING_HAS_RUN:$f::$n' --trace='AM_OUTPUT_DEPENDENCY_COMMANDS:$f::$n' --trace='grub_ASM_USCORE:$f::$n' --trace='_AM_SET_OPTION:$f::$n' --trace='grub_ASM_ABSOLUTE_WITHOUT_ASTERISK:$f::$n' --trace='AM_RUN_LOG:$f::$n' --trace='AM_SUBST_NOTMAKE:$f::$n' --trace='grub_ASM_ADDR32:$f::$n' --trace='_AM_OUTPUT_DEPENDENCY_COMMANDS:$f::$n' --trace='AM_PROG_AS:$f::$n' --trace='AM_PROG_CC_C_O:$f::$n' --trace='grub_CHECK_END_SYMBOL:$f::$n' --trace='grub_CHECK_START_SYMBOL:$f::$n' --trace='_AC_AM_CONFIG_HEADER_HOOK:$f::$n' --trace='AM_CONDITIONAL:$f::$n' --trace='AM_INIT_AUTOMAKE:$f::$n' --trace='AM_MISSING_PROG:$f::$n' --trace='grub_CHECK_USCORE_EDATA_SYMBOL:$f::$n' --trace='_AM_SET_OPTIONS:$f::$n' --trace='grub_CHECK_USCORE_USCORE_BSS_START_SYMBOL:$f::$n' --trace='AM_PROG_INSTALL_SH:$f::$n' |: Arquivo ou diretório não encontrado
==> ERROR: A fail happened on build().
==> ERROR: MAKEPKG couldn't compile grub-legacy.

simon04 commented on 2013-06-04 16:51

0.97-25: {/bin,/sbin,/usr/sbin} adaptions …

bernarcher commented on 2013-06-04 16:38

Is it really necessary to install install-grub in /usr/sbin? It would fit in /usr/bin as well.
There is no /usr/sbin on the default PATH set by the recent /etc/profile changes.

darose commented on 2013-06-04 15:43

simon04 said he'd take it on

All comments