On Jun 2, 2012, at 9:22 PM, Bruce Dubbs wrote:
> This is mostly for Matt, but others may take note.
>
> I was adding new pages to LFS and had a hard time getting pkg-config to
> be recognized by jhalfs. What I found out was that the xml code:
>
>
>
> and the file name
>
> pkg-config-0.
On May 20, 2012, at 1:58 PM, Jeremy Huntwork wrote:
> On 5/20/12 3:10 PM, Bruce Dubbs wrote:
>>> This exact reason, for the record, is why I really dislike binary
>>> distros. I *never* choose the same set of dependencies that are
>>> optional in the source, as the distro does. And because when
On May 18, 2012, at 9:01 AM, Andrew Benton wrote:
> Qrux wrote:
>>
>> BTW, which mail client(s) are folks using that don't wrap
>> automatically?
>
> It doesn't matter what mail readers other people are using...
I disagree. I believe the subject of &qu
On May 18, 2012, at 8:12 AM, Jeremy Huntwork wrote:
> On 5/18/12 5:22 AM, Qrux wrote:
>> But, let's not make it a crime to clarify. If Ken would rather assert
>> that I'm not "new" to the community, then to the extent that his
>> assertion is valid I
On May 17, 2012, at 7:06 PM, Bruce Dubbs wrote:
> Since you are using Applemail, I think the problem is that it is using \r for
> newlines instead of \n. I see your mail wrapped, but when replying, it
> doesn't
> wrap automatically. It's easy enough fo rme to to edit->rewrap though.
That's
On May 17, 2012, at 5:25 PM, Ken Moffat wrote:
> On Thu, May 17, 2012 at 04:37:24PM -0700, Qrux wrote:
>>
>> Console fonts (and asking people to build FB support in kernels) seem like a
>> waste of effort when most people probably spend 99% of their time SSH'ed
On May 17, 2012, at 3:50 PM, Ken Moffat wrote:
> On Thu, May 17, 2012 at 03:38:00PM -0700, Qrux wrote:
>>
>> Is the rationale for kbd inclusion in LFS (as opposed to BLFS) the fact that
>> there are international users who don't have US keyboards?
>
> Even fo
On May 17, 2012, at 3:28 PM, Ken Moffat wrote:
> On Thu, May 17, 2012 at 02:33:16PM -0700, Qrux wrote:
>> So, we have a program that has these complex interactions, and...provides
>> console size/font management? What is the use-case here?
>
> I would hope that is true
On May 17, 2012, at 3:05 PM, Bruce Dubbs wrote:
>> Which I would claim in 2012 is completely bull. How many devs do you know
>> dev straight on the console? Of the oft-quoted tens-of-thousands who've
>> downloaded LFS, what percentage of them develop on the console?
>
> Actually, I do a lot vi
On May 17, 2012, at 12:31 PM, Ken Moffat wrote:
> On Thu, May 17, 2012 at 01:17:46PM +0800, xinglp wrote:
>> Does the 'setfont' resize the console on the fly as change the
>> "vga=xxx" of grub do.
>> The behavior of changing console's resolution on the fly is usefull
>> when use a "live" lfs.
>>
On May 4, 2012, at 8:08 AM, Scott Robertson wrote:
>> Maybe I'm missing something, but I think that entire paragraph could be
>> removed. The book gives the command to mount the LFS partition as:
>
>> mount -pv $LFS -v -t ext3 /dev/ $LFS
>
>> And then warns, effectively, that if you did someth
On Apr 7, 2012, at 6:05 PM, Bruce Dubbs wrote:
> Qrux wrote:
>> On Apr 6, 2012, at 3:24 PM, Bruce Dubbs wrote:
>>
>>> Qrux wrote:
>>>
>>>> 1) Why is ifup bringing up the virtual interface? That is
>>>> clearly a service-level res
On Apr 6, 2012, at 3:24 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> 1) Why is ifup bringing up the virtual interface? That is clearly a
>> service-level responsibility. In fact, in the case of a bridge, that
>> interface doesn't even exist until you create it with
On Apr 6, 2012, at 12:56 PM, Bruce Dubbs wrote:
> I've tried moving some things around on my development system and would like
> some feedback.
>
> For a bridge, br0, I have:
>
> ifconfig.br0
>
> ONBOOT=yes
> IFACE=br0
> SERVICE="bridge ipv4-static"
> IP=192.168.0.22
> GATEWAY=192.168.0.1
> P
On Mar 30, 2012, at 8:28 PM, Bruce Dubbs wrote:
>> In fact, ifdown should *only* set DOWN when there are no IP configs
>> still attached to the logical interface. If there *is* an IP config
>> still attached to the logical interface, then ifdown should just
>> report a warning that it cannot set
On Mar 30, 2012, at 8:28 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> Hopefully no one is relying on that functionality. And, those who are
>> should be doing it through their own customs scripts. IMO, that's bad
>> behavior.
>
> The nature of LFS is that use
On Mar 30, 2012, at 9:42 AM, xinglp wrote:
> 在 2012年3月31日 上午12:05,Bruce Dubbs 写道:
>> xinglp wrote:
>>> http://www.linuxfromscratch.org/lfs/view/development/scripts/apds27.html
>>>
>>> if [ "$(ip addr show ${IFACE} | grep 'inet ')" != "" ]; then
>>> log_info_msg "Bringing down th
On Mar 30, 2012, at 9:05 AM, Bruce Dubbs wrote:
> xinglp wrote:
>> http://www.linuxfromscratch.org/lfs/view/development/scripts/apds27.html
>>
>> if [ "$(ip addr show ${IFACE} | grep 'inet ')" != "" ]; then
>> log_info_msg "Bringing down the ${IFACE} interface..."
>> ip lin
On Mar 29, 2012, at 12:31 AM, Simon O'Riordan wrote:
> I've been searching for about a week and am now going over old links, so I
> think
> I may have exhausted the literature.
> I'm not (yet) an expert on networking LFS.
> What I want to do is add a dhcp ethernet interface to a bridge.
> I am t
On Mar 22, 2012, at 2:20 PM, Bruce Dubbs wrote:
>> # ip addr show eth0
>> 2: eth0: mtu 1500 qdisc pfifo_fast state
>> UP qlen 1000
>> link/ether 00:1e:4f:f8:00:39 brd ff:ff:ff:ff:ff:ff
>> inet 172.16.24.1/24 brd 172.16.24.255 scope global eth0
>> inet 172.16.24.2/24 brd 172.16.24.255 scope
On Mar 17, 2012, at 2:38 PM, Bruce Dubbs wrote:
>> Bruce Dubbs wrote:
>>
>>> Matt and I are very reluctant to change a working
>>> implementation.
>> ...
> Until gcc-4.7 comes out I'm recommending we use the exiting jh
--> ^^^
> branch of lf
On Mar 17, 2012, at 2:38 PM, Bruce Dubbs wrote:
>> Bruce Dubbs wrote:
>>
>>> Matt and I are very reluctant to change a working implementation.
>>> From what we can gather, gcc-4.7/glibc-2.15(?) changes things and will
>>> require some LFS changes. We need to be concentrating on that.
>>
>
On Mar 15, 2012, at 12:09 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> IMO, LVM and mdraid should be done super-early (whether embedded in
>> some other script or separated into their own). It should go right
>> after modules are loaded (S05modules in rcS.d, so maybe S06L
On Mar 15, 2012, at 12:09 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> IMO, LVM and mdraid should be done super-early (whether embedded in
>> some other script or separated into their own). It should go right
>> after modules are loaded (S05modules in rcS.d, so maybe S06L
On Mar 15, 2012, at 9:02 AM, Bruce Dubbs wrote:
> Nathan Coulson wrote:
>> S30checkfs, we added
>>
>> # If any LVM based partitions are on the system, ensure they
>> # are activated so they can be checked/used.
>> if [ -x /sbin/vgchange ]; then
>> /sbin/vgchange -a y >/dev
On Mar 10, 2012, at 7:29 AM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> Bruce, et al, was the 7.1-release built from 7.0-release on bare-metal? VM?
>> Non-LFS host?
>
> My particular 7.1 system was built on 7.0 with a 3.0.4 kernel, but
> others built it from diff
On Mar 10, 2012, at 1:45 AM, Pierre Labastie wrote:
> Le 10/03/2012 09:57, Pierre Labastie a écrit :
>> Sorry, I really meant the tests pass. I didn't send the
>> not-so-informative result of the test:
>> PASS: test-readlink.
>>
>> Whatever I do, I never see an error. Even with the 3.2.6 kernel
On Mar 10, 2012, at 12:57 AM, Pierre Labastie wrote:
> Le 10/03/2012 02:32, Qrux a écrit :
>> Thanks for all the responses (I'm still looking through some info Pierre
>> sent me).
>>
>> @Pierre: I'm talking about *testing* m4 (in Chap 6). If you'
On Mar 9, 2012, at 8:21 PM, Bruce Dubbs wrote:
> Qrux wrote:
>> Howdy.
>>
>> In trying to build LFS-7.0 with LFS-7.0, I'm getting this error:
>>
>> FAIL: test-readlink (exit: 134) ===
>
> Did you see: http://lists.gnu.o
On Mar 9, 2012, at 6:25 AM, g@free.fr wrote:
>> sed -i -e '41s/ENOENT/& || errno == EINVAL/' tests/test-readlink.h
>>
>> OOH, it doesn't appear to be a "huge issue", so the sed is
>> nice...OTOH, it's still a red flag because I don't see this issue
>> when building from my host platform
Howdy.
In trying to build LFS-7.0 with LFS-7.0, I'm getting this error:
FAIL: test-readlink (exit: 134)
===
test-readlink.h:41: assertion failed
It seems to be a fairly well-known issue:
http://old.nabble.com/test-readlink-failure-td3
On Mar 4, 2012, at 7:10 AM, Jeremy Huntwork wrote:
> On 3/1/12 4:27 PM, Jeremy Huntwork wrote:
>> And because of the pre-adjusting there's even less chance to bring in
>> something from the host system. The limits.h file is an example. The
>> first pass of GCC doesn't install a full-featured limi
On Mar 4, 2012, at 8:46 AM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> Does anyone know of any actual vulnerabilities in LFS-proper (either
>> 7.0 or 7.1)?
>
> If we knew/know of any specific vulnerabilities, we'd address them.
Is this necessarily the case?
Aren
On Mar 4, 2012, at 3:25 AM, Ken Moffat wrote:
> On Sun, Mar 04, 2012 at 12:32:32AM -0800, Qrux wrote:
>>
>> Does anyone know of any actual vulnerabilities in LFS-proper (either 7.0 or
>> 7.1)?
>>
> The most recent perl vulnerability came to light after 7.0 was
&g
On Mar 3, 2012, at 12:18 PM, Ken Moffat wrote:
> On Sat, Mar 03, 2012 at 01:50:13PM -0500, Jeremy Huntwork wrote:
>> On 3/3/12 1:11 PM, Qrux wrote:
>>> The security issues with production has been mentioned several times.\
>> I think the reason this comes up is bec
On Mar 3, 2012, at 8:57 AM, Ken Moffat wrote:
> and
> you understand the security risks, then don't let me stop you.
I appreciate the clarification of what you mean when you say "production." I
sort of assume that that's always the case: "Your computers are only as secure
as the competence o
On Mar 2, 2012, at 8:07 PM, Bruce Dubbs wrote:
> Qrux wrote:
>> On Mar 2, 2012, at 4:26 PM, James Robertson wrote:
>>> On Mar 1, 2012 2:49 PM, "Ken Moffat"
>>> wrote:
>>>> Actually, we used to have a guy who did run production servers -
>
your builds, I'd love to compare notes. You can see my
work here: https://github.com/qrux/xlapp. It's an automated build for
virtualization using Xen with LFS as the base system. It provides a few server
"types" (DNS, smtp/imap, and a LAPP stack). The README is now pretty
On Mar 1, 2012, at 12:38 PM, Ken Moffat wrote:
> On Thu, Mar 01, 2012 at 11:30:00AM -0800, Qrux wrote:
>>
>> You're point seems to boil down to: "Don't overreact. 95% of stuff will
>> work."
>
> You could, with equal justification, have sai
On Mar 1, 2012, at 12:18 PM, Jeremy Huntwork wrote:
> On 3/1/12 2:30 PM, Qrux wrote:
>
>> Why not pursue a course more like: "Let's get some downstream (e.g., BLFS,
>> CLFS) people to see what the actual impact of my proposed changes will be to
>> actua
On Mar 1, 2012, at 11:55 AM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> I'm not sure why there's so much opposition to it.
>
> There isn't opposition to testing, but who is going to do all the
> testing needed?
If we're asking buy questions, we&
On Mar 1, 2012, at 9:32 AM, Jeremy Huntwork wrote:
> I'm saying that if you are compiling the libs and binaries, it should
> conform to the configuration of your toolchain. I say 'should'
I never said your way of building the toolchain is wrong--I haven't even
looked. I'm sure it's great. I'
On Mar 1, 2012, at 10:40 AM, Andrew Benton wrote:
> On Thu, 1 Mar 2012 08:43:05 -0800
> Qrux wrote:
>
>> [~/lfs/src/openssl-1.0.0e] # grep ENGINESDIR $(find . -name "*.c" -o -name
>> "*.h")
>> ./crypto/engine/eng_list.c: if((load_dir
On Feb 29, 2012, at 10:46 PM, Jeremy Huntwork wrote:
> Just to be clear - the BIND code itself shouldn't care about lib or
> lib64.
What, specifically, are you addressing when you say "shouldn't care"? Are you
speaking theoretically about how BIND should be designed? Or practically,
based o
On Feb 29, 2012, at 7:03 PM, Jeremy Huntwork wrote:
> On 2/29/12 8:21 PM, Qrux wrote:
>>> It was me that put that in the BLFS page. Thanks for your email to BLFS
>>> dev about the problem with Bind.
>>
>> Why did we go in this circle?
>
> Because
On Feb 29, 2012, at 12:30 PM, Andrew Benton wrote:
> It was me that put that in the BLFS page. Thanks for your email to BLFS
> dev about the problem with Bind.
Why did we go in this circle?
I said BIND needed, minimally, a symlink at /lib64 to work. I realize that
that case is somewhat minor,
On Feb 29, 2012, at 3:59 AM, Andrew Benton wrote:
> On Tue, 28 Feb 2012 17:02:59 -0800
> Qrux wrote:
>
>> I don't think anyone referred to precomp bins. I presume all discussions
>> here are about source builds.
>>
>> 1) Which BLFS version?
>
&g
On Feb 28, 2012, at 4:43 PM, Andrew Benton wrote:
> On Tue, 28 Feb 2012 15:15:27 -0800
> Qrux wrote:
>
>> As for the "64-bit" works in practice...BIND is an example of a downstream
>> app that seems to want to look in /lib64. Whether it's looking for
&g
On Feb 28, 2012, at 8:29 AM, Jeremy Huntwork wrote:
> On 2/28/12 10:42 AM, Andrew Benton wrote:
>> Multilib is only of use if you want to run legacy binaries such as
>> windows programs with wine.
>
> Building Xen from source also required a 32bit libc, presumably for
> supporting 32-bit hosts,
On Feb 27, 2012, at 7:49 PM, Jeremy Huntwork wrote:
> I've revised a local copy of the latest book to include some build
> adjustments. The original concept was suggested on this list a couple
> years ago by Ryan Oliver. I've been using it and adjusting it for the
> past couple of years. It's how
On Feb 27, 2012, at 4:35 PM, Nathan Coulson wrote:
> On Sun, Feb 26, 2012 at 12:22 PM, Qrux wrote:
>>
>> When all is said and done, I'm talking about two tiny little "packages"
>> (bridge-utils and ethtool) that amount to probably 2 executables that
>&g
On Feb 26, 2012, at 10:20 AM, Bryan Kadzban wrote:
> Qrux wrote:
>> For 7.2 & beyond...
>>
>> Bridge-utils is not dissimilar from udev, in that it's a userspace
>> tool for a kernel. And, it's certainly no less optional than
>> inettools.
>
On Feb 26, 2012, at 9:05 AM, Bruce Dubbs wrote:
> Qrux wrote:
>> On Feb 25, 2012, at 8:12 PM, Bruce Dubbs wrote:
>>
>>> Qrux wrote:
>>>
>>>> Probably something like:
>>>>
>>>>BRIDGE_PORTS="eth0 eth1"
>>&
On Feb 25, 2012, at 8:12 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>> Probably something like:
>>
>> BRIDGE_PORTS="eth0 eth1"
>
> It's getting complicated. We then need to consider address1, dhcp2,
> etc. What we have now works for kvm,
On Feb 25, 2012, at 8:09 PM, Bruce Dubbs wrote:
> Qrux wrote:
>
>>> if test -n "${MTU}"; then
>>> if [[ ${MTU} =~ ^[0-9]+$ ]] -a [[ $MTU -ge 68 ]] ; then
>>>ip link set dev ${IFACE} mtu $MTU
>>> else
>>>echo "Invalid
On Feb 25, 2012, at 6:49 PM, Bruce Dubbs wrote:
> Qrux wrote:
>> On Feb 25, 2012, at 9:14 AM, Bruce Dubbs wrote:
>
>> Still, it seems awfully specious to say: "It's only the number of
>> files that needs to coincide; everything else is gravy." The files
On Feb 25, 2012, at 9:14 AM, Bruce Dubbs wrote:
> Qrux wrote:
>> Bruce, Nathan, et al.,
>>
>> Bridging sort of "inverted" the semantics
>> of /lib/lsb/ by setting IFACE to the bridge interface. It
>> inverted the semantics in ipv4-static. I just a
ssue with
bridge, because bridge didn't use the positionals; it just used $IFACE and
$INTERFACES, but "backwards".
Scripts below. Search for #QRUX for my edits. Nathan, bridge is mostly yours;
mind taking a quick look to see if I didn't completely bork it? The scripts
are
Nathan, et al.,
In Aug of last year (2011), you posted a bridge-utils proposal:
http://www.linuxfromscratch.org/pipermail/blfs-dev/2011-August/021129.html
And along with the script, included a patch which looks like this:
Patch for latest LFS **
#!/bin/sh
###
59 matches
Mail list logo