From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Cc: Justin <exitworld@tutanota.com>
Subject: Re: utmp.h
Date: Fri, 27 Dec 2019 05:53:15 -0600 [thread overview]
Message-ID: <cfe9053d-82d0-08f9-35ad-9bfaf68041d3@adelielinux.org> (raw)
In-Reply-To: <Lx4FQb8--3-2@tutanota.com>
[-- Attachment #1.1: Type: text/plain, Size: 1330 bytes --]
On 26/12/2019 20:49, exitworld@tutanota.com wrote:
>
> I believe the paths to utmp and wtmp are defined wrong in utmp.h. Right
> now they are defined in dev/null, when they should be /var/run/utmp and
> /var/log/wtmp. Please see man utmp(5) and the FHS 5.10.2 and 5.13.2
>
> you can respond if you'd like
>
> thank you,
> justin
Hi there Justin,
musl does not implement the utmp/wtmp family of functions itself[1]; it
only provides stubs so that software that uses them can build (but those
functions requiring utmp/wtmp will not work).
For full operation with the utmp(x) functions, you will need to use
something like skarnet's utmps[2], which implements these functions in a
secure manner. Right now, there are only two distributions which offer
utmps: Adélie and NixOS. I am not sure how well-integrated utmps is in
to NixOS, but at Adélie we have fully integrated it and all packages
that utilise the utmp functions work fully as intended.
I hope this helps.
Best,
--arw
[1]:
https://wiki.musl-libc.org/faq.html#Q:-Why-is-the-utmp/wtmp-functionality-only-implemented-as-stubs?
(though we at Adélie, obviously, disagree with the rationale)
[2]: https://skarnet.org/software/utmps/
--
A. Wilcox (awilfox)
Project Lead, Adélie Linux
https://www.adelielinux.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-12-27 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 2:49 utmp.h exitworld
2019-12-27 11:53 ` A. Wilcox [this message]
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=cfe9053d-82d0-08f9-35ad-9bfaf68041d3@adelielinux.org \
--to=awilfox@adelielinux.org \
--cc=exitworld@tutanota.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).