Re: Select package version in package_config?
On Fri, 14 Feb 2014 16:46:21 +0100, Steffen Grunewald steffen.grunew...@aei.mpg.de said: Would FAI obey the hold setting? Sure. FAI only calls apt-get or aptitude, so if they obey the hold status, FAI will do the same. -- regards Thomas
Re: Select package version in package_config?
On Wed, Jan 22, 2014 at 01:07:56PM +0100, Thomas Lange wrote: On Mon, 20 Jan 2014 13:03:42 +0100, Steffen Grunewald steffen.grunew...@aei.mpg.de said: Until the reason of the grub problem has been identified, I'd like to set the version for all 5 grub* packages to 1.99-27+deb7u2 explicitly (or, to cover the chance of the Wheezy package being updated again, to 2.0) - is this possible within FAI? You can do this with apt pinning, but don't aks me about the details. It's also possible to say packagename/distribution (like grub-pc/wheezy) in the package_config files. I've just come across another quirk which needs unconventional handling: it's the hdf5 package set which comes without libhdf5-serial-dev. The accepted workaround is to install that package from a Squeeze repo, put it on hold, and install a tweaked (build -9.1) version of Wheezy's libhdf5-7 over it. I presume that the most adequate way to represent this in FAI would be a hook, right? When would this best happen, just after unpacking the base package? Would FAI obey the hold setting? Thanks, - S
Re: Select package version in package_config?
On Mon, 20 Jan 2014 13:03:42 +0100, Steffen Grunewald steffen.grunew...@aei.mpg.de said: Until the reason of the grub problem has been identified, I'd like to set the version for all 5 grub* packages to 1.99-27+deb7u2 explicitly (or, to cover the chance of the Wheezy package being updated again, to 2.0) - is this possible within FAI? You can do this with apt pinning, but don't aks me about the details. It's also possible to say packagename/distribution (like grub-pc/wheezy) in the package_config files. -- regards Thomas
Re: Select package version in package_config?
On 01/20/2014 01:03 PM, Steffen Grunewald wrote: For some - yet unknown - reason, grub-pc installed itself, but was unable to load the (also properly created) initrd (the kernel loaded fine, but complained about bad format of /sbin/init). Not exactly what you're asking, but I've ditched the FAI-provided grub scripts and instead rely solely on debconf. I find it much more clean, and it works great on my wheezy FAI server, which is able to install squeeze, wheezy and jessie without issue. Assuming you set the GRUB_PC class (based on things like uname -m, or dpkg --print-architecture or something), here is my hooks/debconf.GRUB_PC.source: #!/bin/sh # Add grub-pc debconf settings to simplify the installation. The # $BOOT_DEVICE variable is set in setup-storage/Fstab.pm, called by # the setup-storage script, called by the partition task in the main # FAI subroutines script. # # NOTE: These cannot be set in the FAI debconf task, since we're unable # to use the global $BOOT_DEVICE variable in the debconf files (they # are not scripts). # # NOTE: It's a good idea to override grub2/linux_cmdline_default, since # Ubuntu sets it to quiet splash by default, which is silly. test -n $SERIAL_DEVICE test -n $SERIAL_SPEED serial=console=tty0 console=$SERIAL_DEVICE,$SERIAL_SPEED cat EOF | $ROOTCMD debconf-set-selections grub-pc grub-pc/install_devices multiselect $BOOT_DEVICE grub-pc grub-pc/install_devices_disks_changed multiselect $BOOT_DEVICE grub-pc grub2/linux_cmdline string $serial crashkernel=128M consoleblank=0 reboot=f grub-pc grub2/linux_cmdline_default string EOF When the grub-pc package is installed, it'll use these values and install and configure grub correctly, including setting up /etc/default/grub. sven
