-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Been using The Complete FreeBSD doing okay
until I tried using the following example to
update /usr/src:
cd /usr
cvs co -r RELENG_5_4 src 21 | tee /var/tmp/co.log
I get this:
Ambiguous output redirect
Can someone tell me what I'm doing wrong?
On 2005-06-13 04:41, Denny White [EMAIL PROTECTED] wrote:
Been using The Complete FreeBSD doing okay until I tried using the
following example to update /usr/src:
cd /usr
cvs co -r RELENG_5_4 src 21 | tee /var/tmp/co.log
I get this:
Ambiguous output redirect
You're using the wrong
Giorgos Keramidas wrote:
On 2005-06-13 04:41, Denny White [EMAIL PROTECTED] wrote:
Been using The Complete FreeBSD doing okay until I tried using the
following example to update /usr/src:
cd /usr
cvs co -r RELENG_5_4 src 21 | tee /var/tmp/co.log
I get this:
Ambiguous output redirect
On Monday 13 June 2005 12:53, Giorgos Keramidas wrote:
On 2005-06-13 04:41, Denny White [EMAIL PROTECTED] wrote:
Been using The Complete FreeBSD doing okay until I tried using the
following example to update /usr/src:
cd /usr
cvs co -r RELENG_5_4 src 21 | tee /var/tmp/co.log
I get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Jun 2005, Nikolaos Vassiliadis wrote:
On Monday 13 June 2005 12:53, Giorgos Keramidas wrote:
On 2005-06-13 04:41, Denny White [EMAIL PROTECTED] wrote:
Been using The Complete FreeBSD doing okay until I tried using the
following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Jun 2005, Alex Zbyslaw wrote:
Giorgos Keramidas wrote:
On 2005-06-13 04:41, Denny White [EMAIL PROTECTED] wrote:
Been using The Complete FreeBSD doing okay until I tried using the
following example to update /usr/src:
cd /usr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 13 Jun 2005, Giorgos Keramidas wrote:
On 2005-06-13 04:41, Denny White [EMAIL PROTECTED] wrote:
Been using The Complete FreeBSD doing okay until I tried using the
following example to update /usr/src:
cd /usr
cvs co -r RELENG_5_4 src
