| Newsgroups |
gmane.linux.lfs.book |
| Message-ID |
<[email protected]> |
#5819: UEFI support
-------------------------+-----------------------
Reporter: zeckma | Owner: lfs-book
Type: enhancement | Status: new
Priority: normal | Milestone: 12.5
Component: Book | Version: git
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by thomas):
**The boot loader**
> While I understand what your motivations are, I'm not sure that we
really need to do this.
It is not ''needed'' to do it but maybe it ''should'' be done. It looks
like that UEFI is the mechanism with which PCs are started nowadays. LFS
should support what is commonly required/used. The user can hardly deside
when a new PC is bought, so the book should switch from doing
* "BIOS and optionally UEFI"[[BR]]
that was when EFI was invented and was kinda exotic
to
* "UEFI and optionally BIOS"[[BR]]
now, EFI is in hardware with no choice for the users and the latter is
to support 'old' HW
> From the standpoint of UEFI, perhaps the easiest way to do an initial
boot is to not install GRUB at all, but to use what is installed for the
host unless you are going to have a dedicated bootable drive.
Yes, dropping the boot loader is indeed a possible option as most of the
people who are doing LFS, have one installed already. But without one, the
book is incomplete IMHO and therefore i'd tend to say that is not really a
good option. At least, BLFS must have a chapter covering boot loader oder
boot loaders since grub is not the only one.
**The "LFS/BLFS gap"**
This is a separate thread and has nothing to do with the boot loader and
therefore, a separate ticket might be opened for it.
> There are several issues regarding the transition from LFS to BLFS that
we don't address comprehensively. These include wireless connectivity and
dhcp.
>
> From my point of view sudo, wget (along with make-ca), and ssh are also
pretty critical packages. I did address all these issues in my article at
> https://anduin.linuxfromscratch.org/~bdubbs/external-lfs.
>
IMHO, there is no need to include dhcp nor ssh into LFS. User should be
able to select an unused IP address of the actual network. If a static IP
is provided, then LFS can do networking. But if required, dhcpcd isn't
that complex so it might be optional in LFS. Wireless is a tricky thing as
the host may have only wireless, so the freshly built LFS cannot use it.
The LFS book could state that a wired connection is required in the phase
from from booting into the new LFS until the wireless tools are built.
I think sudo is also not needed as the user has the tools (ch8:shadow) to
create an ordinary user and set its and root's password. When LFS is
booted, use one tty for the user, another tty for root. A third tty for
browsing in the BLFS book via lynx. That's all u need. Without sudo, it is
still possible to go on from LFS to BLFS.
> At a presentation I made a couple of weeks ago I was asked what a user
could do with a base LFS system. My answer was "Build more packages."
>
Which is - after a reboot as described in 11.3 - not true. It cannot be
used for that as it has no client to download anything in a sufficiently
comfortable way nor to read/browse the book(s). To build more packages,
you shouldn't leave the chroot env for a while until enough packages are
installed so that the new system can do downloads with ots own tools.
What LFS is really lacking is a (https-)client like wget, lynx, curl or
something. Not even bash can be used as the `--enable-net-
redirections`[https://stackoverflow.com/questions/7765004/tcp-connection-
bash-only ¹] is not given. wget or lynx seems to be simple packages for
networking (preferable lynx as it can be used to show the books after
reboot, too. wget can only download it). With them, the very next packages
after finishing and booting LFS can be downloaded. The LFS book could be
extended by a small chapter 10½ were some packages gets installed which
enables a booted LFS do download something from the internet. Those
packages (libtasn1, polkit, make-ca, wget) might be stripped down in terms
of dependencies and a clear note that those pkgs are only a vehicle for
the transition from LFS to BLFS and that they will be overwritten in BLFS.
They are in LFS only to enable a freshly booted LFS to go on with BLFS.
--
Ticket URL: <https://wiki.linuxfromscratch.org/lfs/ticket/5819#comment:2>
LFS Trac <https://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page