Date: Sat, 03 Sep 2005 13:47:56 +0300 From: Rein Kadastik <wigry@uninet.ee> Cc: freebsd-questions@freebsd.org Subject: Re: sed not working Message-ID: <43197F5C.9010507@uninet.ee> In-Reply-To: <43197A71.1030106@dial.pipex.com> References: <4318B54B.6080001@uninet.ee> <4318B66E.3010603@uninet.ee> <4318D90B.5030807@dial.pipex.com> <431954E6.1060802@uninet.ee> <43197A71.1030106@dial.pipex.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Alex Zbyslaw wrote:
> Rein Kadastik wrote:
>
>> Alex Zbyslaw wrote:
>>
>>> Rein Kadastik wrote:
>>>
>>>>
>>>> Rein Kadastik wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> I have a problem with sed on one of my systems.
>>>>>
>>>>> 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 :-)
>>
>>
>>
>> It shows /usr/bin/sed
>
>
> Final thought, what about copying /lib/libc.so.{whatever} as well as
> sed from that 4.10 system.
Well, I hope it does not break something as this is actually a
production system.
-- Rein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43197F5C.9010507>