On 7/7/24 13:50, Felix Miata wrote:
The TW installer now checks for a newer installation system than that on the booted media, and downloads and starts it instead, if newer exists. I think the 15.6 installer also does this.
This has DIRE unintended consequences where a slow mirror is auto-selected for the user. The downloading system installer 1/6, 2/6, ... takes 1+ HOURS and there is no way to politely cancel it. It only responds to SIGKILL triggering a reboot - back to square one. Ctrl+C or 'q' or ESC has no effect. So if a bad mirror is obtained, the poor user is stuck unless he triggers SIGKILL by issuing Ctrl+Alt+Del. That doesn't seem like desired behavior from the NET-install program.
I don't believe there are existing plans to enable YaST control of network using systemd-network instead of NM or Wicked. To select DIY control with systemd-network is required to click the link on the Installation Summary page Network section that disables the current selection, leaving two links, one for enabling NM, and one for enabling Wicked. In this state, network configuration applicable to NET installation must have come from using linuxrc, and the systemd-network package must be selected for installation if on first boot you wish configuration of systemd-network to be enabled. This is not inherited by the installed system. Systemd-network must be manually configured upon booting the installed system.
To enable systemd-network use:
populate /etc/systemd/network with files to configure your NIC(s) systemctl enabled systemd-networkd.socket
I don't use wireless so all I know about is ethernet with static IPs, and the above is all I've found necessary in most cases. In a limited few installations, all on Fedora IIRC, it has also been necessary to enable systemd-networkd.service.
I'm about to boot back into TW and try again. I have no browser, no e-mail, no wifi, no nothing so far (minimal X install) There are no tools installed to allow configuration of eth0 or wifi -- which is odd. I did fix "solver.onlyRequires = true" in zypp.conf so hopefully the system isn't too polluted at this point.
Repo management service is enabled by openSUSE-repos-<ReleaseName>. openSUSE-repos-NVIDIA tags along if such hardware is detected. Uninstalling them removes the service. Left unlocked, it/they will reappear, unless NVidia hardware is first removed. Whether uninstalling openSUSE-repos-Tumbleweed will populate /etc/zypp/repos.d/ I have no idea. My server provides all the repo files I use for the purpose.
This is new to me. I didn't have any issues with 15.4 doing NET-install and minimal X. Yast kept working fine. I'll see if removing and locking openSUSE-repos-<ReleaseName> will help. I kinda like what openSUSE-repos-NVIDIA did.
I haven't tried YaST Network or Repositories in years. Repos for new installations are simply copied from my LAN server as required. Those named repo-whatever.repo are all discarded in favor of file and repo names lacking redundance, although alias names are each twin to repo name.
I generally copy a bunch over. I have the TW install mounted at /mnt/tw right now, but I was trying to keep the "fresh install" as fresh as possible. In TW, I can mount 15.4 as /mnt/154, so getting to the files isn't a problem. Sorting out where the new problem causing files on TW are that are preventing wifi config is the biggest chore. Will report back after I get back into 15.4 with a wifi connection. -- David C. Rankin, J.D.,P.E.