Mark Post wrote:
On Thu, Mar 1, 2007 at 7:36 AM, in message
<[EMAIL PROTECTED]>, John Summerfield
<[EMAIL PROTECTED]> wrote:
-snip-
It shouldn't be hard to hook a mkswap command into /etc/inittab, to run
before (almost) everything else and do away with this "ipl cms first" caper.
or even in /linuxrc (in the initial ram disk).
That's certainly possible, but it would a rather Bad Idea [tm]. Why _modify_
every single guest you install when you can have a standardized startup script
in CMS to accomplish the same thing, and you only have to do it once? Setting
up the VDISK isn't the only thing that falls into that category.
If you're using any kind of deployment tools, it gets done once: in the
master if you're cloning, in the kickstart file if you're using
Anaconda. If you're using any kind of configuration management tools,
you could to it there, once, when you set a new system up.
I don't see that adding something into /etc/inittab is worse than doing
it in CMS; it seems to me to have some advantages, it might start
quicker, it doesn't _rely_ on VM/CMS. It works the same, whoever IPLs
your penguin.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
