sed
in [Shell]
|
Prev: fails
Next: Send one stream down two pipes
From: wtree on 4 Apr 2008 17:38 echo $(uname -m | sed -e s/i.86/i386/ ) produces i386 on one fedora installation but no output on another. It appears to be a problem with the sed command. Bash shell on both. ????
From: Bill Marcum on 4 Apr 2008 18:11 On 2008-04-04, wtree(a)imagic-inc.com <wtree(a)imagic-inc.com> wrote: > > > echo $(uname -m | sed -e s/i.86/i386/ ) > > produces i386 on one fedora installation but no output on another. It > appears to be a problem with the sed command. Bash shell on > both. ???? Is one of the machines an x86-64? What is the output of "uname -m" on each machine? By the way there's no need for the echo and $( ).
From: wtree on 5 Apr 2008 12:02 On Apr 4, 6:11 pm, Bill Marcum <marcumb...(a)bellsouth.net> wrote: > On 2008-04-04, wt...(a)imagic-inc.com <wt...(a)imagic-inc.com> wrote: > > > > > echo $(uname -m |sed-e s/i.86/i386/ ) > > > produces i386 on one fedora installation but no output on another. It > > appears to be a problem with thesedcommand. Bash shell on > > both. ???? > > Is one of the machines an x86-64? What is the output of "uname -m" on > each machine? By the way there's no need for the echo and $( ). uname -m output is i686 on both machines. The problem machine is an AMD 64 x2. The sed command produces no output on this machine even when called with the --version.
From: stan on 5 Apr 2008 21:29 wtree(a)imagic-inc.com wrote: > On Apr 4, 6:11 pm, Bill Marcum <marcumb...(a)bellsouth.net> wrote: >> On 2008-04-04, wt...(a)imagic-inc.com <wt...(a)imagic-inc.com> wrote: >> >> >> >> > echo $(uname -m |sed-e s/i.86/i386/ ) >> >> > produces i386 on one fedora installation but no output on another. It >> > appears to be a problem with thesedcommand. Bash shell on >> > both. ???? >> >> Is one of the machines an x86-64? What is the output of "uname -m" on >> each machine? By the way there's no need for the echo and $( ). > > uname -m output is i686 on both machines. The problem machine is an > AMD 64 x2. The sed command produces no output on this machine even > when called with the --version. Did you actually try the uname -m command on both machines? The AMD 64 shouldn't report i686. Please show the exact output from uname -m, as without it there's no way to figure out why the sed command may be working incorrectly.
From: pk on 6 Apr 2008 05:28
stan wrote: >> uname -m output is i686 on both machines. The problem machine is an >> AMD 64 x2. The sed command produces no output on this machine even >> when called with the --version. > > Did you actually try the uname -m command on both machines? The AMD 64 > shouldn't report i686. It could, if it's running a 32-bit linux distribution. The problem seems to be sed, which outputs nothing even when run with --version. -- All the commands are tested with bash and GNU tools, so they may use nonstandard features. I try to mention when something is nonstandard (if I'm aware of that), but I may miss something. Corrections are welcome. |