On 2015-08-26, James <wirel...@tampabay.rr.com> wrote:
> Alec Ten Harmsel <alec <at> alectenharmsel.com> writes:
>
>> > So some vintage installs/upgrades got me thinking. What does Grub-2
>> > offer that grub-1 does not. I cannot think of anything that I need
>> > from Grub-2 not mbr, nor efi board booting. Not dual/multi booting
>> > as grub-1 excels on that, and not on drives larger than 2 T.
>
>> > So what is the (hardware scenario) where grub-2 and it's problems
>> > are superior to grub-1? I'm having trouble thinking of that
>> > situation.......?
>
>> 64-bit hardware with the no-multilib profile[1]. I have no "-bin" packages
>> on my system, nor do I run any pre-built 3rd party applications, so I
>> waste no time compiling worthless 32-bit libraries. Therefore, I need
>> grub 2.
>
> Ok this is interesting. Is this only an AMD64 thing?
Yep. In theory the same thing could come up with respect to 64/32 bit
SPARC or something, but in practice it's ARM64
> On Arm64 you'd most likely want to run 32 bit binaries.
Some people do. Some people don't
> I'm OK with this, but what is the benefit of such profile selection::
> curiously I have no experience with the profile selection, despite
> running quite a few amd64 system. What would the benefits be
> running this profile on older amd64 hardware ?
The main benefit of ARM64 w/o 32-bit libs is that you can't run acroread.
;)
If only evince could "print current view", I could ditch acroread...
--
Grant Edwards grant.b.edwards Yow! What I need is a
at MATURE RELATIONSHIP with a
gmail.com FLOPPY DISK ...
