kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How does the kernel chooses the 'vfat' module for fat32 partitions?
Date: Tue, 10 May 2011 21:35:45 +0700	[thread overview]
Message-ID: <BANLkTinRDZM_BrozJiPwe5ncqnMgpMZQ+w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimBGuFK_EGq8TcVX+nOet14dH7Vwg@mail.gmail.com>

Hi...

On Tue, May 10, 2011 at 14:47, Sudheer Divakaran
<inbox1.sudheer@gmail.com> wrote:
> 'mount' itself was responsible for guessing the vfat driver. Running
> mount with -v gave the following output


we both are partly correct, from "man mount":
" If no -t option is given, or if  the  auto  type  is  specified,
              mount  will try to guess the desired type.  Mount uses the blkid
              or volume_id library for guessing the filesystem type;  if  that
              does not turn up anything that looks familiar, mount will try to
              read the file /etc/filesystems, or,  if  that  does  not  exist,
              /proc/filesystems.   All  of  the  filesystem types listed there
              will be tried, except for those that are labeled "nodev"  (e.g.,
              devpts,  proc and nfs).  If /etc/filesystems ends in a line with
              a single * only, mount will read /proc/filesystems afterwards.
"

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

      reply	other threads:[~2011-05-10 14:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  4:48 How does the kernel chooses the 'vfat' module for fat32 partitions? Sudheer Divakaran
2011-05-10  6:40 ` Mulyadi Santosa
2011-05-10  7:08   ` Sudheer Divakaran
2011-05-10  7:47     ` Sudheer Divakaran
2011-05-10 14:35       ` Mulyadi Santosa [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=BANLkTinRDZM_BrozJiPwe5ncqnMgpMZQ+w@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).