* Jan Engelhardt <jengelh@inai.de> [05-02-15 10:29]:
On Saturday 2015-05-02 13:53, Patrick Shanahan wrote:
* Felix Miata <mrmazda@earthlink.net> [05-02-15 02:39]:
Patrick Shanahan composed on 2015-05-01 22:43 (UTC-0400):
perhaps, NetworkMissManager as I have four remote boxes which fail 80% of the time, but not with wicked.
I have one test box without NM and with Wicked, with default target multi-user, with nearly 200 noauto nfs mounts in fstab (same exact entries as all my PCs running Linux, cut and pasted from template), that if TW booted with 5 on cmdline produces:
instead of any NFS mounts when I try mounting them, simply booting with 5, but not without. If booted normally without 5 or with 3, those mounts mount normally. My LAN has no more than one NIC per PC, all on fixed IP, and none have wireless. A difference between whether NFS mounting works or not according to whether X is running seems inexplicable, and never seen here before there was Wicked.
And using NM booting to runlevel 3/multi-user has *always* failed to provide network communication on any of my machines, wireless or wired, [...] <soap-box> Currently the suit linux was always strong on, networking, is no longer so. </soap-box>
Since networkd is in TW now, new possibilities open up :)
as in /usr/lib/systemd/systemd-networkd, systemd-219-5.1.x86_64, as I fail to find the package "networkd". What does it accomplish re wicked/NetworkManager? tks, -- (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