All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: Migrations to xorriso
Date: Wed, 19 May 2010 15:23:26 +0200	[thread overview]
Message-ID: <106265329817470@192.168.2.69> (raw)
In-Reply-To: <20100519121335.GU21862@riva.ucam.org>

Hi,

> > - Option --diet saves about 400 kB of image
> >   size without losing much benefit.
> If it doesn't lose much,
> why would it not be the default?

Maybe one should revert the default and offer
an option
  --multi-session-toc
instead ?


>  Or, put another way, why would
> somebody want to turn this option off?

I could want a bootable multi-session backup
on USB stick with the opportunity to mount the
backup state of two weeks ago.
For that i'd start with a rescue system created
by grub-mkrescue, add my base backup as second
session and daily updates as further sessions.


The extra 64 kB to 126 kB make sure that the
older sessions of a multi-session ISO image can
be detected and mounted. Useful with incremental
backups on regular files, USB sticks, DVD+RW or
BD-RE media.
But not so much of interest with a single session
rescue image.

Without this extra space one can still add new
sessions but will always see the youngest one as
the only session of the image. (growisofs does
it that way.)
If the first session ends up on sequential media
(CD-R[W], DVD-R, DVD+R, BD-R) then further
multi-session will be managed by the drive
anyway.


> Useless use of cat.

Not in this case. xorriso calls fstat(2) to
determine the semantics of the given output file.
Option -o "${output_image}" or a redirection
by >"${output_image}" would both reveil type
S_IFREG.
But for the diet case i want S_ISCHR or S_IFIFO
so that the output "media" appears as sequential
rather than as overwriteable.


Have a nice day :)

Thomas



  reply	other threads:[~2010-05-19 13:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19 12:01 Migrations to xorriso Thomas Schmitt
2010-05-19 12:13 ` Colin Watson
2010-05-19 13:23   ` Thomas Schmitt [this message]
2010-05-19 21:02     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-19 18:40   ` Isaac Dupree
2010-05-19 19:34     ` Thomas Schmitt
2010-05-19 21:10       ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-19 21:35         ` Seth Goldberg
2010-05-19 21:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
  -- strict thread matches above, loose matches on Subject: below --
2010-05-20  9:30 Thomas Schmitt
2010-05-17 21:33 Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-18  8:49 ` Thomas Schmitt
2010-05-18 12:50 ` Thomas Schmitt
2010-05-19 19:45 ` Thomas Schmitt
2010-05-19 21:23   ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-20  6:31     ` Thomas Schmitt

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=106265329817470@192.168.2.69 \
    --to=scdbackup@gmx.net \
    --cc=grub-devel@gnu.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.