lkml.org 
[lkml]   [1998]   [Oct]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: wtmp problems (with "last")
Date
In article <cistron.Pine.LNX.3.96.981022115257.22930H-100000@ps.cus.umist.ac.uk>,
Riley Williams <rhw@bigfoot.com> wrote:
>Hi Andreas.
>
> > glibc2 which is used with RedHat 5.1 uses a different (larger) utmp
> > format than libc5. If you've got program that expect the libc5 utmp
> > format, you'll notice this corruption. Just upgrade those binaries.
> > When upgrading from a libc5 distribution to a glibc2 one, you
> > should also `rm wtmp' since the format has changed.
>
>This presumably explains the instabilities I noted in an earlier
>email, which appeared to be caused by a conflict between libc5 and
>glibc. At least I know what the problem was now - and that I was right
>to advise either not switching or switching completely...

This is all very dependant on whether your Distribution Maintainer
did a good job providing backwards compatibility. I've heard that
RedHat isn't very good in this respect, and that's what you are
talking about.

With for example Debian the backwards compatibility is very good,
libc5 programs using the library utmp functions can even read and
write the new libc6 UTMP format transparently. And there is a
complete libc5 development system.

So, before you make any generalizations ..

Mike.
--
"Did I ever tell you about the illusion of free will?"
-- Sheriff Lucas Buck, ultimate BOFH.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:45    [W:0.024 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site