Ron Stodden wrote:
> Install steps on the left are upside down - Configure X should be at
> the top, Select Installation Class at the bottom. Progress is
> conventionally displayed as left to right or upwards (Climbing a tree, the
> path to heaven, etc.). so as better to conform to a traffic signal etaphor,
> and conform to 1st quadrant geometry that every one is used to and
> understands.
Please please PLEASE do not do this! That would be extraordinarily
confusing! Checklists are normally filled out top to bottom, same as the
order English text is normally read in (left to right, top to bottom). And
I'm not sure what he's talking about with the traffic signal thing; which
traffic signals, GO is at the bottom, so if we're going to use a traffic
signal metaphor, we need to get to the bottom before we're ready to GO (i.e.
boot). I expect 98% of Mandrake users would find the checklist going from
the bottom to the top, especially if readable labels are next to each item,
to be extremely counter-intuitive. Ron is obviously in the other 2%. But
as long as text labels are next to each item, and those text labels are
written in English, they MUST go from top to bottom to obey standard English
conventions (read from top to bottom).
> The input of networking information is too late, since networking
> characteristics influence the selection of RPMs to install.
I hope not. My network card can't be detected during install (requires ISA
PnP tools and a config file). I can't answer yes to networking since it
then attempts to configure things it can't. I need to answer no here, then
set things up manually later. If it then fails to install RPMs I need for
networking because I said "No" to _configure_ my network during install,
this would be highly annoying. What RPMs are installed or not should depend
on my installation class. What I _configure_ during installation is a
seperate issue entirely, and _should not affect_ what is installed.
> Supermount is fixed to only accept a vfat floppy. Set fs=auto and modprobe
> complains 'no such module'. Ext2 floppies must be mountable.
Then say no to supermount during install. Supermount cannot autodetect
filesystems. When you say "fs=xxx" there needs to be a filesystem named
xxx. If it's not compiled into the kernel, it attempts to load the module
"xxx.o" and if that doesn't exist (such as "auto.o"), you get the "no such
module" error.
-- Guy T. Rice ---------------------------------- <[EMAIL PROTECTED]> --
"Every human being should pursue his or her own dharma perfectly instead
of following another's dharma imperfectly." -- Hindu scriptures
