On Sat, Aug 19, 2006 at 09:02:51PM +0200, Henning Sprang wrote:
> If you'd like to include your own role scripts you'll need to
> create $dist.d/role.d/foo - then specify "--role=foo" when you're
> creating your new instance.
>
> I like the idea of adding some simple stuff to my systems, but here
> it's not clearly said where $dist.d/roles.d needs to be as an absolute
> path. From what I read in code, I understand it can only be in
> /usr/lib/xen-tools.
Yes, that is correct. I will update the manpage to list the complete
path.
> I don't think this is a good idea to place user/admin-edited data there.
> Something in /var or /etc/xen-tools would be a better place for these, I
> think.
Honestly I'd kinda agree, but in the past I found there were problems
with having things in /etc. Merge conflicts due to CVS identifiers,
etc.
Since the roles and scripts generally, are arch-independant and
not generally user-editable it makes sense to keep them where they are.
I could perhaps create symlinks from /etc/xen-tools to matcH:
/etc/xen-tools/debian-hooks.d/ -> /usr/lib/xen-tools/debian.d/roles
etc.
However I'm not sure that improves the situation very much.
Having just one role directory doesn't really work so well since it
is possible that multiple distributions might need different scripts
to do a job - it would be unfair to have to expect a role-writer to
have to code their script for all distributions, or test for it.
eg:
#!/bin/sh
# /etc/xen-tools/role.d/
#
case "$1" in
debian)
blah ...
;;
centos)
blah ..
;;
esace
99% of people probably only care about one distribution so having
per-dist roles seems to offer least suprise.
Steve
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
