You are not logged in.
Pages: 1
It was especially bad on the older 3.x and 4.x kernels, mainly with Nvidia cards as I remember. It teaches you a lot about managing updates and maybe not updating if there isn't any real need. I've tried 6.x on Chimaera but it didn't work properly, my RTX 2080 Ti wouldn't work any more on any driver version. But it should be fine on 15. To be fair the second I put Chimaera on, I installed Kernel 5.x from Backports, same day. I tend to prefer to run a newish kernel, even on LTS distros. If I find some new feature I hate (when they renamed eth0 to some random interface name is a good example) I rebuild and disable it for the build so no need for passing silly parameters to the kernel on boot, it just isn't compiled in. Nouveau support will be one of the first thing I remove from the kernel on Slackware. That driver seriously irks me. I only use the proprietary driver (and have since my Riva TNT back in the day).
Anyway I don't mind LTS, i've run those types of distros before now. Normally you have to update the kernel, but 15 comes with 5.x so it should be fine given Chimaera is on 5.10.0.46 and works well for what I use and need, so i will probably grab the latest version of 5.10, patch it to 46 and use that.
Thanks.
My usual method is to subscribe to majordomo@slackware.com and that gives me the security patch info when they are released. I also rsync the patch directory daily to /var/cache/patch, so I always have the updates available locally. Currently their aren't so many on 15.0, given it's the stable branch and not the bleeding edge of -current. Also some I will compile from source, like OpenVPN which is still older than the current version (I prefer anything that is directly security related to be on the absolute latest stable version).
From the last time I did it, the biggest single annoyance was the kernel. Every time they find something serious you have to download and rebuild it. Most of the time it's not too bad, but occasionally you get runs of lots of new kernels (there was one on Chimaera a couple of months or so back with 2-3 kernel releases in a fortnight). Thankfully having a modern 16 thread CPU makes compiling a lot easier than the days of quad and dual cores or god forbid the super old days with a single core and no hyperthreads, where compiling the kernel took a long time.
You'll never get a desktop app out of Virgin. You get the web interface or the phone app. Personally i'd buy a phone, install the app on it, don't put a sim in it and store it powered down in a safe when not in use. I have a family member that does exactly that. Gets the phone, powers it up, connects to wifi, does what he needs, powers down and puts back in the safe.
The one problem with the web app is moving money. There is a £500 daily limit. On the phone app it's unlimited, which i think is crazy personally given how easily phones get stolen. Which brings me back to the phone in the safe. The other one if you can remember the passcodes and details (you probably can if you use the web portal) is to install the app on your phone when you need to do something and then immediately uninstall it afterwards. That's what i do with another family member when they want to move money into ISA's and send money to people. Don't allow google or apple to store any passwords for anything banking if you do use a phone.
Personally I have a banking app on my phone, but I also retain the web portal access. Funnily enough though I can use VM on my Firefox, but prefer Chromium for anything financial. I have limits set on everything in my account and to change them requires a lot of jumping through hoops, it isn't straightforward. Like chip and pin is set to £10 max, which limits damage if I lost the card.
Also Natwest does pay interest, but not on current accounts. if you throw the money into the digital saver account it gets somewhere around 4.5% per year but only on a balance up to £5000. Many banks have a similar system, so you could potentially have many accounts holding a limited amount earning interest. It's all about gaming the system.
The one thing you have to watch out for if you have lots of money earning interest is the personal savings account limits. If you make more than £1000 per year in interest and are not working, you have to fill out a self assessment and might get taxed. If you don't and you go over it, expect a letter from HMRC. They got really hot on this in the last couple of years. i know a couple of retired people who got stung for this last year. If you are working they generally adjust your tax code to pull the tax off upstream. ISA everything you can to avoid the tax man.
Modern Linux strives to be Windows. Systemd pushed that process and then all sorts of other things are now pushing it further that way. Eventually some day Linux will be Windows and everyone will be subjected to the same spyware as a Windows user and quite frankly you will all have yourselves to blame for it. You will bend over to your corporate and government masters and take it up the proverbial. ![]()
Sarcasm aside, for the record I didn't watch it. Can't stand all the AI slop on YT nowadays or in general life. I'm of the old guard who was here in the early days of Linux and only Slackware and BSD really adhere to the old philosophies nowadays. If you want old, stable platforms those are pretty much it and maybe some of the projects based on them. If you want Windows-esque, hold your hand while you sit on the toilet level Linux (and potentially down the line wipe for you afterwards), you install the modern stuff.
The UNIX philosophy is basically minimalist, modular system and software design. It isn't integrating everything into a single binary. That is the Windows philosophy. But maybe all these people that come to Linux, really (subconsciously) want Windows and that is what has shaped the current path.
I grabbed Slackware64-15.0 last night. I found a brand new ADATA 480gb SSD in my spare drives box (well found several actually so forward thinking has saved me from the AI chip pricing debacle), so I'm squared away for a new install, maybe tonight. I'll be honest and say I will probably just go to Slackware. It's the cycle of things. I've been on Debian/Devuan now since before Devuan was created, back on Debian Jessie, when the whole systemd saga started. But was on Slackware64 13.37 before that for 2-3 years. Now it's back to where it all started. Took me all of 31 years to realise what I started with is still probably the best distro I ever used. ![]()
Yes, I'm not totally against change, but I like an easy life where things don't if I can. I'd like to stick with Devuan ideally, but i'm not against going back to Slackware. My ideal would be Slackware with a decent package manager that handled the updates. But no one ever managed that although some tried. I've probably used all the major distros in my time doing this and originally it boiled down to three. CentOS, Debian and Slackware. CentOS is no longer anything like it was before systemd and the slow march into realms away from Unix fundamentals, Debian I left to come here and Slackware is still old and faithful, mainly due to Patrick's, Linus-esque method of handling the distro and resistance to add new things (although a decent package manager would be a boon). The apt ability to update and upgrade a system, is one of the main reasons I love Devuan, it removes so much hassle. Doing the same on Slackware was a major pain. CentOS also has a decent package manager in yum, but it's need for systemd makes it unsuitable to me (also there was some controversy last year about upstream RHEL, not that I totally read about it).
What will I do. Probably suck it up and dist-upgrade to Daedalus. If it all falls apart, back to Slackware. Looking at it in the last few days, it seems more package managers have appeared and maybe something now exists that can do things more in an apt type of style.
Going back to Slackware would be full circle for me. I started my Linux journey on Zipslack and Bigslack a few months after they were released (and yes I still vaguely remember how long it took to download them on a 28.8k modem, but downloading a full set of Slackware was a week long endeavour). Back when you could still run Linux on top of DOS. The alien-ness of being presented with a terminal and nothing else. I showed it to a friend and he asked me what the point was and I replied "freedom". Zipslack wasn't very functional, but brilliant for repairing a main install that you broke while learning. Bigslack for the uninitiated was Zipslack with Gnome. More functionality and the abilities of a GUI.
Anyway this level of nostalgia means I need to grab an SSD out of the spares box and throw the latest Slackware on it and see what is looks like. Maybe that is the true path. But a lot depends on the status of the current package managers of which there seems to be a few nowadays.
Building from source on a package-based distro (like Devuan) that extensively is asking for trouble. You may want to switch to Gentoo (or Funtoo if that's up & running again) or even Linux from Scratch, Arch or Slackware.
Thing is, what can i do. Stuff like OpenVPN is always out of date on Devuan. Like the current version is 2.7.7 and the latest version available on Chimaera was substantially less than that (maybe in the 2.4 versions), plus there have been some serious security holes patched in some of those releases. Luanti was another one I had to build myself because the Debian version was very out of date (couldn't get mineclonia to run). Other times you go to install something and it needs some specific program or library which isn't available on Devuan/Debian/Ubuntu, so you have to build it yourself to get everything to work. Had that when trying to install a network driver for an obsucure wifi adapter and it wanted a certain library that did not exist on debian, which i had to build myself.
Years back I opened a thread about this when using Debian and the response was essentially tough sht. We can't help you. So I learnt to help myself. Linux is the quintessential hackers operating system after all and it is geared for dealing with exactly this problem.
It's actually not that hard to do with Devuan. I mark any package I intend to build myself, that has an available package with hold, in apt. Then build the package and install to /usr/local like i've always done.
Other than that, you'll probably run into the same pleasure as everyone else that the notion of "backward compatibility" has dissolved and been replaced with "upgrade everything now, and then again next week".
This one thing irks me the most. I don't mind updating stuff to fix security issues, but beyond that, I don't want new functionality. I just want it to work today, like it did yesterday and ten years ago. If it does that i will be forever happy. I think the nearest distro to that is probably LFS. I always found Gentoo to be a bit too clunky. Arch was nice, but too much systemd nowadays. Slackware was very good, but you can bollocks up the system rather easily with updates and a lot of the time never be able to get it back to a working order.
One moan I have about Xorg is I have had messages in the logs about how my mouse and keyboard are slow (Logitech K120 wired keyboard and Razer Deathadder). Now these never used to happen before. Also it tells me my computer is too slow. It's a Ryzen 7 3800x with 64GB Ram and an RTX 2080 Ti. It is about as far from being slow as it can possibly be. I read a year back it's an issue in DirectInput, but I haven't worked out how to fix it so far. When i tried Daedalus the same errors presented, so not fixed yet.
As to the keyboard and mouse not working, the fix is to add your user to the Plugdev group. Then they work. I learnt that one while trying to make Daedalus work in a Qemu VM.
So I am at the point where I need to either upgrade or find something else. But I have tried the current two releases and had no end of problems with them, from the mouse and keyboard not working, to lots of libseat problems (why do i even need this library?). What i want is a distro that doesn't change what works. Doesn't try to reinvent the wheel over and over. If it works today, why try and intentionally break it for tomorrow?
So i run Fluxbox, which i start from startx. I use the proprietary Nvidia driver. I use XFE for my file manager. I compile quite a few things from source and maintain them myself (and am quiet proficient in building things from source). It works and I've been doing it this way for maybe the last 15 years (I used Gnome for the 10 years before that). I just want something that will still allow me to do it this way in 20 years time. I have no use for new fangled things that fix problems that don't exist like this Wayland system. X has been working fine for the last 25 years that i've been using it.
Sorry, needed to moan as I realised today Chimaera no longer gets updates, which means I have to complicate my life with upgrades.
PEBKAC!!!
So i fixed it, after reading this thread.
https://github.com/ValveSoftware/steam- … sues/11921
What could possibly cause the two steam components from not being able to communicate with each other.
So I was trying to set the system so eth0 wasn't enabled at boot until a script in rc.local brought it up at the end (after doing some stuff to the network connection and I forgot I did it). So I spent an hour trying to make this work yesterday. I finally used the networking script in init.d, without even considering that if I told it not to setup networking that it would kill lo as well. So no loopback enabled. eth0 came up on the script like intended, but I never enabled localhost. So it appears steam and steamwebhelper communicate together over localhost and since there was no localhost, it crapped out.
So I typed "ifup lo" and fired up steam and it works, no errors.
You live to learn. ![]()
So I had a look in dmesg and found a segfault in steam. ![]()
So if I read it right there is an issue with libX11. Maybe I should post this to the Steam Github and ask what they recommend.
So i am running oldoldstable (because I hate doing full installs, dist-upgrades always seem to go wrong and then I end up raging and installing something else). So I have had this Chimaera system for the last two years, it works, no hassle. So today some update came through which i thought said dpkg, but what i think it said was dbus. Anyway it broke Steam. I went from playing Elden ring 12 hours ago to a box popping up telling me I have "Error 0x3000" and it looks like Websocket Errors are now the norm. I can click on an option in the box that allows me to ignore and continue, but steam client repeatedly crashes.
src/steamUI/webuitransportcontroller.cpp (175) : Failed to connect to websocket
src/steamUI/webuitransportcontroller.cpp (175) : Failed to connect to websocketSo do I go back to having a tower for gaming and a tower for everything else? That way i could run systemd cancer on a Debian box and literally use it for gaming and nothing else. Not against doing that as it solves problems. Would make my main system a lot cooler, not having the 2080 Ti in it, when all i need is a 1050 Ti or GTX 970 for some basic games. But it's hassle. Or try installing Daedalus again, last time nothing worked.
Does steam work fine in daedalus/excalibur without issue?
I notice they go through phases of hardcore blocking VPN and uBlock users. For instance using a UK VPN or some European VPN gets you a captcha, but swapping to more obscure VPN's can bypass it. Also trying to watch certain videos gives you a demand to log in (CIA video from (possibly) VICE a few weeks back is one I've noticed a late).
My suggestion is VPN and use uBlock with all of the blocklists enabled, CanvasBlocker enabled and self destructing cookies. For me it works maybe 99% of the time, but some videos you can forget about it.
May I ask why you bother with OpenVPN when we have WireGuard?
My ISP completely blocks Wireguard. No dns resolution when using it, can't ping anything and when I asked one of their tech support (a friend from Uni), was told the unofficial policy was to block all wireguard connections via some adaptive AI traffic analysis box, but they won't publicly admit to doing so. He said use OpenVPN on the https port because they don't block OpenVPN since it runs on ports that are used by legitimate services and a lot of businesses use it.
----------------------------------
As to using latest versions, this is one of a handful of programs that I actually compile from source. I'm running 2.7.3 which is the latest. 2.7.1 is old now and 2.7.2 introduced two bug fixes, one that can potentially leak packets on handshake and one that affects servers. Debian packages are rarely fully up to date with the latest releases and definitely not on the day of the new release dropping.
I have two machines that run Devuan. One runs stable, the other oldstable.
The oldstable machine was running the current openvpn for oldstable 2.4.7 (off the top of my head). So the VPN company I use decided to do a security overhaul and presumably upgraded all there infrastructure to a newer version. So at some point, that machine stopped connecting because the version was too old. I tried exploring backports, and also explored pulling in OpenVPN from stable, to no avail. I found I could get it to connect by commenting out data-ciphers in the ovpn file, but that's not an ideal solution.
My solution was to build the newest from source. I grabbed all the dependencies from the Devuan repos. I will take over maintaining OpenVPN myself as I would prefer it was up to date (latest version of OpenVPN, ie, 2.6.4 currently).
So my question.
Are there any security implications, besides the obvious need to rebuild when the dependencies get updated?
I do come from a Slackware background and the need to monitor lists and manually upgrade things is not a big problem for me. I did it for years when i ran Slackware.
Used to use it years back, but a lot of it's ad blocking features are better achieved at the browser level, via say ublock origin. You can also do a system wide adblock using the hosts files found at https://winhelp2002.mvps.org/hosts.htm which I also tend to deploy as a more blanket effort against the ad companies.
Nowadays I find Ublock with all blocklists enabled gets rid of 95% of all ads, but some keep sneaking through (duckduckgo, facebook). In the grand scheme of things i don't use the products from FB much so it doesn't bother me.
When i did use Privoxy, I only used defaults. I think that was probably about 15-20 years back.
Pages: 1