From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "Bhattiprolu, Ravikumar (Ravikumar)" <ravikb@agere.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Magic Number for New File system
Date: Fri, 17 Dec 2004 03:51:11 -0500 [thread overview]
Message-ID: <41C29DFF.9060803@sun.com> (raw)
In-Reply-To: <6E1F4DB94568BB4AA8A30083E67378924BB67C@iiex2ku01.agere.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bhattiprolu, Ravikumar (Ravikumar) wrote:
> Hi All,
>
> We are planning to write a new file system for our requirements. Is
> there any standard way to allocate a magic number for this new file
> system?
Have a cat walk across your numpad. The value is pretty meaningless
other than as a unique identifier for your fstype. See statfs(2) for a
list of known MAGIC numbers.
> Also how to go about writing the new file system?
>
For a block device backed fs, see fs/minix/* for a simple enough
example. Another good example for a much simpler fs is fs/ramfs/inode.c
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBwp3/dQs4kOxk3/MRAnR0AJ4vOWqcG6L192xmsaO3w03Vc5qQhACbBthn
IDjz1oO7q0mofmP1uuitv/E=
=u+W+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-17 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 6:12 Magic Number for New File system Bhattiprolu, Ravikumar (Ravikumar)
2004-12-17 8:51 ` Mike Waychison [this message]
2004-12-18 2:39 ` Theodore Ts'o
2004-12-18 19:53 ` Phil Lougher
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=41C29DFF.9060803@sun.com \
--to=michael.waychison@sun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravikb@agere.com \
/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