On second thought, since the required packages are really just a continuation of base that is too large to fit on floppies, there really does not need to be a menu for that part of the install at all. Base would install then once it is in place, it asks where you want to continue the installation from (cdrom, partition, ftp, etc) then starts loading the required packages (assuming a clean install here). No dependancies to worry about here. Once THAT part is complete, the menu-driven dselect is started with NOTHING pre-selected (and it remembers no selections when you exit).
On Sat, 12 Apr 1997, Jason Gunthorpe wrote: > On Fri, 11 Apr 1997, George Bonser wrote: > > > > > Just a short suggestion: > > > > Split dselect. A small one (dinstall?) just for installation and a more > > full-featured one for configuration management. > > Okay I will bite, Why? > > If you have a small dselect then the first thing to be installed would be > the larger dselect. > > Now perhaps two different programs with different roles would be a good > idea, but what would they be more specificaly? > > Here is an idea that seems to have been hinted at indirectly by a number > of posts and that is a configuration aide for newbies. It would present > them with a list of packages and tell them were the config files are and > direct them to the /usr/doc/package files, etc.. I donno. > > Jason > > I am giving .sigs a break this month George Bonser [EMAIL PROTECTED], [EMAIL PROTECTED]
