r00ty

Pretty sure mine was 16399753. But, not logged in for probably 15 or more years, so could be wrong.

No idea whatsoever about the password :P

I think people's experience with PLE will always be subjective. In the old flat we were in, where I needed it. It would drop connection all the time, it was unusable.

But I've had them run totally fine in other places. Noisy power supplies that aren't even in your place can cause problems. Any kind of impulse noise (bad contacts on an old style thermostat for example) and all kinds of other things can and will interfere with it.

Wifi is always a compromise too. But, I guess if wiring direct is not an option, the OP needs to choose their compromise.

Aha, glad to hear it.

OK, one possibility I can think of. At some point, files may have been created where there is currently a mount point which is hiding folders that are still there, on the root partition.

You can remount just the root partition elsewhere by doing something like

mkdir /mnt/rootonly
mount -o bind / /mnt/rootonly

Then use du or similar to see if the numbers more closely resemble the values seen in df. I'm not sure if that graphical tool you used that views the filesystem can see those files hidden this way. So, it's probably worth checking just to rule it out.

Anyway, if you see bigger numbers in /mnt/rootonly, then check the mount points (like /mnt/rootonly/home and /mnt/rootonly/boot/efi). They should be empty, if not those are likely files/folders that are being hidden by the mounts.

When finished you can unmount the bound folder with

umount /mnt/rootonly

Just an idea that might be worth checking.

I think in 99% of use cases, upgrading isn't a problem. Most of the time new SQL versions are backward compatible. I've never personally had a problem upgrading a database for a product that expects an older version.

They do have compatibility modes too, but those only go back so far too.

But, I think companies with their production databases for perhaps older complex systems are likely very weary of upgrading their working database. This is most likely where this situation comes from. Imagine being the person responsible for IT, that upgraded the DB server and database to the latest version. Everything seemed to be working fine. Then accounts run their year-end process, it falls over and now there are months of data in the newer version that won't work properly. It'd be an absolute pain to get things working again.

Much safer to leave that SQL 2005 server doing what it does best. :P

I think most people that were gaming held onto their CRTs as long as possible. The main reason being, the first generation of LCD panels took the analogue RGB input, and had to present that onto the digital panel. They were generally ONLY 60hz, and you often had to reset their settings when you changed resolution. Even then, the picture was generally worse than a comparable, good quality CRT.

People upgraded mainly because of the reduced space usage and that they looked aesthetically better. Where I worked, we only had an LCD panel on the reception desk, for example. Everyone else kept using CRTs for some years.

CRTs on the other hand often had much better refresh rates available, especially at lower resolutions. This is why it was very common for competitive FPS players to use resolutions like 800x600 when their monitor supported up to 1280x960 or similar. The 800x600 resolution would often allow 120 or 150hz refresh.

When LCD screens with a fully digital interface became common, even though they were pretty much all 60hz locked, they started to offer higher resolutions and in general comparable or better picture quality in a smaller form factor. So people moved over to the LCD screens.

Fast-forward to today, and now we have LCD (LED/OLED/Whatever) screens that are capable of 120/144/240/360/Whatever refresh rates. And all the age-old discussions about our eyes/brain not being able to use more than x refresh rate have resurfaced.

It's all just a little bit of history repeating.

Are you sure it was CRT technology? Because bear in mind, colour CRTs had to focus the beam so accurately that it only hit the specific "pixel" for the colour being lit at that time. What there was, was blur from bad focus settings, age and phosphor persistence (which is still a thing in LCD to an extent).

What DID cause blur was the act of merging the image, the colour and the synchronisation into a composite signal. All the mainstream systems (PAL, SECAM and NTSC) would cause a blurring effect. Games on 80s/90s consoles generally used this to their advantage, and you can see the dithering effects clearly on emulators of systems from that period. Very specifically, the colour signal sharing spectrum with the luminance signal would lead to a softening of the image which would appear like blurring. Most consoles from the time only output either an RF signal for a TV or if you were lucky a composite output.

Good computer monitors (not TVs) of the time were extremely crisp when fed a suitable RGB signal.

It already exists. Although it's not AI, and mostly works best when using channel logos to work out the ad breaks.

Yeah, I was thinking more if there's either an evolutionary improvement or revolutionary (or some movement toward AGI). For me it's better if not, so I get to keep my job for a few more years. But, my general feeling is with the cash injection, there's some chance of a breakthrough.

I mean if LLM/Diffusion type AI is a dead-end and the extra investment happening now doesn't lead anywhere beyond that. Yes, likely the bubble will burst.

But, this kind of investment could create something else. We'll see. I'm 50/50 on the potential of it myself. I think it's more likely a lot of loud talking con artists will soak up all the investment and deliver nothing.

There are, and I think the only real difference has been the community support. The community was behind the original pi and the guides, images and support show that, and it continues to this day.

If this becomes "enshittified" then communities will grow around the alternatives, it's likely there will be an overall winner (or winners per class) and we'll move on. The device itself wasn't ever the whole story.

I'm fairly sure it must take extra work to make dynamic prefixes. I've heard some weird justifications about localised routing. But modern ISPs generally don't work that way at all. For example, my ISP has endpoints in multiple cities, and can fail over to another city if need be. All my static IPv4 and IPv6 instantly move with me in that event.