>American Megatrends
Who are they and why is their spyware on every x86 board in existence?
2 weeks ago
Anonymous
It's literally just a bunch of boomers that remember how to bring up an i386 if you put a whiskey in them.
2 weeks ago
Anonymous
I 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 fricked hardware configurations, that are now used as "features" on some boards.
PowerShell 7.4.2
PS C:Userspc> systemd-analyze
systemd-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.
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 tbh. Did I win?
The 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?
PowerShell 7.4.2
PS C:Userspc> systemd-analyze
systemd-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.
wtf, 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
OP 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
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.
kigger
systemd-analyze: command not found
this u?
No, I'm not a moronic systemd tripgay either.
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?
you're probably not using uefi lol
dmesg says I'm using efi though
>[ 0.000000] efi: EFI v2.3.1 by American Megatrends
idk for some reason it's not reporting how long it was in bios/efi before booting, that's all you're missing
>American Megatrends
Who are they and why is their spyware on every x86 board in existence?
It's literally just a bunch of boomers that remember how to bring up an i386 if you put a whiskey in them.
I 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 fricked hardware configurations, that are now used as "features" on some boards.
PowerShell 7.4.2
PS C:Userspc> systemd-analyze
systemd-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.
why is scrot such a broken piece of shit?
ensmallen the window really small and just run
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 tbh. Did I win?
so far you are in second place. OP is in first.
Startup finished in 6.332s (firmware) + 9.260s (loader) + 1.668s (kernel) + 15.507s (userspace) = 32.769s
graphical.target reached after 15.483s in userspace
Tell me the secrets to being an OS master
The 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?
>tripgay OP
>tripgay replier
Only based posts in this thread.
Startup finished in 4.663s (kernel) + 5.789s (userspace) = 10.452s
graphical.target reached after 5.756s in userspace
is this good?
~14 sec from power button to logged in.
What is it?
a slow piece of shit computor
Startup finished in 35.718s (firmware) + 2.521s (loader) + 17.415s (kernel) + 8.015s (userspace) = 1min 3.670s
multi-user.target reached after 8.012s in userspace.
get on my level
~ lsb_release -d
Description: Devuan GNU/Linux 4 (chimaera)
I did use Devuan for a while, but the lack of systemd meant my security key couldn't work.
Doesn't work on windows 11 🙁
Startup 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.
is there a systemd-analyze for shutdown?
0s if you just unplug it
8s if hold down power button
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
wtf, 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
Startup finished in 6.415s (kernel) + 2.211s (userspace) = 8.627s
graphical.target reached after 2.209s in userspace.
There you go
What a relief!
i'm sorry you have to use xfce
Not needed. I'm all good
Name one thing wrong with Xfce.
it's gay and shitty
To each their own. I think it's amazing with the right theme and icons.
i will but idk what app you put it in
>bashing Windows while your shitbox OS takes minutes to boot
lol
This thread is hilarious
OP 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