From mailing list archives:
I wrote some add-on bits for /etc/rc.network in 4.x that compares
the link addresses of attached network interfaces to a list of link
addresses, then sets ifconfig_ifN* variables accordingly before
rc.network does anything. It provides a means of wiring IP
On Sun, Apr 09, 2006 at 06:48:25PM -0600, M. Warner Losh wrote:
I though thtis was already supported. We export bus/slot/function
information devd, which can be used to configure the device.
If I've read the specs or code incorrectly please do let me know --
my reading here is based on the PCI
In message: [EMAIL PROTECTED]
Bruce M Simpson [EMAIL PROTECTED] writes:
: On Sun, Apr 09, 2006 at 06:48:25PM -0600, M. Warner Losh wrote:
: I though thtis was already supported. We export bus/slot/function
: information devd, which can be used to configure the device.
:
: If I've
I think at this point it's been pretty well established that:
- Device naming and unit numbering is not stable enough to avoid breakage
across hardware changes.
- There is a need for generic and/or descriptive interface naming
independent of driver- and probe-order-based naming.
- There are
On Apr 10, 2006, at 2:23 PM, Darren Pilgrim wrote:
I think at this point it's been pretty well established that:
- Device naming and unit numbering is not stable enough to avoid
breakage across hardware changes.
- There is a need for generic and/or descriptive interface naming
independent
Mike Meyer wrote:
In [EMAIL PROTECTED], Daniel Rock [EMAIL PROTECTED] typed:
So I doubt that the overwriting of an Ingres database really
happened in Solaris, like some other poster described - unless the
administrator fiddled with /etc/path_to_inst by hand (you are free
to shoot in your own
Mike,
Tell me about it, I know exactly what you mean!
On Sat, Apr 08, 2006 at 06:53:11PM -0400, Mike Meyer wrote:
My question about labels for ethernet devices wasn't meant to be
rhetorical. Ethernet device names on Unix are pretty much
worthless. They tell you basically nothing about which
On Sat, Apr 08, 2006 at 05:42:13PM -0600, Scott Long wrote:
Ceri Davies wrote:
On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
For the filesystem I can use geom_label and /dev/ufs/UnlikelyString,
but I'd
also
eth0 works well for the degenerate case where there's a network card
in the system, and nothing else. It works less well for systmes where
there are more than one card, and where the hardware changes a lot for
all the reasons discussed in this thread. It is too generic.
Of course, when you have
In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
Mike Meyer wrote:
In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
[Tying names to MAC addresses.]
That's far better than trying to remember what's on em0.
That's certainly true. But is there an advantage to
On Sun, 2006-Apr-09 09:58:19 -0600, M. Warner Losh wrote:
I've actually run into all of these problems on a machine we have at
work that acts as a gateway to about 10-20 private networks. It has
had between 2-4 dual cards and 2-4 quad cards, in various mix and
match flavors over the years.
We
From: Mike Meyer
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Youre' saying that
instead of /dev/da0, we should have
/dev/HITACHI-HUS103073FL3800-SA19-B0T1L0
That's a ridiculous extreme. All I advocated was that we be able to
easily identify the devices connected to the system,
Mike Meyer wrote:
In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
You could test two different drivers on the same hardware and you wouldn't
have to duplicate or modify your ifconfig lines in /etc/rc.conf, just run:
Yup, and this is an advantage. On the other hand, if you tie
From: Mike Meyer
In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
That's far better than trying to remember what's on em0.
That's certainly true. But is there an advantage to tieing the
PublicLAN name to a MAC address as opposed to em0?
You could test two different drivers
In message: [EMAIL PROTECTED]
Bruce M Simpson [EMAIL PROTECTED] writes:
: What it really comes down to is that one needs a PCI variant which supports
: what's known as 'geographical addressing', and for FreeBSD's device / ifnet
: framework to support naming cards according to the
In message: [EMAIL PROTECTED]
Mike Meyer [EMAIL PROTECTED] writes:
: Of course, this doesn't help the OP's problem of wanting to be able to
: address the sole interface in a system without knowing it's name in
: advance. Maybe a feature to provide a default name for an interface if
:
In message: [EMAIL PROTECTED]
Darren Pilgrim [EMAIL PROTECTED] writes:
: Mike Meyer wrote:
: In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
: You could test two different drivers on the same hardware and you wouldn't
: have to duplicate or modify your ifconfig lines
M. Warner Losh wrote:
The device subsystem already exports a bus-dependent plug and play
position. No need to make it specific to USB/PCI/whatever.
Where is this information found? I can't find anything obvious that
wouldn't change if you inserted a bus in the middle of the probe order.
In message: [EMAIL PROTECTED]
Darren Pilgrim [EMAIL PROTECTED] writes:
: M. Warner Losh wrote:
:
: The device subsystem already exports a bus-dependent plug and play
: position. No need to make it specific to USB/PCI/whatever.
:
: Where is this information found? I can't find
Ceri Davies wrote:
On Fri, Apr 07, 2006 at 03:57:42PM -0700, Brooks Davis wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
I'm trying to configure a bootable image to be used in various situations
and on various (mostly unknown) hardware.
For the filesystem I can use
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Well, the real question is why we force the details of driver names onto
users. Network and storage drivers are especially guilty of this, but
tty devices also are annoying.
Because Unix has always made the hardware details available
Mike Meyer wrote:
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Well, the real question is why we force the details of driver names onto
users. Network and storage drivers are especially guilty of this, but
tty devices also are annoying.
Because Unix has always made the
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Please trim the text you are repling to.
You're argument here doesn't really make sense.
Only because you're carrying it to ridiculous extremes and
misinterpreting it.
Youre' saying that
instead of /dev/da0, we should have
Mike Meyer wrote:
If I do care - for instance, I want to distinguish
between the ethernet interface that's on the internet and the one
that's on my LAN, or I want root to be on the disk with the root file
system on it - then this is a PITA, because every time I add hardware
to the system, or
Mike Meyer wrote:
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Please trim the text you are repling to.
Please, I'm tired of arbitrary email etiquette.
But where do you put the label on an ethernet interface?
mike
It sounds like your message is, don't be like Linux.
...lazy...
Not all problems can be fixed by somebody else. Work a little for a
change.
If you wish to name your interfaces switch to Windows.
ifconfig -a | awk '/^[a-z0-9^]*:/ {i=$1} /inet / {ip=$2;net=$4;}
/status/ {print i ip - net - $2}'
em0: 10.0.1.1 - 0xff00 - active
On Sat, 08 Apr 2006, Mike Meyer wrote:
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Well, the real question is why we force the details of driver names onto
users. Network and storage drivers are especially guilty of this, but
tty devices also are annoying.
Because Unix
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Mike Meyer wrote:
In [EMAIL PROTECTED], Scott Long [EMAIL PROTECTED] typed:
Please trim the text you are repling to.
Please, I'm tired of arbitrary email etiquette.
If you think etiquette is arbitrary, you're sadly mistaken.
But
In [EMAIL PROTECTED], David Taylor [EMAIL PROTECTED] typed:
That doesn't quite work, though. Unless you require everyone wanting
to distinguish between LAN and WAN interfaces uses different types
of hardware for each card, they'll still end up with xl0 and xl1
(or whatever), which is in no
On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
For the filesystem I can use geom_label and /dev/ufs/UnlikelyString, but
I'd
also like to have it try to configure whatever interfaces the machine
happens to have via
Ceri Davies wrote:
On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
For the filesystem I can use geom_label and /dev/ufs/UnlikelyString, but
I'd
also like to have it try to configure whatever interfaces the machine
Mike Meyer wrote:
In [EMAIL PROTECTED], David Taylor [EMAIL PROTECTED] typed:
That doesn't quite work, though. Unless you require everyone wanting
to distinguish between LAN and WAN interfaces uses different types
of hardware for each card, they'll still end up with xl0 and xl1
(or whatever),
Mike Meyer [EMAIL PROTECTED] wrote:
What do I want for that? I identify ethernet boards by which slot on
the back of the system I plug the cable into. Currently, I have to map
that to board types to and which board is plugged into which slot to
know which name to use. I want a name that tells
Scott Long schrieb:
Ceri Davies wrote:
On Sat, Apr 08, 2006 at 08:34:30AM -0600, Scott Long wrote:
Well, the real question is why we force the details of driver names
onto users. Network and storage drivers are especially guilty of
this, but tty devices also are annoying.
How do you
In [EMAIL PROTECTED], Daniel Rock [EMAIL PROTECTED] typed:
So I doubt that the overwriting of an Ingres database really
happened in Solaris, like some other poster described - unless the
administrator fiddled with /etc/path_to_inst by hand (you are free
to shoot in your own foot).
That
In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
Mike Meyer wrote:
In [EMAIL PROTECTED], David Taylor [EMAIL PROTECTED] typed:
That doesn't quite work, though. Unless you require everyone wanting
to distinguish between LAN and WAN interfaces uses different types
of hardware
Mike Meyer wrote:
In [EMAIL PROTECTED], Darren Pilgrim [EMAIL PROTECTED] typed:
If you add something to /etc/rc.d so that a sh-ified version of this script
runs after all interfaces have attached but before any numbering or cloning
takes place you can have lines like this in /etc/rc.conf:
I'm trying to configure a bootable image to be used in various situations
and on various (mostly unknown) hardware.
For the filesystem I can use geom_label and /dev/ufs/UnlikelyString, but I'd
also like to have it try to configure whatever interfaces the machine
happens to have via DHCP.
Other
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
I'm trying to configure a bootable image to be used in various situations
and on various (mostly unknown) hardware.
For the filesystem I can use geom_label and /dev/ufs/UnlikelyString, but I'd
also like to have it try to
On Fri, Apr 07, 2006 at 03:57:42PM -0700, Brooks Davis wrote:
On Fri, Apr 07, 2006 at 11:53:42PM +0100, Ceri Davies wrote:
I'm trying to configure a bootable image to be used in various situations
and on various (mostly unknown) hardware.
For the filesystem I can use geom_label and
40 matches
Mail list logo
