> On Tue, May 27, 2003 at 06:13:09PM +0200, Buchan Milne wrote: >> First stab: >> http://qa.mandrakesoft.com/twiki/bin/view/Main/RequestedFeatures >> >> Those with edit access on the Wiki, feel free to expand ... > > Here's a few other ones (I don't have write access). > > How about more support for a small business environment, including tools > to setup centralised account
I didn't add this yet as a feature request as it belongs in the "The Big Picture" section, and I still need to add some bits to the server section and drakxtools section to support it, but that's basically what I am aiming at, the LDAP wizard was the first attempt, but I may try and use libconf (if I have the time for this at all). But first we need a working openldap-2.1 (with db migration if necessary) and a better default config file (generic regex-based ACLs). > and specialised installs for server and > client boxen. > I really don't think this is necessary. Who determines what a client box runs? Should it run apache or not (maybe the box is a desktop of a web developer). Should it run samba or not (maybe you have windows desktops, and some users need to be able to share files easily). Should it run an ldap server (maybe as a slave for disconnected authentication). Should a server not have KDE (newbie admins will probably need some tools, ksambaplugin is a good example)? > An option to setup an internal mandrake mirror on a server (as one of > the task choices). And of course the companion option on the client to > use this mirror as install/update source. > I have mentioned this before ... so yes, I will add this. What I really think should happen is that urpmi should use ldap .... > In a general sense, would it be a good idea to provide mandrake install > with a context during the installation? Stuff like (pc, laptop) (server, > client) I don't think this is necessarily the rigth approach. The only machine I have worked on with > 1GB ram is not a server, but a laptop ... so which machine gets the enterprise kernel? The only real difference is enabling acpi etc etc. > (office, multimedia, games). This is done already. > Specific hardware questions very > early on in the install procedure and perhaps suggestions to further > tune the > installation afterwards (add nvidia/matrox/ati/etc. drivers from sources > X, Y, Z) in a file in /root/tuning-suggestions.txt. Since commercial versions of Mandrake ship with the drivers anyway, and in some cases the Mandrake Control Center will install drivers from the Club commercial sources, I don't see why any additional provision should be made for vendors who make life more difficult for linux distros. > Maybe this isn't realistic for 9.2, but this would probably make it even > easier for newbies to install mandrake, even for business use. IMHO, rather than supporting proprietary hardware (ie NVidia/ATI drivers), support for open-source friendly hardware (or at least hardware with open-source drivers) must be faultless. The promise issue is a really bad problem on 9.1 ....
