Re: Possible solution to custom installations.
In your email to me, Dale Scheetz, you wrote:
> At the outer level of the distribution tree create directories like: SWS
> for simple work station, NWS for networked work station, etc... The names
> could probably use a little work, but that isn't critical to the idea.
> Each of these directories would have links to the actual package files
> elsewhere in the distribution. The simple work station directory would
> have links to only those packages that are desirable for such a system
> configuration along with a Packages file that contained only those
> packages. This would not cost much disk space and would allow for easy
> installation of such a system with dselect. One would simply point to this
> directory in the [A]ccess phase (and only this directory) and then
> [S]elect All Packages after [U]date ing the available file. All the
> dependencies could be ironed out in testing and could result in a "simple"
> installation path for the "usual" kinds of setup. I think that it might be
> possible to provide a "response" file that would "do the right thing" and
> let the installer go to lunch while the system was built.
Just brief consideration leads me to believe that this will work. The
hard thing will be getting the response file. Maybe we can may out
some possible answers in a readme or install doc for that configuration?
(work) firstname.lastname@example.org / (home) email@example.com - http://www.buoy.com/~tps
"What if there were no hypothetical situations?"
** Disclaimer: My views/comments/beliefs, as strange as they are, are my own.**
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .