From: John Cavan <johnc@damncats.org>
To: Manuel McLure <manuel@mclure.org>
Cc: Andrzej Krzysztofowicz <kufel!ankry@green.mif.pg.gda.pl>,
linux-kernel@vger.kernel.org
Subject: Re: Problem with "su -" and kernels 2.4.3-ac11 and higher
Date: Sun, 22 Apr 2001 23:01:33 -0400 [thread overview]
Message-ID: <3AE39B0D.9BA4413F@damncats.org> (raw)
In-Reply-To: <20010422102234.A1093@ulthar.internal.mclure.org> <200104222138.XAA00666@kufel.dom> <20010422192520.A3618@ulthar.internal.mclure.org>
Manuel McLure wrote:
> Did you try nesting more than one "su -"? The first one after a boot works
> for me - every other one fails.
I tried it with about a half-dozen nested and no problem. Mandrake
cooker here...
uname -a
Linux lion 2.4.3-ac11 #5 SMP Fri Apr 20 22:10:41 EDT 2001 i686 unknown
gcc --version
2.96
ls -l /lib/libc-*
-rwxr-xr-x 1 root root 1216268 Feb 21 05:38
/lib/libc-2.2.2.so
su --version
su (GNU sh-utils) 2.0
I don't think libc is the problem, unless it is in conjunction with the
compiler choice. Have you tried building the kernel with the updated Red
Hat gcc version? I know Mandrake has kept theirs current to Red Hat and
it works fine for me.
John
next prev parent reply other threads:[~2001-04-23 3:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-22 17:22 Problem with "su -" and kernels 2.4.3-ac11 and higher Manuel McLure
2001-04-22 21:38 ` Andrzej Krzysztofowicz
2001-04-23 2:25 ` Manuel McLure
2001-04-23 2:42 ` Brett
2001-04-23 3:20 ` Manuel McLure
2001-04-23 2:42 ` Wayne Whitney
2001-04-23 3:21 ` Manuel McLure
2001-04-23 5:05 ` Manuel McLure
2001-04-23 5:17 ` Albert D. Cahalan
2001-04-23 5:27 ` Wayne Whitney
2001-04-23 9:19 ` Alan Cox
2001-04-23 15:53 ` Bill Nottingham
2001-04-26 4:34 ` Ton Hospel
2001-04-23 3:01 ` John Cavan [this message]
2001-04-23 9:56 ` Andrzej Krzysztofowicz
2001-04-23 16:03 ` Lukasz Trabinski
2001-04-23 16:13 ` Lukasz Trabinski
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=3AE39B0D.9BA4413F@damncats.org \
--to=johnc@damncats.org \
--cc=kufel!ankry@green.mif.pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel@mclure.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