On Tue, Dec 31, 2002 at 05:08:06PM +0200, Sami Haahtinen wrote:
> On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> > As libnss-ldap can be configured to use SASL (and as a result, pluggable
> > modules), I don't think static linking is a very feasible solution. A
> > better questi
On Tue, Dec 31, 2002 at 05:08:06PM +0200, Sami Haahtinen wrote:
> On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> > As libnss-ldap can be configured to use SASL (and as a result, pluggable
> > modules), I don't think static linking is a very feasible solution. A
> > better questi
On Tue, Dec 31, 2002 at 08:04:12PM -0800, Grant Bowman wrote:
> * Sami Haahtinen <[EMAIL PROTECTED]> [021231 19:23]:
> > i don't think i should re-assign the bug (#118607) that started this
> > discussion as it doesn't refer to this problem but to a different
> > problem. Also i'm not quite sure if
On Tue, Dec 31, 2002 at 08:04:12PM -0800, Grant Bowman wrote:
> * Sami Haahtinen <[EMAIL PROTECTED]> [021231 19:23]:
> > i don't think i should re-assign the bug (#118607) that started this
> > discussion as it doesn't refer to this problem but to a different
> > problem. Also i'm not quite sure if
* Sami Haahtinen <[EMAIL PROTECTED]> [021231 19:23]:
> On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> > As libnss-ldap can be configured to use SASL (and as a result, pluggable
> > modules), I don't think static linking is a very feasible solution. A
> > better question would be
* Sami Haahtinen <[EMAIL PROTECTED]> [021231 19:23]:
> On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> > As libnss-ldap can be configured to use SASL (and as a result, pluggable
> > modules), I don't think static linking is a very feasible solution. A
> > better question would be
On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> As libnss-ldap can be configured to use SASL (and as a result, pluggable
> modules), I don't think static linking is a very feasible solution. A
> better question would be, why does the system need nss_ldap loaded at
> time of shutd
On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> As libnss-ldap can be configured to use SASL (and as a result, pluggable
> modules), I don't think static linking is a very feasible solution. A
> better question would be, why does the system need nss_ldap loaded at
> time of shutd
Steve> On Thu, Dec 26, 2002 at 09:55:37AM -0800, Ian Zimmerman wrote:
Steve> Oh, I understand how it would happen that a file in /usr is
Steve> actively in use in this scenario; I'm just questioning why it
Steve> shouldn't be considered a bug in whatever program is still
Steve> running and referen
Steve> On Thu, Dec 26, 2002 at 09:55:37AM -0800, Ian Zimmerman wrote:
Steve> Oh, I understand how it would happen that a file in /usr is
Steve> actively in use in this scenario; I'm just questioning why it
Steve> shouldn't be considered a bug in whatever program is still
Steve> running and referen
On Thu, Dec 26, 2002 at 09:55:37AM -0800, Ian Zimmerman wrote:
> Steve> Oh, I understand how it would happen that a file in /usr is
> Steve> actively in use in this scenario; I'm just questioning why it
> Steve> shouldn't be considered a bug in whatever program is still
> Steve> running and refere
Steve> Oh, I understand how it would happen that a file in /usr is
Steve> actively in use in this scenario; I'm just questioning why it
Steve> shouldn't be considered a bug in whatever program is still
Steve> running and referencing NSS at the time 'umount /usr' is
Steve> called. There are quite
On Thu, Dec 26, 2002 at 09:55:37AM -0800, Ian Zimmerman wrote:
> Steve> Oh, I understand how it would happen that a file in /usr is
> Steve> actively in use in this scenario; I'm just questioning why it
> Steve> shouldn't be considered a bug in whatever program is still
> Steve> running and refere
Steve> Oh, I understand how it would happen that a file in /usr is
Steve> actively in use in this scenario; I'm just questioning why it
Steve> shouldn't be considered a bug in whatever program is still
Steve> running and referencing NSS at the time 'umount /usr' is
Steve> called. There are quite
On Wed, Dec 25, 2002 at 12:18:35AM +0200, Sami Haahtinen wrote:
> On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> > On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
> > > The only proper solution (which i was looking into this weekend
> > > actually) would be to sta
On Wed, Dec 25, 2002 at 12:18:35AM +0200, Sami Haahtinen wrote:
> On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> > On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
> > > The only proper solution (which i was looking into this weekend
> > > actually) would be to sta
On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
> > The only proper solution (which i was looking into this weekend
> > actually) would be to statically link all required libraries into
> > libnss-ldap and keep that i
On Thu, Dec 19, 2002 at 05:23:09PM -0800, Grant Bowman wrote:
> * Sami Haahtinen <[EMAIL PROTECTED]> [021217 15:13]:
> > one solution would be to move the whole module to /usr, but that would
> > not (atleast to my knowledge, although i haven't tested it) solve the
> > problem, the same problem wou
On Fri, Dec 20, 2002 at 11:39:43PM -0600, Steve Langasek wrote:
> On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
> > The only proper solution (which i was looking into this weekend
> > actually) would be to statically link all required libraries into
> > libnss-ldap and keep that i
On Thu, Dec 19, 2002 at 05:23:09PM -0800, Grant Bowman wrote:
> * Sami Haahtinen <[EMAIL PROTECTED]> [021217 15:13]:
> > one solution would be to move the whole module to /usr, but that would
> > not (atleast to my knowledge, although i haven't tested it) solve the
> > problem, the same problem wou
* Steve Langasek <[EMAIL PROTECTED]> [021220 21:44]:
> On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
>
> > The only proper solution (which i was looking into this weekend
> > actually) would be to statically link all required libraries into
> > libnss-ldap and keep that in /lib,
* Steve Langasek <[EMAIL PROTECTED]> [021220 21:44]:
> On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
>
> > The only proper solution (which i was looking into this weekend
> > actually) would be to statically link all required libraries into
> > libnss-ldap and keep that in /lib,
On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
> The only proper solution (which i was looking into this weekend
> actually) would be to statically link all required libraries into
> libnss-ldap and keep that in /lib, i'm not that keen in the idea as it
> might bring some new unex
On Wed, Dec 18, 2002 at 01:07:42AM +0200, Sami Haahtinen wrote:
> The only proper solution (which i was looking into this weekend
> actually) would be to statically link all required libraries into
> libnss-ldap and keep that in /lib, i'm not that keen in the idea as it
> might bring some new unex
* Sami Haahtinen <[EMAIL PROTECTED]> [021217 15:13]:
> On Tue, Dec 17, 2002 at 10:43:27AM -0600, Steve Langasek wrote:
> > What information are you trying to store in LDAP that is so essential to
> > the system prior to mounting of /usr?
> >
> > It is entirely valid for /usr to be located on a net
* Sami Haahtinen <[EMAIL PROTECTED]> [021217 15:13]:
> On Tue, Dec 17, 2002 at 10:43:27AM -0600, Steve Langasek wrote:
> > What information are you trying to store in LDAP that is so essential to
> > the system prior to mounting of /usr?
> >
> > It is entirely valid for /usr to be located on a net
On Tue, Dec 17, 2002 at 03:42:00PM -0800, Grant Bowman wrote:
> * Steve Langasek <[EMAIL PROTECTED]> [021217 08:47]:
> > What information are you trying to store in LDAP that is so essential to
> > the system prior to mounting of /usr?
> > [...]
> Using LDAP information as a replacement for almos
* Steve Langasek <[EMAIL PROTECTED]> [021217 08:47]:
> What information are you trying to store in LDAP that is so essential to
> the system prior to mounting of /usr?
> [...]
Using LDAP information as a replacement for almost all of /etc/password.
--
-- Grant Bowman
On Tue, Dec 17, 2002 at 10:43:27AM -0600, Steve Langasek wrote:
> What information are you trying to store in LDAP that is so essential to
> the system prior to mounting of /usr?
>
> It is entirely valid for /usr to be located on a network share (NFS), so
> you're not really guaranteed to be able
On Tue, Dec 17, 2002 at 03:42:00PM -0800, Grant Bowman wrote:
> * Steve Langasek <[EMAIL PROTECTED]> [021217 08:47]:
> > What information are you trying to store in LDAP that is so essential to
> > the system prior to mounting of /usr?
> > [...]
> Using LDAP information as a replacement for almos
* Steve Langasek <[EMAIL PROTECTED]> [021217 08:47]:
> What information are you trying to store in LDAP that is so essential to
> the system prior to mounting of /usr?
> [...]
Using LDAP information as a replacement for almost all of /etc/password.
--
-- Grant Bowman
On Tue, Dec 17, 2002 at 10:43:27AM -0600, Steve Langasek wrote:
> What information are you trying to store in LDAP that is so essential to
> the system prior to mounting of /usr?
>
> It is entirely valid for /usr to be located on a network share (NFS), so
> you're not really guaranteed to be able
On Tue, Dec 17, 2002 at 08:29:44AM -0800, Grant Bowman wrote:
> After reading the content of this bug, I'm curious which rules would be
> broken by moving the necessary libraries to /lib from /usr/lib. I can
> understand why you have moved this bug to "won't fix" but without some
> kind of soluti
On Tue, Dec 17, 2002 at 08:29:44AM -0800, Grant Bowman wrote:
> After reading the content of this bug, I'm curious which rules would be
> broken by moving the necessary libraries to /lib from /usr/lib. I can
> understand why you have moved this bug to "won't fix" but without some
> kind of soluti
34 matches
Mail list logo
