[gentoo-user] Gummiboot -> efibootmgr
Hello list, Following today's marking of gummiboot as to be deleted in a month, I had a look at efibootmgr in the wiki pages. It looks as though I'll be able to use it instead, but one thing puzzles me: is it possible to create a set of configs for several kernels, the way gummiboot does in /boot/loader/entries/*.conf? Actually, I'd also like to specify each of two kernel versions with three different command lines to start different run levels. My brain isn't working very well today, so would anyone like to offer me some advice? Please? :) -- Rgds Peter
Re: [gentoo-user] Gummiboot -> efibootmgr
On August 22, 2016 5:05:10 PM GMT+02:00, Peter Humphreywrote: >Hello list, > >Following today's marking of gummiboot as to be deleted in a month, I >had a >look at efibootmgr in the wiki pages. It looks as though I'll be able >to use >it instead, but one thing puzzles me: is it possible to create a set of > >configs for several kernels, the way gummiboot does in >/boot/loader/entries/*.conf? Actually, I'd also like to specify each of >two >kernel versions with three different command lines to start different >run >levels. > >My brain isn't working very well today, so would anyone like to offer >me >some advice? Please? :) I really don't understand the urgency in treecleaning gummiboot. Like grub1, it will still work in 10 years time... -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [gentoo-user] What's happened to gentoo-sources?
Hello Alan, On Monday 22 Aug 2016 11:19:07 Alan Mackenzie wrote: > On Sun, Aug 21, 2016 at 10:12:59AM +0100, Peter Humphrey wrote: > > After this morning's sync, both versions 4.4.6 and 4.6.4 of > > gentoo-sources have disappeared. Is this just finger trouble in the > > server chain? I get the same with UK and US sync servers. > > I restrict myself (mostly) to stable releases, and there hasn't been one > for gentoo-sources for a very long time. Indeed, I've found the same on my stable systems. > The latest stable kernel I see (with $ eshowkw gentoo-sources) is 4.1.15- > r1, although 4.4.6 was stable and available at one stage :-(. My x86 box is still running 4.4.6 because I don't want to plunge all the way back to 4.1.45-r1. This box needs to be ~amd64 to get the latest NVMe and amdgpu drivers. -- Rgds Peter
Re: [gentoo-user] What's happened to gentoo-sources?
Hello, Peter. On Mon, Aug 22, 2016 at 02:23:25PM +0100, Peter Humphrey wrote: > On Monday 22 Aug 2016 11:19:07 Alan Mackenzie wrote: > > On Sun, Aug 21, 2016 at 10:12:59AM +0100, Peter Humphrey wrote: > > > After this morning's sync, both versions 4.4.6 and 4.6.4 of > > > gentoo-sources have disappeared. Is this just finger trouble in the > > > server chain? I get the same with UK and US sync servers. > > I restrict myself (mostly) to stable releases, and there hasn't been one > > for gentoo-sources for a very long time. > Indeed, I've found the same on my stable systems. > > The latest stable kernel I see (with $ eshowkw gentoo-sources) is 4.1.15- > > r1, although 4.4.6 was stable and available at one stage :-(. > My x86 box is still running 4.4.6 because I don't want to plunge all the way > back to 4.1.45-r1. This box needs to be ~amd64 to get the latest NVMe and > amdgpu drivers. I never did get around to configuring and building 4.4.6. Maybe I should. But my box is now pushing 7 years old and seems built like a tank (albeit one that needed a new power supply after just over a year). I'm hoping that when the time comes, I'll still be able to buy a motherboard that will allow Gentoo to be installed on it. I can't see myself doing that any time soon. The only real reason to get a more powerful machine would be to be able to build libreoffice in a sensible amount of time. If that were a priority, I could just upgrade to 16 GB RAM and build LO in a ramdisk. > -- > Rgds > Peter -- Alan Mackenzie (Nuremberg, Germany).
[gentoo-user] Trying to install monodevelop
But fails on a pre-req: >>> Install xdt-for-monodevelop-2.8.1 into /mnt/hd/var/tmp/portage/dev-dotnet/xdt-for-monodevelop-2.8.1/image/ category dev-dotnet * Installing Microsoft.Web.XmlTransform.dll to GAC Couldn't find machine.config Unhandled Exception: System.DllNotFoundException: libc at (wrapper managed-to-native) Mono.Tools.Driver:symlink (string,string) at Mono.Tools.Driver.Install (System.Boolean check_refs, System.String name, System.String package, System.String gacdir, System.String link_gacdir, System.String libdir, System.String link_libdir) [0x0044d] in :0 at Mono.Tools.Driver.Main (System.String[] args) [0x00394] in :0 [MVID] eb82f1b5ebb64ba7907675d3358c14b3 1,2 [ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: libc at (wrapper managed-to-native) Mono.Tools.Driver:symlink (string,string) at Mono.Tools.Driver.Install (System.Boolean check_refs, System.String name, System.String package, System.String gacdir, System.String link_gacdir, System.String libdir, System.String link_libdir) [0x0044d] in :0 at Mono.Tools.Driver.Main (System.String[] args) [0x00394] in :0 [MVID] eb82f1b5ebb64ba7907675d3358c14b3 1,2 * ERROR: dev-dotnet/xdt-for-monodevelop-2.8.1::gentoo failed (install phase): * installing XmlTransform/bin/Release/Microsoft.Web.XmlTransform.dll into the Global Assembly Cache failed * * Call stack: * ebuild.sh, line 133: Called src_install * environment, line 2156: Called egacinstall 'XmlTransform/bin/Release/Microsoft.Web.XmlTransform.dll' * environment, line 532: Called die * The specific snippet of code: * gacutil -i "${1}" -root "${ED}"/usr/$(get_libdir) -gacdir /usr/$(get_libdir) -package ${2:-${GACPN:-${PN}}} || die "installing ${1} into the Global Assembly Cache failed" * * If you need support, post the output of `emerge --info '=dev-dotnet/xdt-for-monodevelop-2.8.1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-dotnet/xdt-for-monodevelop-2.8.1::gentoo'`. * The complete build log is located at '/mnt/hd/var/tmp/portage/dev-dotnet/xdt-for-monodevelop-2.8.1/temp/build.log'. * The ebuild environment file is located at '/mnt/hd/var/tmp/portage/dev-dotnet/xdt-for-monodevelop-2.8.1/temp/environment'. * Working directory: '/mnt/hd/var/tmp/portage/dev-dotnet/xdt-for-monodevelop-2.8.1/work/xdt-Release-NuGet-2.8.1-Mono' * S: '/mnt/hd/var/tmp/portage/dev-dotnet/xdt-for-monodevelop-2.8.1/work/xdt-Release-NuGet-2.8.1-Mono' >>> Failed to emerge dev-dotnet/xdt-for-monodevelop-2.8.1, Log file: My /etc/mono/config looks like this: Any libc appears to be here: # ls -l /lib/libc* -rwxr-xr-x 1 root root 1681144 Jul 12 10:24 /lib/libc-2.22.so lrwxrwxrwx 1 root root 12 Jul 12 10:24 /lib/libc.so.6 -> libc-2.22.so Any ideas? Thanks Tim
Re: [gentoo-user] What's happened to gentoo-sources?
Hello, Peter. On Sun, Aug 21, 2016 at 10:12:59AM +0100, Peter Humphrey wrote: > Hello list, > After this morning's sync, both versions 4.4.6 and 4.6.4 of gentoo-sources > have disappeared. Is this just finger trouble in the server chain? I get the > same with UK and US sync servers. I restrict myself (mostly) to stable releases, and there hasn't been one for gentoo-sources for a very long time. The latest stable kernel I see (with $ eshowkw gentoo-sources) is 4.1.15-r1, although 4.4.6 was stable and available at one stage :-(. > -- > Rgds > Peter -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Gummiboot -> efibootmgr
On Mon, 22 Aug 2016 15:59:41 +, J. Roeleveld wrote: > I really don't understand the urgency in treecleaning gummiboot. > Like grub1, it will still work in 10 years time... I agree, just copy it to a local overlay. If a serious bug does arise, you then have the choice of trying to persuade someone to backport the fix from systemd or switch bootloaders. I've no idea how tightly bootctl (as gummibot is now called after its assimilation in the the systemd collective) is bound to systemd. It may well be feasible to create an ebuild that builds bootctl from the systemd sources without the rest of systemd, as is already done with udev. -- Neil Bothwick Experience is what you get when you didn't get what you wanted. pgpp7BdDVLreW.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Gummiboot -> efibootmgr
On Mon, Aug 22, 2016 at 4:08 PM, Neil Bothwickwrote: > > I've no idea how tightly bootctl (as gummibot is now called after its > assimilation in the the systemd collective) is bound to systemd. It may > well be feasible to create an ebuild that builds bootctl from the systemd > sources without the rest of systemd, as is already done with udev. > It sounds like the integration isn't too tight at runtime at least. Worst case just install systemd. It doesn't do anything unless you change your init= line on your kernel command line. It sounds like the systemd team is looking into options for keeping gummiboot around in some form for openrc users. -- Rich
Re: [gentoo-user] Gummiboot -> efibootmgr
On 08/22/2016 08:59 AM, J. Roeleveld wrote: > > I really don't understand the urgency in treecleaning gummiboot. > Like grub1, it will still work in 10 years time... > > -- > Joost > I agree, I still use grub1 on most my installs. No EFI (computers are old) and just haven't bothered going to something different. "If it ain't broke, don't fix it." Dan
Re: [gentoo-user] Gummiboot -> efibootmgr
Den 22. aug. 2016 17:05, skrev Peter Humphrey: > Hello list, > > Following today's marking of gummiboot as to be deleted in a month, I had a > look at efibootmgr in the wiki pages. It looks as though I'll be able to use > it instead, but one thing puzzles me: is it possible to create a set of > configs for several kernels, the way gummiboot does in > /boot/loader/entries/*.conf? Actually, I'd also like to specify each of two > kernel versions with three different command lines to start different run > levels. > > My brain isn't working very well today, so would anyone like to offer me > some advice? Please? :) > As far as I can tell, you need a separate executable for each menu-entry. The "menu" would then be the modern descendant of the "bios" boot-list. Works well for two or three standard boot-configurations. Booting straight into linux on an EFI system without a boot-loader means you have no way to provide command-line or initramfs as far as I can tell, all modules must be compiled in, and default command-line needs to be set in the kernel config. EFI executables can also be created for example by dracut, which will allow kernel, command-line and initramfs in one efi-file. I have never tried this, I'm using xen.efi (a hypervisor kernel) with a config file, which allows loading of separate kernel and initramfs. Config is just a text file with the same name as the executable, with a .cfg extension. Linux has no such magic available I believe. Copying of executables gets unwieldy fast, plus I have found no way to edit the command-line. Therefore I keep a grub2 install as well, which has editable commmand-lines and such, and also sys-boot/systemrescuecd-x86-grub. I put GRUB_PLATFORMS="efi-64" in /etc/portage/make.conf. I let /boot/EFI/Boot/BOOTX64.EFI be a copy of the Grub EFI binary, so that whenever I update the bios and wipe all efi variables, I can boot into Grub, given that /boot/EFI is where I mount my EFI boot partition. Works as advertised. Grub is not able to load xen.efi, so I need to keep xen.gz around as well for that.
Re: [gentoo-user] Gummiboot -> efibootmgr
On Mon, Aug 22, 2016 at 2:34 PM, Håkon Alstadheimwrote: > > Booting straight into linux on an EFI system without a boot-loader means > you have no way to provide command-line or initramfs as far as I can > tell, all modules must be compiled in, and default command-line needs to > be set in the kernel config. You can have an initramfs, but it also has to be compiled in. Just as with the command line there is an option to include an initramfs in the kernel. I think it actually always builds with some kind of stub of one. This means that you can use modules. It is a pita though, since you'd need to configure your kernel without the initramfs, build everything, install your modules, build your initramfs, then change your config to include the initramfs, and THEN rebuild the kernel itself (which would be fast since most of it is already built), and run the final make install I guess. Heaven help you if you need single-user mode or whatever. Though, I guess you could build a bunch of kernels with various command lines. They'd use a lot of space comparatively, but wouldn't actually take that long to build since again the makefile is reasonably efficient. Plus I always build kernels on a tmpfs anyway. It generally makes sense to use a bootloader with EFI as a result. -- Rich