> 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).
Sure, it's possible, but why reinvent the wheel if there's a trivial solution waiting to be used? If you want to do some setup in the virtual machine first (like coupling network adapters to the right lans, setting performance options, etc), it's a lot easier to do it CMS than in Linux -- get it set the way you want it, and then all Linux has to do is detect it and use it. You also don't have to mess with the startup process or /etc/inittab and propagate that between releases, which, given the spotty support from the distributors, if you can claim "it's exactly as you shipped it", you can take a lot of noise right out of the support discussion. In fact, if you DO mess with the startup, you probably invalidate your support agreement, so unless you're prepared to go it on your own, I'd say it's a lot better to use the tools you've got and not try to reinvent the startup logic. ---------------------------------------------------------------------- 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
