[gentoo-user] grub-0.97-r16 and profile 17.0 change

[gentoo-user] grub-0.97-r16 and profile 17.0 change

[Mick]

[-- Attachment #1: Type: text/plain, Size: 5363 bytes --]

I'm getting this error after I changed my profile as per '2017-11-30-new-17-
profiles' news item:

>>> Compiling source in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
grub-0.97 ...
make -j5 -l12.8
make  all-recursive
make[1]: Entering directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/
work/grub-0.97'
Making all in netboot
make[2]: Entering directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/
work/grub-0.97/netboot'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
grub-0.97/netboot'
Making all in stage2
make[2]: Entering directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/
work/grub-0.97/stage2'
x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I.. -I../stage1  -Wall -
Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-
loops=1 -falign-functions=1 -Wundef -Os -fno-stack-protector -nopie -fno-
strict-aliasing -march=i686 -fno-reorder-functions -fno-builtin -nostdinc  -
DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DSUPPORT_GRAPHICS=1 -DFSYS_EXT2FS=1 -
DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_UFS2=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -
DFSYS_VSTAFS=1 -DFSYS_JFS=1 -DFSYS_XFS=1 -DFSYS_ISO9660=1 -
DUSE_MD5_PASSWORDS=1 -DHAVE_CONFIG_H -I. -I.. -I../stage1 -Wall -Wmissing-
prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-loops=1 -
falign-functions=1 -Wundef -g -c -o pre_stage2_exec-asm.o `test -f 'asm.S' || 
echo './'`asm.S
x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I.. -I../stage1  -Wall -
Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-
loops=1 -falign-functions=1 -Wundef -Os -fno-stack-protector -nopie -fno-
strict-aliasing -march=i686 -fno-reorder-functions -fno-builtin -nostdinc  -
DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DSUPPORT_GRAPHICS=1 -DFSYS_EXT2FS=1 -
DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_UFS2=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -
DFSYS_VSTAFS=1 -DFSYS_JFS=1 -DFSYS_XFS=1 -DFSYS_ISO9660=1 -
DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-bios.o `test -f 'bios.c' || echo 
'./'`bios.c
x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I.. -I../stage1  -Wall -
Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-
loops=1 -falign-functions=1 -Wundef -Os -fno-stack-protector -nopie -fno-
strict-aliasing -march=i686 -fno-reorder-functions -fno-builtin -nostdinc  -
DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DSUPPORT_GRAPHICS=1 -DFSYS_EXT2FS=1 -
DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_UFS2=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -
DFSYS_VSTAFS=1 -DFSYS_JFS=1 -DFSYS_XFS=1 -DFSYS_ISO9660=1 -
DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-boot.o `test -f 'boot.c' || echo 
'./'`boot.c
x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I.. -I../stage1  -Wall -
Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-
loops=1 -falign-functions=1 -Wundef -Os -fno-stack-protector -nopie -fno-
strict-aliasing -march=i686 -fno-reorder-functions -fno-builtin -nostdinc  -
DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DSUPPORT_GRAPHICS=1 -DFSYS_EXT2FS=1 -
DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_UFS2=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -
DFSYS_VSTAFS=1 -DFSYS_JFS=1 -DFSYS_XFS=1 -DFSYS_ISO9660=1 -
DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-builtins.o `test -f 'builtins.c' 
|| echo './'`builtins.c
x86_64-pc-linux-gnu-gcc -m32 -DHAVE_CONFIG_H -I. -I.. -I../stage1  -Wall -
Wmissing-prototypes -Wunused -Wshadow -Wpointer-arith -falign-jumps=1 -falign-
loops=1 -falign-functions=1 -Wundef -Os -fno-stack-protector -nopie -fno-
strict-aliasing -march=i686 -fno-reorder-functions -fno-builtin -nostdinc  -
DSUPPORT_SERIAL=1 -DSUPPORT_HERCULES=1 -DSUPPORT_GRAPHICS=1 -DFSYS_EXT2FS=1 -
DFSYS_FAT=1 -DFSYS_FFS=1 -DFSYS_UFS2=1 -DFSYS_MINIX=1 -DFSYS_REISERFS=1 -
DFSYS_VSTAFS=1 -DFSYS_JFS=1 -DFSYS_XFS=1 -DFSYS_ISO9660=1 -
DUSE_MD5_PASSWORDS=1 -g -c -o pre_stage2_exec-char_io.o `test -f 'char_io.c' 
|| echo './'`char_io.c
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option ‘-nopie’; did 
you mean ‘-no-pie’?
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option ‘-nopie’; did 
you mean ‘-no-pie’?
make[2]: *** [Makefile:2878: pre_stage2_exec-bios.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [Makefile:2892: pre_stage2_exec-boot.o] Error 1
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option ‘-nopie’; did 
you mean ‘-no-pie’?
make[2]: *** [Makefile:2920: pre_stage2_exec-char_io.o] Error 1
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option ‘-nopie’; did 
you mean ‘-no-pie’?
make[2]: *** [Makefile:1492: pre_stage2_exec-asm.o] Error 1
x86_64-pc-linux-gnu-gcc: error: unrecognized command line option ‘-nopie’; did 
you mean ‘-no-pie’?
make[2]: *** [Makefile:2906: pre_stage2_exec-builtins.o] Error 1
make[2]: Leaving directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
grub-0.97/stage2'
make[1]: *** [Makefile:382: all-recursive] Error 1
make[1]: Leaving directory '/data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
grub-0.97'
make: *** [Makefile:323: all] Error 2


However, sys-boot/grub-0.97-r17 installed fine once keyworded on this (mostly) 
stable system.  This may save time for others who come across the same 
problem.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Ian Zimmerman]

This profile change seems to have hit a few people in sensitive
locations.

What is the upshot of this change?  Can I eyeball the diff _before_ I
sync ?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Mick]

On 02-12-2017 ,13:28:37, Ian Zimmerman wrote:
> This profile change seems to have hit a few people in sensitive
> locations.
> 
> What is the upshot of this change?  Can I eyeball the diff _before_ I
> sync ?

This is what the news item states:
=================================
~ $ eselect news read new
2017-11-30-new-17-profiles
  Title                     New 17.0 profiles in the Gentoo repository
  Author                    Andreas K. Hüttel <dilfridge@gentoo.org>
  Posted                    2017-11-30
  Revision                  1

We have just added (for all arches except arm and mips, these follow
later) a new set of profiles with release version 17.0 to the Gentoo
repository. These bring three changes:
1) The default C++ language version for applications is now C++14.
   This change is mostly relevant to Gentoo developers. It also
   means, however, that compilers earlier than GCC 6 are masked
   and not supported for use as a system compiler anymore. Feel
   free to unmask them if you need them for specific applications.
2) Where supported, GCC will now build position-independent
   executables (PIE) by default. This improves the overall
   security fingerprint. The switch from non-PIE to PIE binaries,
   however, requires some steps by users, as detailed below.
3) Up to now, hardened profiles were separate from the default
   profile tree. Now they are moving into the 17.0 profile
   as a feature there, similar to "no-multilib" and "systemd".

Please migrate away from the 13.0 profiles within the six weeks after
GCC 6.4.0 has been stabilized on your architecture. The 13.0 profiles
will be deprecated then and removed in half a year.

If you are not already running a hardened setup with PIE enabled, then
switching the profile involves the following steps:
If not already done,
* Use gcc-config to select gcc-6.4.0 or later as system compiler
* Re-source /etc/profile:
    . /etc/profile
* Re-emerge libtool
    emerge -1 sys-devel/libtool
Then,
* Select the new profile with eselect
* Re-emerge, in this sequence, gcc, binutils, and glibc
    emerge -1 sys-devel/gcc:6.4.0
    emerge -1 sys-devel/binutils
    emerge -1 sys-libs/glibc
* Rebuild your entire system
    emerge -e @world

Switching the profile from 13.0 to 17.0 modifies the settings of
GCC 6 to generate PIE executables by default; thus, you need to do
the rebuilds even if you have already used GCC 6 beforehand.
If you do not follow these steps you may get spurious build
failures when the linker tries unsuccessfully to combine non-PIE
and PIE code.
========================================

Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

> * Select the new profile with eselect
> * Re-emerge, in this sequence, gcc, binutils, and glibc
>     emerge -1 sys-devel/gcc:6.4.0
>     emerge -1 sys-devel/binutils
>     emerge -1 sys-libs/glibc
> * Rebuild your entire system
>     emerge -e @world
>

Would emerge -e --exclude gcc --exclude bintuils --exclude glibc @world be
a little more sensible?

[-- Attachment #2: Type: text/html, Size: 655 bytes --]

Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Michael Orlitzky]

On 12/02/2017 04:28 PM, Ian Zimmerman wrote:
> This profile change seems to have hit a few people in sensitive
> locations.
> 
> What is the upshot of this change?  Can I eyeball the diff _before_ I
> sync ?
> 

The new 17.0 profile switches the default C++ version to C++14, and
enables PIE/SSP by default with real upstream support for those
features. As a result, it requires gcc-6.x. Most build failures are due
to that -- basically ancient stable versions that never got tested with
a modern compiler/features until now.

Syncing is safe, nothing bad will happen unless you `eselect profile`
one of the new 17.0 profiles.

You're seeing a lot of reports because there is a news item telling
people to switch to the new profile and run "emerge -e @world".

Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Heiko Baums]

Am Sat, 2 Dec 2017 18:33:09 -0500
schrieb Michael Orlitzky <mjo@gentoo.org>:

> You're seeing a lot of reports because there is a news item telling
> people to switch to the new profile and run "emerge -e @world".

Does this mean that "emerge -e @world" should be run or that the news
item is wrong in this point?

Heiko

Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Michael Orlitzky]

On 12/02/2017 08:07 PM, Heiko Baums wrote:
> Am Sat, 2 Dec 2017 18:33:09 -0500
> schrieb Michael Orlitzky <mjo@gentoo.org>:
> 
>> You're seeing a lot of reports because there is a news item telling
>> people to switch to the new profile and run "emerge -e @world".
> 
> Does this mean that "emerge -e @world" should be run or that the news
> item is wrong in this point?

You do need to run "emerge -e @world", unless you happened to be using a
hardened toolchain already.

So the news item is correct, but having everyone build test the whole
tree at once is unearthing some latent build system bugs.

[gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Ian Zimmerman]

On 2017-12-02 20:14, Michael Orlitzky wrote:

> >> You're seeing a lot of reports because there is a news item telling
> >> people to switch to the new profile and run "emerge -e @world".
> > 
> > Does this mean that "emerge -e @world" should be run or that the
> > news item is wrong in this point?
> 
> You do need to run "emerge -e @world", unless you happened to be using
> a hardened toolchain already.

But only if you in fact switch the new profile on, right?

There seems to be another thing afoot, though.  All (or nearly so)
python libraries are due for rebuild because of

PYTHON_TARGETS="python3_5 -python3_4"

Where does that come from?  I have never fully understood this and
similar variables.  It seems to be kind of like USE but also separate
from USE.  Is it something I can control, as a user?  Where is it
configured?  Is this change tied to the above profile transition?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

Re: [gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Michael Orlitzky]

On 12/02/2017 09:18 PM, Ian Zimmerman wrote:
>>
>> You do need to run "emerge -e @world", unless you happened to be using
>> a hardened toolchain already.
> 
> But only if you in fact switch the new profile on, right?

Right.


> There seems to be another thing afoot, though.  All (or nearly so)
> python libraries are due for rebuild because of
> 
> PYTHON_TARGETS="python3_5 -python3_4"
> 
> Where does that come from?  I have never fully understood this and
> similar variables.  It seems to be kind of like USE but also separate
> from USE.  Is it something I can control, as a user?  Where is it
> configured?  Is this change tied to the above profile transition?

Totally unrelated. PYTHON_TARGETS is a so-called USE_EXPAND variable:

  https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS

It is precisely a bunch of plain-old USE flags under the hood, with a
little bit of syntactic sugar on top so that you can set e.g.

  PYTHON_TARGETS=python3_5

instead of

  USE=python_targets_python3_5

In other words, it automatically namespaces a set of related USE flags.

All of the python stuff is rebuilding because (I guess) the python team
stabilized python-3.5. As a result, you're going to install python-3.5,
and therefore need to rebuild all of your python packages with support
for python-3.5.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Peter Humphrey]

On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
> I'm getting this error after I changed my profile as per
> '2017-11-30-new-17-
> profiles' news item:
> >>> Compiling source in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/

[...]

> However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
> (mostly) stable system.  This may save time for others who come across
> the same problem.

It has. Thanks Mick.

-- 
Regards,
Peter.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Mick]

On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
> > I'm getting this error after I changed my profile as per
> > '2017-11-30-new-17-
> > profiles' news item:
> > >>> Compiling source in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
> 
> [...]
> 
> > However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
> > (mostly) stable system.  This may save time for others who come across
> > the same problem.
> 
> It has. Thanks Mick.
> 
> -- 
> Regards,
> Peter.

Unfortunately, an older system with only 50MB /boot partition did not
have enough space to allow sys-boot/grub-0.97-r17 to install all its
files and fs drivers.  I ended up restoring /boot from a back up.  YMMV.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Daniel Frey]

On 12/03/17 07:12, Mick wrote:
> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
>> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
>>> I'm getting this error after I changed my profile as per
>>> '2017-11-30-new-17-
>>> profiles' news item:
>>>>>> Compiling source in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
>>
>> [...]
>>
>>> However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
>>> (mostly) stable system.  This may save time for others who come across
>>> the same problem.
>>
>> It has. Thanks Mick.
>>
>> -- 
>> Regards,
>> Peter.
> 
> Unfortunately, an older system with only 50MB /boot partition did not
> have enough space to allow sys-boot/grub-0.97-r17 to install all its
> files and fs drivers.  I ended up restoring /boot from a back up.  YMMV.
> 

I have a 250MB /boot partition and have the same problem, and I only 
have one kernel installed at ~5MB.

I wonder how much space it needs in total now...

Dan

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Daniel Frey]

On 12/04/17 17:54, Daniel Frey wrote:
> On 12/03/17 07:12, Mick wrote:
>> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
>>> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
>>>> I'm getting this error after I changed my profile as per
>>>> '2017-11-30-new-17-
>>>> profiles' news item:
>>>>>>> Compiling source in 
>>>>>>> /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
>>>
>>> [...]
>>>
>>>> However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
>>>> (mostly) stable system.  This may save time for others who come across
>>>> the same problem.
>>>
>>> It has. Thanks Mick.
>>>
>>> -- 
>>> Regards,
>>> Peter.
>>
>> Unfortunately, an older system with only 50MB /boot partition did not
>> have enough space to allow sys-boot/grub-0.97-r17 to install all its
>> files and fs drivers.  I ended up restoring /boot from a back up.  YMMV.
>>
> 
> I have a 250MB /boot partition and have the same problem, and I only 
> have one kernel installed at ~5MB.
> 
> I wonder how much space it needs in total now...
> 
> Dan
	
To answer my own question:

Well, it copies from /usr/share/grub and /lib/grub to /boot/grub, and 
the sum of those directories are 270M without any kernels, etc 
installed. I guess I'm going to have to tarball everything up, 
repartition, and untar it.

I guess I'll have to remember to use 500M+ /boot partitions now. Sigh.

Dan

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Michael Orlitzky]

On 12/04/2017 09:13 PM, Daniel Frey wrote:
> 
> Well, it copies from /usr/share/grub and /lib/grub to /boot/grub, and 
> the sum of those directories are 270M without any kernels, etc 
> installed. I guess I'm going to have to tarball everything up, 
> repartition, and untar it.
> 
> I guess I'll have to remember to use 500M+ /boot partitions now. Sigh.
> 

Before you do all that, some people on the bug have reported that the
larger binaries are busted and won't boot.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Daniel Frey]

On 12/04/17 18:15, Michael Orlitzky wrote:
> On 12/04/2017 09:13 PM, Daniel Frey wrote:
>>
>> Well, it copies from /usr/share/grub and /lib/grub to /boot/grub, and
>> the sum of those directories are 270M without any kernels, etc
>> installed. I guess I'm going to have to tarball everything up,
>> repartition, and untar it.
>>
>> I guess I'll have to remember to use 500M+ /boot partitions now. Sigh.
>>
> 
> Before you do all that, some people on the bug have reported that the
> larger binaries are busted and won't boot.
> 
> 
> 

I can confirm that: right after I posted, I rebooted and all hell broke 
loose. I just got booted up again (I'd already removed gcc-5) using grub2.

I was genuinely annoyed with grub2 due to its update and massive config 
files, so I never upgraded to it. I usually had multiple kernel versions 
and grub2 helpfully labeled them all "Linux" so I couldn't tell them apart.

I figured out you can still write your own grub2 files, and it wasn't 
that difficult, other than its numbering is different now (no base-0 
partitions... argh.)

Below is an example of a simple grub.cfg that starts two separate 
kernels (I use a different kernel/partition for MythTV) and a 
chainloader for Windows 7. It took a few iterations for me to get 
everything to boot.

My partitions are as follows:
/dev/sda1: Windows tiny partition, the bootable one
/dev/sda2: Windows 7
/dev/sda3: /boot

As you can see, there's no base-0 counted partitions in the config, that 
messed me up more than once.

I also used PARTUUID for the root= parameter, you can get this by using 
`blkid /dev/sdaX`. Also, don't encapsulate your PARTUUID in quotes, that 
didn't work for me. I simply had (as an example) 
root=PARTUUID=abcdef33-01 and it boots fine.

It was simple enough to convert (and grub-2.02 actually compiles fine 
with gcc-6 and the new profile) and figured others were probably like me 
and avoiding the grub2 config mess.

At least now I know how to configure grub2 manually and simply, so I 
won't avoid it any more.

Dan

------grub.cfg------
timeout=10
default=0

menuentry 'Gentoo 4.1.43-r1' {
         root=hd0,3
         linux /boot/kernel-4.1.43-gentoo-r1 root=PARTUUID=<your 
PARTUUID> quiet rootfstype=ext4
}

menuentry 'Gentoo - MythTV' {
         root=hd0,3
         linux /boot/kernel-4.1.43-gentoo-r1-mythtv root=PARTUUID=<your 
PARTUUID> quiet rootfstype=ext4
}


menuentry "Windows 7" {
         set root=(hd0,1)
         chainloader +1
         boot
}
--------------------

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Peter Humphrey]

On Tuesday, 5 December 2017 03:39:42 GMT Daniel Frey wrote:

> I figured out you can still write your own grub2 files, and it wasn't
> that difficult, other than its numbering is different now (no base-0
> partitions... argh.)

How a developer can number disks from 0 and partitions from 1 and expect 
anyone to take them seriously beats me.

-- 
Regards,
Peter.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Tom H]

On Mon, Dec 4, 2017 at 10:39 PM, Daniel Frey <djqfrey@gmail.com> wrote:
>
> I was genuinely annoyed with grub2 due to its update and massive config
> files, so I never upgraded to it. I usually had multiple kernel versions and
> grub2 helpfully labeled them all "Linux" so I couldn't tell them apart.
>
> I figured out you can still write your own grub2 files, and it wasn't that
> difficult, other than its numbering is different now (no base-0
> partitions... argh.)

You can use

search --no-floppy --fs-uuid --set=root filesystem_uuid

instead of

root=(hdX,msdosY)

and avoid having to deal with the grub1 to grub2 change of disks
starting at 0 and partitions at 1. Why the grub developers didn't make
disks to start at 1 when they made the partitions start at 1 is a
mystery. Maybe we'll be surprised in a future grub3 :)

[gentoo-user] Re: grub-0.97-r16 and profile 17.0 change

[Ian Zimmerman]

On 2017-12-04 18:13, Daniel Frey wrote:

> I guess I'll have to remember to use 500M+ /boot partitions now. Sigh.

I don't get it.

 matica!7 rc$ du /boot/grub
2022	/boot/grub/i386-pc
1340	/boot/grub/fonts
2785	/boot/grub/themes/starfield
2786	/boot/grub/themes
3163	/boot/grub/locale
9317	/boot/grub

~10MB.  This is with grub2.

Maybe you use some heavily graphical theme?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet, fetch the TXT record for the domain.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[wabe]

Daniel Frey <djqfrey@gmail.com> wrote:

> On 12/03/17 07:12, Mick wrote:
> > On 03-12-2017 ,10:57:33, Peter Humphrey wrote:  
> >> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:  
> >>> I'm getting this error after I changed my profile as per
> >>> '2017-11-30-new-17-
> >>> profiles' news item:  
> >>>>>> Compiling source
> >>>>>> in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/  
> >>
> >> [...]
> >>  
> >>> However, sys-boot/grub-0.97-r17 installed fine once keyworded on
> >>> this (mostly) stable system.  This may save time for others who
> >>> come across the same problem.  
> >>
> >> It has. Thanks Mick.
> >>  
> >> -- >> Regards,  
> >> Peter.
> > > Unfortunately, an older system with only 50MB /boot partition did
> > > not  
> > have enough space to allow sys-boot/grub-0.97-r17 to install all its
> > files and fs drivers.  I ended up restoring /boot from a back up.
> > YMMV. I have a 250MB /boot partition and have the same problem, and
> > I only have one kernel installed at ~5MB.  
> 
> I wonder how much space it needs in total now...
> 
> Dan

I'm using a hardened system with grub-0.97-r16 and have a 93MB boot 
partition. It contains eight kernels each about 6.7MB in size and the 
associated System.map files each about 2.2MB in size and I have still 
13MB free space in boot. 

How could this be?

--
Regards
wabe

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Mick]

[-- Attachment #1: Type: text/plain, Size: 3667 bytes --]

On Tuesday, 5 December 2017 02:20:14 GMT wabe wrote:
> Daniel Frey <djqfrey@gmail.com> wrote:
> > On 12/03/17 07:12, Mick wrote:
> > > On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
> > >> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
> > >>> I'm getting this error after I changed my profile as per
> > >>> '2017-11-30-new-17-
> > >>> 
> > >>> profiles' news item:
> > >>>>>> Compiling source
> > >>>>>> in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
> > >> 
> > >> [...]
> > >> 
> > >>> However, sys-boot/grub-0.97-r17 installed fine once keyworded on
> > >>> this (mostly) stable system.  This may save time for others who
> > >>> come across the same problem.
> > >> 
> > >> It has. Thanks Mick.
> > >> 
> > >> -- >> Regards,
> > >> Peter.
> > >> 
> > > > Unfortunately, an older system with only 50MB /boot partition did
> > > > not
> > > 
> > > have enough space to allow sys-boot/grub-0.97-r17 to install all its
> > > files and fs drivers.  I ended up restoring /boot from a back up.
> > > YMMV. I have a 250MB /boot partition and have the same problem, and
> > > I only have one kernel installed at ~5MB.
> > 
> > I wonder how much space it needs in total now...
> > 
> > Dan
> 
> I'm using a hardened system with grub-0.97-r16 and have a 93MB boot
> partition. It contains eight kernels each about 6.7MB in size and the
> associated System.map files each about 2.2MB in size and I have still
> 13MB free space in boot.
> 
> How could this be?
> 
> --
> Regards
> wabe

Quite inexplicable ... 

My kernel is 7.1M, System.map 3.4M and config is 114K.  I usually leave a 
total of three kernels and associated files in my ext2 46M /boot partition and 
they all used to fit in there.  I tried to install grub-0.97-r16 on this 
system a number of times, each time removing another spare kernel until I was 
left with the latest kernel and each time it failed to install completely due 
to running out of disk space.

These are the contents of my old /boot/grub/ as restored from a back up:

# ls -la /boot/grub/
total 1958
drwxr-xr-x 2 root root    1024 Dec  3 14:07 .
drwxr-xr-x 4 root root    1024 Dec  3 11:58 ..
-rw-r--r-- 1 root root   12506 Nov 27  2016 ascii.h
-rw-r--r-- 1 root root    5000 Nov 27  2016 ascii.pf2
-rw-r--r-- 1 root root     197 Feb 27  2010 default
-rw-r--r-- 1 root root      30 Feb 27  2010 device.map
-rw-r--r-- 1 root root   10036 Dec 10  2016 e2fs_stage1_5
-rw-r--r-- 1 root root   52151 Nov 27  2016 euro.pf2
-rw-r--r-- 1 root root    9236 Dec 10  2016 fat_stage1_5
-rw-r--r-- 1 root root    8564 Dec 10  2016 ffs_stage1_5
-rw-r--r-- 1 root root    8947 Nov 27  2016 grub-mkconfig_lib
-rw-r--r-- 1 root root     809 Dec  3 14:07 grub.conf
-rw-r--r-- 1 root root    8564 Dec 10  2016 iso9660_stage1_5
-rw-r--r-- 1 root root   10208 Dec 10  2016 jfs_stage1_5
lrwxrwxrwx 1 root root       9 Feb 27  2010 menu.lst -> grub.conf
-rw-r--r-- 1 root root    8724 Dec 10  2016 minix_stage1_5
-rw-r--r-- 1 root root   11252 Dec 10  2016 reiserfs_stage1_5
-rw-r--r-- 1 root root   33856 Dec 10  2016 splash.xpm.gz
-rw-r--r-- 1 root root     512 Dec 10  2016 stage1
-rw-r--r-- 1 root root  118712 Dec 10  2016 stage2
-rw-r--r-- 1 root root  118712 Dec 20  2015 stage2.old
-rw-r--r-- 1 root root  118712 Dec 10  2016 stage2_eltorito
-rw-r--r-- 1 root root    8852 Dec 10  2016 ufs2_stage1_5
-rw-r--r-- 1 root root 1363292 Nov 27  2016 unicode.pf2
-rw-r--r-- 1 root root    8212 Dec 10  2016 vstafs_stage1_5
-rw-r--r-- 1 root root   49238 Nov 27  2016 widthspec.h
-rw-r--r-- 1 root root   10874 Dec 10  2016 xfs_stage1_5

Installing grub-0.97-r16 would run out of disk space while trying to copy the 
stage2 file.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Raffaele Belardi]

Mick wrote:
> 
> Quite inexplicable ... 
> 
> My kernel is 7.1M, System.map 3.4M and config is 114K.  I usually leave a 
> total of three kernels and associated files in my ext2 46M /boot partition and 
> they all used to fit in there.  I tried to install grub-0.97-r16 on this 
> system a number of times, each time removing another spare kernel until I was 
> left with the latest kernel and each time it failed to install completely due 
> to running out of disk space.
> 
> These are the contents of my old /boot/grub/ as restored from a back up:
> 
> # ls -la /boot/grub/
> total 1958
> drwxr-xr-x 2 root root    1024 Dec  3 14:07 .
> drwxr-xr-x 4 root root    1024 Dec  3 11:58 ..
> -rw-r--r-- 1 root root   12506 Nov 27  2016 ascii.h
> -rw-r--r-- 1 root root    5000 Nov 27  2016 ascii.pf2
> -rw-r--r-- 1 root root     197 Feb 27  2010 default
> -rw-r--r-- 1 root root      30 Feb 27  2010 device.map
> -rw-r--r-- 1 root root   10036 Dec 10  2016 e2fs_stage1_5
> -rw-r--r-- 1 root root   52151 Nov 27  2016 euro.pf2
> -rw-r--r-- 1 root root    9236 Dec 10  2016 fat_stage1_5
> -rw-r--r-- 1 root root    8564 Dec 10  2016 ffs_stage1_5
> -rw-r--r-- 1 root root    8947 Nov 27  2016 grub-mkconfig_lib
> -rw-r--r-- 1 root root     809 Dec  3 14:07 grub.conf
> -rw-r--r-- 1 root root    8564 Dec 10  2016 iso9660_stage1_5
> -rw-r--r-- 1 root root   10208 Dec 10  2016 jfs_stage1_5
> lrwxrwxrwx 1 root root       9 Feb 27  2010 menu.lst -> grub.conf
> -rw-r--r-- 1 root root    8724 Dec 10  2016 minix_stage1_5
> -rw-r--r-- 1 root root   11252 Dec 10  2016 reiserfs_stage1_5
> -rw-r--r-- 1 root root   33856 Dec 10  2016 splash.xpm.gz
> -rw-r--r-- 1 root root     512 Dec 10  2016 stage1
> -rw-r--r-- 1 root root  118712 Dec 10  2016 stage2
> -rw-r--r-- 1 root root  118712 Dec 20  2015 stage2.old
> -rw-r--r-- 1 root root  118712 Dec 10  2016 stage2_eltorito
> -rw-r--r-- 1 root root    8852 Dec 10  2016 ufs2_stage1_5
> -rw-r--r-- 1 root root 1363292 Nov 27  2016 unicode.pf2
> -rw-r--r-- 1 root root    8212 Dec 10  2016 vstafs_stage1_5
> -rw-r--r-- 1 root root   49238 Nov 27  2016 widthspec.h
> -rw-r--r-- 1 root root   10874 Dec 10  2016 xfs_stage1_5
> 
> Installing grub-0.97-r16 would run out of disk space while trying to copy the 
> stage2 file.
> 

Could it be that you ran out of inodes on the /boot partition? Have you tried
# du -i
on /boot?

raffaele

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2855 bytes --]

On Tuesday, 5 December 2017 10:21:49 GMT Raffaele Belardi wrote:
> Mick wrote:
> > Quite inexplicable ...
> > 
> > My kernel is 7.1M, System.map 3.4M and config is 114K.  I usually leave a
> > total of three kernels and associated files in my ext2 46M /boot partition
> > and they all used to fit in there.  I tried to install grub-0.97-r16 on
> > this system a number of times, each time removing another spare kernel
> > until I was left with the latest kernel and each time it failed to
> > install completely due to running out of disk space.
> > 
> > These are the contents of my old /boot/grub/ as restored from a back up:
> > 
> > # ls -la /boot/grub/
> > total 1958
> > drwxr-xr-x 2 root root    1024 Dec  3 14:07 .
> > drwxr-xr-x 4 root root    1024 Dec  3 11:58 ..
> > -rw-r--r-- 1 root root   12506 Nov 27  2016 ascii.h
> > -rw-r--r-- 1 root root    5000 Nov 27  2016 ascii.pf2
> > -rw-r--r-- 1 root root     197 Feb 27  2010 default
> > -rw-r--r-- 1 root root      30 Feb 27  2010 device.map
> > -rw-r--r-- 1 root root   10036 Dec 10  2016 e2fs_stage1_5
> > -rw-r--r-- 1 root root   52151 Nov 27  2016 euro.pf2
> > -rw-r--r-- 1 root root    9236 Dec 10  2016 fat_stage1_5
> > -rw-r--r-- 1 root root    8564 Dec 10  2016 ffs_stage1_5
> > -rw-r--r-- 1 root root    8947 Nov 27  2016 grub-mkconfig_lib
> > -rw-r--r-- 1 root root     809 Dec  3 14:07 grub.conf
> > -rw-r--r-- 1 root root    8564 Dec 10  2016 iso9660_stage1_5
> > -rw-r--r-- 1 root root   10208 Dec 10  2016 jfs_stage1_5
> > lrwxrwxrwx 1 root root       9 Feb 27  2010 menu.lst -> grub.conf
> > -rw-r--r-- 1 root root    8724 Dec 10  2016 minix_stage1_5
> > -rw-r--r-- 1 root root   11252 Dec 10  2016 reiserfs_stage1_5
> > -rw-r--r-- 1 root root   33856 Dec 10  2016 splash.xpm.gz
> > -rw-r--r-- 1 root root     512 Dec 10  2016 stage1
> > -rw-r--r-- 1 root root  118712 Dec 10  2016 stage2
> > -rw-r--r-- 1 root root  118712 Dec 20  2015 stage2.old
> > -rw-r--r-- 1 root root  118712 Dec 10  2016 stage2_eltorito
> > -rw-r--r-- 1 root root    8852 Dec 10  2016 ufs2_stage1_5
> > -rw-r--r-- 1 root root 1363292 Nov 27  2016 unicode.pf2
> > -rw-r--r-- 1 root root    8212 Dec 10  2016 vstafs_stage1_5
> > -rw-r--r-- 1 root root   49238 Nov 27  2016 widthspec.h
> > -rw-r--r-- 1 root root   10874 Dec 10  2016 xfs_stage1_5
> > 
> > Installing grub-0.97-r16 would run out of disk space while trying to copy
> > the stage2 file.
> 
> Could it be that you ran out of inodes on the /boot partition? Have you
> tried # du -i
> on /boot?
> 
> raffaele

The restored from backup /boot shows enough inodes:

# df -i /dev/sda10
Filesystem     Inodes IUsed IFree IUse% Mounted on
/dev/sda10      12048    42 12006    1% /boot

# du --inodes /boot
1	/boot/lost+found
26	/boot/grub
33	/boot

I think there are enough inodes in the partition, but apparently not enough 
space. 
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[wabe]

Mick <michaelkintzios@gmail.com> wrote:

> On Tuesday, 5 December 2017 02:20:14 GMT wabe wrote:
> > Daniel Frey <djqfrey@gmail.com> wrote:  
> > > On 12/03/17 07:12, Mick wrote:  
> > > > On 03-12-2017 ,10:57:33, Peter Humphrey wrote:  
> > > >> On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:  
> > > >>> I'm getting this error after I changed my profile as per
> > > >>> '2017-11-30-new-17-
> > > >>> 
> > > >>> profiles' news item:  
> > > >>>>>> Compiling source
> > > >>>>>> in /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/  
> > > >> 
> > > >> [...]
> > > >>   
> > > >>> However, sys-boot/grub-0.97-r17 installed fine once keyworded
> > > >>> on this (mostly) stable system.  This may save time for
> > > >>> others who come across the same problem.  
> > > >> 
> > > >> It has. Thanks Mick.
> > > >>   
> > > >> -- >> Regards,  
> > > >> Peter.
> > > >> 
> > > > > Unfortunately, an older system with only 50MB /boot partition
> > > > > did not  
> > > > 
> > > > have enough space to allow sys-boot/grub-0.97-r17 to install
> > > > all its files and fs drivers.  I ended up restoring /boot from
> > > > a back up. YMMV. I have a 250MB /boot partition and have the
> > > > same problem, and I only have one kernel installed at ~5MB.  
> > > 
> > > I wonder how much space it needs in total now...
> > > 
> > > Dan  
> > 
> > I'm using a hardened system with grub-0.97-r16 and have a 93MB boot
> > partition. It contains eight kernels each about 6.7MB in size and
> > the associated System.map files each about 2.2MB in size and I have
> > still 13MB free space in boot.
> > 
> > How could this be?
> > 
> > --
> > Regards
> > wabe  
> 
> Quite inexplicable ... 
> 
> My kernel is 7.1M, System.map 3.4M and config is 114K.  I usually
> leave a total of three kernels and associated files in my ext2
> 46M /boot partition and they all used to fit in there.  I tried to
> install grub-0.97-r16 on this system a number of times, each time
> removing another spare kernel until I was left with the latest kernel
> and each time it failed to install completely due to running out of
> disk space.
> 
> These are the contents of my old /boot/grub/ as restored from a back
> up:
> 
> # ls -la /boot/grub/
> total 1958
> drwxr-xr-x 2 root root    1024 Dec  3 14:07 .
> drwxr-xr-x 4 root root    1024 Dec  3 11:58 ..
> -rw-r--r-- 1 root root   12506 Nov 27  2016 ascii.h
> -rw-r--r-- 1 root root    5000 Nov 27  2016 ascii.pf2
> -rw-r--r-- 1 root root     197 Feb 27  2010 default
> -rw-r--r-- 1 root root      30 Feb 27  2010 device.map
> -rw-r--r-- 1 root root   10036 Dec 10  2016 e2fs_stage1_5
> -rw-r--r-- 1 root root   52151 Nov 27  2016 euro.pf2
> -rw-r--r-- 1 root root    9236 Dec 10  2016 fat_stage1_5
> -rw-r--r-- 1 root root    8564 Dec 10  2016 ffs_stage1_5
> -rw-r--r-- 1 root root    8947 Nov 27  2016 grub-mkconfig_lib
> -rw-r--r-- 1 root root     809 Dec  3 14:07 grub.conf
> -rw-r--r-- 1 root root    8564 Dec 10  2016 iso9660_stage1_5
> -rw-r--r-- 1 root root   10208 Dec 10  2016 jfs_stage1_5
> lrwxrwxrwx 1 root root       9 Feb 27  2010 menu.lst -> grub.conf
> -rw-r--r-- 1 root root    8724 Dec 10  2016 minix_stage1_5
> -rw-r--r-- 1 root root   11252 Dec 10  2016 reiserfs_stage1_5
> -rw-r--r-- 1 root root   33856 Dec 10  2016 splash.xpm.gz
> -rw-r--r-- 1 root root     512 Dec 10  2016 stage1
> -rw-r--r-- 1 root root  118712 Dec 10  2016 stage2
> -rw-r--r-- 1 root root  118712 Dec 20  2015 stage2.old
> -rw-r--r-- 1 root root  118712 Dec 10  2016 stage2_eltorito
> -rw-r--r-- 1 root root    8852 Dec 10  2016 ufs2_stage1_5
> -rw-r--r-- 1 root root 1363292 Nov 27  2016 unicode.pf2
> -rw-r--r-- 1 root root    8212 Dec 10  2016 vstafs_stage1_5
> -rw-r--r-- 1 root root   49238 Nov 27  2016 widthspec.h
> -rw-r--r-- 1 root root   10874 Dec 10  2016 xfs_stage1_5
> 
> Installing grub-0.97-r16 would run out of disk space while trying to
> copy the stage2 file.


Strange, indeed. 

# ls -alh /boot/grub/
total 505K
drwxr-xr-x 2 root root 1,0K 22. Nov 03:51 .
dr-x------ 4 root root 1,0K 22. Okt 20:51 ..
-rw-r--r-- 1 root root  197  7. Dez 2016  default
-rw-r--r-- 1 root root   15 28. Dez 2014  device.map
-rw-r--r-- 1 root root  11K 26. Apr 2017  e2fs_stage1_5
-rw-r--r-- 1 root root 9,3K 26. Apr 2017  fat_stage1_5
-rw-r--r-- 1 root root 8,7K 26. Apr 2017  ffs_stage1_5
-rw------- 1 root root 7,9K  4. Mär 2014  grub.cfg
-rw-r--r-- 1 root root  514 22. Nov 03:50 grub.conf
-rw-r--r-- 1 root root 8,7K 26. Apr 2017  iso9660_stage1_5
-rw-r--r-- 1 root root  11K 26. Apr 2017  jfs_stage1_5
lrwxrwxrwx 1 root root    9 11. Mär 2012  menu.lst -> grub.conf
-rw-r--r-- 1 root root 8,9K 26. Apr 2017  minix_stage1_5
-rw-r--r-- 1 root root  12K 26. Apr 2017  reiserfs_stage1_5
-rw-r--r-- 1 root root  34K 26. Apr 2017  splash.xpm.gz
-rw-r--r-- 1 root root  512 26. Apr 2017  stage1
-rw-r--r-- 1 root root 119K 26. Apr 2017  stage2
-rw-r--r-- 1 root root 119K 26. Apr 2017  stage2_eltorito
-rw-r--r-- 1 root root 119K  7. Dez 2016  stage2.old
-rw-r--r-- 1 root root 8,9K 26. Apr 2017  ufs2_stage1_5
-rw-r--r-- 1 root root 8,3K 26. Apr 2017  vstafs_stage1_5
-rw-r--r-- 1 root root  11K 26. Apr 2017  xfs_stage1_5

$ eix sys-boot/grub
[I] sys-boot/grub
     Available versions:  
     (0)    0.97-r16{tbz2} ~0.97-r17
     (2)    [m]2.02(2/2.02)^st [m]**9999(2/9999)^st
       {custom-cflags debug device-mapper doc efiemu +fonts libzfs mount multislot ncurses netboot nls sdl static test +themes truetype GRUB_PLATFORMS="coreboot efi-32 efi-64 emu ieee1275 loongson multiboot pc qemu qemu-mips uboot xen xen-32"}
     Installed versions:  0.97-r16{tbz2}(09:05:23 26.04.2017)(ncurses -custom-cflags -netboot -static)
     Homepage:            https://www.gnu.org/software/grub/
     Description:         GNU GRUB boot loader

* sys-boot/grub-static
     Available versions:  0.96-r1 0.97 0.97-r6 0.97-r9 0.97-r10 0.97-r12
     Homepage:            https://www.gnu.org/software/grub/
     Description:         GNU GRUB Legacy boot loader (static build)

Found 2 matches

--
Regards
wabe

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Peter Humphrey]

On Sunday, 3 December 2017 15:12:21 GMT Mick wrote:
> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
> > On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
> > > I'm getting this error after I changed my profile as per
> > > '2017-11-30-new-17-
> > > 
> > > profiles' news item:
> > > >>> Compiling source in
> > > >>> /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
> > 
> > [...]
> > 
> > > However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
> > > (mostly) stable system.  This may save time for others who come across
> > > the same problem.
> > sys-boot/grub-0.97-r17
> > It has. Thanks Mick.
> 
> Unfortunately, an older system with only 50MB /boot partition did not
> have enough space to allow sys-boot/grub-0.97-r17 to install all its
> files and fs drivers.  I ended up restoring /boot from a back up.  YMMV.

I spoke too soon, too. Sys-boot/grub-0.97-r17 compiled and installed all 
right, as a package, but when I went to install it to the MBR I got an error 
complaining of a mismatch or corruption in stage X. The wording was 
something like that, and I forget the value of X. There was no mention of 
disk space, and the boot partition is 2GB, so I think it's something else.

Installing sys-boot/grub-static-0.97-r12 instead went smoothly, so I've left 
it like that for the moment.

Does the team think I should go back to grub-0.97-r17, take proper records 
and file a bug report?

-- 
Regards,
Peter.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Kai Peter]

On 2017-12-06 13:28, Peter Humphrey wrote:
> On Sunday, 3 December 2017 15:12:21 GMT Mick wrote:
>> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
>> > On Saturday, 2 December 2017 12:30:57 GMT Mick wrote:
>> > > I'm getting this error after I changed my profile as per
>> > > '2017-11-30-new-17-
>> > >
>> > > profiles' news item:
>> > > >>> Compiling source in
>> > > >>> /data/tmp_var/portage/sys-boot/grub-0.97-r16/work/
>> >
>> > [...]
>> >
>> > > However, sys-boot/grub-0.97-r17 installed fine once keyworded on this
>> > > (mostly) stable system.  This may save time for others who come across
>> > > the same problem.
>> > sys-boot/grub-0.97-r17
>> > It has. Thanks Mick.
>> 
>> Unfortunately, an older system with only 50MB /boot partition did not
>> have enough space to allow sys-boot/grub-0.97-r17 to install all its
>> files and fs drivers.  I ended up restoring /boot from a back up.  
>> YMMV.
> 
> I spoke too soon, too. Sys-boot/grub-0.97-r17 compiled and installed 
> all
> right, as a package, but when I went to install it to the MBR I got an 
> error
> complaining of a mismatch or corruption in stage X. The wording was
> something like that, and I forget the value of X. There was no mention 
> of
> disk space, and the boot partition is 2GB, so I think it's something 
> else.
> 
> Installing sys-boot/grub-static-0.97-r12 instead went smoothly, so I've 
> left
> it like that for the moment.
> 
> Does the team think I should go back to grub-0.97-r17, take proper 
> records
> and file a bug report?

I question if this makes sense for a masked ebuild.

I'm curious about what was discussed until now. The issue seems to be 
quite simple to solve.

The build fails but portage/gcc does give clear info in this case: the 
option "-nopie" have to be changed to "-no-pie". This option is set in 
860_all_grub-0.97-pie.patch. Here is a diff:

--- a/860_all_grub-0.97-pie.patch       2012-05-31 01:00:13.000000000 
+0200
+++ b/860_all_grub-0.97-pie.patch       2017-12-07 11:28:57.536089642 
+0100
@@ -17,8 +17,8 @@
  +            grub_cv_cc_fpie=no)
  +    ])
  +    if test "x$grub_cv_cc_fpie" = xyes; then
-+      STAGE1_CFLAGS="$STAGE1_CFLAGS -nopie"
-+      STAGE2_CFLAGS="$STAGE2_CFLAGS -nopie"
++      STAGE1_CFLAGS="$STAGE1_CFLAGS -no-pie"
++      STAGE2_CFLAGS="$STAGE2_CFLAGS -no-pie"
  +    fi
     fi
   fi

Maybe the easiest way is to create a new grub-patches package, but there 
are other ways to change this too. I'm expected the upstream will change 
this soon - within the remaining 5 weeks ;-).

Another thing is I question that grub-legacy have to be rebuild at all. 
I'm pretty sure it is save to remove it from the world file or comment 
it out.

Anyhow, upgrading to grub2 is IMHO the right way. There are some 
examples given in parallel threads how to write a grub.cfg by hand - and 
keep it simple :-). Then nothing else then the grub2 binary and 
grub2-install is required usually.

Kai
-- 
Sent with eQmail-1.10

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Peter Humphrey]

On Thursday, 7 December 2017 12:04:08 GMT Kai Peter wrote:
> On 2017-12-06 13:28, Peter Humphrey wrote:
> > On Sunday, 3 December 2017 15:12:21 GMT Mick wrote:
> >> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:

--->8

> > Sys-boot/grub-0.97-r17 compiled and installed all right, as a package,
> > but when I went to install it to the MBR I got an error complaining of a
> > mismatch or corruption in stage X. The wording was something like that,
> > and I forget the value of X. There was no mention of disk space, and the
> > boot partition is 2GB, so I think it's something else.
> > 
> > Installing sys-boot/grub-static-0.97-r12 instead went smoothly, so I've
> > left it like that for the moment.
> > 
> > Does the team think I should go back to grub-0.97-r17, take proper
> > records and file a bug report?
> 
> I question if this makes sense for a masked ebuild.

Masked? Not here, it isn't.

> I'm curious about what was discussed until now. The issue seems to be
> quite simple to solve.
> 
> The build fails but portage/gcc does give clear info in this case: the
> option "-nopie" have to be changed to "-no-pie". This option is set in
> 860_all_grub-0.97-pie.patch. Here is a diff:

--->8

Yes, this has been made clear already, but it's not the problem I had.

> Maybe the easiest way is to create a new grub-patches package, but there
> are other ways to change this too. I'm expected the upstream will change
> this soon - within the remaining 5 weeks ;-).
> 
> Another thing is I question that grub-legacy have to be rebuild at all.
> I'm pretty sure it is save to remove it from the world file or comment
> it out.

Then the first emerge -c will remove it from the system.

> Anyhow, upgrading to grub2 is IMHO the right way. There are some
> examples given in parallel threads how to write a grub.cfg by hand - and
> keep it simple :-). Then nothing else then the grub2 binary and
> grub2-install is required usually.

Long-standing readers may remember that I have reasons for avoiding grub-2. 
I still think it's a monstrosity and I'd much prefer never to have to 
wrestle with it again.

On the other hand, I suppose I could have another go at writing my own 
grub.cfg, just for the one little Atom box, if only for a quiet life.

-- 
Regards,
Peter.

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Helmut Jarausch]

On 12/07/2017 03:22:30 PM, Peter Humphrey wrote:
> Long-standing readers may remember that I have reasons for avoiding  
> grub-2.
> I still think it's a monstrosity and I'd much prefer never to have to
> wrestle with it again.
> 
> On the other hand, I suppose I could have another go at writing my own
> grub.cfg, just for the one little Atom box, if only for a quiet life.

I've solved my grub2 problems as follows.

I've written a template file and a tiny Python script which replaces  
the variables
within that template.

If anybody is interested, I will share my template and Python script.

Helmut

Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change

[Kai Peter]

On 2017-12-07 15:22, Peter Humphrey wrote:
> On Thursday, 7 December 2017 12:04:08 GMT Kai Peter wrote:
>> On 2017-12-06 13:28, Peter Humphrey wrote:
>> > On Sunday, 3 December 2017 15:12:21 GMT Mick wrote:
>> >> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:
> 
> --->8
> 
>> > Sys-boot/grub-0.97-r17 compiled and installed all right, as a package,
>> > but when I went to install it to the MBR I got an error complaining of a
>> > mismatch or corruption in stage X. The wording was something like that,
>> > and I forget the value of X. There was no mention of disk space, and the
>> > boot partition is 2GB, so I think it's something else.
>> >
>> > Installing sys-boot/grub-static-0.97-r12 instead went smoothly, so I've
>> > left it like that for the moment.
>> >
>> > Does the team think I should go back to grub-0.97-r17, take proper
>> > records and file a bug report?
>> 
>> I question if this makes sense for a masked ebuild.
> 
> Masked? Not here, it isn't.
In the meaning of 'keyworded':
KEYWORDS="~amd64 ~x86 ~x86-fbsd"
(Why i did know that this will be misunderstood?)

Anyway, it's your choice to file a bug.
> 
>> I'm curious about what was discussed until now. The issue seems to be
>> quite simple to solve.
>> 
>> The build fails but portage/gcc does give clear info in this case: the
>> option "-nopie" have to be changed to "-no-pie". This option is set in
>> 860_all_grub-0.97-pie.patch. Here is a diff:
> 
> --->8
> 
> Yes, this has been made clear already, but it's not the problem I had.
Didn't find it in this thread - my fault. Btw. kernels haven't to be 
stored in /boot necessarily - related to the posts of the size of the 
boot partition. And maybe related to your problem: the r17 ebuild 
differs by the use of patches heavily.
> 
>> Maybe the easiest way is to create a new grub-patches package, but 
>> there
>> are other ways to change this too. I'm expected the upstream will 
>> change
>> this soon - within the remaining 5 weeks ;-).
>> 
>> Another thing is I question that grub-legacy have to be rebuild at 
>> all.
>> I'm pretty sure it is save to remove it from the world file or comment
>> it out.
> 
> Then the first emerge -c will remove it from the system.
Does anybody run emerge -c blindly w/o reviewing the packages before? If 
yes compile it outside of portage. Or backup the required files, do 
emerge -c and restore the backup'd files afterwards. Or ...
> 
>> Anyhow, upgrading to grub2 is IMHO the right way. There are some
>> examples given in parallel threads how to write a grub.cfg by hand - 
>> and
>> keep it simple :-). Then nothing else then the grub2 binary and
>> grub2-install is required usually.
> 
> Long-standing readers may remember that I have reasons for avoiding 
> grub-2.
> I still think it's a monstrosity and I'd much prefer never to have to
> wrestle with it again.
Now, AFAIK, grub2 wants to be a universal boot loader for different 
architectures against grub-legacy is for PC's only. If you still want to 
rely on grub-legacy it would be the best solution to take over the 
project or fork it.
> 
> On the other hand, I suppose I could have another go at writing my own
> grub.cfg, just for the one little Atom box, if only for a quiet life.

-- 
Sent with eQmail-1.10