On 03/13/2011 11:39 PM, DJ Lucas wrote:
> Okay, so I was just thinking...<Deity>
> help us! I figure we have at least 6 months, potentially a year until
> the next major LFS release, and now seems like a pretty good time to
> explore some of the ideas that have been shelved for
On 03/13/2011 11:45 PM, DJ Lucas wrote:
>
>
>> * EGlibC - Seems like Debian and friends are moving to EGlibc, gives us
>> a couple of niceties but nothing major, not sure what other distros are
>> doing, but I've seen a lot of mentions of it recently. The work is
&g
On 03/14/2011 12:03 AM, Nathan Coulson wrote:
On Sun, Mar 13, 2011 at 9:45 PM, DJ Lucas <mailto:d...@linuxfromscratch.org>> wrote:
On 03/13/2011 11:39 PM, DJ Lucas wrote:
> Okay, so I was just
thinking...<Deity>
> help us! I figure we have at least 6
deviated on, and LFS-ized where CLFS differs. You'd be largely on your
own (as I am), but this is no different than where you are now. :-) I
had thought about trying to maintain an internal copy in docbook source,
but it is just entirely too much work and I've got enough of that as is.
Robert Xu wrote:
>On Mon, Mar 14, 2011 at 16:45, Ken Moffat
>wrote:
>> On Sun, Mar 13, 2011 at 11:39:04PM -0500, DJ Lucas wrote:
>>
>>> * Dynamic boot script - No more static list of links, this kind of
>ties
>>> into LSB Bootscripts, but there are othe
Ken Moffat wrote:
>On Sun, Mar 13, 2011 at 11:39:04PM -0500, DJ Lucas wrote:
>
>> * Multi-lib - Shunned previously, but there are many projects that
>> expect this environment.
> For people who build from source, which projects *expect* multilib on
>x86_64 ?
For
On 03/14/2011 08:56 PM, Bruce Dubbs wrote:
> I've read about 15 messages on this topic and will try to incorporate
> the relevant areas in my response.
Thanks.
> Ken Moffat wrote:
>> On Sun, Mar 13, 2011 at 11:39:04PM -0500, DJ Lucas wrote:
>>> Okay, so I was just thin
Andrew Benton wrote:
>
>What would it take to compile a 64 bit system without the /lib
>=> /lib64 symlink (i.e, with the libs installed into /lib and
>no /lib64)? Obviously, it works as it is, it just looks like an ugly
>hack. I'd much rather (for aesthetic reasons) do away with
>{/usr,}/lib64 if
-info /usr/share/info/*.info
Simple enough? :-) This is pretty much the gist of everything in LFS.
The little sample addition was for my own use, but figured I'd leave it
in there for others if they wanted to use something similar.
-- DJ
g ldconfig, and
existing machine specific tasks like the /etc/localtime copy or adding a
configuration file in /etc (3c).
Distribution specific tasks go here. Things like copying skel items to
all users folders and the like simply get tacked on at the end by the
packaging tool, again, not cover
..just building for the heck of it for now in a
test build.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the ab
A warning message is printed when running make in chapter 6 binutils
about not finding /usr/bin/file in a multi-lib build. Can somebody doing
a regular LFS build check your build logs and see if the same is true
for normal LFS?
-- DJ Lucas
--
This message has been scanned for viruses and
On 04/10/2011 10:29 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> A warning message is printed when running make in chapter 6 binutils
>> about not finding /usr/bin/file in a multi-lib build. Can somebody doing
>> a regular LFS build check your build logs and see if the same
On 04/11/2011 07:07 PM, Bruce Dubbs wrote:
> Andrew Benton wrote:
>> On Sun, 10 Apr 2011 22:47:24 -0500
>> DJ Lucas wrote:
>>> It does seem to build correctly, but I don't think it'd be bad to go
>>> ahead and add the symlink with perl when creating t
did an install.
>
> I also tried on a ubuntu system (x86_64) and got no failures at all. I
> did skip the root tests.
>
Same results here. Same two tests failed exactly once. Unable to
reproduce after that. I'd exit chroot and start over, but I'm manually
(slowly) running thro
Going through the book manually for the first time in a while. The
instructions to build readline force linking against the non-wide
libncurses, this actually doesn't matter as the script adds the wide
version, but is there any reason not to explicitly use -lncursesw?
-- DJ Lucas
--
On 04/25/2011 06:21 PM, DJ Lucas wrote:
> is there any reason not to explicitly use -lncursesw?
Additionally, in that same command block, the semicolons and backslashes should
not be necessary unless I'm just missing something.
-- DJ Lucas
--
This message has been scanned for vir
ake maintenance merges between the two much easier, but that
really isn't your responsibility unless you choose to make it so, which
is currently a manual effort.
> So this raises the question of licensing and/or proper
> attribution. From what I can tell, the scripts don't contain a
Jeremy Huntwork wrote:
>On 5/9/11 2:53 AM, DJ Lucas wrote:
>> The simple solution is to stop networking before applying changes.
>When
>
>Yes, I know. :) But in practice that becomes an annoyance. Admins used
>to working Fedora/Debian/Ubuntu or others assume that chan
On 05/09/2011 10:33 PM, Bryan Kadzban wrote:
> DJ Lucas wrote:
>>
>> You know what? I think we are over thinking this. How about a state
>> file? Upon successful initialization of an interface, copy the config
>> file to a subdir of /run/network. The ifdown script source
On 05/10/2011 07:25 AM, DJ Lucas wrote:
> I'm just about done with the DESTDIR POC (still need to add instructions
> to account for lib64 -> lib since I did this on multilib first) but that
> can use some time to mature a bit anyway, so should have time on Wed if
> one of y
Archaic wrote:
>On Tue, May 10, 2011 at 07:25:50AM -0500, DJ Lucas wrote:
>>
>> * ifup - copy configuration file from /etc/network/$int/$file to
>
>> /run/network/$int/$file upon successful initialization of the
>interface.
>
>I believe /var/run is a mo
Jeremy Huntwork wrote:
>On 5/10/11 8:25 AM, DJ Lucas wrote:
>> * Most important, pull as much as possible of the items below
>from
>> LightCube OS's files to ease merging and keep the diffs to a minimum
>so
>> that they are easily shared across distrib
, just drop a text copy in
SVN and it will be there. All of the contributors to the new scripts
have agreed to that license (knowingly or not). The only maintenance
burden comes once a year on Jan 1st.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is
After updating from udev-165 to udev-168, I ran into a timing issue with settle
using tmpfs for /dev. My swap partition failed to mount because the device node
was not present. No other changes than those made to the bootscripts and FS
layout to account for /run. I rebooted a few more times to s
On 05/11/2011 11:14 PM, Bryan Kadzban wrote:
> DJ Lucas wrote:
>> After updating from udev-165 to udev-168, I ran into a timing issue
>> with settle using tmpfs for /dev. My swap partition failed to mount
>> because the device node was not present. No other changes than
On 05/11/2011 11:25 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> After updating from udev-165 to udev-168, I ran into a timing issue
>> with settle using tmpfs for /dev. My swap partition failed to mount
>> because the device node was not present. No other changes than
s folder before
they go into the book and move the old to bootscripts-old afterward.
I'll post a patch for the necessary book, udev-config, and rendering
changes to the list at that time.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and
m ${CONFMODE} etc/init.d/lfs-functions
${EXTDIR}/init.d/lightcube-functions
install -m ${MODE} etc/init.d/halt ${EXTDIR}/init.d/
install -m ${MODE} etc/init.d/console ${EXTDIR}/init.d/
install -m ${MODE} etc/init.d/localnet ${EXTDIR}/init
On 05/14/2011 04:09 PM, Bruce Dubbs wrote:
DJ Lucas wrote:
On 05/14/2011 02:47 PM, Bruce Dubbs wrote:
DJ,
You need to change the version/release date in general.ent and
lfs-bootscripts-version in packages.ent to actually publish the
bootscript changes.
Do you wnat me to do it
On 05/14/2011 04:37 PM, DJ Lucas wrote:
> Everything is covered per this conversation in SVN with the exception of
> accounting for missing /run in LightCube OS, but I think it was decided
> that it would be added. Also no ip flush (I forgot, but will get it in a
> day or two) on do
ny) provides a script
> appropriate to handle the interface shutdown?
>
> Zach
Actually, yeah, that is a great idea! We had planned to merge the dhcp
scripts anyway to simplify Gnome-System-Tools interface management in BLFS.
-- DJ Lucas
--
This message has been scanned for viruses and
dang
On 05/15/2011 01:22 AM, DJ Lucas wrote:
> On 05/15/2011 12:11 AM, Zachary Kotlarek wrote:
>> Could we just do this in ifdown:
>>
>> if [ -x /lib/network-services/dhcp ]; then
>> /lib/network-services/dhcp $interface down
>> fi
>>
>
On 05/15/2011 01:39 AM, Nathan Coulson wrote:
On Sat, May 14, 2011 at 9:36 PM, DJ Lucas <mailto:d...@linuxfromscratch.org>> wrote:
On 05/14/2011 04:37 PM, DJ Lucas wrote:
> Everything is covered per this conversation in SVN with the
exception of
> accounting f
On 05/16/2011 12:59 AM, Bryan Kadzban wrote:
> DJ Lucas wrote:
>>
> I see some traffic on linux-hotplug about this as well, so it looks like
> it's not LFS-specific, at least. (Arch and Debian have both had bugs
> reported about this.) The messages from Kay so far seem
7;ip addr flush $1' to the end of the ifdown script
yet). That is another thing too, now that ifup and ifdown are no longer
in a controlled environment and available to admins without mucking
around in the network-devices tree, some error checking needs to be done
in the scripts for proper a
Bruce Dubbs wrote:
>Zachary Kotlarek wrote:
>> On May 16, 2011, at 12:49 AM, Bryan Kadzban wrote:
>>
>>> I also *think* the only way the cached config might not match the
>>> running config is if root mucked with the running config manually.
>>
>>
>> Or when /run is not writable at the time th
they are much cleaner and easy
to follow now.
Scripts attached for review.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
#!/bin/sh
# Begin /etc/init.d/network
### BEGIN INIT INFO
# Provides:$network
# Required-
e of ONBOOT. Conditions on the value of ONBOOT could actually be
harmful when stopping networking.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscra
if someone wants to
review the script and learn from it. I went ahead and changed all four
examples to inline tests.
>> echo "ERROR: ${INTERFACE} is not a valid network interface."
>> echo ""
>> exit2
> That should be
On 05/16/2011 12:59 AM, Bryan Kadzban wrote:
> DJ Lucas wrote:
>>
> I see some traffic on linux-hotplug about this as well, so it looks like
> it's not LFS-specific, at least. (Arch and Debian have both had bugs
> reported about this.) The messages from Kay so far seem
On 05/14/2011 11:12 PM, DJ Lucas wrote:
> Attached patch is pretty invasive, 33 KB uncompressed. :-) I wasn't
> sure whether to leave inittab in the book where it is currently, but I
> am thinking from a packaging POV that it should remain as is and be
> removed from the bootsc
On 05/18/2011 01:58 PM, Jeremy Huntwork wrote:
> On 5/18/11 1:16 PM, DJ Lucas wrote:
>> Alright, with last commit to lsb-bootscripts, I think we are ready to
>> go. Bruce, Matt, you guys get a chance to review the patch?
> I've been looking over the scripts, they look good,
On 05/18/2011 05:50 PM, Jeremy Huntwork wrote:
> On 5/18/11 1:16 PM, DJ Lucas wrote:
>> On 05/14/2011 11:12 PM, DJ Lucas wrote:
>>> Attached patch is pretty invasive, 33 KB uncompressed. :-) I wasn't
>>> sure whether to leave inittab in the book where it is current
On 05/18/2011 05:50 PM, Jeremy Huntwork wrote:
> On 5/18/11 1:16 PM, DJ Lucas wrote:
>> On 05/14/2011 11:12 PM, DJ Lucas wrote:
>>> Attached patch is pretty invasive, 33 KB uncompressed. :-) I wasn't
>>> sure whether to leave inittab in the book where it is current
Bruce Dubbs wrote:
>Matthew Burgess wrote:
>
>> Firstly, thanks for taking the time to do this, it looks pretty good
>to me.
>
>I haven't had time to review yet.
>
>> Secondly, what follows are probably bike-shed topics, but I'll throw
>my
>> 2p in along with everyone elses anyway :) :
>>
>> mak
Matthew Burgess wrote:
>On Wed, 18 May 2011 12:16:22 -0500, DJ Lucas
>wrote:
>
>> Alright, with last commit to lsb-bootscripts, I think we are ready to
>> go. Bruce, Matt, you guys get a chance to review the patch?
>
>Hi DJ, apologies for the delay, but I've n
On 05/18/2011 08:57 PM, Jeremy Huntwork wrote:
> On 5/18/11 9:26 PM, DJ Lucas wrote:
>> Results of a bad sed? I hadn't noticed that, only fixing the misspelling
>> in the dependencies. Prior to that commit it was "kernel" when it was
>> mountkernfs. Fixing.
&g
On 05/20/2011 03:47 AM, Matthew Burgess wrote:
> On Thu, 19 May 2011 17:25:15 -0500, DJ Lucas
> wrote:
>> Matthew Burgess wrote:
>>
>>> make-aux-files.sh: Why renaming things to lsb-bootscripts? If we're
>>> migrating (which I think we should), shouldn&
On 05/21/2011 07:10 AM, Jeremy Huntwork wrote:
> On 5/21/11 2:48 AM, DJ Lucas wrote:
>> I do plan to add a "service" script later that would alleviate the issue
>> completely, as was suggested by Jeremy a few months ago, but I'm a
>> little stuck as far as ho
On 05/21/2011 11:17 AM, Robert Xu wrote:
> On Sat, May 21, 2011 at 08:10, Jeremy Huntwork
> wrote:
>> On 5/21/11 2:48 AM, DJ Lucas wrote:
>>> I do plan to add a "service" script later that would alleviate the issue
>>> completely, as was suggested by Jerem
On 05/21/2011 12:32 PM, Jeremy Huntwork wrote:
> On 5/21/11 12:52 PM, DJ Lucas wrote:
>> Oh, I didn't realize that it had continued beyond the new network script
>> and ifup/ifdown scripts, or rather I read it as just example, not an
>> actual suggestion. Give me a few
On 05/21/2011 12:20 PM, Bryan Kadzban wrote:
> DJ Lucas wrote:
>> There are a couple of packages, non-obvious packages at that, that
>> install their own bootscripts and they work in the current proposal
>> without modifications using the lsb functions.
> I mus
Okay. There will still be one change to the network script *after* I get
BLFS bootscripts into place.
Attached (revised) patch makes all necessary changes as of 20110523-0515
UTC.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean
e
Either need to roll back the inadvertent commit to the bootscripts
tarball job or move forward with the patch I sent in. Let me know if I
should do this.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.or
ifies the job to always reorder as opposed to trying to
fit a script in between others).
HTH
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
On 05/30/2011 08:19 PM, Bruce Dubbs wrote:
> Dan Nicholson wrote:
>> On Mon, May 30, 2011 at 12:55 PM, Bruce Dubbs wrote:
>>> DJ Lucas wrote:
>>>> On 05/30/2011 12:34 PM, Bruce Dubbs wrote:
>>>>> In the latest svn, the bootscripts are lfs-bootscripts-2
ot--install_initd should be used if available (think
upgrades) with a fallback to a predefined order if not, for new installs.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
F
On 06/06/2011 03:07 PM, Matthew Burgess wrote:
>
> I'd prefer for us not to use HJL's binutils
>
Then don't. That patch doesn't look all that invasive..no need to add
tests for local build fix, just the 3 corrected files (bottom of the list).
-- DJ Lucas
--
This
tentional?
It was done intentionally. I was not aware that anyone had ever used a
file named ifconfig.interface and this was not documented anywhere. I
removed it because it simply because it was one more test case in ifup
and ifdown. I could certainly put it back.
-- DJ Lucas
--
This message has
On 06/07/2011 09:49 AM, Matthew Burgess wrote:
> On Mon, 06 Jun 2011 18:14:59 -0500, DJ Lucas
> wrote:
>> On 06/06/2011 03:07 PM, Matthew Burgess wrote:
>>> I'd prefer for us not to use HJL's binutils
>>>
>> Then don't. That patch doesn't l
d, but I do not recall specifics. Not really sure why
gitorious was chosen over alioth for project home either...curious.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lf
has been a little bit more of a PITA than anticipated. I was having a
bit of difficulty in getting my custom attributes to play nicely, but it
is all resolved now, or at least I hope it is.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clea
.d/functions scripts.
>>
Yes, there is a lot of unused/outdated stuff in there now and much room
for improvement. A complete restart would be good. I'd also like you to
consider using the rc script additions from the LSB bootscripts and some
of the logic from the initd_functions if you d
Moved to LFS-Dev.
On 07/17/2011 07:57 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> On 07/17/2011 02:51 PM, Bruce Dubbs wrote:
>>> DJ Lucas wrote:
>>
>>>> Actually, this check needs to be removed. It causes issues for the alsa
>>>> script and also se
ending the available services can be
reused (although they'll require some modifications). We can even tear
down the interfaces properly based on a running cache constructed the
same way (as was suggested a few weeks ago in the LSB thread).
-- DJ Lucas
--
This message has been scanned fo
On 07/19/2011 12:29 AM, DJ Lucas wrote:
>
> The ifup script greps for all lines containing "^iface $1" (which also
> has the type and service fields), record the line numbers found, get
> type and service from those line numbers (f3 and f4 resp.), next line,
> nex
On 07/19/2011 12:20 AM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>
>> If alsa utils is installed, you should have K links in RLs 0,1,2,6 and
>> no start links as the volume restore is handled by udev.
> No, we don't have anything at RL2. At least not now. The BLFS
st. Every distro provides this now and it might be expected by
some users (especially nice to have on headless systems). Also, since
if{up,down} will be system tools, they need to have help text added at
very least on error...but wait to see what happens when/if the single
config is done.
On 07/12/2011 04:14 PM, Andrew Benton wrote:
> I agree, I'd like to see a hint, but not enough to actually do the work
> myself...
I'd look into it, but I just don't think either are quite ready for
prime time, besides I like the idea of runlevels too much to give them
up j
to?
>
Yes please. I am experiencing this exact issue now on a 32bit cross
build of glibc. I just had a system board failure and apparently the
CMOS battery is dead or near dead. Any possibility that the system time
was the issue William?
make[4]: Warning: File `/tools/include/linux/limit
On 09/01/2011 11:21 PM, Bruce Dubbs wrote:
> Nathan Coulson wrote:
>> Glibc-2.28.8
Pretty sure that the glib version and the glibc version were mixed up.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
According to the home page, we should be applying the upstream patches
found here:
http://www.mpfr.org/mpfr-3.0.1/allpatches
See bugs section at: http://www.mpfr.org/mpfr-3.0.1/
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean
complexity was the main objection. I've not yet had the time
to test Bruce's rewrite.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
kely in hind sight, except for maybe the test runlevel 4, but even
that output would likely be on screen unless you are replacing your
method of remote access.
More to come (along with suggested fixes) when I actually put them into
use over the next couple of days.
-- DJ Luc
Bertrand.
>
Upstream patch committed as procps-3.2.8-fix_HZ_errors-2.patch. Still
needs to be updated in the book.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Taken from cross-lfs:
sed -i 's@\(^#define DEFAULT_EDITOR_PROGRAM \).*@\1"vi"@' lib/config.h
Any reason not to do this in LFS?
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/
On 09/04/2011 11:48 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> On 06/07/2011 05:16 AM, LANOUX Bertrand wrote:
>>> Hi all,
>>>
>>> I have noticed the "unknown HZ value" message still appears at boot
>>> time and under some unpredictable ci
ing 127.0.0.1 entry.
I'm not really sure what to do about actual IPv6 entries as your prefix
will likely change when your router is rebooted unless ISPs start
handing out static /64s (the last 64 bits are stable as they are
assembled from the MAC address with FFFE inserted in the middle).
txt
%ed
I can't see many people using that functionality, but it is configured
incorrectly by default. :-/ Setting the EDITOR environment variable
allows you to change it, but you'll never get the intended functionality
out of any random editor value.
-- DJ Lucas
--
This message ha
l said and done, I feel like I learned a bit
(on a new platform - MikroTik RouterOS), and had to re-learn an awful
lot as well, but IMO, sink or swim is the best possible learning method. :-)
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed t
came to the conclusion that a rewrite was in order as opposed to
'fixing' the
scripts that were already written. I understand that education was the
focus,
but I had thought the judicious use of comments in the extended
functionality
of the LSB scripts would have provided much more ed
On 09/05/2011 11:58 AM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> Taken from cross-lfs:
>>
>> sed -i 's@\(^#define DEFAULT_EDITOR_PROGRAM \).*@\1"vi"@' lib/config.h
>>
>>
>> Any reason not to do this in LFS?
> I have never seen the use o
On 09/05/2011 07:48 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
> > LSB defined functions belong in /lib/lsb/init_functions so that
> compliant
>> bootscripts work as expected. Do not include the LSB definitions directly in
>> the distro's functions file. Either sour
/etc/bash_completion file from the default /etc/profile.
Also, what of /etc/profile.d/ for LFS? Best continued to be left for
BLFS? I would consider it nice to have in a default installation, but
there is nothing that uses it until the 4th package into BLFS for me.
-- DJ Lucas
--
This message ha
On 09/10/2011 11:49 PM, DJ Lucas wrote:
> Grub and GLib both install bash completion scripts. Need to add
> something to the default /etc/profile in the book to take advantage of them.
>
> Additionally, the one for grub is broken currently looking for a have()
> function, which
On 09/11/2011 12:42 AM, DJ Lucas wrote:
>
> I haven't found where the Debian one is developed yet.
>
https://alioth.debian.org/projects/bash-completion/
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxf
On 09/11/2011 12:04 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> On 09/10/2011 11:49 PM, DJ Lucas wrote:
>>> Grub and GLib both install bash completion scripts. Need to add
>>> something to the default /etc/profile in the book to take advantage of them.
>>>
&
On 09/11/2011 12:24 PM, Andrew Benton wrote:
> On Sat, 10 Sep 2011 23:49:36 -0500
> DJ Lucas wrote:
>
>> Grub and GLib both install bash completion scripts. Need to add
>> something to the default /etc/profile in the book to take advantage of them.
>>
> rm -rf /etc
well
in the context of that particular boot script...you could even write a
message for each one if you wanted to have more verbose output in the
event of a failure, or a stepping like we do in mountvirtfs.
> I'd like to see some more discussion about this.
>
> -- Bruce
What ya'll
Bryan Kadzban wrote:
>Nathan Coulson wrote:
>> Another thought (one I have not actually tested, forgive me if It's
>> not possible) is trigger only block devices in the first pass, then
>> try devices/subsystems on the 2nd pass?
>
>DJ Lucas wrote:
>>
istributed version control. Taking it a step further, you have all of
the history of that repo, even dating back to CVS, on at least two other
boxes now. I cannot possibly fathom how that could be a bad thing. I
will probably go through the steps myself just for the learning aspect
of it, but yeah
itten to the
boot log in case color codes are used in screen messages, and reduced
duplication of items in rc.site and init-functions (rc.site is required
for init-functions/rc). Please review, and discuss if necessary, before
commit.
Thanks.
-- DJ Lucas
--
This message has been scanned for virus
On 11/05/2011 04:15 PM, Bruce Dubbs wrote:
> DJ Lucas wrote:
>> Mostly for Bruce, but sent to list for everyone's review:
>>
>> Attached are some fixes for the bootscripts. These are mostly cosmetic,
>> but there are some minor functional changes due in part to reve
On 11/05/2011 06:04 PM, Bruce Dubbs wrote:
> Bruce Dubbs wrote:
>> DJ Lucas wrote:
>>> Mostly for Bruce, but sent to list for everyone's review:
> I had left the definitions
>
> NORMAL="\\033[0;39m" # Standard console grey
> SUCCESS="\\033
ve misunderstood the above comment, you should set libexecdir
back to /usr/lib/coreutils as this has been standard practice in LFS and
BLFS for as far back as I can remember (/usr/lib/). There
are several examples in BLFS for sure, and in both books IIRC.
-- DJ Lucas
--
This message has been
The man-pages download link in the book is incorrect, the correct one is:
http://man7.org/linux/download/man-pages/man-pages-3.35.tar.gz
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman
uble with git, it
will not be available in the chroot environment, but is picked up by
default.
-- DJ Lucas
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch
On 11/26/2011 09:27 PM, DJ Lucas wrote:
> Latest gettext configure can hang in chapter 5 on "checking where .elc
> files should go..." if emacs is installed on the host. Should probably
> add "--without-emacs" and probably "--without-git" to the chapter 5
On 11/26/2011 10:02 PM, DJ Lucas wrote:
> On 11/26/2011 09:27 PM, DJ Lucas wrote:
>> Latest gettext configure can hang in chapter 5 on "checking where .elc
>> files should go..." if emacs is installed on the host. Should probably
>> add "--without-emacs" an
101 - 200 of 551 matches
Mail list logo
