** Changed in: initramfs-tools (Ubuntu)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/45225
Title:
update-initramfs should update all initrds
To man
This can be set by admin, if he wishes so, but it definetly makes no
sense as default, thus closing.
** Changed in: initramfs-tools (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https:/
** Changed in: initramfs-tools (Ubuntu)
Importance: Medium => Wishlist
Status: New => Triaged
--
update-initramfs should update all initrds
https://bugs.launchpad.net/bugs/45225
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
As I was hit by this problem recently, I'm glad to see that upstream
initramfs-tools 0.90 adds a configuration setting to have 'update-initramfs -u'
regenerate all initrds. The configuration variable 'update_initramfs' in
'update-initramfs.conf' could already be used in versions prior to 0.90 to
As I commented in bug #69199, updating from 710 to 8.04 beta installs
both 386 and GENERIC kernels, and only updates the INITRAMFS for the
former one, but not for the later, so the system only boots when
choosing the 386 kernel. Running "update-initramfs -u all -k" fixes this
problem. Anyway, the 3
I was bitten by this recently. Conflicts between EVMS and the newest
kernel version were causing my system to fail to boot. Removing EVMS
did not initially fix the problem because it only updated the -generic
initramfs rather than the -386 one which is the one I was currently
booting. Whether or
It did:) initramfs-update -u updated only the newest kernel in the
system even if it wasn't used and tried even if related files in /boot
weren't present.
--
update-initramfs should update all initrds
https://bugs.launchpad.net/bugs/45225
You received this bug notification because you are a membe
archdrone, your problem is a different issue and a bug in your own deb
package: when it was removed, it didn't delete all the 2.6.23 files from
/boot.
--
update-initramfs should update all initrds
https://bugs.launchpad.net/bugs/45225
You received this bug notification because you are a member of
I compiled 2.6.23 kernel into deb package then installed it but because I keep
on using old 2.6.22 I removed the 2.6.23 (apt-get remove 2.6.23-custom).
However now when I do `apt-get install whatever` I get error "E: dpkg was
interrupted, you must manually run 'dpkg --configure -a' to correct th
This also affects people who use upstream kernels, including rc
versions. The current mechanism only updates e.g. 2.6.22-rc7 also 2.6.22
(final) is newer.
--
update-initramfs should update all initrds
https://bugs.launchpad.net/bugs/45225
You received this bug notification because you are a membe
I can confirm this: for some performance tests that I suggested to run I have
-386 and -k7, but -386 was more recently installed.
I installed an update which regenerated only -386, although -k7 was running at
the time:
Unpacking replacement kubuntu-artwork-usplash ...
Setting up kubuntu-artwork-u
11 matches
Mail list logo
