Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
06-13-2014, 01:03 AM
|
#1
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
|
Grub 1
Is anybody able to compile Grub 1 on 14.1?
The package from 14.0 /extra seems to work fine, but I am unable to compile Grub 1 under 14.1. I get a failure in asm.S.
Just curious.
Thanks.
P.S. Yes, I know 14.1 comes with Grub 2 and Lilo.
|
|
|
06-13-2014, 01:20 AM
|
#2
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Grub-legacy may require patches to build on current systems, but you may have to scour other distributions for them.
|
|
|
06-13-2014, 10:22 AM
|
#3
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
Original Poster
|
I have been looking. I was hoping to find a distro still using Grub 1, to find the sources and patches, but no luck yet.
|
|
|
06-13-2014, 11:37 AM
|
#4
|
Senior Member
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,223
Rep:
|
Gentoo has grub-legacy, you might want to take a look at it.
|
|
|
06-13-2014, 11:40 AM
|
#5
|
Member
Registered: Sep 2013
Location: Sumter SC, USA
Distribution: MX, Lubuntu
Posts: 449
Rep:
|
I think PCLinuxOS uses it as well...
|
|
|
06-13-2014, 02:39 PM
|
#6
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Gentoo might as well. They hang onto a lot of old packages.
|
|
|
06-13-2014, 04:08 PM
|
#7
|
LQ Guru
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,863
|
PCLinuxOS does as does CentOS.
|
|
|
06-13-2014, 04:55 PM
|
#8
|
Member
Registered: May 2008
Location: Republic of Texas
Posts: 393
Rep:
|
You should find grub (0.97) under slackware-14.0 and 'extra'
Otherwise, I have got it as a slackware package - I'll mail it to you ...
Note that grub-0.97 is _only_ 32-bit - to my (meagre) knowledge, nobody has successfully managed to compile it using 64-bit :-(
That being said - I'm a big fan of grub-legacy - use it all the time as my 'master-boot', then whenever I install a distro, I put its bootloader on the root filesystem and just chainload to it.
IMHO - the downfall of grub2 is that its trying to be all-encompassing. If you want to remove the one distro whose grub2 is on the MBR - then you need to install another one there ...
'ts true what they say - grub2 is an OS looking for a decent bootloader! ;-)
Last edited by perbh; 06-13-2014 at 04:59 PM.
|
|
|
06-13-2014, 06:55 PM
|
#9
|
Member
Registered: Apr 2011
Location: California, USA
Distribution: Slackware
Posts: 528
|
32-Bit
Quote:
Originally Posted by perbh
Note that grub-0.97 is _only_ 32-bit - to my (meagre) knowledge, nobody has successfully managed to compile it using 64-bit :-(
|
As I type and show my ignorance of grub (and other topics) ...
As a boot loader it shouldn't matter it it's 32 or 64 bit. It's independent of the OS to be installed, correct?
Perhaps it would matter if one only had a 64 bit resources available to build grub.
Would there be an advantage to having grub compiled as 64 bit?
You were probably just making an observation, but it made me wonder. Just asking.
|
|
|
06-13-2014, 09:25 PM
|
#10
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
Original Poster
|
Quote:
I think PCLinuxOS uses it as well...
|
I found an srpm from PCLOS. Contains a buttload of patches, far more than Slackware.
Quote:
You should find grub (0.97) under slackware-14.0 and 'extra'
|
Uh, yeah, I know, I mentioned that in my original post. That is where I got the sources to compile.
Quote:
nobody has successfully managed to compile it using 64-bit :-(
|
Yeah, I know. I am using 32-bit 14.1 to compile. My SWAG is gcc gets stricter with each release and that now causes the build failure.
Quote:
As a boot loader it shouldn't matter it it's 32 or 64 bit. It's independent of the OS to be installed, correct?
|
Operationally, Grub 1 is system agnostic. Just doesn't compile on 64-bit. I am guessing because part of the code is assembler.
|
|
|
06-13-2014, 09:35 PM
|
#11
|
Member
Registered: May 2008
Location: Republic of Texas
Posts: 393
Rep:
|
Quote:
As a boot loader it shouldn't matter it it's 32 or 64 bit. It's independent of the OS to be installed, correct?
|
Absolutely correct - you can easily boot a 64-bit distro. I mentioned the fact cuz Woodsman had trouble compiling it - so I just wondered if he was trying a 64-bit compile ...
Quote:
Just doesn't compile on 64-bit. I am guessing because part of the code is assembler
|
That has always been my understanding as well ...
Last edited by perbh; 06-13-2014 at 09:37 PM.
|
|
|
06-13-2014, 09:46 PM
|
#12
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,251
|
Quote:
Originally Posted by Woodsman
Operationally, Grub 1 is system agnostic.
|
Not if it needs to boot a non-supported filesystem. The change to 256 byte inodes for ext4 (and later ext3) exposed that. Or btrfs.
What about gpt formatted disks ?.
These are but a couple of the reasons grub legacy was abandoned. If you choose to pursue non-supported software, you have to expect dramas.
|
|
|
06-14-2014, 01:37 AM
|
#13
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
Original Poster
|
Quote:
These are but a couple of the reasons grub legacy was abandoned. If you choose to pursue non-supported software, you have to expect dramas.
|
Uh, no, I expect to poke around the web looking for help and solutions. Oh, wait, I am doing just that in this thread.
|
|
|
06-14-2014, 09:45 AM
|
#14
|
Amigo developer
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,928
|
I think I wouldn't hesitate to use the pclinuxos sources including all the patches. You could also use sources from fedora -even if a couple of years old. LFS or gentoo probably use less patches, if you prefer.
I'm still using grub-legacy -a version whose patches I have picked and chosen over the years.
|
|
|
06-14-2014, 10:07 AM
|
#15
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
LFS switched to Grub-2.x a while ago, but the patches for legacy are still available and should allow for a compile in a 64-bit environment:
http://www.linuxfromscratch.org/patches/downloads/grub/
That should help, but if it conflicts with glibc or GCC you might be stuck.
|
|
|
All times are GMT -5. The time now is 03:13 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|