From pycyn@aol.com Fri Nov 23 13:30:23 2001 Return-Path: X-Sender: Pycyn@aol.com X-Apparently-To: lojban@yahoogroups.com Received: (EGP: mail-8_0_0_1); 23 Nov 2001 21:30:23 -0000 Received: (qmail 98358 invoked from network); 23 Nov 2001 21:30:23 -0000 Received: from unknown (216.115.97.167) by m5.grp.snv.yahoo.com with QMQP; 23 Nov 2001 21:30:23 -0000 Received: from unknown (HELO imo-r09.mx.aol.com) (152.163.225.105) by mta1.grp.snv.yahoo.com with SMTP; 23 Nov 2001 21:30:23 -0000 Received: from Pycyn@aol.com by imo-r09.mx.aol.com (mail_out_v31_r1.9.) id r.61.16fc4fbb (4007) for ; Fri, 23 Nov 2001 16:30:21 -0500 (EST) Message-ID: <61.16fc4fbb.293019ec@aol.com> Date: Fri, 23 Nov 2001 16:30:20 EST Subject: tar(1) tao To: lojban@yahoogroups.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_61.16fc4fbb.293019ec_boundary" X-Mailer: AOL 6.0 for Windows US sub 10535 From: pycyn@aol.com X-Yahoo-Profile: kaliputra --part1_61.16fc4fbb.293019ec_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/23/2001 1:26:00 PM Central Standard Time, b.gohla@gmx.de writes: > The tao that can be tar(1)ed is not the entire Tao. > The path that can be specified is not the Full Path. > What the fatal fandango is "tar(1)" and how is it related to Tao (in the original)? Nuzzling into Linux suggests it is a function deep in all the eunuchs but I am not sure that any of that applies here (nor what the "(1)" means). Archiving a path doesn't seem to be the same as walking it -- or describing it, depending. So, that joke failing, what is going on? --part1_61.16fc4fbb.293019ec_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/23/2001 1:26:00 PM Central Standard Time, b.gohla@gmx.de writes:


The tao that can be tar(1)ed is not the entire Tao.
The path that can be specified is not the Full Path.


What the fatal fandango is "tar(1)" and how is it related to Tao (in the original)?  Nuzzling into Linux suggests it is a function deep in all the eunuchs but I am not sure that any of that applies here (nor what the "(1)" means).  Archiving a path doesn't seem to be the same as walking it -- or describing it, depending.  So, that joke failing, what is going on? --part1_61.16fc4fbb.293019ec_boundary--