On 04/11/2014 11:39 AM, Phil Wyett wrote:
> On Fri, 2014-04-11 at 11:28 -0400, Steve Clark wrote:
>> On 04/11/2014 11:21 AM, Steve Clark wrote:
>>> On 03/20/2014 12:04 PM, Steve Clark wrote:
Hello,
Anybody else run into problems with biosdevname .0.5..0-2 changing names
from p2p
On Fri, 2014-04-11 at 16:39 +0100, Phil Wyett wrote:
> On Fri, 2014-04-11 at 11:28 -0400, Steve Clark wrote:
> > On 04/11/2014 11:21 AM, Steve Clark wrote:
> > > On 03/20/2014 12:04 PM, Steve Clark wrote:
> > >> Hello,
> > >>
> > >> Anybody else run into problems with biosdevname .0.5..0-2 changing
On Fri, 2014-04-11 at 11:28 -0400, Steve Clark wrote:
> On 04/11/2014 11:21 AM, Steve Clark wrote:
> > On 03/20/2014 12:04 PM, Steve Clark wrote:
> >> Hello,
> >>
> >> Anybody else run into problems with biosdevname .0.5..0-2 changing names
> >> from p2p1 to em1 when upgrading from biosdevname 0.4.
On 04/11/2014 11:21 AM, Steve Clark wrote:
> On 03/20/2014 12:04 PM, Steve Clark wrote:
>> Hello,
>>
>> Anybody else run into problems with biosdevname .0.5..0-2 changing names
>> from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
>>
>> Darn!
>> I thought biosdevname was to keep the names th
On 03/20/2014 12:04 PM, Steve Clark wrote:
> Hello,
>
> Anybody else run into problems with biosdevname .0.5..0-2 changing names
> from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
>
> Darn!
> I thought biosdevname was to keep the names the same!!
>
>
Update - I filed a bug report and got t
On 03/21/2014 06:36 PM, SilverTip257 wrote:
> On Fri, Mar 21, 2014 at 6:28 PM, Warren Young wrote:
>
>> On 3/20/2014 10:33, SilverTip257 wrote:
>>> And an interface should only be detected as pXpY if it's a PCI NIC.
>>> THOUGH I've seen it already where an onboard NIC in a Lenovo desktop was
>>> d
On Fri, Mar 21, 2014 at 6:28 PM, Warren Young wrote:
> On 3/20/2014 10:33, SilverTip257 wrote:
> >
> > And an interface should only be detected as pXpY if it's a PCI NIC.
> > THOUGH I've seen it already where an onboard NIC in a Lenovo desktop was
> > detected as p5p1.
>
> Just because the MAC ch
On 3/20/2014 10:33, SilverTip257 wrote:
>
> And an interface should only be detected as pXpY if it's a PCI NIC.
> THOUGH I've seen it already where an onboard NIC in a Lenovo desktop was
> detected as p5p1.
Just because the MAC chip is soldered to the motherboard doesn't mean it
can't be on the P
On Thu, Mar 20, 2014 at 11:33 AM, SilverTip257 wrote:
>
> An interface should only be automatically named em1 if it's an onboard NIC
> in a (just Dell?) system.
>
> And an interface should only be detected as pXpY if it's a PCI NIC.
> THOUGH I've seen it already where an onboard NIC in a Lenovo de
On Thu, Mar 20, 2014 at 12:04 PM, Steve Clark wrote:
> Hello,
>
> Anybody else run into problems with biosdevname .0.5..0-2 changing names
> from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
>
I'll second Les' statement that this sounds like a bug.
An interface should only be automatica
On Thu, Mar 20, 2014 at 11:14 AM, wrote:
> >
>> Anybody else run into problems with biosdevname .0.5..0-2 changing names
>> from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
>
> Is this in 6.5?
>>
>> Darn!
>> I thought biosdevname was to keep the names the same!!
>
> Maybe enough folks we
On 03/20/2014 12:14 PM, m.r...@5-cent.us wrote:
> Steve Clark wrote:
>> Anybody else run into problems with biosdevname .0.5..0-2 changing names
>> from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
> Is this in 6.5?
Yes.
>> Darn!
>> I thought biosdevname was to keep the names the same!!
> M
Steve Clark wrote:
>
> Anybody else run into problems with biosdevname .0.5..0-2 changing names
> from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
Is this in 6.5?
>
> Darn!
> I thought biosdevname was to keep the names the same!!
Maybe enough folks were annoyed with the old Sun-ism, and
Hello,
Anybody else run into problems with biosdevname .0.5..0-2 changing names
from p2p1 to em1 when upgrading from biosdevname 0.4.1-3?
Darn!
I thought biosdevname was to keep the names the same!!
--
Stephen Clark
*NetWolves Managed Services, LLC.*
Director of Technology
Phone: 813-579-3200
14 matches
Mail list logo