Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
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
Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
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
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
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.0 +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
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
Mickwrote: > On Tuesday, 5 December 2017 02:20:14 GMT wabe wrote: > > 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 > > > > 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 root1024 Dec 3 14:07 . > drwxr-xr-x 4 root root1024 Dec 3 11:58 .. > -rw-r--r-- 1 root root 12506 Nov 27 2016 ascii.h > -rw-r--r-- 1 root root5000 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 root9236 Dec 10 2016 fat_stage1_5 > -rw-r--r-- 1 root root8564 Dec 10 2016 ffs_stage1_5 > -rw-r--r-- 1 root root8947 Nov 27 2016 grub-mkconfig_lib > -rw-r--r-- 1 root root 809 Dec 3 14:07 grub.conf > -rw-r--r-- 1 root root8564 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 root8724 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 root8852 Dec 10 2016 ufs2_stage1_5 > -rw-r--r-- 1 root root 1363292 Nov 27 2016 unicode.pf2 > -rw-r--r-- 1 root root8212 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 root9 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
Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
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 root1024 Dec 3 14:07 . > > drwxr-xr-x 4 root root1024 Dec 3 11:58 .. > > -rw-r--r-- 1 root root 12506 Nov 27 2016 ascii.h > > -rw-r--r-- 1 root root5000 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 root9236 Dec 10 2016 fat_stage1_5 > > -rw-r--r-- 1 root root8564 Dec 10 2016 ffs_stage1_5 > > -rw-r--r-- 1 root root8947 Nov 27 2016 grub-mkconfig_lib > > -rw-r--r-- 1 root root 809 Dec 3 14:07 grub.conf > > -rw-r--r-- 1 root root8564 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 root8724 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 root8852 Dec 10 2016 ufs2_stage1_5 > > -rw-r--r-- 1 root root 1363292 Nov 27 2016 unicode.pf2 > > -rw-r--r-- 1 root root8212 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 1204842 120061% /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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
On Mon, Dec 4, 2017 at 10:39 PM, Daniel Freywrote: > > 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 :)
Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
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 root1024 Dec 3 14:07 . > drwxr-xr-x 4 root root1024 Dec 3 11:58 .. > -rw-r--r-- 1 root root 12506 Nov 27 2016 ascii.h > -rw-r--r-- 1 root root5000 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 root9236 Dec 10 2016 fat_stage1_5 > -rw-r--r-- 1 root root8564 Dec 10 2016 ffs_stage1_5 > -rw-r--r-- 1 root root8947 Nov 27 2016 grub-mkconfig_lib > -rw-r--r-- 1 root root 809 Dec 3 14:07 grub.conf > -rw-r--r-- 1 root root8564 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 root8724 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 root8852 Dec 10 2016 ufs2_stage1_5 > -rw-r--r-- 1 root root 1363292 Nov 27 2016 unicode.pf2 > -rw-r--r-- 1 root root8212 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
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
On Tuesday, 5 December 2017 02:20:14 GMT wabe wrote: > Daniel Freywrote: > > 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 root1024 Dec 3 14:07 . drwxr-xr-x 4 root root1024 Dec 3 11:58 .. -rw-r--r-- 1 root root 12506 Nov 27 2016 ascii.h -rw-r--r-- 1 root root5000 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 root9236 Dec 10 2016 fat_stage1_5 -rw-r--r-- 1 root root8564 Dec 10 2016 ffs_stage1_5 -rw-r--r-- 1 root root8947 Nov 27 2016 grub-mkconfig_lib -rw-r--r-- 1 root root 809 Dec 3 14:07 grub.conf -rw-r--r-- 1 root root8564 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 root8724 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 root8852 Dec 10 2016 ufs2_stage1_5 -rw-r--r-- 1 root root 1363292 Nov 27 2016 unicode.pf2 -rw-r--r-- 1 root root8212 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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
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=PARTUUID> quiet rootfstype=ext4 } menuentry 'Gentoo - MythTV' { root=hd0,3 linux /boot/kernel-4.1.43-gentoo-r1-mythtv root=PARTUUID=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
Daniel Freywrote: > 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
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
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
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
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
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.
[gentoo-user] grub-0.97-r16 and profile 17.0 change
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/