From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org
Cc: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
Subject: Re: new mount regression
Date: Fri, 16 Nov 2012 10:36:15 +0100 [thread overview]
Message-ID: <20121116093615.GA20338@x2.net.home> (raw)
In-Reply-To: <20121114231031.GB20303@altlinux.org>
On Thu, Nov 15, 2012 at 03:10:31AM +0400, Dmitry V. Levin wrote:
> > Also new mount understands fstype list in options:
> >
> > $ mount -t vfat,hfsplus,ext4,ext3,ext2 /dev/loop0 /media
>
> Already reported with a patch in
> http://marc.info/?l=util-linux-ng&m=134876452206541
> The patch was labelled a hack and rejected in
> http://marc.info/?l=util-linux-ng&m=134910609108013
> but no better alternative is available so far.
I have applied the Gleb's patch as I did not found a better
(less invasive) solution.
Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-11-16 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 20:04 new mount regression Alexey Gladkov
2012-11-14 23:10 ` Dmitry V. Levin
2012-11-16 9:36 ` Karel Zak [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=20121116093615.GA20338@x2.net.home \
--to=kzak@redhat.com \
--cc=glebfm@altlinux.org \
--cc=util-linux@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).