Server category

Now Ubuntu are stable enough to use it in enterprise, but it can not replace Windows because of lack Active Directory features. Main of AD feature is admin can configure all network from ONE server, and all configuration stores in ONE place and have the same userID for all network.

Ubuntu can do the same but it need to have common configuration repository and main programs must get config from this repo.


It is hard to change all software in Ubuntu to use common config-API, but Canonical can change their own soft (Bazaar, etc). Then prepare soft that can configure it.

This will be great step towards usability and admin frendship. Also this will add marketing points to Ubuntu, because neither Windows not other linux distro (RHEL, etc) have same functionality. SuSE have Yast, but it is not the same.

Ubuntu and Canonical as a big Linux player can begin this great task, and help Open Source projects create ONE configuration API and move to using it.

May be you should look at gconf first and another tools next. And begin to migrate Cannonical own products to this common conf API, then help other projects.

This IDEA will easily fix http://brainstorm.ubuntu.com/idea/68/ and so on.

Why dont we have a program in the Ubuntu server through which we can create and maintain a number of virtual OS.
The different advantage of the program may be,
1) Testing professionals: for testing in different OS environments
2) IT professionals: they could create different OS in a single system and could provide to the required user remotely. This considerably reduces the number of individual hardware and also saves lot of power.

There could be an immense advandage over other OS if this particular application or program is combined with Ubuntu.

.htaccess is a file that contains "directives" telling the Apache server how to behave under certain circumstances. It's the file that tells the server how to handle "404 not found" errors, whether to requre a password for certain directories and files, etc, etc. there are many, many ways these directives are useful and necessary. It provides basic "doorman security" to a website. If it is written badly i.e. contains mistakes, the results can be serious.

It would be useful to have a wizzard to walk the developer thru the creating/maintenence of this file. It could live on the server in a (password protected!) directory, or be a local application that creates the .htaccess file to be uploaded. It could also include an .htpasswd generator.