From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Nanakos Chrysostomos <nanakos@wired-net.gr>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: superblock & inode's
Date: Tue, 26 Jul 2005 12:59:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0507261259010.31248@virtwinxp02.rdmcorp.com> (raw)
In-Reply-To: <40710.62.1.10.61.1122396787.squirrel@webmail.wired-net.gr>
On Tue, 26 Jul 2005, Nanakos Chrysostomos wrote:
> Hi all,
> i want to read the superblock & inode for a block device.
> I dont want to use readdir to get the inode and dir name.I want to do it
> like the skeleton below,can someone help me??
>
>
> #include <sys/types.h>
> #include <stdio.h>
>
> int main()
> {
>
> struct what_struct d; /* What struct to use for inode*/
> struct what_struct_sb sb; /*What struct to use for superblock */
> int fd;
>
> fd=open("/dev/hda1",0);
> lseek(fd,4096L,0); /* Is this the first inode?? Where is the next one?*/
> /*Where is the superblock allocated in the disk */
> read(fd,&d,sizeof(d));
> /*Retrieve information now ....*/
>
> return 0;
> }
your best bet is to get a copy of the kernel source and check out the
directory fs/ext3, particularly the source files super.c and inode.c.
rday
next prev parent reply other threads:[~2005-07-26 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 8:47 Unsigned off_t? Holger Kiehl
2005-07-25 8:53 ` Jeff Woods
2005-07-25 9:00 ` Holger Kiehl
2005-07-26 5:24 ` Glynn Clements
2005-07-26 7:38 ` Holger Kiehl
2005-07-26 16:53 ` superblock & inode's Nanakos Chrysostomos
2005-07-26 16:59 ` Robert P. J. Day [this message]
2005-07-27 5:21 ` sumit kalra
2005-07-27 7:24 ` Glynn Clements
2005-07-27 18:53 ` Nanakos Chrysostomos
2005-07-27 7:23 ` Unsigned off_t? Glynn Clements
2005-07-27 20:09 ` Holger Kiehl
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=Pine.LNX.4.63.0507261259010.31248@virtwinxp02.rdmcorp.com \
--to=rpjday@mindspring.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=nanakos@wired-net.gr \
/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).