Also I think mjt is right. The installer should be able to report if
tar failed for any reason.
Maybe open a new bug about this issue?
--
Purdea Andrei
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia
> which is ensured since / is writable (through aufs).\
--exposed-root is supposed to mount / as read-only. It doesn't really work for
me, so I might be wrong, but in that case /tmp would not be writable (unless
something in the initrd mounts /tmp as tmpfs)
> the only problem here remains that mo
I attached /etc/init.d/mountkernfs.sh, and /lib/live/config/002-user-setup
Only two modifications have been made: I added a sleep statement to each:
002-user-setup:72 contains: sleep 40
mountkernfs.sh:120 contains: sleep 20
This will force the bug to show up Every time you try to boot.
The error
Package: live-config
Version: 3.0~a31-1
There is a race condition between mountkernfs and user-setup
When RAMTMP=yes in /etc/default/rcS, then the
mountkernfs init.d script mounts /tmp as a tmpfs.
The 002-user-setup script first writes some data into a temporary file,
and then reads it back, and
4 matches
Mail list logo
