headers
Paul Estep | 1 Jan 2006 20:17
Picon
Favicon

re: lfs-builder

Hail
I too was interested in something different than the xml based scripting that alfs was built on. Like you Ario I created my own Bash scripts. I was interested in looking to see how you handled certain issues with bash scripting LFS commands. I did not install your build scripts, I like my own of course, but I did looked them over.
In escript/lib/escript/iwatch there is a reference to lib/escript/installwatch.so. I couldn't figure out if this was a library built when I installed your scripts or something that had to be installed previously.
Is the installwatch.so built with the lfs-6.1.1-builder.tar.bz2 scripts that you attached?
I also looked at the hint you submitted but didn't see any reference to it either.
Lastly thanks for your Building LFS with Xlfsbook hint.
Paul Estep
 
--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 1 comment |
headers
Thomas Pegg | 1 Jan 2006 23:05
Picon
Favicon

Re: clfs profile for use with alfs

AJ Lewis wrote:
> Hey all,
> 
> I was just wondering if someone already had a clfs profile to use  with 
> the alfs project.  I'm building x86_64 multilib, and would like  to use 
> alfs to do it, but I thought I'd check here before I went and  did all 
> the profile modifications myself.

Sorry for a late reply on this, but a profile is in the works, it's not 
finished as of yet, but you can check out what's currently in SVN from 
here: svn://svn.linuxfromscratch.org/ALFS/profiles/CLFS/trunk

Thomas

--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Thomas Pegg | 1 Jan 2006 23:25

State of ALFS

Hello all, this is the first of hopefully a series of monthly (perhaps 
weekly) messages, giving a basic summary of where things stand within 
the ALFS project.

nALFS and alfs:
Currently with nALFS, potentially a new 1.2.6 release will happen due to 
a recent report of some file corruption when using the [search_replace] 
element, plus a fix for display of line drawing characters when in UTF-8 
   mode.

alfs development seems to have stalled a bit again, but we'll see if we 
can't get that hopping again. We had some good progress on the 
communication protocol, we may want to see if we can work on refining 
that some, as well as work on some means of authentication next.

The Profiles:
I believe the LFS profile is lagging a little behind current trunk. The 
profile for CLFS is progressing, still some work to be done and major 
testing on arches I don't have available for testing, mainly all arches 
other than x86 and x86_64.

Now for the BLFS profile, this beast needs major work, but really we 
need more hands to help with it, myself and Joachim just is not enough 
anymore. This brings another question do we want to keep maintaining 
this profile? BLFS is such a fast moving target it seems a bit 
impossible currently. I personally would like to see it continue, but I 
currently have no time to keep up with it anymore, my plate is full 
enough with LFS and CLFS and I know Joachim's time is limited.

Comments?

Thomas
--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 5 comments |
headers
Richard A Downing | 2 Jan 2006 08:08
Picon
Gravatar

Re: State of ALFS

On Sun, 01 Jan 2006 17:25:09 -0500
Thomas Pegg <tom <at> tpegg.org> wrote:

<snip> 
> Now for the BLFS profile, this beast needs major work, but really we 
> need more hands to help with it, myself and Joachim just is not
> enough anymore. This brings another question do we want to keep
> maintaining this profile? BLFS is such a fast moving target it seems
> a bit impossible currently. I personally would like to see it
> continue, but I currently have no time to keep up with it anymore, my
> plate is full enough with LFS and CLFS and I know Joachim's time is
> limited.

I think that until you can derive the profiles automatically from the
book's xml source you will never have enough resources to keep up with
BLFS.  The profiles are considerably more complex than most (c)LFS
ones, and they change in 'substance' more often (not just version
numbers).

R.

--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Robertus Ario Jatmiko | 2 Jan 2006 09:40
Picon

re: lfs-builder


--- Paul Estep <epdagger <at> sbcglobal.net> wrote:

> Hail
>   I too was interested in something different than
> the xml based scripting that alfs was built on. Like
> you Ario I created my own Bash scripts. I was
> interested in looking to see how you handled certain
> issues with bash scripting LFS commands. I did not
> install your build scripts, I like my own of course,
> but I did looked them over.
>   In escript/lib/escript/iwatch there is a reference
> to lib/escript/installwatch.so. I couldn't figure
> out if this was a library built when I installed
> your scripts or something that had to be installed
> previously.
>   Is the installwatch.so built with the
> lfs-6.1.1-builder.tar.bz2 scripts that you attached?
>   I also looked at the hint you submitted but didn't
> see any reference to it either.
>   Lastly thanks for your Building LFS with Xlfsbook
> hint.
>   Paul Estep

Hi Paul,

Thanks for your interest on this lfs-builder :).
The actual installwatch.so library file can be found
in the installwatch package from the following
website:

http://asic-linux.com.mx/~izto/checkinstall/installwatch.html

Technically, as you can see in the lfs-builder
package, the 'escript' directory is the key of this
lfs-builder project. Escript was written far before I
had the idea of implementing this lfs-builder. So,
escript is actually a separate implementation. You can
found more technical information regarding escript in
escript/README and escript/INSTALL. The reference to
lib/escript/installwatch.so was there because I
plainly copied the whole 'escript' directory to the
lfs-builder directory.

However, I'm currently working on the lfs-builder that
uses the installwatch features. With these features,
lfs-builder can uninstall, archive installed packages,
reinstall, and many things that can make lfs-builder
be a package manager for LFS :).

Hope this will answer your queries. Thanks again for
having the time to read the hint I submitted (although
it is not posted).

Regards,
Ario

  I like Salmonfish .

Send instant messages to your online friends http://au.messenger.yahoo.com 
--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Thorsten von Eicken | 2 Jan 2006 10:30

it boots!

Brief report from a pretty excited fellow whose nALFS build and first 
LFS build finally booted! It's not a straightforward nALFS build. I'm 
building on an i686 for an embedded i486 board (a pcengines WRAP board). 
I've been looking for a while for a small-but-not-tiny linux 
distribution that runs a 2.6 kernel and on which I can run a full 
packaging system. I've been using 256MB CF cards and now 512MB (they're 
under $35 a pop so I don't see a point in trying to fit into less), 
which mean I have a little bit of luxury in the space department.

I modified the 6.1 profile and it fits into 208MB without even stripping 
all executables. The most exciting part is that gcc works (no, I'm not 
gonna compile huge software packages on a 266Mhz i486 with just a CF 
card for storage):
   -bash-3.00# cat foo.c
   #include <stdio.h>
   main(){printf("Hello World!\n");}
   -bash-3.00# gcc -o foo foo.c
   -bash-3.00# ./foo
   Hello World!
   -bash-3.00#

Anyway, the bottom line is THANKS A MILLION for LFS and nALFS! This 
would have been soo much more work without all this! What I have is far 
from being redistributable, but if anyone is actively trying to do 
something similar I'd be very interested in comparing notes.

Cheers,
	Thorsten
--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 1 comment |
headers
Артур Демченков | 2 Jan 2006 13:17
Picon

Re: alfs-discuss Digest, Vol 602, Issue 1

> Now for the BLFS profile, this beast needs major work, but really we 
> need more hands to help with it, myself and Joachim just is not enough 
> anymore. This brings another question do we want to keep maintaining 
> this profile? BLFS is such a fast moving target it seems a bit 
> impossible currently. I personally would like to see it continue, but I 
> currently have no time to keep up with it anymore, my plate is full 
> enough with LFS and CLFS and I know Joachim's time is limited.
> 
> Comments?
> 
> Thomas

I could work on 1 chapter (for now) of BLFS book. Is that ok?
--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
mark gross | 2 Jan 2006 17:20

Re: State of ALFS

Thomas Pegg wrote:

> Hello all, this is the first of hopefully a series of monthly (perhaps 
> weekly) messages, giving a basic summary of where things stand within 
> the ALFS project.
>
> nALFS and alfs:
> Currently with nALFS, potentially a new 1.2.6 release will happen due 
> to a recent report of some file corruption when using the 
> [search_replace] element, plus a fix for display of line drawing 
> characters when in UTF-8   mode.
>
> alfs development seems to have stalled a bit again, but we'll see if 
> we can't get that hopping again. We had some good progress on the 
> communication protocol, we may want to see if we can work on refining 
> that some, as well as work on some means of authentication next.
>
>
> The Profiles:
> I believe the LFS profile is lagging a little behind current trunk. 
> The profile for CLFS is progressing, still some work to be done and 
> major testing on arches I don't have available for testing, mainly all 
> arches other than x86 and x86_64.
>
> Now for the BLFS profile, this beast needs major work, but really we 
> need more hands to help with it, myself and Joachim just is not enough 
> anymore. This brings another question do we want to keep maintaining 
> this profile? BLFS is such a fast moving target it seems a bit 
> impossible currently. I personally would like to see it continue, but 
> I currently have no time to keep up with it anymore, my plate is full 
> enough with LFS and CLFS and I know Joachim's time is limited.

After I finish wading throught the BLFS (I've just finished building QT 
and GTK+) I hope to start looking at the automated build systems. 

Its too soon to tell if I'm going to be able to help with keeping the 
thing up to date, but I would like to see it continue as well.

--mgross

>
>
>
> Comments?
>
>
>
> Thomas

--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |
headers
Jamie Bennett | 3 Jan 2006 21:04

Re: State of ALFS

On Sun, 2006-01-01 at 17:25 -0500, Thomas Pegg wrote:
> Hello all, this is the first of hopefully a series of monthly (perhaps 
> weekly) messages, giving a basic summary of where things stand within 
> the ALFS project.

Good to hear.

> nALFS and alfs:
> Currently with nALFS, potentially a new 1.2.6 release will happen due to 
> a recent report of some file corruption when using the [search_replace] 
> element, plus a fix for display of line drawing characters when in UTF-8 
>    mode.

Good call. Any bug as serious as this should warrant a point release.

> alfs development seems to have stalled a bit again, but we'll see if we 
> can't get that hopping again. We had some good progress on the 
> communication protocol, we may want to see if we can work on refining 
> that some, as well as work on some means of authentication next.

Do we have a definitive answer documented on what the finished profile
syntax is going to be? Also is there a todo list somewhere? bugzilla?
Now that I'm back in the land of the connected it would be nice to get
my teeth into something. 

I think along side the authentication work, some form of extensive
logging should be thought about. Logging, especially in LFS and the land
of ICA testing, is essential and the more detailed the logs are the more
likely the new tool will be adopted by the mainstream LFS builders.

> 
> The Profiles

Snip.

I believe that with the work done on jhlfs it has shown that the correct
way forward from here should be to auto-generate the profiles. A jhlfs
Makefile->profile hack in perl/python would be all that is needed to
generate the book profiles using jhlfs to download and parse the book.

> Comments?

Keep up the good work ;)

> Thomas

Jamie

--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 1 comment |
headers
Jamie Bennett | 3 Jan 2006 21:05

Re: it boots!

On Mon, 2006-01-02 at 01:30 -0800, Thorsten von Eicken wrote:
> Brief report from a pretty excited fellow whose nALFS build and first 
> LFS build finally booted! 

Always good to hear the positive (and not so positive) user reports :)

> I modified the 6.1 profile and it fits into 208MB without even stripping 
> all executables. 

Care to share what you modified to get it that small?

> 	Thorsten

Jamie

--

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Permalink | Reply | 0 comments |

Gmane