*BSD News Article 28975


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!pipex!uknet!EU.net!Germany.EU.net!netmbx.de!zib-berlin.de!news.th-darmstadt.de!iti.informatik.th-darmstadt.de!deeken
From: deeken@iti.informatik.th-darmstadt.de (Hannes Deeken)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: yet more FreeBSD-1.1-BETA install bugs
Date: 29 Mar 1994 17:45:34 +0200
Organization: TU Darmstadt, ITI
Lines: 22
Message-ID: <deeken.764955732@iti.informatik.th-darmstadt.de>
References: <Cn7vwo.2z0@cosy.sbg.ac.at> <JKH.94Mar25151624@sentnl.ilo.dec.com> 	<2n71jn$6c3@Germany.EU.net> <JKH.94Mar29161752@sentnl.ilo.dec.com>
NNTP-Posting-Host: spessart.iti.informatik.th-darmstadt.de

jkh@sentnl.ilo.dec.com (Jordan Hubbard) writes:

>In article <2n71jn$6c3@Germany.EU.net> bs@Germany.EU.net (Bernard Steiner) writes:
>   There is a bug in the FreeBSD-1.1-BETA install script with respect to the
>   bad144 stuff.
>   It reads something like
>   bad144 -s > /dev/null 2>&1 | BLAH
>   but should IMHO read
>   (bad144 -s > /dev/null) 2>&1 | BLAH

>Hmmm.  Why?

Because '>/dev/null 2>&1' redirects stdout _and_ stderr to /dev/null,
so 'BLAH' gets no input. Bernards form works, but IMHO '2>&1 >/dev/null'
is more suitable, since you don't get another subprocess.


Hannes
-- 
Hans-Christoph Deeken | hannes@flinx.{RoBIN.de,hotb.sub.org} (home)
Jungfernstrasse 34    | deeken@iti.informatik.th-darmstadt.de (university)
64291 Darmstadt       | IRC: Glenlivet