This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [PATCH] ppc64 utmp changes
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Martin Schwidefsky <schwidefsky at de dot ibm dot com>
- Cc: Roland McGrath <roland at redhat dot com>, aj at suse dot de, Steve Munroe <sjmunroe at us dot ibm dot com>, bcollins at debian dot org, libc-alpha at sources dot redhat dot com
- Date: Tue, 1 Oct 2002 16:55:46 +0200
- Subject: Re: [PATCH] ppc64 utmp changes
- References: <OF661DDA68.9402585C-ONC1256C45.00441893@de.ibm.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Tue, Oct 01, 2002 at 03:05:30PM +0200, Martin Schwidefsky wrote:
>
> > For sparc64 it can be changed without versioning, Ben, do you agree?
> > For x86-64, as Andreas said, I believe everybody can recompile glibc
> > and recompile those few programs which access wtmp etc. files directly
> > (SysVinit, anything else?) and > /var/log/wtmp.
> > ppc64 initiated this, so is ok with this change too.
> > The only question is s390x, Martin?
>
> Hmm, I checked utmp.h and utmpx.h on a 31 bit system 64 bit system. The
> files are identical but the structures have a different layout (__time_t
> and __suseconds_t have type unsigned long -> 4 vs. 8 byte). This makes
> the /var/log/wtmp format different on 31bit vs. 64bit. So 31 bit programs
> running on 64 bit may not access /var/log/wtmp. To make things worse we
> already have a 64 bit distro out there so we can't simply change utmp.h.
> Now it depends which programs do access /var/log/wtmp. For the standard
> stuff in a distribution we always use the 64 bit versions of the programs.
I was afraid of that :(.
Below is a partial list of packages on my box which probably do direct wtmp access
on my box:
adjtimex-1.13-4
comsat-0.17-6
dhclient-3.0pl1-7
dhcp-3.0pl1-7
dos2unix-3.1-12
dump-0.4b28-4
ethereal-0.9.5-3
ethereal-gnome-0.9.5-3
gkrellm-1.2.13-1
gnome-libs-1.4.1.2.90-20
gnome-terminal-2.0.1-2
hanterm-xf-2.0.0-6
isdn4k-utils-3.1-58
kdebase-3.0.3-3
kterm-6.2.0-30
lynx-2.8.5-7
mars-nwe-0.99pl20-10
mgetty-1.1.28-7
mgetty-voice-1.1.28-7
mingetty-1.00-3
mozilla-nss-1.0.1-15
ncpfs-2.2.0.18-11
openssh-server-3.4p1-2
ppp-2.4.1-7
procps-2.0.7-25
psacct-6.3.2-23
rpm-4.1-0.87
rsh-server-0.17-10
rwho-0.17-16
samba-2.2.5-8
samba-client-2.2.5-8
samba-common-2.2.5-8
samba-swat-2.2.5-8
screen-3.9.11-10
sh-utils-2.0.12-2
SysVinit-2.84-5
talk-server-0.17-17
tcsh-6.12-2
telnet-server-0.17-23
tetex-latex-1.0.7-56
utempter-0.5.2-10
util-linux-2.11r-9
wu-ftpd-2.6.2-7
XFree86-4.2.0-65
zsh-4.0.4-8
Given the size of this list, I'm afraid the chance of third party packages
doing wtmp access is extremely high.
Jakub