All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joe Harrington" <jharring@micron.net>
To: "CSCD 440-01 Mailing List" <cs440@tux.ewu.edu>
Cc: <linux-kernel@vger.kernel.org>
Subject: filesystems
Date: Wed, 22 Nov 2000 00:26:22 -0800	[thread overview]
Message-ID: <007d01c0545d$e6444760$53b613d1@micron.net> (raw)

Does a typical Linux system or Mandrake boot using the ext2 filesystem? Do
all filesystems have or use commands such as stat, read, write and chmod. I
am trying to figure out without looking through the code how a VFS
filesystem works. I am assuming that it does not use the major minor system,
for faster access to data? On my system I have:

            ext2
            msdos
nodev proc

Yes I did a man filesystems, man virtual filesystems, and manVFS. What does
the nodev stand for? I have seen other systems containing filesystems such
as:

            ext2
            minix
            msdos
            vfat
nodev proc
nodev nfs
            iso9660
            ufs
nodev autofs
nodev devpts

Basically, do you mount a VFS filesystem, does it keep pages in RAM longer
than other filesystems. How would a VFS filesystem handle system calls such
as "stat" or "open"? I am just looking for something that can easily help me
visualize the VFS process.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-22  8:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  8:26 Joe Harrington [this message]
2000-11-22  9:34 ` filesystems Tigran Aivazian
2000-11-22  9:51   ` filesystems Tigran Aivazian
  -- strict thread matches above, loose matches on Subject: below --
2001-05-03  8:22 filesystems Jure Menart

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='007d01c0545d$e6444760$53b613d1@micron.net' \
    --to=jharring@micron.net \
    --cc=cs440@tux.ewu.edu \
    --cc=linux-kernel@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.