Hello. I just created a fresh master node from the most recent ISO, then went to replace wicked with systemd-network, but when I attempt to remove wicked, zypper shows that wicked is now part of the basesystem pattern? Can someone elaborate on what else wicked is being used for to cause this dependency? If it's not used to drive any of the container components, then why the strict dependency? ------------------------------------------------- This free account was provided by VFEmail.net - report spam to abuse@vfemail.net ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options!
On 5. Sep 2021, at 04:36, cornfeedhobo
wrote: Hello. I just created a fresh master node from the most recent ISO, then went to replace wicked with systemd-network, but when I attempt to remove wicked, zypper shows that wicked is now part of the basesystem pattern?
Can someone elaborate on what else wicked is being used for to cause this dependency? If it's not used to drive any of the container components, then why the strict dependency?
MicroOS is a narrowly defined operating system, designed, built, tested and released for single purpose use cases. This by its very definition means we don’t support all the possibilities that exist in the Tumbleweed codebase. We only test and support wicked, so we have a hard dependency in the patterns that define MicroOS. You can of course go wild and customise things if you don’t mind deviating from the patterns. Hope this clears that up.
participants (2)
-
cornfeedhobo
-
Richard Brown