Path: utzoo!attcan!uunet!cs.utexas.edu!chinacat!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F. Haugh II)
Newsgroups: comp.unix.wizards
Subject: Re: Hard links to directories: why not?
Message-ID: <18474@rpp386.cactus.org>
Date: 28 Jul 90 20:24:00 GMT
References: <18461@rpp386.cactus.org> <1990Jul22.035130.12559@zoo.toronto.edu> <18466@rpp386.cactus.org> <3724@auspex.auspex.com> <18468@rpp386.cactus.org> <1990Jul23.083256.17790@athena.mit.edu>
Reply-To: jfh@rpp386.cactus.org (John F. Haugh II)
Organization: Lone Star Cafe and BBS Service
Lines: 18
X-Clever-Slogan: Recycle or Die.

In article <1990Jul23.083256.17790@athena.mit.edu> jik@pit-manager.mit.edu (Jonathan I. Kamens) writes:
>  Are /dev and /usr/tmp on your machine on different partitions?  If
>so, then the behavior of mv is understandable.

No, it is not understandable.  It doesn't take much work to do a
mknod() on the device major/minor numbers from stat().

The description for mv(1) is 

	"mv moves (changes the name of) file1 to file2."

On the bottom, under "Notes:" it says that mv must copy the file
it it exists on another filesystem.  So, someone did half the
work to notice the filesystems were different, but never bothered
to see if it was a device or FIFO object.
-- 
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh@rpp386.cactus.org