John is your reply to mine suggesting that Daniels message should be
shared? If so you have read much more into it than what I said. I think I
must be misunderstanding your point and reading it wrong. I think it may be
in reply to his message or even this whole mess but even so I still
strongly dis
Be sure to share Daniels story via social media using the buttons on his
blog. I hope it wakes up the entire community to what happens when you
actually do something right around here! https://t.co/NwWs9AfW87 Thanks,
On Mon, Nov 9, 2015 at 2:15 PM Richard Newton wrote:
> I agree, shame on those
Resolved thanks to chals suggestion that
a properly formatted live-persistence.conf file be included file on the
root of the persistence image file system which is documented in man
live-persistence.conf.
I hope this helps clarify the process I used to try and create the live
system.
1. From a wheezy desktop create chroot image for sid.
2. Within Chrooted sid downloaded current git versions and build
live-build, live-config, and live-boot.
3. Install built live-build, live-config, and live-boot
Package: live-boot
Version: 3.0~b1-1
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
Built live from chrooted Sid and booted from disk with persistence file in root
as described in manual.
* What exactly
I am not sure but I think the Bug now exists in the Squeeze Repos?
P: Configuring file /etc/apt/sources.list
Reading package lists...
Building dependency tree...
The following NEW packages will be installed:
apt-utils
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 271
6 matches
Mail list logo
