Well, getting out 1.1 is a little more than just the installer. I'm working
on reorganizing the base OS, and had a problem because I think I may need to
get involved in some of that code and could not work on the installer. I
spend about seven years as part of the Tru64 UNIX install team, so I know a
little about installers ;-)
I suggest you take a look at the existing installer. It's OK, but tries to
copy some of the older Linux installers and seems to be somewhat
overwhelming, so that needs to be slimmed down. I'd also like to apply a
different design.
What I have in mind is a design in which all questions are asked up front
and responses are tested for validity, e.g., do you have enough disk space
for all the selected software, do you have the right hardware for a selected
option, etc., and then the install happens. In my previous experience, we
had a GUI that wrote a file to a RAM disk, and then invoked a process we
called playback to to the physical install. We also wote this file out to
the installed disk so that an installation could be easily cloned.
After installation, there was a directory.that was examined for post install
steps. It will be used for software configuration and other actions
necessary after the first reboot.
Additionally, we need to improve software packaging so that any dependencies
are checked prior to attempting installs and packages have an opportunity to
run run pre- and post-install processes or scripts. It should be a single
file, ala rpm, although there are strong arguments as to why it should be
something akin to the windows installer.
Of course, I don't expect all this in 1.1, but this is the vision.
Your turn. What did you have in mind?
Pat Villani
Project Coordinator
On Fri, Mar 5, 2010 at 2:33 AM, Verizon <port...@verizon.net> wrote:
> If you guy's need still an installer program for Freedos, let me know.
>
> Tell me exactly what processes you want it to do, (i.e., format, sys,
> create directories, load files, etc) and I should have a full blown,
> graphics installer, similar to that used for Windows done for your
> inspection in in a couple of weeks if time, and my job permits.
>
> It may be able to FDISK a system as well, but I have never tried doing an
> FDISK from a command line enviroment. I don't even know if there is an
> FDISK program that does this, so I'll have to have a little information on
> that one. I have an older machine here I can test it on.
>
> Seems that's the only way we're going to get FreeDOS 1.1 out, right?
>
> Tom
>
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Freedos-devel mailing list
> Freedos-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-devel
>
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
