*BSD News Article 28873


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!EU.net!Germany.EU.net!news
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: yet more FreeBSD-1.1-BETA install bugs
Date: 30 Mar 1994 18:17:24 +0200
Organization: EUnet Deutschland GmbH, Dortmund, Germany
Lines: 33
Distribution: world
Message-ID: <2nc8mk$8lf@Germany.EU.net>
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: qwerty.germany.eu.net


In article <JKH.94Mar29161752@sentnl.ilo.dec.com>, jkh@sentnl.ilo.dec.com (Jordan Hubbard) writes:
|> In article <2n71jn$6c3@Germany.EU.net> bs@Germany.EU.net (Bernard Steiner) writes:
|>    bad144 -s > /dev/null 2>&1 | BLAH
|>    but should IMHO read
|>    (bad144 -s > /dev/null) 2>&1 | BLAH
|> 
|> Hmmm.  Why?

Well, regardless of the sequence of ">" and "2>&1", the dup2() is done, so
that stderr ends up in /dev/null. The additional braces (brackets ?
parentheses ? whatever...) make the thing executed by a sub-shell that
re-directs stdout to /dev/null and passes stderr up, where stderr gets
dup2()'ed to stdout and that is then piped to the rest of the magic stuff.

|>    The stock kernel probes my wd8013 sitting at 0x300 as mcd0, but that's just a
|>    minor annoyance
|> 
|> That's fixed and folded back into the release.

Glad to hear.

|> If you want any assurance of reaching anybody at all, the thing to
|> do is send to:	freebsd-bugs@freefall.cdrom.com

Will do so quite soon now to go on ranting about the lp[at]probe().
And will send a message in a minute regarding the new cp(1) implementation
which causes kernel panics.

Great idea, that mmap() stuff. Except for isofs files, since isofs does not
seem to handle mmap()... (tar works, though)

-Bernard