wtf /g/? And I'm on Mint w/ Cinnamon lol
whats the command for that?
(No forkbombs thanks)
>>57025652
systemd-analyze, friendo
>>57025634
>mint
What a fucking idiot.
>>57025634
>systemd
I found your problem
>>57025677
dumb question, does systemd load in userspace or kernelspace?
>>57025677
elaborate further plz
>>57025634
>mint
>>57025666
>systemd-analyze
Thanks mate
>>57025711
distro and DE?
>>57025721
Debian 8 XFCE
>Startup finished in 2.017s (kernel) + 1.350s (initrd) + 3min 1.383s (userspace) = 3min 4.750s
:^(
>>57025976
how
Startup finished in 4.523s (kernel) + 1.784s (userspace) = 6.308s
Mint with Cinnamon
>Startup finished in 3.255s (kernel) + 17.806s (userspace) = 21.061s
Debian with Cinnamon
>>57026038
wtf am I doing wrong guise?
>>57025634
well wouldn't it be convenient if systemd-analyze could list processes by startup time ...
>>57025976
wtf..... WTF
>>57025999
i don't know
i just put my computer to sleep at the end of the day
uptime
22:32pm up 42 days 15:18, 12 users, load average: 0.55, 0.74, 0.79
Windows 10: Booted with chromium, fb2k, file, etc open before screen turned on fully.
spinnan cubez/hdd fags btfo.
>>57026264
I have windows 10 with an SSD and find this incredibly hard to believe. My screen turns on during the bios screen. do you have an incredibly shit monitor?
Windows 10 LTSB does not have this problem
>>57025634
>Mint
Install Antergos
>>57025634
>>57025698
he's meming
>>57026353
>not using server 2016
Arch KDE, on a 5400 rpm with an amd E1-1500
>>57025634
Why don't you just see what software takes so long?
Just add the --blame flag after the command and post results.
>>57026662
Sorry brainfart over here. systemd-analyze blame
That's the command.
>>57026675
it was something like apt daily
>>57025634
>Mint w/ Cinnamon
It's bloated and laggy as fuck. I used to use that too and even though I installed it on an SSD it booted up in 40 seconds, even slower than windows. Debian with cinnamon boots in 5 seconds from the same drive though.