[SOLVED]
The problem was not related to live-build.
Only because live-build is creating a lot of new files at some point I
was just
out of free inodes
on partition I had 99% used. And then
every other program started to act weird. So anyway I cleaned a bit my
disk and I am back on level 69% ful
[SOLVED]
The problem was not related to live-build.
Only because live-build is creating a lot of new files at some point I
was just
out of free inodes
on partition I had 99% used. And then
every other program started to act weird. So anyway I cleaned a bit my
disk and I am back on level 69% ful
[2014-12-04 20:26:23] lb build --version
4.0.3-1
Hmmm. Strange error when I (again) tried to build image.
When lb build enters the lb chroot_install-packages install stage at
some point of unpacking packages I got no space left on device error.
This is strange because I have 483,3 Gb free space
="Debian Live 20130402-03:00"
> LB_MEMTEST="memtest86+"
> LB_NET_ROOT_PATH="/srv/debian-live"
> LB_NET_ROOT_SERVER="192.168.1.1"
>
> # Advanced source options
> LB_SOURCE_IMAGES="tar"
> LB_SOURCE="true"
>
>
>
ian.org"
LB_ISO_VOLUME="Debian Live 20130402-03:00"
LB_MEMTEST="memtest86+"
LB_NET_ROOT_PATH="/srv/debian-live"
LB_NET_ROOT_SERVER="192.168.1.1"
# Advanced source options
LB_SOURCE_IMAGES="tar"
LB_SOURCE="true"
And the log ends up wit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 06, 2010 at 10:06:00PM -0200, Teresa e Junior wrote:
[...]
> Hello, Tomás! Sorry for the delay!
No worries :-)
> Unfortunately, if I try to allocate more memory for aufs, the system
> locks on low memory machines, because there's not enou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 4 Nov 2010 10:54:03 +0100
to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Nov 04, 2010 at 06:39:03AM -0200, Teresa e Junior wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Thu, 4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Nov 04, 2010 at 06:39:03AM -0200, Teresa e Junior wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 4 Nov 2010 09:25:05 +0100
> to...@tuxteam.de wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Wed
tal ram). That would mean that those filesystems
are allowed to grow *up to* the respectively given sizes, not more.
> I thought I could solve this by increasing the size of the tmpfs, but
> unless I'm doing it the wrong way, seems not to have solved the issue.
Just leave the size
Hello!
I have created a well compressed live image of a lightweight system, and
I have a script which decompress a file during the boot. My issue is
that I get a "No Space Left on Device" error. My image won't work on
systems with less than 320MB of RAM. It makes my lightweight s
10 matches
Mail list logo
