This sounds very interesting:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
It would get me around my limitations on the screen on the OQO. And the instructions read rather well.
Only thing I don't know how to do is have vncviewer in 'listen' mode.
On Wed, Sep 24, 2008 at 11:27:21AM -0400, Robert Moskowitz wrote:
This sounds very interesting:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
It would get me around my limitations on the screen on the OQO. And the instructions read rather well.
Only thing I don't know how to do is have vncviewer in 'listen' mode.
vncviewer -listen
:-)
On 24/09/08 8:27 AM, "Robert Moskowitz" rgm@htt-consult.com wrote:
This sounds very interesting:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
It would get me around my limitations on the screen on the OQO. And the instructions read rather well.
Only thing I don't know how to do is have vncviewer in 'listen' mode.
Hey Robert,
I am the one that wrote that wiki article. How to put the client into listen mode depends on which VNC client you are using, and on what platform.
I would just have a quick read over the docs for your vnc client.
So for example if you are using the linux client, I am sure there is a CLI switch, or if you are using one of the win clients, there is usually a shortcut for the listening mode in the start menu.
DNK
First try did not work....
dnk wrote:
On 24/09/08 8:27 AM, "Robert Moskowitz" rgm@htt-consult.com wrote:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
Only thing I don't know how to do is have vncviewer in 'listen' mode.
I am the one that wrote that wiki article. How to put the client into listen mode depends on which VNC client you are using, and on what platform.
Building the CD was relatively easy. BTW, if you copy the Centos 5.2 1of6 iso image to a system with gnome, Nautlius 'open with Archive Manager' makes it trivial to extract all the files from the image. The rest of your build instructions were easy to follow. I am using:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
above is all one long line....
For my setup. Where the real IP address I am using is what I got from ifconfig on my notebook.
I have 'vncviewer -listen' running in a terminal window on my Centos notebook, and it reports to be listenting on port 5500. 'iptables -L' reports ACCEPT for fcp-addr-srvr1 (which google tells me is port 5500), and I have opened port 5500 within my Intranet.
Boot from CD (there is actually a screen on my OQO, but at only 800x480, I would not know if there was something at the bottom of the display) and I watch it start up and proceed all the way to the Centos5 X screen and sit there. Nothing on the client. Guess I am going to have to open a monitor port on the switch the OQO is plugged into and watch with tcpdump to see if anything is actually happening.
hmmm, for the 'heck of it', I pressed <altN> and the install took off. Asked me what language and such I wanted (the 'standard' two dialog windows). The third <alt-N> brought me to Disk Druid. That kernel line is NOT working quite right. It is clear the changes to the first two lines 'took':
prompt 0 timeout 0
As the install did not wait for any command line input. So what is wrong with that kernel line? I editted isolinux.cfg with gedit, and I just looked at the file on the iso build server with vi and it shows that as all one line. What is wrong here? Should I break out wireshark, or is there a problem with:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
where 1.2.3.5 is really the IP address of my client system. and me.htt-consult.com replace with the fqdn of my repo server (this works just fine with a 'linux askmethod').
on 9-25-2008 12:31 PM Robert Moskowitz spake the following:
First try did not work....
dnk wrote:
On 24/09/08 8:27 AM, "Robert Moskowitz" rgm@htt-consult.com wrote:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
Only thing I don't know how to do is have vncviewer in 'listen' mode.
I am the one that wrote that wiki article. How to put the client into listen mode depends on which VNC client you are using, and on what platform.
Building the CD was relatively easy. BTW, if you copy the Centos 5.2 1of6 iso image to a system with gnome, Nautlius 'open with Archive Manager' makes it trivial to extract all the files from the image. The rest of your build instructions were easy to follow. I am using:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
Change the above to ; kernel vmlinuz (crlf) append initrd=initrd.img ramdisk_size=8192 upgradeany vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us (with the append line being one line) You can leave out the upgradeany command, it has been in there for a long time and I don't do upgrades very often.
above is all one long line....
For my setup. Where the real IP address I am using is what I got from ifconfig on my notebook.
I have 'vncviewer -listen' running in a terminal window on my Centos notebook, and it reports to be listenting on port 5500. 'iptables -L' reports ACCEPT for fcp-addr-srvr1 (which google tells me is port 5500), and I have opened port 5500 within my Intranet.
Boot from CD (there is actually a screen on my OQO, but at only 800x480, I would not know if there was something at the bottom of the display) and I watch it start up and proceed all the way to the Centos5 X screen and sit there. Nothing on the client. Guess I am going to have to open a monitor port on the switch the OQO is plugged into and watch with tcpdump to see if anything is actually happening.
hmmm, for the 'heck of it', I pressed <altN> and the install took off. Asked me what language and such I wanted (the 'standard' two dialog windows). The third <alt-N> brought me to Disk Druid. That kernel line is NOT working quite right. It is clear the changes to the first two lines 'took':
prompt 0 timeout 0
As the install did not wait for any command line input. So what is wrong with that kernel line? I editted isolinux.cfg with gedit, and I just looked at the file on the iso build server with vi and it shows that as all one line. What is wrong here? Should I break out wireshark, or is there a problem with:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
where 1.2.3.5 is really the IP address of my client system. and me.htt-consult.com replace with the fqdn of my repo server (this works just fine with a 'linux askmethod').
If you are going to do a remote install source, just use the netboot cd image. It is much smaller, and doesn't have to deal with the media check.
I do installs like this all the time on headless servers in my site.
Scott Silva wrote:
on 9-25-2008 12:31 PM Robert Moskowitz spake the following:
First try did not work....
dnk wrote:
On 24/09/08 8:27 AM, "Robert Moskowitz" rgm@htt-consult.com wrote:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
Only thing I don't know how to do is have vncviewer in 'listen' mode.
I am the one that wrote that wiki article. How to put the client into listen mode depends on which VNC client you are using, and on what platform.
Building the CD was relatively easy. BTW, if you copy the Centos 5.2 1of6 iso image to a system with gnome, Nautlius 'open with Archive Manager' makes it trivial to extract all the files from the image. The rest of your build instructions were easy to follow. I am using:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
Change the above to ; kernel vmlinuz (crlf) append initrd=initrd.img ramdisk_size=8192 upgradeany vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us (with the append line being one line) You can leave out the upgradeany command, it has been in there for a long time and I don't do upgrades very often.
And what about the ramdisk_size=8192? Seems I have seen that somewhere, but it is not on the current append initrd.... line in the .cfg file.
above is all one long line....
If you are going to do a remote install source, just use the netboot cd image. It is much smaller, and doesn't have to deal with the media check.
What does that save me? I already have the 1of6 iso image here...
I do installs like this all the time on headless servers in my site.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
on 9-25-2008 1:09 PM Robert Moskowitz spake the following:
Scott Silva wrote:
on 9-25-2008 12:31 PM Robert Moskowitz spake the following:
First try did not work....
dnk wrote:
On 24/09/08 8:27 AM, "Robert Moskowitz" rgm@htt-consult.com wrote:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
Only thing I don't know how to do is have vncviewer in 'listen' mode.
I am the one that wrote that wiki article. How to put the client into listen mode depends on which VNC client you are using, and on what platform.
Building the CD was relatively easy. BTW, if you copy the Centos 5.2 1of6 iso image to a system with gnome, Nautlius 'open with Archive Manager' makes it trivial to extract all the files from the image. The rest of your build instructions were easy to follow. I am using:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
Change the above to ; kernel vmlinuz (crlf) append initrd=initrd.img ramdisk_size=8192 upgradeany vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us (with the append line being one line) You can leave out the upgradeany command, it has been in there for a long time and I don't do upgrades very often.
And what about the ramdisk_size=8192? Seems I have seen that somewhere, but it is not on the current append initrd.... line in the .cfg file.
Like I said it has "been around the block" and was first used on CentOS 4 since I think it was the first one to have the vnc option. When I first started using it, the ramdisk size was too small to work properly. I don't know if the defaults are different, but it doesn't hurt as I did an install with it about 2 weeks ago on a 64 bit server with CentOS 5.
It is working.....
Got through disk druid to set the drive how I like, then did the desktop setup.
It is now formatting the drive, and should be all installed before long. Then the updates :)
And finally fix up the anaconda-ks.cfg so I can use it to build the other 3 the same way...
Scott Silva wrote:
on 9-25-2008 1:09 PM Robert Moskowitz spake the following:
Scott Silva wrote:
on 9-25-2008 12:31 PM Robert Moskowitz spake the following:
First try did not work....
dnk wrote:
On 24/09/08 8:27 AM, "Robert Moskowitz" rgm@htt-consult.com wrote:
http://wiki.centos.org/TipsAndTricks/VncHeadlessInstall
Only thing I don't know how to do is have vncviewer in 'listen' mode.
I am the one that wrote that wiki article. How to put the client into listen mode depends on which VNC client you are using, and on what platform.
Building the CD was relatively easy. BTW, if you copy the Centos 5.2 1of6 iso image to a system with gnome, Nautlius 'open with Archive Manager' makes it trivial to extract all the files from the image. The rest of your build instructions were easy to follow. I am using:
kernel vmlinuz vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us
Change the above to ; kernel vmlinuz (crlf) append initrd=initrd.img ramdisk_size=8192 upgradeany vnc vncconnect=1.2.3.5 headless ip=dhcp ksdevice=eth0 method=http://me.htt-consult.com/centos/5.2/os/i386 lang=en_US keymap=us (with the append line being one line) You can leave out the upgradeany command, it has been in there for a long time and I don't do upgrades very often.
And what about the ramdisk_size=8192? Seems I have seen that somewhere, but it is not on the current append initrd.... line in the .cfg file.
Like I said it has "been around the block" and was first used on CentOS 4 since I think it was the first one to have the vnc option. When I first started using it, the ramdisk size was too small to work properly. I don't know if the defaults are different, but it doesn't hurt as I did an install with it about 2 weeks ago on a 64 bit server with CentOS 5.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
dnk -
Ray Van Dolson -
Robert Moskowitz -
Scott Silva