It’s pointless and stupid is what it is.

It’s the way that word has been used for over 20 years.

I’ve been wrestling with this issue myself recently.

There can be both performance and other issues with a db whose data files are on nfs. That said I’ve done this for years without any real problem. No db corruption so far - but it’s a possibility and I’ve probably been lucky. I have good backups just in case.

Like you I also don’t want to maintain a “pet” database on my file server. I want to spin up databases in kubernetes pods and not use local pod storage.

I’ve been investigating using iSCSI instead. It’s “block level” rather than “file level” and performs better with a database. Also none of the locking issues mentioned. It’s a recommended way to do remote storage for a db.

The downside is that it’s less resilient to the file server becoming unavailable.

Might be worth investigating for you as well - I’ll be performing some poc tests to figure out how much of a pain it may be (I don’t want to need to fsck a bunch of targets after a file server reboot).

My biggest customizations are all of the software I install and use to do things with the computer.

Wait… So if Linux doesn’t have the api (sorry, the “signal” 🙄) how will sites that require it respond? What does it mean to be “exempt” - every user is considered to be an adult?

An alternative to complete cloning (which gets out of date fast) would be to manage systems with ansible.(or puppet, or chef).

You can script configurations, package installs, users, etc. And it also allows for hardware/architecture specifics when needed (e.g. drivers for the different platforms).

You would then just install a base os and run your playbook. No need to store gigs of data and easier to update the base os to newer versions. You could even mix

You can also push out changes without needing to snapshot a new image and re-install it everywhere.

does it still work for software development?

… Why wouldn’t it? Like you could do other things but not write code?

Both extremes are absolutely maddening here. I’m getting as sick of the anti-AI crowd as I am the vibe-code-tech-bros. At this point you could just put them all in a sack and start hitting them with sticks and wouldn’t care who got the worst of it.

There’s a definite middle-ground here. Linus is one of the ultimate pragmatists and it shows here. It was helpful - so he used it. It helped you so you used it. I’ve found it to be incredibly helpful so I use it.

Not all usages are equal just as all hand-written code is not equal. There are good ways to use these tools and bad ways. But the tools themselves are still just tools.

It’s a bit more interesting than that…

Linux, unlike Windows, will let you delete a file that is actively in use. It removes the reference on the file system but the contents of the file won’t be deleted until all file pointers to it close. In fact it will still be seen as taking up disk space until it’s garbage collected (deleting a large file that’s in use can be frustrating).

So the file is actually still available to that running process. If you replace it with a new executable and run that then you get the new version.

No “poors” are running a 486. You would take the best part of and hour to boot a modern distro on a 66MHz (that’s 0.066GHz for you kids) 486. That’s if it would boot at all - which it likely wouldn’t.

No - nobody is still using one that would be running a modern distro. Anyone relying on hardware this old is already managing their own ecosystem of software.

We’re talking about computers that have clock speeds in the megahertz range FFS. They’re slower than an ESP32 and take a lot more power.

Nothing of value was lost.

Omg. You people are ridiculous. 🤣

I’m sure you’ll be devastated to learn that Linux stopped supporting the i386 in 2012.

Oh no!

Anyway…

Is this useful? They’re started but doing absolutely nothing. Who cares? You need to plan for max usage not idle.

My forgejo instance running right now is using 1070MiB. That’s way off your 173MB.

People who don’t run nixos.

You know what’s funny? Codeberg has said nothing about being concerned about liability.

Their terms service change simply mentions that they require certain licenses and that they have concern over the licensing of LLM meeting that standard.

Event their follow up communication says absolutely nothing of liability.

“It’s not…”

“There are probably law firms…”

This is wild unfounded speculation.

P2P torrent users are nothing like a code hosting platform. 🤣

As has been said - their liability for llm code is no different from hosting any other code. They already have the same risk. And that is typically that they must respond to take-down notices which they are already doing.

They are already dealing with all of the problems they would be dealing with with llm code.

It’s just code puritanism wrapped in pseudo legal justification. Own it.