NSS/LDAP and DragonFly

One of the requirements to get NSS/LDAP working on (most) any unixlike system is to have dynamic binaries; meaning they are dependent on various libraries to run.  Since you’re talking about programs for login when you’re talking about NSS/LDAP, that means if the libraries aren’t available, you can’t log in.  DragonFly has static binaries just to avoid that problem.

Francois Tigeot proposed switching to dynamic binaries and building a /rescue directory with static backups, as is the case with I think FreeBSD and NetBSD.  If you follow the thread, it looks like the best path is to use initrd instead.  Initrd stands for INITial Ram Disk, and is the first volume the computer sets up to boot from BIOS.  Since initrd gives the computer enough space to load all the needed modules (like Hammer2…), it works without making the computer dependent on various libraries or having a bloated /rescue directory.

(Someone correct me if I have the details wrong.)  As long as we’re talking about things that would help DragonFly in a larger environment, can someone work on a VM balloon memory driver, too?

Posted by     Categories: DragonFly, Goings-on     1 Comment
1 Comment on NSS/LDAP and DragonFly

Respond | Trackback

  1. Anonymous says:

    I second the memory ballooning.