How Does Linux Boot Process Work?
Вставка
- Опубліковано 11 гру 2023
- Get a Free System Design PDF with 158 pages by subscribing to our weekly newsletter: bytebytego.ck.page/subscribe
Animation tools: Adobe Illustrator and After Effects.
Checkout our bestselling System Design Interview books:
Volume 1: amzn.to/3Ou7gkd
Volume 2: amzn.to/3HqGozy
The digital version of System Design Interview books: bit.ly/3mlDSk9
ABOUT US:
Covering topics and trends in large-scale system design, from the authors of the best-selling System Design Interview series.
This is a good summary, but it seems like there's a lot going on behind the scenes in all of these process, especially systemD. Would be nice to cover that in a future video :)
That would require a 1000 page book,...may be 10000 pages!
systemD is a disgrace and as UNIX-like as it gets.
Its functioning should never be covered nor should its name even be uttered more than strictly necessary
@@nid274hey bro in which domain you are studying right now?
@@nid274try reading Abraham Silberschatz OS concepts book
Yeah, pretty much "what does Kernel at boot" and "what does process with pid=1 at boot before enters configured runlevel" should have been content of the video, not detecting devices, running EFI, and rest of irrelevant shit.
Bravo si multumesc.E simplu,frumos pe intelesul tuturor...fara explicatii savante.CHIAR UN TUTORIAL...GENIAL DE SIMPLU!!!La mai multe inainte !!!
There's a bit of a misconception about BIOS. MBR is limited to 2TB, but a BIOS doesn't need to be restricted to MBR, it could've moved to a different (likely proprietary) format... it's just that GPT and EFI were more flexible and the groundwork was already completed
Good overview, but missing a discussion of ACPI, initramfs/initrd.
agreed, initramfs is a crucial part to be included in a boot process video IMHO
@@thecataclysmexactly, especially that the title mentions Linux specifically
@@thecataclysm Which is also the most interesting part that solves the chicken/egg problem.
All I know about ACPI is that it got FUBARd in my laptop and now the lspci doesn't even show my wireless lan card. Don't know what started it, but I guess it was some power cycling malfunction because it started after I woke the PC up from sleep. I've done fresh linux install and it doesn't work. So most likely will need to flash BIOS :(
I was expecting that you would really be talking about the kernal boot process and not everything around. But in the end, I never saw an exhaustive explanation about the boot process in the first place so I am that to know that I did not miss out anything.
Great summary and visualization of the entire boot process. Very well done mate!!!!
Great content, always helpful and always impressive. Thank you very much for taking the time to make these.
As has already been said, there is a lot going on in each of these steps.
My major criticism is that step 5 simplifies away the usual mechanism of running some code from an initial ramdisk: this is done so that the kernel does not have to contain all the device drivers needed to load whatever modules it needs before the final root partition becomes readable.
That also means that an earlier step needed to load the initial ram disk into memory and tell the kernel where to find it. Grub (or some other boot program like Lilo) will have done this already, so the Grub step should mention that it loads a filesystem containing drivers as well as libraries into ram before passing control to the kernel.
And then, in my opinion, you need an extra step between 4 and 5 for the initial ram stage, that is used to get the system able to actually read the code it needs off the disks. While it does that the kernel only needs to know how to read the initial ramdisk.
More detail follows...
There are two exceptions to what i just said
1. If you compile your own kernel you can arrange that the kernel has all the drivers it needs built in (Gentoo users might do this, knowing in advance exactly what filesystem and hardware will hold the operating system)
2. Puppy (and most Live Disk systems) boot into the ramdisk and never leave it.
For different reasons, both these exceptions slow down system loading (because either the kernel or the ramdisk is huge) but often speeds up running once the boot is complete because the kernel has what it needs in memory at all times, one way or another.
Great visualization of the entire boot process, Thank you.
Have never such a visually stunning explanation of a boot process. Amazing video
Thankyou so so much for sharing. Piece of art with tons of knowledge
Very nicely explained and beautifully visualized presentation. I have to ask tho, would you like to make that same presentation again but for a Secured and TPM measured bootgraph ? If so, please do it, people and especially the linux community would need this in order to understand why the TPM makes booting so much more secure. I would even offer my help understanding a measured boot process (which I am pretty sure you would have no trouble understanding on your own).
That’s beautiful and enormous work! Great thanks.
I was looking for something like this. This is great thank you!
Best Summary of the Boot process
This is incredibly well explained and illustrated! Thank you so much!
Wow, I just loved it - I am recomending to my felow IT guys who ignore those initial steps.
Regards from Brazil and keep posting!
KUDOS! I've never seen such nicer explanation for this.
Excellent presentation. Thank you for posting it.
One of the best channels in last few years
This channel is absolutely brilliant. I am blown away! 0__0 wow
It is possible to use gpt partitions without needing UEFI. Even old motherboards with intel 775 socket will boot using gpt partitions without UEFI:
"Yes, it is possible to use GPT (GUID Partition Table) partitions without UEFI (Unified Extensible Firmware Interface). GPT is a partitioning scheme for formatting and partitioning hard drives, and it's independent of the firmware interface being used (UEFI or BIOS).
However, the ability to boot from a GPT-partitioned disk depends on the firmware of your system. Most modern systems use UEFI firmware to boot, and UEFI is compatible with both GPT and the older MBR (Master Boot Record) partitioning scheme.
If your system uses the older BIOS (Basic Input/Output System) firmware instead of UEFI, it may have limitations when it comes to booting from GPT disks. Some BIOS systems can boot from GPT disks using a compatibility support module (CSM), while others may not support GPT booting at all.
So, in summary, while you can use GPT partitions without UEFI, the ability to boot from a GPT disk depends on the firmware capabilities of your system."
Nicely done! Good visual aids too
Very lovely & professional made
I was looking something like this and kind of explanation thanks man😊
Sir, thank you for such creative tutorials please make one on Spark
Great video.. I could not have done this better like you
Though I am a Linux user for the last 15 years..
Thank you
Thank you sir.
Nice diagrams too.
When Linux chooses to support initramfs boot, and selects the rootfs path to be packaged in the initramfs source file, it will try to boot in initramfs mode. In this way, the rootfs will be compressed and packaged in the same image file as the Linux kernel. Then uboot will load the whole image file into memory when the system is loaded. In this way, the rootfs cannot be modified in flash, and will be lost when the power is lost.
Thanks this is really informative
@@jali-cj5zq
Thanks for reading my comments!! I hope everyone’s got vim on their resolutions for 2024
I sept yesterday learning all this by myself and today, youtube recommended me this. If I had found this video, maybe I would have learned all that in 5 minutes.
Awsome, great job. thanks a lot for your time. excellent explanation!
Great overview. I think is good background info for any OS.
Nice explanation and great graphics.
thanks for the explanation! this helps!
thank your for this helpful explanation!
Nice and simple !
But you're missing the loading of initrd. I admit I can't remember from the top of my head when exactly it occurs. Would be a nice addition to your explanation.
In the classic Grub or Lilo bootloader, the initrd or initram (NB they are different!) is loaded after the kernel but before control is passed.
There are also the kernel parameters (append details in some boot loaders) that the boot loader has to make available to the kernel. These can be flags or switches to the kernel, to systemd, or to other programs run later on.
This was excellent, well done.
This is my favourite new channel.
very very nice. excellent animation. forcing us to view compulsorily immediately though we have plenty of pending works. it is like movie attracts us. go ahead.
Thanks! Loud and clear
I don't think you need to tell your audience anything about BIOS/UEFI, POST, boot devices or the boot loader. That part could've been left out and start with the kernel. Funny that you call loading the kernel "finishing the start-up process", considering the video's title suggests it's about the *Linux* boot process, _not_ the generic boot process that every OS goes through. Loading the kernel is actually where the actual Linux part starts! Not trying to bash, just suggesting how these videos can be better imho.
The information density here is very high
Nice video good explanation and presentation 👍
wow amazing, which tool you use for graphical representation in your explanations? ill try for my students too. please tell me if you can
Great job! It looks clean, straightforward, and easy to understand. Could you tell me what software you used to create this video? I'm interested in making my own technical videos in the same manner.
Where is initrd or initramfs? It is present in most if not all Linux system? Seems like you missed something.
Excellent demo
Great presentation! Thanks!
I love your presentations! Which tool do you use to create or generate them with such a beautiful animation?
Linux newbie here 🤓 Very nice video.
this is awesome, the same core idea when develop embedded firmware as well
nice explanation best so far :)
Thanks, it's a very good summary video with a good global presentation
Great descriptions... 😊
Excellent presentation and narration; whats' used for your animations?
Thank you for the information, as a follow-up will be great to take a step back and have instructions on how to identify if our system (desktop, laptop, mini PC, or server) supports UEFI for a faster boot, better functionality, and security. Thank you again!
That should be something you can look up based on your OS version and your motherboard model.
Doesn't grub also load an initrd image as well as the kernel? Where does squashfs fit in?
No way. I just guessed it right. I told exact same on my interview 😂.
What about the SPI flash? Coreboot/DepthCharge or uBoot and TowBoot?
What about the details of gdm3 and starting the graphical shell?
This seems more like a brief description of how *any* OS boots on a PC, just using the linux names for the later steps where it'll differ. Up to the boot loader step, there's not even an OS involved. And Windows uses a boot loader as well, it's just not called that and tends to be hidden from view for most people. Still, the same process. Code the hardwired system can find that loads the actual operating system. And whatever OS it is, the first step will usually be getting the kernel of the system going, drivers, etc. Same basic flow for any OS. Aside from the names used in those last steps, nothing here specific to linux.
An actual OS specific discussion of the boot process would start with the kernel loading. It's from that point that OS's diverge. The boot loader itself can be setup to point to different kernels and/or different OSs itself, which is how a dual boot works.
Missing initrd or initramfs part?
Right, this part is missing
also it is possible to use GPT without using UEFI boot ... so this is kind of useless, at least for me.
awww I thought you're gonna go into more detail about primary and secondary boot loader
Well done!
systemd-boot is great. No fuss just straight to the point !
I would have appreciated more time being given to the transition between the boot loader and systemd (the kernel initialization).
Same, i wonder what the name of the first process that runs within the kernel is. Is there some sort of entry point within the kernel like a main function or something that eventually calls systemd?
how do do you do these animations? its nice and clean!
Thanks for sharing
I anticipate to implement a service daemon manager in my operating system soon! Currently it just handles the transferred ownership from my kernel and does nothing but outputting in tty mode
So much nitpicking in the comments. I guess this is what happens when you try to teach linux users lol. Nice overview. Could be a nice quick ref for users.
With how short the common attention span is I think this is a nice start for people trying to learn more about linux.
Thank you
Great !!!
more please !!
High quality animation. Thank you for the effort. Can you make a video about Windows booting ?
Fire and explosions are covered in physics class.
I bought your books 📚, but haven't had time to read, by I hope I will do soon.
Hey, can you do the same for Windows?
2TiB drives was NOT a limitation of the BIOS firmware. If you had a very late version of a BIOS with the proper hardware, you could easily support sizes > 2TiB.
You made a fair point. The video refers to the 2TB limit of the master boot record (MBR). We should have been more precise in our language.
Exactly, as soon as they conflated MBR/GPT with BIOS/UEFI I knew this channel was mostly fluff. I think it's the second or third time this channel tricked me with an attractive topic and pretty graphic over lluminaughti-level writing. Too bad, a properly presented boot summary in 5 (or even 10) minutes would be pretty cool.
Today I read chapter 5 on How Linux Works by press starch. You took about 30 pages and summarized them in 4:43 minutes, except the book of course went in more detail at each step. Plus it had all the different boot loaders listed, even ones that are dead and gone. Do you have a System D VS Wayland video yet?
Systemd and wayland do different things. Systemd is simply the first program that the Linux kernel executes. When it starts, it reads a bunch of configuration files to figure out which other programs need to be run for the system to function, such as a network firewall or database like Mysql/Postgres. It also boots a program responsible for showing you the login screen. It's this login program (formally, a display manager) that figures out how to boot your desktop environment, which may use the Wayland protocol (it is not a program) or X11 protocol to communicate with the Wayland server or the X11 server, respectively.
The Wayland and X11 servers are also simply programs that do the job of interfacing with the linux kernel (and by extension the hardware) to allow clients (i.e., your window manager like Gnome or your browser like Firefox) to be able to draw to the screen in a hardware-independent way (i.e., not worrying about whether you're running AMD/Nvidia/Intel graphics). All that's necessary to run a graphical program is for it to speak the Wayland protocol to a running Wayland server process.
It just so happens that Systemd is responsible for starting the X11 and Wayland servers, because the init system is the most natural way to manage long-running processes upon which many other processes depend.
Prior to boot loader what is the software that controls all these? Also how does a boot loader identify all the available kernals? like how does it know? is there already a software that reads this?
very nice video... loved it...
If initramfs also coved in this video then this could be the best one...
Great thanks
Although a thing to point out is that you don't need a boot loader now, you can just expose the kernel to UEFI and write flags directly into boot record.
Can you please post a link to a "how to" on skipping the "grub" phase of booting?
And if you do that do you have to avoid using an initial ramdisk in the usual Linux way? I can't see how the boot flags alone can properly load the ramdisk (which might of course be my ignorance, hence my question)
@@trueriver1950 use an efistub and efibootmgr to make uefi entry with kernel args pointing to initrd
excellent!
Thank you, well done. :-)
Always impressive.
UEFI was in Macs for years. "New kid", right.
This question might not get answered but I’ll try anyway. What program do you use to generate those cool animations for your videos?
thank you!
Coreboot for the win
How to run two kernel at the same time. Can you ever switch processor type. Two clocks.
I think this video could have extended itself to include the graphical boot process. The display manager which boots up the desktop environment.
and loading the filesystem image?
The main problem with this video, and I don't want to be too critical, is that there's no real-depth in what is going on. Firstly the explanation about the BIOS and POST etc has nothing to do with Linux. That's the hardware initializing itself for the booting of an operating system. The video should have focused from this moment onwards and gone into the details.
I agree
Everything in this video is 100% accurate. A more appropriate approach would be, ‘Great video - would it be possible to shoot a follow up with more depth on x,y or z?’ Every YT creator should be considering YT algorithm when producing - and the algorithm favors videos that appeal to a broad audience - technical depth narrows the audience. 🙏
Mf it's called scope, this is a obviously meant to be a high level overview
@@XxZeldaxXXxLinkxX I take it from your comment that you have literacy problems, yeah? The video is titled, How does the Linux boot process work and this video barely even gets close to describing the process. I mean, the BIOS boot process is the same whether you're booting Linux, Windows or BBC Basic! It literally has nothing to do with the Linux boot process. If they described how the BIOS initialized itself, that's different and would constitute a 'scope'.
I think, it's not precisely about Linux boot up as soon as he starts from "what happens when you press the power button".
Edit: Anyway, it's a nice video giving revisions to those who know everything.
Wonder why there is a stage 1 (initrd) and stage 2 in the Linux boot process
initrd used to be a ext2/ext3 partition that can be mounted as loop device, now it's just a compressed a cpio archive, usually distro kernel is light and doesn't have network/disk/fs drivers so when the kernel is pushed to memory by grub it can't recognize hw and even mount fs. All needed drivers are stored in initrd image. More over linux thin clients mount root via nfs or nbd and again drivers and glue shell code is stored in initrd. And so called second stage is a chain load when a real hd init process is started and a root pivot is happening.
thanks
How does this relate to hibernate and suspend? I.e. I assume some of the steps involved in boot would also have to happen after a wakeup from suspend/hibernate, but other things do not. What are the differences and similarities between a boot from scratch, and waking up from suspend/hibernate?
Mostly same. On a very high level its just that when you hibernate, the contents of your RAM are temporarily stored to your hard disk and during the boot process the kernel will pull these contents and use them instead of starting new process.
Windows: press on, uefi/bios starts, windows starts
Mac: press on, macos starts
Linux:
"You had me at POST"
Спасибо, добрый человек.
My linux mint struggles to start on its own despite having only one ssd and it's the main bootable device, it works well when I start it in safety mode but won't boot straight after I power my pc.
Anyone.. Which software is used to make this video (animations)?
2:19 What is Aid boot v0 ? Is it a some project?
I hated systemd when my distro first started using it, but now i think its much better than system V