> Jeff Black wrote: > > > I was able to find 3 links in that email. There were 1 binary and 2 source code > > links. > > Unfortunately when extracting the tar.gz'd binary(s) I end up with 1 file. > > Mtools.exe > > Typing mtools.exe gave a 'help' screen of sorts. "the following commands are > > supported:" <insert > > long list of mtools commands here>, but at the bash command prompt > > $ mcopy > > $ bash: mcopy : command not found > > > > Understandable considering mcopy actually didn't exist ;( > > > > I was able to download and compile the source code for mtools after browsing > > around for a bit... > > > mcopy and other 'm'-commands are symlinks to mtools, they are created > during 'make install' when you build from source, or you could create > them yourself.
Ugh, using winzip on tar.gz's is proving to be hazardous. Now that Ive written out the directions for installing cygwin and meeting all unattended's dependencies, I'm not sure what is 'better', installing mtools from source or downloading binaries. For now I'll leave the directions as is. ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ unattended-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-devel
