>The idea actually came from Dell. It's frequently described as a method
>to prevent the device name from changing during a reboot, but that was
>already in place. What biosdevname does is make names *predictable* on
>Dell systems. It shouldn't be enabled anywhere else.
It is not at all exclusi
On 08/09/2012 11:31 AM, Scott Robbins wrote:
> It's another idea from Fedora, the theory, IIRC, was that this way,
> devices would always have the same name, whereas under the method
> that has been used device names could change on a reboot.
The idea actually came from Dell. It's frequently desc
On Fri, Aug 10, 2012 at 9:15 AM, Nate Duehr wrote:
> >
>> Alternatively, with the biosdevname, you can pin the interface name to
>> the pci(e) slot. That way its a trivial exercise to get 'remote hands'
>> to swap out a dead nic -- no need to fiddle with the mac address.
>
> And if you don't...
>
On Aug 9, 2012, at 7:43 PM, Kahlil Hodgson
wrote:
> On 10/08/12 09:18, Reindl Harald wrote:
>> and that is why i use /etc/udev/rules.d/70-persistent-net.rules to
>> pin device-name / MAC and no mac-address in ifconfig-scripts since
>> many years
>
> +1
>
> Alternatively, with the biosdevname,
On 10/08/12 09:18, Reindl Harald wrote:
> and that is why i use /etc/udev/rules.d/70-persistent-net.rules to
> pin device-name / MAC and no mac-address in ifconfig-scripts since
> many years
+1
Alternatively, with the biosdevname, you can pin the interface name to
the pci(e) slot. That way its a
On 10/08/12 04:31, Scott Robbins wrote:
...
> I tend to agree with the slashdot commentator who called it overcomplicated
> and unnecessary. It's another idea from
> Fedora, the theory, IIRC, was that this way, devices would always have the
> same name, whereas under the
> method that has been
On 10/08/12 03:33, Richard Reina wrote:
> I have just installed 6.3 on a machine that was previously running
> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
> wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
> static IP as I intend to for this to be ma
I installed off the live CD. I will try a 6.3 net install and see what changes.
El Aug 9, 2012, a las 2:40 PM, m.r...@5-cent.us escribió:
> Richard Reina wrote:
>> If it's as simple as sticking the MAC address into the ifcfg-eth file,
>> I can live with that. But only ifcfg script that exits in
On Thu, Aug 9, 2012 at 1:47 PM, wrote:
>
>>> I have just installed 6.3 on a machine that was previously running
>>> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
>>> wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
>>> static IP as I intend to for th
Richard Reina wrote:
> If it's as simple as sticking the MAC address into the ifcfg-eth file,
> I can live with that. But only ifcfg script that exits in
> /etc/sysconfig/network-scripts/ is ifcfg-lo
>
> I have no idea what k3wl is.
Script-kiddie speak. 3 == e. I was being sarcastic (about the fed
If it's as simple as sticking the MAC address into the ifcfg-eth file,
I can live with that. But only ifcfg script that exits in
/etc/sysconfig/network-scripts/ is ifcfg-lo
I have no idea what k3wl is.
Thanks for the replies.
2012/8/9, m.r...@5-cent.us :
> Scott Robbins wrote:
>> On Thu, Aug 09
Scott Robbins wrote:
> On Thu, Aug 09, 2012 at 12:33:43PM -0500, Richard Reina wrote:
>> I have just installed 6.3 on a machine that was previously running
>> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
>> wlan0 and p4p1 (instead of eth0). I would like to make the ethern
On Thu, Aug 09, 2012 at 12:33:43PM -0500, Richard Reina wrote:
> I have just installed 6.3 on a machine that was previously running
> 5.8. Under 5.8 eth0 was eth0. Now with 6.3 /sbin/ifconfig gives me lo,
> wlan0 and p4p1 (instead of eth0). I would like to make the ethernet a
> static IP as I inte
13 matches
Mail list logo
