them, and work out how to boot other linux installs.
os-prober
---------
+---------
All one has to do is Depend on os-prober, and then run the os-prober
command. This command takes no arguments: it will scan all disks available
with their own boot sectors.
Tests are executable programs in the directory /usr/lib/os-probes/. Each
-test is called once per partition, with the partiton to check as its
+test is called once per partition, with the partition to check as its
parameter, and may output a string as described above, or nothing if it does
not recognise an OS on that partition. Tests return an exit code of 0
if they successfully found an OS, and no further tests will be run on that
linux-boot-prober
-----------------
-the linux-boot-prober command should be run with a single argument
+The linux-boot-prober command should be run with a single argument
consisting of a partition that is known to have a linux root filesystem on
it, as returned by the os-prober command. It will try to work out how to
boot that linux installation, and if it is successful, will output one or
is made that any partitions referred to in the kernel parameters will still be
in the same place after Debian is installed, or that the /etc/fstab of the
system will be right, or that the system will even boot. The initrd field may
-be empty if there is no initrd. The label is whatever label was used in the
+be empty if there is no initrd. The label is whatever label was used in the
boot loader for this linux installation, and it may be quite long or very
short (or nonexistent), and may be inaccurate, confusing, or non-unique. See
TODO for other limitations.
* Replace basename/dirname with shell string processing (thanks, Hedayat
Vatankhah; part of #694668).
* Call dmraid only once (thanks, Jeff Mahoney).
+ * Fix typos in README (thanks, Nyav; closes: #803155).
-- Colin Watson <cjwatson@debian.org> Sat, 31 Dec 2016 17:11:49 +0000