From owner-freebsd-questions Fri Apr 19 07:34:00 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA08720 for questions-outgoing; Fri, 19 Apr 1996 07:34:00 -0700 (PDT) Received: from fslg8.fsl.noaa.gov (fslg8.fsl.noaa.gov [137.75.131.171]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA08712 for ; Fri, 19 Apr 1996 07:33:56 -0700 (PDT) Received: by fslg8.fsl.noaa.gov (5.57/Ultrix3.0-C) id AA04800; Fri, 19 Apr 96 14:33:45 GMT Message-Id: <9604191433.AA04800@fslg8.fsl.noaa.gov> Received: by emu.fsl.noaa.gov (1.40.112.3/16.2) id AA248234537; Fri, 19 Apr 1996 08:35:37 -0600 Date: Fri, 19 Apr 1996 08:35:37 -0600 From: Sean Kelly To: s_koyin@eduserv.its.unimelb.edu.au Cc: questions@freebsd.org In-Reply-To: <199604190652.QAA01500@eduserv.its.unimelb.EDU.AU> (message from HMG coA reductase on Fri, 19 Apr 1996 16:52:36 +1000 (EST)) Subject: Re: Questions... Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>>>> "Ivan" == HMG coA reductase writes: Ivan> G'day, does anyone have the answers to below? Some of them, yes. Ivan> 1. is there a way to access the FreeBSD file-system from Ivan> DOS? No. Ivan> 2. is Motif Window Manager (mwm) available for FreeBSD? Ivan> Seems available linux... Both run XFree86... I've seen commercial versions of mwm available with a couple of Motif 1.2 kits. I'm not a fan of Motif (it's rather ugly, actually) so I can't help any further---except to say that you might check the commerical resources under the FreeBSD home page (http://www.freebsd.org/) ... I remember seeing a vendor listed who sells Motif with mwm. But, you might want to consider fvwm over mwm. It's free, it's compatible with mwm, and can be configured to look like mwm. Heck, even its default configuration looks very much like mwm. Ivan> 3. why do i get this error: gzip: pipe broken (where gzip Ivan> could be col or zcat) usually when pressing `q' while Ivan> reading manpages. Because the gzip process writes to its standard output, which is a pipe connected to teh standard input of your pager command, `more'. When you press `q', the `more' command closes its standard input and exits. This causes the pipe to close. The gzip process doesn't know you pressed `q', and since the pipe to which it was writing was closed, it gets notified via a signal (SIGPIPE). gzip just wants to tell you what happened, so it prints ``broken pipe.'' Just ignore the message. -- Sean Kelly NOAA Forecast Systems Laboratory kelly@fsl.noaa.gov Boulder Colorado USA http://www-sdd.fsl.noaa.gov/~kelly/