Michael Keuter wrote:
>> Michael Keuter wrote:
>>
>>
>> Hi John,
> I just updated the Wiki and gave a reference to a dev-mailing list
> discussion about the Zabbix package.
> http://doc.astlinux.org/devdoc:packages
>
> BTW: Astlinux 0.5 was NEVER released formally, and only a few freaks
>
John,
Thanks for helping us understand how you use it and what's important to you.
The ISO stuff is Darrick's domain, so I'll let him tackle that.
I just banged out some directions on burning images and uploading build results
to a running system.
As for the move to 1.8: yeah, I think everyo
And that's simpler?
Ok, if you say so. :-)
It wouldn't work for me because my build host is on a remote network, and the
only way it can install images back to my local network is via SSH... it
doesn't have a publicly visible web server. Indeed, I'm not even sure I've
ever bothered to ins
For the page:
http://doc.astlinux.org/devdoc:documentation
in the section "Creating an Image", this is fairly simple. If someone can cut,
massage, and paste this into the Wiki, that would be great.
= = =
Use "dmesg" to figure out the size of the CF when you insert it into your build
system
Mark,
First, assuming you're not working with 'trunk', do the following:
mkdir scripts
wget -P scripts -O shipit.sh
'http://astlinux.svn.sourceforge.net/viewvc/astlinux/trunk/scripts/shipit.sh?revision=4337'
chmod a+x scripts/shipit.sh
and then if you need to use a particular port to ssh into
Or, for us mortals... :-)
In your build system, after a successful build for the 0.7 branch, you will see
two files:
astlinux-0.7-4300.tar.gz
astlinux-0.7-4300.tar.gz.sha1
The "4300" corresponds to the current SVN rev, your number will vary.
Create your own private HTTP repository for your cus
>Michael Keuter wrote:
>
>>>Under prerequisites - ??? isn't very helpful in specifying a package!
>>>
>>It's better than nothing. Until I wrote this a few days ago, we had
>>no package list at all :-).
>>
>Not really meant to criticize, but ??? gives no guidance as to what
>to look for, or where t
Michael Keuter wrote:
>> Under prerequisites - ??? isn't very helpful in specifying a package!
>>
> It's better than nothing. Until I wrote this a few days ago, we had
> no package list at all :-).
>
Not really meant to criticize, but ??? gives no guidance as to what to
look for, or w
>I support a fair number with the geni-586 flavor on HP thin clients.
>Some are using or have upped to 0.7.2, and no one really has a
>desire to use Asterisk 1.6 for our application as a gateway to the
>Collectors network. Some are using Cisco 3810's via SIP, a few with
>single port T1, to mate
I support a fair number with the geni-586 flavor on HP thin clients.
Some are using or have upped to 0.7.2, and no one really has a desire to
use Asterisk 1.6 for our application as a gateway to the Collectors
network. Some are using Cisco 3810's via SIP, a few with single port T1,
to mate with
This is what I followed to do my build. However, the docs just kinda
stop right when it gets to the useful part.
On 08/22/2010 01:12 AM, Darrick Hartman wrote:
> Mark,
>
> Please follow this step by step:
>
> http://doc.astlinux.org/devdoc:documentation
>
> Some of those scripts are out-dated a
Before we move the discussion to -devel to bang out the details, why don't we
get a sense of what the users want in bold strokes?
For instance, how many people are running 1.4? How many run 1.6?
And of those running 1.4, how many were waiting for 1.8 so they could skip 1.6
as an interim rele
Philip,
The point of a numbered branch is stability. That's why a majority of
the changes that have happened in trunk will never make it into 0.7. It
doesn't make sense to do so. Branching makes more sense when things
have been tested a bit more thoroughly. I'd have little objection to
bra
13 matches
Mail list logo
