From owner-freebsd-security@FreeBSD.ORG  Wed May 31 01:22:15 2006
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
X-Original-To: freebsd-security@freebsd.org
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5BD6516A6E2
	for <freebsd-security@freebsd.org>;
	Wed, 31 May 2006 01:22:15 +0000 (UTC)
	(envelope-from v.velox@vvelox.net)
Received: from mail07.powweb.com (mail07.powweb.com [66.152.97.40])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1928C43D58
	for <freebsd-security@freebsd.org>;
	Wed, 31 May 2006 01:22:14 +0000 (GMT)
	(envelope-from v.velox@vvelox.net)
Received: from vixen42.vulpes (24-119-225-24.cpe.cableone.net [24.119.225.24])
	by mail07.powweb.com (Postfix) with ESMTP id 6871C14DB02;
	Tue, 30 May 2006 18:22:12 -0700 (PDT)
Date: Tue, 30 May 2006 20:23:25 -0500
From: Vulpes Velox <v.velox@vvelox.net>
To: brain@winbot.co.uk
Message-ID: <20060530202325.1398cc84@vixen42.vulpes>
In-Reply-To: <447AEA9B.6030005@winbot.co.uk>
References: <20060523120100.37D2B16A54F@hub.freebsd.org>
	<20060523083944.H96736@eboyr.pbz>
	<f34ca13c0605240233t1b3555dbn39f34b4d598d5bb7@mail.gmail.com>
	<20060524220703.K62075@a2.scoop.co.nz>
	<44743358.2020304@winbot.co.uk>
	<20060528210403.GB8791@silverwraith.com>
	<447AEA9B.6030005@winbot.co.uk>
X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Survey
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2006 01:22:16 -0000

On Mon, 29 May 2006 13:35:39 +0100
Craig Edwards <brain@winbot.co.uk> wrote:

> I was thinking more of the time-to-repair of a broken install,
> rather than a broken python or perl program, for example if your
> perl site-perl folder gets damaged, or your python compiled libs
> become ABI 'incompatible' somehow (say due to a g++ upgrade?).
> 
> In this case, both python *and* perl are pretty hard to repair
> unless you know the language, and can leave a system administrator
> between a rock and a hard place (reinstall, or seek an expert of
> that language)
> 
> I guess the same goes for ruby, i wouldn't know where to start in 
> repairing a broken ruby install...

It's been awhile since I've done something stupid that fragged ruby.
It was easy to fix though. I just rebuilt all the ruby stuff using
portupgrade. The same thing needs done with lots of perl modules as
well after perl is upgraded.