lp:ubuntu/maverick-proposed/grub-installer
- Get this branch:
- bzr branch lp:ubuntu/maverick-proposed/grub-installer
Branch merges
Branch information
Recent revisions
- 85. By Colin Watson
-
Install GRUB to the SATA RAID or multipath device when /boot is on such
a device, rather than installing to the first hard disk (LP: #603854). - 84. By Colin Watson
-
Purge grub-efi* when $grub_package is grub or grub-pc, and purge grub,
grub-legacy, and grub-pc when $grub_package is grub-efi (LP: #632642). - 83. By Colin Watson
-
[ Soren Hansen ]
Add a preseedable grub-installer/timeout template to adjust the initial
GRUB timeout (LP: #628418). - 82. By Colin Watson
-
* Resynchronise with Debian. Remaining changes:
- Show the grub menu and raise the menu timeout if other operating
systems are installed (only for GRUB Legacy right now).
- Remove splash boot parameter unless debian-installer/ framebuffer= true
and debian-installer/ splash= true.
- If / or /boot are on a removable device, install GRUB there by
default.
- Only mount /target/proc if it isn't already mounted.
- Support setting OVERRIDE_UNSUPPORTED_ OS in the environment to force
grub-installer to use its default MBR selection method despite there
being unsupported operating systems on the disk.
- Unless grub-installer/make_active is preseeded to false, mark the
partition to which GRUB is being installed as bootable, or failing
that the first available primary partition on the disk to which GRUB
is being installed.
- Support grub-installer/bootdev_ directory preseeding to make use of the
relative path feature of grub4dos, so that we can point grub4dos at
part of a disk for Wubi. Setting this disables normal grub
installation, but still generates a device.map (for GRUB Legacy only);
it also hides the menu.
- Handle cases where /boot is bind-mounted.
- Add support for writing an GRUB Legacy MBR on each disk in an
mdadm-managed RAID providing /boot. (GRUB 2 can handle this already.)
- Properly make use of output from os-prober to configure the booting of
other operating systems on dmraid arrays. Attempt to guess where in
the device map the array belongs, by substituting the first drive in
the dmraid array for the dmraid array device node itself, and removing
any reference to other member disks of the array.
- Set a sensible default boot device when /cdrom is not iso9660, as this
is probably a USB install and (hd0) does not make sense when
installing from a removable disk.
- Go back to using update-grub -y for GRUB Legacy for now; our grub
package is a bit old and still requires this.
- Default to grub2 for GPT systems.
- Allow grub/grub2 choice for ext4, though still default to grub2.
- If /boot is on an MD device and we're using GRUB 2, install GRUB there
rather than (hd0); GRUB 2 will interpret that as meaning that it needs
to install to each of the RAID members.
- Mount /target/sys when running update-grub.
- If using GRUB 2 and installing to a RAID device any of whose
components are partitions, then default to installing to the MBRs of
each of the containing disks, since GRUB 2 will refuse to install to
the partition devices.
- Bind-mount /proc and /sys while running grub-install.
- Update grub-installer/bootdev text to avoid GRUB device naming that
changed between GRUB Legacy and GRUB 2, and to use libata-style device
naming since that is more accurate for most people.
- Install grub-efi on i386/efi and amd64/efi subarchitectures.
* Don't ask for a boot device on EFI, and don't pass a boot device
argument to grub-install. - 81. By Colin Watson
-
* Install grub-efi on i386/efi and amd64/efi subarchitectures.
* Resolve symlinks in default boot device (LP: #602758). - 80. By Colin Watson
-
'nosplash' doesn't work because it isn't passed through by user-params.
Use debian-installer/ splash= false for this behaviour instead
(LP: #548954). - 79. By Colin Watson
-
Historically, Ubuntu's default behaviour in the absence of command-line
arguments to the installer has been to pass 'splash' to the installed
system so that it gets a splash screen (and similarly 'quiet'). There's
some argument that this behaviour should require passing 'splash' to the
installer as well, but it's too late in the Lucid cycle for this change.
Nevertheless, we need a way to configure images such that they don't get
'splash' in the installed system, so introduce a 'nosplash' argument
which inhibits this, for use by the server CD (LP: #548954). - 78. By Colin Watson
-
* Ask grub-installer/
only_debian at high priority again (LP: #47135).
Originally, in Warty, we ensured that this question wouldn't be visible
by default to support simple installations of Ubuntu with as few
questions as possible. However, since then, we wrote Ubiquity, which
has taken over responsibility for the simple installation case, and it's
become clear that automatically installing GRUB to the first disk's MBR
is inadequate for many more complex situations. Ironically, Ubiquity
makes this option easily accessible from the "Advanced" dialog box, but
Ubuntu's d-i required a special boot parameter to display it.
* Update grub-installer/bootdev text to avoid GRUB device naming that
changed between GRUB Legacy and GRUB 2, and to use libata-style device
naming since that is more accurate for most people (LP: #391775)
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:ubuntu/natty/grub-installer