From: Logen Kain <walach.o...@gmail.com>
To: voidlinux@googlegroups.com
Subject: What's a complete "just works" distro?
Date: Sat, 21 Mar 2015 17:17:46 -0700 (PDT) [thread overview]
Message-ID: <de6ca1b5-1e35-4262-a249-1d416e81b0b9@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1994 bytes --]
tl;dr:
Me rambling and mostly figuring it out on my own, read at your own risk.
I often say VoidLinux has one big con:
All other distros feel slow once you use Void.
It actually is a con for me at this point, because I'm looking for a "just
works" distro. The last time I tried to use Ubuntu, it was at least 100
times slower than Void (and also rarely "just works").
Apt is slower during a normal update, than it takes fglrx to do it's
thing. In addition to all those problems, Ubuntu has a way of frustrating
me as much as a set of headphones that have that broken wire that almost
works if you twist it just right.
Are there any distros out there that have at least a fraction the speed
Void does? I'd like to have a distro on hand that has tons of packages so
it's easier to test new programs I find out about that are not available on
void.
The only distro I can think of that might match this requirement is Sabayon.
The only other distro that comes close, aside from Sabayon, is Arch LInux.
I'm actually looking into audio/video production, so any distros that are
good for that, as well as being fast, is what I'm looking for.
xbps and runit spoil me. I expect too much from my operating systems now.
Honestly, I'll probably just spin up Arch in a VM to test packages. If I
like the program, then I'll try to package it for Void. Void is missing a
lot of packages for the artist community.
Unrelated question: How the hell does Void seemingly never break? I've
seen a couple issues over the time I've been with Void, but it all seems to
get fixed without my intervention. On Arch Linux, if I forget to update
for a week, my system would crash if I tried to update.
Perhaps Gentoo would work out, just build a machine specifically for audio
production and just never update it.
Anyway, I've pretty much answered myself here, but I'm going to post
anyway. Perhaps there is something I'm not seeing.
[-- Attachment #1.2: Type: text/html, Size: 2101 bytes --]
next reply other threads:[~2015-03-22 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 0:17 Logen Kain [this message]
2015-03-22 7:58 ` Juan RP
2015-03-22 14:07 ` Christian Neukirchen
2015-03-23 3:30 ` Logen Kain
2015-04-07 20:38 ` bougyman
2015-03-22 17:29 ` Stefan Mühlinghaus
2015-03-23 3:38 ` Logen Kain
2015-03-22 21:46 ` JD Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de6ca1b5-1e35-4262-a249-1d416e81b0b9@googlegroups.com \
--to="walach.o..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).