Karanbir Singh - Thinkability - Latest Comments on Upgrading to CentOS4, over a remote vnc connection

Edward [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

Edward [Visitor] — Tue, 28 Dec 2010 18:52:43 +0000

Hello! After the CentOS install, it asks for reboot(after os installation) then my machine isn't booting up right, what to do?

Charles [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

Charles [Visitor] — Wed, 27 Aug 2008 21:17:49 +0000

Greetings,
The kernel argument limitation is in lilo. You can get around it by upgrading to grub before doing the installation.

Another useful nugget of information: to avoid problems with device re-ordering, you can specify a MAC address in the ksdevice argument (at least as of the RHEL4 pxeboot image, not tested with earlier versions).

Bruno Klaus [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

Bruno Klaus [Visitor] — Wed, 30 Apr 2008 15:27:43 +0000

Thanks for your quick replay.
Yes, it works! You safed me hours with this...

I will include you in my prayers!

regards, Bruno

Karanbir Singh [Member] in response to: Upgrading to CentOS4, over a remote vnc connection

Karanbir Singh [Member] — Wed, 30 Apr 2008 14:54:59 +0000

Bruno, when you setup your remote install process - you can specify a kickstart over a http url in the comment line, so just add something like this :

ks=http://somewhere.com/ks.cfg

and it will run with that kickstart. Ofcourse, you need to make sure that the ks.cfg works perfectly with no user intervention required :D

Bruno Klaus [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

Bruno Klaus [Visitor] — Wed, 30 Apr 2008 12:57:30 +0000

What a great idea! It works perfectly for me (upgrade of C4.4 to C5.1)
One question: is it possible to make this completely unattendet?

If we stage the machine inhouse, we use pxe and kickstart.cfg files, s the install process is fully automated. It would be very nice, if this is also remote possible.

Have I to put the ks.cfg file also in /boot?

Thanks for this excellent guide!

regards, Bruno

General Failure [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

General Failure [Visitor] — Wed, 02 Apr 2008 17:08:39 +0000

Just finished a fresh install of CentOS5 over the internet using your method and worked absolutely brilliantly!!

You are a *. Saved me several hours of travel to fix the server. Superb instrcutions.

David Stockton [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

David Stockton [Visitor] — Thu, 21 Feb 2008 12:13:38 +0000

Just done a CentOS 4.4 Server CD to CentOS 5 remote vnc installation using this method and it worked like a charm.

Thanks!

Kai [Visitor] in response to: Upgrading to CentOS4, over a remote vnc connection

Kai [Visitor] — Sun, 14 Oct 2007 22:55:37 +0000

Make sure that your append command line (all that *behind* the append command) is no longer than 255 characters. Anything after that gets truncated. So, if you happen to have your method URL at the end and it fails because it cannot retrieve stage2.img then this is likely the cause: it got truncated somewhere in the middle of the URL.
According to http://syslinux.zytor.com/archives/2005-February/004816.html all newer kernels should be able to accept longer append lines if configured/compiled to do that. As they do use boot protocol 2.02+ which apparently allows this length. But either the pxeboot code or the syslinux kernel or both on the RH/CentOS installations is not prepared to handle that.