I dont know why I was doing things this way.  I ended up creating a filesystem locally using yum and moving it up to server vs installing it on the server via Whitebox's install method.  Thanks for your help!  I still have a console related issue with the new installation.  As it sits right now, it spawns several xterms from which I can log into my system.  I start my guest with:
screen -d -m -S wbl ./linux-2.6.8 \
  mem=256M \
  ubd0=root_fs \
  ubd1=swap \
  eth0=tuntap,,,192.168.0.253 \
  con0=fd:0,fd:1 con1=pty

It should be noted that I start my guest via ssh.  I want everything to be in my ssh window, including my login prompt.  I had this working at some point on an old installation but of course cant remember how I started that guest.

This appears to stop the xterms but my login prompt never appears in my ssh console, it just halts after init starts everything:

screen -d -m -S wbl ./linux-2.6.8 \
  mem=256M \
  ubd0=root_fs \
  ubd1=swap \
  eth0=tuntap,,,192.168.0.253 \
  con0fd:0,fd:1 con1=pts con2=pts con3=pts con4=pts con5=pts con6=pts

Thanks again for any assistance.



On 6/22/05, Terry <td3201@gmail.com> wrote:
I dont know why I was doing things this way.  I ended up creating a filesystem locally using yum and moving it up to server vs installing it on the server via Whitebox's install method.  Thanks for your help!

On 6/21/05, Jeff Dike < jdike@addtoit.com> wrote:
On Tue, Jun 21, 2005 at 06:51:02PM -0500, Terry wrote:
> Yes, that would make a lot of sense. Of course, I don't have that. Any
> special way to go about creating one?

mknod, just make it look like the host's console.  But what else is your /dev
missing?

If it's a former devfs empty /dev/, you'll need block devices, ttys, null,
and a bunch of other things.

                                Jeff