On Tue, 2004-07-06 at 06:28, Chad Carr wrote: > I think the basic premise of a preconfig system would be to take some > user input (this could start small like asking them to select their > NICs from a list and what type of boot media they want), then > generating a .bin or .iso for them with the modules built in and the > initial config-db laid populated with default values. > > I have basically two questions I would like to put up to the group: > > 1) Should this tool be host-based (downloadable) or server-based (a web > interface)?
Chad, I lean toward a downloadable preconfig system. Web interfaces take considerable resources to host. They do tend to be more popular though. > 2) What main functionality should it have? This is a list of > possibilities to get the discussion going: > configure console (serial, vga, or headless) > configure NICs (possibly including initial IP addressing) > configure dns/dhcpd > configure time zone/ntp > configure additional packages to install (not the package configs > themselves) > > If we decide to create a host-based tool, we need to answer two > additional questions: > > 1) Do we require linux as a host? > 2) Do we require network access during preconfig? -- Mike Noyes <mhnoyes at users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
