From: unruh on
["Followup-To:" header set to comp.os.linux.misc.]
On 2009-12-31, Douglas Mayne <invalid(a)invalid.com> wrote:
> On Sun, 20 Dec 2009 02:24:34 +0000, no.top.post wrote:
>
>> On my old system, I've only just figured out how to backup a tree by:--
>>
>> mkisofs -R /mnt/p6/usr/lib | cdrecord -v fs=6m speed=2 dev=0,0 -
>>
>> Obviously I'd rather not have small [10% of CD capacity] dir-trees on
>> each CD, so I'd want to serially write several dir-trees to the same CD.

Why not? those CDs are only 25 or 50 cents each. Your time is worth much
more than that.

>>
>> Apparently the above instruction does:
>> <read the tree & convert it> AND_THEN <write the converted data to CD>
>> So then the 2nd step would start writing from the CD beginning ?

You can, you know, put more onto the mkisofs command.
mkisofs -R /mnt/p6/usr/{lib,bin} /var/spool/mail /mnt/p2/apple |cdrecord ...
>>
>> But this is too simplistic since it's seen from the
>> messages-while-running that a fifo is repeatedly written and read.
>>
>> So how can I read multiple dir-trees and write them to the CD ?

man mkisofs

>>
>> == TIA
>>
> IME, data written to a CD needs to be "staged" in some way. The staging

No. the staging in his example is done by a pipe.

> directory provides the top-level directory structure for the final CD.
....
From: Michael Black on
On Thu, 31 Dec 2009, unruh wrote:

> ["Followup-To:" header set to comp.os.linux.misc.]
> On 2009-12-31, Douglas Mayne <invalid(a)invalid.com> wrote:
>> On Sun, 20 Dec 2009 02:24:34 +0000, no.top.post wrote:
>>
>>> On my old system, I've only just figured out how to backup a tree by:--
>>>
>>> mkisofs -R /mnt/p6/usr/lib | cdrecord -v fs=6m speed=2 dev=0,0 -
>>>
>>> Obviously I'd rather not have small [10% of CD capacity] dir-trees on
>>> each CD, so I'd want to serially write several dir-trees to the same CD.
>
> Why not? those CDs are only 25 or 50 cents each. Your time is worth much
> more than that.
>
Sure, and I have loads of floppies sitting around, some a quarter of a
century old, and yet virtually none of them are full. In trying to
"organize" them, I'd start a new floppy for some specific use, or I'd
buy some shareware or freeware floppy and it was relatively empty. Yes,
they are cheap, but they take up space.

It's the same with CDROMs, the cost isn't the factor, but they can really
accumulate if you don't put much on each.

Michael
From: Douglas Mayne on
On Thu, 31 Dec 2009 19:05:00 +0000, unruh wrote:

> ["Followup-To:" header set to comp.os.linux.misc.] On 2009-12-31,
> Douglas Mayne <invalid(a)invalid.com> wrote:
>> On Sun, 20 Dec 2009 02:24:34 +0000, no.top.post wrote:
>>
>>> On my old system, I've only just figured out how to backup a tree
>>> by:--
>>>
>>> mkisofs -R /mnt/p6/usr/lib | cdrecord -v fs=6m speed=2 dev=0,0 -
>>>
>>> Obviously I'd rather not have small [10% of CD capacity] dir-trees on
>>> each CD, so I'd want to serially write several dir-trees to the same
>>> CD.
>
> Why not? those CDs are only 25 or 50 cents each. Your time is worth much
> more than that.
>
Note: I am not the OP. I assume your comment is directed to him.
(Personally, I use optical media to hold an encrypted loopback
filesystems which nearly consumes the disc capacity in a single session.)
>
>
>>> Apparently the above instruction does:
>>> <read the tree & convert it> AND_THEN <write the converted data to
>>> CD>
>>> So then the 2nd step would start writing from the CD beginning ?
>
> You can, you know, put more onto the mkisofs command. mkisofs -R
> /mnt/p6/usr/{lib,bin} /var/spool/mail /mnt/p2/apple |cdrecord ...
>
The problem with that syntax is the directory structure "merges" together
for all appended args. Again, I am not the OP, but it wouldn't be useful
to me in a backup context. The staging directory is necessary to keep
them from merging. YMMV.

>>>
>>> But this is too simplistic since it's seen from the
>>> messages-while-running that a fifo is repeatedly written and read.
>>>
>>> So how can I read multiple dir-trees and write them to the CD ?
>
> man mkisofs
>
>
>>> == TIA
>>>
>> IME, data written to a CD needs to be "staged" in some way. The staging
>
> No. the staging in his example is done by a pipe.
Ok, but see comment above.
>
>
>> directory provides the top-level directory structure for the final CD.
> ...
Note: comments inline.

--
Douglas Mayne