Post number #517756, ID: 2d5e3e
|
I'm still struggling with Debian. But one day Arch will be mine. Although I do wonder what's the point of making my life that hard.
Post number #517757, ID: 30fc2d
|
Now it's time to install gentoo
Post number #517759, ID: b7068e
|
What desktop or Windows manager should I install?
Post number #517768, ID: feafbb
|
>>517759 lxde if you want a complete de. A tiling vm like awesome otherwise.
Post number #517772, ID: 66c69c
|
>>517756 >that hard It's as easy as setting up Debian netinstall. Updates are even easier in Arch because you aren't tracking updates by arbitrary OS version, no 'update the OS this year for longer support' either.
Post number #517782, ID: 45cf7c
|
>>517759 I would recommend the KDE-Plasma Desktop. If you look for something more resource friendly, have a look at LxQt. Since it's based on the same UI-Engine (Qt), as KDE most Applications from KDE integrate seamless into LxQt (and vice versa). You can install them parallel and choose between them during login either remotely with "x2go" or locally with a local display/session/login-manager like "sddm". Most other Desktops (and apps) use GTK as ui-engine, which sucks.
Post number #517853, ID: 469c34
|
>>517751 delete your VM
Post number #517860, ID: 2368c1
|
>>517853 I didn't install it on a virtual machine.
Post number #517888, ID: 8ba761
|
In the words of an achorman: I don't believe you.
Post number #517939, ID: 2d5e3e
|
>>517772 Setting up Debian was easy, maintaining it properly is hard. Mint was way easier.
Post number #517942, ID: b4f7cf
|
Arch is just a toy
Post number #517980, ID: ffa2e7
|
>>517939 Debian has been nirvana for me for many many years now. But with sadness, I know that my next install when the time comes, will be Devuan. Systemd has become worse than svchost.
Post number #518117, ID: 55cd8d
|
>>517751 install gentoo
Post number #518188, ID: bc260d
|
>>517751 Wait for Elon Musk OS.
Post number #518428, ID: 2d5e3e
|
>>517980 See, I don't understand what you're talking about. I am not ready for Arch.
Post number #518434, ID: 66c69c
|
>>518428 tl;dr "my girlfriend now is needy and unstable, I want our relationship gone."
Post number #518437, ID: f37662
|
>>518428 Systemd initially was an init script (scripts that run when you start the system that prepares everything in your computer to be used, it's like when you turn on a car and the car turns on all the needed mechanisms to work). I said was because Systemd started to be more invasive with other processes, irrespecting the unix philosophy. The main risk isn't that, but the fact that almost every distro uses systemd, without an option to change it.
Post number #518438, ID: f37662
|
>>518428 systemd guy again :) Systemd is also a theorical source of vulnerabilities because of power it has, and it would be a literal One Piece of a backdoor for not only attackers but goverment agencies.
Post number #518809, ID: 0e490f
|
The thing is most functionality systemd provides you'd install 99% of the time anyway. You could easily argue it's more secure to keep that in a single well maintained and audited package then dozens or hundreds of small miscellaneous packages.
Post number #518852, ID: 05980b
|
Capcha
Post number #518946, ID: 2d5e3e
|
>>518809>>518438>>518437 Thanks for the explanation.
Post number #518969, ID: feafbb
|
>>518809 Sounds like a lot of work. Are people actually trying to do something about this? Are you?
Post number #519288, ID: 989eff
|
I actually like systemd, because it makes administration easier to me. But I also see the issues people have with it, as it somehow violates the unix standards that I also love and respect. I just wish distributors would make it more optional in their distros. All distros I currently (have to) work with are very depended on systemd. I think it's also because it makes things easier for distributors. Comfort always has its price and sometimes is a false friend.
Total number of posts: 24,
last modified on:
Sat Jan 1 00:00:00 1546555566
| What now?