Samuel Sieb composed on 2019-01-05 23:52 (UTC-0800): > Felix Miata wrote: >> Samuel Sieb composed on 2019-01-05 23:29 (UTC-0800): >>> You don't want to use NetworkManager? >> There's nothing to manage. Setup fixed IP when initialized. Never has reason to be >> changed. It's a test installation on a test PC. > NetworkManager handles that just fine as well. It's pretty light > weight. I believe there's even a mode for one shot setup and quit. On 4th try the upgrade worked. Systemctl status network is generated even though Network Manager and network-scripts are both installed. :-) >>> The initscripts package that contains the "network" initscript is gone >>> in F30. I don't know if it was moved, but it's most likely just gone now. >> http://mirrors.us.kernel.org/fedora/development/rawhide/Everything/x86_64/os/Packages/n/network-scripts-10.01-1.fc29.x86_64.rpm >> sort of suggests not. It contains /etc/rc.d/init.d/ -rwxr-xr-x 1 8353 Aug 6 07:06 network > Not sure what you're trying to point out there. network-scripts is a > subpackage of initscripts which is gone in F30. Do you see a > network-scripts package for F30? I never found a 30 on mirrors.kernel.org. I just assumed whatever is on rawhide would be the same or close enough. >>>> I tried to chroot from F29. I got in, but attempting to ping generates system error. >>> What error? Just that there is no active network interface? >> Simply system error, no details, no clues. > What is the actual text of the message? I already wrote 50% or more of the one line error message. I don't remember whether it was 3 words or 4, but system error were two. >>>> Any suggestions what might generate successful upgrade or a way to repair the >>>> latest? Is it too early to be using --releasever=30? >>> Use the netinst boot image and use the rescue option. That will mount >>> all the necessary mount points and let you chroot. Install NetworkManager. >> Which netinst image? Does it matter which version? How is NM to be used on a >> system with no X? > I don't think it matters which netinst. I usually use the Everything one. > NetworkManager has no relation to X and doesn't need graphical tools. > You can edit the ifcfg files yourself or use nmcli. It is compatible > with the ifcfg files for the network initscript. Moot at this point, but good to know for next time. :-) The actual cause almost certainly has roots in my attempt to streamline the workaround for the upgrade process filling up / with downloaded packages and being unable to proceed. I had previously used dnf to eliminate kde*, kf5* and plasma*. Apparently it took out NM stuff without my noticing. This time I temporarily moved /var to a separate filesystem. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
