Re: Sysinst GSOC project

[Martin Husemann <martin%duskware.de@localhost>]

On Sat, Apr 26, 2008 at 11:56:13PM -0700, Tim Rightnour wrote:
> #!/bin/sh
> preinst -o file
> postinst -f file

Exactly, and the auto-adaption/dhcp/dns tool could later replace
the interactive part, like

#!/bin/sh
autoadapt -i my.conf -o file
postinst -f file

> I think your first line of action should be to do a few installs, and write
> down all the questions sysinst asks you, and translate those into your config
> file.  You may find that there are certain lines of reasoning that open up
> different paths, where options that didn't show up before, now show up.

Note that there are also a lot of machine dependend prompts, and things that
get only asked on certain conditions depending on values chosen or found on
the machine (like existing partitions). This is where the frontend/backend
split becomes hairy, as you realy want more a "strategy" than a concrete
answer in the config file, so the backend can do it's magic w/o interaction.

Anyway, IIUC you want to use/modify the existing sysinst source to create
the frontend - so you will have to read the source anyway and come accross
all the questions, even the "hidden" ones.

Martin