A Dimarts, 11 de maig de 2010 13:36:07, vàreu escriure: > Hello Jordi, > > Jordi Pujol: > > I have found that in the booting process, > > the root filesystem, that is mounted usign aufs, can not be modified, > > It not works well until the system init procedure has been completed. > > > > + mount -n -t squashfs -o ro,noatime > > /lnet/image/LneTPers64/00filesystem.squashfs /lnet/00filesystem.squashfs > > Just to make sure, is /lnet/00filesystem.squashfs accessible after this > line? Is the 'loop' option unnecessary? >
yes to both questions, - some commands are not listed in the previous message, if the mount of 00filesystem.squashfs fails, the startup procedure would stop and show an error message. - the mount command in Busybox autodetects the loop option > > + mount -n -t aufs -o > > nodev,noatime,nowarn_perm,xino=/lnet/xino/.aufs.xino,br:/lnet/cow=rw:/lne > > t/90pcjordi.squashfs=rr:/lnet/12firmwarert.squashfs=rr:/lnet/10tws.squash > > fs=rr:/lnet/00filesystem.squashfs=rr: aufs /root > > + mkdir -p /root/lnet > > + mount -n -o move /lnet /root/lnet > > > > Then, stopping the system startup here, and accessing the busybox command > > What is the fs-type of /lnet, /lnet/xino and /lnet/cow? Are they all in > a single tmpfs or something? > > And what does /lnet contain? /lnet is a directory on /, a more complete listing of the executed commands follows: + modprobe -qb aufs brs=1 + mkdir -p /lnet + mount -n -t tmpfs -o rw,relatime,size=2061540k tmpfs /lnet + mkdir -p /lnet/image + mkdir -p /lnet/cow + mkdir -p /lnet/xino + mount -n -t ext3 -o ro,noatime /dev/sda1 /lnet/image + mkdir -p /lnet/00filesystem.squashfs + mount -n -t squashfs -o ro,noatime /lnet/image/LneTPers64/00filesystem.squashfs /lnet/00filesystem.squashfs + mkdir -p /lnet/10tws.squashfs + mount -n -t squashfs -o ro,noatime /lnet/image/LneTPers64/10tws.squashfs /lnet/10tws.squashfs + mkdir -p /lnet/12firmwarert.squashfs + mount -n -t squashfs -o ro,noatime /lnet/image/LneTPers64/12firmwarert.squashfs /lnet/12firmwarert.squashfs + mkdir -p /lnet/90pcjordi.squashfs + mount -n -t squashfs -o ro,noatime /lnet/image/LneTPers64/90pcjordi.squashfs /lnet/90pcjordi.squashfs + mount -n -t aufs -o nodev,noatime,nowarn_perm,xino=/lnet/xino/.aufs.xino,br:/lnet/cow=rw:/lnet/90pcjordi.squashfs=rr:/lnet/12firmwarert.squashfs=rr:/lnet/10tws.squashfs=rr:/lnet/00filesystem.squashfs=rr: aufs /root + mkdir -p /root/lnet + mount -n -o move /lnet /root/lnet > If it contains some shared libraries and the next command requires them, > then the command may become un-runnable. no more libraries are needed, all the libraries related to the commands included in the initramfs file are also included in the initramfs file, and the path is not changed until the main init procedure starts, previous releases of aufs have executed that without problems, The error messages are sent by commands that write on the aufs filesystem, the "cat" command using output to a file on the aufs filesystem answers "invalid option", the "vi" editor does not write the files and stops the command execution, Jordi Pujol Live never ending Tale GNU/Linux Live forever! http://livenet.selfip.com ------------------------------------------------------------------------------
