Why does the kernel not get updated when using a persistant Live USB?
up vote
2
down vote
favorite
I have created a live usb of Ubuntu 12.04 with a 4GB persistence file. Firefox and other software get updated when running update manager. However, the linux kernel will not update and I am unable to install synaptic package manager, ubuntu tweak, etc. Is there a fix for this. Thanks in advance.
12.04 live-usb persistent
add a comment |
up vote
2
down vote
favorite
I have created a live usb of Ubuntu 12.04 with a 4GB persistence file. Firefox and other software get updated when running update manager. However, the linux kernel will not update and I am unable to install synaptic package manager, ubuntu tweak, etc. Is there a fix for this. Thanks in advance.
12.04 live-usb persistent
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have created a live usb of Ubuntu 12.04 with a 4GB persistence file. Firefox and other software get updated when running update manager. However, the linux kernel will not update and I am unable to install synaptic package manager, ubuntu tweak, etc. Is there a fix for this. Thanks in advance.
12.04 live-usb persistent
I have created a live usb of Ubuntu 12.04 with a 4GB persistence file. Firefox and other software get updated when running update manager. However, the linux kernel will not update and I am unable to install synaptic package manager, ubuntu tweak, etc. Is there a fix for this. Thanks in advance.
12.04 live-usb persistent
12.04 live-usb persistent
edited May 17 '12 at 7:37
coversnail
4,618133369
4,618133369
asked May 14 '12 at 4:39
McStud
112
112
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
i found this solution also on askubuntu and i apply it and worked for me and i share again here:
gksudo gedit /etc/kernel/postinst.d/zz-update-grub
**
Comment out line 15
**
BEFORE
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
exec update-grub
;;
AFTER
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
# exec update-grub
;;
Run the configuration script:
$ sudo dpkg --configure -a
(lots of debugging)
$
You should see a lot of debugging, and NOT the error line at the end.
To be sure, re-run the configuration. It should end immediately without any logs:
$ sudo dpkg --configure -a
$
Now, you can restore the zz-update-grub file, just in case you want to install an other kernel later and Grub start to work with overlayfs...
add a comment |
up vote
0
down vote
This is apparently a common question no one replied correctly to.
None of the existing ISO9660-based live operating systems provide a kernel update feature: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and the system partition is, as said, ISO9660-formatted.
After some years of asking me why, I found the liveng whitepaper on Read the Docs.
The full aim of the liveng project is to give the Community a set of
best practices in order to turn a common Debian Linux live into a
live(ng) operating system which features:
native encrypted persistence;
kernel update (on a live ISO 9660 filesystem!);
UEFI, with UEFI Secure Boot compatibility, with a real efi partition.
Tails is another example of live system with kernel update facility, but its filesystem is FAT, not so-good for a live...
New contributor
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
i found this solution also on askubuntu and i apply it and worked for me and i share again here:
gksudo gedit /etc/kernel/postinst.d/zz-update-grub
**
Comment out line 15
**
BEFORE
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
exec update-grub
;;
AFTER
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
# exec update-grub
;;
Run the configuration script:
$ sudo dpkg --configure -a
(lots of debugging)
$
You should see a lot of debugging, and NOT the error line at the end.
To be sure, re-run the configuration. It should end immediately without any logs:
$ sudo dpkg --configure -a
$
Now, you can restore the zz-update-grub file, just in case you want to install an other kernel later and Grub start to work with overlayfs...
add a comment |
up vote
1
down vote
i found this solution also on askubuntu and i apply it and worked for me and i share again here:
gksudo gedit /etc/kernel/postinst.d/zz-update-grub
**
Comment out line 15
**
BEFORE
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
exec update-grub
;;
AFTER
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
# exec update-grub
;;
Run the configuration script:
$ sudo dpkg --configure -a
(lots of debugging)
$
You should see a lot of debugging, and NOT the error line at the end.
To be sure, re-run the configuration. It should end immediately without any logs:
$ sudo dpkg --configure -a
$
Now, you can restore the zz-update-grub file, just in case you want to install an other kernel later and Grub start to work with overlayfs...
add a comment |
up vote
1
down vote
up vote
1
down vote
i found this solution also on askubuntu and i apply it and worked for me and i share again here:
gksudo gedit /etc/kernel/postinst.d/zz-update-grub
**
Comment out line 15
**
BEFORE
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
exec update-grub
;;
AFTER
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
# exec update-grub
;;
Run the configuration script:
$ sudo dpkg --configure -a
(lots of debugging)
$
You should see a lot of debugging, and NOT the error line at the end.
To be sure, re-run the configuration. It should end immediately without any logs:
$ sudo dpkg --configure -a
$
Now, you can restore the zz-update-grub file, just in case you want to install an other kernel later and Grub start to work with overlayfs...
i found this solution also on askubuntu and i apply it and worked for me and i share again here:
gksudo gedit /etc/kernel/postinst.d/zz-update-grub
**
Comment out line 15
**
BEFORE
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
exec update-grub
;;
AFTER
*/postinst.d/*:|*/postinst.d/*:configure|*/postrm.d/*:|*/postrm.d/*:remove)
# exec update-grub
;;
Run the configuration script:
$ sudo dpkg --configure -a
(lots of debugging)
$
You should see a lot of debugging, and NOT the error line at the end.
To be sure, re-run the configuration. It should end immediately without any logs:
$ sudo dpkg --configure -a
$
Now, you can restore the zz-update-grub file, just in case you want to install an other kernel later and Grub start to work with overlayfs...
answered Oct 11 '12 at 17:05
nadeem
176213
176213
add a comment |
add a comment |
up vote
0
down vote
This is apparently a common question no one replied correctly to.
None of the existing ISO9660-based live operating systems provide a kernel update feature: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and the system partition is, as said, ISO9660-formatted.
After some years of asking me why, I found the liveng whitepaper on Read the Docs.
The full aim of the liveng project is to give the Community a set of
best practices in order to turn a common Debian Linux live into a
live(ng) operating system which features:
native encrypted persistence;
kernel update (on a live ISO 9660 filesystem!);
UEFI, with UEFI Secure Boot compatibility, with a real efi partition.
Tails is another example of live system with kernel update facility, but its filesystem is FAT, not so-good for a live...
New contributor
add a comment |
up vote
0
down vote
This is apparently a common question no one replied correctly to.
None of the existing ISO9660-based live operating systems provide a kernel update feature: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and the system partition is, as said, ISO9660-formatted.
After some years of asking me why, I found the liveng whitepaper on Read the Docs.
The full aim of the liveng project is to give the Community a set of
best practices in order to turn a common Debian Linux live into a
live(ng) operating system which features:
native encrypted persistence;
kernel update (on a live ISO 9660 filesystem!);
UEFI, with UEFI Secure Boot compatibility, with a real efi partition.
Tails is another example of live system with kernel update facility, but its filesystem is FAT, not so-good for a live...
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
This is apparently a common question no one replied correctly to.
None of the existing ISO9660-based live operating systems provide a kernel update feature: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and the system partition is, as said, ISO9660-formatted.
After some years of asking me why, I found the liveng whitepaper on Read the Docs.
The full aim of the liveng project is to give the Community a set of
best practices in order to turn a common Debian Linux live into a
live(ng) operating system which features:
native encrypted persistence;
kernel update (on a live ISO 9660 filesystem!);
UEFI, with UEFI Secure Boot compatibility, with a real efi partition.
Tails is another example of live system with kernel update facility, but its filesystem is FAT, not so-good for a live...
New contributor
This is apparently a common question no one replied correctly to.
None of the existing ISO9660-based live operating systems provide a kernel update feature: the kernel and the initrd are the only components that a live operating system cannot update, because they lay outside of the data persistence partition (if any) and the system partition is, as said, ISO9660-formatted.
After some years of asking me why, I found the liveng whitepaper on Read the Docs.
The full aim of the liveng project is to give the Community a set of
best practices in order to turn a common Debian Linux live into a
live(ng) operating system which features:
native encrypted persistence;
kernel update (on a live ISO 9660 filesystem!);
UEFI, with UEFI Secure Boot compatibility, with a real efi partition.
Tails is another example of live system with kernel update facility, but its filesystem is FAT, not so-good for a live...
New contributor
New contributor
answered Nov 15 at 9:44
Happy Penguin
463
463
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f136638%2fwhy-does-the-kernel-not-get-updated-when-using-a-persistant-live-usb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown