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
On 08.04.2006, at 5:04, Jeremy Baggs wrote:
I suppose it would be nice to have something that works out of the
box, but the solution I have been using
is group permissions on the devices and then making the mount point
in fstab relative instead of absolute. ie:
/dev/cd0 cdrom
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
On Thursday 30 March 2006 02:36, Brad Davis wrote:
Hi All,
It is time for the quarterly Status Reports. As always, reports are
encouraged for anything that relates to FreeBSD development,
documentation, independent projects, or anything else that might be
interesting to the community as a
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 [EMAIL PROTECTED], Sergey Babkin [EMAIL PROTECTED] typed:
I think this is a problem consisting of multiple parts:
1. Identify physical devices and be able to access them.
2. Identify some stable logical names by device type,
that stay fixed when the configuration changes.
3. Be able
Hi,
Started doing a little reading on the UFS and UFS2
file systems. I'm just wondering if all types of files
have extended attribute blocks available including
named pipes, sockets, and device files?
Is it still the case that there are three unused extended
attribute blocks available?
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
In message: [EMAIL PROTECTED]
Mike Meyer [EMAIL PROTECTED] writes:
: The major problem with it is that todays bus architectures don't have
: stable device addresses. Instead of devices having a fixed address on
: the bus that the user sets, the addresses are assigned as the devices
:
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
In [EMAIL PROTECTED], M. Warner Losh [EMAIL PROTECTED] typed:
In message: [EMAIL PROTECTED]
Mike Meyer [EMAIL PROTECTED] writes:
: The major problem with it is that todays bus architectures don't have
: stable device addresses. Instead of devices having a fixed address on
: the
20 matches
Mail list logo
