post your systemd-analyze
Startup finished in 13.643s (firmware) + 4.085s (loader) + 36.621s (kernel) + 23.176s (userspace) = 1min 17.526s graphical.target reached after 23.168s in userspace.
>>100198054kigger
>>100198054systemd-analyze: command not found
>>100198086this u?
Startup finished in 441ms (kernel) + 4.860s (initrd) + 50.500s (userspace) = 55.803s graphical.target reached after 50.434s in userspace.Why am I missing some of the stages?
Startup finished in 441ms (kernel) + 4.860s (initrd) + 50.500s (userspace) = 55.803s graphical.target reached after 50.434s in userspace.
>>100198092No, I'm not a retarded systemd tripfag either.
PowerShell 7.4.2PS C:\Users\pc> systemd-analyzesystemd-analyze: The term 'systemd-analyze' is not recognized as a name of a cmdlet, function, script file, or executable program.Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
>>100198107you're probably not using uefi lol
why is scrot such a broken piece of shit?
>>100198151ensmallen the window really small and just run scrot -u
scrot -u
Startup finished in 8.986s (firmware) + 7.843s (loader) + 1.609s (kernel) + 4.914s (userspace) = 23.353s graphical.target reached after 4.892s in userspace.I don't know what any of this shit means to be perfectly desu. Did I win?
>>100198126dmesg says I'm using efi though>[ 0.000000] efi: EFI v2.3.1 by American Megatrends
Startup finished in 6.332s (firmware) + 9.260s (loader) + 1.668s (kernel) + 15.507s (userspace) = 32.769sgraphical.target reached after 15.483s in userspace
>>100198164so far you are in second place. OP is in first.
>>100198169idk for some reason it's not reporting how long it was in bios/efi before booting, that's all you're missing
>>100198054Tell me the secrets to being an OS master
>>100198218The path to becoming an OS master, a true wizard of the computer, isn't a linear one. It's a journey that blends theoretical knowledge, practical experience, and a deep curiosity for how things tick. Here's a roadmap to get you started:Foundational Knowledge:Dive into Core Concepts: Master the fundamentals of computer science. This includes understanding data structures, algorithms, memory management, and processes. These are the building blocks of any operating system.Pick Your OS Poison: While there are many operating systems (OS), focus on a few popular ones like Windows, Linux, or macOS. Learn their architecture, kernel functionalities, and user interaction mechanisms.Practical Experience:Get Hands-on: Don't just read about OS, play with them! Install different operating systems on virtual machines or personal machines (if you're comfortable). Experiment, break things (safely), and tinker to understand how they work under the hood.Command Line Fu: Become a master of the command line. This is the direct interface to the OS and grants you fine-grained control. Learn powerful tools and scripting languages like Bash or PowerShell to automate tasks and manipulate the OS.Deepen Your Expertise:Open Source Magic: Explore the world of open-source operating systems like Linux. Here, you can delve into the source code, understand how the OS is built, and even contribute to its development.Never Stop Learning: The OS landscape is constantly evolving. Keep yourself updated with the latest advancements in security, virtualization, and containerization technologies. There are online courses, workshops, and conferences dedicated to OS that can further your knowledge.The Wizard's Touch:Beyond Functionality: Becoming a master goes beyond technical prowess. Understand the design philosophies behind different OSes. Why is Linux known for its flexibility? What makes macOS user-friendly?
Startup finished in 4.663s (kernel) + 5.789s (userspace) = 10.452sgraphical.target reached after 5.756s in userspace
is this good?
>>100198054whats the use case for this thread
Startup finished in 35.718s (firmware) + 2.521s (loader) + 17.415s (kernel) + 8.015s (userspace) = 1min 3.670smulti-user.target reached after 8.012s in userspace.
get on my level~ lsb_release -dDescription: Devuan GNU/Linux 4 (chimaera)
~ lsb_release -dDescription: Devuan GNU/Linux 4 (chimaera)
>>100198054Doesn't work on windows 11 :(
>>100198054Startup finished in 5.494s (firmware) + 2.328s (loader) + 5.303s (kernel) + 1.048s (userspace) = 14.175s graphical.target reached after 1.048s in userspace.I have to press a key in rEFInd to continue, so the loader time could be a lot lower.
>>100198169>American MegatrendsWho are they and why is their spyware on every x86 board in existence?
>>100198358I did use Devuan for a while, but the lack of systemd meant my security key couldn't work.
>>100198405It's literally just a bunch of boomers that remember how to bring up an i386 if you put a whiskey in them.
>>100198054
>>100198054>tripfag OP>>100198242>tripfag replier>>100198086>>100198117>>100198374>>100198492Only based posts in this thread.
>>100198054is there a systemd-analyze for shutdown?
>>100198265~14 sec from power button to logged in.
>>100198405I think it's kind of like enterprise software that's still run on IBM mainframes. It works, and nobody is willing to stump up the money to do it themselves. It's not worth it for motherboard manufacturers, and trying to break into the market would be quite difficult, since initial cost to develop the firmware would be very considerable. I also have no doubt it's full of weird hacks and gimmicks that were originally to work around fucked hardware configurations, that are now used as "features" on some boards.
Startup finished in 10.632s (firmware) + 5.857s (loader) + 42.711s (kernel) + 2.344s (userspace) = 1min 1.546s graphical.target reached after 2.298s in userspace.severely bloated arch btw
Startup finished in 10.632s (firmware) + 5.857s (loader) + 42.711s (kernel) + 2.344s (userspace) = 1min 1.546s graphical.target reached after 2.298s in userspace.
>>100198492is that... is that.... SHARTIX!?!??!?!?
Startup finished in 6.415s (kernel) + 2.211s (userspace) = 8.627s graphical.target reached after 2.209s in userspace.
There you go
>>1001990130s if you just unplug it
>>1001996258s if hold down power button
>>100198304What is it?
>>100199650a slow piece of shit computor
What a relief!
>>100199710i'm sorry you have to use xfce
>>100199521wtf, this is what my Kubuntu system gets and with an encrypted harddrive that I have to enter a password for during the boot process (idk where that's accounted for though)Startup finished in 3.378s (firmware) + 4.598s (loader) + 17.064s (kernel) + 19.859s (userspace) = 44.901s graphical.target reached after 19.832s in userspace
>>100198054i will but idk what app you put it in
>>100199823
>>100199737Not needed. I'm all good
>>100199737Name one thing wrong with Xfce.
>>100199914it's gay and shitty
>bashing Windows while your shitbox OS takes minutes to bootlolThis thread is hilarious
>>100199944To each their own. I think it's amazing with the right theme and icons.
>>100199955OP here, mine took 20 seconds including 13 seconds of OS-agnostic time to be fully loaded up to the desktop. That's a 7 second boot basically and it's to a full and fat KDE desktop
