From owner-freebsd-questions@FreeBSD.ORG Fri Sep 2 22:58:22 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD0CE16A41F for ; Fri, 2 Sep 2005 22:58:22 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out6.blueyonder.co.uk (smtp-out6.blueyonder.co.uk [195.188.213.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 102A743D48 for ; Fri, 2 Sep 2005 22:58:20 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.229.102] ([82.41.229.102]) by smtp-out6.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Fri, 2 Sep 2005 23:59:07 +0100 Message-ID: <4318D90B.5030807@dial.pipex.com> Date: Fri, 02 Sep 2005 23:58:19 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.8) Gecko/20050530 X-Accept-Language: en, en-us, pl MIME-Version: 1.0 To: Rein Kadastik References: <4318B54B.6080001@uninet.ee> <4318B66E.3010603@uninet.ee> In-Reply-To: <4318B66E.3010603@uninet.ee> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Sep 2005 22:59:07.0912 (UTC) FILETIME=[EC86D880:01C5B011] Cc: freebsd-questions@freebsd.org Subject: Re: sed not working X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 22:58:22 -0000 Rein Kadastik wrote: > > Rein Kadastik wrote: > >> Hi >> >> I have a problem with sed on one of my systems. >> >> Lets take the following command: >> >> sed -e '/^\([a-z_][a-z_]*\) /s//\1 gen_/' >> >> On all other systems the input would be transformed: >> int something() -> int gen_something() >> >> On the broken system, the transformation is not done: >> int something() -> int something() >> >> The broken system used to be 4.6-STABLE but I managed to upgrade it >> to 4.11-RELEASE-p11, hoping that the update procedure will fix the >> sed, but apparently not. Imagine the make buildworld without working >> sed :) Anyway I generated the files on other working system so I >> managed to get through the buildworld part. Installkernel and >> installworld did not used sed so no problems there. >> >> Does anybody have some ideas, what would be the reason? I tested the >> sed command also on 4.8-RELEASE and 4.10-STABLE where it works >> nicely. Even copied the sed over from working systems but no luck. > You've probably tried this, but what does "which sed" show on the broken system? It should show /usr/bin/sed and if it doesn't, there's your problem :-) --Alex