What files in file system ensure Debian Live will mount a casper-rw loop file at boot
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I have been trying for some time to get casper-rw persistent overlay working in Debian Live from scratch, booting the loopback file at startup. Since I only have one Debian Live installation on USB, I have to either make the casper file in a different distro, or do so in Debian, then move it into place. I understand that a casper-rw file with this name must be placed in the root directory of the bootable device, (so loose on the USB key).
Help I have already seen online suggests the use of partitions, rather than a loopback file, which I do not want: I specifically want a mountable persistent overlay file on the same partition for saving minimal system customizations in Debian-based distros (the same kind of thing Gentoo does with .lzm loopback files and 'flushchanges', upon command or not). Debian advice also suggests merely adding the line 'persistent' to the live options at boot, which does not work: the casper file is not mounted (as passing lsblk will show), and no system changes are retained when restarting. I assume that in fact the trick may be to alter fstab or create and edit appropriate instructions at /usr/share/initramfs-tools/scripts/, but only surmise this from one or two posts I have seen online.
So far, no advice I have seen on this subject works for me. Casper-rw file drives only seem to work in Ubuntu when set from an appropriate USB installer (like UnetBootin), but never seem to work when created, put in place and booted with 'persistent' in the boot string (which must be done again every time too).
Does anyone know what files must be created or edited to make Debian Live mount the casper loop file at boot, and keep changes from a session, and boot with them at next (or even all) boots? The real answer should surely be simple.
debian fstab loop-device persistence
asked Oct 15 '17 at 17:51
Arghon
1
add a comment |Â
up vote
0
down vote
favorite
I have been trying for some time to get casper-rw persistent overlay working in Debian Live from scratch, booting the loopback file at startup. Since I only have one Debian Live installation on USB, I have to either make the casper file in a different distro, or do so in Debian, then move it into place. I understand that a casper-rw file with this name must be placed in the root directory of the bootable device, (so loose on the USB key).
Help I have already seen online suggests the use of partitions, rather than a loopback file, which I do not want: I specifically want a mountable persistent overlay file on the same partition for saving minimal system customizations in Debian-based distros (the same kind of thing Gentoo does with .lzm loopback files and 'flushchanges', upon command or not). Debian advice also suggests merely adding the line 'persistent' to the live options at boot, which does not work: the casper file is not mounted (as passing lsblk will show), and no system changes are retained when restarting. I assume that in fact the trick may be to alter fstab or create and edit appropriate instructions at /usr/share/initramfs-tools/scripts/, but only surmise this from one or two posts I have seen online.
So far, no advice I have seen on this subject works for me. Casper-rw file drives only seem to work in Ubuntu when set from an appropriate USB installer (like UnetBootin), but never seem to work when created, put in place and booted with 'persistent' in the boot string (which must be done again every time too).
Does anyone know what files must be created or edited to make Debian Live mount the casper loop file at boot, and keep changes from a session, and boot with them at next (or even all) boots? The real answer should surely be simple.
debian fstab loop-device persistence
asked Oct 15 '17 at 17:51
Arghon
1
Debian != Ubuntu . Make a new partition on the usbkey made with the iso image. format it as (for example) ext4, label the filesystempersistence(that's mandatory to have it namedpersistence). At its root create the filepersistence.confwith content/ union. Boot this usbkey, but before the boot loader actually boots linux, edit the linux boot arguments and add ...persistence! Now boot. You have to add thepersistenceparameter at each boot. Or reimage the live usb to include it. See there: cosmolinux.no-ip.org/raconetlinux2/persistence.html (works the same with Debian 9)
– A.B
Oct 16 '17 at 0:05
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have been trying for some time to get casper-rw persistent overlay working in Debian Live from scratch, booting the loopback file at startup. Since I only have one Debian Live installation on USB, I have to either make the casper file in a different distro, or do so in Debian, then move it into place. I understand that a casper-rw file with this name must be placed in the root directory of the bootable device, (so loose on the USB key).
Help I have already seen online suggests the use of partitions, rather than a loopback file, which I do not want: I specifically want a mountable persistent overlay file on the same partition for saving minimal system customizations in Debian-based distros (the same kind of thing Gentoo does with .lzm loopback files and 'flushchanges', upon command or not). Debian advice also suggests merely adding the line 'persistent' to the live options at boot, which does not work: the casper file is not mounted (as passing lsblk will show), and no system changes are retained when restarting. I assume that in fact the trick may be to alter fstab or create and edit appropriate instructions at /usr/share/initramfs-tools/scripts/, but only surmise this from one or two posts I have seen online.
So far, no advice I have seen on this subject works for me. Casper-rw file drives only seem to work in Ubuntu when set from an appropriate USB installer (like UnetBootin), but never seem to work when created, put in place and booted with 'persistent' in the boot string (which must be done again every time too).
Does anyone know what files must be created or edited to make Debian Live mount the casper loop file at boot, and keep changes from a session, and boot with them at next (or even all) boots? The real answer should surely be simple.
debian fstab loop-device persistence
asked Oct 15 '17 at 17:51
Arghon
1
I have been trying for some time to get casper-rw persistent overlay working in Debian Live from scratch, booting the loopback file at startup. Since I only have one Debian Live installation on USB, I have to either make the casper file in a different distro, or do so in Debian, then move it into place. I understand that a casper-rw file with this name must be placed in the root directory of the bootable device, (so loose on the USB key).
Help I have already seen online suggests the use of partitions, rather than a loopback file, which I do not want: I specifically want a mountable persistent overlay file on the same partition for saving minimal system customizations in Debian-based distros (the same kind of thing Gentoo does with .lzm loopback files and 'flushchanges', upon command or not). Debian advice also suggests merely adding the line 'persistent' to the live options at boot, which does not work: the casper file is not mounted (as passing lsblk will show), and no system changes are retained when restarting. I assume that in fact the trick may be to alter fstab or create and edit appropriate instructions at /usr/share/initramfs-tools/scripts/, but only surmise this from one or two posts I have seen online.
So far, no advice I have seen on this subject works for me. Casper-rw file drives only seem to work in Ubuntu when set from an appropriate USB installer (like UnetBootin), but never seem to work when created, put in place and booted with 'persistent' in the boot string (which must be done again every time too).
Does anyone know what files must be created or edited to make Debian Live mount the casper loop file at boot, and keep changes from a session, and boot with them at next (or even all) boots? The real answer should surely be simple.
debian fstab loop-device persistence
asked Oct 15 '17 at 17:51
Arghon
1
asked Oct 15 '17 at 17:51
Arghon
1
asked Oct 15 '17 at 17:51
Arghon
1
asked Oct 15 '17 at 17:51
Arghon
1
1
Debian != Ubuntu . Make a new partition on the usbkey made with the iso image. format it as (for example) ext4, label the filesystempersistence(that's mandatory to have it namedpersistence). At its root create the filepersistence.confwith content/ union. Boot this usbkey, but before the boot loader actually boots linux, edit the linux boot arguments and add ...persistence! Now boot. You have to add thepersistenceparameter at each boot. Or reimage the live usb to include it. See there: cosmolinux.no-ip.org/raconetlinux2/persistence.html (works the same with Debian 9)
– A.B
Oct 16 '17 at 0:05
add a comment |Â
Debian != Ubuntu . Make a new partition on the usbkey made with the iso image. format it as (for example) ext4, label the filesystempersistence(that's mandatory to have it namedpersistence). At its root create the filepersistence.confwith content/ union. Boot this usbkey, but before the boot loader actually boots linux, edit the linux boot arguments and add ...persistence! Now boot. You have to add thepersistenceparameter at each boot. Or reimage the live usb to include it. See there: cosmolinux.no-ip.org/raconetlinux2/persistence.html (works the same with Debian 9)
– A.B
Oct 16 '17 at 0:05
Debian != Ubuntu . Make a new partition on the usbkey made with the iso image. format it as (for example) ext4, label the filesystem
persistence (that's mandatory to have it named persistence). At its root create the file persistence.conf with content / union. Boot this usbkey, but before the boot loader actually boots linux, edit the linux boot arguments and add ... persistence! Now boot. You have to add the persistence parameter at each boot. Or reimage the live usb to include it. See there: cosmolinux.no-ip.org/raconetlinux2/persistence.html (works the same with Debian 9)– A.B
Oct 16 '17 at 0:05
Debian != Ubuntu . Make a new partition on the usbkey made with the iso image. format it as (for example) ext4, label the filesystem
persistence (that's mandatory to have it named persistence). At its root create the file persistence.conf with content / union. Boot this usbkey, but before the boot loader actually boots linux, edit the linux boot arguments and add ... persistence! Now boot. You have to add the persistence parameter at each boot. Or reimage the live usb to include it. See there: cosmolinux.no-ip.org/raconetlinux2/persistence.html (works the same with Debian 9)– A.B
Oct 16 '17 at 0:05
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f398259%2fwhat-files-in-file-system-ensure-debian-live-will-mount-a-casper-rw-loop-file-at%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Debian != Ubuntu . Make a new partition on the usbkey made with the iso image. format it as (for example) ext4, label the filesystem
persistence(that's mandatory to have it namedpersistence). At its root create the filepersistence.confwith content/ union. Boot this usbkey, but before the boot loader actually boots linux, edit the linux boot arguments and add ...persistence! Now boot. You have to add thepersistenceparameter at each boot. Or reimage the live usb to include it. See there: cosmolinux.no-ip.org/raconetlinux2/persistence.html (works the same with Debian 9)– A.B
Oct 16 '17 at 0:05