Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 09 Apr 2006 10:01:56 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Mike Meyer <mwm-keyword-freebsdhackers.102a7e@mired.org>
Cc:        hackers@freebsd.org
Subject:   Re: Using any network interface whatsoever
Message-ID:  <4438CD84.1020906@infracaninophile.co.uk>
In-Reply-To: <17464.29347.529203.354768@bhuda.mired.org>
References:  <C05CAC06.C0BD%ceri@submonkey.net>	<20060407225742.GA21619@odin.ac.hmc.edu>	<20060407230247.GH16344@submonkey.net>	<4437C9F6.5000008@samsco.org>	<20060408233740.GA84768@submonkey.net>	<44384A55.2010103@samsco.org> <4438630E.4090300@deadcafe.de> <17464.29347.529203.354768@bhuda.mired.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5A8B6881266714BDB20380B9
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Mike Meyer wrote:
> In <4438630E.4090300@deadcafe.de>, Daniel Rock <freebsd@deadcafe.de> ty=
ped:
>> 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).
>=20
> That happened very early in the life of Solaris, in the early 90s.
> Persistent numbering was added to Solaris in response to this incident
> (there were probably others as well).
>=20
> This was on a relatively large server, with something like 4 SCSI
> buses. A drive was added to a previously unused bus, making it appear
> "between" two drives that were already in the system. This gave all
> the drives further on in the probe sequence a device number one higher
> than they had previously had.

It sounds for me as if you (Mike Meyer) are asking for something like
'acpidump -d' or 'pciconf -l -v' output, but translated into a filesystem=

abstraction -- ie a tree of directories corresponding to different busses=

containing device files ordered according to the bus slot they are
plugged into.  This would be something that you can use either in place
of the traditional /dev or as an adjunct to it.  I believe Solaris has
a /devices tree which does essentially this.

In practice however on the systems we deploy we know that the principal
network interfaces are the ones on-board the motherboard, and we know
that em0 or bge0 is the one closest to the PSU.  Similarly for other
devices -- disk device numbers can be deduced from the physical slot they=

are in.  Sure it's just a convention, and it helps that the equipment
supplier we use is very consistent about such things, and that in general=

we don't go around plugging USB disk devices into server systems that
frequently.  But on the whole it works.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       7 Priory Courtyard
                                                      Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey         Ramsgate
                                                      Kent, CT11 9PW


--------------enig5A8B6881266714BDB20380B9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEOM2J8Mjk52CukIwRA3eGAJ9fIvHwgwv3yIoSd8USWv77AGlFigCfYdeL
xewb3JZgzBoH2GvFRrU/b4c=
=L4uX
-----END PGP SIGNATURE-----

--------------enig5A8B6881266714BDB20380B9--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4438CD84.1020906>