Justin Zygmont wrote:
>
> > Seriously: I think the binary install should do exactly the same
> > that the (excellent) source install does; i.e. it should put
> > exactly the same files in exactly the same locations (/usr/local)
> > that are used by ./configure, make, [become root] make install. It
> > should just free the dummy user from the compilation step, for
> > which he/she most probably lacks the tools, and would be
> > confronted with (to her/him) incomprehensible error messages
> > because of that. It should (like the source install) also be
> > independent of freedos, because dosemu itself is independent of
> > it. Like the source install, it should ask which directory is the
> > 'C drive'. If user/dummy does not know, it should be pointed out
> > that some form of DOS is needed, and installation of freedos offered.
>
> well, a compresed tar file will extract itself relative to your current
> path, so you can't really have it install to /usr/local by default, it's
> not usually a problem anyways. There is the RPM that might be preferrable
> for you, dosemu is much easier than it used to be.
>
sound the gong!
tar -xzfP tarfile will install absolute if
tar -czfP tarball / was used
OK-OK simmer down class.
cd someplace with space (/tmp)
mkdir a dummy directory (/tmp/d)
cd the dummy dir (pwd -> /tmp/d )
mkdir usr
mkdir usr/local
mc /usr/local ./usr/local
arrow down to dosemu
<F5> and copy branch
<F10>
tar -czPf /anotherplace/tarfile /
get the picture?
done?
clean up your disk!
the -P retains leading "/"
Steve Turner
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
