public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Amit Dor-Shifer <amitds@oversi.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Re: Mounting squashfs fails
Date: Tue, 17 Nov 2009 12:26:27 +0200	[thread overview]
Message-ID: <4B027A53.8070805@oversi.com> (raw)

With respect to a/m post:

AFAIK, catalyst is using sys-fs/squashfs-tools from the hosting FS, not 
the one in the chroot.
Seems that there's always the potential of breaking the liveCD, when its 
kernel doesn't support the squashfs generated by catalyst.

Would be effective if catalyst performs the assertion that kernel & 
squashfs versions agree.

Even if the above is not favorable, I think catalyst should not depend 
on the hosting FS for generating an image. I assume a major design-goal 
of catalyst is to be as independent as possible from the hosting 
environment.

Perhaps catalyst can use a chrooted version of squashfs-tools (like it 
does w/portage). That would give users a good intervention point for 
overriding the version of squashfs-tools they want (by setting it in 
stage1.spec, livecd/packages).

Amit




                 reply	other threads:[~2009-11-17 12:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B027A53.8070805@oversi.com \
    --to=amitds@oversi.com \
    --cc=gentoo-catalyst@lists.gentoo.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