Date: Fri, 14 Jan 2011 09:46:05 -0700 From: Michael Loftis <mloftis@wgops.com> To: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Policy on static linking ? Message-ID: <AANLkTinmfaOOz6gWN7khDCJZn2y3bAU=WB=yGuRfAiv%2B@mail.gmail.com> In-Reply-To: <E1PdkJV-0007GJ-Rc@dilbert.ticketswitch.com>
index | next in thread | previous in thread | raw e-mail
On Fri, Jan 14, 2011 at 7:07 AM, Pete French <petefrench@ticketswitch.com> wrote: > I build code using static linking for deployment across a set of > machines. For me this has a lot of advantages - I know that the > code will run, no matter what the state of the ports is on the > machine, and if there is a need to upgrade a library then I do it > once on the build machine, rebuild the executable, and rsync it out > to the leaf nodes. Only one place to track security updates, only > one place where I need to have all the porst the code depends on > installed. > You still have to track security updates for the rest of your system. ssh for example. Kernel bugs too (though admittedly those are much more rare).home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinmfaOOz6gWN7khDCJZn2y3bAU=WB=yGuRfAiv%2B>