I hope they handle it more gently than they usually do!

Twitter is pro-religion? What kind? Satanism? Muslim? Hindu? Oh! Buddhist! Elon’s clearly a Buddhist.

Every time I see one of these posts about an OSS project finally moving off Twitter, I have this same baffled reaction: why the fuck were they still using it‽

Ah. I skip a lot of neutrek; most everything between DS9 and Lower Decks, although I am watching Strange New Worlds and find it about 50% enjoyable. I have a hard time with all of the retconning. :shrug:

A lot of this stuff goes over my head. Trauma from some of the later movies, and the dark turn everything took during DS9 put me off.

There are dozens of projects to share storage; what’s needed are systems that share compute. Crypto currency controversy aside, things like Etherium with smart contracts, or the more venerable - but centrally controlled - seti@home, are more what’s needed. I suppose having the ability to support some mechanism of micro payments isn’t unreasonable, but I think it it were something like “I’ll donate X% of my unused C/GPU cycles to any processing request signed by the public key from this project,” I’d feel more comfortable about it. Micro payments for selling unused cycles to arbitrary projects is just another capitalist market I’m not interested in participating in.

Caveat: I’d be comfortable selling spare compute to for-profit projects: companies, etc. But that’s a side-note. What I’d like to see is a general-purpose way to donate spare cycles to specific projects. Definitely supporting whitelists, but optionally supporting blacklists. I think PK would be the foundation, as it would allow a True Believer to donate cycles to any project in the GNU Foundation, or specific projects from self-hosters.

Such compute would probably be horrendously slow, and figuring out how to parcel out and distribute e.g. compiling a project in an arbitrary language sounds like quite a challenge. I can see cases where the CI speed isn’t especially critical, such as building assets for a release, but the technical challenges seem difficult.

Ah. Yeah, that makes sense.

Can anyone who’s in data center security explain why it’s a good thing to limit the number of people in the center at one time?

I’d think setting up a system where only one person is allowed to be in there, alone, would be far worse.

Is that really from ST? Or from a porn parody?

Oh, yeah; I’m fine with a GUI boot USB, and a GUI installer… but if possible, having a target use is nice. Having a “server” target often means they skip installing X/Wayland, window managers, DE, and a bunch of applications - which means a far shorter installation and fewer post-install clean-up hoops of removing crap that’s not going to get used.

I like the convenience of the GUI installers; I just like the option of saying “don’t install a desktop GUI.”

That sounds pretty neat.

I looked into it; it looks like they’ve got placeholders for server-oriented installs, but no ISOs yet; only for desktop and mobile at the moment. But it’s a cool project, and I’m keeping my eye on it - thanks!

This is why centralization is bad.

Maybe this will encourage more engagement in projects like i2p and ipfs. I’d be happy to donate some compute and bandwidth to these projects.

Maybe there isn’t a good solution, but throwing money at it doesn’t address the underlying issue that these important OSS projects are at the mercy of Big Hosting.

I just made up a new boogey-man!

Huh. I wonder who gave you a downvote for this. It looks like good advice, and TBH in all the years I’ve been using Linux, since I stopped building the kernels myself I haven’t messed with targeted builds or any of the newer power saving options.

Good advice, thanks

I think you have an X/Y problem.

Rootless podman requires no special firewall management. Like docker, you mearly expose you want in the container, and if you want those ports accessible outside the machine, the firewall has to allow access - just like any other program.

How is your podman configured? To use pasta, or slirp4netns? I often have trouble with pasta - I merely haven’t spent the time to figure out the details of using it - so I always just switch (back) to slirp4netns, which was the original network tool. Do this in /etc/containers/containers.conf, or dig into pasta and see if there’s something in there. The pasta package is actually called “passt.”

Did you set up subuid and subgid correctly?

Did you confirm you can access your services locally?

If you are using slirp4netns and have your account configured in subuid and subgid, then rootless podman should function as any other networking program, and you shouldn’t have any firewall issues.

As an aside, and just my humble opinion, I really hate firewalld. It makes firewall configurations complex and byzantine, and almost impossible to work with with other tools like nft. I’m sure it is great for some people, but anytime you add more complexity to a configuration, you add more opportunity for something to be incorrectly configured. I hate fighting with it, and have had times where I struggled to get it to open a port: I was in the wrong “zone”, or was in persistent mode rather than runtime mode, or whatever. It’s just unnecessary added complexity, and lately if the distro installs it I just uninstall it first thing and use nft.

If you followed the rootless podman wiki and everything else looks good, I’d look suspiciously at firewalld.

I just got a new, cheap, fanless micro computer that advertises itself as running Linux, and I spent today looking at Arch-based distros; Cachy made my short list, although I’ve never run it.

Is it suitable for running a headless, fanless mini-PC that’s raspy just going to be a snapclient host?

Is there a “Server” option in the installer? Once I get this set up, it’s going to be running entirely headless and without any peripherals (except the AUX out), and I’d like to strip out all of the unneeded software.

I’ve installed bare Arch before, and it’s a PITA I’d rather avoid; it’s easier to just install Garuda or Endeavor and then uninstall X and Wayland, and everything that depends on them. I’m wondering how Cachy fares in this situation.

Before anyone suggest I use a different, non-Arch distro for this: no. I understand pacman and yay, and I know where Arch puts files that every distro has a different opinion on locating. I’ll play with other distributions and switch when I find one I like more, but this is a device I just want to set up and forget about except for periodic upgrades.

Anyway, what are your opinions on CachyOS? I’ve been pretty happy with Endeavor for desktops, but I wouldn’t put it on a headless server.

I momentarily forgot the word “subconscious,” if you can believe it.

Upvote for flawless punctuation.

And their prey get run over all the time, too.

Inquiring minds want to know.

It seems absurd. On the one hand, we have Wayland folks saying X is dead, there’s no development, blah, blah. On the other hand, it reads like they’ve got a bunch of compute dedicated to CI and repo hosting. I can believe the bandwidth of literally every distro is configured to download source directly from FreeDesktop because of constant code merges. But if there’s no development going on, why not just ask distros to torrent the code? Heck, even if there were daily changes, they could still push out torrents.

Bandwidth aside, what’s all that CI compute doing with a stalled and dead project?

Maybe you drop it enough to really enjoy prison.

Your id is trying to tell you something.

Respect for Worf casually holding a saddle one-handed. Those things are heavy.