Comment Re:Oh right. Silly me (Score 1) 142
How is it more friendly?
Lets say you write code that extends the OS's abilities.
Option A)
On QNX you write the resource manager (lets just call it that). Run it... opps, it crashed.
Run resource manager in debugger, and debug it.
Edit source. recompile. Run.
Don't want your resource manager anymore?
slay it off.
make more mods, run it again... you get the idea.
Option B)
On Linux. write the code. build the kernel with
your mods. reboot (ick). opps, it crashed (whole OS goes bye-bye). boot using alternate image.
Pull out *LOTS* of hair fixing the thing... you think.
rebuild kernel, reboot (and pray).
wash, rinse repeat...
Ok, you got it working the way you want. Don't want to use it right now... sorry - if you are going to use the sevices that code provides it must be omni-present. The only option is to boot between two versions of the kernel... one with one without the additional services.
Option C)
With QNX that piece of code is a seperate process which can be started and stopped as needed. It can also be watch dogged... if for ANY reason your resource manager (for want of a better name) terminates unexpectedly, it can be restarted and services restored quickly.
Option D)
Same code built into Linux kernel... if for any reason the code terminates unexpectedly (faults) --- BOOM!
So I'm curious... which options do you think are more friendly (pick any 2) ;-)
For stuff that you wouldn't link into the linux kernel, what does having the kernel source buy you? A deeper understanding of its inner workings? Which you shouldn't need if the kernel just works and does what it is supposed to do right?
Ok, I admit it -- I'm a little biased.
Lets say you write code that extends the OS's abilities.
Option A)
On QNX you write the resource manager (lets just call it that). Run it... opps, it crashed.
Run resource manager in debugger, and debug it.
Edit source. recompile. Run.
Don't want your resource manager anymore?
slay it off.
make more mods, run it again... you get the idea.
Option B)
On Linux. write the code. build the kernel with
your mods. reboot (ick). opps, it crashed (whole OS goes bye-bye). boot using alternate image.
Pull out *LOTS* of hair fixing the thing... you think.
rebuild kernel, reboot (and pray).
wash, rinse repeat...
Ok, you got it working the way you want. Don't want to use it right now... sorry - if you are going to use the sevices that code provides it must be omni-present. The only option is to boot between two versions of the kernel... one with one without the additional services.
Option C)
With QNX that piece of code is a seperate process which can be started and stopped as needed. It can also be watch dogged... if for ANY reason your resource manager (for want of a better name) terminates unexpectedly, it can be restarted and services restored quickly.
Option D)
Same code built into Linux kernel... if for any reason the code terminates unexpectedly (faults) --- BOOM!
So I'm curious... which options do you think are more friendly (pick any 2)
For stuff that you wouldn't link into the linux kernel, what does having the kernel source buy you? A deeper understanding of its inner workings? Which you shouldn't need if the kernel just works and does what it is supposed to do right?
Ok, I admit it -- I'm a little biased.
