fetch works for me, however, it has some limitations: due to issues with
busybox, name resolution doesn't work which restricts fetch parameter to
urls with IPs in it only.
this has also the effect, that you cannot fetch from an namebased
virtualhost in your httpd configuration.
ok
if yo
Daniele Primon a écrit :
Is the loop device setup correctly? You should try losetup to be
sure. Another hint makes me suspicious about is the double slash in
//fai.squashfs
i rerun with a remade sqaushfs and i got the same problem :
+ mkdir -p //fai.squashfs
+ log_begin_msg Mounting "/live/
hi,
Following my faillure with AOE and debian live i tried to use the
fetch parameter to load a squafs image.
So i created a squafs image and install nginx as a web server. The
debian live still fail this time with the error:
+ printf Begin: Mounting "/live/image/live/fai.squashfs" on
"/
Daniel Baumann a écrit :
Jean Spirat wrote:
ii live-initramfs 1.139.1-3 Debian
Live initramfs hook
in theory it is a debien lenny ... :(
so if this is not the good one i have a problem !! i will check.
1.154.5-1 migrated today, however
i made some progress, instead of using a partition on a block device i
used directly the block devicce /dev/etherd/e10.2 (instead of
/dev/etherd/e10.1p1 ) :
+ echo 00-15-17-8F-44-3C
+ mac=00-15-17-8F-44-3C
+ echo 00-15-17-8F-44-3C
+ sed s/-//g
+ mac=0015178F443C
+ mount_images_in_directory /dev
i was just saying that i've no clue about it. with nfs, i have some :)
eheh ;)
ii live-initramfs 1.139.1-3 Debian
Live initramfs hook
shouldn't make any difference here, but in future, could you use the
most current one from sid (preferably) or at
in fact this is where my AOE mount fails, the system ends up read only
and the aufs part is not working.
i've absolutely no clue about AOE. i'm not even sure it's possible with
current live-initramfs. did you try regular nfs based netboot first?
no in fact i cannot use NFS for policy
a forward from some talk with the FAI guys.. perhaps you can help me here :)
FAI only needs the live-initramfs package which provides the functions
to boot from network, mounts the root file system via NFS and adds
aufs (another unionfs) on top of it. Using aufs we have write access to all
f
during the system boot, an aufs (or unionfs) layer on top of the
read-only mounted filesystem (squashfs) is established. any write you do
will result in a transparent ramdisk overlay.
ok this is what is not working for me
I tried to make one live system to work with FAI but it complain tha
Hello there,
I have a little question about debian live, perhaps you can help me as
the docs on the web are not clear to me:
- debian live boot from read only media, like cds for exemple
Then, how it handle the write to files like in the /var directory ?
I tried to make one live system to w
Richard Nelson a écrit :
On Thu, Dec 18, 2008 at 7:12 AM, Jean Spirat wrote:
hi,
i am new to debian live. I use FAI to install debian servers and it use
debian live for its initrd system. My issue is that it mount a nfs volume
for the root filesystem and i want to replace it by an AOE
hi,
i am new to debian live. I use FAI to install debian servers and it use
debian live for its initrd system. My issue is that it mount a nfs
volume for the root filesystem and i want to replace it by an AOE target.
I writed a script called init-premount/aoetools that basicaly do a
ifconf
12 matches
Mail list logo
