Re: DragonFly 3.4 release planning
Dan Cross <[email protected]>
| Newsgroups | gmane.os.dragonfly-bsd.kernel |
|---|---|
| Message-ID | <CAEoi9W6atSZ6hkm1i4DJMePS+v5pUYA2-VoAJtaXZxF-0-RWpw@mail.gmail.com> |
On Sat, Mar 30, 2013 at 2:25 PM, Matthew Dillon <[email protected] > wrote: > :> Binaries in /bin and /sbin are compiled statically, which makes them > unusable > :> with NSS modules. > :> This is IMHO the biggest remaining issue with this release. > : > :Just curious - hasn't this been the case for some time? > :And if so / not - why did this become an issue for you now? > : > :Not taking one side or another, just wondering about more background info, > :though I do seem to recall a rather strong position taken *against* > :dynamic /bin /sbin in this project when FreeBSD switched to dynamic > :builds in the freebsd ~6.x-7.x era > > I think I'm the only one who is really against making /bin and /sbin > dynamic. I feel kinda silly standing on top of the hill holding up > the red flag :-(. > > I really hate the concept of a /rescue. I could live with a nullfs > overloading of /bin and /sbin, but so far nobody (including I) has > thought up a good clean way to do it and still have the safety of > static binaries in single-user mode. > 4.4BSD had the convention of calling /rescue /stand (I suppose /stand was actually a bit more restricted, not including as many things as /rescue). Regardless, I never really understood the rationale for changing the name, and it did not seem like a bad way to do things: what is your specific objection? - Dan C.