I've been a Linode customer and I believe you have to use the kernels that they have modified for Linode. There may be a process to create a system image with a compatible kernel but then you get into issues when it's time to upgrade. Linode has the greater resources anyway so battling against system D seems like a waste of time. I've accepted that systemd is the way linux works now, just part of its resource profile.
On Thu, May 30, 2024 at 4:00 PM Steve Litt <sl...@troubleshooters.com> wrote: > Kent Borg said on Thu, 30 May 2024 09:31:15 -0700 > > >And why does > >systemd think it needs to be a whole damn OS in and of itself? It is a > >pig. And it is complex making, it a security risk. (Yes, I blame > >systemd for the xz security breach that nearly backdoored sshd all > >over the internet. No, systemd should *not* be patching other code, > >certainly not sshd. Grrr.) > > LOL, better put on your flame proof suit, because I have a feeling > you're going to need it after the preceding paragraph. :-) > > Can't you put any OS or distro you want on your Linode thing? Use Void > Linux, runit instead of systemd, less resource hogging training wheels, > especially when your user interface is either CLI or LXDE, LXQt or > Openbox. > > Here's how I view systemd: > > http://troubleshooters.com/linux/systemd/lol_systemd.htm > > I wear my flame proof suit regularly. :-) > > > SteveT > > Steve Litt > > Autumn 2023 featured book: Rapid Learning for the 21st Century > http://www.troubleshooters.com/rl21 > _______________________________________________ > Discuss mailing list > Discuss@driftwood.blu.org > https://driftwood.blu.org/mailman/listinfo/discuss > _______________________________________________ Discuss mailing list Discuss@driftwood.blu.org https://driftwood.blu.org/mailman/listinfo/discuss
