Re: [lfs-dev] /sbin/ifup, MTU, bridging, and CHECK_LINK

2012-02-26 Thread Bruce Dubbs
Qrux wrote: > Practically, I've had to change to a lower one for PPP connections, > and higher ones for better gigE throughput. Some people have modems; > others have machines in a data center. > > I don't think it's about the applicability of the setting. I don't either. I was just saying th

Re: [lfs-dev] /sbin/ifup, MTU, bridging, and CHECK_LINK

2012-02-26 Thread Bruce Dubbs
Qrux wrote: > 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, but a general solution is more >> d

Re: [lfs-dev] /sbin/ifup, MTU, bridging, and CHECK_LINK

2012-02-26 Thread Qrux
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" >>> It's getting complicated. We then need to consider address1, dhcp2, >>> etc. What w

Re: [lfs-dev] /sbin/ifup, MTU, bridging, and CHECK_LINK

2012-02-26 Thread Bryan Kadzban
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. I disagree -- assuming by "inettools" you mean "inetutils", because the former is not in LFS. hostname is requir

Re: [lfs-dev] /sbin/ifup, MTU, bridging, and CHECK_LINK

2012-02-26 Thread Bruce Dubbs
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. > > I disagree -- assuming by "inettools" you mean "inetutils", because the > former i

[lfs-dev] ethtool & brctl

2012-02-26 Thread Qrux
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. > > hostname is required for X (it runs "hostname -f"

[lfs-dev] Util-linux arch command

2012-02-26 Thread Bruce Dubbs
I was looking at the instructions for util-linux and notice that we use --enable-arch. Does anyone remember why? When I 'man arch', it says "arch is a deprecated command since util-linux 2.13. Use uname -m or use arch from the GNU coreutils package." I did check coreutils and --enable-ins

Re: [lfs-dev] Util-linux arch command

2012-02-26 Thread Steve Crosby
Added in 6,4 as follows - but no idea why - perhaps the mailing lists in this date range will have a clue •2008-10-11 ◦[randy] - Added three configure parameters to the Chapter 6 Util-linux-ng instructions so that additional programs are installed. Also updated the installed programs list. On M

Re: [lfs-dev] Util-linux arch command

2012-02-26 Thread Bruce Dubbs
Steve Crosby wrote: > On Mon, Feb 27, 2012 at 5:14 PM, Bruce Dubbs wrote: >> I was looking at the instructions for util-linux and notice that we use >> --enable-arch. Does anyone remember why? When I 'man arch', it says >> "arch is a deprecated command since util-linux 2.13. Use uname -m or

Re: [lfs-dev] Util-linux arch command

2012-02-26 Thread Matt Burgess
On Sun, 2012-02-26 at 22:50 -0600, Bruce Dubbs wrote: > Perhaps we should just drop it since neither util-linux nor coreutils > builds it normally and it probably could be replaced with an alias or > script that just does `uname -m`. I'd be happy to see the Util-Linux version dropped. I'm not

Re: [lfs-dev] Util-linux arch command

2012-02-26 Thread Gilles Espinasse
- Original Message - From: "Bruce Dubbs" To: "LFS Developers Mailinglist" Sent: Monday, February 27, 2012 5:50 AM Subject: Re: [lfs-dev] Util-linux arch command > > ◦[randy] - Added three configure parameters to the Chapter 6 > > Util-linux-ng instructions so that additional program

Re: [lfs-dev] Util-linux arch command

2012-02-26 Thread Matt Burgess
On Mon, 2012-02-27 at 08:33 +0100, Gilles Espinasse wrote: > Each configure run arch at 2 different path and look to satisfy from > 'unknow' answer > /bin/arch = `(/bin/arch) 2>/dev/null || echo > unknown` > /usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null |