From: Marcos Dione <mdione@grulic.org.ar>
To: linux-fsdevel@vger.kernel.org
Subject: 'Not a directory'
Date: Sun, 26 May 2002 23:18:40 -0300 [thread overview]
Message-ID: <20020527021840.GD856@tempest.styx.org.ar> (raw)
I'm playing with a new fs developed by myself. I reached the stage
where I can mount the fs and even read the root's inode. but when I
try to cd into de mountpoint, chdir(2) complais that 'Not a directory'.
doing a 'ls -l' I see that the mountpoint has the mode, dates and
size of the directory being mounted. the mode is 040755, so I don't
see the problem. also, using ramfs as reference, I note that the
directory is not inspected in any way, so I think that is not a
problem if I didn't developed the super, inode and file ops *yet*.
also, I would *really* appreciate any link to any docs about
implementing filesystems for linux (e.g., what should all the *_ops
functions must do, return, etc., which should be reimplemented or
which could be ignored or even use the generic_* ones, and so on)
best regards.
next reply other threads:[~2002-05-27 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 2:18 Marcos Dione [this message]
2002-05-27 6:48 ` 'Not a directory' Jan Hudec
2002-05-27 7:28 ` Anton Altaparmakov
2002-05-28 17:51 ` Greg KH
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=20020527021840.GD856@tempest.styx.org.ar \
--to=mdione@grulic.org.ar \
--cc=linux-fsdevel@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