On 06-Apr-00 Gustavo V G C Rios wrote: > Considering the current kernel design approach used by traditional > system, what happens if a drive were wrongly coded ? ^-- I assume you mean 'driver' > Would the entiry system crash ? It depends on the bug, sometimes you'll just spin forever, or end up keeping processes stuck in your driver etc.. Othertimes the system will panic (ie try to reference memory you shouldn't etc..) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: Is traditional unixes kernel r... Gustavo V G C Rios
- Re: Is traditional unixes kern... Kenneth Wayne Culver
- Re: Is traditional unixes kern... Nick Sayer
- Re: Is traditional unixes... Gustavo V G C Rios
- Re: Is traditional un... Andrew Reilly
- Re: Is traditional unixes kern... Ronald G. Minnich
- Re: Is traditional unixes kern... Wes Peters
- Re: Is traditional unixes kernel r... Warner Losh
- Re: Is traditional unixes kernel really stable ... Matthew Dillon
- Re: Is traditional unixes kernel really st... Alfred Perlstein
- RE: Is traditional unixes kernel really stable ... Daniel O'Connor
- RE: Is traditional unixes kernel really stable ... Yevmenkin, Maksim N, CSCIO
- Re: Is traditional unixes kernel really st... Gustavo V G C Rios
- Re: Is traditional unixes kernel reall... Ugen Antsilevitch
- Re: Is traditional unixes kernel r... David Holloway
- Re: Is traditional unixes kern... Wes Peters
- Re: Is traditional unixes kernel reall... Patryk Zadarnowski
- RE: Is traditional unixes kernel really stable ... Yevmenkin, Maksim N, CSCIO