On Tue, Nov 30, 2010 at 04:11:52PM -0600, Matt Domsch wrote:
> On Tue, Nov 30, 2010 at 10:13:30PM +0100, Fabian Deutsch wrote:
> > Good day,
> >
> > Am Dienstag, den 30.11.2010, 13:04 -0600 schrieb Matt Domsch:
> > > On Mon, Nov 29, 2010 at 08:48:05PM +0530, Rahul Sundaram wrote:
> > > > On 11/29/
On Wed, Dec 01, 2010 at 01:18:09PM -0500, Przemek Klosowski wrote:
> On 11/30/2010 05:24 PM, Matt Domsch wrote:
> > On Tue, Nov 30, 2010 at 04:22:54PM -0600, Matt Domsch wrote:
> >> On Tue, Nov 30, 2010 at 04:18:10PM -0600, Michael Cronenworth wrote:
>
> >>> Many desktops have dual-NICs. I'm typin
Przemek Klosowski wrote:
> Huh? so the first device (handle 2D) will be called 'em0' and the second
> device (handle 3D) will be also called 'em0'?
2D and 3D reference one NIC.
I only had one NIC in my e-mail to avoid it being lengthy. ;)
--
devel mailing list
devel@lists.fedoraproject.org
https:
On 11/30/2010 05:24 PM, Matt Domsch wrote:
> On Tue, Nov 30, 2010 at 04:22:54PM -0600, Matt Domsch wrote:
>> On Tue, Nov 30, 2010 at 04:18:10PM -0600, Michael Cronenworth wrote:
>>> Many desktops have dual-NICs. I'm typing from an SMBIOS 2.6 ASUS desktop
>>> motherboard with dual-NICs.
>>>
>>> Han
On 12/01/2010 10:13 AM, Matthew Miller wrote:
>
> Because it's not so almighty. In BSD-land, including Solaris, the devices
> are named after the driver, so you get /dev/sis0 and /dev/bge1 and
> /dev/e1000g0 and whatnot.
>
That BSD scheme suffers the same pitfalls as the current fedora scheme
On Tue, Nov 30, 2010 at 04:29:32PM -0600, Michael Cronenworth wrote:
> Interesting work, Matt. I'm surprised the Unix purists who would fight
> you to death to keep sendmail on desktops would allow you to change the
> almighty eth* naming scheme.
Because it's not so almighty. In BSD-land, includ
On 12/01/2010 07:55 AM, Ralf Ertzinger wrote:
> Hi.
>
> On Wed, 1 Dec 2010 01:33:33 + (UTC), Ben Boeckel wrote:
>
>> Why? FreeBSD (and other BSDs, I'm sure) have been naming network
>> interfaces based on the manufacturer, at least, for a while now (I
>> personally started with 7.x and am uns
Hi.
On Wed, 1 Dec 2010 01:33:33 + (UTC), Ben Boeckel wrote:
> Why? FreeBSD (and other BSDs, I'm sure) have been naming network
> interfaces based on the manufacturer, at least, for a while now (I
> personally started with 7.x and am unsure of when that was new). I was
> always curious why eth
On Wed, 2010-12-01 at 14:04 +0530, Rahul Sundaram wrote:
> On 12/01/2010 01:50 PM, Jon Masters wrote:
> > On Tue, 2010-11-30 at 16:29 -0600, Michael Cronenworth wrote:
> >>
> >> OK. Perhaps the wiki should be updated to state the feature works more
> >> generically (SMBIOS 2.6+) and not for just D
On 12/01/2010 01:50 PM, Jon Masters wrote:
> On Tue, 2010-11-30 at 16:29 -0600, Michael Cronenworth wrote:
>>
>> OK. Perhaps the wiki should be updated to state the feature works more
>> generically (SMBIOS 2.6+) and not for just Dell/HP systems?
> +1
>
> And also, I'd love to see fewer attacks on
On Tue, 2010-11-30 at 16:29 -0600, Michael Cronenworth wrote:
> Matt Domsch wrote:
> >> > Yes, your system, on new install, or if you delete
> >> > /etc/udev/rules.d/70-persistent-net.rules and the HWADDR lines from
> >> > /etc/sysconfig/network-scripts/ifcfg-*, will then use the new names.
> >
On Tue, Nov 30, 2010 at 06:36:17PM -0600, Joe Nall wrote:
> As someone who deals with HP DL580 boxes with 6+ NICs routinely,
> this is good stuff. Deterministic naming of the built in NICs will
> simplify installation instructions for us.
Thanks for the good word!
> Are the internal names going t
Michael Cronenworth wrote:
> Interesting work, Matt. I'm surprised the Unix purists who would fight
> you to death to keep sendmail on desktops would allow you to change the
> almighty eth* naming scheme.
Why? FreeBSD (and other BSDs, I'm sure) have been naming network
interfaces based on the m
On Nov 30, 2010, at 4:34 PM, Matt Domsch wrote:
> On Tue, Nov 30, 2010 at 04:29:32PM -0600, Michael Cronenworth wrote:
>> Matt Domsch wrote:
> Yes, your system, on new install, or if you delete
> /etc/udev/rules.d/70-persistent-net.rules and the HWADDR lines from
> /etc/sysconfig/netw
On Tue, Nov 30, 2010 at 04:29:32PM -0600, Michael Cronenworth wrote:
> Matt Domsch wrote:
> >> > Yes, your system, on new install, or if you delete
> >> > /etc/udev/rules.d/70-persistent-net.rules and the HWADDR lines from
> >> > /etc/sysconfig/network-scripts/ifcfg-*, will then use the new name
Matt Domsch wrote:
>> > Yes, your system, on new install, or if you delete
>> > /etc/udev/rules.d/70-persistent-net.rules and the HWADDR lines from
>> > /etc/sysconfig/network-scripts/ifcfg-*, will then use the new names.
> specifically, em0 for the above device, and em for the
> second NIC spe
On Tue, Nov 30, 2010 at 04:22:54PM -0600, Matt Domsch wrote:
> On Tue, Nov 30, 2010 at 04:18:10PM -0600, Michael Cronenworth wrote:
> > Matt Domsch wrote:
> > > I don't expect desktops to expose
> > > this information - they have only 1 NIC.
> >
> > Many desktops have dual-NICs. I'm typing from an
On Tue, Nov 30, 2010 at 04:18:10PM -0600, Michael Cronenworth wrote:
> Matt Domsch wrote:
> > I don't expect desktops to expose
> > this information - they have only 1 NIC.
>
> Many desktops have dual-NICs. I'm typing from an SMBIOS 2.6 ASUS desktop
> motherboard with dual-NICs.
>
> Handle 0x002
On 11/30/2010 01:12 PM, Matt Domsch wrote:
> I don't expect desktops to expose
> this information - they have only 1 NIC.
There are 2 built-in NIC ports on at least a couple ASUS and
Gigabyte motherboards that have been sold into the "desktop"
market in the last couple years. My desktops also ha
Matt Domsch wrote:
> I don't expect desktops to expose
> this information - they have only 1 NIC.
Many desktops have dual-NICs. I'm typing from an SMBIOS 2.6 ASUS desktop
motherboard with dual-NICs.
Handle 0x002D, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
On Tue, Nov 30, 2010 at 10:13:30PM +0100, Fabian Deutsch wrote:
> Good day,
>
> Am Dienstag, den 30.11.2010, 13:04 -0600 schrieb Matt Domsch:
> > On Mon, Nov 29, 2010 at 08:48:05PM +0530, Rahul Sundaram wrote:
> > > On 11/29/2010 08:27 PM, Matt Domsch wrote:
> > > > On Mon, Nov 29, 2010 at 12:17:2
On Tue, Nov 30, 2010 at 03:25:45PM -0600, Michael Cronenworth wrote:
> Matt Domsch wrote:
> > I've pushed the comps change to pull biosdevname into @base by
> > default. And I've posted a patch to anaconda-devel-list to pull
> > biosdevname into the installtime environment. Cross your fingers,
>
Matt Domsch wrote:
> I've pushed the comps change to pull biosdevname into @base by
> default. And I've posted a patch to anaconda-devel-list to pull
> biosdevname into the installtime environment. Cross your fingers,
> this is gonna be great!
Could anaconda not be smart enough to pull this in t
On Tue, Nov 30, 2010 at 10:13:30PM +0100, Fabian Deutsch wrote:
> Good day,
>
> Am Dienstag, den 30.11.2010, 13:04 -0600 schrieb Matt Domsch:
> > On Mon, Nov 29, 2010 at 08:48:05PM +0530, Rahul Sundaram wrote:
> > > On 11/29/2010 08:27 PM, Matt Domsch wrote:
> > > > On Mon, Nov 29, 2010 at 12:17:2
Good day,
Am Dienstag, den 30.11.2010, 13:04 -0600 schrieb Matt Domsch:
> On Mon, Nov 29, 2010 at 08:48:05PM +0530, Rahul Sundaram wrote:
> > On 11/29/2010 08:27 PM, Matt Domsch wrote:
> > > On Mon, Nov 29, 2010 at 12:17:22AM -0600, Matt Domsch wrote:
> > >> I've just pushed biosdevname-0.3.1 into
On Wed, Dec 01, 2010 at 02:37:04AM +0530, Rahul Sundaram wrote:
>On 12/01/2010 12:34 AM, Matt Domsch wrote:
>
> Can you expand the release notes section of
>
> [1]http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
>
> Please include the benefits in that.
>
> Done.
>
>
On 12/01/2010 12:34 AM, Matt Domsch wrote:
Can you expand the release notes section of
http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
Please include the benefits in that.
Done.
Can you explain why only those particular HP and Dell models are affected by
this change? I
On Mon, Nov 29, 2010 at 08:48:05PM +0530, Rahul Sundaram wrote:
> On 11/29/2010 08:27 PM, Matt Domsch wrote:
> > On Mon, Nov 29, 2010 at 12:17:22AM -0600, Matt Domsch wrote:
> >> I've just pushed biosdevname-0.3.1 into rawhide. This is not yet
> >> installed by default as part of @base, nor is it
On 11/29/2010 08:27 PM, Matt Domsch wrote:
> On Mon, Nov 29, 2010 at 12:17:22AM -0600, Matt Domsch wrote:
>> I've just pushed biosdevname-0.3.1 into rawhide. This is not yet
>> installed by default as part of @base, nor is it used by anaconda, but
>> those changes will come over the next few days.
On Mon, Nov 29, 2010 at 12:17:22AM -0600, Matt Domsch wrote:
> I've just pushed biosdevname-0.3.1 into rawhide. This is not yet
> installed by default as part of @base, nor is it used by anaconda, but
> those changes will come over the next few days.
I've pushed the comps change to pull biosdevna
30 matches
Mail list logo
