Date: Sat, 9 Jan 2010 20:45:27 +0100 From: Ed Schouten <ed@80386.nl> To: Scott Long <scottl@samsco.org> Cc: FreeBSD Arch <arch@freebsd.org> Subject: Re: Replacing <utmp.h> with <utmpx.h> Message-ID: <20100109194527.GX64905@hoeg.nl> In-Reply-To: <B9E71A45-2FE2-4280-9B1C-E52F80D583BE@samsco.org> References: <20100109120444.GW64905@hoeg.nl> <B9E71A45-2FE2-4280-9B1C-E52F80D583BE@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--yRmRcZUEmv8Gpn4q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Scott Long <scottl@samsco.org> wrote: > Does this have any implications for the compat4x/5x/6x/7x/8x > libraries that we ship? Also, what legacy apps that are statically > compiled and touch utmp/wtmp? Well, the issue is that nothing right now compiles against utmp/wtmp/etc. <utmp.h> just provides a set of structures for the applications to use, no actual symbols. All applications just tinker with the files themselves, so there is no difference between dynamic and static linkage here. Nothing in libc uses <utmp.h> or its database files. There are three functions in libutil that do that, namely login(3), logout(3) and logwtmp(3). These functions are not present in my branch, because they are hardly implementable on top of utmpx. This means I am going to increment libutil's major and let it be the way it is. I decided to just give up on trying to be compatible, because there is hardly anything we can do. --=20 Ed Schouten <ed@80386.nl> WWW: http://80386.nl/ --yRmRcZUEmv8Gpn4q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAktI3NcACgkQ52SDGA2eCwXrKQCfWTlcAJyJ+Z12FFCV13iIpSBv wyIAn24N92ydg35VDqQ2u0DEarf/2dmL =wCQ8 -----END PGP SIGNATURE----- --yRmRcZUEmv8Gpn4q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100109194527.GX64905>