All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Filesystem module autoprobe?
Date: Tue, 24 Dec 2013 16:31:06 -0500	[thread overview]
Message-ID: <52B9FD1A.4060708@ubuntu.com> (raw)
In-Reply-To: <1387916547.2343.23.camel@dabdike.int.hansenpartnership.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 12/24/2013 03:22 PM, James Bottomley wrote:
> If you're expecting
> 
> mount /dev/sda1 /mnt
> 
> to insert all the available filesystem modules and discover that
> /dev/sda1 is ext2, this is a case of mismatched user expectations 
> (because we won't).

mount uses libblkid to identify the correct filesystem and tells the
kernel to use it.

> If
> 
> mount -t ext2 /dev/sda1 /mnt
> 
> isn't autoprobing, that's either a bug or a distribution problem.

So that *should* autoprobe?  Any pointers to some docs on how that is
supposed to work or where to start looking to figure out why it isn't?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJSuf0aAAoJEI5FoCIzSKrw7aUH/ir25B8lch2syfvPxY/k7x06
5j05rowEBpY6yhRtM7h2UmtzP6yJH8eVy2lBRnhHoURWFmNiCid9FAPOawn+bl1B
QLno+VPZpIaxuQ6mv0dBtq7EVzzPnpl3MR5Im+P6UabEmqfMlp6HFGBXIHYhJFSj
to2XXwxt4xrZo8GZxelVEGSjaYUx1FrRmPxoaH8KxBwY0kfDqaYDibC8flaWuFnT
W9WZdcy9BgURLt6eBRDN9Vk2EW05S64NiGNyGkGKZwHoQoWjLhTkGghmW9le+aui
bZxJl0cnjeNTfriNB5iVjMZOvJHO7Ui0AWwBGPUGI/XMx2DyDUEMi1wo+9TNQOQ=
=ibM2
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-12-24 21:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  3:34 Filesystem module autoprobe? Phillip Susi
2013-12-24 20:22 ` James Bottomley
2013-12-24 21:31   ` Phillip Susi [this message]
2013-12-24 23:31     ` James Bottomley

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=52B9FD1A.4060708@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-fsdevel@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 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.