Martin,
If rc.conf.d exists in /mnt/kd then the rc.conf file is ignored. This
is by design.
Darrick
Martin Croome wrote:
> I hit this problem with Zap hardware not starting properly.
>
>
>
> The problem is in /usr/sbin/gen-rc-conf.
>
>
>
> if [ -d /mnt/kd/rc.conf.d ]; then < -- This
I hit this problem with Zap hardware not starting properly.
The problem is in /usr/sbin/gen-rc-conf.
if [ -d /mnt/kd/rc.conf.d ]; then < -- This directory does exist
if [ -f /stat/etc/rc.conf ]; then
sed -e 's/^#.*//' -e '/^$/ d' /stat/etc/rc.conf >>/tmp/etc/rc.conf
elif [ -d /
No.
You change the file /etc/asterisk/extensions.conf and the unionfs will
take care of it for you.
You shouldn't need to go poking behind the curtain (i.e. in the
/oldroot/mnt/asturw directory).
-Philip
Clara Chan wrote:
> Hi, all,
>
> I am running a Via board and using Runnix on my CF.
>
>
Hi, all,
I am running a Via board and using Runnix on my CF.
I am trying to edit files like extensions.conf and sip.conf.
I understand that the "correct" way of configuring it is to change the
/oldroot/mnt/asturw/stat/etc/asterisk/extensions.conf (for instance).
However, not all people are co
Mark,
Specifically (I mean exactly) which img.gz (note not tar.gz) file is
wrong? Anything with an img.gz should be an image file.
I'm going to have to call you on this because I just gunzip'ed each of
the img.gz files that are posted on my site and I can guarantee that
they are all image fil
This is what I've been trying to say for a week now.
The .img.tgz file on Darrick's website isn't an image file but rather a
collections of the manual install files.
Mark
On Thu, 2008-10-16 at 10:40 -0400, John Novack wrote:
>
> IT Services wrote:
> > Using physdiskwrite gives me a disk which
Ok I compiled trunk 2014 and it runs fine, trunk 2005 kernel panics
branch 0.6 kernel panics... at least in my environment which is a via 3R80
motherboard.. not sre what it does against other platforms...
-Christopher
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECT
I was seeing that last night with # 2010. I figured that it was the fix
I committed as 2009... but if you all were running 2005 and seeing it
as well, then it clearly wasn't that.
I'm running 2014 right now, and it's booting reliably.
Can someone else give it a try?
-Philip
Tom Chadwin wro
I have the same kernel panic at the same stage, after kernel memory freed.
On Thu, Oct 16, 2008 at 3:51 PM, Chris Abnett <[EMAIL PROTECTED]> wrote:
> Interesting… my trunk 1945 runs perfectly.. however I compiled trunk 2005
> and get a kernel panic during the actual astlinux image boot.. so n
Interesting. my trunk 1945 runs perfectly.. however I compiled trunk 2005
and get a kernel panic during the actual astlinux image boot.. so now im
compiling branch 0.6 to see if I get the same thing..
My panic occurs after it verifies the astlinux.run image then goes to boot
then dies after it sa
IT Services wrote:
> Using physdiskwrite gives me a disk which results in a kernel panic on
> boot.
I get the same result attempting to install the img file using dd to a
CF card.
I have no idea why the one step install doesn't work, and it seems
others do it with success, and no general inter
Using physdiskwrite gives me a disk which results in a kernel panic on boot.
Running astinstall from the livecd gives me an unbootable partition (though
fdisk claims its bootable flag is set).
Still failing to get Astlinux running ona single HD system.
Tom
On Wed, Oct 15, 2008 at 3:36 PM, Chris
12 matches
Mail list logo
