Not at all an idiot question. It took me months before I had this epiphany,
tried it, and it worked.
On Wed, Apr 1, 2009 at 3:27 AM, Tom Chadwin
wrote:
> > Just connect the card into a Windows machine. Open "My Computer"
> > Right click on the CF Disk and select rename. This will edit the
> > fi
> Just connect the card into a Windows machine. Open "My Computer"
> Right click on the CF Disk and select rename. This will edit the
> filesystem label.
Ah. As simple as that. Many thanks. Apologies for the idiot question.
Thanks
Tom
On Tue, Mar 31, 2009 at 11:19 AM, Tom Chadwin <
nnpait.servi...@googlemail.com> wrote:
>
> I should have said, Is there an easy way to label the partition using
> Windows?
>
> Thanks
>
Yes. Just connect the card into a Windows machine. Open "My Computer" Right
click on the CF Disk and select re
Tom,
> If you're seeing verification failed, my best guess is you are out of
> space on the vfat partition
That would probably be it. I had 0.6.1 upwards in there, and had to
delete them before I could upgrade manually.
> mlabel -i /dev/sdb1 ::Label
I should have said, Is there an easy way to l
On Mar 31, 2009, at 9:58 AM, Darrick Hartman wrote:
> Tom,
>
> If you're seeing verification failed, my best guess is you are out of
> space on the vfat partition (because an old revision which wasn't
> controlled by the automatic update script was never removed). The
> download truncated and be
Tom,
If you're seeing verification failed, my best guess is you are out of
space on the vfat partition (because an old revision which wasn't
controlled by the automatic update script was never removed). The
download truncated and because the download truncated, the sha1sum check
fails.
Perha
I've got the same issue on two 5501s, and, after remounting manually,
if I try either the GUI or command line automatic upgrade, I get a
verification failure. I've manually done the upgrades instead, and all
seems well, but any ideas what's behind the verification failure?
> If you did a manual ru
Thanks for this.
I have just run an 'upgrade firmware' from the Web UI, from 0.6.3 to
0.6.4 (on a net5501) and it worked fine. Now Runnix is coming into its
own :-)
Mart
Darrick Hartman wrote:
> The AstLinux Team is happy to announce that AstLinux 0.6.4 is available.
> All users of AstLinux
Hi Darrick,
Thank you for the prompt reply and the advice.
I was hoping you wouldn't ask me about the initial install. Frankly, I
TOO am trying to remember exactly how I did the initial install. Sadly,
my only recollection is weeping, gnashing of teeth, and great elation
when it finally wor
Dan,
I'm curious how you did the initial install. It sounds like the file
system label is missing on the 'RUNNIX' partition. With it missing, you
can still upgrade, but you'll need to manually mount the partition.
(usually /dev/hda1)
mount -t vfat /dev/hda1 /oldroot/cdrom
Then you'll see th
All,
It's said that the world's biggest problems could easily have been
solved when they were little. I'm noticing a problem with my Astlinux
installation that I hope is one of those easily-solved, little ones.
However, without your advice, I suspect it will snowball into far bigger
trouble
The AstLinux Team is happy to announce that AstLinux 0.6.4 is available.
All users of AstLinux are encouraged to upgrade since this release
fixes the recently reported security vulnerability in Asterisk 1.4.23.1
Right now a mix up on the Sourceforge site is preventing us from
uploading full i
12 matches
Mail list logo
