As it is currently structured, the persistence partition must be labeled
"persistence" (in Ubuntu, it must be labeled "casper-rw"). Is there any
way to use a different label other than "persistence"?
Package: live-boot
Version: 1:20230131
Severity: normal
Dear Maintainer,
since the fix_ for #934701_, live boot is no longer considering the
partition mounted e.g. on /run/live/medium even when looking for
persistence partition image files (as opposed to persistence on regular
partitions).
It
Package: live-config
Version: 11.0.4
Severity: wishlist
Note to self:
When running an older live image without persistence (e.g. sid), the unattended
upgrades package will:
1) consume network bandwidth by downloading updated packages
2) consume memory due to the overlay filesystem
3) disrupt
Your message dated Thu, 05 May 2022 10:34:23 +
with message-id
and subject line Bug#934701: fixed in live-boot 1:20220505
has caused the Debian Bug report #934701,
regarding live-boot: fixed handling of live media device in case of persistence
to be marked as done.
This means that you claim
Package: live-tools
Version: 1:20190831
Severity: normal
Tags: patch
Debian Live Team,
# apt install live-tools
# live-persistence
E: live-boot not installed
# apt install live-boot
# live-persistence activate VOLUME
/usr/bin/live-persistence: 240: /sbin/cryptsetup: not found
...
# apt install
Hello,
my pendrive live (jessie) created under wheezy works fine with
persistence (/etc/network too with ip=frommedia)
Now under bullseye I created the file live-image-amd64.hybrid.iso
successfully but persistence and ip=frommedia don't work.
cat ~/auto/config
#!/bin/sh
set -e
lb c
Package: live-boot
Version: 1:20190614
Severity: normal
When using persistence, the live media mount point is moved from
/run/live/medium to /run/live/persistence/$something.
This is probably unintended and makes it much harder for third-party
tools to find the original live medium. The attached
I tried removing the part of my hook to set CRYPTSETUP=y in
/etc/cryptsetup-initramfs/conf-hook
(see
https://github.com/mmguero/deblive/blob/master/buster/config/hooks/normal/0991-security-performance.hook.chroot#L92
and
https://www.reddit.com/r/debian/comments/8yxiud/livebuild_issue_getting_pers
would boot fine with encrypted persistence (with the
"persistence
persistence-encryption=none,luks" arguments added via "bootappend-live").
However, sometime recently something changed where when I boot the image on
my laptop I get a continually-scrolling "Nothing to rea
l 10/07/18 a les 23:38, Miguel Martins ha escrit:
> Hi team,
>
> I am unable to setup persistence with Debian live 9.4.0 xfce
>
> I am using
> https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-9.4.0-amd64-xfce.iso
>
> So far, I have been
Hi team,
I am unable to setup persistence with Debian live 9.4.0 xfce
I am using
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-9.4.0-amd64-xfce.iso
So far, I have been able to boot this image from a USB stick. The idea
is to setup a partition on the same USB
>> Any chances that you are willing to add this feature for overlayfs too?
> Don't count on Tails people to do this, sorry.
I just submitted a patch, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86
Cheers
Ronny
Package: live-boot
Version: 1:20170623
Severity: wishlist
Hi,
it would be nice if one could give multiple possible labels for
persistence devices in the persistence-label option, causing live-boot
to probe all matching devices for persistence.conf files.
The code is fine with handling multiple
Ronny Standtke:
> Any chances that you are willing to add this feature for overlayfs too?
Don't count on Tails people to do this, sorry.
> giova.esp...@libero.it:
>> Boot option "persistence-read-only" doesn't work on debian live 9.0.1
> I suspect (without having tried myself) that it still works when using
> aufs, and nobody added support for this feature for overlayfs.
>
> Now, FWIW we (Tails)
giova.esp...@libero.it:
> Boot option "persistence-read-only" doesn't work on debian live 9.0.1
I suspect (without having tried myself) that it still works when using
aufs, and nobody added support for this feature for overlayfs.
Now, FWIW we (Tails) have added this feature
Boot option "persistence-read-only" doesn't work on debian live 9.0.1
I've made a USB stick for the classrooms I run as a CS teacher :
http://framagit.org/groolot/liveusb
and you can see that
https://framagit.org/groolot/liveUSB/blob/master/auto/config configures
the persistence and my students uses USB keys without any kind of problem.
Note that my persis
16 03:14 PM, Aidan Sciortino wrote:
>> I've rolled up some custom debian ISOs using live-build to use on a live
>> USB drive to develop on for a software class at school. I made sure to
>> set the --bootappend-live "boot=live persistence" option, and I've made
&
On 09/22/2016 03:14 PM, Aidan Sciortino wrote:
I've rolled up some custom debian ISOs using live-build to use on a live
USB drive to develop on for a software class at school. I made sure to
set the --bootappend-live "boot=live persistence" option, and I've made
a partitio
I've rolled up some custom debian ISOs using live-build to use on a live
USB drive to develop on for a software class at school. I made sure to set
the --bootappend-live "boot=live persistence" option, and I've made a
partition called persistence and populated it with a p
Your message dated Tue, 07 Jun 2016 16:44:38 +
with message-id
and subject line Bug#817831: fixed in live-config 5.20160607
has caused the Debian Bug report #817831,
regarding [live-config] configuration file placed in /live/config.conf is not
read while in persistence mode
to be marked as
I have been doing this since Debian Squeeze with a patched
9990-misc-helpers in my live initrd. I can use (optionally) a
single-partition live usb with RW access and a persistence file.
It is activated only if "mountmode=rw,noatime" is on cmdline. I never
had any problem with this (alt
Package: live-config
Version: 5.20151121
Severity: important
--- Please enter the report below this line. ---
If booting with persistence mode, then the /live/config.conf file is no
longer accessible and used by the live-config frontend.
Instead, if we boot in persistence with configuration file
erms of security than the debian that I
> everyday use for Web-browsing.
> Is this guess right?
> I made a persistence partition by the following script.
>
> mkdir /media/usb0
> mkfs.ext4 -L persistence /dev/sdb1
> mount -t ext4 /dev/sdb1 /media/usb0
> echo "/home"
Hi.
I use debian live 8.2.
I want to retain after reboot the effect of commands:
# apt-get upgrade
# apt-get install
Because I guess it's safer in terms of security than the debian that I
everyday use for Web-browsing.
Is this guess right?
I made a persistence partition by the following s
was created I put it on a pendrive and I created
> a second partition with label persistence and I edit the file persistence.conf
> with /home, /etc/network, and /union in it, but persistence doesn't work.
>
Sorry for the late reply. I have read your mail at least once a week
since y
On Fri, 2015-08-21 at 11:31 +, Chas Williams III wrote:
> At one point live boot had support for fsck'ing persistent media before
> mounting read/write. This appeared to have been removed due to lack
> of usage/interest.
Here is a better attempt -- now fsck runs before the filesystem is
moun
;
+ else
+ force=""
+ fi
+
+ if [ "$FSCKFIX" = yes ]
+ then
+ fix="-y"
+ else
+ fix="-a"
+ fi
+
+ fsc
Robert Spiteri gmail.com> writes:
> thanks for your reply
>
> the persistence.conf file is a text file containing the character '/'
> because I want all the system changes to be persistent.
>
> I followed the stable manual...
>
> Kindly advise.
>
>
Problem solved... forgot to add the " unio
Daniel Baumann progress-technologies.net> writes:
>
> On 08/15/2015 02:30 PM, Robert Spiteri wrote:
> > 7. create the persistence.conf file
>
> what's the content of the file?
>
> > 8. populated it with /
>
> what do you mean with 'populated with /' exactly?
>
thanks for your reply
the pe
On 08/15/2015 02:30 PM, Robert Spiteri wrote:
> 7. create the persistence.conf file
what's the content of the file?
> 8. populated it with /
what do you mean with 'populated with /' exactly?
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progre
Hi,
1. I downloaded debian live cinnamon iso.
using virtualbox...
2. create a virtual hard disk of 2GB
3. booted debian live
4. formatted harddisk as ext4
5. create persistence image as per stable manual instructions
6. mounted the image
7. create the persistence.conf file
8. populated it with
label persistence and I edit the file persistence.conf
with /home, /etc/network, and /union in it, but persistence doesn't work.
I probably missed something.
Thank you in advance for helping me to solve this problem.
udenz
Gaudenz Steinlin writes:
> Hi
>
> Attached is a prototype patch to implement custom persistence for
> live-config components. Only one component is converted to this to show
> how it's intended to work. The patch is not yet tested. I'd like to have
> some feeba
On Tue, Jun 16, 2015 at 6:30 PM, Jan Kowalsky wrote:
>
> So I try to include an
> usr/share/initramfs-tools/conf-hooks.d/forcecryptsetup with
>
> export CRYPTSETUP=y
>
> in the includes.chroot and build the image again and it works.
>
> The live-initramfs packages should maybe export this variable
Am 12.06.2015 um 23:27 schrieb Jan Kowalsky:
> Am 11.06.2015 um 16:12 schrieb chals:
>> On Thu, Jun 11, 2015 at 11:58 AM, Jan Kowalsky
>> wrote:
>>> Hi all,
>>>
>>> I try to build a live system with luks encrypted persistence. It fails,
>>> b
ut yeah lets have (full) --encryption support.
W dniu 12.06.2015 o 23:27, Jan Kowalsky pisze:
>
> Am 11.06.2015 um 16:12 schrieb chals:
>> On Thu, Jun 11, 2015 at 11:58 AM, Jan Kowalsky
>> wrote:
>>> Hi all,
>>>
>>> I try to build a live system with luks
Am 11.06.2015 um 16:12 schrieb chals:
> On Thu, Jun 11, 2015 at 11:58 AM, Jan Kowalsky
> wrote:
>> Hi all,
>>
>> I try to build a live system with luks encrypted persistence. It fails,
>> because inside the initramfs the cryptsetup binaries don't exist. In t
On Thu, Jun 11, 2015 at 11:58 AM, Jan Kowalsky
wrote:
> Hi all,
>
> I try to build a live system with luks encrypted persistence. It fails,
> because inside the initramfs the cryptsetup binaries don't exist. In the
> past - from wheezy I was able to build an encrypted system
i should have mentioned:
debian jessie
live-boot-initramfs-tools 4.0.2-1
live-build 4.0.3-1
Am 11.06.2015 um 11:58 schrieb Jan Kowalsky:
> Hi all,
>
> I try to build a live system with luks encrypted persistence. It fails,
> because inside the initramfs th
Hi all,
I try to build a live system with luks encrypted persistence. It fails,
because inside the initramfs the cryptsetup binaries don't exist. In the
past - from wheezy I was able to build an encrypted system as long as I
took the live-boot-initramfs-tools from jessie.
Is it possib
On Sat, May 30, 2015 at 3:54 PM, Nick Taylor wrote:
>
> The contents of persistence.conf are:
> /home
> /usr
> /etc
> / union
>
Hi,
It *might* be a problem of nested mounts? See the persistence.conf
manpage -->
http://live-systems.org/manpages/current/en/html/persistence.conf.5.html
hth
--
Howdy:
I successfully created a live dvd of Debian jessie kde.
I created an ext4 partition named "persistence" on /dev/sdc2
I created a file named "persistence.conf" in the persistence partition.
The contents of persistence.conf are:
/home
/usr
/etc
/ union
I boot t
Source: live-boot
Version: 5.0~a3-1
Severity: normal
When booting with persistence the live medium ends up being mounted on
/lib/live/mount/persistence/*devname* after boot. It should instead be
mounted on /lib/live/medium. This happens because while probing for
persistence already mounted
close 700984 4.0.2-1
thanks
Hi,
i can't reproduce this with jessie anymore.
Regards,
Daniel
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/
--
Processing commands for cont...@bugs.debian.org:
> close 700984 4.0.2-1
Bug #700984 [live-boot] image hangs when using luks persistence and debug
enabled
Marked as fixed in versions live-boot/4.0.2-1.
Bug #700984 [live-boot] image hangs when using luks persistence and debug
enabled
Marked
Hi
Attached is a prototype patch to implement custom persistence for
live-config components. Only one component is converted to this to show
how it's intended to work. The patch is not yet tested. I'd like to have
some feeback before going on and converting all the components a
Am 09.12.2014 um 13:15 schrieb antonio maddalosso:
> why, if I copy the live dir in a ntfs partition and start the image from
> this partition the partition is mounted ro?
> cat /etc/mtab
> ...
> /dev/sda1 /lib/live/mount/medium ntfs
> ro,noatime,uid=0,gid=0,fmask=0177,nls=utf8,errors=continue,mtf_
Debian Live Manual: Chapter about persistence:
http://live.debian.net/manual/current/html/live-manual.en.html#557
Enjoy!
On 09.12.2014 13:15, antonio maddalosso wrote:
> why, if I copy the live dir in a ntfs partition and start the image
> from this partition the partition is mounted ro?
automate the persistence in debianlive?
Processing commands for cont...@bugs.debian.org:
> retitle 767195 cryptsetup needs to be enabled for initramfs inclusion
Bug #767195 [live-build] live-boot: Encrypted persistence not possible at boot
time
Changed Bug title to 'cryptsetup needs to be enabled for initramfs inclusion'
retitle 767195 cryptsetup needs to be enabled for initramfs inclusion
tag 767195 pending
thanks
fixed in git, thanks.
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baum...@progress-technologies.net
Internet: http://people.progress-technologies.net
On Wed, Oct 29, 2014 at 6:09 PM, Evgeni Golov wrote:
> Hi,
>
> On 10/29/2014 08:20 AM, Rajko Albrecht wrote:
>>
>> it ask for password and setup the encryption, thats ok. But boot time
>> persistence works only for unencrypted storage.
>
> You will need to do
Ok, I tried a lot, but with current live-build without patching
live-update-initramfs it is not possible getting a live system which
supports encrypted partitions at boot time for persistence.
So it must get fixed in live build tools, eg in live-update-initramfs.
Or cryptsetup changes the
Ok,
Yes, then this is a bug in live-build not boot.
I tried a lot since yesterday getting this parameter into initram build
but no chance until now. No ideas anymore meanwhile (without patching
the live builds itself)
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subj
Hi,
On 10/29/2014 08:20 AM, Rajko Albrecht wrote:
> I tried a while getting a live system working with encrypted persistence on
> boot time. When doing
>
> live-persistence activate /dev/sdx2
>
> it ask for password and setup the encryption, thats ok. But boot time
> persi
Package: live-boot
Version: 4.0.1-1
Severity: important
Tags: d-i
Dear Maintainer,
I tried a while getting a live system working with encrypted persistence on
boot time. When doing
live-persistence activate /dev/sdx2
it ask for password and setup the encryption, thats ok. But boot time
I can't get persistence to work using a 1G ext4 file "persistence"
(containing persistence.conf) in the root directory of a FAT USB flash
drive. I'm booting from the flash drive using syslinux, as described by
Ben Armstrong
(http://syn.theti.ca/2013/06/22/tutorial-wheezy-
On 07/15/2014 02:26 PM, Ed Dixon wrote:
> I am sure this has come up but I have not found anything in the mailing
> list regarding how to create a persistent store on a logical volume. Is
> it possible?
haven't tried myself, and am not aware that anyone worked on it (patches
though would be very w
Hi,
I am sure this has come up but I have not found anything in the mailing
list regarding how to create a persistent store on a logical volume. Is it
possible? Efforts here have failed.
Thanks,
On 04/07/2014 05:24 PM, Michal Suchanek wrote:
> So they are not likely to
> have that feature in the future.
for now they will not as said before, but during the jessie release
cicle, i'll be redoing the syslinux foo, and that means we could have
one more additional entry with '
On 2 April 2014 15:17, Paul Wise wrote:
> On Wed, 2014-04-02 at 13:56 +0200, chals wrote:
>
>> That is fair enough but my guess is that rebuilding an iso image might
>> take longer or rather involve more manual work than building an image
>> from scratch. The requirements for creating a build syst
Greetings,
On Sat, Apr 5, 2014 at 6:55 PM, Paul Wise wrote:
> On Wed, 2014-04-02 at 15:44 +0200, Daniel Reichelt wrote:
>
> > presuming your boot medium is an USB stick, instead of dd'ing the
> > hybrid-iso to it you could partition/format it/make it bootable with
> > syslinux manually and copy
On Wed, 2014-04-02 at 15:44 +0200, Daniel Reichelt wrote:
> presuming your boot medium is an USB stick, instead of dd'ing the
> hybrid-iso to it you could partition/format it/make it bootable with
> syslinux manually and copy the /isolinux from the image and the iso
> itself to the stick's root an
Greetings,
On Thu, Apr 3, 2014 at 3:52 AM, Kamil Czekirda wrote:
> I suggest use debian live installer (live-medium-install):
>
> http://install.live-systems.org/scripts.php
>
> and my mod (ask for persistence):
>
> http://volt.iem.pw.edu.pl/~czekirdk/live-medium-insta
d-with-persistence-on-usb/
Ben
signature.asc
Description: OpenPGP digital signature
Hi,
> I think there is a terminology mismatch here. I wanted to avoid building
> or rebuilding ISO images entirely, I wanted to use the existing images.
presuming your boot medium is an USB stick, instead of dd'ing the
hybrid-iso to it you could partition/format it/make it bootable with
syslinux
Greetings,
On Wed, Apr 2, 2014 at 8:44 AM, Richard Nelson wrote:
> Greetings,
>
>
> On Wed, Apr 2, 2014 at 8:17 AM, Paul Wise wrote:
>
>> On Wed, 2014-04-02 at 13:56 +0200, chals wrote:
>>
>> > That is fair enough but my guess is that rebuilding an iso image might
>> > take longer or rather in
Greetings,
On Wed, Apr 2, 2014 at 8:17 AM, Paul Wise wrote:
> On Wed, 2014-04-02 at 13:56 +0200, chals wrote:
>
> > That is fair enough but my guess is that rebuilding an iso image might
> > take longer or rather involve more manual work than building an image
> > from scratch. The requirements
On Wed, 2014-04-02 at 13:56 +0200, chals wrote:
> That is fair enough but my guess is that rebuilding an iso image might
> take longer or rather involve more manual work than building an image
> from scratch. The requirements for creating a build system are
> relatively low. See,
I think there is
On Wed, Apr 2, 2014 at 7:54 AM, Paul Wise wrote:
>
> I could have just rebuilt the ISO but wanted to avoid that so hdd images
> aren't useful because I would have to build them myself.
>
That is fair enough but my guess is that rebuilding an iso image might
take longer or rather involve more manu
On 04/02/2014 05:32 AM, Paul Wise wrote:
> Is there any way to enable persistence without entering it on every
> boot?
yes, if you build the image yourself you can either add the parameter
to the default parameters, or you can specify it in the live-boot
configfile within the image itsel
oint of view, I see the
> persistence boot parameter as an option. There are certain cases in
> which you want persistence enabled, then you add the parameter at boot
> time. In other cases you will not want persistence enabled, so it
> shouldn't be automatically added.
Perhaps you
On Wed, Apr 2, 2014 at 5:32 AM, Paul Wise wrote:
> Hi all,
>
> I wanted to enable persistence without having to remember to enter it
> every time I boot. I couldn't find a way to do that so I hexedited the
> ISO image, found where the isolinux/live.cfg content was located, add
Hi all,
I wanted to enable persistence without having to remember to enter it
every time I boot. I couldn't find a way to do that so I hexedited the
ISO image, found where the isolinux/live.cfg content was located, added
the persistence parameter and overwrote the now broken failsafe menu
00:00 Franck TALBART :
> Dear Live Debian users,
>
> I am trying to install my own home server using live debian Wheezy on a
> USB key. For the moment, I have enabled the persistence mode which works
> great. To do so, I have created a partition on the space left of the USB
>
@mifamofi.net>> wrote:
Hi,
I'm trying to create a live usb key, but I'm stuck to a problem I
can't solve.
I'm using boot=live persistence toram option as kernel options
On a second partition of the live usb I put an ext3 partition with
a label
Greetings,
On Fri, Jan 24, 2014 at 5:13 AM, PAM wrote:
> Hi,
>
> I'm trying to create a live usb key, but I'm stuck to a problem I can't
> solve.
>
> I'm using boot=live persistence toram option as kernel options
>
> On a second partition of the l
Hi,
I'm trying to create a live usb key, but I'm stuck to a problem I can't
solve.
I'm using boot=live persistence toram option as kernel options
On a second partition of the live usb I put an ext3 partition with a
label persistence
whatever the options I put in p
Dear Live Debian users,
I am trying to install my own home server using live debian Wheezy on a USB
key. For the moment, I have enabled the persistence mode which works great.
To do so, I have created a partition on the space left of the USB stick.
Finally, I have created a persistence.conf file
Hi there!!
After I finish to work on the live-rw partition (when I've booted debian
wheezy with the 'persistence' parameter) I halt the PC using the 'shutdown
-hH now' command and then I reboot the PC without the 'persistence'
parameter. Then, when I
On Tue, Dec 10, 2013 at 2:55 PM, Vladimir Smelhaus wrote:
> I tried it. I would swear that didn't work in stable. But now it's ok. Works
> as described in the manual. But this time I tried with wheezy mixed with
> latest live-* packages.
>
I'm glad that it works for you now. The contents of live-
On Tue, Dec 10, 2013 at 1:12 PM, Vladimir Smelhaus wrote:
Hi,
persistence is not working when persistent storage is image file. When it is
a disk partition, it's ok.
I am trying to make live system with persistence file.
# dd if=/dev/null of=rw.ext4 bs=1 count=0 seek=20M
Have you tried w
On Tue, Dec 10, 2013 at 1:12 PM, Vladimir Smelhaus wrote:
> Hi,
>
> persistence is not working when persistent storage is image file. When it is
> a disk partition, it's ok.
>
> I am trying to make live system with persistence file.
>
> # dd if=/dev/null of=rw.ext4
Hi,
persistence is not working when persistent storage is image file. When
it is a disk partition, it's ok.
I am trying to make live system with persistence file.
# dd if=/dev/null of=rw.ext4 bs=1 count=0 seek=20M
# mkfs.ext4 -F -L persistence rw.ext4
# mount rw.ext4 /mnt
# echo /etc &
On 10/24/2013 06:07 AM, Ka-Hei Law wrote:
> Or should I try newer versions of live-boot?
quoting from http://live.debian.net/project/lifespan/:
"NOTE: Always use the newest version of component within its branch. We
do not support any previous versions within a branch, regardless if that
version
Problem solved. The latest 3.x version of live-boot work out-of-the-box on
Ubuntu 12.04 LTS, and both squashfs files are mounted correctly!
All I did was to install the 3 deb package in
http://live.debian.net/files/3.x/packages/live-boot/3.0.1-1/ :-)
On Thu, Oct 24, 2013 at 12:07 AM, Ka-Hei Law
Unfortunately it does not work on Ubuntu 12.04 LTS (live-boot 3.0~a24)
Here is the error message:
only one RO file system supported with exposedroot
I have not manually enabled "exposedroot". The error message comes from
/usr/share/initramfs-tools/scripts/live:
if [ ${rofscount} -ne 1 ]
So if I create a file "live/filesystem.module" and put my multiple squashfs
filenames in it, live-boot will mount and overlay/merge all the contained
filesystems? That's pretty nice!
On Wed, Oct 23, 2013 at 12:14 PM, Daniel Baumann <
daniel.baum...@progress-technologies.net> wrote:
> On 10/23/20
On 10/23/2013 04:17 PM, gm...@netvope.lcm.hk wrote:
> Is this feature available in live-boot?
not exactely (as in 'not automatically'), but you can use modules to
acchieve the exactly same thing, see man live-boot.
--
Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:
erence of using squashfs persistence
image files. Is this feature available in live-boot?
Thanks,
Ka-Hei
adjusted it to the label "persistence" and
> created a configuration file persistence.conf. This is working fine.
>
> Additionally I have a read-only partition labeled "live-sn".
> How can I realize this with live build 3.0?
If I recall correctly, snapshots had issu
Hello,
I actual use a squeeze live image which is build with live build 2.x and
I want to migrate it to wheezy with live build 3.0.
The home folder should be persistent. Therefore I have a partition
labeled "home-rw". I already adjusted it to the label "persistence&
Hello,
I didn't think your email was useless at all. It pointed me to the correct
,,how to act'' way about Debian, in which I'm new. One gets stuck easily in
wrong information. Can be such darkness. Oew..
>
>Searching for it now yields that everything is well
>documented and I would've avoid
On Sat, Aug 3, 2013 at 10:08 AM, Johannes Schauer wrote:
> Hi,
>
Hi,
It is good to know that you found the right way to do it )
>
> Those things made me not search for the --bootappend-live option in the
> debian-live manual. Searching for it now yields that everything is well
> documented and
Hi,
the problem is solved. It was a feature and not a bug. I guess I got confused
by:
1. many sources [1,2,3] claiming that it was enough to run:
lb config --bootappend-live "persistence"
2. the fact that the default value for LB_BOOTAPPEND_LIVE in the
live-build-cgi.
Hi,
I tested this with live-build versions 3.0.5-1 and 4.0~a20-1 as well as with
the http://live-build-cgi.debian.net/ online service to make sure it's not my
local configuration. When enabling --bootappend-live persistence I get the
following messages after choosing to boot the live syst
Hello
1. I was using live-build 3.0.5-1 from Debian Wheezy. I try to use link
persistence and have a problem at boot. The directory (or symbolic link I
assume) /live/persistence is not created so my persistent and linked file
targets a missing file). Manually creating /live/persistence according
Package: live-boot
Version: 3.0.1-1
Severity: important
Tags: upstream
Dear Maintainer,
persistence apparently failes when the persistence file is located on same ext4
partition as is the live ISO which is booted with GRUB2.
Allowing to put both ISO files and persistence files onto the same
1 - 100 of 290 matches
Mail list logo
