On Wed, Jun 12, 2002 at 11:39:30PM +0200, Marcin Sochacki wrote:
On Wed, Jun 12, 2002 at 03:18:12PM -0400, David L. Zoll wrote:
For most of my production servers I just run Potato, though, since
perfect reliability is far more important than newer software for
me. The only package I wish
2) Hand compile openssh on each Potato machine, allowing for SSH2
network-wide, but requiring monitoring openssh for security
issues, and an annoying hand compiled upgrade on each machine
if/when issues are found.
2a) Handle compile on one machine, and use apt-get to install on
4) Upgrade apt to the version in Woody and then use pinning to get
ssh from Woody.
Question: wouldn't that also require getting apt, dpkg, etc. from
woody? I though pinning wasn't available in potato?
KEN
--
Kenneth J. Pronovici [EMAIL PROTECTED]
Personal Homepage:
On Thu, Jun 13, 2002 at 11:30:21AM -0500, Kenneth Pronovici wrote:
Question: wouldn't that also require getting apt, dpkg, etc. from
woody? I though pinning wasn't available in potato?
And most woody packages require libc6 2.2, which potato does not have.
Doing apt-get source openssh -b on
Question: wouldn't that also require getting apt, dpkg, etc. from
woody? I though pinning wasn't available in potato?
And most woody packages require libc6 2.2, which potato does not have.
Doing apt-get source openssh -b on potato with your deb-src lines set to
woody instead works
5 matches
Mail list logo
