From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Peter" Subject: Re: FEATURE Req: integrate badblocks check into fsck.reiser* Date: Fri, 1 Sep 2006 23:02:57 +0000 (UTC) Message-ID: References: <200609012250.44548.vs@namesys.com> <44F8B3C8.1050802@slaphack.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org Sender: news List-Id: Content-Type: text/plain; charset="us-ascii" To: reiserfs-list-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org On Fri, 01 Sep 2006 17:27:20 -0500, David Masover wrote: snip... >> both mkfs.reiserfs and fsck.reiserfs have -B option to accept list of >> bad blocks. We thought that should be enough. > > It really should. Why bother with a patch? Just write a wrapper script > that runs badblocks and passes in the list to mkfs. It was just a thought from userland. My perspective was that a user, not a hard-boiled geek, might get lulled into a false sense of security but may not have the wherewithal to write a wrapper. If nothing else, when the final doc is written (did I say final?:)), it should include a notice about not running badblocks. -- Peter +++++ Do not reply to this email, it is a spam trap and not monitored. I can be reached via this list, or via jabber: pete4abw at jabber.org ICQ: 73676357