In article <1992Aug28.171744.6460@rz.uni-karlsruhe.de> S_TITZ@iravcl.ira.uka.de (Olaf Titz) writes:
This isn't true - although the kernel is one big chunk of
code, it is subdivided into smaller modules, such as the VM
code, each one of the file systems, each device driver, etc. Some of these
modules have incestous relationships with eachother due to various
kludges and hacks, but this isn't necessary.
You do have to understand some basic "common" things used in the
kernel - ie, how the fs register points into user space, how
sleep/wakeup work, etc, but to say you have to understand the
whole kernel to write a device driver is a gross overstatement.
<deleted>
I agree too - 1.5 - 3M for a typical vendor's kernel is outrageous,
when it doesn't do anything that a generic 500K BSD or Linux kernel
can't do.
Blasphemy! There is nothing but the one true EMACS! :-)
--
Microsoft is responsible for propogating the evils it calls DOS and Windows,
IBM for AIX (appropriately called Aches by those having to administer it), but
marketing's sins don't come close to those of legal departments.
Boycott AT&T for their absurd anti-BSDI lawsuit.
Previous message: [thread] [date] [author] Next message: [thread] [date] [author]
Messages in current thread:
Re: RISC approach to OS - Re: GNU kids on the block?, Drew Eckhardt, (Fri Aug 28, 1:47 pm)