<Esc>:r /proc/version Linux version 6.13.1 (root@amiitoo) (gcc (GCC)
14.2.0, GNU ld (GNU Binutils) 2.43.1) #1 SMP PREEMPT_DYNAMIC Sun Feb 2 04:56:59 UTC 2025
That seemed abnormally quick.
Was there something wrong with the last kernel where they had to
release another so fast?
That seemed abnormally quick.
Not really. According to kernel.org;
mainline: 6.13 2025-01-19
stable: 6.13.1 2025-02-01
I haven't had a chance to check. It just so happened to present itself (6.13.1) when I was upgrading one of the four machines I am working on.
So far twon of them are both running 6.12.11 since 6.12.12 hadn't
presented itself until yesterday, which was after I upgraded them to 6.12.11. I still have one more machine to get up to date, and it will probably be a 6.12.12 kernel which is listed as 'stable'.
But then you had 6.12.11 on Jan 23 and 6.12.12 on Feb 1 in between?
What's the reasoning with all that?
I'm guessing 6.12.x is still receiving security patches or
something while 6.13.x is now currently being worked on?
I'm guessing 6.12.x is still receiving security patches or
something while 6.13.x is now currently being worked on?
That sounds about right except that there are previous releases still
being supported such as;
longterm: 5.4.290 2025-02-01
I note you are claiming gcc-14.2.1 which you might want to check as
far as suitable kv's and glibc versions are concerned. So far no
issues with gcc-14.2.0/glibc-2.41 that I've noticed but I am betting
that a gcc-14.3.0 release isn't too far off.
longterm: 5.4.290 2025-02-01
I can't possibly think of any _recent_ distros are still deploying
this kernel version
I also happen to have a couple RPi3's doing the exact same thing
(collecting dust). However, I don't remember what kernel version I
was on when I stopped using them.
I ended up getting much better hardware and going that route
instead.
I can relate.
Linux version 6.13.1-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20250128, GNU ld (GNU Binutils) 2.43.1) #1 SMP PREEMPT_DYNAMIC Sun, 02 Feb 2025 01:02:29 +0000
Linux version 6.13.1-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1
20250128, GNU ld (GNU Binutils) 2.43.1) #1 SMP PREEMPT_DYNAMIC Sun,
02 Feb 2025 01:02:29 +0000
<Esc>:r /proc/version Linux version 6.13.1 (root@amiitoo) (gcc (GCC) 14.2.0, GNU ld (GNU Binutils) 2.44) #1 SMP PREEMPT_DYNAMIC Wed Feb 5 05:26:06 UTC 2025
You have a newer gcc but I am one step ahead with binutils. According
to the main gnu site it was released 2025-02-02 which was just a
couple days ago.
All I can say for sure at this point in time is that at least 1:153/7001.53423 works as this reply is evidence of. :-)
The current plan is to update the fidonet node - Little Mikey's Brain
I used to pick ones that are easy to remember given it's output in
hex, such as FACE. Converting to binary for msg headers one is forced
to use little endian. Personally I think binary data should be
excluded, especially in headers.
Sounds like you have a bit of work ahead of you.
That's putting it mildly. I should be done with the node later this
evening and possibly starting the EuroPoint. If things go smoothly
all should be right by Sunday fidoally-speaking.
You get to have all that fun,
while I have to jump up on the roof and fix a few shingles that
flew off in the 50mph winds we had yesterday.
while I have to jump up on the roof and fix a few shingles that flew
off in the 50mph winds we had yesterday.
Ouch! I hate when that happens.
Since you first brought up the weather we dropped to below 0C and got
a couple dumps of snow. A neighbour just knocked on my door asking
to borrow a ladder to fix his roof which got damaged by huge lumps of icey-snow falling from trees. I think you jinxed us or perhaps it
was me claiming no snow this winter that triggered it. Either way it
really sucks.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 98:04:55 |
Calls: | 295 |
Files: | 5,636 |
Messages: | 226,221 |