Has anybody considered that devd might be the ideal vehicle for doing
something like this?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Tue, Nov 19, 2002 at 11:24:10AM -0800, Rich Morin wrote:
> At 10:37 AM -0800 11/19/02, Brooks Davis wrote:
> >Once the if_xname patch is in, it will be exceedingly simple to add some
> >code to ether_ifattach to do that if you really want.
>
> Well, _I_ really want FreeBSD to move in the direct
At 10:37 AM -0800 11/19/02, Brooks Davis wrote:
Once the if_xname patch is in, it will be exceedingly simple to add some
code to ether_ifattach to do that if you really want.
Well, _I_ really want FreeBSD to move in the direction of "plug and play";
this is merely one small contribution. That s
On Tue, Nov 19, 2002 at 12:27:33AM -0800, Terry Lambert wrote:
> Doug Barton wrote:
> > Pardon me if I'm being dense, but I don't understand what your proposal
> > does that the existing interface config tools do not. Can you give a
> > description (not code) of what you're trying to accomplish?
>
At 3:17 PM +0100 11/19/02, René Scharfe wrote:
OK, perhaps this can be made even simpler. Put this into your /etc/rc.conf
and be done:
# a hack to ease the configuration of machines with only one NIC
_single=`ifconfig -l link`
eval ifconfig_${_single}="inet 192.168.254.193 netmask 255.255.
On Tuesday 19 November 2002 05:20, Rich Morin wrote:
>network_interfaces=SINGLE
>ifconfig_single=" inet 192.168.254.193 netmask 255.255.255.0"
>ifconfig_single_alias0="inet 192.168.254.199 netmask 255.255.255.255"
OK, perhaps this can be made even simpler. Put this into your /etc
Doug Barton wrote:
> Pardon me if I'm being dense, but I don't understand what your proposal
> does that the existing interface config tools do not. Can you give a
> description (not code) of what you're trying to accomplish?
He wants it to "just work" with an unknown card. FreeBSD does not
name
At 11:39 PM -0800 11/18/02, Doug Barton wrote:
Pardon me if I'm being dense, but I don't understand what your proposal
does that the existing interface config tools do not.
Well, it's quite possible that I am replicating some existing feature;
feel free to clue me in if this is the case.
Can y
Pardon me if I'm being dense, but I don't understand what your proposal
does that the existing interface config tools do not. Can you give a
description (not code) of what you're trying to accomplish?
Doug
--
"We have known freedom's price. We have shown freedom's power.
And in this gre
René Scharfe <[EMAIL PROTECTED]> has developed an alternative way of performing
this function. It's a LOT smaller than my version, yet it seems to cover
all the bases. To use his version, you put:
network_interfaces=SINGLE
ifconfig_single=" inet 192.168.254.193 netmask 255.255.255.0"
Hearing no objections (:-), I decided to go ahead with this effort.
I have created a script named /etc/rc.ifsgl, which is invoked by
(the FreeBSD 4.7 RELEASE version of) /etc/rc.network, as follows:
183a184,185
. /etc/rc.ifsgl # handle sgl_ifconfig variable (etc).
That is, just b
I had a recent experience in which my FreeBSD system would not configure
my Ethernet card because the specification in rc.conf was for a different
type of card. It seems like FreeBSD could easily handle the general case
(only one network interface) automagically, letting folks with fancier
systems
12 matches
Mail list logo
