From: ashish mahamuni <ashitpro@yahoo.co.in>
To: Kernelnewbies <kernelnewbies@nl.linux.org>,
Rohit Sharma <imreckless@gmail.com>
Cc: ext4 <linux-ext4@vger.kernel.org>
Subject: Re: reading superblock
Date: Tue, 16 Sep 2008 09:47:27 +0530 (IST) [thread overview]
Message-ID: <756126.76299.qm@web94603.mail.in2.yahoo.com> (raw)
In-Reply-To: <2d08ef090809150941j3dbed8fah700aa5c9e886366@mail.gmail.com>
Hello Rohit,
I hope you are doing this for getting hand on ext2/ext3 file systems.
So what I'll suggest is try to read the on disk data structures and read the Super Block. That will really help you to understand some part of file systems instead relying on some existing functions.
I've posted one article regarding reading super block you can look at that...
http://bytes.com/forum/thread771405.html
Regards,
Ashish
--- On Mon, 15/9/08, Rohit Sharma <imreckless@gmail.com> wrote:
> From: Rohit Sharma <imreckless@gmail.com>
> Subject: reading superblock
> To: "Kernelnewbies" <kernelnewbies@nl.linux.org>
> Cc: "ext4" <linux-ext4@vger.kernel.org>
> Date: Monday, 15 September, 2008, 10:11 PM
> I want to read ext2 superblock and display the structure.
>
> which function do i need to call for that.
> is it ext2_get_sb() or ext2_fill_super() or both ??
>
> this is the function prototype:
> static int ext2_fill_super(struct super_block *sb, void
> *data, int silent)
>
> what are the parameters data and silent used for.
>
> --
> To unsubscribe from this list: send an email with
> "unsubscribe kernelnewbies" to
> ecartis@nl.linux.org
> Please read the FAQ at http://kernelnewbies.org/FAQ
Get an email ID as yourname@ymail.com or yourname@rocketmail.com. Click here http://in.promos.yahoo.com/address
prev parent reply other threads:[~2008-09-16 4:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 16:41 reading superblock Rohit Sharma
2008-09-16 4:17 ` ashish mahamuni [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=756126.76299.qm@web94603.mail.in2.yahoo.com \
--to=ashitpro@yahoo.co.in \
--cc=imreckless@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-ext4@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