Make sure your motherboard can support resizable bar. Intels arc cards require it.

Especially for older hardware that may be hidden in a firmware or uefi/bios upgrade.

Proxmox gives you a nice (and limited!) front end to manage containers and virtualization, but it also lets you do other cool stuff like resource pooling, credential management and too much to really get into.

Really powerful enterprise and whole organization level management in that package.

It’s not the only game in town, but it’s free and well documented and I recommended bare metal Debian as a stepping stone as opposed to alternative because proxmox runs on top of Debian so knowing that system is very nice.

The overhead is real. On the other hand, all your little vms and containers are rarely doing something all at the same time so it doesn’t matter.

The downsides of not going straight to proxmox are all pretty much permutations of missing out on features or having to deal with a migration later on down the line when you do switch to it.

Those features are almost universally stuff you might decide to not use or to use in a particular way, so it’s easy to say “pump your brakes and get your feet underneath yourself first” before handing you a tool that can be configured (with the help of Reddit, stackexchange and llms) in infinite wrong ways.

Kind of like suggesting someone learn how to make a simple miter joint before handing them the universally loved and used cordless oscillating multi tool. The tool is really powerful, but the skills and foresight doing even just one miter joint will give you let you make better choices about how to use the oscillating multitool when you have it.

Migration from bare metal to literally anything else is incredibly well documented and not a big deal.

Often times for some of the stuff you said you’d be running there are guides for migrating that particular package from metal to containers, vms, or to proxmox itself.

I want to make it clear that everything you learn from bare metal Debian would transfer over and compliment learning skills directly with the proxmox package because proxmox runs on top of Debian and Debian would likely be the os your vms or containers are made from.

You don’t need to throw yourself in the deep end to learn how to swim.

E: there is the extremely rare possibility that you will have some crash or security problem due to lack of containers/vms. I say extremely rare and I mean extremely rare. My personal server which was bare metal for twenty years just recently had its first one and it was actually related to a problem with containerization as opposed to lack of it. Your mileage may vary but for home users who don’t have public IPs and services getting pounded on 24/7 it wasn’t even something I thought about.

I’m a big fan of gpl everything, but when sudo was getting installed in everything the argument that “this great security technology needs to be permissively licensed so there will be no reason for companies to not make its use standard practice” held a lot of weight!

Another stupendous reason to gpl uutils so that the decades of experence of hundreds of system programmers can be leveraged in the rewrite.

Eventually proxmox will be the right choice for you. Right now it’s not because you’re not skilled or knowledgeable enough to be able to navigate it.

That is not a dig or a slight, it’s a very powerful and complex package built on top of an already powerful and complex package.

Just do containerless normal person Debian then when everything’s running how you’d like and you’re ready you can migrate to proxmox.

The big benefit of doing that instead of jumping into proxmox with both feet immediately is that you’ll be learning more and be able to solve your own problems as you get to the point of using proxmox.

op, if you can’t see any spyware it’s probably fine.

If you say that you gotta strap it down first for safety.

Slap the top of the pc and exclaim “no spyware in this thing”.

My “I don’t need to save space, I want it for a different purpose” tee shirt is raising a lot of questions answered by my “I don’t need to save space, I want it for a different purpose” tee shirt.

Rocmuh balls

Ahh, let me be clear: systemd is bad. Age verification is maybe bad.

The age verification added to systemd is a field in the userdb json that the administrator can set. It’s intended to comply with California law that requires the device attest when queried.

If that isn’t clear enough: it’s a plaintext field in a text document set by the administrator.

If that still isn’t clear enough: the California law lets you lie and the systemd implementation is designed to accommodate that allowance.

Op should use devuan to not have systemd though, that shit sucks.

Toyota, Nissan and Mitsubishi never made a 7.3 (although some of those Mitsubishi diesels are nice).

We need to bring back calling people slurs on the internet.

Just literally finding any reason to say no.

E: I want to be a little more clear, rather than policing language or tone, I responded to help that person understand. The mods did what they do and I believe rightly removed the offending posts.

I do believe the conditions around rust at the present moment create a perverse incentive. Because rust is a common language for junior developers and commonly has mit licenses and is very well suited to llm analysis from a running heap or code perspective it ends up being very useful and attractive to companies who want to get rid of senior devs, use more ai and not have to contribute their work back to the public.

That’s a perverse incentive.

Wow, where are those requirements published? I’m sure more people would follow the rules of the project if it were made clear that input is contingent upon some existing level of community involvement…

Of course, I have never seen such rules put in place except to exclude the most base mlm scam spammers on mailing lists, but that’s neither here nor there.

Shouldn’t my obvious willingness to engage with people about this topic serve as some sort of indicator that I’m serious and not “drive by”?

Shouldn’t the fact that I’m not being rude or crass like the other poster you brought up (to achieve rhetorical ends I’m not exactly clear on!) be an indicator that my input should be taken seriously?

So open source is only for people who already in the club then? Who gets to have a say? What are the restrictions on that say?

MIT defenders are laveyian satanists until someone has an opinion they disagree with lol.

I’m genuinely astounded that a recurring argument for simply dismissing suggestions to change the license to the one the original project had is “that’s my purse, I don’t know you!”

I could understand where you’re coming from if the people were, to a man, rude and demanding. Having read lots of threads about rust/mit rewrites of c/gpl stuff and participated in several, they’re pretty often just like me: politely presenting a perfectly reasonable argument even when met with very defensive pushback.

If you use Debian, even the simple “package popularity contest” is a default “no” in the installer.

That said, your personal conception of privacy is gonna be different than lots of other people’s.

Worth noting that a company used extremely small models and found something like 80+% of what mythos is claimed to have found.

The claimed circumstances are different, “mythos, go find exploits in open source codebases” vs “model, find a vulnerability in FreeBSD”, but there’s a subtle distinction.

Yes.

Open source is more than code, it’s software for everyone including non programmers.