41–50 of 131 posts
I"m still absolutely floored with how good the archwiki is. I can't hype it up enough. I really did't know what I was doing with systemd until I read that wonderful article, and also, the link to why the arch maintainer switched that distro to systemd made my accept the change to it.
I"m still absolutely floored with how good the archwiki is. I can't hype it up enough. I really did't know what I was doing with systemd until I read that wonderful article, and also, the link to why the arch maintainer switched that distro to systemd made my accept the change to it.
When I was starting with Linux (15 years ago) with Fedora, Ubuntu, etc., for all of my questions I kept finding answers on the Arch wiki. So eventually I just switched to Arch, so the answers would always work. That was an era when searching the Internet worked. Come to think of it, I haven't had Arch wiki pop up in my search results in years.
Instead of creating multiple wikis with probably 80% of duplicate information between them, it would be great to have a cross distribution wiki with separate sections for distribution-specific instructions where it makes sense. Gentoo had a fantastic wiki before they lost it to disk array failure (IIRC) around ten years ago, now pretty much everyone is going to the Arch wiki, why not try to turn it into a shared proj…
What would be even better - just a single, unified distro. Imagine if all those man-hours where actually focused on delivering a single working and polished FOSS OS. I know, FOSS is all about choice, yada yada.
Nobody wants Linux to be more like windows, and otherwise they’d just use windows.
The Arch wiki is one of the best things the Linux community has produced. It's like a modern, improved and more complete version of TLDP. I haven't even used Arch on any of my machines but can't count how many times I've found their wiki useful for my workstations, servers and even custom Yocto-built systems. Arch supports many ways of doing a thing, so whatever tool I'm dealing with, Arch probably supports that and…
Instead of creating multiple wikis with probably 80% of duplicate information between them, it would be great to have a cross distribution wiki with separate sections for distribution-specific instructions where it makes sense. Gentoo had a fantastic wiki before they lost it to disk array failure (IIRC) around ten years ago, now pretty much everyone is going to the Arch wiki, why not try to turn it into a shared proj…
Wikis do tend to link a lot across one another. On the Alpine Wiki, I prefer to link to the ArchWiki when applicable, rather than copy content over.
Instead of creating multiple wikis with probably 80% of duplicate information between them, it would be great to have a cross distribution wiki with separate sections for distribution-specific instructions where it makes sense. Gentoo had a fantastic wiki before they lost it to disk array failure (IIRC) around ten years ago, now pretty much everyone is going to the Arch wiki, why not try to turn it into a shared proj…
What would be even better - just a single, unified distro. Imagine if all those man-hours where actually focused on delivering a single working and polished FOSS OS. I know, FOSS is all about choice, yada yada.
I know, people have difference preferences, yada yada.
The Arch wiki is one of the best things the Linux community has produced. It's like a modern, improved and more complete version of TLDP. I haven't even used Arch on any of my machines but can't count how many times I've found their wiki useful for my workstations, servers and even custom Yocto-built systems. Arch supports many ways of doing a thing, so whatever tool I'm dealing with, Arch probably supports that and…
After using FreeBSD and OpenBSD, it is frankly shocking how bad Linux documentation is in comparison. On the BSDs every command, every program, every system call, and every configuration file are thoroughly documented in man pages and other guides. The FreeBSD Handbook in particular is a treasure. It more than makes up for some of the more difficult aspects of the OS by providing thorough and approachable documentati…
BSD ties the kernel and the software on top of it together pretty heavily, creating the expectation that the documentation should cover all of it.
Linux is meanwhile kernel and software kept separated, meaning that the documentation usually winds up assembled from separate tools, each with their own standards.
Hopefully they share it with NixOS next
Earlier quoted context omitted.
What would be even better - just a single, unified distro. Imagine if all those man-hours where actually focused on delivering a single working and polished FOSS OS. I know, FOSS is all about choice, yada yada.
Yep, and who cares about the FOSS OS part? We could combine Macos and Windows too! Think of all the money and time that could be saved by having a single global unified OS team! I know, people have difference preferences, yada yada.
It wouldn't produce a FOSS OS, as they are not FOSS.
Try more.