You are not logged in.
What's the average amount of days in uptime that you keep your Devuan-installed systems on before a reboot is necessary?
Although I'm using Devuan Ceres full-time, I usually keep mine on for at least thirty days (but even longer for systems that aren't my top priorities), provided there are no issues needing to be resolved in that time frame. I'm not a fan of rebooting every other hour because an update broke something or I just did a minor kernel upgrade, although I keep in mind to not go crazy on the energy costs (I know you can hibernate, but I don't trust it at all). Nevertheless, all my systems are hooked up via UPS, in case shit hits the fan.
How about your systems? I'd like to keep one going for several months or even a whole year, but I'm in an area where air quality is generally bad and dust builds up quickly.
Devuan Ceres is amazing and far more stable than any other "stable" desktop GNU/Linux distro I've tried. Been running it for two months straight without a single error (current kernel is the 5.8 branch), and in my experience, this showcases the best of both worlds (for stability and updates). I never liked doing major upgrades, anyway.
Thunderbird is both a blessing (stable, easy-to-use GUI) and a curse (Mozilla). Are there any noteworthy forks of it, just as Firefox itself has been forked left and right over the decades?
Thanks for the heads-up. I remember reading the thread before, but forgot about the pinning specifics for MX GNU/Linux. Nevertheless, the Systemd pinning is crucial when including repositories such as those in.
I saw this on a different forum, so I figured this thread would be interesting to see what we're all using to pull in packages and updates from.
When I installed Beowulf, I had the security, backports, and updates branches thrown in for good measure. Now that I'm predominantly on Ceres, those are no longer necessary. I also like to keep all my sources on the same file, rather than individual files per repository. It just makes things a lot simpler.
I added WineHQ's repository to get the most out of my Wine-dependent programs, and Pale Moon is the least sucky graphical browser in my opinion.
deb http://deb.devuan.org/merged ceres main contrib non-free
deb https://dl.winehq.org/wine-builds/debian/ bullseye main
deb https://download.opensuse.org/repositories/home:/stevenpusser/Debian_Unstable/ /And, here's my permanent Systemd blacklist (just in case I decide to add MX GNU/Linux repositories for the GUI tools):
Package: systemd
Pin: release *
Pin-Priority: -1
Package: *systemd*
Pin: release *
Pin-Priority: -1
Package: systemd:amd64
Pin: release *
Pin-Priority: -1
Package: systemd:i386
Pin: release *
Pin-Priority: -1[rant]
Moral of the story: The Crucial BX500 series SSDs are utter crap.Of that pair of SSDs, one is dead as a doornail (doesn't register on the bus), the other is clearly dying.
Both are less than a year old and still under warranty, but I'll be throwing them in the trash rather than returning them - the last thing I want is more of the same.
Both have history of hitting ~70c and thermal throttling under sustained write loads, despite the enclosure and the drives directly above them never breaking 26c.
The nasty plastic casing never even gets warm, and now that I've dissected one I see somebody at crucial thinks putting a thermal pad on the controller is a luxury. 70c is listed as max operating and they never exceeded it, but I'll bet a cookie heat is why they died.Crucial, your budget SSD line gets a solid F from me. The Kingston A400 series is not only cheaper, it's also built properly and doesn't constantly try to cook itself.
I wanted budget SSDs for that filesystem, and expected budget performance. What I didn't expect was something so shitty it can't even sustain the already mediocre performance numbers without overheating.
FWIW, a BX500 reporting 70c writes at ~7MB/s.
[/rant]
That's disappointing. I actually own a couple of Crucial MX500s, and they've yet to disappoint me in the two years I've been using them. Temperature spikes have never been an issue, and it's been a pretty bad summer in my area. The HP SSDs I've owned, however, were already having multiple bad sectors within a few months of using them. Now, those are the cheaply produced SSDs (not surprised, since HP is a shit brand).
I might try out a Kingston SSD next time. I do use their HyperX Fury line for DDR3 memory, which is pretty nice and fast.
Personally, I don't use display managers, so starting the X session via command line is simple enough for me. I remember liking LXDM a lot, and as far as I can recall, it's not at all affected by Systemd.
Pretty cool, indeed. Great way to entice fans of Gentoo, Arch GNU/Linux, and other such distros to try out Devuan and see what it's all about.
The "unstable" Ceres is more stable than most other "stable" distros. Crazy world we live in. ![]()
I'm fine with Pale Moon. It's the only active fork that supports XUL. The developers might be interesting characters and the browser probably does stifle from limited resource power, but considering that I have JavaScript turned off almost always, pages load blazing fast, anyway.
Another Firefox fork that I like is IceCat, which is created by and for freetards. Too bad there isn't an official repository to automatically receive updates through APT. I never bother with the Tor feature, since Tor Browser is there for a reason (to keep things neat and tidy with configuration profiles).
Otter Browser is great, but it hasn't been updated in a while, hasn't it? At least it's closer to what Opera was like, before a Chinese corporation bought it and installed all sorts of backdoors. Even the "VPN" can't be trusted one bit.
For a Chromium fork that I use, Iridium Browser is solid. It's just that the Debian build is outdated. Otherwise, not interested in Googleshit.
Bathory - In Nomine Satanas
The first three Bathory albums are simply masterpieces of black metal.
Currently have Saxon's Metalhead blasting out of these speakers.
I'd rather stick to one distro at a time, although I do have VMs for Artix GNU/Linux, Slackware, Void GNU/Linux, and a few other "hipster" distros to mess around with. In case the Linux kernel gets pozzed (doubtful, but anything goes in "cancel culture"), I'm going to add an OpenBSD install.
Never going back to Ubuntu or any other distro based on it, and Devuan is the KO to Debian by removing Systemd altogether.
How are you attempting to update your system?
I would use
# apt update # apt upgrade # apt full-upgradeOr perhaps
# apt update # aptitude safe-upgrade # aptitude full-upgradeNote that full upgrades are sometimes needed in testing/unstable because obsolete packages have to be removed. Also note that full upgrades can break testing/unstable systems if a transition is underway.
Yes, I'm updating using the first method (except the third line, which I see will remove a couple of Python packages).
# apt full-upgrade
The following packages will be REMOVED:
jack libpython-dbg libpython-dev python python-all python-all-dbg python-all-dev python-cddb python-dbg python-dev python-eyed3 python-magic python-ogg python-pathlib python-pyvorbis python2-dbg python2-devI just apt update/upgraded my system, and these all upgraded without incident. Except 3 python2 packages - there has been some funny business with python2 for a while.
Not long after I posted this thread, I saw that the compiler packages mentioned up above become possible to upgrade. I upgraded without a single problem.
I've been using the "unstable" Ceres for a few weeks. It's going along just fine, perhaps better than Chimaera or even Beowulf. The only problem is I've been noticing more packages are kept back when I check for updates. I just put the repositories for Chimaera and Beowulf back on (temporarily) in order to recover some missing Python packages (due to still being at 2.7.17-2, despite Python2 and others being at 2.7.18-2). I also did that to make Youtube-dl functional again.
Now, I'm seeing a growing list of packages that can't be upgraded. In this situation, should I just ignore it and wait until newer versions are available from upstream?
The following packages have been kept back:
cpp-10 cpp-9 g++-10 g++-10-multilib g++-9 g++-9-multilib gcc-10 gcc-10-base gcc-10-base:i386 gcc-10-multilib gcc-9 gcc-9-base gcc-9-multilib gfortran-9 lib32asan5 lib32asan6 lib32atomic1 lib32gcc-10-dev lib32gcc-9-dev lib32gcc-s1 lib32gomp1 lib32itm1 lib32quadmath0 lib32stdc++-10-dev lib32stdc++-9-dev lib32stdc++6 lib32stdc++6-10-dbg lib32ubsan1 libasan5 libasan6 libatomic1 libatomic1:i386 libcc1-0 libgcc-10-dev libgcc-9-dev libgcc-s1 libgcc-s1:i386 libgfortran-9-dev libgfortran5 libgomp1 libgomp1:i386 libitm1 liblsan0 libpython-all-dbg libpython-all-dev libpython2-dbg libpython2-dev libpython2-stdlib libquadmath0 libstdc++-10-dev libstdc++-9-dev libstdc++6 libstdc++6:i386 libtsan0 libubsan1 libx32asan5 libx32asan6 libx32atomic1 libx32gcc-10-dev libx32gcc-9-dev libx32gcc-s1 libx32gomp1 libx32itm1 libx32quadmath0 libx32stdc++-10-dev libx32stdc++-9-dev libx32stdc++6 libx32stdc++6-10-dbg libx32ubsan1 python-all python-all-dbg python-all-dev python2 python2-dbg python2-dev python2-minimalI am happy to announce that iwd is now forked for Devuan! You can see the package information at pkginfo.devuan.org. I would like to thank Mark Hindley for guiding me on this.
And because we have to fork iwd to make it work for Devuan, it unfortunately means that both the upstream and Debian maintainer are not interested in supporting sysvinit. I hope they change their mind, not only because I don't want to maintain this fork forever, but also because this is a bad path for GNU/Linux.
Anyway, since this thread was supposed to be about my xfce4-alsa-plugin, I decided to package it for Debian. I'm currently finding a sponsor at mentors.debian.net. Once it gets accepted to the main archive, I will ask the xfce4 metapackage maintainers to consider not depending on xfce4-pulseaudio-plugin, but on xfce4-pulseaudio-plugin | xfce4-alsa-plugin, so that Xfce users have a choice between PA and Alsa on their panel. That's the main goal I had on mind when packaging xfce4-alsa-plugin.
That's good news, indeed. I also use that panel plugin, which I had to compile myself and copy the two files (both the function and the launcher) across my machines. I look forward to seeing it become a binary package, which is just not fair to those who like Xfce, but don't want to use PulseAudio. ALSA has proven itself time after time to be a simple, reliable sound server. Works just fine for people working with audio recordings.
Yeah, they do disappear when you reboot. Still haven't been able to figure out a proper workaround.
Looks good to me. ![]()
brocashelm wrote:Rather than we continue going back and forth over the proposed naming, why not go with a generic one for now as a placeholder? That's the least of our worries. Having a centralized section for that use case is definitely a necessity.
I think the Devuan staff know what's best, and a huge plus is listening to the community. Let's lead by example with this new section.
I dont see the need for any rush to create a section, unless you have urgent issues? As the old saying goes "proper preparation prevents piss poor performance" or the 6 p's!
I don't see the need to hold yourself back over something as trivial as a name. Besides, there are already a couple of examples thrown in. Freedom Hacks sounds good.
brocashelm wrote:I don't mean to hijack this thread, but I also use VeraCrypt and have a different problem at the moment.
As I like to tinker with security, I installed the LibPAM-TMPDIR package, only to find out that VeraCrypt can't "see" that I have mounted volumes, thus no ability to unmount them through the software. I could do it through the system, but it leads to a bit of a mess. How would I go about fixing this without removing the package? Do I need to set a specific mount path for VeraCrypt? If so, that would be appreciated.
Are they veracrypt volumes?
Maybe dont hijack this thread and create a new thread as your issue has nothing to do with the OP.
Yes, they are VeraCrypt volumes.
And, if a moderator wants to split these posts into a separate thread, go ahead.
Using Runit, I was also experiencing abrupt freezing for a while. I understood what I was getting myself into, but I didn't seem to find much of a solution. This was only affecting one of my machines, whereas the others were also on the Chimaera branch. Ever since I "moved" all my machines to Ceres, I've been running the system for three days straight without issue. I keep an eye out for faults, yet my machines couldn't be any more stable!
Don't overwhelm yourself with learning command lines. Just keep being patient and try different things. See what the terminal is spitting out and try to to apply changes. At the same time, launch GUIs via terminals to keep track of errors and other suggestions. Optionally, look into security hardening tools (e.g. Lynis) for tips on proper Chmod usage in directories and files, essential privacy steps, and so on.
It also helps to learn the ways of other package managers, as well as compiling from source. APT is great and I like it more than Pacman and Portage, but learning those and other distros' methods of managing packages can help brush up on your knowledge of GNU/Linux.
I don't mean to hijack this thread, but I also use VeraCrypt and have a different problem at the moment.
As I like to tinker with security, I installed the LibPAM-TMPDIR package, only to find out that VeraCrypt can't "see" that I have mounted volumes, thus no ability to unmount them through the software. I could do it through the system, but it leads to a bit of a mess. How would I go about fixing this without removing the package? Do I need to set a specific mount path for VeraCrypt? If so, that would be appreciated.
Refracta is just too damn good to pass up. I heard of Devuan back in January 2018 via Distrochooser (I wanted a Debian-based distro that respected me, and Devuan was ranked on top) and tried it from time to time, but could never get a feel for it. ASCII was just not that pleasant, due to metapackage inconsistencies.
Things finally took a sharp turn for the better with Beowulf, but I still felt that something was missing. That's when I decided to go with one off the list, and Refracta looked to be the most attractive derivative of them all. Right off the bat, it just worked for me. I liked that GUI text editors such as Geany were included, and rather than PulseAudio bullshit for sound, I got ALSA, which has NEVER failed on me, no matter what hardware problems were experienced.
I personally believe that Refracta is what the main Devuan should have been more like, since I just don't like Poettering shitware of any kind. Regardless, any of those derivatives will still take you straight to Devuan. It's a much looser distinction than, say, GNU/Linux Mint and Ubuntu (since they are both alike and unalike for different reasons).
Rather than we continue going back and forth over the proposed naming, why not go with a generic one for now as a placeholder? That's the least of our worries. Having a centralized section for that use case is definitely a necessity.
I think the Devuan staff know what's best, and a huge plus is listening to the community. Let's lead by example with this new section.
Runit is excellent and can already be used with Devuan since Beowulf.
Here's a quick guide:
This guide shows how to use runit-init as PID1 in Devuan, it is primarily aimed at Jesse from Distrowatch
First, instal the runit-init package:
# apt install runit-initAPT will ask for a specific confirmation for the operation because replacing the init system is far from trivial, type in the required authorisation to install the package.
Next, reboot into runit-init. Check it has worked with
cat /proc/1/commThe output should be runit.
That's it!
EDIT: if a display manager is not required then add the user to the input group to allow access to the keyboard &c:
# gpasswd -a $USER input
I vote in favor. That's the whole point of Devuan, and then some.