Xref: utzoo unix-pc.general:2851 comp.sys.att:6357
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!njin!princeton!jonlab!jon
From: jon@jonlab.UUCP (Jon H. LaBadie)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: Floppy Boot, Filesystem, and Diags (was Re: 3.5" floppy disk revisited)
Summary: a small amount of space can be saved by linking mv to cp and ln
Message-ID: <777@jonlab.UUCP>
Date: 5 May 89 11:28:20 GMT
References: <695@icus.islp.ny.us> <629@cbnewsc.ATT.COM> <698@icus.islp.ny.us>
Followup-To: unix-pc.general
Organization: 4455 Province Line Rd., Princeton, NJ 08540
Lines: 30

In article <698@icus.islp.ny.us>, lenny@icus.islp.ny.us (Lenny Tropiano) writes:

	A discussion of how to create a bootable diskette
	followed by this list of files to place on the diskette

> 
> These can be taken from the hard disk:

  ...

> /bin/cp linked to /bin/ln
  ...
> /bin/mv

	rest of article deleted

I would just like to point out that on most unix systems, mv is also
simply a link to cp and ln.  It could have been implemented this way
on the UNIX-PC also, but the implementers chose to give us two
identical programs in /bin.  One is the linked cp and ln, the other
is mv.  They are byte for byte identical.  The only difference
is the permissions.  Mv is set uid'ed.

If space becomes a premium on the floppy, a few blocks could be saved
by linking mv to cp and ln, then changing permissions on them to
match /bin/mv on the HD (4755, root owner).
-- 
Jon LaBadie
{att, princeton, bcr}!jonlab!jon
{att, attmail, bcr}!auxnj!jon