Boris Epstein wrote:
> Both are original installations.
I think it depends on the network card that you're exposing to the VM or
are the VMs using the same network adapter type? (The "fake" adapter
model.) Otherwise, I really wouldn't know why.
--
users mailing list
users@lists.fedoraproject.or
On Fri, Nov 18, 2011 at 4:42 PM, Michael Cronenworth wrote:
> Boris Epstein wrote:
> > However, the question is: I've got another Fedora 16 / 32 bit machine
> > installed under VirtualBox, and it has your regular eth0. How could that
> be?
>
> Is your VM originally F16 or was it upgraded from a pr
Boris Epstein wrote:
> However, the question is: I've got another Fedora 16 / 32 bit machine
> installed under VirtualBox, and it has your regular eth0. How could that be?
Is your VM originally F16 or was it upgraded from a previous Fedora?
Fedora saves the device name once you install Fedora so
On Fri, Nov 18, 2011 at 4:19 PM, Michael Cronenworth wrote:
> Boris Epstein wrote:
> > Any idea where these strange names come from and what the significance
> > of them is?
>
> It was a Fedora 15 Feature.
>
> http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
> --
>
Michael, th
Boris Epstein wrote:
> Any idea where these strange names come from and what the significance
> of them is?
It was a Fedora 15 Feature.
http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription o
Hello listmates,
I recently installed Fedora 16 as a guest VM under VirtualBox and instead
of the usual eth0/eth1 etc. names I got the following:
[root@ipa-test0 ~]# ifconfig
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
