From: michael chang <thenewme91@gmail.com>
To: sergey ivanov <seriv@parkheights.dyndns.org>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 problem with pam_mktemp
Date: Thu, 11 Aug 2005 20:42:57 -0400 [thread overview]
Message-ID: <b14e81f00508111742908cf55@mail.gmail.com> (raw)
In-Reply-To: <42FB3026.1050609@parkheights.dyndns.org>
On 8/11/05, sergey ivanov <seriv@parkheights.dyndns.org> wrote:
> I have not succeeded with integrating reiser4 & pam_mktemp.
> From one side I recompiled kernel with reiser4 patches modified to
> return ENOTTY for attempt to deal with attributes, as tmpfs does.
> Pam_mktemp does not work after this. So I returned to the kernel with
> original Namesys' patches.
> # strace -o su.log -fF su - seriv
> 1993 mkdir("/tmp/.private", 0711) = -1 EEXIST (File exists)
> 1993 lstat64("/tmp/.private", {st_mode=S_IFDIR|0711, st_size=7, ...}) = 0
> 1993 open("/tmp/.private", O_RDONLY) = 3
> 1993 ioctl(3, EXT2_IOC_GETFLAGS, 0xbf9e37f8) = -1 EISDIR (Is a directory)
> So it looks like reiser4 tries to be good and answer to ioctl
> getting/setting attributes "EEXIST" and "EISDIR",
> and not return error "ENOTTY".
This seems kind of confusing -- the problem with the idea that all
files are files and directories... do we really want to be returning
that it's a directory here? My guess is that this is the confusing
bit about this filesystem. AFAIK, this is probably confusing the PAM
code or whatever. *shrugs*
--
~Mike
- Just my two cents
- No man is an island, and no man is unable.
next prev parent reply other threads:[~2005-08-12 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 16:29 reiser4 problem with pam_mktemp sergey ivanov
2005-07-31 13:34 ` Vladimir V. Saveliev
2005-08-10 3:41 ` sergey ivanov
2005-08-10 12:14 ` Vladimir V. Saveliev
2005-08-11 11:01 ` sergey ivanov
2005-08-12 0:42 ` michael chang [this message]
[not found] ` <42FB2F04.7090003@parkheights.dyndns.org>
[not found] ` <42FC702D.8070802@namesys.com>
2005-08-12 10:55 ` sergey ivanov
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=b14e81f00508111742908cf55@mail.gmail.com \
--to=thenewme91@gmail.com \
--cc=reiserfs-list@namesys.com \
--cc=seriv@parkheights.dyndns.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.