> Have a look in the following file:
> % cat /etc/udev/rules.d/z25_persistent-net.rules
Thanks. That was what was causing the issue, and removing the unwanted lines
solved the problem.
I can see the rationale behind this new scheme, but I wonder if it doesn't
cause more problems than it solve
> just delete all ethx lines and then on reboot eth0 should be eth0 again...
>
> HTH
>
> PS. I had a similar issue recently also with VMWare and this solved it ;)
Had this here, too, boggling my mind - thanks :)
--
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d--(+)@ s-:+ a C UL++ P+>
On Monday 25 August 2008 17:19:00 roy hills wrote:
> I have a Debian Etch system running on VMware workstation 6. The system
> has been copied from another system using dump/restore in single user mode
> followed by re-installing grub in the MBR.
>
> The system boots and runs fine. The only oddit
I have a Debian Etch system running on VMware workstation 6. The system has
been copied from another system using dump/restore in single user mode followed
by re-installing grub in the MBR.
The system boots and runs fine. The only oddity is that it assigns the name
"eth2" to the only Etherne
4 matches
Mail list logo
