Re: libc6 utmp and wtmp [Was: Re: official C library]
In article <email@example.com>,
Johnie Ingram <firstname.lastname@example.org> wrote:
>"Michael" == Michael Meskes <email@example.com> writes:
>Michael> 1) utmp structure changed. I recompiled login for libc 6 so
>Michael> who works again. But I still have problems accessing it (for
>Michael> instance with procps) or writing it (for instance xterm). I
>Michael> take it all binaries that access utmp have to be recompiled.
>Am I correct in thinking the major players to be synchronized here are
>shellutils (who), sysvinit (last), netstd (rsh), login, ppp, procps,
>wu-ftpd, and ssh?
Well, if the program that uses utmp is wellbehaved and uses getutent()
and friends, we could put a libc6-utmp emulation in libc5.
Then you just let libc6 conflict with libc5 <= 5.4.23-6 so that installing
libc6 forces an install of a libc5 with the emulation layer.
There are some programs though that read/write utmp not using the
library interface. Usually you can find them by running strings on the
program and checking for /var/run/utmp.
I don't know what to do about those, but they should be fixed for libc6
anyway so maybe we can fix them, recompile for libc5 and put them in
Debian-1.3.x. The programs that write to utmp are the worst, those are
getty, in.rlogind, in.telnetd, pppd, sshd, rxvt, sessreg
>From my Debian-1.3 system:
init: /var/run/utmp [harmless]
telinit: /var/run/utmp [harmless]
| Miquel van Smoorenburg | "I need more space" "Well, why not move to Texas" |
| firstname.lastname@example.org | "No, on my account, stupid." "Stupid? Uh-oh.." |
| PGP fingerprint: FE 66 52 4F CD 59 A5 36 7F 39 8B 20 F1 D6 74 02 |
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .