Re: [Astlinux-users] Fwd: New Images

[Lonnie Abelbeck]

On Sep 14, 2008, at 11:28 AM, Darrick Hartman wrote:

> I like the discussion generated about the 'cdrom' directory.  The
> intention was for it to be unmounted after boot from the beginning,  
> but
> we finally got around to fixing the bug that was preventing it from
> getting unmounted.  You can mount this partition by simply doing this:
>
> mount -t vfat /dev/hdX1 /oldroot/cdrom
>
> I would be open to a few different options
>
> 1).  Leaving it mounted, but mounted as read-only by default
> 2).  Having a variable in 'runnix.conf' which could be set to leave  
> the
> cdrom left mounted read-only
> 3).  Any other suggestions.

I cast my vote for #1.

The Status tab "Disk Usage" will then by default show the stats of the  
runnix partition.

This also makes all AstLinux systems consistent, whether the image is  
mounted via loop or ram.

Lonnie


-
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
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]

Re: [Astlinux-users] Fwd: New Images

[Michael Keuter]

>I was actually hoping that Philip would have had a chance to respond to
>that.  It's statically set in target/initrd/initrd.mk, but there's a way
>to set it via shell variable (export BLA=foo in bash) but I don't recall
>the variable that he used.  Right now there's not an easy way to make it
>auto detectable.
>
>I like the discussion generated about the 'cdrom' directory.  The
>intention was for it to be unmounted after boot from the beginning, but
>we finally got around to fixing the bug that was preventing it from
>getting unmounted.  You can mount this partition by simply doing this:
>
>mount -t vfat /dev/hdX1 /oldroot/cdrom

Thanks for clarifying this. Now that I know it, I can live with that.

>I would be open to a few different options
>
>1).  Leaving it mounted, but mounted as read-only by default

I would prefer option 1.

>2).  Having a variable in 'runnix.conf' which could be set to leave the
>cdrom left mounted read-only
>3).  Any other suggestions.
>
>I just fixed the bug that was in the core logic that had existed in the
>initrd/linuxrc script.  Kristian thought it would be cleaner to have it
>unmounted after boot, but perhaps it would be better to leave it visible
>or at least create an entry in the fstab so it could be remounted.
>
>I believe if you do 'findfs LABEL=RUNNIX' that you'd be given the
>correct partition to mount as /oldroot/cdrom.
>
>Darrick

Michael

--
Email: mailto:[EMAIL PROTECTED]


-
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
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]

Re: [Astlinux-users] New Images

[Darrick Hartman]

Darrick Hartman wrote:
> Philip Prindeville wrote:
>> Make sure your partition is big enough for at least two compressed 
>> images (i.e. 96MB or bigger).
> 
> This is why the cf-0.6-XXX-ARCH.img.gz images are created with a 128MB 
> vfat partition.  You'll have room for at least 3 versions.

One more note on the currently posted cf-XXX image files.  They all have 
the KCMD variable 'noram' set.  This was forces the astlinux image to 
remain mounted in loopback mode and not copy the files to system ram.

This was not intentional on my part, but is easy to fix.

mount -o remount,rw /oldroot/cdrom (in this case, this is still mounted 
but as read-only).

edit the astlinux-0.6-XXX.run.conf file and remove the 'noram' variable.

reboot.

Also, if you have have a system with low ram, you can add 'noram' to the 
KCMD line and force a system with 256mb or more to keep the astlinux os 
mounted loopback (so it doesn't use system ram).  If you are on a system 
with less than 200mb ram, astlinux will force noram, even if it's not set.

Darrick

-
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
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]

Re: [Astlinux-users] Fwd: New Images

[David Kerr]

On Sun, Sep 14, 2008 at 1:47 PM, Philip Prindeville <
[EMAIL PROTECTED]> wrote:

> D
>
> where xxx defaults to 90 (megabytes), but can be larger (depending on how
> much memory you have).  On systems with 512MB or so, you can set it to 120
> safely.
>
> See target/initrd/initrd.mk and target/x86/runnix/runnix.mk for details.
>  Oh, and package/busybox/busybox.mk.
>
> H... IMAGEFS_SIZE is actually a misnomer.  It should have been
> RAMFS_SIZE instead.  Oh, well.
>

Now that made me check... I'm using an ALIX 2C3 which only has 256MB, so
pushing it to 110MB for ramdisk may be cutting it fine. I guess I'll find
out.

David
-
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
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]

Re: [Astlinux-users] Fwd: New Images

[Philip Prindeville]

Darrick Hartman wrote:
> David Kerr wrote:
>   
>> On Sun, Sep 14, 2008 at 8:53 AM, Lonnie Abelbeck 
>> <[EMAIL PROTECTED] > wrote:
>>
>>
>> On Sep 14, 2008, at 4:19 AM, Michael Keuter wrote:
>>
>>  >> I'm just uploading some new images to my website.  Some of these
>>  >> are the
>>  >> regular 'runnix' files where the tar ball contains the appropriate
>>  >> astlinux-XXX.run, run.conf etc files and some are complete images
>>  >> that
>>  >> you can simply dd to a new CF.  The complete images have a naming
>>  >> convention of cf-0.6--ARCH.img.gz
>>  >>
>>  >> Darrick
>>  >> --
>>  >
>>  > Hi Darrick,
>>  >
>>  > thanks for the new images. But in the new 1958-geni586-image the
>>  > "/oldroot/cdrom/" directory is empty after reboot. That means you
>>  > cannot update, whithout plugging the CF-card out.
>>  > It also seems that the trunk-images (in my case 1907) has precedence
>>  > over the 0.6 version. That could be a naming convention. You
>>  > mentioned a "ver" file some time ago. How is the syntax for that?
>>  >
>>  > Michael
>>
>> Actually this is a new feature, Darrick added the polishing touches to
>> the initrd.img, which includes unmounting the FAT16 (vfat) runnix
>> partition after the 'run' file is loaded into memory.  Cleaning up.
>>
>> I
>>
>>
>> Why is this beneficial?  Seams to me to be making things more 
>> confusing/harder?
>>
>> Also... I'm still waiting for someone to tell me how to increase the 
>> size of the ramdisk (see my email to this list from yesterday).  I've 
>> googled to the cows come home and played with various menuconfig 
>> settings, but cannot figure it out.
>> 
>
> David,
>
> I was actually hoping that Philip would have had a chance to respond to 
> that.  It's statically set in target/initrd/initrd.mk, but there's a way 
> to set it via shell variable (export BLA=foo in bash) but I don't recall 
> the variable that he used.  Right now there's not an easy way to make it 
> auto detectable.
>   

You may be able to override things with:

$ make ... IMAGEFS_SIZE:=xxx

where xxx defaults to 90 (megabytes), but can be larger (depending on 
how much memory you have).  On systems with 512MB or so, you can set it 
to 120 safely.

See target/initrd/initrd.mk and target/x86/runnix/runnix.mk for 
details.  Oh, and package/busybox/busybox.mk.

H... IMAGEFS_SIZE is actually a misnomer.  It should have been 
RAMFS_SIZE instead.  Oh, well.


> I like the discussion generated about the 'cdrom' directory.  The 
> intention was for it to be unmounted after boot from the beginning, but 
> we finally got around to fixing the bug that was preventing it from 
> getting unmounted.  You can mount this partition by simply doing this:
>
> mount -t vfat /dev/hdX1 /oldroot/cdrom
>
> I would be open to a few different options
>
> 1).  Leaving it mounted, but mounted as read-only by default
> 2).  Having a variable in 'runnix.conf' which could be set to leave the 
> cdrom left mounted read-only
>   

Hmmm... that would complicate any scripts that update the system... more 
possible states for it to have to deal with.

In any case, if you have a system with a small amount of memory (like my 
net5501 w/ 256MB) but a large image (118MB), then you will always have 
the compressed image mounted RO anyway (since it reads and decompresses 
the image on the fly).

Or if you have things set up so that your applications require a lot of 
RAM at run-time, you might also want to forgo having the image 
uncompressed to ramfs.

-Philip



> 3).  Any other suggestions.
>
> I just fixed the bug that was in the core logic that had existed in the 
> initrd/linuxrc script.  Kristian thought it would be cleaner to have it 
> unmounted after boot, but perhaps it would be better to leave it visible 
> or at least create an entry in the fstab so it could be remounted.
>
> I believe if you do 'findfs LABEL=RUNNIX' that you'd be given the 
> correct partition to mount as /oldroot/cdrom.
>
> Darrick
>   


-
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
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]

Re: [Astlinux-users] New Images

[Darrick Hartman]

Philip Prindeville wrote:
> 
> Make sure your partition is big enough for at least two compressed 
> images (i.e. 96MB or bigger).

This is why the cf-0.6-XXX-ARCH.img.gz images are created with a 128MB 
vfat partition.  You'll have room for at least 3 versions.

-
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
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]

Re: [Astlinux-users] New Images

[Philip Prindeville]

Darrick Hartman wrote:
> I'm just uploading some new images to my website.  Some of these are the 
> regular 'runnix' files where the tar ball contains the appropriate 
> astlinux-XXX.run, run.conf etc files and some are complete images that 
> you can simply dd to a new CF.  The complete images have a naming 
> convention of cf-0.6--ARCH.img.gz
>
> SO, if you are starting out fresh and do not have a CF prepared with 
> runnix, do the following:
>
> 1).  Download the cf-0.6--ARCH.img.gz file
> 2).  gunzip the file so you are left with a cf-0.6--ARCH.img file
> 3).  Using dd on Linux (or *BSD) or physdiskwrite on Windows transfer 
> the files to your CF card.  These images will write a 128MB vfat 
> partition containing everything you need to boot up to astlinux.
>
> 4).  Insert the CF into your target device and boot.
> 5).  After booting, login as root (pass astlinux).
> 6).  Create a new partition for unionfs (fdisk /dev/hdX, n, p, 2 ...)
> 7).  Type "sync" which should allow the new partition to be seen.  If 
> not, reboot, relogin then continue with 8.
> 8).  Run 'genunion /dev/hdX2' which will create the file system, copy 
> files and set the file system label to ASTURW for that partition.
> 9).  Reboot and enjoy your system.
>
> If you already have your CF setup, you'll want to continue downloading 
> the astlinux-0.6--ARCH.tar.gz files, expanding those and copying the 
> files to the 'os' directory.
>
> I've tested the net5501 files.  The others should work as well.
>
> You can find these files here:
>
> http://www.djhsolutions.com/astlinux
>
> Darrick
>   

If you have limited DRAM (like I do on my 256MB net5501) and you're not 
decompressing the entire image to ramdisk, but rather keeping the 
compressed file mounted and reading it on demand, then you'll need to do 
the following:

mount -o remount,rw /oldroot/cdrom
pushd /oldroot/cdrom
mv os os.old
popd
mount -o remount,ro /oldroot/cdrom

first...  otherwise, the image in your "os" directory will be "busy" 
when you try to untar the new image.

Reboot, remount the filesystem as writable (as above), and "rm -rf 
/oldroot/cdrom/os.old" when you're sure the new image is working 
satisfactorily.

Make sure your partition is big enough for at least two compressed 
images (i.e. 96MB or bigger).

-Philip


-
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
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]

Re: [Astlinux-users] ntpd hangs at boot for a long time

[Philip Prindeville]

Darrick Hartman wrote:
> Michael Keuter wrote:
>   
>>> Michael Keuter wrote:
>>>   
  Hi list,

  on my Astlinux test PC (PIII 1GHz, 256 MB RAM) all geni386 trunk
  images hang at boot, when the ntpd demon starts, for about 2-5
  minutes. Trunk-1806-image was the latest where it worked. Now I got
  1907 on it.
  The PC has normal static network settings and works normally after
  booted completely. It also gets a dynmic IP during the runnix boot. I
  also tried a fix IP-address for the ntp server (europe.pool.ntp.org)
  but it doesn't helped.
 
>>> Hi Michael,
>>>
>>> The only time I've seen this happen is if the ntp server was
>>> unreachable.  It's possible that there is a bad ntp server in the
>>> europe.pool.ntp.org pool.  That dns uses some sort of a round robin
>>> approach to deciding which ntp server in the pool you get.
>>>
>>> I'll check, but I don't recall any changes to ntp between those revisions.
>>>
>>> Off topic, but I would strongly suggest using images built from the 0.6
>>> branch rather than from trunk.  Trunk will be in various states of
>>> brokenness over the new few weeks/months as some big updates happen
>>> (kernel, gcc, uclibc etc).  0.6 will only get bug fixes and minor
>>> changes so it's going to be much more stable.
>>>
>>> Darrick
>>>   
>> Hi Darrick,
>>
>> I used only your prebuild images. And no, it must 
>> be something special because when I boot my 
>> net4801 with 0.4.8 and the same ntp server, there 
>> is no problem.
>> Is it possible to make the timeout for ntpd 
>> shorter? If I remember there was a switch some 
>> time ago from one ntpd programm to anotherŠ
>> 
>
> We can look at this.  Actually, there are a few possible explanations.
>
> 1).  0.4.8 used openntpd.  We switched to ntpd because it has been more 
> reliable.  I've seen openntpd stop functioning and really cause problems.
>
> 2).  When you boot the new system with runnix.  Is runnix obtaining an 
> IP address?  If so, is it the same IP address that your device uses 
> AFTER it's booted?  You mentioned a static IP address for Astlinux, but 
> dhcp for runnix.  Perhaps your switch is caching the MAC address and 
> confusing the initial network functionality. (just throwing that out 
> there).  Try setting both to the same static IP address and gateway or 
> setting both to dhcp to see what happens.
>   

Or alternately, disconnect the external interface during the Runnix 
phase of booting, and plug it back in once the AstLinux image starts to 
load.

-Philip


>   
>> BTW: Is there any newer prebuild 0.6 geni386 image than 1907?
>> 
>
> Yup.  I'm building some 0.6 images from SVN 1957 today and will upload 
> them later.  I had a major issue with my server yesterday afternoon so I 
> was busy working that out.  Cross your fingers for me that it stays running.
>
> Darrick
>   


-
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
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]

Re: [Astlinux-users] Fwd: New Images

[Darrick Hartman]

David Kerr wrote:
> On Sun, Sep 14, 2008 at 8:53 AM, Lonnie Abelbeck 
> <[EMAIL PROTECTED] > wrote:
> 
> 
> On Sep 14, 2008, at 4:19 AM, Michael Keuter wrote:
> 
>  >> I'm just uploading some new images to my website.  Some of these
>  >> are the
>  >> regular 'runnix' files where the tar ball contains the appropriate
>  >> astlinux-XXX.run, run.conf etc files and some are complete images
>  >> that
>  >> you can simply dd to a new CF.  The complete images have a naming
>  >> convention of cf-0.6--ARCH.img.gz
>  >>
>  >> Darrick
>  >> --
>  >
>  > Hi Darrick,
>  >
>  > thanks for the new images. But in the new 1958-geni586-image the
>  > "/oldroot/cdrom/" directory is empty after reboot. That means you
>  > cannot update, whithout plugging the CF-card out.
>  > It also seems that the trunk-images (in my case 1907) has precedence
>  > over the 0.6 version. That could be a naming convention. You
>  > mentioned a "ver" file some time ago. How is the syntax for that?
>  >
>  > Michael
> 
> Actually this is a new feature, Darrick added the polishing touches to
> the initrd.img, which includes unmounting the FAT16 (vfat) runnix
> partition after the 'run' file is loaded into memory.  Cleaning up.
> 
> I
> 
> 
> Why is this beneficial?  Seams to me to be making things more 
> confusing/harder?
> 
> Also... I'm still waiting for someone to tell me how to increase the 
> size of the ramdisk (see my email to this list from yesterday).  I've 
> googled to the cows come home and played with various menuconfig 
> settings, but cannot figure it out.

David,

I was actually hoping that Philip would have had a chance to respond to 
that.  It's statically set in target/initrd/initrd.mk, but there's a way 
to set it via shell variable (export BLA=foo in bash) but I don't recall 
the variable that he used.  Right now there's not an easy way to make it 
auto detectable.

I like the discussion generated about the 'cdrom' directory.  The 
intention was for it to be unmounted after boot from the beginning, but 
we finally got around to fixing the bug that was preventing it from 
getting unmounted.  You can mount this partition by simply doing this:

mount -t vfat /dev/hdX1 /oldroot/cdrom

I would be open to a few different options

1).  Leaving it mounted, but mounted as read-only by default
2).  Having a variable in 'runnix.conf' which could be set to leave the 
cdrom left mounted read-only
3).  Any other suggestions.

I just fixed the bug that was in the core logic that had existed in the 
initrd/linuxrc script.  Kristian thought it would be cleaner to have it 
unmounted after boot, but perhaps it would be better to leave it visible 
or at least create an entry in the fstab so it could be remounted.

I believe if you do 'findfs LABEL=RUNNIX' that you'd be given the 
correct partition to mount as /oldroot/cdrom.

Darrick

-
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
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]

[Astlinux-users] Recorded sound files not on kd or backed up

[David Kerr]

I used the asterisk-gui to record my own sound files.  As I prepare to
migrate from an older build of astlinux (1792) to branch 0.6 I have found
that these files are not stored on the kd nor backed up (by the alternate
web interface, that copies everything on /mnt/kd).

Sound files that I record myself get placed into
/var/lib/asterisk/sounds/record which unionfs maps onto my compactflash
card. But because they are not in /mnt/kd (like voicemail is) they don't get
backed up. I think this is a bug and that this directory should bet mapped
onto the kd?

Regards,
David.
-
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
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]

[Astlinux-users] Fwd: New Images

[David Kerr]

On Sun, Sep 14, 2008 at 8:53 AM, Lonnie Abelbeck
<[EMAIL PROTECTED]>wrote:

>
> On Sep 14, 2008, at 4:19 AM, Michael Keuter wrote:
>
> >> I'm just uploading some new images to my website.  Some of these
> >> are the
> >> regular 'runnix' files where the tar ball contains the appropriate
> >> astlinux-XXX.run, run.conf etc files and some are complete images
> >> that
> >> you can simply dd to a new CF.  The complete images have a naming
> >> convention of cf-0.6--ARCH.img.gz
> >>
> >> Darrick
> >> --
> >
> > Hi Darrick,
> >
> > thanks for the new images. But in the new 1958-geni586-image the
> > "/oldroot/cdrom/" directory is empty after reboot. That means you
> > cannot update, whithout plugging the CF-card out.
> > It also seems that the trunk-images (in my case 1907) has precedence
> > over the 0.6 version. That could be a naming convention. You
> > mentioned a "ver" file some time ago. How is the syntax for that?
> >
> > Michael
>
> Actually this is a new feature, Darrick added the polishing touches to
> the initrd.img, which includes unmounting the FAT16 (vfat) runnix
> partition after the 'run' file is loaded into memory.  Cleaning up.
>
> I


Why is this beneficial?  Seams to me to be making things more
confusing/harder?

Also... I'm still waiting for someone to tell me how to increase the size of
the ramdisk (see my email to this list from yesterday).  I've googled to the
cows come home and played with various menuconfig settings, but cannot
figure it out.

Thanks
David
-
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
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]

Re: [Astlinux-users] New Images

[Lonnie Abelbeck]

On Sep 14, 2008, at 4:19 AM, Michael Keuter wrote:

>> I'm just uploading some new images to my website.  Some of these  
>> are the
>> regular 'runnix' files where the tar ball contains the appropriate
>> astlinux-XXX.run, run.conf etc files and some are complete images  
>> that
>> you can simply dd to a new CF.  The complete images have a naming
>> convention of cf-0.6--ARCH.img.gz
>>
>> Darrick
>> --
>
> Hi Darrick,
>
> thanks for the new images. But in the new 1958-geni586-image the
> "/oldroot/cdrom/" directory is empty after reboot. That means you
> cannot update, whithout plugging the CF-card out.
> It also seems that the trunk-images (in my case 1907) has precedence
> over the 0.6 version. That could be a naming convention. You
> mentioned a "ver" file some time ago. How is the syntax for that?
>
> Michael

Actually this is a new feature, Darrick added the polishing touches to  
the initrd.img, which includes unmounting the FAT16 (vfat) runnix  
partition after the 'run' file is loaded into memory.  Cleaning up.

In order to update the /oldroot/cdrom/os/ directory you need to mount / 
dev/hd[ab]1, I'll defer to others to give the proper mount command.

The somewhat confusing part of this, as Michael discovered, is that  
you can place files in /oldroot/cdrom, but they will not persist  
across reboots unless /oldroot/cdrom is attached to /dev/hd[ab]1 .

Perhaps in the future, a script:
/usr/sbin/update-run-image 
"http://www.djhsolutions.com/astlinux/astlinux-0.6--ARCH.tar.gz 
"

would...
1) mount the runnix partition, if necessary

2) move the current run* files, possibly to /oldroot/cdrom/old/  
(removing any previous old files there)

3) wget $1

4) tar xzf ...

5) move files from #4 to /oldroot/cdrom/os/

6) cleanup created directory from #4

7) if error, unmount the runnix partition and exit with non-0

8) exit with 0 if all went well.

9) The calling program would issue an /sbin/reboot if exit 0

Just an idea... but if updating were this convenient, leaving the  
runnix partition unmounted becomes a moot point. IMHO

Then, perhaps...
/usr/sbin/revert-run-image

if-and-only-if old/run* files exist, this script would remove the  
current run* files and move the old/run* files to os/

Lonnie







Lonnie


-
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
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]

Re: [Astlinux-users] New Images

[Michael Keuter]

>>I'm just uploading some new images to my website.  Some of these are the
>>regular 'runnix' files where the tar ball contains the appropriate
>>astlinux-XXX.run, run.conf etc files and some are complete images that
>>you can simply dd to a new CF.  The complete images have a naming
>>convention of cf-0.6--ARCH.img.gz
>>
>>Darrick
>>--
>
>Hi Darrick,
>
>thanks for the new images. But in the new 1958-geni586-image the 
>"/oldroot/cdrom/" directory is empty after reboot. That means you 
>cannot update, whithout plugging the CF-card out.

Forget that. I fixed that, it was a problem with some files on my 
asturw partition.

>It also seems that the trunk-images (in my case 1907) has precedence 
>over the 0.6 version. That could be a naming convention. You 
>mentioned a "ver" file some time ago. How is the syntax for that?

Michael

--
Email: mailto:[EMAIL PROTECTED]


-
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
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]

Re: [Astlinux-users] New Images

[Michael Keuter]

>I'm just uploading some new images to my website.  Some of these are the
>regular 'runnix' files where the tar ball contains the appropriate
>astlinux-XXX.run, run.conf etc files and some are complete images that
>you can simply dd to a new CF.  The complete images have a naming
>convention of cf-0.6--ARCH.img.gz
>
>Darrick
>--

Hi Darrick,

thanks for the new images. But in the new 1958-geni586-image the 
"/oldroot/cdrom/" directory is empty after reboot. That means you 
cannot update, whithout plugging the CF-card out.
It also seems that the trunk-images (in my case 1907) has precedence 
over the 0.6 version. That could be a naming convention. You 
mentioned a "ver" file some time ago. How is the syntax for that?

Michael

--
Email: mailto:[EMAIL PROTECTED]


-
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
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]

[Astlinux-users] New Images

[Darrick Hartman]

I'm just uploading some new images to my website.  Some of these are the 
regular 'runnix' files where the tar ball contains the appropriate 
astlinux-XXX.run, run.conf etc files and some are complete images that 
you can simply dd to a new CF.  The complete images have a naming 
convention of cf-0.6--ARCH.img.gz

SO, if you are starting out fresh and do not have a CF prepared with 
runnix, do the following:

1).  Download the cf-0.6--ARCH.img.gz file
2).  gunzip the file so you are left with a cf-0.6--ARCH.img file
3).  Using dd on Linux (or *BSD) or physdiskwrite on Windows transfer 
the files to your CF card.  These images will write a 128MB vfat 
partition containing everything you need to boot up to astlinux.

4).  Insert the CF into your target device and boot.
5).  After booting, login as root (pass astlinux).
6).  Create a new partition for unionfs (fdisk /dev/hdX, n, p, 2 ...)
7).  Type "sync" which should allow the new partition to be seen.  If 
not, reboot, relogin then continue with 8.
8).  Run 'genunion /dev/hdX2' which will create the file system, copy 
files and set the file system label to ASTURW for that partition.
9).  Reboot and enjoy your system.

If you already have your CF setup, you'll want to continue downloading 
the astlinux-0.6--ARCH.tar.gz files, expanding those and copying the 
files to the 'os' directory.

I've tested the net5501 files.  The others should work as well.

You can find these files here:

http://www.djhsolutions.com/astlinux

Darrick
-- 
Darrick Hartman
DJH Solutions, LLC
http://www.djhsolutions.com
Small Business IT Specialists

-
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
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]