On 5/23/2017 4:43 PM, Ken Moffat wrote:
> On Tue, May 23, 2017 at 02:40:03PM -0600, Alan Feuerbacher wrote:
>>
>> However, I'm getting conceptually stuck at how to boot with my EFI
>> motherboard (Asus TUF Mark 1), using the lfs-uefi.txt hint mentioned
in the
>> LFS book, ch. 8.4.1.
SNIP
>> Two sticking points:
>>
>> 1. I assume that with my present setup, I should use /dev/sdd rather
than
>> /dev/sda, because I DON'T want to change the Fedora boot stuff.
Rather, I
>> want to be able to boot directly from the LFS disk. Ultimately, I
want to
>> use a boot manage like RodsBooks' rEFTnd (which I successfully installed
>> on /dev/sdb). And if I remove all disks, but /dev/sdd, I want to boot
>> directly from that.
>
> I think you are correct. The hint probably assumes one drive.
So far, I've gone with the assumption to install to /dev/sdd, apparently
successfully. But see below. Also, I have five disks installed, all
running and all with different Linuxes in various states, so I have to
be very careful keeping track of which disk is which.
>> 2. Do I use the LFS book's instructions on partitioning a strictly
MBR boot
>> setup, or make GPT partitions? See the information and discussion below.
>
> I think you have to use GPT partitions for UEFI.
That's what I've done now.
>> Here is my first cut at /etc/fstab for systemd on /dev/sdc:
>> # file system mount-point type options dump fsck
>> # order
>>
>> /dev/sdc4 / ext4 defaults 1 1
>> /dev/sdc3 /boot ext4 defaults 1 2
>> /dev/sdc1 /boot/efi vfat defaults 0 2
>> /dev/sdc5 /opt ext4 defaults 1 2
>> /dev/sdc6 /home ext4 defaults 1 2
>> /dev/sdc2 swap swap pri=1 0 0
>
> I think that looks reasonable.
Ok, here is the new one, after converting to GPT using gdisk:
/dev/sdd4 / ext4 defaults 1 1
/dev/sdd1 /boot/efi vfat defaults 0 1
/dev/sdd3 /boot ext4 defaults 1 2
efivarfs /sys/firmware/efi/efivars efivarfs defaults 0 1
/dev/sdd5 /opt ext4 defaults 1 2
/dev/sdd6 /home ext4 defaults 1 2
/dev/sdd2 swap swap pri=1 0 0
> Personally, I long-ago stopped giving /opt its own filesystem: if
> '/' is big enough, I can rename directories in /opt for testing a
> newer version.
Perhaps this can be included in the discussion of partitioning schemes
in the LFS book.
>> Question: has anyone on the LFS staff besides the authors (Dan
McGhee, Kevin
>> M. Buckley) gone through all this? I'm happy to be a guinea pig,
>> because I'm learning a lot.
>
> LOL. The phrase "staff" used to be used in BLFS - but who is paying
> us ?
Payment is perhaps the satisfaction of a job well done.
I suppose I could have reverted to my Long Island upbringing and said
"Youse LFS guys".
> I don't know for certain, but I suspect most of the editors
> have been able to disable UEFI on new machines. My personal opinion
> of UEFI is still "There be dragons."
That's for sure!
On this new machine of mine, I've disabled Secure Boot (had to remove a
Key) but I'm using UEFI boot, since disabling it means enabling the old
CSM Legacy boot in the Bios.
> I suspect I might have to learn more about it for my next machine.
I don't think we will have much choice, given that the industry is going
that way.
I'm thinking that in the long term, I might try installing LFS with
Secure Boot, ala the material in RodsBooks. The lfs-uefi.txt hint
mentions this as a good resource.
> No timescale for that, I started using gimp-2.9 on my photo-editing
> machine and discovered it was underpowered (2.9 seemed to only use 1
> core, and the xcf files are a lot bigger) - but meanwhile I'm using
> 2.8 on my development machine and that is ok. So for me there is no
> rush to get my first ryzen.
Well I had no choice, since my old Windows machine died, and I
repurposed the old Linux machine for Windows. Meanwhile I bought new
hardware for Linux, since I'm dumping Windows ASAP.
> I don't think Dan or Kevin have posted on the lists recently, so you
> are probably somewhat on your own.
Ok.
> Being a guinea pig can be fun,
> but less so if hardware gets damaged. So please think carefully
> about what you are doing at each step (but I imagine the worst thing
> is likely to be a trashed partition, which you can recreate from a
> working system such as fedora).
Already been there. Grub trashed my Fedora boot partition when I used it
wrongly first time around.
Apparently I messed up sending the above yesterday, so here it is again.
Sorry if it's a duplicate.
Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
