mailing list of musl libc
 help / color / mirror / code / Atom feed
From: aep <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: make -i with linux-pam
Date: Tue, 22 May 2012 20:45:24 +0200	[thread overview]
Message-ID: <ec7187ecbdf1f2e6b961f3f7aff490df@exys.org> (raw)
In-Reply-To: <20120522182826.GU163@brightrain.aerifal.cx>

> They might be _used to_ it working, but that doesn't
> necessarily mean they "want" it.

Heh, this is where the difference in mindset shows. I tend to think 
people using things, actually want them.

> With that said, one acceptable approach might be to have utmp/wtmp
> support exist, but silently bail out (reporting success) if the file
> does not exist.

having utmp in libc is just so utterly wrong in the first place.
This really belongs in the higher stack, where decisions like that can 
be made based on config files.
Maybe some admins want to log ips, maybe some just usernames, some 
prefer binary logs, some prefer cleartext, etc..

Sounds like an interesting problem for your platform vision :)



  reply	other threads:[~2012-05-22 18:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14  3:58 Isaac Dunham
2012-05-14  4:11 ` Rich Felker
2012-05-14 18:01   ` Isaac Dunham
2012-05-14 18:17     ` Rich Felker
2012-05-15  0:09   ` Isaac Dunham
2012-05-16  3:24     ` Rich Felker
2012-05-16 14:23       ` Isaac Dunham
2012-05-21 19:12       ` aep
2012-05-21 19:28         ` Rich Felker
2012-05-21 20:24           ` aep
2012-05-21 20:55             ` Rich Felker
2012-05-21 21:08               ` aep
2012-05-21 21:20                 ` Rich Felker
2012-05-22 16:51             ` Christian Neukirchen
2012-05-22 17:50               ` Rich Felker
2012-05-22 18:22               ` aep
2012-05-22 18:28                 ` Rich Felker
2012-05-22 18:45                   ` aep [this message]
2012-05-22 20:00                     ` Rich Felker

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=ec7187ecbdf1f2e6b961f3f7aff490df@exys.org \
    --to=aep@exys.org \
    --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).