4 ms·
I guess I'm biased as an Arch user but I've found their documentation to be leagues ahead of everything else I've used. That said, it doesn't solve the offline
by busterarm 12y ago
I guess I'm biased as an Arch user but I've found their documentation to be leagues ahead of everything else I've used. That said, it doesn't solve the offline access issue you raised and the BSDs are firmly in second place.
That said, I've been starting to care quite a lot more about security and code correctness in light of recent events and have been waiting for today to install OpenBSD on my machine.
- eeZi 12y ago> That said, it doesn't solve the offline access issue you raised https://www.archlinux.org/packages/community/any/arch-wiki-docs/ https://www.archlinux.org/packages/community/any/arch-wiki-d...
- rakoo 12y agoAlso of interest: http://kmkeen.com/arch-wiki-lite/ http://kmkeen.com/arch-wiki-lite/
- deleted 12y ago[deleted]
- cgag 12y agoYou'd put the bsd handbooks in second place after the Arch wiki? The FreeBSD handbook seems a lot more impressive and coherent to me, so does the OpenBSD documentation.
- rakoo 12y agoI guess he meant compared to other various Linux distribution docs; in that case I can only agree with him.
- _delirium 12y agoThey're a bit hard to compare imo. The FreeBSD documentation is more coherent but also more focused/narrow, covering only the base system and a few common extensions. The Arch documentation is less coherent, but quite extensive, covering almost everything. I think the Arch wiki is less good as a proper manual, something you'd sit down and read cover to cover as an introduction to the system. But one thing that's nice about it is that it's really a one-stop shop: if you want to know what some package does, how it works, and how to configure it, it's probably there. If it doesn't play nicely with Arch or needs a workaround for common issues, chances are it's documented there too. Whereas with FreeBSD you're good as long as you stick with the base system, but it's a wilderness once you venture out into ports, with documentation/tips/workarounds scattered across the web, forums, mailing lists, StackOverflow, etc.