Ratheendran R:
> > For your case, I guess the new files you made goes to the upper writable
> > branch ("/rw" before switch_root), and gone after reboot.
> > About the multiple writable branches case, refer to aufs manual
> > first. Also you may want to read about "move-down" or "fhsm" features.
>
Sorry for the typo error in the previous mail's last sentence.In fact I
tried Unionfs not AUFS.
On Tue, Dec 30, 2014 at 5:26 PM, Ratheendran R <[1]ratheendra...@gmail.com>
wrote:
Thanks J. R. Okajima,
Â
Ratheendran R:
> *Now after this command file created in home d
Thanks J. R. Okajima,
Â
Ratheendran R:
> *Now after this command file created in home directory is missing
after
> reboot.I tried creating changes in /etc folder same observation. *
It is unclear to me what you want to do.
Also I am afraid you have not read
Ratheendran R:
> *Now after this command file created in home directory is missing after
> reboot.I tried creating changes in /etc folder same observation. *
It is unclear to me what you want to do.
Also I am afraid you have not read aufs manual.
For your case, I guess the new files you made g
Thanks J. R. Okajima for your patience and time.
I don't think it correct.
What you want to do is
    # mount -o remount,rw /rootfs
     make ext3 /rootfs writable.
I did run the above command on my shell
after this I get the message below on runnin
Hello Guan,
Guan Xin:
> mount -t aufs -o br=3D/mnt-cow:/mnt-ro aufs /new-root
> mount --bind /mnt-cow /new-root/live/cow
> mount --bind /mnt-ro /new-root/live/ro
> umount -l /mnt-cow /mnt-ro
> exec switch_root /new-root "$INIT" "$RUNLEVEL"
>
> Then /live/cow and /live/ro will be empty.
> They wil
Ratheendran R:
> *mount -o noatime,ro -t ext3 /dev/mmcblk0p1 /rootfsmount
> -orw-ttmpfsaufs-tmpfs/rwmount -t aufs -o
> noatime,br=/rw=rw:/rootfs=ro none /aufsmkdir -p /aufs/rootfsmount --move
> /rootfs /aufs/rootfs*
>
> *exec switch_root /aufs /sbin/init*
Ok, you
Hi J. R. Okajima,
Since I am new to Aufs, my explanation may be inadequate.
I am able to see the /rootfs folder in the / after the mount --move in
initramfs.
snapshot of init file from initramfs
mount -o noatime,ro -t ext3Â Â Â /dev/mmcblk0p1Â Â Â Â Â Â /rootfs
mount Â
Ratheendran R:
> Now after the switch_root call from init of initramfs the mount /rw /ro and
> /aufs are cleaned.
>
> exec switch_root /aufs /sbin/init
>
>
> The mount point is not accessible ,Please correct me if my understanding is
> wrong.
??
Do you mean that after switch_root you cannot see a
Hi Ratheendran and Okajima,
I had a similar problem. When I do the followings in initrd:
mount -t aufs -o br=/mnt-cow:/mnt-ro aufs /new-root
mount --bind /mnt-cow /new-root/live/cow
mount --bind /mnt-ro /new-root/live/ro
umount -l /mnt-cow /mnt-ro
exec switch_root /new-root "$INIT" "$RUNLEVEL"
T
Thanks J R Okajima,
Excuse me for my inadequate explanation of the problem.
I am following the below link for the Read only implementation.
[1]https://matt.bionicmessage.net/blog/2013/03/26/HOWTO%3A%20Read%20only%20r
ootfs,%20writes%20to%20USB%20on%20Linux
Â
Now after the sw
CC: aufs-users ML
Ratheendran R:
> I forgot to mention in my earlier correspondence that I am using initramfs
> and mount the aufs and then call the switch root to main file system.hence
> I miss the /aufs in initramfs. so in this case what is the work around.
I don't understand what you want to
Hello Ratheendran,
Ratheendran R:
> 1) Can I use Aufs in production environment for our product.
It is GPL-ed (as linux kernel mainline).
> 2) Does Aufs support older version of linux like 2.6.37 which is my current
> requirment.
It did.
You can check the support status on http://aufs.sf.net.
13 matches
Mail list logo
