Comment 7 for bug 434693

> > Because we're building just one image, and people use this same image as
> > the base for all kinds of different things on EC2. We don't want to
> > force a web-, database-, or anyting else-server down everone's throats,
>
> That's not at all what ec2-init is doing, though, and thus doesn't
> answer my question at all. The init script I was talking about
> doesn't deal with databases and that stuff, it does some static
> general things like installing binutils, ruby packages with apt-get,
> installing ruby gems, symlinking stuff around, etc. All those seem
> to be part of every EC2 image, so I asked why this setup can't happen
> when you build the "one" image, instead of running at first boot in a
> very questionable way?

I think I've found the problem.
a.) I'm probably not doing a great job of explaining myself. thats not
new.
b.) I really wish that rightscale-init script wasn't in the package that
you reviewed. But I'm glad that Martin took the time to point it out.

Above, when Martin said "The init script I was talking about" he was
referring to 'rightscale-init'. See debian/ec2-init.rightscale-init.init
(http://tinyurl.com/ydxp8c5). It should not be there. And, in bug
434181, I even convinced the rightscale developers of that.

However, at grave risk of confusing things, I want to point out that this
script is an example of one that might be via ec2 user data to ec2-init
(ec2-run-user-data.py)

So, I will get rightscale-init removed from the package, and clean up the
other issues that you pointed out.