Sorry, I forgotted to mention I meant having that red sentence in home page of
http://www.takenset.us. just a suggestion ;)
Regards,
Yasser.
From: yasser.zam...@live.com
To: lfs-support@linuxfromscratch.org
Date: Sun, 6 May 2012 10:08:43 +0430
Subject: Re: [lfs-support] Automated LFS Program (T
Thanks a lot for helping community by your work. I just have a suggestion:
As LFS has been cited that one of it's main purpose is education, so this is
not bad to have a red bold sentence like something like "Please do not use
Ta-Kenset for your first LFS generation because you'll lose it's edu
Hello,
I have been working on automating the Linux From Scratch build (and
general builds) and
came up with a program that you may find useful (hopefully). I called it
Ta-Kenset (takenset) and
it can be retrieved at http://www.takenset.us.
I've built several LFS systems with
>On Sat, 5 May 2012 09:43:28 -0700 (PDT)
>Fernando de Oliveira wrote:
>
> On 05-05-2012 12:20, Yasser Zamani wrote:
>
> [...]
>
> > One more thing; sometimes I know why to run the script but I don't
> > know how script works exactly. the main example is sed. I know it
> > edits streams to replac
On 05-05-2012 12:20, Yasser Zamani wrote:
[...]
> One more thing; sometimes I know why to run the script but I don't know how
> script works exactly. the main example is sed. I know it edits streams to
> replace or remove something but it's command in book is complicated for me at
> this time
On Sat, 05 May 2012 16:20:45 +0100
Yasser Zamani wrote:
>
> Hi there,
>
> At first thank you very much for this useful site and book!
>
> Currently I'm doing jobs step-by-step with no getting any errors; however,
> sometimes the steps are very specific e.g. GCC pass 2 steps. GCC needs that
>
Yasser Zamani wrote:
> Hi there,
>
> At first thank you very much for this useful site and book!
>
> Currently I'm doing jobs step-by-step with no getting any errors; however,
> sometimes the steps are very specific e.g. GCC pass 2 steps. GCC needs that
> patch, fixincludes should be suppressed,
Hi there,
At first thank you very much for this useful site and book!
Currently I'm doing jobs step-by-step with no getting any errors; however,
sometimes the steps are very specific e.g. GCC pass 2 steps. GCC needs that
patch, fixincludes should be suppressed, -fomit-frame-pointer should be r
On Sat, 2012-05-05 at 17:19 +1200, Gordon Findlay wrote:
> In my perception the book currently assumes that the audience is
> people with some (considerable) understanding of the command-line, and
> OS concepts in general (for example the fact that 'source directory'
> might have different meanings
On Fri, 2012-05-04 at 10:34 -0700, Qrux wrote:
> Would it be hard to put an "unpack_warning" entity before each of the
> "Phase 1" builds (all 2 or 3), or even the "Phase 2" builds (those
> same 2 or 3)?
Hard? No. But would it be productive to do so? If the reader hasn't
understood the basic instr
HI.
Le samedi 05 mai à 01:02, Bruce Dubbs a écrit :
> Qrux wrote:
>
> > If LFS is just a source code project, then to some extent you can say that
> > prose style or organization is irrelevant. It's not, because it's often
> > repeated that it's a book, as well. So, style is important, because
11 matches
Mail list logo
