For what it is worth, my daily driver is still 32-bit, Toshiba laptop - I hope it outlives me!

I would understand if Pat decided it was time to drop 32-bit, and would likely stay with 14.2 for as long as I could could keep it going in a useful and safe-enough way.

3 members found this post helpful.

There's practically no extra burden. When I'm done on 64-bit, I boot 32-bit and run a simple script that uses buildlist-from-changelog.sh and make_world.sh (both in the source directory) to catch up to 64-bit. Occasionally this shakes out some errors, so it's a worthwhile test if nothing else.

15 members found this post helpful.

As an aside, 5nm is looking to be the last process shrink (for a very long time, or perhaps ever). Moore's Law is coming to a close.

We are unlikely to see commodity 128-bit hardware, outside of SIMD or similar extensions -- the R5900 had a 128x128->256 multiply and a few other 128-bit operators, using conjoined registers, but that's different from a fully 128-bit architecture.

For half a century, Moore's Law improvements have been a feature of the industry, something we could make plans around. Our planning will have to change. Architectures won't stop evolving, but the rate of improvement will mostly flatten out. We will have to accomplish what we can in our lives with hardware not much more powerful than what we already have.

5 members found this post helpful.

Enorbet I would lay down an die or is that dye or dying hehehe with out you. winks be lost. shitt$ing rainbows with FFplay and 14.2. 3.4.5 SDL2 only LOL.
But if Pat got as High as I am he would. look at the tool I been been building with for a long time. Ramble ramble.

Pat Put the BONG Down and lets get a system that works ok 14.2 is broken. more than the kernel. great tool for building pre-libs we use to build programs with . But hey want to just drink wine piss bob off and replace the air bags on my truck love ya.
The 14.2 $arch for sbopkg is a broken thing for ALIEN BOB.
remember ft=hater
old marines never die we just let our dust protect you Bob

bro the blue paradise we truck local to Aurora CO is good stuff. cost and pay back. 14.2 broke fix it your high lost your high. I try to be that also.

For some damned reason, it feels like I've dropped into a net version of Finnegans Wake.

1 members found this post helpful.

I'll try to a bit subtle and polite but ummm Drakeo... I think ur cider done fermented and is well on the way to 190 proof.

2 members found this post helpful.

Wow. It's a shame Alan Turing isn't around.

Pat's a big boy. he will be fine. I got big shoulders. his work. I grab it and make it work for me. 14.2 is broken because
it is past date. only thing I use it for is to build programs that I built libraries from 14.1. Usability for ongoing media
pretty much broke. it is a time and $date thing. current is ok. current kde5 ok
got to love it
Richard we be lost with out you,

holding out on that script dude mmmmmmmmmmmmmmmmm help */*/*/*/
glad it not that much work

Man, did you become a BZ warrior?

(A comment that dates me like those of you who don't understand it wouldn't believe. I've added a link since the meaning of the phrase has drifted somewhat since I learned it.)

3 members found this post helpful.

14.2 works fine provided you don't need newer hardware support. And with minimal adjustment, it can be easily changed to add that hardware support for most cases.

Did you not read what he said? He said they're in the source/ directory. So, go to your favorite mirror and check out -current's source directory. In there, you'll find buildlist-from-changelog.sh and make_world.sh

4 members found this post helpful.

Drakeo, You've been asked to refrain from this kind of behavior in the past. If you'd like to continue participating at LQ, please keep this in mind. If you have any questions, feel free to contact me directly.

--jeremy

I have no clue what I have said sorry have no clue pm me.