2013/5/22 Ian Pilcher arequip...@gmail.com:
Did this ever get implemented? Fedora 19 has predictable interface
names turned on, and I'm really not looking forward to having to
clean up the anaconda-created ifcfg- file(s) every time I do a new
install from now on.
I've Googled, but come up
'Twas brillig, and Ian Pilcher at 22/05/13 06:31 did gyre and gimble:
On 01/08/2013 12:27 PM, Lennart Poettering wrote:
On Tue, 08.01.13 12:19, Ian Pilcher (arequip...@gmail.com) wrote:
Will there still be a way to turn this off from the kernel command line?
(I don't see anything on the wiki
'Twas brillig, and Ian Pilcher at 22/05/13 06:31 did gyre and gimble:
On 01/08/2013 12:27 PM, Lennart Poettering wrote:
On Tue, 08.01.13 12:19, Ian Pilcher (arequip...@gmail.com) wrote:
Will there still be a way to turn this off from the kernel command line?
(I don't see anything on the wiki
2013/5/22 Michael Biebl mbi...@gmail.com:
IMPORT{cmdline}=net.ifnames
ENV{net.ifnames}==0, GOTO=net_name_slot_end
IMPORT{cmdline} is supposed to import a command line parameter, so I
would try booting with net.ifnames=0.
No need to ask google :-)
It's also part of the systemd.directives
On 05/22/2013 05:31 AM, Ian Pilcher wrote:
Did this ever get implemented? Fedora 19 has predictable interface
names turned on, and I'm really not looking forward to having to
clean up the anaconda-created ifcfg- file(s) every time I do a new
install from now on.
Did you file a bug against
On 05/22/2013 04:00 AM, Jóhann B. Guðmundsson wrote:
Did you file a bug against Anaconda?
No, why would I? AFAIK, using the systemd-provided network interface
names is the intended behavior.
(I happen to prefer the old eth*/wlan* names, but that's just a personal
preference.)
--
On 05/22/2013 01:48 PM, Ian Pilcher wrote:
On 05/22/2013 04:00 AM, Jóhann B. Guðmundsson wrote:
Did you file a bug against Anaconda?
No, why would I? AFAIK, using the systemd-provided network interface
names is the intended behavior.
To me it looks like anaconda does not behave correctly if
On 05/22/2013 09:11 AM, Jóhann B. Guðmundsson wrote:
To me it looks like anaconda does not behave correctly if
net.ifnames=0/1 is passed to the kernel command line since you have to
clean up those anaconda-created ifcfg- file(s) after install.
Are you saying that you tested with net.ifnames=0
On 05/22/2013 02:55 PM, Ian Pilcher wrote:
On 05/22/2013 09:11 AM, Jóhann B. Guðmundsson wrote:
To me it looks like anaconda does not behave correctly if
net.ifnames=0/1 is passed to the kernel command line since you have to
clean up those anaconda-created ifcfg- file(s) after install.
Are you
Jóhann B. Guðmundsson (johan...@gmail.com) said:
On 05/22/2013 01:48 PM, Ian Pilcher wrote:
On 05/22/2013 04:00 AM, Jóhann B. Guðmundsson wrote:
Did you file a bug against Anaconda?
No, why would I? AFAIK, using the systemd-provided network interface
names is the intended behavior.
To me
On 05/22/2013 05:57 PM, Bill Nottingham wrote:
Jóhann B. Guðmundsson (johan...@gmail.com) said:
On 05/22/2013 01:48 PM, Ian Pilcher wrote:
On 05/22/2013 04:00 AM, Jóhann B. Guðmundsson wrote:
Did you file a bug against Anaconda?
No, why would I? AFAIK, using the systemd-provided network
On Wed, May 22, 2013 at 10:48:57AM +0200, Michael Biebl wrote:
2013/5/22 Michael Biebl mbi...@gmail.com:
IMPORT{cmdline}=net.ifnames
ENV{net.ifnames}==0, GOTO=net_name_slot_end
IMPORT{cmdline} is supposed to import a command line parameter, so I
would try booting with net.ifnames=0.
On 01/08/2013 12:27 PM, Lennart Poettering wrote:
On Tue, 08.01.13 12:19, Ian Pilcher (arequip...@gmail.com) wrote:
Will there still be a way to turn this off from the kernel command line?
(I don't see anything on the wiki page.)
biosdevname had this, and we have been thinking of adding this
HI,
we just start using the network name schema. Anybody
can explain how the LAbels:
ID_NET_NAME_ONBOARD_LABEL=Ethernet Port 1
defined here:
http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c#n52
are exposed to user land tools? Can a user land tool i.e. tcpdump
On Wed, Feb 13, 2013 at 7:19 PM, Tomasz Torcz to...@pipebreaker.pl wrote:
On Tue, Feb 12, 2013 at 09:07:00AM +0100, Jan Engelhardt wrote:
On Monday 2013-01-07 23:29, Lennart Poettering wrote:
For your example the new code would pick a name of enp0s0d0, i.e. for
pci bus 0, slot 0, and dev_id
On Wed, Feb 13, 2013 at 07:29:10PM +0100, Kay Sievers wrote:
On Wed, Feb 13, 2013 at 7:19 PM, Tomasz Torcz to...@pipebreaker.pl wrote:
On Tue, Feb 12, 2013 at 09:07:00AM +0100, Jan Engelhardt wrote:
On Monday 2013-01-07 23:29, Lennart Poettering wrote:
For your example the new code
On Wed, Feb 13, 2013 at 7:35 PM, Tomasz Torcz to...@pipebreaker.pl wrote:
On Wed, Feb 13, 2013 at 07:29:10PM +0100, Kay Sievers wrote:
On Wed, Feb 13, 2013 at 7:19 PM, Tomasz Torcz to...@pipebreaker.pl wrote:
On Tue, Feb 12, 2013 at 09:07:00AM +0100, Jan Engelhardt wrote:
On Monday
On Monday 2013-01-07 23:29, Lennart Poettering wrote:
For your example the new code would pick a name of enp0s0d0, i.e. for
pci bus 0, slot 0, and dev_id 0.
Is it Solaris time yet? enp0s0d0, that's just like c0t0d0s0. And
next, we'll have /pci@0/pci@0/pci@1/pci@0/pci@2/network@0,1 as
interface
Seems we need to introduce aliases available across all tools ;)
What about eth0 as label to show the heritage ???
Honestly, how are the labels exposed to userland tools?
--
Holger Winkelmann
Travelping GmbH
+49-171-5594745
### Sent from a mobile device. Sorry for brevity and typos... ###
2013/1/8 Lennart Poettering lenn...@poettering.net:
Heya,
a few days ago Kay commited a change to git that made predictable
network interface names the default for the upcoming systemd/udev
197. To explain what this is about we put together this wiki document:
Hi,
I.e. fe0/01 for fast Ethernet port in first slot with a multi port NIC.
Well, as these names show up in sysfs and hence in the file system they
can't really include slashes since that's not allowed in file
names. This is a general kernel limitation.
I know about limitations in
On Tue, 08.01.13 16:36, Alexander E. Patrakov (patra...@gmail.com) wrote:
2013/1/8 Lennart Poettering lenn...@poettering.net:
Heya,
a few days ago Kay commited a change to git that made predictable
network interface names the default for the upcoming systemd/udev
197. To explain what
On Tue, 08.01.13 13:37, Holger Winkelmann (h...@travelping.com) wrote:
Hi,
I.e. fe0/01 for fast Ethernet port in first slot with a multi port NIC.
Well, as these names show up in sysfs and hence in the file system they
can't really include slashes since that's not allowed in file
On Tue, 08.01.13 12:19, Ian Pilcher (arequip...@gmail.com) wrote:
On 01/07/2013 03:48 PM, Lennart Poettering wrote:
Anyway, comments welcome,
Will there still be a way to turn this off from the kernel command line?
(I don't see anything on the wiki page.)
biosdevname had this, and we
Heya,
a few days ago Kay commited a change to git that made predictable
network interface names the default for the upcoming systemd/udev
197. To explain what this is about we put together this wiki document:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
Hi,
Generally great idea specially embedded people like us will welcome. Do you
have any idea it's possible to allow the / slash in interface names as known
and seen in other network devices? It could be used to name interface
regarding the slot and port?
I.e. fe0/01 for fast Ethernet
On Mon, 07.01.13 23:06, Holger Winkelmann (h...@travelping.com) wrote:
Hi,
Generally great idea specially embedded people like us will
welcome. Do you have any idea it's possible to allow the / slash in
interface names as known and seen in other network devices? It could
be used to name
27 matches
Mail list logo
