Bryan Kadzban wrote:
Matthew Burgess wrote:
Well, I don't know what caused it but I got an error when trying to
move /usr/bin/mv to /bin - it complained that there wasn't a
/usr/bin/mv.
I have seen that once or twice myself. At the time, I put it down to
either something with package users, or a race condition inside mv when
it's moving itself. Now I'm thinking it isn't the package-user setup,
at least.
Sure enough, `mv' was already in /bin.
That's what I saw as well -- it's almost like mv had already moved it
when it complained.
I now appear to have two copies of `mv'!
OK... that's *not* what I saw. ;-)
I might be able to explain this one. Firstly, like you, my /usr/bin and
/bin are on the same FS. Secondly:
root:/usr/bin# ls -i /bin/mv /usr/bin/mv
1583093 /bin/mv 1881376 /usr/bin/mv
So, they're definitely not hard links and:
root:/usr/bin# ls -l /bin/mv /usr/bin/mv
-rwxr-xr-x 1 root root 71112 2006-11-24 15:24 /bin/mv
-rwxr-xr-x 1 root root 71112 2006-11-24 15:24 /usr/bin/mv
...they're definitely not symlinks.
Now, what happened was that on getting the error from the initial run, I
changed the instructions to not run `mv /usr/bin/mv /bin' and re-ran the
build/installation. That would explain why I'd have two copies of the
binary in different locations. The thing that's still leaving me
scratching my head is the fact that the timestamps are the same. I
don't think I'm that fast at typing or that a compile, test + install of
coreutils can be run instantaneously.
I'll run another build shortly to see if I can reproduce any of this.
In the meantime I'll revert that part of the commit.
Thanks,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page