Well, I pretty much hoped I had more time to prepare for this, but since
Randy brought it up here we go. (gonna be a long one...)
Randy McMurchy wrote:
>
> In my opinion, the book should represent the proper build order
> more than an alphabetical order.
>
+1 !!
I spend the last couple of we
David Ponessa wrote:
> Hello everyone,
>
> Going through SVN-20050711, I found the autofs instructions are
> lacking the configure sentence:
>
> ./configure --prefix=/ --mandir=/usr/share/man
>
> before the make statement...
>
> Bye
>
Hm. I think you're right (cause it won't work for me wit
Bruce Dubbs wrote:
> I have made the changes to the 6.1 branch for the bugs targeted for 6.1
> and set up for -pre2. I've not yet rendered on belgarath. Does anyone
> have any open issues before I generate -pre2?
>
> -- Bruce
Just out of curiosity or lack of understaning:
The fix for the m
Hi.
Two issues with extra-prompt.sh which popped up during my work on the
alfs-profile for blfs-6.1, see:
http://archives.linuxfromscratch.org/mail-archives/alfs-discuss/2005-September/007000.html
First the minor one: If my understandig of extra-prompt.sh as it is in the
book is right, the ou
Bruce Dubbs wrote:
> No, it *supplements* PS1. As the book says:
> "The normal variable, PS1, is supplemented by PROMPT_COMMAND. If set,
> the value of PROMPT_COMMAND is executed as a command prior to issuing
> each primary prompt."
>
> It is meant as an example. We expect users to use it or n
Alex Prinsier wrote:
> When configuring shadow, the blfs profiles don't execute the following
> command:
>
> for FUNCTION in OBSCURE_CHECKS_ENAB CRACKLIB_DICTPATH \
> PASS_CHANGE_TRIES PASS_ALWAYS_WARN
> do
> sed -i -e "s/^$FUNCTION/# &/" /etc/login.defs
> done
>
> The BLFS b
Jeremy Huntwork wrote:
> Torsten Vollmann wrote:
>> First of all for profile-related things it's better to use alfs-dev
>
> alfs-discuss. :)
>
> --
> JH
ups
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.ht
Hi.
I commentet out the export line in the script but still PROMPT_COMMAND is
set and used... Only commenting out the PROMPT_COMMAND line helps
Could it be the export isn't needed at all? Sadly I'm not so deep into bash
programming but always thought things not exported don't make it beyond the
s
Hi.
I would like to discuss the structure of part III - general libraries and
utilities seen from a dependency meeting point of view.
I know it is not quite possible to arrange the whole book in a way that you
can go through it step by step and be able to compile all packages this way,
but at
Hi.
Just a minor glitch:
If I'm not mistaken, there sould be "&&" in the svn instructions for HAL after
the sed-command...
Torsten.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
>
> This would require mkisofs and cdrecord (usually these are the tools
> used), but the Cdrtools package doesn't seem to be listed as a
> dependency for *any* KDE package.
You may want to have a look at k3b (www.k3b.org)
It is not part of the standard kde-packages, but belongs to kde-extra-ge
Gosh - not fast enough :-)
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
12 matches
Mail list logo
