From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: detecting squashfs volumes
Date: Wed, 08 Mar 2006 18:48:43 +0000 [thread overview]
Message-ID: <20060308184843.GA10049@vrfy.org> (raw)
In-Reply-To: <20060308165836.GA18525@danisch.de>
On Wed, Mar 08, 2006 at 09:07:18AM -0800, Greg KH wrote:
> On Wed, Mar 08, 2006 at 05:58:36PM +0100, Hadmut Danisch wrote:
> > Hi,
> >
> > I'd like to have CDROMs (and other block devices) with a squashfs
> > volume (not a squashfs file on a ISO filesystem) automatically mounted
> > when putting it into the drive, just with normal ISO cdroms.
> >
> > The main problem seems to be that vol_id does not detect anything
> > about squashfs volumes, no label, no UUID, no filesystem type. The
> > reasons seems to be squashfs itself, as far as I know it does not
> > contain any label or UUID.
> >
> > What would it take to have squashfs extended to support these
> > features? What would I have to tell the squashfs maintainer?
>
> This exact email would be a good start :)
Ok :)
http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=commitdiff;h/567dd62ede3cf979e426738925446f1182ba52
Kay
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-03-08 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 16:58 detecting squashfs volumes Hadmut Danisch
2006-03-08 17:07 ` Greg KH
2006-03-08 18:48 ` Kay Sievers [this message]
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=20060308184843.GA10049@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).