From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Pluggable Hell Part 2: Fixing everything up!
Date: Thu, 07 Apr 2005 01:17:27 +0200 [thread overview]
Message-ID: <1112829447.9136.121.camel@nosferatu.lan> (raw)
In-Reply-To: <200504070011.31705@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 2852 bytes --]
On Thu, 2005-04-07 at 00:11 +0200, Diego "Flameeyes" Pettenò wrote:
> > > openpam will pdepend on
> > > freebsd-pam-modules to provide both in a simple way.
> > Why? What good will they do on linux? Just stick them in bsd profile.
> Mainly, openpam is shipped without any kind of module. If someone would like
> to replace Linux-PAM with openpam on a Linux system (it's possible), I'd much
> prefer to provide it with everything he needs. Linux-PAM builds its own
> modules, openpam just provide pam implementation and needs other packages to
> provide the basic modules. FreeBSD's modules should work on Linux and this
> would make possible the switch between Linux-PAM and openpam.
>
I was more talking about the virtual/pam-modules (or whatever). Having
a a PDEPEND is just fine.
> > Like I said before, only real reason why I will biatch about this one,
> > is its called 'pam' on all linux distro's, and it will be another lost
> > history (ok, so the workaround is a schlepp) case without real cause.
> Actually it's called libpam usually :)
> Mainly, calling it pam is usual on linux-centric systems, but as Gentoo is not
> only Linux, and "it's all about choice", having it called as it's named,
> IMHO, is a way to state clearly what it is.
> Just take a look to telnet-bsd and netkit-telnetd. On Debian there's
> netkit-telnet which is called just telnet.
> Anyway this is only "cosmetic" and for what I "need" or better I feel is
> needed, this is something which can be omissed.
>
Like I said - its more just me than anything else.
> > Ugh, no - just more crud that somebody will have to clean out later.
> > Like I said, get pam-0.78 and issues fixed, bumped to stable on all
> > linux archs, and we can scourge the tree.
> That's a decision up to you as pam mantainers :)
> Anyway I'm available to add the temporary fixes, trace them, and remove them
> when all is done, if needed.
>
Id rather just do it cleanly.
> > > I'll work anyway on a pam_stack hack for openpam, also if I'm not sure
> > > if, when and how I'll be able to make it work... also I don't like too
> > > much messing with security stuff :/
> > Sorry, you are on your own here.
> I know and I'll try to do everything I can, but if in the mean time it could
> be used the other method should be enough until there's a way to "support"
> pam_stack on openpam.
>
Well, the include should work, be the cleanest and less up and down way
(you really do not want to coordinate a big change across the tree in
more than one direction more than once - you usually end up burning
yourself) - I'll work through the pam bugs for 0.78, and see if we can
get it pushed to stable.
Thanks,
--
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 23:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 20:15 [gentoo-dev] Pluggable Hell Part 2: Fixing everything up! Diego "Flameeyes" Pettenò
2005-03-31 0:41 ` Luca Barbato
2005-03-31 10:12 ` Gregorio Guidi
2005-03-31 14:10 ` Fabian Zeindl
2005-03-31 13:21 ` Diego "Flameeyes" Pettenò
2005-04-06 21:38 ` Martin Schlemmer
2005-04-06 22:11 ` Diego "Flameeyes" Pettenò
2005-04-06 23:17 ` Martin Schlemmer [this message]
2005-04-08 7:22 ` Diego "Flameeyes" Pettenò
2005-04-08 9:47 ` [gentoo-dev] portage on NetBSD (was: Pluggable Hell Part 2: Fixing everything up!) Stefan Sperling
2005-04-08 18:32 ` [gentoo-dev] portage on NetBSD Aaron Walker
2005-04-08 18:43 ` Diego "Flameeyes" Pettenò
2005-04-06 22:15 ` [gentoo-dev] Pluggable Hell Part 2: Fixing everything up! 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=1112829447.9136.121.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