This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
Text like "A Monolithic kernel is a kernel architecture where the entire kernel is run in kernel space in supervisor mode." needs to be cleaned up. "entire kernel is run in kernel space " Kernel is suppose to be in Kernel Space. I think what it meant here is that apart from Kernel section, Device Driver and other modules like File system and security system, network system are also made part of the Kernel system. (May Be I am wrong .. but someone who knows better should update and clean this section.
Amberved ( talk) 15:27, 21 March 2008 (UTC)
-- Beland 21:32, 21 March 2007 (UTC)
The text is unreadable at the image's normal display size, and the image contains non-functional gradients and coloration. LokiClock ( talk) 04:44, 11 February 2010 (UTC)
In what respect is a monolithic kernel a more well-defined subject than monolithic code in general? Can the article be generalized? Also, how does "monolithic" compare to spaghetti code? While "monolithic" is not as pejorative, are they conceptually any different? Ham Pastrami ( talk) 12:22, 3 April 2008 (UTC)
This part is patently untrue.
I read in http://en.wikipedia.org/wiki/HP-UX that, it is also runs on monolithic kernel method. Does this OS also need to be added here ? Kanthaa ( talk) 11:56, 14 December 2008 (UTC)
Isn't Slackware simply a GNU/Linux distro? Or is there some sort of history behind it where did not use Linux? I don't think adding a bunch of Linux distros to be the most sane thing to do, even though the kernels are slightly different. -- SeyedKevin ( talk) 00:20, 23 October 2009 (UTC)
If you don't already know this material, and take the time to look here and elsewhere on the web, it would be impossible to cut through the morass of jargon. It is the worst example of technical writing that I have seen on Wikipedia in a long time.
Specifically I find the content is like a paragraph version of a power point presentation missing the verbal explanation and Q&A. Each major point needs to incorporate a linear presentation that contains no extraneous points that are not also explained somewhere (by links). There is exactly one, thoroughly inadequate link, for about 25 points, none of which are explained in this way.
I don't mean to be too critical of busy experts contributing time, but writing requires taking time to be explicit in presentation - it is a discipline that is very worthwhile to command - and no matter how busy you are you should try and practice it.
As for possible dialect issues from non-native English speakers, I would just appreciate knowing what your native language is because there are structural issues it might help me understand, that otherwise will appear to be incomprehensible. Just a personal suggestion that I appreciate.
Other than that, the discussions are fragmentary, but I am digging them more than the article. -- Xgenei ( talk) 07:39, 28 September 2014 (UTC)
I believe that title of this article is wrong. The terminology used here should be "supervisory mode kernel" rather than a "monolithic kernel". The word monolithic means "made from a single stone" (ie a monolithic kernel is build in a monolithic fashion and is not composed of modules, in other words a monolithic kernel is the opposite of a modular kernel, which has the capability of loading modules.) —Preceding unsigned comment added by Markhobley ( talk • contribs) 08:44, 31 December 2009 (UTC)
If it is made up of modules, then it is modular, regardless of how the modules are arranged. Monolithic / Modular are terms describing structural build, rather than addressing methods, protection rings, etc. IMHO of course - Mark.
Golftheman says "It does not matter is the OS modular or not when it is in binary level. The OS architecture has not changed at all even then, it is still working as single binary. The modularity is in binary levele, not in architecture level."
This is all true, but modular / monolithic refers to architectural level, not the binary level. Monolithic means "made from a single stone", (ie not made up of modules). The kernel is modular (and modules can be added dynamically). A monolithic kernel would not be made of modules, and would require recompilation to include additional code.
86.183.106.50 ( talk) 16:30, 18 October 2010 (UTC)
My understanding of monolithic kernel is that it's about design/architecture related to kernel/user mode. The section called loadable modules is talking about something different: loading images at runtime. Why is there is a section about modularity in this document on monolithic kernel?
It confuses the heck out of me since commonly monolithic is the opposite of modularity. So one (me) might assume that there's a section about a modular kernel since it is the opposite of monolithic kernel. But in this case it's not. Kernels are monolithic, microkernel or hybrid; there is no modular. Well, they can be modular ... but in a different way. So confusing.
One way to clear this up is to say something like: the term 'monolithic' is used in two different ways for kernel. A kernel can also be monolithic (or modular) with respect to loading images at runtime. Therefore, a kernel can be both modular and monolithic even though those terms are opposites in general. Stevebroshar ( talk) 00:45, 22 May 2024 (UTC)
This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
Text like "A Monolithic kernel is a kernel architecture where the entire kernel is run in kernel space in supervisor mode." needs to be cleaned up. "entire kernel is run in kernel space " Kernel is suppose to be in Kernel Space. I think what it meant here is that apart from Kernel section, Device Driver and other modules like File system and security system, network system are also made part of the Kernel system. (May Be I am wrong .. but someone who knows better should update and clean this section.
Amberved ( talk) 15:27, 21 March 2008 (UTC)
-- Beland 21:32, 21 March 2007 (UTC)
The text is unreadable at the image's normal display size, and the image contains non-functional gradients and coloration. LokiClock ( talk) 04:44, 11 February 2010 (UTC)
In what respect is a monolithic kernel a more well-defined subject than monolithic code in general? Can the article be generalized? Also, how does "monolithic" compare to spaghetti code? While "monolithic" is not as pejorative, are they conceptually any different? Ham Pastrami ( talk) 12:22, 3 April 2008 (UTC)
This part is patently untrue.
I read in http://en.wikipedia.org/wiki/HP-UX that, it is also runs on monolithic kernel method. Does this OS also need to be added here ? Kanthaa ( talk) 11:56, 14 December 2008 (UTC)
Isn't Slackware simply a GNU/Linux distro? Or is there some sort of history behind it where did not use Linux? I don't think adding a bunch of Linux distros to be the most sane thing to do, even though the kernels are slightly different. -- SeyedKevin ( talk) 00:20, 23 October 2009 (UTC)
If you don't already know this material, and take the time to look here and elsewhere on the web, it would be impossible to cut through the morass of jargon. It is the worst example of technical writing that I have seen on Wikipedia in a long time.
Specifically I find the content is like a paragraph version of a power point presentation missing the verbal explanation and Q&A. Each major point needs to incorporate a linear presentation that contains no extraneous points that are not also explained somewhere (by links). There is exactly one, thoroughly inadequate link, for about 25 points, none of which are explained in this way.
I don't mean to be too critical of busy experts contributing time, but writing requires taking time to be explicit in presentation - it is a discipline that is very worthwhile to command - and no matter how busy you are you should try and practice it.
As for possible dialect issues from non-native English speakers, I would just appreciate knowing what your native language is because there are structural issues it might help me understand, that otherwise will appear to be incomprehensible. Just a personal suggestion that I appreciate.
Other than that, the discussions are fragmentary, but I am digging them more than the article. -- Xgenei ( talk) 07:39, 28 September 2014 (UTC)
I believe that title of this article is wrong. The terminology used here should be "supervisory mode kernel" rather than a "monolithic kernel". The word monolithic means "made from a single stone" (ie a monolithic kernel is build in a monolithic fashion and is not composed of modules, in other words a monolithic kernel is the opposite of a modular kernel, which has the capability of loading modules.) —Preceding unsigned comment added by Markhobley ( talk • contribs) 08:44, 31 December 2009 (UTC)
If it is made up of modules, then it is modular, regardless of how the modules are arranged. Monolithic / Modular are terms describing structural build, rather than addressing methods, protection rings, etc. IMHO of course - Mark.
Golftheman says "It does not matter is the OS modular or not when it is in binary level. The OS architecture has not changed at all even then, it is still working as single binary. The modularity is in binary levele, not in architecture level."
This is all true, but modular / monolithic refers to architectural level, not the binary level. Monolithic means "made from a single stone", (ie not made up of modules). The kernel is modular (and modules can be added dynamically). A monolithic kernel would not be made of modules, and would require recompilation to include additional code.
86.183.106.50 ( talk) 16:30, 18 October 2010 (UTC)
My understanding of monolithic kernel is that it's about design/architecture related to kernel/user mode. The section called loadable modules is talking about something different: loading images at runtime. Why is there is a section about modularity in this document on monolithic kernel?
It confuses the heck out of me since commonly monolithic is the opposite of modularity. So one (me) might assume that there's a section about a modular kernel since it is the opposite of monolithic kernel. But in this case it's not. Kernels are monolithic, microkernel or hybrid; there is no modular. Well, they can be modular ... but in a different way. So confusing.
One way to clear this up is to say something like: the term 'monolithic' is used in two different ways for kernel. A kernel can also be monolithic (or modular) with respect to loading images at runtime. Therefore, a kernel can be both modular and monolithic even though those terms are opposites in general. Stevebroshar ( talk) 00:45, 22 May 2024 (UTC)