home *** CD-ROM | disk | FTP | other *** search
-
- >>>>> mtk == Markus Wild <mw@eunet.ch> wrote:
-
- > Cannot create link file or directory exist!
-
- mtk> If you're overwriting existing stuff, these warnings can
- mtk> happen..
-
- > File (tar, compress, gzip, mount-????, init) busy cannot extract!
-
- mtk> Happens if you're trying to overwrite a currently
- mtk> running executable. This means that this executable
- mtk> wasn't updated in your filesystem, so take care!
-
- > Could not create directory: it exists!
-
- mtk> Harmless.
-
- > Something else, I was using my /opt directory for my transfer area and
- > this wasn't formated. Could this have been creating any of my above problems
- > with tar. Perhaps something was looking to put files on the /opt directory.
-
- mtk> Directory or partition? I don't see how you'd want to
- mtk> format a directory...
-
- As an aside... I had none of these problems. What I had done was
- to build tar and gzip again and had them installed in /usr/local/bin.
- For some reason, I could never get the older tar+gzip to do xzvfp -
- I always got "stdin not in compressed format" error message... I
- noticed the same problem with pjotr's system when I telnetted there
- and built some stuff for him.
-
- Because I had tar+gzip in /usr/local/bin, and /usr/local/bin is on
- my path, I was able to do: rm /bin/* and then tar xzvfp /tmp/usr-bin.tgz
- (and the same for each of the bin-*.tgz files.
-
- For what it's worth, I'm paranoid. I do not trust to simply untar
- the new bin-*.tgz over the existing filesystem (already installed /bin
- for example). If you had an old /bin/foo and the new archive does
- not have a new /bin/foo, then you have the new bin-bin.tgz installed
- plus the old /bin/foo. My paranoia is that I neither want the old
- /bin/foo nor do I wish to risk the old /bin/foo being incompatible
- with new bins that it works with. When I imagine running a mixture
- of old tcp/nfs daemons with new tcp/nfs daemons, I can only see
- problems.
-
- Now, I must point out that before you rm /usr/lib/*, you should
- consider that if you had installed X11 or built your own libraries
- to install there, then you would be erasing these too. I had
- links to the X11 libs in /usr/lib that I wanted to preserve. So
- I did: cd /usr/lib and then rm individual files by hand to keep
- what I wanted.
-
- I should also point out that mtk's bin-*.tgz have links made in them
- that did not work on my system. His X11 links point to some odd
- place that my X11 isn't at :-) A good thing about tar is that it
- will not overwrite your links. If you keep your /usr/lib/X11 link
- in place, when you untar the usr-usrlib.tgz file, it won't destroy
- the perfectly good link you already made.
-
- Another thing I remember is that the new bin-bin.tgz file did not
- have a /bin/sh in it! TO fix that, I simply made a link to bash
- for it: ln -s /bin/bash /bin/sh.
-
- Lastly, I had problems building a kernel from the bsdsyssrc720.tgz,
- but the src0712.tgz file had all the files needed, in the right
- places, to build kernels. A word of advice: use the AMIGA config
- file as a starting point. The GODZILLA one will not build a working
- kernel. (makes me wonder how mtk does it :-) Apply chopps' patches
- if you want X to work.
-
-
-
- mtk> -Markus
- mtk> --
- mtk> CHUUG/EUnet Switzerland Markus Wild
- mtk> Zweierstrasse 35 Tel: +41 1 291 45 80 mw@eunet.ch
- mtk> CH-8004 Zuerich Fax: +41 1 291 46 42
- mtk> S=mw;P=EUnet;A=EUnet;C=CH
-
-
-