From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] PAM related: pam_console ?
Date: Wed, 06 Apr 2005 23:52:19 +0200 [thread overview]
Message-ID: <1112824339.9136.107.camel@nosferatu.lan> (raw)
In-Reply-To: <200504010019.11949@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
On Fri, 2005-04-01 at 00:19 +0200, Diego "Flameeyes" Pettenò wrote:
> On Thursday 31 March 2005 23:35, Mike Frysinger wrote:
> > if you do split it though, i'd suggest you split every module rather than
> > just certain ones that catch your fancy ... better to be consistent :p
> That's what I wanted to do, provide only basic modules with linux-pam
> (pam_unix and other) needed for basic auth facilities.
>
And every time there is a version update also update the slew of other
ebuilds? Like I said, if I wanted to be in the KDE/gstreamer herds, I
would have been.
> pam_console was just the first of the list.
>
You want it that bad, you can do it, but then you are its daddy, and do
all the updating, bug fixing (I'm sure the devfs crap do will give
issues, as its compile tested to 0.78 api) etc (and thank god if you
do).
> Anyway, pam 0.79 is out.. I just ask pam herd if they can add virtual/pam so
> that we can continue on openpam :)
>
Yes, I know will get to it somewhere - its usually a pita to get some
patches updated (pam_console-* for example :/) ... I'll get to it
eventually (want to first see what fedora do, as many pam guys are from
redhat).
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-06 21:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 13:17 [gentoo-dev] PAM related: pam_console ? Diego "Flameeyes" Pettenò
2005-03-31 13:27 ` Mike Frysinger
2005-03-31 13:34 ` Diego "Flameeyes" Pettenò
2005-03-31 13:57 ` Mike Frysinger
2005-03-31 14:26 ` Diego "Flameeyes" Pettenò
2005-03-31 15:01 ` Mike Frysinger
2005-03-31 15:17 ` Diego "Flameeyes" Pettenò
2005-04-06 21:47 ` Martin Schlemmer
2005-04-07 7:34 ` [gentoo-dev] bootstrap.sh and /var/lib/portage/world mathias
2005-04-07 13:08 ` Chris Gianelloni
2005-04-06 21:41 ` [gentoo-dev] PAM related: pam_console ? Martin Schlemmer
2005-03-31 20:38 ` Robin H. Johnson
2005-03-31 21:09 ` Diego "Flameeyes" Pettenò
2005-03-31 21:35 ` Mike Frysinger
2005-03-31 22:19 ` Diego "Flameeyes" Pettenò
2005-04-06 21:52 ` Martin Schlemmer [this message]
2005-04-06 21:40 ` Martin Schlemmer
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=1112824339.9136.107.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox