Re: dragonfly pdf documentation

[Emiel Kollof <coolvibe@xxxxxxxxxxxxxxxx>]

On Tuesday 29 March 2005 16:41, Hummel Tom wrote:
> Eduardo Tongson schrieb:
> >>BTW, why is the reason that some names like network interface names
> >>are named differently between linux and dragonbsd?
> >
> > I think you mean eth0 vs xl0,dc0
> >
> > Linux uses eth_ for naming a network interface, on BSD interfaces are
> > named after the driver, xl0 (3Com 3C90x), dc0 (DEC). IMHO it is one of
> > Linux' design flaws. Naming it after the device is a plus because it
> > makes troubleshooting easier and less confusing (you know right away
> > which interface are you messing with).
>
> Personally i like the idea of naming all network devices after the
> network type. If you change card types there won't be any trouble in
> scripts and configs you forgot about etc...
> and a short check into the kernel message buffer, will clear up any
> confusion about the network devices :)

Like so? :

pikachu# ifconfig nv0 name external0
pikachu# ifconfig 
external0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.10.135 netmask 0xffff0000 broadcast 10.0.255.255
        inet6 fe80::230:1bff:feb1:161c%external0 prefixlen 64 scopeid 0x1
        inet 213.156.3.35 netmask 0xffffffe0 broadcast 213.156.3.63
        ether 00:30:1b:b1:16:1c
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
pikachu# ifconfig external0 name foobar0
pikachu# ifconfig
foobar0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 10.0.10.135 netmask 0xffff0000 broadcast 10.0.255.255
        inet6 fe80::230:1bff:feb1:161c%foobar0 prefixlen 64 scopeid 0x1
        inet 213.156.3.35 netmask 0xffffffe0 broadcast 213.156.3.63
        ether 00:30:1b:b1:16:1c
        media: Ethernet autoselect (100baseTX <full-duplex>)

:)

DragonFly has been able to to that for quite a while.

Cheers,
Emiel
-- 
"Good-bye.  I am leaving because I am bored."
		-- George Saunders' dying words