I'm trying to do an install on a headless machine (a node in a cluster), and I'm having trouble figuring out what I do when stage 1 is complete. Stage 1 works just fine - I boot the installation system over the network, then ssh into the box and run yast. The installation then completes, and the machine reboots. When I ssh into it again, I can tell some Yast.Second-Stage thingie is running, but how do I get to "talk" to it to continue the second stage? /Per Jessen, Zürich
On Friday 19 May 2006 02:10, Per Jessen wrote:
I'm trying to do an install on a headless machine (a node in a cluster), and I'm having trouble figuring out what I do when stage 1 is complete. Stage 1 works just fine - I boot the installation system over the network, then ssh into the box and run yast. The installation then completes, and the machine reboots. When I ssh into it again, I can tell some Yast.Second-Stage thingie is running, but how do I get to "talk" to it to continue the second stage?
Hi Per, I'll toss an idea your way... they're cheap! ;-) I don't know if it's realistic, but here it is: If you could log into a second and third console during stage 1... even using something like screen... you could 'park' #3 in the directory where YaST writes the stage 2 boot script, leave #2 available for ad hoc commands while running YaST, as before, in #1. Once the stage 2 boot script has been written, you quickly switch to #2, suspend YaST, switch back to #3 and edit the script in such a way as to launch YaST in a session that you can log into remotely. Once the script is updated, you switch back to #2 to resume YaST and allow it to reboot. Remember, it's just a concept... I have no way of knowing how realistic it is. regards, Carl
Carl Hartung wrote:
If you could log into a second and third console during stage 1...
Yep, that's not a problem.
even using something like screen... you could 'park' #3 in the directory where YaST writes the stage 2 boot script,
Looks like /etc/init.d/
Once the stage 2 boot script has been written, you quickly switch to #2, suspend YaST, switch back to #3 and edit the script in such a way as to launch YaST in a session that you can log into remotely. Once the script is updated, you switch back to #2 to resume YaST and allow it to reboot.
Remember, it's just a concept... I have no way of knowing how realistic it is.
It might work - but surely there is a "proper" (i.e. by SUSE) way to do this? There is a Network Install page in the wiki at opensuse.org, but it's not exactly comprehensive :-( /Per Jessen, Zürich
On Friday 19 May 2006 12:21, Per Jessen wrote:
It might work - but surely there is a "proper" (i.e. by SUSE) way to do this? There is a Network Install page in the wiki at opensuse.org, but it's not exactly comprehensive :-(
/Per Jessen, Zürich
The SUSE way to do a network install is to use VNC. I've done it several times, sometimes just to avoid having to walk across the room to use the keyboard. During the first boot of the installation choose install and add the parameters: install vnc=1 vncpassword=secret Then the install continues on term 1 untill it gives you the connection parms you need to connect. then you can connect via vncviewer .... After the reboot, you connect with vncviewer again to get the rest of the dialog.... Jerry
Jerry Westrick wrote:
The SUSE way to do a network install is to use VNC.
Or ssh - it is certainly supported.
During the first boot of the installation choose install and add the parameters: install vnc=1 vncpassword=secret
I boot an etherboot-image from floppy, and then retrieve the install kernel and initrd with a similar set of parms from a tftp-server.
Then the install continues on term 1 untill it gives you the connection parms you need to connect. then you can connect via vncviewer ....
Yes, so far I have no problems.
After the reboot, you connect with vncviewer again to get the rest of the dialog...
OK, this is where I'm not sure what to do. I can connect with ssh, but how do I "get the rest of the dialog" ? When you connect with vncviewer, are you taken straight to a Yast2 window or do you need to do anything special? /Per Jessen, Zürich
On Friday 19 May 2006 14:38, Per Jessen wrote:
Jerry Westrick wrote:
The SUSE way to do a network install is to use VNC.
Or ssh - it is certainly supported.
During the first boot of the installation choose install and add the parameters: install vnc=1 vncpassword=secret
I boot an etherboot-image from floppy, and then retrieve the install kernel and initrd with a similar set of parms from a tftp-server.
Then the install continues on term 1 untill it gives you the connection parms you need to connect. then you can connect via vncviewer ....
Yes, so far I have no problems.
After the reboot, you connect with vncviewer again to get the rest of the dialog...
OK, this is where I'm not sure what to do. I can connect with ssh, but how do I "get the rest of the dialog" ?
I did that in the past, installing over ssh. The first and the second time you log in, you get directions regarding what command to type to start/continue the installation. I am certain it was like that in 9.3. Has 10.0 or 10.1 changed that much that you don't get directions of what to do after logging in with ssh? BTW, the advantage of VNC is that you can install remotely without the need of running Linux (MHO). Any VNC capable OS would do. ;) Cheers, Leen
Leendert Meyer wrote:
BTW, the advantage of VNC is that you can install remotely without the need of running Linux (MHO). Any VNC capable OS would do. ;)
Hi Leen, not much of an advantage around here - we only have Linux. I'll have to take a look at VNC one of these days, but ssh does everything I need so far. /Per Jessen, Zürich
On Friday 19 May 2006 16:19, Per Jessen wrote:
Leendert Meyer wrote:
BTW, the advantage of VNC is that you can install remotely without the need of running Linux (MHO). Any VNC capable OS would do. ;)
Hi Leen,
not much of an advantage around here - we only have Linux. I'll have to take a look at VNC one of these days, but ssh does everything I need so far.
Indeed, why use VNC if ssh does everything? (That was the point I tried to make) BTW, did you read the mail from Olaf Hering in this thread? He replied to your original mail; it seems to me it would solve your problem. Cheers, Leen
Leendert Meyer wrote:
BTW, did you read the mail from Olaf Hering in this thread? He replied to your original mail; it seems to me it would solve your problem.
Yep, I saw Olafs reply - which was just was I was after. I haven't tried it yet though, but I'll keep you all up to date :-) /Per Jessen, Zürich
On Friday 19 May 2006 14:38, Per Jessen wrote:
OK, this is where I'm not sure what to do. I can connect with ssh, but how do I "get the rest of the dialog" ? When you connect with vncviewer, are you taken straight to a Yast2 window or do you need to do anything special?
/Per Jessen, Zürich
Yep that is the case. Yast is running on the X-Windows, (it just so happens to be the VNC one and not the physical one :-) Jerry P.S. What a treat! I get to help Per! BTW "Grüsse aus Basel!", and Congrats on FCZ winning the championship!
Jerry Westrick wrote:
Yast is running on the X-Windows, (it just so happens to be the VNC one and not the physical one :-)
Ah, that does make it easier.
Jerry P.S. What a treat! I get to help Per!
My wife says I need a lot of help ... :-) /Per Jessen, Zürich
On Fri, May 19, Per Jessen wrote:
I'm trying to do an install on a headless machine (a node in a cluster), and I'm having trouble figuring out what I do when stage 1 is complete. Stage 1 works just fine - I boot the installation system over the network, then ssh into the box and run yast. The installation then completes, and the machine reboots. When I ssh into it again, I can tell some Yast.Second-Stage thingie is running, but how do I get to "talk" to it to continue the second stage?
/usr/lib/YaST2/bin/YaST2.sshinstall or /usr/lib/YaST2/startup/YaST2.ssh I did not get around to actually modifing motd to give that hint.
participants (5)
-
Carl Hartung
-
Jerry Westrick
-
Leendert Meyer
-
Olaf Hering
-
Per Jessen