mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Toon van der Pas <toon@hout.vanvergehaald.nl>
To: Ali Bayazit <listeci@bayazit.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Judith und Mirko Kloppstech <jugal@gmx.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion for CD filesystem for Backups
Date: Mon, 7 Feb 2005 23:51:39 +0100	[thread overview]
Message-ID: <20050207225138.GC9850@hout.vanvergehaald.nl> (raw)
In-Reply-To: <1096003099.16849.16.camel@mevlevi>

On Fri, Sep 24, 2004 at 01:18:19AM -0400, Ali Bayazit wrote:
> 
> On Thu, 2004-09-23 at 17:16 +0100, Alan Cox wrote:
> > On Iau, 2004-09-23 at 00:04, Judith und Mirko Kloppstech wrote:
> > > Why not write a file system on top of ISO9660 which uses the rest of the 
> > > CD to write error correction. If a sector becomes unreadable, the error 
> > > correction saves the data. Besides, a tool for testing the error rate 
> > > and the safety of the data can be easily written for a normal CD-ROM drive.
> > > 
> > > The data for error correction might be written into a file so that the 
> > > CD can be read using any System, but Linux provides error correction.
> > 
> > Send patches, or possibly if you are dumping tars and the like just
> > write yourself an app to generate a second file of ECC data.
> 
> Wouldn't it be safer to do ECC on meta-data also?
> That probably means replacing ISO9660 though.

There seems to be a good user space alternative for this purpose:

	http://dvdisaster.berlios.de

Regards,
Toon.
-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

  reply	other threads:[~2005-02-07 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 23:04 Judith und Mirko Kloppstech
2004-09-23 16:16 ` Alan Cox
2004-09-24  5:18   ` Ali Bayazit
2005-02-07 22:51     ` Toon van der Pas [this message]
2004-09-23 18:40 ` Erik Hanson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050207225138.GC9850@hout.vanvergehaald.nl \
    --to=toon@hout.vanvergehaald.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jugal@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=listeci@bayazit.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®