

They were asked multiple times to show where the 700MB where coming from, and they just didn’t, that’s a great way to get their issues fixed :D


They were asked multiple times to show where the 700MB where coming from, and they just didn’t, that’s a great way to get their issues fixed :D


You don’t have classified documents, but you probably use bank in your browser running as your user. Maybe you use local mail program to send emails, also running as your user. A simple malware could add emails to be send asking your family to send you some money through online service.
And that’s easily done because the only isolation layer is user and group.


Are you saying that AI slop is bad in those (counts) 4 removed lines of code?
Downsizing. If you don’t need to run or keep stuff, then you don’t need so many servers and storage. You may run stuff on cheap mini-pcs.
Sleep: In my experience sleep sucks, I’ve spent long hours planning around sleep in homelab, like: when do I restart, do updates, when do I upload backups. I have Pi and at some point I realised some actions on Pi need my sleeping NAS… so I dropped all the sleep and now it works 24/7.
Is it about Krita being on steam not for free?
If I’d use krita on regular basis I’d be happy to support the devs. Also, the license is the same as always - it’s open source.
I’m not sure you’ll get nice performance in local network with small appliances (consumer network hardware, mini PCs and rpi 4). I’ve never got sub-ms network disk access on 1Gbps switch and router. In the end I’ve done the opposite - I’ve added one k8s host with a lot of storage, and any storage services are deployed there. All the other k8s services rely on local SSDs.


Open a console with top/htop and check if it will be visible when the system halts.
From my experience it looks like out of memory situation and some process starts swapping like crazy, or a faulty hdd that tries to read some part of the disk over and over again without success.


There probably is a clever way that you could do it, but clever ways are easy to overstep, misconfigure and can be unreliable long-term.


His arguments are „we don’t know how brains work, we don’t know how conscience works, but we also don’t know how quantum mechanics could enable conscience, so it’s definitely the thing”.
It’s a trope that comes up every now and then: if we don’t know, then it’s definitely quantum mechanics.


Congratulations, now your „password” (the 512-byte random key file) is stored as plaintext on your machine :)
With rate-limiting, non-trivial passwords are not viable to be brute-forced, so making them larger just doesn’t give you much.


I’m running ZFS mirror on Ubuntu on a USFF machine with 2 external USB 2.5’’ drives. I do weekly scrubs, never lost any data even during power loss. Some of the 2.5’’ USB drivers are crap, I had to replace drive 2 times over last 5 years - while one of the drives is with me since the beginning.
I would say that a lot of people over-secure their local home file storage. If you use filesystem (or software) that does checksumming, your home data will be safe. Yeah, in case of power loss you may lose like 2s of last writes on ext4, and that won’t matter much for majority of people because it’s not like it’s your company’s only copy of internal data.


I’ve got Ubuntu + ZFS, and I’m pretty happy about it. No OMV, no Cockpit, everything is set up through a few ansible roles.


It’s a bazzite issue. Many people share that the drivers are pretty reliable on other distros.
From experience, they got pretty good over last 2-3 years.


AGPL means they are licensing it to you, they are not bound by the license because they are the copyright owners.


No, it’s not hard. By default open source drivers will run, but you can install the nvidia ones through driver manager and everything should just work.


No, it should work out of the box through the open source driver. But, for most people the Nvidia driver (closed) works without issues, you need to install it through driver manager app.


What folder did you run it in?


As @Strit wrote, use sudo, as docker keeps its container, image and volume files under /var/lib/docker, and that folder is not readable without sudo (or root).


You know that you can change license of software that you own copyright to? You can take GPL code and change it to something else, but you can’t un-GPL existing released code. It’s the same thing with MIT.
The only people bound by the license are people who use it because it is licensed to them.
The difference is that organisation may develop MIT software without publishing their code.
And inaccurate.