Date: Mon, 31 Dec 2018 19:45:11 +0100
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Eric Molitor <emolitor@molitor.org>
Cc: alpine-aports@lists.alpinelinux.org, Eric Molitor <eric@molitor.org>
Subject: Re: [alpine-aports] [PATCH] Initial commit of rEFInd package for
 alpine linux. - Includes patich to disable fortify headers when building
 libeg as nanojpeg.c uses custom efi allocators that were breaking.
Message-ID: <20181231184511.1CkSS%steffen@sdaoden.eu>
In-Reply-To: <20181231161318.8896-1-eric@molitor.org>
References: <20181231161318.8896-1-eric@molitor.org>
Mail-Followup-To: Eric Molitor <emolitor@molitor.org>,
 alpine-aports@lists.alpinelinux.org, Eric Molitor <eric@molitor.org>
User-Agent: s-nail v14.9.11-123-g49d1a5c2
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD;
 url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in
 the world can make no bugs.
Precedence: list

Eric Molitor wrote in <20181231161318.8896-1-eric@molitor.org>:
 |---
 | community/refind/APKBUILD                     | 30 +++++++++++++++++++
 | community/refind/refind-disable-fortify.patch | 11 +++++++
 | 2 files changed, 41 insertions(+)
 | create mode 100644 community/refind/APKBUILD
 | create mode 100644 community/refind/refind-disable-fortify.patch

Does this always work for you?  Once i put Alpine on the bare
metal of an old MacBook Air back in October/November, by sheer
luck, and because it is in my repo for a long time i put rEFIt

  -rw-r----- 1 steffen code 6823525 Mar  7  2010 /x/src/code/.rEFIt-0.14.dmg

first, otherwise we would have been, well, dead (booting from
USB is impossible for whatever reason, and i do not dare to touch
the firmware): even though the initial screen was there, it
failed to boot Linux.  Luckily the refit entry could be selected,
and with it i could, and still can boot.  In the meantime,
whatever might have changed, 0.11.3 could boot at least once
(i usually boot once a week only, and see rEFIt first).

I used to know that rEFIt has the same problem, but it is always
stunning that if you mess up the configuration file (especially
the boot order) the software will not fall back to some automatic
"just try to get the best out of it", but fails to start up.  This
configuration file parse problem includes busy loops which can
turn your computer into a toaster.  Maybe it has to be this way.
Other than that this works here for a decade.

(I am very lucky that the Acer just works with nothing but
Syslinux.  And now that i have finally and somehow could set bit
2 to gain the "legacy_boot" bit in the GPT partitioning of the
server, it is like that there, too!)

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---