Rick Moen wrote:
>> The point is that _some_ of this is not. But thank you for raising
> the matter of filesystem (and block-device) drivers: Increasingly,
> we _are_ starting to see measures to have these in userspace,
> specifically to protect core system functionality against problems in
> their code.
>
I'm not sure if I want my system to keep ticking over if something as
vital as block devices start going a bit wobbly. I think if there's a
chance of data corruption I'd prefer my kernel to panic and sieze up :)
To use an entirely inappropriate car analogy (I'm gunning for a CEO
position) would you like your engine to keep going if you steering
stopped working?
Or maybe the BBC tech reporting route? The Drive C is like the long term
memory of the computer. This is where the computer's emotions and
instincts are "stored". If this crashes (a term coined by Microsoft
during their invention of the world wide internetweb meaning "to become
pooched") then the computer can be prone to a breakdown.
How about Star Trek? "They're corrupting the data buffers! If we can
shift them off primary systems and relign the dilithium matrix so it can
be isolated we... just... might... be able to save the ship!"
"Like running block device modules in user space!"
"Exactly."
/me cuts down on the coffee.
--
ICQ:139064407 Jabber:fuzzbucket at jabber.org Yahoo:rapidyokes
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!