Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Jan 2007 09:22:31 +0200
From:      Danny Braniss <danny@cs.huji.ac.il>
To:        Vulpes Velox <v.velox@vvelox.net>
Cc:        freebsd-hackers@freebsd.org, Doug Barton <dougb@FreeBSD.org>
Subject:   Re: LDAP integration 
Message-ID:  <E1H4BJX-0002XZ-3O@cs1.cs.huji.ac.il>
In-Reply-To: <20070108185247.2b6e1f69@vixen42> 
References:  <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org>  <20070108185247.2b6e1f69@vixen42>

next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, 07 Jan 2007 22:02:30 -0800
> Doug Barton <dougb@FreeBSD.org> wrote:
> 
> > Vulpes Velox wrote:
> > > I was just wondering. How many people here have given lots of
> > > though about integrating FreeBSD configuration with LDAP. I've
> > > just begun looking at it a lot more and was curious as to what
> > > other people think in this area.
> > 
> > It would be more useful to have this discussion if you defined what
> > you meant by "FreeBSD configuration" in more detail. You might also
> > want to search the archives first, there is a lot of discussion
> > about various proposals in this area, all of which end up getting
> > shot down because they don't offer sufficient added value to
> > justify the pain of the change.
> 
> I mean exactly that. Initially I have begun looking at rc.conf as a
> logical starting point.
> 
> Initially I think seeing a rc.d stuck right in right after NETWORKING
> would be very interesting to have. Right after NETWORKING is
> finished, a program is kicked off that updates a rc file that is then
> included after parsing rc.conf.
> 
> I am currently wondering if any one else working on this, before I
> start digging to much into it. The only LDAP stuff I am finding
> on this list has been recently in regards to integration of a ldap nss
> module into the base system.

i realy don't know what this has to do with LDAP, but in our diskless
environment, /etc/rc.initdiskless, has some coded added that
based on info from DHCP will build a 'personalized' rc.conf
(the DHCP info is loaded into kenv by boot).

...
confpath=`kenv conf-path`
if [ -n "$confpath" ] ; then
    if [ "`expr $confpath : '\(.*\):'`" ] ; then
        echo Mounting $confpath on /conf
        mount_nfs $confpath /conf
        chkerr $? "mount_nfs $confpath /conf"
        to_umount="${to_umount} $confpath"
    fi
fi
...
eval `kenv | sed -n 's/^rc\.//p'`
rm -f /etc/rc.conf /etc/rc.conf.local
for fc in $conf0 $conf1 $conf2 $conf3 $conf4 $conf5 $conf6 $conf7 $conf8 
$conf9 rc.conf.$hostname
do
    ho=`expr $fc : '\(.*\):'`
    fl=`expr $fc : '.*/\(.*\)'`
    if [ "${ho}" != "" ]; then
        mp=`expr $fc : '\(.*\)/.*'`
        mount_nfs $mp /mnt > /dev/null 2>&1
        if [ -f /mnt/$fl ]; then
            echo "# from $fc /mnt/$fl" >> /etc/rc.conf
            cat /mnt/$fl >> /etc/rc.conf
        fi
        umount /mnt > /dev/null 2>&1
    elif [ -e /conf/$fc ] ; then
        echo "# from /conf/$fc" >> /etc/rc.conf
        cat /conf/$fc >> /etc/rc.conf
    fi
done





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1H4BJX-0002XZ-3O>