Re: DragonFly 3.4 release planning

[Dan Cross <crossd@xxxxxxxxx>]

--e0cb4efe2bd8f7945004d9289f0d
Content-Type: text/plain; charset=UTF-8

On Sat, Mar 30, 2013 at 2:25 PM, Matthew Dillon <dillon@apollo.backplane.com
> 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.

--e0cb4efe2bd8f7945004d9289f0d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On Sat, Mar 30, 2013 at 2:25 PM=
, Matthew Dillon <span dir=3D"ltr">&lt;<a href=3D"mailto:dillon@apollo.back=
plane.com" target=3D"_blank">dillon@apollo.backplane.com</a>&gt;</span> wro=
te:<br>

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">:&gt; Binaries in=
 /bin and /sbin are compiled statically, which makes them unusable<br>
<div class=3D"im">:&gt; with NSS modules.<br>
:&gt; This is IMHO the biggest remaining issue with this release.<br>
:<br>
:Just curious - hasn&#39;t this been the case for some time?<br>
:And if so / not - why did this become an issue for you now?<br>
:<br>
:Not taking one side or another, just wondering about more background info,=
<br>
:though I do seem to recall a rather strong position taken *against*<br>
:dynamic /bin /sbin in this project when FreeBSD switched to dynamic<br>
:builds in the freebsd ~6.x-7.x era<br><br>
</div>=C2=A0 =C2=A0 I think I&#39;m the only one who is really against maki=
ng /bin and /sbin<br>
=C2=A0 =C2=A0 dynamic. =C2=A0I feel kinda silly standing on top of the hill=
 holding up<br>
=C2=A0 =C2=A0 the red flag :-(.<br>
<br>
=C2=A0 =C2=A0 I really hate the concept of a /rescue. =C2=A0I could live wi=
th a nullfs<br>
=C2=A0 =C2=A0 overloading of /bin and /sbin, but so far nobody (including I=
) has<br>
=C2=A0 =C2=A0 thought up a good clean way to do it and still have the safet=
y of<br>
=C2=A0 =C2=A0 static binaries in single-user mode.<br></blockquote><div><br=
></div><div style>4.4BSD had the convention of calling /rescue /stand (I su=
ppose /stand was actually a bit more restricted, not including as many thin=
gs as /rescue). =C2=A0Regardless, I never really understood the rationale f=
or changing the name, and it did not seem like a bad way to do things: what=
 is your specific objection?</div>

<div style><br></div><div style>=C2=A0 =C2=A0 =C2=A0 =C2=A0 - Dan C.</div><=
div style><br></div><div style>=C2=A0</div></div></div></div>

--e0cb4efe2bd8f7945004d9289f0d--