On Wednesday 21 November 2001 04:38, Guillaume Cottenceau wrote:
> Alan <[EMAIL PROTECTED]> writes:
> > Some things I would like to see in the installer...
> >
> > 1) When you select "development" as an option, all devel packages get
> > installed by default.  It is a royal pain in the ass to have to go back
> > and find devel packages later on when you are trying to get a piece of
> > code to build.
>
> No, development gives a few base development packages such as autoconf,
> automake, gcc, binutils, plus additional development packages for each
> group you selected.

I said "should".  There needs to be some sort of option that will 
automatically install development packages as part of the install.  Finding 
out that you missed one is a real pain when you are in the middle of a 
compile.  (Or dealing with users who have a low frustration level.)

> > 2) Something to configure multiple monitors/cards in X.  (Also a way to
> > go back and reconfigure a monitor when you buy a new one because the old
> > one let out the magic smoke.)
>
> Via Xinerama or not you may configure two monitors when you have two cards
> or you have one card with dual head. This was introduced in 8.0 or 8.1,
> not sure.

I am speaking of a graphical Xinerama config option at install. I can do this 
by hand, but I have been dealing with users who have never mucked with an 
XF86Config-4 file in their life. 

I have a Matrox G400 Max card with dual heads.  I have set them up before.  
Users who have similar set ups with Windows are probably wondering why Linux 
does not set things up to see the second monitor.

> > 3) If SMP is detected, don't assume that it is a 686. (The
> > firewall-on-a-disc does this. My dual Pentium Pro 200 was not amused.)
>
> Uh? SMP means using kernel-smp, which is a i586 kernel AFAIK.

Well then it locked up for some other reason. I will have to investigate 
further when I have time.

> > 4) On upgrade, remove previous catalog entries in the Mandrake updater.
> > (So it does not show versions from 2+ versions, just the current one.) If
> > you don't remove them, label them better in the catalog listing so they
> > can be removed later.
> >
> > 5) On upgrade, find a way to make the upgrade complete in less than 12
> > hours! (This one has gotten on my nerves. The last upgrade from 8.0 to
> > 8.1 went to poorly, I did a scratch-and-burn on the system to fix it.)
>
> We've put some sleep everywhere, on purpose :-)).

Well, since the upgrade leaves the system in a fairly buggy state, few people 
try it more than once.

It should not take that long. I will need to look at that section of code I 
guess...


Reply via email to