For starters, consider another distro if you want to make things easy on yourself. Alpine is probably a poor choice unless you have a reason to use it. I guess you could use it as a desktop if you really want to, but it’s more geared for containers and embedded devices. It uses musl instead of glibc so you will have problems running software that isn’t packaged for Alpine. The issue with Puppy is you will have a hard time getting help when you need it because it’s kind of a niche distro.
For your first time, you’re better off using something more mainstream. You are going to run into some issues and it’s a lot easier finding solutions for popular distros. Debian would be a fine choice because it’s widely used and runs great on older hardware. Beyond that, you could look at Ubuntu, Fedora, PopOS and Mint.
I don’t get the issue with “maintaining Xorg”. Like, I get that it has a “cost”, I just don’t understand why that cost would be an issue since it’s basically fixed, marginal cost (and has been since like 2015): the software is already mature, so it’s unlikely to see relevant changes, or even minor changes (if that’s what we want to mean with “dead”). That means, it can be affixed to a specific toolkit and environment to build (if this isn’t being done already - which any mature project like RedHat should be!) basically guaranteeing it’ll build forever. You can just set a virtual button or a yearly crontab to do it. Fixed, marginal cost.
Contrasted to that, what Wayland is doing is kinda a representation of the worst ways of capitalism: centralize the profits, socialize the costs and the externalities (redesign, recode, rebuild), and blame society (the Linux communities) for it, all for a variable cost that is unbounded in time and space because you never know what’s gonna cost a small project like a text editor to reimplement the entire desktop stack “just” for Wayland.
I think he explains it pretty well, he even gives some examples and mentions there are many others. For a company to support such a large component for its commercial customers has a lot of work and verification we wouldn't consider as end users. His comment also explains why you can't just maintain a status quo with it and make an automatic build and forget...
As a third party, my understanding is that both the implementation and the protocol are really hard, if not next to impossible to iterate on. Modern hardware doesn’t work like how it did when X did, and X assumes a lot of things that made sense in the 90s that don’t now. Despite that, we cram a square peg into the round hole and it mostly works - and as the peg becomes a worse shape we just cram it harder. At this point no one wants to keep working on X.
And I know your point is that it works and we don’t need too, but we do need too. New hardware needs to support X - at least the asahi guys found bugs in the X implementation that only exists on their hardware and no one who wants to fix them. Wayland and X are vastly different, because X doesn’t make sense in the modern day. It breaks things, and a lot of old assumptions aren’t true. That sucks, especially for app devs that rely on those assumptions. But keeping around X isn’t the solution - iterating on Wayland is. Adding protocols to different parts of the stack with proper permission models, moving different pieces of X to different parts of the stack, etc. are a long term viable strategy. Even if it is painful.
But keeping around X isn’t the solution - iterating on Wayland is. Adding protocols to different parts of the stack with proper permission models, moving different pieces of X to different parts of the stack, etc. are a long term viable strategy. Even if it is painful.
The problem is, that’s always used as an excuse to force people to be gratis beta testers. I’ve been around for the wrecks that were (and still are) Pulseaudio and Systemd. Wayland is even worse: it doesn’t even fully start a session in my machine. If as devs you want to “iterate”, sure, go ahead; but leave it in the dev branch; as a user, don’t try to sell me Wayland again until it’s actually over.
The problem is, that’s always used as an excuse to force people to be gratis beta testers
If as devs you want to “iterate”, sure, go ahead; but leave it in the dev branch; as a user, don’t try to sell me Wayland again until it’s actually over.
it’s opensource software, don’t like it? go ahead, don’t use it. They don’t owe anyone shit
Another method would be to just mount the remote smb location from your DC using fstab. I use Linux on bare metal, and I added a line to my remote share with noauto, so it doesn’t mount it automatically at boot, since I need to connect to the VPN first, and I don’t need permanent access. When I do need access, I just run mount adm and I’m in.
Those instructions are from the official docs, and install.sh comes from the source repo. It’s an annoying script (it basically runs apt, npm, make, on your behalf…thanks, I can do that myself), but if you’re trusting the repo source to begin with, I don’t think it’s any less secure.
YouTube got traction before Google bought it and before Google bought it they tried to make Google videos and failed, what peertube lacks is contributors
And discoverability, it still has ways to go on the social networking integration. I still don't know how to go from watching a peertube video on a peertube instance to liking/boosting it on another fediverse service, even if I wanted to.
That said, I have been following Peertube for a couple of years, and the progress has been incredible. It makes sense to create a solid foundation for video playback first, and a lot of people seem to not understand the extent of the innovation Peertube has made in that regard. Social media tools obviously come second after providing a solid service, and I have no idea it will develop in great ways in the coming years. :)
I rarely use Windows but I have a dual boot situation on my desktop PC for the odd game that acts up on Linux or to recreate bug reports. Every time I boot into Windows, I’m like, “Damn, people live like this?” Why does every single thing ask for a reboot? I know the reason but why can’t that be fixed?
I’m dualbooting as well, but only because a few games I play aren’t supported on Linux due to their anticheat. Namely Fortnite and Destiny 2. I’d completely switch if that wasn’t the case. Hopefully someday.
I’ve also found this article that doesn’t add nvidia to the mix. But in general it seems to work the same for both as long as you have the drivers proper for your hardware installed
I’m a software developer (my background), I was always kind of interested in it, but primarily the fact that Apple stopped giving my 2015 MacBook Pro OS updates, including security updates, which forced me to do something.
And yeah, Plasma or GNOME is pretty much how the OS looks like.
I was experimenting with the Cadence tools from KXStudio. These are mostly made for JACK, but PipeWire has a JACK interface so it should work. It’s similar to helvum, but with more options.
Not sure right now which one (maybe Carla), but one of these programs also support adding sound effect nodes that have their own GUI! You probably want to use it in multi-client or patchbay mode
My audio set up is using jack on Ubuntu. If I were to start using pipewire, does it replace jack? Or do you use it alongside jack? I use mostly ardour, hydrogen, renoise and bitwig.
qjackctl will actually connect to pipewire, I use its graph window a lot to route audio when the default volume control isn’t enough. But yeah it does (or can) replace jackd.
Fedora Silverblue. But when switching I had to wrap my head around the differences in the workflow of doing things. Once youre past that it’s rock solid and had no issues so far.
when switching I had to wrap my head around the differences in the workflow of doing things. Once youre past that it’s rock solid and had no issues so far.
init system, without which you’d be left with only one program running at a time
some programs are written in interpreted language (e.g python, shell, perl), so the interpreter would also be required
C library, without which none of the above would function (yes, even if all the programs are statically compiled, it still has that library included with each executable)
this one is not necessary for the runtime, but is needed for creating a working system: toolchain – preprocessor, compiler, linker, assembler – all the stuff for transforming the source code into executables
Another comment mentioned Linux From Scratch, I’d totally recommend that, but it would take so much of your time manually building stuff (which is why it is so educational). If you don’t have the time, you may want to opt with Gentoo instead.
The multi-user system, which is a bunch of config files, libraries, utils and UIs, that deal with logging in or doing stuff as a specific user.
The logging system. Individual applications can simply log to a different file each but for system services the logging is usually centralized and offers additional features (like logging remotely etc.)
Setting up networking is pretty much mandatory these days.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.