On Dec 31, 2007, at 1:47 PM, Jonathan GF wrote: > Hi all, > > when i thought my knowledge of UnionFS was almost none i was wrong. > IS NONE :/ > > I tried to replicate the behavior i got from asterisk-beta-1445 > into asterisk-beta-1459 but i couldn't. I don't understand nothing. > Hope somebody can explain me a bit. > > I mounted RW the CF (/), entered /stat/var/lib/asterisk/ and > deleled the sounds directory. Then mounted back RO the CF (/). > Rebooted. After boot, UnionFS seemed to work because the directory > was deleted in the CF. > > I did exactly the same with the newer asterisk-beta-1459 and after > all the process the directory yet existed. Why? > > The only thing both tests shared is the keydisk and the UnionFS > partition. The asterisk-beta-1459 system boots but says /oldroot is > unable to be unmounted because the resoruce is busy. That's all. No > more information. UnionFS seems to work but finally don't. > > My keydisk is a 2 GB usb pen drive. It's partitioned in 3 pieces: > 1.5 Gb for /mn/kd, 256Mb for UnionFS and spare space. > > Somebody can (this year or the next :) explain me a bit how to > proceed having UnionFS in place? > > My best, > > Jonathan GF
Johathan, I am no unionfs expert, but I have had much success with Darrick's latest builds. In my situation, I have a 1G CF card (net5501), and only two partitions. The first partition is created with Darrick's "runnix.img.gz" image creating +128M FAT16 partition (1). I then later used fdisk to add only one more "ext2" partition for the remaining of the disk, which I "blessed" with "genunion" and added asturw=/dev/hda2 to the KCMD. (I don't set "kd") Now the cool'ness of unionfs. Don't mount anything else, let unionfs do it's thing. When the system boots, the "ro" AstLinux image is copied to the / oldroot/mnt/asturo/ path, and the unionfs 'overlay' runs in parallel in the /oldroot/mnt/asturw/ path (at least this is what happens on a net5501). Now, the resulting filesystem is the 'union' of these two parallel filesystems, with priority given to the "asturw" path. So, if you do a: touch /mnt/kd/foo note that an empty file is created (in the "asturw" path), but /mnt/ kd/foo is fully read-writable. Now, as I mentioned a few days back, you can actually "delete" original "ro" files, and unionfs makes a note of it in the "asturw" path with a hidden file beginning with ".wh." prefix. In general there is no need to remove "ro" files, simply change them, and the newer file will be placed in the "asturw" path and will be used instead of the original "ro" file. So, with your sounds, simply add them, and configure asterisk to use them. The keydisk "/mnt/kd" can also be handled by unionfs instead of a separate partition. The best is to touch, edit and cat files, and understand what is happening. Look in the /oldroot/mnt/asturw/ path to see the changes. Unionfs is very cool. Lonnie ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
