Introduction to *nix¶
Module Overview¶
- The *nix architecture
- Getting around
- Command line editors - nano
- Command line editors - vim
- VSCode
The *nix Architecture¶

- OS is a resource manager
- Each layer provides an abstraction
- Confining scope and protection
A brief history of Linux¶
Hello everybody out there using minix –
I’m doing a (free) operating system (just a hobby, won’t be big and
professional like gnu) for 386(486) AT clones. This has been brewing
since april, and is starting to get ready. I’d like any feedback on
things people like/dislike in minix, as my OS resembles it somewhat
(same physical layout of the file-system (due to practical reasons)
among other things).
I’ve currently ported bash(1.08) and gcc(1.40), and things seem to work.
This implies that I’ll get something practical within a few months, and
I’d like to know what features most people would want. Any suggestions
are welcome, but I won’t promise I’ll implement them 🙂
Linus (torvalds@kruuna.helsinki.fi)
PS. Yes – it’s free of any minix code, and it has a multi-threaded fs.
It is NOT protable (uses 386 task switching etc), and it probably never
will support anything other than AT-harddisks, as that’s all I have :-(.
- Built in 1991 as a personal project
- Aims to be POSIX compliant
- Uses best of SysV and BSD
Distributions¶
Distributions target usage type/end user:
- Servers : RedHat Enterprise, Oracle Linux, Ubuntu Server, CentOS, Debian
- Desktop: Mint, ArchLinux, Fedora, Ubuntu Desktop
- Containers: Alpine, CoreOS, Photon OS
- Security: Kali, TAILS, Qubes