On Monday 03 September 2001 3:48 am, Tim Wunder wrote:
> What does the 'mv' command actually do?
> I've always been under the impression that it simply renames the
> file/directory, but I get the feeling there's more to it than that.
>
> My recent experience with compiling the KDE2.2 SRPMs has led me to think
> that.
>
> When I tried to compile the KDE2.2 source under eW3.1, I first mv'd the
> /opt/kde2 directory to /opt/kde22, thinking this got the existing KDE stuff
> out of the way for the new install. But I couldn't get kdelibs to compile.
> I then decided to just try instaling kde2 from the RPMs instead of the
> SRPMs and that seemed to work (well, I DID --force --nodeps everything). I
> then had the problem of starting KDE, which apparently was the result of
> the inability to load a shared library.
>
> I then punted. I rm -r'd the /opt/kde2 directory and mv'd /opt/kde22 back
> to /opt/kde2. Next I cp -R'd /opt/kde2 to /opt/kde22 for a backup.
> After that, I decided to re-try the SRPMs, and everything compiled fine
> (except for kdegraphics, which required a little cheating).
>
> The only difference bewteen my two methods, was the use of 'cp -R' to make
> a backup of /opt/kde2 rather than 'mv'.
>
> Hence my question, what does the command 'mv' actually do?
mv just does a rename (as long as the source & target are on the same
partition/drive, but that's another story). I think your problem arose
because the kde2.2 compile needed something from the original kde2 tree,
which of course you had effectively removed by doing a mv. I can't say for
sure as you didn't say what the compile error actually was.
HTH
Pam
--
UK Linux Step by Step mirror: http://www.pam.roberts.btinternet.co.uk/sxs/
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
