Jochen Schulz escreveu:
> This is a feature. ;-) Udev (the program that dynamically creates device
> nodes) tries to always assign the same device name to the same physical
> device.
Except for hard drivers, where it tends to do exactly the opposite. :-)
--
Eduardo M Kalinowski
[EMAIL PROTECTED]
Keith Steensma:
>
> I have a sever that has been running for months with a single Realtek
> 8139 network card. The NIC failed and I put in a 3Com 3C905B-TX card
> (that I pulled from a working test machine). When I rebooted the
> server, the 3Com card was no configured and I ended up with
On Mon, Oct 13, 2008 at 09:37:19 -0500, Keith Steensma wrote:
> I have never seen this addressed in the mailing list, so I'll have to
> ask for help
>
> I have a sever that has been running for months with a single Realtek
> 8139 network card. The NIC failed and I put in a 3Com 3C905B-TX card
On Mon Oct 13, 2008 at 16:55:06 +0200, Nyizsnyik Ferenc wrote:
> > What is it that the install routine does that finds the NIC's. Is
> > this a command line (something) that can (should) be run manually
> ethx devices always correspond to the one NIC they were created for.
> Your new NIC is work
On Mon, 13 Oct 2008 09:37:19 -0500
Keith Steensma <[EMAIL PROTECTED]> wrote:
> I have never seen this addressed in the mailing list, so I'll have to
> ask for help
>
> I have a sever that has been running for months with a single Realtek
> 8139 network card. The NIC failed and I put in a 3Com
I have never seen this addressed in the mailing list, so I'll have to
ask for help
I have a sever that has been running for months with a single Realtek
8139 network card. The NIC failed and I put in a 3Com 3C905B-TX card
(that I pulled from a working test machine). When I rebooted the
serv
6 matches
Mail list logo
