From: Chris.Smith@raytheon.co.uk
Date: Thu, 9 Nov 2000 15:02:45 +0000
Message-Id:
Subject: Re: [SLE] Can we post suggestions anywhere (Was: Re: [SLE] SuSE 7.1 timeline?)
Hi,
** The chance of having Intel's own driver included within the Kernel
** itself is about zero as Intel does not want it to be part of the Kernel.
For
** what reason I have no idea. SuSE maybe able include if they can make a
deal
** with Intel, but I wouldn't hold your breath.
I didn't suggest including it with the kernel. An optional package
could be installed by yast1/2 and the driver configured from there.
It's a module (.o) so it should just be modprobable and yast1/2
could pick the module up if it exists. It would save playing
around with aliases etc. snd/emu10k1 already does this without
the yast installation capability. I'm sure there are EtherExpress
owners all over who would like this.
Intel, despite what everyone always says, is a very nice company.
I'm sure they'd be glad to have their own drivers available to
SuSE users.
** Easier setup of two or more Network cards during installation.
** Currently configuring either card sets it up as eth0.
Agreed.
** Yast1 or Yast2 inclusion of Primary and Secondary DNS, rather
** than just nameserver. I am too lazy to write out all the zones
** and it would also be nice to follow some sort of template).
Agreed again..
** Now that Yast2 is module based that should be easier to
** accomplish.
That would be good. Sorting out the colours in yast2 console
mode would make me happy too.
Another point I wish to bring up (if anyone is still listening)
is:-
Why do you need to install xshared to use OpenSSH ?????
Apart from these points - I'm the happiest person about :)
- Chris.
