[FAQ] How is Linux Layered?


Recommended Posts

An excellent beginner's take on the display layers for Linux/GNU :)

I have some follow up questions though... for example, font rendering is something I would think is handled by the Desktop Environment, but it seems so consistent across all three desktop environments. How is this handled?

Another question -- how difficult is it to start with just the kernel, and build up a system to the Desktop Environment? I assume it is NOT a trivial task :)

Again, great job! Thanks!

An excellent beginner's take on the display layers for Linux/GNU  :)

I have some follow up questions though... for example, font rendering is something I would think is handled by the Desktop Environment, but it seems so consistent across all three desktop environments.  How is this handled?

Another question -- how difficult is it to start with just the kernel, and build up a system to the Desktop Environment?  I assume it is NOT a trivial task  :)

Again, great job!  Thanks!

585281741[/snapback]

X handles most of the font tasks, and actually most of the GUI tasks overall. Everything GUI-wise is built up on top of X and implements more features, such as GUI toolkits like GTK and QT. I'm not sure which handles anti-aliasing of fonts, X or the DE, but anti-aliasing seems different for each environment, so it's more than likely the DE.

I'm uncertain what you mean by your second question, whether you mean a base install and building of from there or building from scratch. The former is much easier than the latter, it's mostly just building some packages. The latter is much more involved and requires a lot of work since you're building everything. Check out LFS and look at the book there.

Here I think a word is missing: "The target audience for this is quite likely someone who is considering installing Linux for the first time, or who has installed it recently, but is having ______ understanding the variety of choices."

585300193[/snapback]

Good catch! (Y) I'll correct that now. :yes:

Such is the advantage of Open Source: Enough eyes, and every problem is shallow (to paraphrase Linus Torvald's quote)

  • 2 weeks later...
  • 4 weeks later...
interesting thread markjensen  :)

585541731[/snapback]

Thanks. Glad you found it interesting.

This gets asked a lot, and it tough for many newcomers to understand at first.

  • 3 months later...
Great guide mark, same for the other one's in this FAQ section...

this section is gold-dust, only just started looking at it..

586113058[/snapback]

Thanks. :)

Oh, and several of us Green Mods (fred66, rezza, Armeck and myself) have been working at getting the HOWTO & FAQs moved out to be more visible. Still in the works, though progress seems slow...

  • 3 years later...

Good post and does in fact help a lot in Understanding how Linux Works and what setting needs to be changed or adressed to do this or that ... Either way I'm not sure if this is the place to put this but since we are talking about layers I read on Wikipedia that there are Seven layers of an OS !! Right ?? I only counted Six !! And Is this model of WIndow Managers , Kernel , Etc ... apply on all Operating System like WIndows for Example and Leopard and so on

... but since we are talking about layers I read on Wikipedia that there are Seven layers of an OS !! Right ?? I only counted Six !! And Is this model of WIndow Managers , Kernel , Etc ... apply on all Operating System like WIndows for Example and Leopard and so on

I think you mean the OSI model for the seven layers. It has to do with communications, not Operating Systems.

Not sure if that is what you meant... :unsure:

I think you mean the OSI model for the seven layers. It has to do with communications, not Operating Systems.

Not sure if that is what you meant... :unsure:

This is basically it : http://wiki.answers.com/Q/7_layers_of_operating_system

I'm sure I read it on WIkipedia that this model is the seven layers of the operating system : hardware, firmware, kernel, memory manager, input output manager, file manager and application layer

It seems that this is in fact the OSI model also according to Wikipedia , What exactly is this and doesn't it apply to Operating Systems ??

PS : If I'm going off topic please feel free to ignore me , I don't want to derail such a brilliant post

OSI = Open Systems Interconnection, it's how different computers talk to each other.

As for the OS, that "layout" seems a bit strange, the memory manager and IO live in the kernel, not on top of it (unless we're talking about microkernel, but they add an extra 20 layers or so), and applications don't run on top of the file manager, they run along side it.

It seems that this is in fact the OSI model also according to Wikipedia , What exactly is this and doesn't it apply to Operating Systems ??

It's just someone who's misunderstood and thought the OSI model applies to operating systems. It doesn't, it deals with networking (and in a very academic way, compared to IP which does not follow the OSI model and is more practically designed).

OSI = Open Systems Interconnection, it's how different computers talk to each other.

As for the OS, that "layout" seems a bit strange, the memory manager and IO live in the kernel, not on top of it (unless we're talking about microkernel, but they add an extra 20 layers or so), and applications don't run on top of the file manager, they run along side it.

On Windows (sorry, I know it's a Linux thread) the layers are technically hardware abstraction layer->drivers/kernel (scheduling, synchronization, interrupt/exception handling)->executive (memory, IO, process/thread management, networking, etc)->subsystems->applications. With the exception of the applications, most of this runs in kernel mode, so it's not a microkernel architecture in the sense that everything above the kernel runs in user mode.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Dude get a clue, LTSC is Enterprise, not even legal for consumers, and ESU is not mainstream support cycle, just an extended security updates period.
    • Nvidia is your issue more so than linux itself. I did used it for a while with an old 1060 3gb, but using propietary drivers was kind of messy.
    • Qmmp 2.3.3 by Razvan Serea Qmmp (Qt-based MultiMedia Player) is a free, open-source audio player that delivers a classic music listening experience with a modern foundation. Inspired by the legendary Winamp, Qmmp features a familiar, customizable interface that supports both Winamp and XMMS skins, making it instantly recognizable to long-time users. It handles a wide variety of audio formats including MP3, OGG Vorbis, FLAC, WAV, AAC, and many others, ensuring smooth playback across diverse music libraries. In addition to basic playback, Qmmp offers advanced features such as a 10-band equalizer, crossfading, gapless playback, and audio visualization plugins. Users can manage playlists efficiently, create and save multiple lists, and even enable streaming from online sources. Plugin support extends the player’s capabilities, allowing integration of features like lyrics display, ReplayGain, and more. Built with the Qt framework, Qmmp runs smoothly and efficiently, making it ideal even for older systems. 10 great QMMP features you might not know: Global Hotkeys Support – Control playback using customizable system-wide keyboard shortcuts. CUE Sheet Support – Automatically detects and plays tracks from CUE files for full album playback. Last.fm Scrobbling – Integrated support for sending playback data to Last.fm. Audio CD Playback – Play music directly from audio CDs. Command Line Interface – Control Qmmp via command-line options for scripting or automation. System Tray Integration – Minimize to and control playback from the system tray. MPRIS Support – Integration with desktop media player controls via the MPRIS (Media Player Remote Interfacing Specification) interface. Spectrum Analyzer and Oscilloscope – Built-in visualizations for real-time audio feedback. Configurable Notifications – Custom pop-ups for track changes and playback status. Multiple Output Backends – Support for ALSA, PulseAudio, JACK, and more, offering flexible audio routing. Qmmp 2.3.3 changelog: fixed build with PipeWire versions less than 0.3.50; fixed settings dialog layout; fixed default CUE encoding; fixed possible null pointer dereference; fixed tracks order when added using drag and drop (2.3.3 only); fixed uninitialized structure usage; improved sid plugin: added libsidplayfp 3.0 support; added feature to build without residfp engine; fixed memory leak; fixed displaying audio information; updated Japanese translation (2.3.3 only). Download: Qmmp 64-bit | 24.0 MB (Open Source) Download: Qmmp 32-bit | 24.1 MB View: Qmmp Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • BATorrent 3.0.3 is out.
  • Recent Achievements

    • Rookie
      moog19 went up a rank
      Rookie
    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
  • Popular Contributors

    1. 1
      +primortal
      496
    2. 2
      PsYcHoKiLLa
      270
    3. 3
      Skyfrog
      75
    4. 4
      Steven P.
      68
    5. 5
      FloatingFatMan
      63
  • Tell a friend

    Love Neowin? Tell a friend!