Re: Wireless update (long)

2006-04-01 Thread Archaic
On Fri, Mar 31, 2006 at 11:55:26PM -0600, Bruce Dubbs wrote: > > Overall, I think this is fairly complicated. I'm going to have to think > about what to say in the book. Right now, there seems to be two > packages needed: wireless-tools and madwifi drivers, but there needs to > be a section on c

Re: Wireless update (long)

2006-04-01 Thread Chris Staub
Bruce Dubbs wrote: I've had some success with the wireless. I can now communicate via a wireless card on a LFS system. I've got a built in card and an external PCMCIA card, but I've only checked out the PCMCIA card for now. I don't anticipate any problems though. For the record, this is wha

Re: Wireless update (long)

2006-04-01 Thread lfs
On Sat, April 1, 2006 8:31 am, Archaic wrote: > madwifi is only needed by you. That and many of the drivers you listed in > the kernel config are user-specific. I don't see how the book is going to > do this. Heavy use of the wiki will certainly be required, but there are > so many "ifs" in the equ

Xorg7.0 (Xorg.conf confusion)

2006-04-01 Thread Dan Winkler
Folling the instrctions set forth in the current BLFS svn in the Xorg7.0 section: the install went wonderfully all seems to be working properly out the gate (including my DRM eg no errors I run the test X -config ~/xorg.conf.new and get my test screen with no hard crashes and mouse is moving

Re: Wireless update (long)

2006-04-01 Thread Joe Ciccone
Bruce Dubbs wrote: > $ iwconfig ath0 essid "NETGEAR" channel 11 ap 00:14:6C:09:C9:E7 > This is overkill most of the time. This is what my system does when it udev sees ath0. This can probably be easily incorperated into the bootscripts, I'll play around with it. iwconfig ath0 essid Ciccone && i

Belgarath SSH down?

2006-04-01 Thread Randy McMurchy
Hi all, SSH (port 22) seems to be broken on Belgarath. Note these tests on my private network and Anduin: [EMAIL PROTECTED]: ~/BLFS/BOOK > telnet rmlinux.mcmurchy.prv 22 Trying 192.168.0.222... Connected to rmlinux.mcmurchy.prv. Escape character is '^]'. SSH-1.99-OpenSSH_4.2 [EMAIL PROTECTED]:

BLFS-svn xorg.conf file location

2006-04-01 Thread Dan Winkler
I have followe all the instructions for installing Xorg-7.0 everything went perfect. the test of my `/xorg.conf.new file showed everything working. so I attempted to move it to its final location Per BLFS-svn 03/31/06 E.G mv `/xorg.conf.new /etx/X11/xorg.conf problem is following the X 7 buil

Re: Wireless update (long)

2006-04-01 Thread Bruce Dubbs
Joe Ciccone wrote: > Bruce Dubbs wrote: >> $ iwconfig ath0 essid "NETGEAR" channel 11 ap 00:14:6C:09:C9:E7 >> > This is overkill most of the time. This is what my system does when it > udev sees ath0. This can probably be easily incorperated into the > bootscripts, I'll play around with it. > >

Re: Belgarath SSH down?

2006-04-01 Thread Alexander E. Patrakov
Randy McMurchy wrote: SSH (port 22) seems to be broken on Belgarath. Please fix http://wiki.linuxfromscratch.org/blfs/ticket/1872 to avoid this in the future (assuming that the kernel on Belgarath understands the oom_adj parameter) -- Alexander E. Patrakov -- http://linuxfromscratch.org/ma

Status: FTP Package updates

2006-04-01 Thread Justin R. Knierim
Hi BLFS Devs, I am working on converting the BLFS FTP repo from the previous "bzip2 if at all possible" to the new "original package format" standard. I am finished up to Chapter 13 as of tonight. One thing I wanted to mention: md5sums and sha1sums of the original-format perl modules are av

Re: Belgarath SSH down?

2006-04-01 Thread Bruce Dubbs
Alexander E. Patrakov wrote: > Randy McMurchy wrote: > >> SSH (port 22) seems to be broken on Belgarath. > > Please fix http://wiki.linuxfromscratch.org/blfs/ticket/1872 to avoid > this in the future (assuming that the kernel on Belgarath understands > the oom_adj parameter) Hard to do on Belgar

Re: BLFS-svn xorg.conf file location

2006-04-01 Thread Guy Dalziel
On 02/04/06, Dan Winkler <[EMAIL PROTECTED]> wrote: > E.G mv `/xorg.conf.new /etx/X11/xorg.conf > > problem is following the X 7 build instructions it appears there is no > /etc/X11 directory. At that point I don't believe the /etc/X11 directory exists, and needs to be created in order to move the