Text 5549, 89 rader
Skriven 2006-03-22 22:59:04 av James Bradley (1:134/77.0)
     Kommentar till en text av Maurice Kinal
Ärende: 802.11g, eth0/1, dhcpcd.
================================
Maurice Kinal wrote James Bradley on 03-20-06 12:59

 JB> fallback, and check for any other DH buddies.

 MK> Okay.  I've never looked at gentoo rc scripts so
 MK> I have no idea how they do things.

I'm sitting right behind them, and I can't tell you, "how they do things." <L>

 MK> Sure.  :-)  What is wrong with eth0 btw?

I'm suspecting a few things. After I rebuilt the kernel, and installed dhcp,
*and* instituted static addressing... I can't paste from other consoles for
some reason right now, but quickly:

ifconfig      eth0 shows no   IRQ/I-O
       eth1 shows   5/0x240

So I'm suspecting a resource issue at the moment, but I really have no need for
two NICs in the same machine with the new toys - er, I mean tools - in the mix.
When I was running nothing but cross-over, and thin coax it would have been
more an issue. I might troubleshoot this by passing arguements for eth0, but
chances are good I will remove 0, promote 1 and call it a day.

 MK> Probably.  I've never had a networking usb
 MK> thingy so I am just guessing here.  Apparently
 MK> there are firewire cables that will also
 MK> network, not unlike serial null modem cables,
 MK> but I have never done anything over firewire so
 MK> I know nothing about that either.

I've also read (here?) about using USB-2 as an ad-hock network. Pretty fast,
from WIR, but I imagine the distances may not be great.

 JB> instructions, on when to "click the mouse on the 'Next' button" for

 MK> Heh, heh.  I hate those things but apparently
 MK> most people seem to think they need them in
 MK> order for their computer to operate properly.
 MK> They can keep it.

What, in the bathtub next to the toaster that didn't come with instructions?
<giggle>

 MK> using dumb terminals on vax/vms and then later
 MK> Sparc stations, and all the hardware stuff was
 MK> taken care of for me so I just used it.  Linux

Now you're just teasing me. I have two high resolution (ISO whatever) dumb
terminals in my basement, that were the cat's pajamas in the mid->late
nineties. I just bought two 19" flat screen Dell CRT monitors at auction
earlier today. (Rebranded Sony Trinitrons by the looks.) Shesh... Sure glad AB
has a recycling program in effect. <EG>

 MK> is where I learned the more hardcore stuff since
 MK> there was nobody around to do it for me and it
 MK> was always my dime.  However having unix
 MK> experience from a user's perspective sure didn't
 MK> hurt me any but didn't always help from a
 MK> hardware perspective.  I had to learn the hard
 MK> way.

On the one hand, I want to notate everything. Sure, there are the 'scrap'
notes, that I will come to know with little or no reminder. The notes that I'll
never read again, and the notes I wish I took and the ones that made it
prematurely to the scrap pile. I think the best instruction I received, was
from a surgeon intern. She said, "One will tell you your suture tails are too
long, and the next will tell you they are too short." So are my notes.

 MK> guess on my part. Personally I found the "dhcpcd
 MK> -k eth#" to come in handy when someone from the
 MK> outside world was attempting to crack my
 MK> passords and wasting my bandwidth.  I could
 MK> always start it up again and renew the needed
 MK> connection.  It worked great.  No complaints
 MK> about dhcpcd here when it was needed.

Well, that's what kinda surpized me here. Both docs told me to use static
addressing, but when I fumbled through that in Windows, neither pages were
reached. Back to DHCP, and both were found. I may have set a static address out
of range for the 11g->bridge on this Gentoo box, though, so I might just try
the dual boot, to see what RH thinks about the situation. It really does well
in finding HW changes FWICT.
 

___ MultiMail/Linux v0.47

--- Maximus 3.01
 * Origin: -=-= Calgary Organization CDN (403) 242-3221 (1:134/77)