On Wed, 22 Jan 2003, Benoit des Ligneris wrote:
> 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)
This sounds good to me.
> 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"
> ...
I'd prefer "oscar_". Especially since we decided at IU that
"install_cluster" will go away, in favor of a top-level "oscar" command.
So you invoke "oscar" to install your cluster, and [eventually] also
invoke "oscar" to get into maintenance mode.
I think "oscar_" vs "o_" is more meaningful. And it's the same number of
keystrokes.
"os<tab>" on my MDK 9.0 box reveals 4 (very obviously non-OSCAR) commands.
But let's go for uniqueness -- "osc<tab>" shows no commands. So 4
keystrokes for uniqueness.
"o<shift>-<tab>" is also 4 keystrokes. So I'm in favor of "oscar_"
because it's more obvious that those are OSCAR-related commands.
--
{+} Jeff Squyres
{+} [EMAIL PROTECTED]
{+} http://www.lam-mpi.org/
-------------------------------------------------------
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
