Re: [Cooker] Re: What to do with RFEs
On Fri, 2003-05-30 at 16:14, Michael Reinsch wrote: Hi! On Tue, 27 May 2003 18:13:09 +0200 Buchan Milne [EMAIL PROTECTED] wrote: First stab: http://qa.mandrakesoft.com/twiki/bin/view/Main/RequestedFeatures Those with edit access on the Wiki, feel free to expand ... I don't have access (well, this is a wiki and it is also well hidden - so why is access control required anyway? The big wikis don't have one either...), so I'll post my stuff here: Better support for notebooks: I'm not talking about hardware at the moment but other stuff which is not required for normal desktop computers because they don't get carried around. Most of the stuff I'd like to see in the next release are already filed as bug reports (e.g. http://qa.mandrakesoft.com/show_bug.cgi?id=3944 - power management scripts) or packaged (http://archives.mandrakelinux.com/cooker/2003-05/msg01355.php - automatic location control - do some stuff automatically when changing networks). The two things I've mentioned are both quite small scripts, but they help me a lot, so I guess they might help others as well. In ref to the above Please!
Re: [Cooker] Re: What to do with RFEs
On Tue, May 27, 2003 at 06:13:09PM +0200, Buchan Milne wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Warly wrote: Buchan Milne [EMAIL PROTECTED] writes: There have been a number of threads relating to requests for enhancements / new features for 9.2, and I think it's about time to get them all in one place. I think that list of proposed enhancements should be more logically put in wiki. 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 and specialised installs for server and client boxen. 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. 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) (office, multimedia, games). 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. 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. Cheers Simon
Re: [Cooker] Re: What to do with RFEs
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
Re: [Cooker] Re: What to do with RFEs
Hi! On Tue, 27 May 2003 18:13:09 +0200 Buchan Milne [EMAIL PROTECTED] wrote: First stab: http://qa.mandrakesoft.com/twiki/bin/view/Main/RequestedFeatures Those with edit access on the Wiki, feel free to expand ... I don't have access (well, this is a wiki and it is also well hidden - so why is access control required anyway? The big wikis don't have one either...), so I'll post my stuff here: Better support for notebooks: I'm not talking about hardware at the moment but other stuff which is not required for normal desktop computers because they don't get carried around. Most of the stuff I'd like to see in the next release are already filed as bug reports (e.g. http://qa.mandrakesoft.com/show_bug.cgi?id=3944 - power management scripts) or packaged (http://archives.mandrakelinux.com/cooker/2003-05/msg01355.php - automatic location control - do some stuff automatically when changing networks). The two things I've mentioned are both quite small scripts, but they help me a lot, so I guess they might help others as well. -- Michael Reinsch [EMAIL PROTECTED] http://mr.uue.org pgp0.pgp Description: PGP signature
Re: [Cooker] Re: What to do with RFEs
Am Samstag, 31. Mai 2003 00:50 schrieb [EMAIL PROTECTED]: 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. I thought yesterday about a thing like this. The context should not be detected automatically (this wouldn't work) , but installs for special purposes would be a good thing, I think. What I think of (examples): a router --- dhcpd + firewall + minimalistic installation + ?(mserver/linecontrol)? + ... would be a good thing to choose this installation i think of an installation like specialized distributions like esmith and others. soho-server more things additional to the above, like ldap, samba, apache for intranet (??) and what else one could think of. multimedia-homeserver - dvr/mp3-box/dvd-player/streaming-server ( think of mythtv / vdr / GiantDisc / whatelse) A big part of te above could be done from a package list like the autoinstall disk. It should be easy to deploy such a profile and maybe collecting/sharing of such profiles could be made possible. The problem is that some parts of the configuration should be done then automatically too and that can't be done with a thing like the autoinstallation disc. I don't know if this can at all be done, but it would be nice to be able to compete with some specialized ditributions (have a mandrake box installed for a special task, w/o the need of big work after installation) Just an idea I thought about yesterday Steffen
[Cooker] Re: What to do with RFEs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Warly wrote: Buchan Milne [EMAIL PROTECTED] writes: There have been a number of threads relating to requests for enhancements / new features for 9.2, and I think it's about time to get them all in one place. I think that list of proposed enhancements should be more logically put in wiki. First stab: http://qa.mandrakesoft.com/twiki/bin/view/Main/RequestedFeatures Those with edit access on the Wiki, feel free to expand ... Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+046VrJK6UGDSBKcRAgGVAJ0ZqcAmQxnIxWJo5WtuEXKfpKTgZQCgntnI SmDSP4IRYa/oTnTHl8y5gQg= =XbiU -END PGP SIGNATURE- ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer. **
