On Sep 4, 2008, at 7:34 PM, Clara Chan wrote:
> 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 t
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.
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
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 Channe
Unfortunately for me, I tried that and it didn't work.
I am currently using unionfs instead of the kd option. I've change the setting
in /mnt/kd/rc.conf
As I had a /etc/rc.modules, it was not possible to simply put that line in my
/mnt/kd/rc.conf, I had to add a line into the /etc/rc.modules.
I put it in there and it worked. Thanks for all the help.
I think the documentation should be written in the format one of those
"choose your own adventure" books.
/If you have /mnt/kd/rc.conf.d/user.conf please turn to page 47. If you
do not please turn to page 49.
;)
/
Lonnie Abelbeck wro
On Sep 4, 2008, at 9:08 AM, Justin Coffi wrote:
> ZAPMODS=wctdm24xxp
>
> That is the line I have in my /mnt/kd/rc.conf. I've tried it with ir
> without quotes. After the reboot I ran lsmod and I have nothing to
> show for it.
If (and only if) the directory /mnt/kd/rc.conf.d/ exists, you will
ZAPMODS=wctdm24xxp
That is the line I have in my /mnt/kd/rc.conf. I've tried it with ir
without quotes. After the reboot I ran lsmod and I have nothing to show
for it.
Darrick Hartman wrote:
Edit your rc.conf file and set ZAPMODS=wctdm24xxp
Then reboot.
Justin Coffi wrote:
I moved the f
Justin,
1) Make sure /mnt/kd/zaptel.conf is a plain file and not a symbolic
link elsewhere.
2) Issue the following command:
ls -la /oldroot/mnt/asturw/etc/
If there are any forms of zaptel.conf in /oldroot/mnt/asturw/etc/,
remove them.
3) Then reboot. Hope that does it.
Lonnie
On Sep 4,
Edit your rc.conf file and set ZAPMODS=wctdm24xxp
Then reboot.
Justin Coffi wrote:
> I moved the file from /etc/zaptel.conf to /mnt/kd/zaptel.conf and
> reboot. Now the file information is stored in /mnt/kd/zaptel.conf but
> ztcfg won't read it. Even if I use "ztcfg -vv -c /mnt/kd/zaptel.conf"
I moved the file from /etc/zaptel.conf to /mnt/kd/zaptel.conf and
reboot. Now the file information is stored in /mnt/kd/zaptel.conf but
ztcfg won't read it. Even if I use "ztcfg -vv -c /mnt/kd/zaptel.conf"
Another challenge I'm facing:
I believe that I shouldn't have to run "modprobe wctdm24xxp
11 matches
Mail list logo