a friend of mine just sent me this email.  could you point me/him in the
correct direction??  i'll probably have him join th list.  but until then...

----FORWARDED MESSAGE----
> Am on the verge of putting BSD on machine with MFM drive,
> and am wondering about mapping bad blocks.
> 
> Some blocks are know bad, (mfgr's table).
> Some blocks are marked bad by norton under M$DOZE.
> Some blocks will go bad later.
> 
> Now what?
> 
> NetBSD provides bad144, which I recall from the ancient days
> of VMS. There is also a badsect thang, which maps bad blocks
> to a file, never to be seen again.
> 
> Three questions:
> 
> 1) what is the canonical procedure for doing this?
> 
> 2) Is there a repository of NetBSD FAQs, HOWTOs and so on?
> 
> 3) [not relevant, personal questions]
> 
> Dave

thanks,

-brian

-- 
** Brian Hechinger ** wonko@mail.arkham.net ** http://www.arkham.net **
--
"Yes, evil comes in many forms, whether it be a man-eating cow or
 Joseph Stalin, but you can't let the package hide the pudding!  Evil
 is just plain bad!  You don't cotton to it.  You gotta smack it in the
 nose with the rolled-up newspaper of goodness!  Bad dog!  Bad dog!"
                                --The Tick