Thanks, Lonnie. That explanation was greatly appreciated, I was wanting to know the difference between unionfs and keydisk, in terms of file structure and that painted a fairly clear picture. I have already started from scratch on the unionfs system, but trying to apply what I learnt in the 0.4.8 version to this.
In the previous version of the web interface, it was required to ummount the file system prior to changing any configuration, I presume as this is no longer an option, it is no longer required? Btw, as a general question, I am having trouble in changing my password on the new system. Is "mount -o rw,remount /" still required, prior to "passwd"?? A reboot erases the changes I make to the "passwd" command. Cheers, Clara -----Original Message----- From: [EMAIL PROTECTED] on behalf of Lonnie Abelbeck Sent: Fri 9/5/2008 9:53 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] zaptel.conf Clara, I'll try to add a little insight, you might be at a good point to take your knowledge and start over with a freshly formatted card. 1) unionfs vs. kd : In the past, an additional write-able partition for a 'keydisk' (/mnt/kd/) was the only way non-volatile configuration files could be referenced along side a read-only system image. The latest addition of unionfs allows a write-able partition to overlay the read-only system image and magically make the read-only system image appear read-write. A key point is that even if you are not using a third partition for a keydisk, and only using unionfs in the second partition (as Darrick suggests in the notes), you will still want to place all your configuration files in the /mnt/kd/ path. This also has the added benefit that all your configuration files are under a single directory tree, so backups and restores are simple. A simple example, your zaptel.conf should be placed in /mnt/kd/ zaptel.conf. This is the AstLinux way. Creating /etc/zaptel.conf (via unionfs) will not work, and possibly cause trouble. You might think this is silly, but pre-unionfs dictated this solution, and as stated above, has other benefits. So, if you have a configuration file to edit or add, find where in the /mnt/kd/ path it belongs. 2) /mnt/kd/rc.conf vs /mnt/kd/rc.conf.d/ : AstLinux configuration settings can occur in only two ways, either a single /mnt/kd/rc.conf file or all the *.conf files in the /mnt/kd/rc.conf.d/ directory. the rc.conf.d/ directory has precedence, so if it exists, the rc.conf file will be ignored (as Justin has demonstrated in his post.) The new web interface uses the rc.conf.d/ directory, so a convention is suggested that user settings not handled by the web interface should be placed in the /mnt/kd/rc.conf.d/user.conf file. The ZAPMODS variable is such an example. I discuss this in the altweb documentation. New Web Interface Documentation: http://lonnie.abelbeck.com/astlinux/info/webgui.php I hope this adds a little insight to the AstLinux configuration schema. You want want to start fresh, using the /mnt/kd/zaptel.conf file you built and add ZAPMODS in either /mnt/kd/rc.conf or /mnt/kd/ rc.conf.d/user.conf Regards, Lonnie On Sep 4, 2008, at 5:33 PM, Clara Chan wrote: > As I am currently trying to use unionfs instead of a keydisk, and > trying to edit zaptel.conf, can somebody advise which configuration > files I should be editting, the below conf files are all headed with > '# Autogenerated by /usr/local/sbin/sangoma/setup-sangoma -- do not > hand edit > # Zaptel Channels Configurations (zaptel.conf)' > > find / -name zaptel.conf > /mnt/kd/wanpipe/wancfg_zaptel/templates/zaptel.conf > /etc/zaptel.conf > /stat/etc/wanpipe/wancfg_zaptel/templates/zaptel.conf > /oldroot/mnt/asturw/mnt/kd/wanpipe/wancfg_zaptel/templates/zaptel.conf > /oldroot/mnt/asturw/etc/zaptel.conf > /oldroot/mnt/asturo/stat/etc/wanpipe/wancfg_zaptel/templates/ > zaptel.conf > /oldroot/mnt/asturo/etc/zaptel.conf > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
<<winmail.dat>>
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
