Re: eth0 again - the end

On 21.07.2014 11:30, poma wrote: On 21.07.2014 07:35, Amadeus W.M. wrote: [systemd-devel] 70-persistent-net.rules http://lists.freedesktop.org/archives/systemd-devel/2013-April/010343.html README.Fedora-18 http://pkgs.fedoraproject.org/cgit/systemd.git/tree/README.Fedora-18?h=f18#n17 0005-F18

Re: eth0 again

On Mon, 21 Jul 2014, Paul Cartwright wrote: On 07/20/2014 09:39 PM, Thomas Cameron wrote: It's doing exactly the opposite of what I want. Have you tried this? http://www.cyberciti.biz/faq/howto-linux-rename-ethernet-devices-named-using-udev/ -- I have the same issue, and I don't have this

Re: eth0 again

On 07/20/2014 09:39 PM, Thomas Cameron wrote: >> > It's doing exactly the opposite of what I want. >> > >> > > Have you tried this? > > http://www.cyberciti.biz/faq/howto-linux-rename-ethernet-devices-named-using-udev/ > -- I have the same issue, and I don't have this file they say to modify..

Re: eth0 again - the end

On 21.07.2014 07:35, Amadeus W.M. wrote: [systemd-devel] 70-persistent-net.rules http://lists.freedesktop.org/archives/systemd-devel/2013-April/010343.html README.Fedora-18 http://pkgs.fedoraproject.org/cgit/systemd.git/tree/README.Fedora-18?h=f18#n17 0005-F18-Revert-udev-network-device-renami

Re: eth0 again - the end

> > [systemd-devel] 70-persistent-net.rules > http://lists.freedesktop.org/archives/systemd-devel/2013-April/010343.html > > README.Fedora-18 > http://pkgs.fedoraproject.org/cgit/systemd.git/tree/README.Fedora-18?h=f18#n17 > > 0005-F18-Revert-udev-network-device-renaming-immediately-.patch > htt

Re: eth0 again

On Mon, 21 Jul 2014 04:40:16 +0100, Marko Vojinovic wrote: > On Sun, 20 Jul 2014 23:53:33 + (UTC) > "Amadeus W.M." wrote: >> >> Unfortunately the device is sill named em1, not eth0. So it's not NM. >> I don't understand why the udev rules files are ignored. Bug maybe? >> I'll report it and

Re: eth0 again

> I just tested on my machine... All I did was add net.ifnames=0 to the > linux16 line of /boot/grub2/grub.conf: > >> [tcameron@case ~]$ grep vmlinuz /boot/grub2/grub.cfg >> linux16 /vmlinuz-3.10.0-123.4.2.el7.x86_64 >> root=UUID=e69ef7fa-d3c3-4d88-972b-31c7cb65777c ro vconsole.keymap=us

Re: eth0 again

On Sun, 20 Jul 2014 23:53:33 + (UTC) "Amadeus W.M." wrote: > > Unfortunately the device is sill named em1, not eth0. So it's not NM. > I don't understand why the udev rules files are ignored. Bug maybe? > I'll report it and see what happens. AFAIK udev rules allow you to rename your networ

Re: eth0 again - the end

On 20.07.2014 17:54, Amadeus W.M. wrote: I have to install Matlab on a Fedora 20 machine and I need to rename the network device to eth0, or else Matlab won't install. This is a known issue: http://www.mathworks.com/matlabcentral/answers/100235-why-can-t-i-activate-matlab-or-start-the-license-ma

Re: eth0 again

On 07/20/2014 09:08 PM, Amadeus W.M. wrote: > That may be useful. Looks like udevinfo is superseeded by udevadm. Other > than that, udevadm shows no sign of eth0: > > [root@phoenix ~]# udevadm info --query=all --path /sys/class/net/em1 > P: /devices/pci:00/:00:1e.0/:02:0c.0/net/em1

Re: eth0 again

>> >> > Has anybody referred you to this? > > http://www.cyberciti.biz/faq/howto-linux-rename-ethernet-devices-named- using-udev/ > > I have no idea if it works, but it seems straightforward... > > billo Not that particular link, but that's covered here: http://www.freedesktop.org/wiki/Softwar

Re: eth0 again

On Sun, 20 Jul 2014 20:42:57 -0500, Thomas Cameron wrote: > On 07/20/2014 08:08 PM, Amadeus W.M. wrote: >> On Sun, 20 Jul 2014 20:55:46 -0400, Tom Horsley wrote: >> >>> On Sun, 20 Jul 2014 23:51:27 + (UTC) >>> Amadeus W.M. wrote: >>> This is degenerating in an off-topic discussion. The q

Re: eth0 again

On 07/20/2014 08:08 PM, Amadeus W.M. wrote: > On Sun, 20 Jul 2014 20:55:46 -0400, Tom Horsley wrote: > >> On Sun, 20 Jul 2014 23:51:27 + (UTC) >> Amadeus W.M. wrote: >> >>> This is degenerating in an off-topic discussion. The question is how to >>> rename the network device back to eth0. Let's

Re: eth0 again

On 07/20/2014 08:08 PM, Amadeus W.M. wrote: > On Sun, 20 Jul 2014 20:55:46 -0400, Tom Horsley wrote: > >> On Sun, 20 Jul 2014 23:51:27 + (UTC) >> Amadeus W.M. wrote: >> >>> This is degenerating in an off-topic discussion. The question is how to >>> rename the network device back to eth0. Let's

Re: eth0 again

On Sun, 20 Jul 2014, Amadeus W.M. wrote: On Sun, 20 Jul 2014 09:59:15 -0600, Kevin Fenzi wrote: That's why I'm so baffled. Neither the old nor the new methods work. If I boot interactively, what should I be looking for? Has anybody referred you to this? http://www.cyberciti.biz/faq/howto

Re: eth0 again

On Sun, 20 Jul 2014 20:55:46 -0400, Tom Horsley wrote: > On Sun, 20 Jul 2014 23:51:27 + (UTC) > Amadeus W.M. wrote: > >> This is degenerating in an off-topic discussion. The question is how to >> rename the network device back to eth0. Let's focus. > > At this point, "use the source, Luke" a

Re: eth0 again

On Sun, 20 Jul 2014 19:50:44 -0500, Thomas Cameron wrote: > On 07/20/2014 03:30 PM, JD wrote: >> On Sun, Jul 20, 2014 at 1:49 PM, Thomas Cameron >> > > >> wrote: >> >> >> If you disable NM, you need to enable network. From a local console >> (in oth

Re: eth0 again

On Sun, 20 Jul 2014 23:51:27 + (UTC) Amadeus W.M. wrote: > This is degenerating in an off-topic discussion. The question is how to > rename the network device back to eth0. Let's focus. At this point, "use the source, Luke" appears to be the only option :-( I see on my system in dmesg outp

Re: eth0 again

On 07/20/2014 03:30 PM, JD wrote: > On Sun, Jul 20, 2014 at 1:49 PM, Thomas Cameron > mailto:thomas.came...@camerontech.com>> > wrote: > > > If you disable NM, you need to enable network. From a local console (in > other words, don't do this over a network session like ssh): > > syst

Re: eth0 again

Amadeus W.M. wrote: > This is degenerating in an off-topic discussion. The question is how to > rename the network device back to eth0. Let's focus. As a matter of interest, what happens if in /etc/sysconfig/network-scripts you write ifcfg-enp2s0, say, as DEVICE=eth1 TYPE=Ethernet ... ? I d

Re: eth0 again

> > If you disable NM, you need to enable network. From a local console (in > other words, don't do this over a network session like ssh): > > systemctl disable NetworkManager.service systemctl stop > NetworkManager.service systemctl enable network systemctl start network > > Thomas Unfortunat

Re: eth0 again

> > Well, desktop fans will soon fall into the minority :) This is degenerating in an off-topic discussion. The question is how to rename the network device back to eth0. Let's focus. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://

Re: eth0 again

On Mon, 21 Jul 2014 00:27:23 +0100 Marko Vojinovic wrote: > So there will always be a market for desktops. Not to mention big racks full of servers, which also tend not to flit from Starbucks to Starbucks :-). -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscript

Re: eth0 again

On Sun, 20 Jul 2014 16:16:15 -0600 JD wrote: > > Well, desktop fans will soon fall into the minority :) Comparing the number of smartphones, tablets and laptops to desktops, they already are a minority. However... If anything, the paradigm of a "workstation" is certainly not going away. Program

Re: eth0 again

On 07/20/2014 03:16 PM, JD wrote: Well, desktop fans will soon fall into the minority :) Don't bet on it. A desktop not only gives you more bang for the buck than a laptop, it's much easier to upgrade or expand. In fact, I've never yet needed to buy a pre-built desktop because I have a good

Re: eth0 again

On Sun, Jul 20, 2014 at 2:41 PM, Joe Zeff wrote: > > On 07/20/2014 01:30 PM, JD wrote: >> >> D >> oesn't this prevent you from connecting to >> open hotspots? >> >> The >> nm-applet >> will not be able to communicate with NM >> and thus will not be able to list detected ssid's. > > > Not everybody

Re: eth0 again

On 07/20/2014 01:30 PM, JD wrote: D ​oesn't this prevent you from connecting to open hotspots? ​ ​The ​ nm-applet ​ will not be able to communicate with NM and thus will not be able to list detected ssid's.​ Not everybody is using a laptop. Right now, I'm working on a desktop that's connected

Re: eth0 again

On Sun, Jul 20, 2014 at 1:49 PM, Thomas Cameron < thomas.came...@camerontech.com> wrote: > > If you disable NM, you need to enable network. From a local console (in > other words, don't do this over a network session like ssh): > > systemctl disable NetworkManager.service > systemctl stop NetworkM

Re: eth0 again

On 07/20/2014 10:54 AM, Amadeus W.M. wrote: > Also, NetworkManager might have something to do with this, because if I > right-click the NW applet -> Edit Connections, I do have a connection named > eth0, but if I try to edit that, the device MAC address is > > 00:0c:f1:bc:29:fe (em1) > > So NW

Re: eth0 again

On Sun, 20 Jul 2014 15:54:41 +, Amadeus W.M. wrote: > I have to install Matlab on a Fedora 20 machine and I need to rename the > network device to eth0, or else Matlab won't install. This is a known issue: > > http://www.mathworks.com/matlabcentral/answers/100235-why-can-t-i-activate-matlab-

Re: eth0 again

On Sun, 20 Jul 2014 16:13:23 + (UTC) "Amadeus W.M." wrote: > > I tried that (biosdevname=0) first, before I saw the new ways. No go. Well, it's possible, and even likely that you have both. ;) ie, you are disabling the systemd one, but the biosdevname one kicks in then. In any case, if yo

Re: eth0 again

On Sun, 20 Jul 2014 09:59:15 -0600, Kevin Fenzi wrote: > On Sun, 20 Jul 2014 15:54:41 + (UTC) > "Amadeus W.M." wrote: > >> I have to install Matlab on a Fedora 20 machine and I need to rename >> the network device to eth0, or else Matlab won't install. This is a >> known issue: >> >> http:/

Re: eth0 again

On Sun, 20 Jul 2014 15:54:41 + (UTC) "Amadeus W.M." wrote: > I have to install Matlab on a Fedora 20 machine and I need to rename > the network device to eth0, or else Matlab won't install. This is a > known issue: > > http://www.mathworks.com/matlabcentral/answers/100235-why-can-t-i-activat