From: Karel Zak <kzak@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Francis Moreau <francis.moro@gmail.com>,
"Dale R. Worley" <worley@alum.mit.edu>,
util-linux@vger.kernel.org, gabeblack@chromium.org,
gwendal@chromium.org
Subject: Re: losetup on a image file containing (GPT) partition doesn't create partition devices
Date: Wed, 3 Dec 2014 17:10:29 +0100 [thread overview]
Message-ID: <20141203161029.GF1994@x2.net.home> (raw)
In-Reply-To: <547F22F7.30008@ubuntu.com>
On Wed, Dec 03, 2014 at 09:49:27AM -0500, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/3/2014 3:36 AM, Karel Zak wrote:
> > Yes, I don't like the idea with the ioctl workaround in losetup.
> > It's fine to use such workarounds in stable branches or in distro
> > specific patches, but I really don't want to use workarounds for
> > bugs in regular releases (master branch).
>
> Then again, maybe the whole idea of the kernel handling the partition
> table should be abandoned ( and the feature removed from the kernel )
> and losetup should just call partx and be done with it.
That's another story :-) And yes, I mostly agree.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-12-03 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 9:44 losetup on a image file containing (GPT) partition doesn't create partition devices Francis Moreau
2014-10-03 14:29 ` Dale R. Worley
2014-10-03 19:58 ` Dale R. Worley
2014-10-03 20:26 ` Francis Moreau
2014-10-04 19:35 ` Francis Moreau
2014-10-06 15:47 ` Dale R. Worley
2014-10-06 15:56 ` Francis Moreau
2014-10-27 20:16 ` Mike Frysinger
2014-12-02 19:29 ` Phillip Susi
2014-12-03 8:36 ` Karel Zak
2014-12-03 14:49 ` Phillip Susi
2014-12-03 16:10 ` Karel Zak [this message]
2015-02-16 8:52 ` Mike Frysinger
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=20141203161029.GF1994@x2.net.home \
--to=kzak@redhat.com \
--cc=francis.moro@gmail.com \
--cc=gabeblack@chromium.org \
--cc=gwendal@chromium.org \
--cc=psusi@ubuntu.com \
--cc=util-linux@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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.