Re: p.s.: Linux build speed

On Sat, 04 May 2024 23:52:46 +0000, 🌈💐🌻🌺🌹🌻💐🌷🌺🌈Jen🌈💐🌻🌺🌹🌻💐
🌷🌺🌈 Dershmender
💐🌻🌺🌹🌻💐🌷🌺🐶笛🌈💐🌻🌺🌹🌻💐🌷🌺🌈 <root@127.0.0.1> wrote in
<=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?=3DF0=3D9F=3D8C=3DBA?
=3DKCLHYs2.jAkJQ8$@45.203.143.5=3D?U=3D?UTF-8?Q?T?=3DF-8?Q?
=3DF0=3D9F=3D8C=3DBA?=3D>:

On Sat, 4 May 2024 22:49:22 -0000 (UTC), LO AND BEHOLD; vallor
<vallor@cultnix.org> determined that the following was of great
importance to vallor <vallor@cultnix.org> and subsequently decided to
freely share it with us in <v16e1i$1e3ds$3@dont-email.me>:
 
 
Are you trying to be a usenet newsgroup gatekeeping Edgelord again?

No.  Would be wonderful if you'd talk more about Linux, and
less about me.  Up to you, of course.

I've been using Linux since 1996 and before that it was
VAX/Ultrix/SparcOS/SunOs.  Not much DOS.  Just Apple ][e/][GS.  I
whitehat hacked some Novell in high school.

Our high school computer lab had Apple ][+'s connected
to a Corvus hard drive, a whopping 20MB of storage.  The
OS had a fundamental insecurity that was a bit of a
bother:  one could type "CATALOG V###" to change
to someone else's volume.  I patched the Corvus DOS 3.3
RWTS routine to reset the computer if people tried that
trick.  This turned into a bit of an "arms race", where
I think those involved learned more about computing than
the Pascal programs we were writing for AP Computer Science.

This has nothing to do with Linux, of course.  Are you satisfied?

One thing I can tell you about straying away from distro-supplied
kernels is that you're eventually going to break something

I didn't realize you were a soothsayer.

I'm not doing anything I haven't done for many years previous
to running Mint.  (There was a bit of a hiatus when I started
running Mint, but now the "bug" has bit me again.)

The only difference between then and now is that I'm posting
more about building kernels and running them.  I've been scanning
the patches and reading the release notes, which more often than not I
used to forgo.  (Linus has a policy of not changing syscalls without
very good reason because he doesn't like to break userspace.)

and possibly
brick your system pretty well when some low level driver compiles but
doesn't catch all of its proper dependencies and linking library
versions and nobody has caught it because 97% of the user base went
through the documented distro upgrade paths and testing phases whereas
you like to "live dangerously".

(That was a long sentence, and I'm not sure I understand it...)

Low-level drivers aren't linked against userspace libraries.  Probably
the biggest issue would be the version of gcc I'm using (11) -- but
if a kernel doesn't boot, I can use grub to boot an earlier kernel.
(I'd like to build with "-march=native" at some point, but that's
slightly outside of my comfort zone right now.)

 
Hope you have good and recent backups.

Yes, I have Timeshift keeping backups on a separate drive, and that
gets backed up to the NAS.  Protip: Timeshift doesn't back up one's
home directory, so I have a cron job that rsyncs /home to
the NAS.

I will note that the biggest issue I've had with Linux itself
was with btrfs, which I once used for my / partition.  It
got itself into a state where it couldn't be repaired.  Someday
I may try it again -- say in five years?  (Beats me.)

--
-v