On Wed, 13 Jun 2018 00:58:09 -0400
Michael Shell wrote:
> IMHO, lilo had one particularly awful design decision and the resulting
> unexpected behavior was never explained to us as it should have been -
> lilo would *reinterpret* whatever the user specified for root= in terms
> of device
On Tue, 12 Jun 2018 10:28:26 -0500
Bruce Dubbs wrote:
> I don't think you can say that for all BIOS firmware, but it is
> certainly true for some.
I'm surprised by this, but you are correct here! According to
t13.org/Documents/UploadedDocuments/project/d1386r0-EDD.pdf
since 1999 BIOes have
On Tue, Jun 12, 2018 at 10:28:26AM -0500, Bruce Dubbs wrote:
> On 06/12/2018 12:43 AM, Michael Shell wrote:
>
> There are a lot of things that can go wrong when disk sector numbers are
> embedded into the code like lilo does. I do not know anything about the
> internals of elilo though.
>
On 06/12/2018 12:43 AM, Michael Shell wrote:
On Mon, 11 Jun 2018 23:20:51 -0500
Bruce Dubbs wrote:
What issues with GPT and legacy boot? Grub needs some space for it's
code that is OS independent. A separate small partition makes sense.
Putting the boot code in firmware is what does not
On Tue, 12 Jun 2018 14:25:48 +0800
Xi Ruoyao wrote:
> efibootmgr uses the library from efivar for /sys/firmware/efi/efivars.
> I searched "efivarfs" in the Github repo and found the commit to add
> efivarfs support:
>
On 2018-06-11 20:21 -0400, Michael Shell wrote:
> On Mon, 11 Jun 2018 23:13:29 +0800
> Xi Ruoyao wrote:
> > Now we use CONFIG_EFIVAR_FS (y or m), instead of CONFIG_EFI_VARS,
>
> Do you know if efibootmgr will autodetect (at run time) between the two kernel
> interfaces (and if this is a recent
On 2018-06-12 01:43 -0400, Michael Shell wrote:
> As I understand it, that is the policy of the kernel developers - a system
> might work in many cases, but it is not guaranteed and a future kernel
> update could break systems that rely on any fixed /dev/sd* naming. To me,
> this means that, until
On Mon, 11 Jun 2018 23:20:51 -0500
Bruce Dubbs wrote:
> What issues with GPT and legacy boot? Grub needs some space for it's
> code that is OS independent. A separate small partition makes sense.
> Putting the boot code in firmware is what does not make sense. And you
> still need a custom
On 06/11/2018 07:21 PM, Michael Shell wrote:
On Mon, 11 Jun 2018 21:24:08 +0800
niuneilneo wrote:
As you might guess, I'm not a big fan of grub. There is a reason it has been
said of grub by the gummiboot developers:
"gummiboot is intended to be a minimal alternative to GNU GRUB that
On Mon, 11 Jun 2018 21:24:08 +0800
niuneilneo wrote:
> This most updated UEFI installation guide is mainly contributed by Xi
> and already committed to LFS knowledge base.
That is a good one. I missed the importance of the earlier post to it.
Thanks for the tip!
But, my post was not about
On 2018-06-11 03:01 -0400, Michael Shell wrote:
> On Sun, 10 Jun 2018 07:27:53 -0500
> "Rob" wrote:
>
> > I just want to make sure this partition layout is correct before
> > doing grub.
>
> .
> .
> > DeviceStart End Sectors Size Type
> > /dev/sdb1 2048 1050623 1048576
On 06/10/2018 12:28 PM, Bruce Dubbs wrote:
On 06/10/2018 08:31 AM, Rob wrote:
Xi Ruoyao wrote:
LFS book does *not* support EFI. If you followed the book, you should
use "legacy boot" instead of EFI. And, since the partition table is
GPT, you should create a "BIOS boot partition" (in
Dear Michael,It is very nice of you by providing a very detailed instruction to install LFS on EFI booting environment. But I am afraid there is no need to re-invent the wheel, due to that there is a very complete guide for this purpose. This most updated UEFI installation guide is
On Mon, 11 Jun 2018 03:01:00 -0400
Michael Shell wrote:
> Your kernel will have to be compiled with an EFI stub.
I should have also stated here:
"*if* you want to boot directly using the EFI system and bypassing any
need for grub or other bootloader".
Mike
--
Quite interesting to store data on mobile esata box. Please remember to backup
important data periodically, because I have terrible experience for losing
crucial data on usb medias. niuneilneo 邮箱：niuneil...@gmail.com 签名由 网易邮箱大师 定制 On
06/11/2018 08:53, Rob wrote: Ken Moffat wrote: >>You
are
Ken Moffat wrote:
You are ignoring one important fact from Rob's original post - the
disk is only 37.3GB. To be honest, to me that looks barely usable
for storage (even with only one, probably never updated, system).
It works fine to run the system. And the system is CLI only.
The /home is on
On Mon, Jun 11, 2018 at 08:29:50AM +0800, lei niu wrote:
> I do not quite agree with Bruce on LFS main partition size. I give / about
> 50GB, and due to my laziness during LFS + BLFS installation process, this
> amount of partition is easily consumed after the gnome compilation. So my
>
I do not quite agree with Bruce on LFS main partition size. I give / about
50GB, and due to my laziness during LFS + BLFS installation process, this
amount of partition is easily consumed after the gnome compilation. So my
suggestion is: give as much space as you can to home partition, this
On 06/10/2018 08:31 AM, Rob wrote:
Xi Ruoyao wrote:
LFS book does *not* support EFI. If you followed the book, you should
use "legacy boot" instead of EFI. And, since the partition table is
GPT, you should create a "BIOS boot partition" (in section 2.4.1.3 of
LFS book) for it.
There is no
Xi Ruoyao wrote:
LFS book does *not* support EFI. If you followed the book, you should
use "legacy boot" instead of EFI. And, since the partition table is
GPT, you should create a "BIOS boot partition" (in section 2.4.1.3 of
LFS book) for it.
There is no such thing as legacy boot on this
On 2018-06-10 07:27 -0500, Rob wrote:
> I just want to make sure this partition layout is correct before
> doing grub.
> fdisk -l /dev/sdb
> Disk /dev/sdb: 37.3 GiB, 400 bytes, 78125000 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
I just want to make sure this partition layout is correct before
doing grub.
fdisk -l /dev/sdb
Disk /dev/sdb: 37.3 GiB, 400 bytes, 78125000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
22 matches
Mail list logo
