Re: sed and grep stopped working!

2018-08-19 Thread ToddAndMargo
On 08/18/2018 05:29 AM, Ed Greshko wrote: One could also "dnf install memtester" which will, if I recall correctly, give you an entry in your grub boot menu to start a memory test. I've not used any other those utility in a long time as I've not run into any weird memory problems. I am awas

Re: sed and grep stopped working!

2018-08-18 Thread Ed Greshko
On 08/17/18 20:34, Tom Horsley wrote: > On Fri, 17 Aug 2018 03:23:17 -0700 > Todd Chester wrote: > >> And now that you all write me back, they mysteriously started >> working again. AAHH! > This is the sort of thing that always makes me want to > run memtest for a few hours to see if

Re: sed and grep stopped working!

2018-08-18 Thread Wolfgang Pfeiffer
On Sat, Aug 18, 2018 at 02:20:31PM +0200, Wolfgang Pfeiffer wrote: Read about kali-linux the other day [ ... ] They write that the system won't neither touch nor mount an internal disk [2]. .. in forensic boot mode! Regards, Wolfgang [1] https://docs.kali.org/introduction/what-is-kali-lin

Re: sed and grep stopped working!

2018-08-18 Thread Wolfgang Pfeiffer
On Fri, Aug 17, 2018 at 09:49:01AM -0700, ToddAndMargo wrote: On 08/17/2018 09:17 AM, Matthew Miller wrote: On Fri, Aug 17, 2018 at 08:34:12AM -0400, Tom Horsley wrote: Todd Chester wrote: And now that you all write me back, they mysteriously started working again. AAHH! This is

Re: sed and grep stopped working!

2018-08-17 Thread Tim via users
Allegedly, on or about 17 August 2018, Tom Horsley sent: > This is the sort of thing that always makes me want to > run memtest for a few hours to see if memory corruption > is happening (in, for instance, the in memory copies of > pages from shared libs the tools might have been using). > > http:

Re: sed and grep stopped working!

2018-08-17 Thread Cameron Simpson
On 17Aug2018 00:17, Todd Chester wrote: grep and sed stopped working! I dnf re-installed them both. No joy What the heck (not my "actual" word)? [...] Next time this happens consider snapshotting the output at various points: $ echo "a-b-c" | tee echo.out | ( set -x; sed -e 's/-//g' ) 2>se

Re: sed and grep stopped working!

2018-08-17 Thread ToddAndMargo
On 08/17/2018 05:34 AM, Tom Horsley wrote: On Fri, 17 Aug 2018 03:23:17 -0700 Todd Chester wrote: And now that you all write me back, they mysteriously started working again. AAHH! This is the sort of thing that always makes me want to run memtest for a few hours to see if memor

Re: sed and grep stopped working!

2018-08-17 Thread ToddAndMargo
On 08/17/2018 09:17 AM, Matthew Miller wrote: On Fri, Aug 17, 2018 at 08:34:12AM -0400, Tom Horsley wrote: Todd Chester wrote: And now that you all write me back, they mysteriously started working again. AAHH! This is the sort of thing that always makes me want to run memtest for

Re: sed and grep stopped working!

2018-08-17 Thread Matthew Miller
On Fri, Aug 17, 2018 at 08:34:12AM -0400, Tom Horsley wrote: > Todd Chester wrote: > > And now that you all write me back, they mysteriously started > > working again. AAHH! > This is the sort of thing that always makes me want to > run memtest for a few hours to see if memory corrupt

Re: sed and grep stopped working!

2018-08-17 Thread Tom Horsley
On Fri, 17 Aug 2018 03:23:17 -0700 Todd Chester wrote: > And now that you all write me back, they mysteriously started > working again. AAHH! This is the sort of thing that always makes me want to run memtest for a few hours to see if memory corruption is happening (in, for instance

Re: sed and grep stopped working!

2018-08-17 Thread Todd Chester
On 08/17/2018 12:17 AM, Todd Chester wrote: Hi All, grep and sed stopped working!  I dnf re-installed them both. No joy What the heck (not my "actual" word)?   H How do I fix this? Many thanks, -T And now that you all write me back, they mysteriously started wor

Re: sed and grep stopped working!

2018-08-17 Thread Ed Greshko
On 08/17/18 15:17, Todd Chester wrote: > Hi All, > > grep and sed stopped working!  I dnf re-installed them > both. No joy > > What the heck (not my "actual" word)? > > >   H > > How do I fix this? > > Many thanks, > -T > > > uname -r > 4.17.9-200.fc28.x86_64 > > # rpm -qa

Re: sed and grep stopped working!

2018-08-17 Thread Dave Mitchell
On Fri, Aug 17, 2018 at 12:17:26AM -0700, Todd Chester wrote: > Hi All, > > grep and sed stopped working! I dnf re-installed them > both. No joy Maybe your PATH and/or aliases settings are causing the wrong commands to be chosen. Does $ /usr/bin/echo "abc" | /usr/bin/grep "a" work? If not,

Re: sed and grep stopped working!

2018-08-17 Thread Samuel Sieb
On 08/17/2018 12:17 AM, Todd Chester wrote: grep and sed stopped working!  I dnf re-installed them both. No joy The packages to check are likely pcre and pcre2. "rpm -q pcre pcre2" "rpm -qV pcre pcre2" ___ users mailing list -- users@lists.fedoraproj

sed and grep stopped working!

2018-08-17 Thread Todd Chester
Hi All, grep and sed stopped working! I dnf re-installed them both. No joy What the heck (not my "actual" word)? H How do I fix this? Many thanks, -T uname -r 4.17.9-200.fc28.x86_64 # rpm -qa grep grep-3.1-5.fc28.x86_64 # rpm -qa sed sed-4.5-1.fc28.x86_64 $