1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
initramfs-tools (0.129) unstable; urgency=medium
* Some systems that do not support suspend-to-disk (hibernation) will
require a configuration change to explicitly disable this.
From version 0.128, the boot code waits for a suspend/resume device
to appear, rather than checking just once. If the configured or
automatically selected resume device is not available at boot time,
this results in a roughly 30 second delay.
You should set the RESUME variable in
/etc/initramfs-tools/conf.d/resume or
/etc/initramfs-tools/initramfs.conf to one of:
- auto - select the resume device automatically
- none - disable use of a resume device
- UUID=<uuid> - use a specific resume device (by UUID)
- /dev/<name> - use a specific resume device (by kernel name)
-- Ben Hutchings <ben@decadent.org.uk> Thu, 20 Apr 2017 23:21:32 +0100
initramfs-tools (0.121~rc1) unstable; urgency=medium
* If initramfs-tools is configured to use busybox but it is not
installed, mkinitramfs will now fail. Previously it would quietly use
klibc instead, sometimes producing a broken initramfs. You may need
to modify /etc/initramfs-tools/initramfs.conf or install busybox when
upgrading.
* Support for loop-aes has been removed. If you use loop-aes encryption
for the root or /usr filesystem, you will need to switch to cryptsetup.
See the 'loop-AES extension' section in cryptsetup(8).
-- Ben Hutchings <ben@decadent.org.uk> Tue, 22 Dec 2015 21:56:40 +0000
initramfs-tools (0.119) unstable; urgency=medium
* The initramfs will now run fsck on the root filesystem before
mounting it. If the chosen init program is systemd and there is a
separate /usr filesystem, it will also fsck and mount /usr.
* If /usr is a separate filesystem on a RAID device and the INITRDSTART
setting in /etc/default/mdadm is not 'all', you will need to change it
to include that device.
* If /usr is a separate filesystem on an LVM logical volume, and the
line for /usr in /etc/fstab specifies the device by UUID or LABEL,
you must change this line to specify the device using the format
/dev/mapper/VG-LV or /dev/VG/LV.
* It is no longer possible to bind-mount the /usr filesystem.
* If the RTC (real time clock) is set to local time and the local time is
ahead of UTC, e2fsck will print a warning during boot about the time
changing backward (bug #767040). You can disable this by putting the
following lines in /etc/e2fsck.conf:
[options]
broken_system_clock=1
[As of e2fsprogs version 1.42.13 this message is informational, and
no configuration change is required.]
-- Ben Hutchings <ben@decadent.org.uk> Mon, 13 Apr 2015 01:00:21 +0100
initramfs-tools (0.94) unstable; urgency=low
To improve boot speed and avoid some complications, video drivers are
no longer included in the initramfs by default (MODULES=most).
-- maximilian attems <maks@debian.org> Mon, 05 Apr 2010 08:10:34 +0200
initramfs-tools (0.76) unstable; urgency=low
This release features nfs auto detection in the initramfs.
The boot paramaters are parsed according to the linux source
Documentation/kernel-parameters.txt and more specifically
Documentation/nfsroot.txt.
The initramfs-tools(8) manpage documents the parsed boot parameter.
Note that the undocumented and non compliant nfsoption bootarg got
dropped.
-- maximilian attems <maks@sternwelten.at> Wed, 23 Aug 2006 08:47:26 +0200
initramfs-tools (0.61) unstable; urgency=low
This release moves the initramfs-tools confdir from /etc/mkinitramfs to
/etc/initramfs-tools. Packages are encouraged to ship files as scripts
under /usr/share/initramfs-tools.
Local tests behaved fine, but be warned that this could potentially
cause boot troubles on upgrade.
-- maximilian attems <maks@sternwelten.at> Wed, 21 Jun 2006 09:16:01 +0200
initramfs-tools (0.10) breezy; urgency=low
This release includes hardware auto detection in the initramfs.
This means two things in particular that are important:
1) the resulting initramfs will be huge. Like 10 megs huge.
I will shrink it down once it's correct. If you're on an
arch that doesn't like >4mb initramfs', then this won't boot.
2) Your network drivers are loaded in the initramfs, so hotplug
won't see a network event, so ifup won't be run. This will
be fixed shortly in hotplug.
-- Jeff Bailey <jbailey@ubuntu.com> Fri, 17 Jun 2005 15:17:06 +0000
|
