On Sat, Feb 25, 2006 at 11:08:37AM +0000, i18rabbit@cwazy.co.uk wrote:
> it is not helping resolve anything to say:
> 
> "modifying any script or file on a NetBSD system voids
>  any and all operational guarantees".
>
> if this is the case, no one would be deserving of reporting
> a problem - because everyone modifies configuration files.

As far as I know, NetBSD has no operational guarantees in the first
place.  But you're not modifying configuration files; you're making more
significant changes. And reporting problems is fine, but you should be
more forthcoming about changes you've made to the standard system. As
it stands, I have no idea how your custom /etc looks, so I don't know
how I can help. I'm also puzzled as to your belief that it was somehow
a problem with the NetBSD source, rather than looking at your changes
first. Anyways, I already suggested that you check your PAM configuration,
which is stored in /etc, but you've been more interested in trying to
explain how it's NetBSD's problem, rather than actually trying the things
I suggested.

> just because it strikes as a bad idea,
> doesn't mean it is a bad idea.  i can
> use the same /etc on a Linux system
> as well - bringing up a BSD/Linux
> system is a simple and generic process
> and can be done with 20 simple shell lines
> for most any system.

Well good luck with that then.