Skip to main content

Preseeding Ubuntu Natty 11.04

I decided to start this blog because of the never ending battles I have with remembering what I have conquered before, and thinking that other people have the same problems.

The specific problem I was working on when I came to this conclusion was preseeding a Natty netboot install. EVERY version of Ubuntu brings more preseeding problems - something always changes, causing you to get prompted for something new, when the previous release worked without a hitch.

This time (going from Lucid to Natty) was the keyboard layout preseed. I got the dreaded keyboard layout screen.

Turns out the preseed file is only looked at once the locale is set (makes sense), so you have to pass the keyboard config in the kernel line of your PXE boot:

LABEL stuff_natty64kernel linux.natty64append vga=normal initrd=initrd.gz.natty64 locale=en_AU preseed/locale=en_AU keyboard-configuration/layoutcode=us console-setup/ask_detect=false netcfg/wireless_wep= netcfg/choose_interface=auto netcfg/get_hostname= netcfg/get_domain= preseed/url=http://myserver/preseed/ubuntu_natty/preseed.cfg http_proxy= my_image_type=stuff --

The key component this time is:

keyboard-configuration/layoutcode=us

I worked this out by checking the update log for console-setup (which is what you used to have to pass for Lucid):

console-setup (1.57ubuntu8) natty; urgency=low
* Move keyboard detection templates from console-setup.templates to
keyboard-configuration.templates.
-- Colin Watson Mon, 28 Feb 2011 19:21:18 +0000

And there you have it - instead of being "console-setup/layoutcode=us", it is now "keyboard-configuration/layoutcode=us"

Makes sense now - but that is an hour of my life I can't get back!

S

Comments

  1. Thanks Sean, I was just trying to sort this out!

    ReplyDelete
  2. I can't seem to get Natty to respect the MBR auto-installation directives:
    d-i grub-installer/only_debian boolean true
    d-i grub-installer/with_other_os boolean true

    Basically, I want to nuke the MBR and install Natty's grub there, no matter what.

    However, no combination of these settings
    (TT/TF/FT/FF) gets me past the prompt for where to install grub.

    Manually entering /dev/sda works fine, but that's unacceptable.
    Any pointers would be most appreciated.

    ReplyDelete
  3. Thanks for this, I thought I was the only one going crazy.

    ReplyDelete
  4. Thanks for the tip about the keyboard layout!
    But my other problem is installing the GRUB into the MBR... What is the solution to preset it?

    ReplyDelete
  5. Olivier - the line that seems to do it for me (and has done since Hardy) is


    d-i grub-installer/only_debian boolean true

    ReplyDelete
  6. I can't get the partitioning to preseed no matter what I try. Can you post the partition section of your preseed?

    ReplyDelete
  7. stiqs - here you go:


    d-i partman-auto/disk string /dev/sda
    d-i partman-auto/method string regular

    d-i partman-auto/expert_recipe string physics-workstation :: 200 20000 250 ext4 $primary{ } $bootable{ } method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /boot } . 25000 20000 29000 ext4 method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /usr/local } . 3000 20000 6000 ext4 method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /tmp } . 18000 18000 21000 ext4 method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ / } . 1000 20000 300% linux-swap method{ swap } format{ } . 1000 10000 1000000000 ext4 method{ format } format{ } use_filesystem{ } filesystem{ ext4 } mountpoint{ /scratch } .

    d-i partman/confirm_write_new_label boolean true
    d-i partman/choose_partition select Finish partitioning and write changes to disk
    d-i partman/confirm boolean true
    d-i partman-partitioning/confirm_copy boolean true
    d-i partman/confirm_new_label boolean true

    ReplyDelete

Post a Comment

Popular posts from this blog

Compiling tun.ko for Android - OpenVPN

I have a Xoom, and a Galaxy S, and need to be able to compile my own tun.ko for the kernel version I have. As you all know, if the kernel version of the module you are trying to insert isn't the same, it won't insert, and will give you errors like:


<3>[95175.874872] tun: version magic '2.6.36.4-athm1-OV-launchpad-1.2.2+ SMP preempt mod_unload ARMv7 ' should be '2.6.36.3-gc2bee64 SMP preempt mod_unload ARMv7 '

in dmesg. We need to compile the module for the right version of the kernel


Download the Kernel source - normally from http://android.git.kernel.org/. The Xoom can be found at http://android.git.kernel.org/kernel/tegra.git, and the Galaxy S can be found at http://android.git.kernel.org/kernel/samsung.git. Use

$ pwd
   /scratch/xoom
$ git clone http://android.git.kernel.org/kernel/tegra.git to clone the Xoom kernel sourceCopy your old kernel config from your device

$ pwd
   /scratch/xoom
$ adb pull /proc/config.gz
$ gunzip config.gz
$ mv config.gz tegr…

Renewing Puppet CA and puppet master certificates

My two Puppet deployments are just about to turn 5 years old, and as such, the CA and puppet master certificates are just about to expire.

The documentation online seem to suggest the only way to renew these certs is by deleting the /var/lib/puppet/ssl directory and getting Puppet to renew them. This would mean renewing all the certificates of all the nodes at the same time. Even the official Puppet docs suggest this is the way too.(https://docs.puppet.com/puppet/3.7/ssl_regenerate_certificates.html)

The way I will describe renews the CA certificate and puppetmaster certificate in a way which is still trusted by every existing host.


First, copy the important files to a new directory# mkdir /root/puppet_renewal # cd /root/puppet_renewal # mkdir /root/puppet_renewal/ca # mkdir /root/puppet_renewal/puppetmaster # mkdir /root/puppet_renewal/puppetmaster/private_keys # mkdir /root/puppet_renewal/puppetmaster/certs # cp /var/lib/puppet/ssl/ca/ca_key.pem /root/puppet_renewal/ca # cp /var/lib/…