From: rct@gherkin.frus.com (Bob_Tracy)
To: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
Cc: system_lists@nullzone.org, linux-kernel@vger.kernel.org
Subject: Re: SEVERE Problems in 2.5.12 at uid0 access
Date: Wed, 1 May 2002 13:04:11 -0500 (CDT) [thread overview]
Message-ID: <m172ySZ-0005khC@gherkin.frus.com> (raw)
In-Reply-To: <3CD02C60.3030004@wanadoo.fr> "from Pierre Rousselet at May 1, 2002 07:56:48 pm"
Pierre Rousselet wrote:
> Bob_Tracy wrote:
> > Confirmed on a 2.5.11 system as well. Talk about your basic heart
> > attack! I'd just installed Postfix and found that I couldn't access
> > any of the directories under /var/spool/postfix. Fortunately (?),
> > I've got older kernels to fall back on, and that's one of the hazards
> > of running on the bleeding edge I reckon.
> >
> > Oh yeah... ext2 filesystem. I think this bug is at least mostly
> > independent of the filesystem type.
>
> The same here with 2.5.12 and ext2, have you run fsck on this fs ?
Yes, it's clean. Changing the owner of the inaccessible directory to
root allows you to "cd" into it and everything seems normal.
Alternatively, you can simply boot up on an older kernel and that takes
care of the problem too.
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next prev parent reply other threads:[~2002-05-01 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 11:14 system_lists
2002-05-01 17:06 ` Bob_Tracy
2002-05-01 17:56 ` Pierre Rousselet
2002-05-01 18:04 ` Bob_Tracy [this message]
2002-05-01 18:13 ` Skip Ford
2002-05-01 18:18 ` Alexander Viro
2002-05-02 21:39 ` Paul Larson
[not found] <Pine.GSO.4.21.0205011417230.12640-100000@weyl.math.psu.edu >
2002-05-01 18:57 ` system_lists
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=m172ySZ-0005khC@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre.rousselet@wanadoo.fr \
--cc=system_lists@nullzone.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
all inboxes | Powered by JetHome®