[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: question about netstart, hostname.xxx
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: question about netstart, hostname.xxx
- From: Nick Holland <nick_(_at_)_holland-consulting_(_dot_)_net>
- Date: Wed, 27 Oct 2004 11:20:34 -0400
(sorry, Mozilla figured this was spam, didn't notice it until this
morning. Ever wonder what goes through a spam filter's mind? "This is
about doing something to sis? That's sick!")
STeve Andre' wrote:
> On Wednesday 27 October 2004 05:07, Greg Thomas wrote:
>> STeve Andre'
>> > On Tuesday 26 October 2004 22:10, Nick Holland wrote:
>> >> Nope, I do this on my laptop...which ever pcmcia card I stick in it is
>> >> processed, the rest are just ignored, not even an error message.
>> >> Also, if I change the NIC on a machine, I usually leave the old
>> >> hostname.* files in place rather than removing or renaming them, just in
>> >> case I realize the problem was elsewhere and I want to put the old NIC
>> >> back in place.
>> > Continuing this question, if I have say an fxp nic thats plugged in and a
>> > wi wireless interface with an access point near, what determines which
>> > becomes activated at boot time?
>> Am I missing something? If hostname.wi0 and hostname.fxp0 exist then both
>> are activated, just like if you have a sis0 and an xl0.
> I haven't tried this in some time (months) but I found that only
> one was activated, hence my question. But yes it does make
> sense as I write this that both should have come up. So I'll try
> that tomorrow. Guess this was a waste of electrons. Sorry.
ONE POSSIBLE EXPLAINATION: When Henning reworked dhcpd and dhclient, he
stuck something in there to look for a carrier. This is way cool -- if
you have a laptop with an on-board NIC and sometimes go wireless, have
both hostname.* files in place. When dhclient sees no wire on your
on-board NIC, it will give you a few seconds to plug one in, then give
up and move on, and hopefully your wireless card is in place. No idea
what it would do if there is no AP near by, but if you don't want
wireless, worst case, just eject the card. IF that was your situation,
it might appear that only one was being recognized. Not true, just that
only one was actually working, the other was bailing out quickly.
Kinda figures that the laptop I had that I needed this feature for broke
just before it went into the system. :)
Visit your host, monkey.org