Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!rex!ukma!seismo!dimacs.rutgers.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.unix.questions
Subject: Re: Limitations of cp and mv?
Message-ID: <16212@smoke.brl.mil>
Date: 21 May 91 03:19:50 GMT
References: <2570004@hpcc01.HP.COM> <7918@auspex.auspex.com> <DJM.91May19175716@egypt.eng.umd.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 11

In article <DJM.91May19175716@egypt.eng.umd.edu> djm@eng.umd.edu (David J. MacKenzie) writes:
>mv (no special option needed -- I don't like that part) will move
>entire directory trees across filesystems transparently.

Well, it CAN'T.  Hard links into the hierarchy from outside it cannot be
preserved by such a move.

Where in the world did POSIX.2 get the idea of -R?  I've already determined
that we are NOT going to be specifying POSIX.2 in any procurements I'm
involved in -- why would I want to specify an incompatible, non-UNIX system
instead of the subset of UNIX that I really need?