Glynn,
I have a couple of questions on the specific requirements below. On
general question is are the requirements within a section (such as
"Installation") ordered by priority?
Also, is there a general prioritization here or could priorities be
assigned to the individual items as you see them? For example, are
there a set of items that are "must haves" for a meaningful, first
Indiana distribution?
3.1) Installation
INS-1: Provide infrastructure to install Indiana from
a single CD. The default install should be a
graphical experience, with a text console install
if preferred. The core install will be a basic
operating system and desktop environment.
There appear to be two distinct requirements being called out here.
The first, let's called it INS-1a, is around an installer that's build
around a CD rather than a DVD. The second, let's called it INS-1b,
concerns the default set of components/functionality delivered with the
CD. Is that correct?
Concerning INS-1b, what are the specific features that the installed OS
should provide? I realize the common thing to do will be to use
something that satisfies PKG-2 to download other components but is
there an expectation around this initial installation? Some examples
here include: which (productivity) tools? which languages? which
hardware drivers besides the obvious ones concerning the disk and
network?
INS-3: Any installation should be aware of existing
installed operating systems, prompt the user
for an appropriate action and intuitive
steps to carry out that action, particularly
with respect to re-partitioning if
necessary.
Some additional clarification of this requirement would be helpful.
How integrated should this repartitioning tool be with the installer
itself? Which existing operating systems should the installer be aware
of? Which partition types need to be supported on x86/x64 systems for
installation (and subsequent boot?)
INS-4: A LiveCD should be available for a 'try first,
install later' experience. The LiveCD functionality
should be integrated into the core install CD.
Given how little a CD can hold, how important is that the "live" media
actually be a CD versus something like a DVD? If the requirement is
really around a CD, again what are the attributes/features that the
live environment should contain? Which tools, languages, drivers,
etc?
3.4) Laptop Support
LAP-1: Provide a utility to generate feedback for system
configurations that are being installed, and build
a basic public hardware compatibility list. Provide
drivers for the most popular configurations.
There also seem to be two distinct requirements specified here. The
first, let's called it LAP-1a, seem to express a requirement for a tool
which generates a system report and makes it available to be used to
build a HCL. Or is it to have a tool like the Sun Device Detection
Tool run before or during installation to identify whether the target
machine is suitable for a Indiana installation?
The other requirement, let's called it LAP-1b, seems to call out the
need for more drivers. If that's the case, then there needs to be much
more specific requirements around which devices are important.
LAP-3: The system should automatically connect to an available
network, whether through a network cable or wireless
connection.
Given that Network Auto-Magic Phase 0 is already part of OpenSolaris,
what specific enhancements are meant by this requirement?
LAP-4: Any system connected up to an external video projector
should work without needing added configuration.
"Any" covers a awfully lot of systems. :-) Is there a list of the more
important ones given that we're talking about video drivers here?
dsc
_______________________________________________
indiana-discuss mailing list
[email protected]
http://opensolaris.org/mailman/listinfo/indiana-discuss
