Linux and Solaris

Came across an article by Max Bruning [ The Solaris internals Guru ] on differences between Solaris and Linux.
Just noting down few points from the detailed article for quick reading later on.
For ppl interested in the complete article please refer to
http://www.opensolaris.org/os/article/2005-10-14_a_comparison_
of_solaris__linux__and_freebsd_kernels/

Linux
=========================================================================

1. Uses a Virtual File Switch mechanism for abstracting file system details from users
2. Inode is the file system indepent data struct
3. Default local file system is ext3fs .ext3fs is an extent based journalling fs
4. Uses LRU as a page replacement algorithm
5. Uses a pagedaemon called kswapd for page replacement
6. Basic unit of scheduling is task_struct
7. Processes and threads are rep by task_struct
8. A single-threaded process in Linux has a single task_struct
9. Scheduling decisions are based on priority :the "lower" the priority value, the better
10. Supports time-shared scheduling of threads
11. Favor interactive threads/processes. Interactive threads run at better priority than compute-bound threads, but tend to run for shorter time slices.
12. Debugging tool : gdb
    

Solaris :
=========================================================

1. Uses a Virtual File System mechanism for abstracting file system details from users
2. Vnode is the file system independent data structure
3. Default local file system is ufs
4. ufs is based on BSD Fast file system
5. Uses LRU as a page replacement algorithm
6. Uses a pagedaemon called pageout for page replacement
7. Each process is rep by proc_t and each thread in a process is rep by kthread_t structures
8. A single-threaded process in Solaris has a proc_t, a task_struct single kthread_t, and a klwp_t.
9. Scheduling decisions are based on priority: The "higher" the priority value, the better
10. Supports time-shared scheduling of threads
11. Favor interactive threads/processes. Interactive threads run at better priority than compute-bound threads, but tend to run for shorter time slices.
12. Kernel visibility tools : mdb,kdb,"Dtrace"