the Linux install for 5.6

[John Esak]

Great. Yeah, I realized I would have to do all the uncompressing and etc.
myself... with the cool tar flag which I didn't know about, thnks, or
gunzip... but my question was directed to FP Tech/support... where are the
"correct" instructions if the files are all tar'd/gzipped. The 3
instructions the guy read to me were each wrong. Only 3 and each one was
completely incorrect. for example the first one reads:

   mount /cdrom /mnt

Now, how is that going to work? Unless there is a device actually called
/cdrom???  Well, the command didn't work, so I switched it to:

   mount /dev/cdrom /mnt

and, of course, that worked. Then, on to the tar of the files... it was
completely messed up, not having the z flag you mention and pointing to a
directory called /mnt/cdrom/FullDev or FullRun. There is no cdrom
directory... Yes, I can fix all this stuff, but my question is why. We had a
long beta period, no one mentioned the Linux install not working. How could
it, though?  Maybe the beta testers were all going through their "own" fixed
install procedures?  All I know is, no average business owner like the guy I
was helping is going to be able to install from the existing printed on the
CD-Rom cover, instructions. Well, I guess no average business owner should
be installing programs on a Linux system??? Consultants have been doing this
forever and I guess always will be doing it. Too bad.

John


> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of Fairlight
> Sent: Thursday, April 27, 2006 9:52 PM
> To: filePro Mailing List
> Subject: Re: the Linux install for 5.6
>
>
> Confusious (John Esak) say:
> >
> > I fixed the incorrect mount command to mount the cdrom properly
> onto /mnt.
> > But I can't fix the incorrect tar command that is looking in the wrong
> > directory for FullDev and FullRun, etc.  Well, I can certainly
> fix the path,
> > omit "cdrom" but then it can't find the file it is looking for
> because the
> > file is tar'd and gzipped... How could these instructions be so
> completely
> > wron?  Is there any place for us to look for a correct set of
> installation
> > instructions?
>
> You didn't say what the actual tar command they gave was, but if it's for
> linux and it's a gzipped tar, use 'xvzf' for your flags.  The 'z' is what
> does the uncompress (or compress when creating).
>
> mark->
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list