Subscribe to receive announcements about Devuan - 10.05.18, 00:16: > Dear Init Freedom Lovers, > > Once again the Veteran Unix Admins salute you! > > We are happy to announce that the Devuan 2.0 ASCII Release Candidate > is now available thanks to the support, feedback, and collaboration of > the Devuan community. Devuan 2.0 ASCII Stable will be following soon. > > The Devuan 2.0 ASCII RC installer now offers a wider variety of > Desktop Environments including XFCE, KDE, MATE, Cinnamon, LXQT (with > others available post-install). In addition, there are options for > "Console productivity" with hundreds of CLI and TUI utils, as well as > a minimal base system ideal for servers.
Marvelous! Congratulations! Thank you for your dedication! I am late in adopting Devuan for my systems. I think I am generally quite conservative about switching to a different distribution, if I have one that mostly works. Even when it is similar. One part of this is: I first like to see whether the new distributor is serious about long-term support of the distribution and it looks like you are! Also I occasionally ran into annoyances with Systemd and a total lack of willingness of upstream and partly lack of willingness of distributors like Debian or Red Hat to do anything about them. I already prepared two server VMs for switching to Devuan. I purged the systemd package from the system. And by doing that disconnected one of them from the network by rebooting it cause purging systemd removed a file from /etc/systemd that caused the old interface names like "eth0" still to be in effect. After removing that file the interface was called "ens32", breaking my network configuration. I wonder whether to file a bug report about that with Debian. As purging systemd package should *never ever* change network interface names (that is the business of udev or something like it). So on one the the VMs, my backup VM the interface is now called "ens32". On the other VM, my main server VM, it is still "eth0" cause I used "net.ifnames=0" in kernel command line. I´d like to switch over my backup VM first and wonder whether the network device with Devuan ASCII will be called "eth0" again. Thats totally fine with me, however I´d like to know before hand, so I can adapt /etc/network/interfaces before repeating. Cause I have no direct console access to the machine. I can get temporary access if need be, but best would be when it is not required. As for my main server VM: I am likely going with a new Devuan ASCII install anyway, as the old VM is still 32-bit and I just don´t feel like cross grading (and dealing with a lot of issues). So I wait for a new VM to be created for me to install Devuan ASCII directly on and then migrate my services one by one. I bet I´d like to use OpenRC on both of them in order to learn something new. > Upgrade paths from Debian Jessie, Devuan Jessie, and Debian Stretch > are available. Please see the instructions at: > https://devuan.org/os/documentation/dev1fanboy/ You are still using "apt-get". With Debian Stretch and later I switched my habit to using the shorter, newly written "apt" command. Also I love "This site is a cookie-free zone" :) Mine is too. I also wonder about migrating my main laptop. I think I first will give myself some time to have experiences with the server VMs, before attempting to do anything with the laptop. There is a huger complexity involved for migrating a laptop with a ton of applications and usage scenarios. Especially I wonder about network without Network Manager, but on a Plasma desktop – no, I won´t switch to something else. I have the following scenarios for the laptop: - Cable based network with DHCP, but at one place with 801.x. - Different, mostly WPA2 based, WLAN - OpenVPN connection for employer network access I meanwhile – after a long time of installing and purging Network Manager out of frustration – use Network Manager for all of this. How would this play out with Devuan ASCII? Or well Ceres, as I am currently using Debian GNU/Linux Sid on that machine. For OpenVPN I bet I would be fine using a text based configuration file + some script to set up some routes again. But the other stuff should work with some kind of GUI that is working with Plasma desktop. I bet I may be out of luck with that. Another thing is audio: Similar to Network Manager I meanwhile also use Pulseaudio for everything. I think I had even more install and purge cycles with that one. It was total crap for me till about Pulseaudio 7 or so. It is now mostly working nicely. Everything means: - Playback with Amarok, Firefox, Chromium, VLC and others. - USB sound speakers - Bluetooth based headset + Twinkle softphone - Rarely Skype (I am quite good at avoiding it) How would this play out on Devuan? Can I still use Pulseaudio or what would you recommend? I hope for Pipewire to be better, but since it comes from Red Hat developers it may depend on Systemd. Any other experiences with Plasma desktop on Ceres? What does work? What does not? Thanks, -- Martin _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
