Skip to main content

Major Linux Vs UNIX Kernel Differences


UNIX has been regarded as the mother of most of the operating systems. Some of the popular members of this family Include :
  • System V Release 4(SVR4) developed by AT&T.
  • 4.4 BSD From university of California
  • AIX from IBM.
  • HP-UX from Hewlett-Packard.
  • Solaris from Sun Microsystems.

Linux is relatively a new member of this family. Linux was initially written by Linus Torvalds in 1991 for IBM compatible personal computers. As an OS, GNU Linux has experienced huge success and popularity in last 20 years with most of the commercial servers now using GNU Linux. To add to the popularity, end users have also started using Linux these days with most of the popular Laptop and PC manufactures giving GNU Linux as a per-installed OS.
For those who are still confused between Linux being an OS or kernel, Linux in true sense as written by Linus was a kernel that was written by referring to book on Unix internals (Though the Linux kernel has adopted good features from many other Unix like kernels too) while the commercially available distributions that contain utilities like graphical desktop, text editors, compilers etc on top of the Linux kernel are complete operating systems.
Though Linux Kernel borrows most of its features from Unix/Unix-Like kernels but still there are many points where the two type of kernels differ significantly. In this article, the main focus will be on these differences. The list is not exhaustive but contains the main differences.

1. Monolithic Vs Micro-kernel Approach

Monolithic kernels are those where all the kernel code runs as a single process while Micro-kernel kernels are those where the core of a kernel (that controls the different pieces of OS) runs in one process while other services like device drivers etc run as different processes. Linux follows monolithic approach while there are a couple of exceptions in Unix-Like kernels that follow Micro-kernel approach.

2. Adding/Removing features to kernel

While traditional Unix/Unix-like systems require static linking of new modules being added, Linux supports a powerful feature where-in kernel components like device drivers etc can be loaded and unloaded dynamically. This feature is known as Loadable kernel modules (LKM). Any new component can be added/removed as an LKM to the kernel. This means there is no need to compile the whole kernel again. Also, if a component is not needed, it can easily be unloaded. This feature makes Linux kernel very flexible.

3. Kernel Threading

Many Unix-Like kernels are organized as a set of kernel threads. A kernel thread can be thought of as an independent execution flow. A kernel thread can run user process or some kernel code. The basic Idea is to do context switches between the kernel threads which is less expensive than context switches between processes as threads operate in same address space. While many Unix-Like OS use kernel threads for process context switching, Linux uses kernel threads only for executing some kernel code periodically.

4. Multi-threaded application support

Almost all modern OS, be it Unix-Like or Linux distributions, support multi-threading. A multi-threaded application is one which creates more than one execution flows. These independent execution flows are known as threads. Threads are light weight processes. In most of the Unix-Like systems, light weight processes are based on kernel threads while in Linux these LWP are created by a call to function clone() which lets the application to create a separate process like fork() does but the difference being that with clone() the newly generated process can share its physical memory, opened files, address space etc. As these newly created process works in a shared environment, so they are given a different name ‘threads’. So we see that Linux and Unix/Unix-Like differ in the way multi-threaded environment is handled internally.

5. STREAMS

Streams I/O subsystem is included in most of the Unix kernels and has become a preferred interface for writing device drivers, terminal drivers etc. While on the other hand there is nothing like Streams in Linux.

6. Preemptive Vs Non-Preemptive Kernels

Preemptive kernels are the kernels which can preempt the currently executing process. It means that a process which is currently executing can be forcibly interrupted if a process with higher priority is ready for execution. On the other hand, Non preemptive kernels are those where a running process cannot be forcibly interrupted even if a higher priority process is ready for execution. Normally, Linux OS are Non preemptive while some of the Unix systems like Solaris 2.x etc are fully preemptive. Usually Real time OS have fully preemptive kernels. These days we have Linux Real time OS which have fully preemptive kernels.
So we see that though Linux was born out of the basic idea from Unix but still it differs from Unix/Unix-Like kernels in many ways. Despite of these differences Linux still inherits a lot from Unix and is still considered as a member of Unix family of kernels.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,