> Hostname :
> nfs_oscar -> oscar_nfs_home > pbs_oscar -> oscar_pbs
Absolutely I agree on these.
I've always said the main installation/maintanance program should be named oscar.> Applications : > install_cluster -> oscar
I don't agree with that, not as a blanket rule. Oscar is all about pulling in best practices for cluster software. It is not about re-writing all the software that is put into/installed with oscar. Commands that are part of oscar should not be all named oscar_*, this would mean we can't attract outside packages.> Everyone seems to agree with the general rule to prefix all oscar > commands by "oscar" so that everyone will be able to easily know which > oscar commands are available on his system.
> However, I think that the core packages should show the example and
The binary for oda that is installed with the oda rpms will be named oda. If we want to have an oscar_database symbolic link to it, fine.> implement the naming conventions ;-) Those name are only meaningfull for > OSCAR developpers ! Users (I know some of them ;-) and even some > developpers asked some questions about those abreviations. I even > thought that oda was "OSCAR database abstraction" (instead of OSCAR > database) !!! > > Question 1 is : should opd be renamed "oscar_package_downloader" ? > Question 2 is : should "oda" renamed "oscar_database" ?
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
