LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-29-2016, 06:46 PM   #16
ReaperX7
LQ Guru
 
Registered: Jul 2011
Location: California
Distribution: Slackware64-Current
Posts: 6,449
Blog Entries: 15

Rep: Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021Reputation: 2021

If you're trying out GPT+EF02 (BIOS Boot Partition) with a Legacy BIOS mode enabled motherboard then LILO should be fine, up to the 2.2GB+ barrier.

However, I would consider migrating to Grub as it is still actively developed and supports both EF00 EFI and EF02 BIOS Boot Partitions.
 
Old 05-31-2016, 07:21 PM   #17
gordydawg
Member
 
Registered: Sep 2013
Distribution: slackware
Posts: 41

Original Poster
Rep: Reputation: Disabled
I would like to thank everyone for their thoughts on this thread. I still prefer legacy bios booting even on UEFI motherboards. Your mileage may vary.

In the past, I used Lilo for easy chain loading of other OS's (other distros and FreeBSD). With -current, I can still use Lilo, even on GPT partitioning. But after making changes in liloconf, I now get sector 63 warnings when making changes due to newer sector alignments favored by gdisk and the newer version of fdisk. Oddly, though everything still boots fine.

For my own uses, Syslinux works well for GPT and similar linux distros, but I've yet to get it successfully chain loading to ZFS based FreeBSD.

As for Grub, I'm not familiar with it to grok how to change it post install (seems it resides in many config files) and if it supports chain loading, even to ZFS based Unix's.

Lilo had a good run, but it's now depreciating. One of these days, I'll be the last person to turn off the lights on Lilo.

Thanks for your opinions and observations.

Last edited by gordydawg; 05-31-2016 at 07:24 PM.
 
Old 06-01-2016, 03:25 AM   #18
luvr
Member
 
Registered: May 2005
Location: Boom - The Home Town of Tomorrowland, Belgium
Distribution: Slackware, Debian, Xubuntu
Posts: 315
Blog Entries: 1

Rep: Reputation: 135Reputation: 135
Quote:
Originally Posted by gordydawg View Post
But after making changes in liloconf, I now get sector 63 warnings when making changes due to newer sector alignments favored by gdisk and the newer version of fdisk. Oddly, though everything still boots fine.
That's because you're probably still using the traditional partition alignment, which is based on cylinder, head, sector addresses. The first partition then generally starts at sector number 63.

These days, more and more high-capacity hard disks use hardware sectors of 4096, instead of 512, bytes (even though they continue to use "logical sectors" of 512 bytes, which means that your computer and Operating System will still count units of 512-byte sectors). Since one hardware sector (i.e., 4096 bytes) then corresponds to 8 logical sectors, you would do better to align partitions on multiples of 8 sectors for optimal performance. The general recommendation, nowadays, is to align partitions on multiples of 1MB, i.e., 2048 (logical) sectors.

The traditional alignment will still work, but will be suboptimal on modern high-capacity disks (hence the warning).

Quote:
As for Grub, I'm not familiar with it to grok how to change it post install (seems it resides in many config files) and if it supports chain loading, even to ZFS based Unix's.
GRUB does support chainloading. The "many config files" are really just there to control its automatic configuration options. You can still write your GRUB configuration manually, though.
 
Old 06-03-2016, 04:57 AM   #19
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 2,270

Rep: Reputation: 605Reputation: 605Reputation: 605Reputation: 605Reputation: 605Reputation: 605
Quote:
Originally Posted by luvr
Quote:
Originally Posted by rkelsen
Quote:
Originally Posted by Didier Spaier
You are just making your life harder refusing to use UEFI in my opinion.
Seconded.
Like I said, I honestly have no idea why that should be the case.
Because UEFI is safer and easier to use.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Lilo set-up to dual boot Slackware 12.2 with Slackware64 -current? hitest Slackware 19 08-10-2009 05:31 AM
Slackware64-current : can't have lilo updating the boot loader after kernel upgrade Didier Spaier Slackware 3 07-21-2009 08:00 AM
Slackware64-current ATI, and few more proprietary questions dolphin77 Slackware 15 06-10-2009 09:15 AM
Slackware64-current ATI, and few more proprietary questions dolphin77 Linux - Newbie 1 05-22-2009 06:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:22 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration