Grub Development Archive on 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: Tue, 18 May 2010 14:50:32 +0200	[thread overview]
Message-ID: <106270877212158@192.168.2.69> (raw)
In-Reply-To: <4BF1B631.1030207@gmail.com>

Hi,

i sent this message 4 hours ago but it did
not show up yet. So i send it again on the risk
to produce a duplicate.

------------------------------------------------

While my local bzr upgrade problems still persist
i can view grub-mkrescue.in at 
  https://code.launchpad.net/~vcs-imports/grub/grub2-bzr


> xorriso -pathspecs on -as mkisofs

I would make this
  xorriso -report_about HINT -as mkisofs -graft-points

Option -report_about HINT will reduce verbosity
to the level of messages about unusual events
and remedy proposals.

Since xorriso is run in mkisofs emulation, it
seems clearer to use -graft-points rather than
xorriso option -pathspecs.


> -as mkisofs ${grub_mkisofs_arguments} --protective-msdos-label
> -o ${output_image} -r ${iso9660_dir} ${source}

The potential content of ${grub_mkisofs_arguments}
looks good so far.
I assume you have already tested your use cases.


There remain opportunities for result size
reduction:

The result will be up to 426 kB larger than the
one of grub-mkisofs. (Modern mkisofs or
genisoimage would give you 300 kB extra.)

------------------------------------------------

You may add mkisofs option
  -no-pad
to avoid trailing padding of 300 kB which is only
needed if you later burn the image to a CD in
write mode TAO.
Alternatively you could allow option -no-pad in
the option interpreter of grub-mkrescue rather
than issueing:
    -*) 
        echo "Unrecognized option \`$option'" 1>&2

The burn program can eventually add padding.
xorriso -as cdrecord will by default use write
mode SAO if the file size is detectable.

------------------------------------------------

Another 64 to 126 kB can be saved by hiding the
fact that the target is a random access file.
One would replace
    -o ${output_image}
by
    | cat >${output_image}
This deprives the result of the capability to
show on overwriteable media a table-of-content
with older sessions.

------------------------------------------------

In my tests the size reduced result was 4 kB
smaller than the result from grub-mkisofs.


Have a nice day :)

Thomas



  parent reply	other threads:[~2010-05-18 12:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-17 21:33 Migrations to xorriso Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-18  8:49 ` Thomas Schmitt
2010-05-18 12:50 ` Thomas Schmitt [this message]
2010-05-19 19:45 ` Thomas Schmitt
2010-05-19 21:23   ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-05-20  6:31     ` Thomas Schmitt
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19 12:01 Thomas Schmitt
2010-05-19 12:13 ` Colin Watson
2010-05-19 13:23   ` Thomas Schmitt
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
2010-05-20  9:30 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=106270877212158@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox