Re: [MiNT] Install script

[Peter Slegg <p.slegg@scubadivers.co.uk>]

Hi,

Paul has put a lot of effort into re-working my basic script that
was originally intended just to extract the daily build and make it
a bit easier to update my installation.

I don't know what state the script is in at the moment but I don't
think it's intended as full installer, I think the official releases
are still the prime source.

I did try Paul's script but it failed so I haven't been using it.

Regards,

Peter


On Thu, 1 Sep 2011 19:18:34 , David Sandberg <david@tomsand.com> wrote:
>
> Dear Paul, I don't understand why your upgrade script don't downloads
> automatically every stuff you needed for an elementary installation of
> AFROS and EASymint. If the places in internet are well known where the
> newest stuff to find. I think a script like that one of Minipack, which
> install all the needs and can download it automatically. This
> were very usefull.
>
> With aranym, AFROS, Easymint it is a pine, if the good explanation of
> Arnou or Marc-Anton (in German) don't ever work, if there are not more
> to find the disk.img you need for the AFROS install, only the directory
> with the files as a Zip-archive. It was very tricky to install
> Minipack, then duplicate the disk.img as IDE1. Delete all files and
> copy the AFROS on it (only the important thinks). Then install AFROS
> with easymint and copy the Files from so build AFROS-Disk.img
> to /C-Partition of AFROS/Easymint.
>
> Why that all don't work automatically to install? Otherwise it were
> nice if on your scripts.php site were little explanation to find for
> every script is for.
>
> Best David/Goli
>
>
> Am Wed, 3 Aug 2011 03:08:02 +1200
> schrieb Paul Wratt <paul.wratt@gmail.com>:
>
> > ok, here it is:
> >  mintupgr.sh
> >
> > although it started out as the initial script by Peter, it no longer
> > bears any resemblance
> >
> > I think I have got all the bugs ironed out
> >
> > it will work on auto-detect under MiNT.
> >
> > it can run under non-MiNT, uses defaults if auto-detecting
> >
> > if you set the defaults, just supply a .bz2, it will only cp/mv the
> > MINT.PRG & XAAES.KM for that system (without renaming)
> >
> > if you want a complete install supply --drivers --extras as well, the
> > folder will be called "install" instead of "upgrade"
> >
> > If does way more that most people will need, check --help
> >
> > if you dont have a complete system (SpareMiNT/EasyMiNT/GentooMiNT) you
> > can get a small archive with the required files.. (--requires or
> > --info)
> >
> > You should be able to pass any valid path to the FreeMiNT archive, bit
> > I designed it to work out of the current directory
> >
> > That is one of the lesser defaults that be can modified, along with
> > all the folder names and unique id, quiet, and copy/move
> >
> > Anyway, see what you think, let me know if you find any bugs..
> >
> > it should do just about any system, but not invalid ones (had000,
> > stv4e).. use --presets to get a quick list of common machines (ie
> > Falcon, CT6x, ARAnyM, etc), both Milan and Hades will get you an 060
> > configuration (based on the fact Peter has a mil060)
> >
> > if you prefix your normal options with --help it will show you a dry
> > run, adding the --list-xxxxxxx options will show all listed files (ls)
> > but only if you supply an archive (ie normal options)
> >
> > unknown --options are droped, you can get a list of suitable drivers
> > with --help _system_type_ --drivers, anyone with knowledge of a
> > specific platform driver set, double check you are getting what you
> > expect (thats what the apparent random posting was for), I dont know
> > if I got everything.. and some may still be wrong..
> >
> > if you use move (instead of copy) and it detects a previous extraction
> > (they dont get deleted), it should extract over the folder, this
> > depends on the uniqueness of the folder names
> >
> > the --info and --help should show current machine, which is set to
> > ara040, but it also has auto-detect on, so if you have a mint machine
> > it will auto-detect
> >
> > if you do heaps of kernel tests, use a hires unique id (its #'d in the
> > script). One last thing, it places "archive.txt" in the destination,
> > which contains the name of the .bz2 used, if you need that info for
> > some reason..
> >
> > Cheers
> >
> > Paul
>
>
>