Re: Configuring the network script (Chapter 7) with Debian Lenny as host

2010-03-14 Thread Bruce Dubbs
Simon Geard wrote: > On Sun, 2010-03-14 at 17:19 -0500, Bruce Dubbs wrote: >> that can be an issue on a laptop that has both wireless and wired nics. > > That should be a very rare case, I think. Wireless devices will > generally be named wlan* by the kernel, and wired devices will be eth*. > That

Re: Configuring the network script (Chapter 7) with Debian Lenny as host

2010-03-14 Thread Chris Staub
On 03/15/2010 12:58 AM, Simon Geard wrote: > On Sun, 2010-03-14 at 17:19 -0500, Bruce Dubbs wrote: >> that can be an issue on a laptop that has both wireless and wired nics. > > That should be a very rare case, I think. Wireless devices will > generally be named wlan* by the kernel, and wired devic

Re: Configuring the network script (Chapter 7) with Debian Lenny as host

2010-03-14 Thread Simon Geard
On Sun, 2010-03-14 at 17:19 -0500, Bruce Dubbs wrote: > that can be an issue on a laptop that has both wireless and wired nics. That should be a very rare case, I think. Wireless devices will generally be named wlan* by the kernel, and wired devices will be eth*. That's the case on my desktop (wit

Re: Configuring the network script (Chapter 7) with Debian Lenny as host

2010-03-14 Thread Trent Shea
On Sunday 14 March 2010 16:19:30 Bruce Dubbs wrote: > Trent Shea wrote: > > I just ran a jhalfs build for lfs-6.6 and got hung up in chapter 7's > > "configuring the network script" at the for command. There are no errors > > reported, but no rule created either. I worked around this by booting to

Re: Configuring the network script (Chapter 7) with Debian Lenny as host

2010-03-14 Thread Bruce Dubbs
Trent Shea wrote: > I just ran a jhalfs build for lfs-6.6 and got hung up in chapter 7's > "configuring the network script" at the for command. There are no errors > reported, but no rule created either. I worked around this by booting to the > new system and running the for command again. > >

Re: grep-2.5.4

2010-03-14 Thread Bruce Dubbs
stosss wrote: > There are known test failures in the fmbtest.sh tests. The "|| true" > construct is used to avoid automated build scripts failing due to the > test failures. A good run will show 1 failure from 14 tests, although > the test failure will detail 2 failed sub-tests. That's true, but

Re: grep-2.5.4

2010-03-14 Thread Ken Moffat
On 14 March 2010 20:12, Bruce Dubbs wrote: > guitarje...@radioheadfan.com wrote: >>  Ok. so I am in lfs book 6.6 at section 6.27 grep-2.5.4. Grep has failed 1 >> of 14 tests fmbtest.sh: >> > >> Test #6 F failed: Cosi tu ÄiÅ¡Ã... >> Test #7 F failed: Cosi tu ÄiÅ¡Ã... >> FAIL: fmbtest.sh >>

Configuring the network script (Chapter 7) with Debian Lenny as host

2010-03-14 Thread Trent Shea
Hi, I just ran a jhalfs build for lfs-6.6 and got hung up in chapter 7's "configuring the network script" at the for command. There are no errors reported, but no rule created either. I worked around this by booting to the new system and running the for command again. If someone can confirm t

Re: grep-2.5.4

2010-03-14 Thread Bruce Dubbs
guitarje...@radioheadfan.com wrote: > Ok. so I am in lfs book 6.6 at section 6.27 grep-2.5.4. Grep has failed 1 of > 14 tests fmbtest.sh: > > Test #6 F failed: Cosi tu ÄiÅ¡Ã... > Test #7 F failed: Cosi tu ÄiÅ¡Ã... > FAIL: fmbtest.sh > PASS: yesno.sh > = >

Re: grep-2.5.4

2010-03-14 Thread stosss
On Sun, Mar 14, 2010 at 2:21 PM, wrote: > Ok. so I am in lfs book 6.6 at section 6.27 grep-2.5.4. Grep has failed 1 of > 14 tests fmbtest.sh: > > PASS: warning.sh > PASS: khadafy.sh > PASS: spencer1.sh > PASS: bre.sh > PASS: ere.sh > PASS: pcre.sh > PASS: status.sh > PASS: empty.sh > PASS: option

grep-2.5.4

2010-03-14 Thread guitarjerry
Ok. so I am in lfs book 6.6 at section 6.27 grep-2.5.4. Grep has failed 1 of 14 tests fmbtest.sh: PASS: warning.sh PASS: khadafy.sh PASS: spencer1.sh PASS: bre.sh PASS: ere.sh PASS: pcre.sh PASS: status.sh PASS: empty.sh PASS: options.sh PASS: backref.sh PASS: file.sh PASS: foad1.sh Test #6 F