Yeah no. An operating system kernel doesn't just act as a host for userland processes, it interacts with hardware. Hardware behaves in weird and unexpected ways, can be quite hard to debug, can fail, etc.
This is why Linux is excellent. Users of other operating systems often remind people to update their device drivers. A non-technical Linux responds asking what the heck device drivers are. To the casual user, device drivers become invisible because they work exactly as intended.
The kernel talks to the device using an API it exposes. Similarly Chrome will talk to the OS using an API it exposes. OS APIs can also behave in weird and unexpected ways, be hard to debug and fail. Chrome protects the content it hosts from this complexity. Interacting with the layer underneath you is part of your job of hosting things on top of you.
Those are just drivers to stuff that runs its own cpu and interfaces over some kind of serial port. Printers are a well known example of this. Also intel wireless nics with their firmware blobs.
Not are drivers are like that. For instance, drivers/input/serio/ps2-gpio.c is all about timing the right signals.
You are missing the point. The kernel is still abstracting over those GPIO timings so programs don't need to know the timings themselves. This is the benefit of using a platform. These low level things get abstracted away from what you have to do.
Oh, I see. You're piecing together the layers much like a cake.
The way I see it, everything is tied together as some kind of flow chart where different elements have different jobs. Linux is quite a small part of the system when compared to Google Chrome. Even if you were to invert the cake, as a whole it still wouldn't make sense to me to see it that way.
Hardware tends to have more distinct layering than the lalala-land of software where pretty much anything goes.
And have that be a shell script which starts whatever you need. You'll probably want fsck in there, mount -a, some syslogd, perhaps dbus, some dhcp client, whatever else you need, and finally the getty which is probably a good idea to respawn after it exits. That's usually the job of init so you could well end your rc with exec /sbin/init
This. Only CPU microcode can't be loaded without an initramfs unless you enable late loading, but that's labeled dangerous because it may cause instability. If needed, you could let the built-in motherboard uefi do the microcode updates instead.
Working with both at the same time makes their strengths and pitfalls shine. It's like that dual-boot computer where you're constantly in the wrong OS.
HTML has better separation of concerns than latex.
Latex does typesetting a lot better than html.
HTML layout can differ wildly in the same document.
Latex documents are easier to layout in the first place.
Even if Oracle evaporated and their contemporary ZFS source became unencumbered, I doubt OpenZFS would want to try and merge significantly parts. They already have their own encryption implementation for example.
Hmm. Trying to remember if places I've worked at talked about "The Intranet" or "the intranet." I guess you could use "Intranet" as a proper noun if you're talking about the one in use at your company but then "intranet" if you're talking about the concept of an internet inside your company's firewall that's not connected to the Internet.
But yes, capitalized "Internet" refers to the "Connected Internet," of which there is only one. The first rule of SIPRnet is no one talks about SIPRnet. But if we did talk about it, the comment would likely be that it is like "the Internet" but not "the Internet."
If you spend time in academia or academia-adjacent industrial research, you sometimes hear "an internet" (always with lower case to signal it's a common noun) to describe a network of networks. But you are right... that use is not growing and if anything shrinking.
Maybe some aliens out there have their own internet. But then is the internet just the sum of all intranets and thus in a way just the top-level intranet?
It just needs a catchy name.
reply