mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: Strange behavior observed w.r.t 'su' command
Date: Fri, 28 Nov 2003 10:54:14 +0100	[thread overview]
Message-ID: <yw1xad6g3jjt.fsf@kth.se> (raw)
In-Reply-To: <20031128093929.13486.qmail@web40909.mail.yahoo.com>

Bradley Chapman <kakadu_croc@yahoo.com> writes:

> Confirmed. I have a Red Hat 9 system running 2.6.0-test11 with glibc
> 2.3.2-82 and coreutils 4.5.3-19.0.2. Killing su with SIGKILL does
> put the keyboard into unbuffered mode and does alternate the
> prompts. No error messages appear in dmesg.

Does anyone know why redhat keeps doing these strange modifications?
Over the years, I've encountered quite a few problems caused by redhat
messing things up.  A few examples:

- gcc 2.96
- A rather recent redhat version shipped with a broken 'sort'
  command.  It performed a seemingly random permutation.
- Redhat 9 perl doesn't treat rexexps the same way a clean perl of the
  same version does.

Anyway, I guess it could be over soon, if only people would understand
to stay away from that fedora stuff.

-- 
Måns Rullgård
mru@kth.se


  reply	other threads:[~2003-11-28  9:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-28  9:39 Bradley Chapman
2003-11-28  9:54 ` Måns Rullgård [this message]
2003-11-28  9:59 ` Raj
  -- strict thread matches above, loose matches on Subject: below --
2003-11-28  8:30 Raj
2003-11-28  9:15 ` Måns Rullgård
2003-11-28 10:57   ` Tim Cambrant
2003-11-28 10:54     ` Andre Tomt
2003-11-28 10:33 ` Andreas Schwab
2003-11-28 10:47   ` Måns Rullgård
2003-11-28 10:53     ` Andreas Schwab
2003-11-28 11:11       ` Måns Rullgård
2003-11-28 11:56         ` Andreas Schwab
2003-11-28 11:22       ` Raj
2003-11-28 11:52         ` Andreas Schwab

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=yw1xad6g3jjt.fsf@kth.se \
    --to=mru@kth.se \
    --cc=linux-kernel@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

Powered by JetHome