Hello, I would like to enforce some rules for the naming of oscar hostnames and commands.
For the moment, there are several conventions. For instance, for hostname, there is : oscar_server nfs_oscar and pbs_oscar I think that the idea to specify the oscar name before is interesting and therefore have the oscar_server oscar_nfs (instead of nfs_oscar) oscar_pbs (instead of pbs_oscar) Is everyone OK with the idea ? This will allow us to have similar convention for the CLI provided by OSCAR. Well, the question is asked because we are currently adding oscar_ldap (or ldap_oscar ;-) and so this question arise "naturaly". For the oscar tools and commands, the same kind of logic should be used. Because of tab completion, I think that the "oscar" part should come first. However, being a lazy sysadmin, oscar is maybe too long. What about prefixing all oscar defined commandas by "o_". For instance "opd" -> "o_package_downloader" "install_cluster" - > "o_install_cluster" ... This approach is coherent with the hostname convention (while shorter ;-)) and allow an admin to quickly find the oscar related commands by typing "o_" + <tab> (for bash, can differ in other shell). Ben -- Benoit des Ligneris Etudiant au Doctorat -- Ph. D. Student Web : http://benoit.des.ligneris.net/ Mydynaweb Developpe(u)r: http://mydynaweb.net/ Centre de Calcul Scientifique http://ccs.USherbrooke.ca/ OSCAR Symposium-May 11-14 http://oscar2003.ccs.USherbrooke.ca/ ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
