[opensuse-factory] wicked wicked
Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked. Tabooing wicked deselects zypper, and breaks too much to remember it all, a vast amount of yast, making software selection during installation take horrendous extra time clicking all those break xxx instead of allow wicked to be installed dialogs. e.g. inexplicable ones like yast2-users. Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/23/2014 08:51 PM, Felix Miata pecked at the keyboard and wrote:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
Tabooing wicked deselects zypper, and breaks too much to remember it all, a vast amount of yast, making software selection during installation take horrendous extra time clicking all those break xxx instead of allow wicked to be installed dialogs. e.g. inexplicable ones like yast2-users.
Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be?
Because the devs will never learn the lesson that they need to get something new /working/ BEFORE making it the default. Does KDE4 and systemd ring any bells? :-) -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/23/2014 10:24 PM, Ken Schneider - openSUSE wrote:
On 01/23/2014 08:51 PM, Felix Miata pecked at the keyboard and wrote:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
Tabooing wicked deselects zypper, and breaks too much to remember it all, a vast amount of yast, making software selection during installation take horrendous extra time clicking all those break xxx instead of allow wicked to be installed dialogs. e.g. inexplicable ones like yast2-users.
Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be?
Because the devs will never learn the lesson that they need to get something new /working/ BEFORE making it the default. Does KDE4 and systemd ring any bells? :-)
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Tumbleweed GeForce GTS 450/PCIe/SSE2 Just updated Tumbleweed to kernel-desktop-3.13.0-9.1.g4b6e17a.x86_64 and installing NVIDIA-Linux-x86_64-331.38.run fails to install, nvidia.ko. Leaving w/o graphical desktop. Booted to kernel-desktop-3.12.8 to access X. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 24 January 2014 01:14:52 Patrick Shanahan wrote:
Tumbleweed GeForce GTS 450/PCIe/SSE2
Just updated Tumbleweed to kernel- desktop-3.13.0-9.1.g4b6e17a.x86_64 and installing NVIDIA-Linux-x86_64-331.38.run fails to install, nvidia.ko. Leaving w/o graphical desktop. Booted to kernel-desktop-3.12.8 to access X.
Hi Patrick See this patch [1], works for compiling 331.38 NVIDIA driver. (For both kernel module and uvm module). Deiu [1] http://cvs.rpmfusion.org/viewvc/rpms/nvidia-kmod/devel/nvidia_3.13_kernel.patch?revision=1.2&root=nonfree&view=markup -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Amuraritei Andrei <sirdeiu@bydeiu.net> [01-24-14 02:12]:
On Friday 24 January 2014 01:14:52 Patrick Shanahan wrote:
Tumbleweed GeForce GTS 450/PCIe/SSE2
Just updated Tumbleweed to kernel-desktop-3.13.0-9.1.g4b6e17a.x86_64 and installing NVIDIA-Linux-x86_64-331.38.run fails to install, nvidia.ko. Leaving w/o graphical desktop. Booted to kernel-desktop-3.12.8 to access X.
See this patch [1], works for compiling 331.38 NVIDIA driver. (For both kernel module and uvm module).
Note that the version indicated is 1.2 and 1.3 is available. Applied 1.3 to the NV...run file and applied with CUDA. tks much, You have credit for a 1/2 gallon of Dos Equis :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Friday 24 January 2014 23:16:48 Patrick Shanahan wrote:
* Amuraritei Andrei <sirdeiu@bydeiu.net> [01-24-14 02:12]:
On Friday 24 January 2014 01:14:52 Patrick Shanahan wrote:
Tumbleweed GeForce GTS 450/PCIe/SSE2
Just updated Tumbleweed to kernel-desktop-3.13.0-9.1.g4b6e17a.x86_64 and installing NVIDIA-Linux-x86_64-331.38.run fails to install, nvidia.ko. Leaving w/o graphical desktop. Booted to kernel-desktop-3.12.8 to access X.
See this patch [1], works for compiling 331.38 NVIDIA driver. (For both kernel module and uvm module).
[1] http://cvs.rpmfusion.org/viewvc/rpms/nvidia-kmod/devel/nvidia_3.13_kernel .patch?revision=1.2&root=nonfree&view=markup Note that the version indicated is 1.2 and 1.3 is available.
Applied 1.3 to the NV...run file and applied with CUDA.
tks much, You have credit for a 1/2 gallon of Dos Equis :^)
Hey, yeah. After I replied to your message, later I was looking through the NVIDIA forum, and leighlinux posted that 1.3 was available. Thanks for the beer. Will settle for some Heineken also ;) Deiu -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-01-24 00:03 (GMT-0600) Larry Finger composed:
Ken Schneider wrote:
Felix Miata composed:
Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be?
Because the devs will never learn the lesson that they need to get something new /working/ BEFORE making it the default. Does KDE4 and systemd ring any bells? :-)
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall.
I tried to return to ifup by reinstalling with wicked tabooed. Ifup in 13.1 is in a package that in 13.2 does not exist. So far I've been unable to get 13.2 networking in that fresh install except by chroot to it from 13.1, which is why I started this thread. So far it's looking like anyone who wants eth0 started by ifup in 13.2 needs to get there by upgrading from a 13.1 that was using ifup. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le vendredi 24 janvier 2014 à 00:03 -0600, Larry Finger a écrit :
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall.
wicked is not wicd.. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 01/24/2014 05:43 AM, Frederic Crozat pecked at the keyboard and wrote:
Le vendredi 24 janvier 2014 à 00:03 -0600, Larry Finger a écrit :
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall.
wicked is not wicd..
Maybe not, but in this thread wicd is wicked. :-) -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-01-24 11:43 (GMT+0100) Frederic Crozat composed:
wicked is not wicd..
http://wicd.sourceforge.net/ makes that seem incorrect. What then is wicd, and how does it differ from wicked? zypper se -s wicd returns null on Factory/13.1 aka 13.2m0. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
In data venerdì 24 gennaio 2014 14:25:12, Felix Miata ha scritto:
On 2014-01-24 11:43 (GMT+0100) Frederic Crozat composed:
wicked is not wicd..
http://wicd.sourceforge.net/ makes that seem incorrect. What then is wicd, and how does it differ from wicked? zypper se -s wicd returns null on Factory/13.1 aka 13.2m0. Completely unrelated project. wicd is, more or less an alternative to networkmanager (stack and gui), used a lot when networkmanager was in not so good state. I think that you can find it in OBS, never shipped with the distro.
Bye. -- * Linux user # 198661 * Home http://www.kailed.net * Powered by openSUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Fri, 24 Jan 2014 11:43:54 +0100 Frederic Crozat <fcrozat@suse.com> wrote:
Le vendredi 24 janvier 2014 à 00:03 -0600, Larry Finger a écrit :
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall.
wicked is not wicd..
"WICD (pronounced like wicked)" [1]_ .. [1] https://help.ubuntu.com/community/WICD - -- Jan Matějka | QA Engineer for Maintenance SUSE s.r.o. | https://www.suse.com/ GPG: A33E F5BC A9F6 DAFD 2021 6FB6 3EBF D45B EEB6 CA8B -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCgAGBQJS6KvxAAoJEIN+7RD5ejahZ34H/jgnnl3LiSvW4AcFAT8ev9yh DhuKY5G4dCmAQ3UyJI3VQzLTrxpFfM8SzneIt6NVzuycNHHFj+hNbPv7WCXh3Cbk 40zzqqyLy8NjPYmNlS6VEvg3JSd12ZFnQY8wwxYwraHrxNDZcEC/6n/A8aTwF9y4 9BzF7hlVNHOMHSArtUasK4DDl9B2mhBRkN0c7+9aXard4JDrysDnVgqq1zf79qIm 5TdH8R2FVyMeZyc1PF07FFNp6JSu3XZIlimPeRRxJTRAB1zdxPbGCMDxVx9UkkIR R7NTWh3u8Ww5znFSLSpT5+wA5NuN/dkN1vK/0GM1Af3p1rzD/G1GXG2IWaj3g9U= =OahG -----END PGP SIGNATURE----- N�����r��y隊Z)z{.���r�+�맲��r��z�^�ˬz��N�(�֜��^� ޭ隊Z)z{.���r�+��0�����Ǩ�
Jan Matejka - 8:21 29.01.14 wrote:
On Fri, 24 Jan 2014 11:43:54 +0100 Frederic Crozat <fcrozat@suse.com> wrote:
Le vendredi 24 janvier 2014 à 00:03 -0600, Larry Finger a écrit :
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall.
wicked is not wicd..
"WICD (pronounced like wicked)" [1]_
That is the other way around, wicd is "wicked", but wicked in this context is not wicd. It is just really badly chosen name for the new project. wicked is brand new thing that also does networking stuff. -- Michal HRUSECKY SUSE LINUX, s.r.o. openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Intentional top post. This thread is using wicd and wicked interchangeably. They are totally different packages. Wicked is brand new and not even in the 13.1 release I don't think. Wicked is in obs and is expected to be a major new feature in 13.2. It will be the default network manager for the next SLES (fall 2014) and was developed internally by suse. Greg Larry Finger <Larry.Finger@lwfinger.net> wrote:
On 01/23/2014 10:24 PM, Ken Schneider - openSUSE wrote:
On 01/23/2014 08:51 PM, Felix Miata pecked at the keyboard and wrote:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
Tabooing wicked deselects zypper, and breaks too much to remember it all, a vast amount of yast, making software selection during installation take horrendous extra time clicking all those break xxx instead of allow wicked to be installed dialogs. e.g. inexplicable ones like yast2-users.
Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be?
Because the devs will never learn the lesson that they need to get something new /working/ BEFORE making it the default. Does KDE4 and systemd ring any bells? :-)
I won't go so far as to say that the devs will never learn; however, wicd (aka wicked) is extremely wicked. I installed a copy to test something for a user, and I also was unable to return to NetworkManager when through. The only thing was to reinstall.
Larry
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Jan 23, Felix Miata wrote:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
wicked by itself should work. But whats most likely broken is writing /etc/sysconfig/network/ifcfg-<interface_name>. What I see with fresh SLE12 installs is that such files get written, but their name lacks the "<interface_name>" part. So neither ifup nor wicked will do anything with such file. My guess is that the fix for the issue you are seeing is to create the files manually, like ifcfg-eth0: BOOTPROTO='dhcp' STARTMODE='onboot' But on the other hand, even though yast did not create the proper ifcfg-* files during fresh install it does write proper files in the running system. So what is your installation source, how do you do a fresh install?
Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be?
Appearently some package has Requires: wicked, and this package is in turn required by other packages? Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-01-24 09:07 (GMT+0100) Olaf Hering composed:
Felix Miata wrote:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all. I tried zypper rm wicked, but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
wicked by itself should work. But whats most likely broken is writing /etc/sysconfig/network/ifcfg-<interface_name>. What I see with fresh
Not a problem here. It was a perfect match to the one used by 13.1.
SLE12 installs is that such files get written, but their name lacks the "<interface_name>" part. So neither ifup nor wicked will do anything with such file.
My guess is that the fix for the issue you are seeing is to create the files manually, like ifcfg-eth0: BOOTPROTO='dhcp' STARTMODE='onboot'
But on the other hand, even though yast did not create the proper ifcfg-* files during fresh install it does write proper files in the running system.
My guess is the problem had to do with the complaint ifup kept making WRT network@eth0.service. I solved it for the instant host by overwriting the installation by cloning from the 13.1 installation and zypper dup'ing it to Factory.
So what is your installation source, how do you do a fresh install?
HTTP from download.opensuse.org's factory started by Grub loading initrd and linux is the normal procedure here.
Ifup has always worked nicely with single NIC systems on a 100% wired LAN, no network "management" required. Why does unneeded network "management" need to be entangled in everything as wicked appears to be?
Appearently some package has Requires: wicked, and this package is in turn required by other packages?
Apparently a big web of interdependencies as many times as I had to click on break package to clear the solver window. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Thu, 23 Jan 2014 20:51:16 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all.
I just installed fresh. The problem was, that no ifcfg-* was created. After I used yast to configure interface everything run just fine. And (comparing with NetworkManager) wicked did not try to undo manual configuration with ifconfig or even dhcpcd.
I tried zypper rm wicked,
You expected it will magically create configuration for interface?
but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
The problem was that yast did not create interface configuration file. How is it related to wicked? It would fail for a traditional ifup as well. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-01-24 22:15 (GMT+0400) Andrey Borzenkov composed:
÷ Thu, 23 Jan 2014 20:51:16 -0500 Felix Miata composed:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all.
I just installed fresh. The problem was, that no ifcfg-* was created. After I used yast to configure interface everything run just fine. And (comparing with NetworkManager) wicked did not try to undo manual configuration with ifconfig or even dhcpcd.
I tried zypper rm wicked,
You expected it will magically create configuration for interface?
You mean /etc/sysconfig/network/ifcfg-eth0? I copied that from 13.1 partition. Or yast made one. I don't remember. That installation no longer exists. Its y2logs do: https://bugzilla.novell.com/show_bug.cgi?id=860394
but couldn't get network to work except by using yast to delete NIC and add it back at every boot. Network@eth0.service refused to survive boot, if it ever got created at all. I couldn't find any wicked instructions anywhere on opensuse.org. Its man page is too terse for me to get a useful enough amount out of it. So I decided to install all over again, starting by tabooing wicked.
The problem was that yast did not create interface configuration file.
Which file did it not create? network@eth0.service? If not, then what? I never did find any network@eth0.service anywhere, though I did see reference to it somewhere among various messages.
How is it related to wicked? It would fail for a traditional ifup as well. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Fri, 24 Jan 2014 13:59:00 -0500 Felix Miata <mrmazda@earthlink.net> пишет:
On 2014-01-24 22:15 (GMT+0400) Andrey Borzenkov composed:
÷ Thu, 23 Jan 2014 20:51:16 -0500 Felix Miata composed:
Yesterday I installed fresh. Result was too much screwed up to make sense of it all.
I just installed fresh. The problem was, that no ifcfg-* was created. After I used yast to configure interface everything run just fine. And (comparing with NetworkManager) wicked did not try to undo manual configuration with ifconfig or even dhcpcd.
I tried zypper rm wicked,
You expected it will magically create configuration for interface?
You mean /etc/sysconfig/network/ifcfg-eth0?
I mean /etc/sysconfig/network/ifcfg-<interface-name>. Interface names are not necessary ethX today.
The problem was that yast did not create interface configuration file.
Which file did it not create? network@eth0.service?
/etc/sysconfig/network/ifcfg-ens3 in my case. How is it called in your case I do not know. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-01-24 23:41 (GMT+0400) Andrey Borzenkov composed:
÷ Fri, 24 Jan 2014 13:59:00 -0500 Felix Miata composed:
On 2014-01-24 22:15 (GMT+0400) Andrey Borzenkov composed:
You expected it will magically create configuration for interface?
You mean /etc/sysconfig/network/ifcfg-eth0?
I mean /etc/sysconfig/network/ifcfg-<interface-name>. Interface names are not necessary ethX today.
They are here. e.g.: # ls -l /etc/sysconfig/network/*eth* -rw-r--r-- 1 root root 133 Dec 21 04:50 /etc/sysconfig/network/ifcfg-eth0 # ls -l /etc/udev/rules.d/*net* -rw-r--r-- 1 root root 371 Jan 24 14:30 /etc/udev/rules.d/70-persistent-net.rules -rw-rw-r-- 1 root root 0 Oct 4 19:05 /etc/udev/rules.d/80-net-name-slot.rules
The problem was that yast did not create interface configuration file.
Which file did it not create? network@eth0.service?
/etc/sysconfig/network/ifcfg-ens3 in my case. How is it called in your case I do not know.
You do now. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2014-01-24 23:41 (GMT+0400) Andrey Borzenkov composed:
÷ Fri, 24 Jan 2014 13:59:00 -0500 Felix Miata composed:
On 2014-01-24 22:15 (GMT+0400) Andrey Borzenkov composed:
You expected it will magically create configuration for interface?
You mean /etc/sysconfig/network/ifcfg-eth0?
I mean /etc/sysconfig/network/ifcfg-<interface-name>. Interface names are not necessary ethX today.
They are here. e.g.: # ls -l /etc/sysconfig/network/*eth* -rw-r--r-- 1 root root 133 Dec 21 04:50 /etc/sysconfig/network/ifcfg-eth0 # ls -l /etc/udev/rules.d/*net* -rw-r--r-- 1 root root 371 Jan 24 14:30 /etc/udev/rules.d/70-persistent-net.rules -rw-rw-r-- 1 root root 0 Oct 4 19:05 /etc/udev/rules.d/80-net-name-slot.rules # cat /proc/cmdline root=/dev/sda10 rw ipv6.disable=1 net.ifnames=0 noresume splash=verbose vga=791 video=1024x768@60 3
The problem was that yast did not create interface configuration file.
Which file did it not create? network@eth0.service?
/etc/sysconfig/network/ifcfg-ens3 in my case. How is it called in your case I do not know.
You do now. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Jan 24, 2014 at 11:41:15PM +0400, Andrey Borzenkov wrote:
/etc/sysconfig/network/ifcfg-ens3 in my case. How is it called in your case I do not know.
So much for "predictable interface names"... :-) Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Mon, 27 Jan 2014 09:18:50 +0100 Michal Kubecek <mkubecek@suse.cz> пишет:
On Fri, Jan 24, 2014 at 11:41:15PM +0400, Andrey Borzenkov wrote:
/etc/sysconfig/network/ifcfg-ens3 in my case. How is it called in your case I do not know.
So much for "predictable interface names"... :-)
Yes, those interfaces are not predictable in normal sense. This is quite misleading and I wish this label could be removed. They are persistent names based on intrinsic interface properties, but this is it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrey Borzenkov wrote:
В Mon, 27 Jan 2014 09:18:50 +0100 Michal Kubecek <mkubecek@suse.cz> пишет:
On Fri, Jan 24, 2014 at 11:41:15PM +0400, Andrey Borzenkov wrote:
/etc/sysconfig/network/ifcfg-ens3 in my case. How is it called in your case I do not know. So much for "predictable interface names"... :-)
Yes, those interfaces are not predictable in normal sense. This is quite misleading and I wish this label could be removed. They are persistent names based on intrinsic interface properties, but this is it.
At least, in Yast, it's possible to assign sensible names such as "eth0". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (15)
-
Amuraritei Andrei -
Andrey Borzenkov -
Daniele -
Felix Miata -
Frederic Crozat -
Greg Freemyer -
James Knott -
Jan Matejka -
Ken Schneider - Factory -
Ken Schneider - openSUSE
-
Larry Finger -
Michal Hrusecky -
Michal Kubecek -
Olaf Hering -
Patrick Shanahan