|
![](/i/fill.gif) |
Darren New <dne### [at] san rr com> wrote:
> The easy way to set up an "image" that you can boot on an Amazon EC2
> machine is you boot one of their images, log in, make the changes you
> want (like install POV-Ray, configure it to run your render farm
> software when it boots, etc), then run a program that takes a snapshot
> of the machine and sticks it into a bootable file. The problem is that
> program winds up needing your secret Amazon passwords in order to store
> the file in a place you can boot it. So it's possible your password,
> which costs you money to use, winds up in (for example) the "Recent
> Documents" area, or the swap sector, or the command history, or
> something like that. If you don't know where and when all that magic
> gets stored, it's difficult to make sure that the image you created
> doesn't have something like that in there.
>
> Not *too* difficult, but I'd need to take a fair amount of time to make
> sure it all worked before I'd release it to someone else. :-)
>
> --
> Darren New / San Diego, CA, USA (PST)
I didn't realize that the image required your Amazon passwords and such. Thanks
for explaining it.
-Mike
Post a reply to this message
|
![](/i/fill.gif) |