Advanced Bash-Scripting Guide. Fault Management - OpenSolaris Information Resources. A Comparison of Solaris, Linux, and FreeBSD Kernels at OpenSolaris.org. In addition to the Oracle Technology Network (OTN) , developers and system administrators can find Oracle Solaris information on Twitter and Facebook and at the official Oracle Solaris blog . Available Solaris source can be viewed using the OpenGrok source browser . The majority of the source is distributed under an OSI-approved license. Code based on existing open source projects continues to be available under its current license(s). [*] The Caiman Project delivers installation technology. The IPS Project delivers the network-based Image Packaging System. [*] Many projects stopped publishing current source in August 2010 (including the ON (Operating System/Networking) project).
Therefore, some source available via the source browser is current (such as the Desktop and X11) and some is a snapshot from 2010 (such as ON), depending on the status of the particular project. Solaris vs freebsd vs linux. De eso va mas o menos interesante artículo que compara los kernels de solaris, freebsd y linux desde un punto de vista constructivo (que no es poco).
Algunas cosas son curiosas Solaris has support for a "fixed priority" class, a "system class" for system threads (such as page-out threads), an "interactive" class used for threads running in a windowing environment under control of the X server En Linux, Ingo Molnar propuso cosas parecidas (añadir algo que permitira marcar a las X & friends como "interactivos" para poder tratarlos de manera especial, o poner las X a prioridad -10 para olvidarse de los problemas). Linus lo rechazó frontalmente: In short, you're taking a very NT'ish approach - make certain programs run in the "foreground", and give them a static boost because they are magically more important. Linux divides machine-dependent layers from machine-independent layers at a much higher level in the software. Igual que esta. Microkernel. Structure of monolithic and microkernel-based operating systems, respectively Microkernels were developed in the 1980s as a response to changes in the computer world, and to several challenges adapting existing "mono-kernels" to these new systems.
New device drivers, protocol stacks, file systems and other low-level systems were being developed all the time. This code was normally located in the monolithic kernel, and thus required considerable work and careful code management to work on. Microkernels were developed with the idea that all of these services would be implemented as user-space programs, like any other, allowing them to be worked on monolithically and started and stopped like any other program. This would not only allow these services to be more easily worked on, but also separated the kernel code to allow it to be finely tuned without worrying about unintended side effects.
Although major work on microkernels had largely ended, experimenters continued development. Upstart: runlevel desde grub | Xinug.