From: Sergey Vlasov <vsu@altlinux.ru>
To: Wakko Warner <wakko@animx.eu.org>
Cc: Alan Jenkins <sourcejedi@phonecoop.coop>, linux-kernel@vger.kernel.org
Subject: Re: cd burning: kernel / userspace?
Date: Thu, 12 Aug 2004 16:37:32 +0400 [thread overview]
Message-ID: <20040812163732.7599de97.vsu@altlinux.ru> (raw)
In-Reply-To: <20040812001218.GA20341@animx.eu.org>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
On Wed, 11 Aug 2004 20:12:18 -0400 Wakko Warner wrote:
> > I'm not sure this is necessary. Can't you just do:
> >
> > # dump -0 -B 700000 -u -z3 /home -f -| cdrecord /dev/hdb -
> >
> > dump and cdrecord allow you to use "-" as a filename to indicate that
> > output shoud be written to stdout and input should be read from stdin
> > respectively.
>
> Yes, but if I was to understand it right, dump will close/reopen at "700000"
> (whatever that is, 700000kb?). That won't work with cdrecord since it's
> expecting a single input stream, not many seperated by a pause. I'd
> consider it more like using tar with the multiple tape option. When it is
> finished writing to a tape, it'll wait for the user to physically change
> tapes and start writing at the beginning of the new tape.
http://www.serice.net/shunt/ can arrange this.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-12 12:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 9:51 cd burning: kernel / userspace? Alan Jenkins
2004-08-10 22:05 ` Wakko Warner
[not found] ` <4119DFB0.6050204@phonecoop.coop>
[not found] ` <20040811164109.GA18761@animx.eu.org>
2004-08-11 21:03 ` Alan Jenkins
2004-08-11 21:33 ` Wakko Warner
2004-08-11 21:43 ` Alan Jenkins
2004-08-12 0:12 ` Wakko Warner
2004-08-12 9:07 ` Alan Jenkins
2004-08-12 12:37 ` Sergey Vlasov [this message]
2004-08-12 23:06 ` Kevin Fox
2004-08-13 0:13 ` Wakko Warner
2004-08-16 21:37 ` David Lang
2004-08-10 23:50 ` Valdis.Kletnieks
2004-08-16 20:47 ` Pavel Machek
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=20040812163732.7599de97.vsu@altlinux.ru \
--to=vsu@altlinux.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=sourcejedi@phonecoop.coop \
--cc=wakko@animx.eu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.