A brand new network namespace doesn’t have any network interfaces. When you start a process in a namespace, all its child processes will start there too. It’s like a little network jail, and the functionality is baked into the kernel / is kernel enforced.
I use this to keep certain processes on a vpn, with no need for interface-binding support from the process, or a vpn-killswitch.
Another fun fact, this is the functionality that enables containerization, like docker/podman
I'm excited for this one. It seems to be the last 15.X release until whatever openSUSE ALP does. I'm probably going to switch my servers to MicroOS, but I'm happy that I get another year or so with 15.6.
Congrats on the hard work everyone! I'm out of town for the release, but I might upgrade my VPN server remotely to join in a little.
Excellent news about Aeon and the development of an own installer. The last time I installed Aeon it didn't allow automatic user login, is this possible anymore? Thanks
There is still an issue that the update want delete the steam package because of a broken dependency.
2 Problems:
Problem: 1: the installed calibre-7.4.0-2.3.x86_64 requires 'libQt6Gui.so.6(Qt_6.7.0_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.7.0-2.2.x86_64
Problem: 2: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided
deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64
Problem: 1: the installed calibre-7.4.0-2.3.x86_64 requires 'libQt6Gui.so.6(Qt_6.7.0_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.7.0-2.2.x86_64
Solution 1: Following actions will be done:
keep obsolete libQt6Gui6-6.7.0-2.2.x86_64
keep obsolete libQt6Core6-6.7.0-2.2.x86_64
keep obsolete libQt6DBus6-6.7.0-2.2.x86_64
keep obsolete libQt6OpenGL6-6.7.0-2.2.x86_64
keep obsolete libQt6Widgets6-6.7.0-2.2.x86_64
Solution 2: deinstallation of calibre-7.4.0-2.3.x86_64
Solution 3: break calibre-7.4.0-2.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 2
Problem: 2: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided
deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64
Solution 1: deinstallation of steam-1.0.0.79-1.4.x86_64
Solution 2: keep obsolete glibc-locale-base-32bit-2.39-7.1.x86_64
Solution 3: break steam-1.0.0.79-1.4.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c):
The main benefit is that the base system is immutable, which should make it much more reliable. So to get new software, instead of doing a zypper install ..., you'd leave the base system alone and only install packaged apps (e.g. flatpaks). That way you don't get conflicts between package versions and upgrades can be predictable.
I don't have direct experience with it, so I don't know how well that works in practice. But I definitely like the idea of using it for my NAS, which doesn't need a lot of updates. It currently runs Leap, but MicroOS should be a relatively straight-forward switch.
I'm thinking of switching to Aeon from Tumbleweed, but i always wonder how you would work with cli tools, like LaTeX or various compilers. Is distrobox the way to go? Does it work seamless?
Same. I think you just use transactional-update instead of zypper when you're ready to install something permanently. I don't know what the package selection looks like though.
But anything that's going to need frequent updates should probably be installed outside of transactional-update. For compilers, I generally use some kind of compiler version manager (e.g. rustup for Rust), which would be outside of the immutable base.
Not sure why they included random Python packages in the KDE Frameworks section.
Good work to everyone patching the various exploits, April was a spicy month. Oh, and I'm loving KDE 6, so awesome work getting the ready too (I think that was last month though).
Anyone here using Slowroll as a daily driver? I guess the upgrading to Plasma 6 will be quite smoother than with Tumbleweed, which clearly shows the utility of this distribution, but I was wondering about how it goes as a daily driver.
Also, anyone knows whether consecutive snapshot upgrades are openQA’d specifically for Slowroll?
Already wondered what’s causing a 5GB Update, but this explains it:
For snapshot 0328, Ring0 has been completely bootstrapped (as the attack vectors for xz were not fully known, we went the safest route) and for 0329 all of Tumbleweed rebuilt against that new base; Ezpect that snapshot to appear ‘large’ (even though many packages will not be different).
I wanted to try a different DE to get things working, but with network manager down I couldn’t install anything else! Tumbleweed already had IceWM, but without any networkmanager control there either.
Course that was before I discovered I didn’t need any internet to finish the job and fix it. I assumed the update completed but broke something, and hoped against hope there’d be a fix issued quickly that I could further update to.
P.S. I assume you mean zypper dup, but perhaps you’re using the new Irish Culinary/Political Linux, and supper DUP is the right command.
I had more or less the same problem in my laptop and in my main PC. But you can get around it just by login again and doing the update through zypper. I believe it restarts the session 3 times, and one of those after login, you just have a black screen. Use Ctrl+Alt+T to bring up the terminal and zypper dup again. After zypper is done just restart and everything will be fine.
Did this with both PCs and both are working with no problems.
Yeah, if I’d known what was going on I could have just switched to VT1 straight away and finished the update. Did the other machine fine by updating from VT1 from the start.
openSUSE
Hot