Re: My overview of the kernel --> do I have it correct ??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11-07-08 07:25, William Case wrote:

Let's rejoin the list if we're going to continue this conversation anyway...

Please do, even if only with a large brush. Until then, at least I
personally am going to view your model as a little ridiculous and
of no substance or use.

Suggest another one then. His definition suggests a library of abstracted hardware access, device multiplexing (eg. multiple
programs use the network card at once), storage and retrieval of data
and other system services.  How does that get me anywhere new?

Why do you think you need to get anywhere new? Operating systems are not new and many intelligent people have thought about them over the decades and the above model that you say that (snipped) "could have been cut and pasted from the opening pages of any first year text" did not end up on those first pages for nothing.

You asked for (explicitly non-expansive) comments on your model, not for readers to provide another one even though Rik in fact did. Ofcourse, if you think you need more useful comments, the onus is on you to first explain why your model helps any.

If not, I could come in here and say I'd like to view kernels as large collections of independent nano-bots and then demand that people tell why they weren't. Wouldn't you in that case agree I'd first have to explain WHY I'd like to do such a ridiculous thing in order to indicate to you that any comment you'd provide would have a chance of being useful; wouldn't just be swallowed whole into my intellectual vanity?

As far as I can see each one of those tasks simply has code that
points to further code in the library.  Libraries are simply a list
of definitions and functions.  The particular library codes that have
to be pointed to for each task are in stored in a structure.

And why does that view help any? What does it explain? Frankly, this table view you've outlined sounds as the kind of Unifying Encompassing Model every single one of us will have thought up back when we were naieve, beginning programmers. As indicated, you are here in very pragmatic surroundings and reality is that operating system kernels aren't collections of tables or any other neat abtraction but heaps and heaps of messy code...

And sure, you can talk anything to any model, even if only by insisting that enough of that whch doesn't fit is an uninteresting detail (can you see I walked this road?) but the question of it helping any is the important one.

Rene.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux