unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements])
Date: Thu, 27 Apr 2017 19:08:40 +0200	[thread overview]
Message-ID: <20170427190840.79bcaa76@scratchpost.org> (raw)
In-Reply-To: <87k26afl07.fsf_-_@gmail.com>

>... -V gnu-disk-image /mnt/disk-image-partition-1.
> xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules

That's because all characters in an ISO 9660 volume identification need to be one of "ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_".

If you use more complicated labels you additionally need to support an extension like Joliet (which provides its own seperate directory tree in addition to the one of ISO 9660!).  It's easier to use uppercase letters only and not have a second tree.

See <http://wiki.osdev.org/ISO_9660>.

That page also describes how the disklabel looks:
- The first 32 KiB contain some non-ISO9660 stuff - it might be misdetected as something non-ISO9660 if you take it seriously.  So skip that.
- A sector has 2 KiB.
- The volume descriptors start at sector 16.
- There can be multiple volume descriptors.
- Each volume descriptor is one sector long.
- A volume descriptor can be either a boot record, a primary volume descriptor, a supplementary volume descriptor (for Joliet), a volume partition descriptor, or a volume descriptor set terminator.
- The list of volume descriptors have to be terminated by a volume descriptor set terminator.

- The primary volume descriptor contains the volume identifier at offset 40, length 32 Byte.

See also <http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-119.pdf>.

  parent reply	other threads:[~2017-04-27 17:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 14:17 GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements] ng0
2017-04-18 15:16 ` Chris Marusich
2017-04-19 20:59   ` Ludovic Courtès
2017-04-23  4:52     ` Chris Marusich
2017-04-24  5:11       ` GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements]) Chris Marusich
2017-04-27 13:42         ` GuixSD bootable ISO-9669 image Ludovic Courtès
2017-04-27 17:08         ` Danny Milosavljevic [this message]
2017-04-27 20:00           ` GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements]) Danny Milosavljevic
2017-04-28  8:18             ` Danny Milosavljevic
2017-05-02 12:37               ` GuixSD bootable ISO-9669 image Ludovic Courtès
2017-05-02 12:53                 ` ng0
2017-05-03  6:26                   ` Mark H Weaver
2017-05-02 20:09                 ` Danny Milosavljevic
2017-05-02 21:11                   ` Ludovic Courtès
2017-05-07 19:37                     ` Danny Milosavljevic
2017-05-08 14:14                       ` Ludovic Courtès
2017-05-11 23:30                         ` Danny Milosavljevic
2017-05-12 15:33                           ` Ludovic Courtès
2017-05-14 21:25                             ` Danny Milosavljevic
2017-05-16  8:31                               ` Ludovic Courtès
2017-06-06  9:35                                 ` Danny Milosavljevic
2017-06-08 12:25                                   ` Ludovic Courtès
2017-05-02 20:12                 ` Danny Milosavljevic

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20170427190840.79bcaa76@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).