RHEL4 update 3 (both amd-64 and i386) works fine using kickstart over http. Installed several servers so far. But you need to keep one thing in mind if you are dealing with HP servers with RAID controllers (though DL140s I don't think have RAID controllers), refer to the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187093 This is still true and reproducable every time I want to reproduce it. Surprisingly there is no update on it so far. Regards. Ajitabh Pandey -----Original Message----- From: kickstart-list-bounces@xxxxxxxxxx [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Dag Wieers Sent: 11 August 2006 06:48 To: Discussion list about Kickstart Subject: RE: Kickstart fails mounting nfs source On Thu, 10 Aug 2006, Elizabeth.Brosch@xxxxxxxxxxx wrote: > On Thu, 10 Aug 2006, Chip Shabazian wrote: > > > What version/update are you building from? > > > > Can you access the nfs mount if installing manually (not doing ks on > > the boot line)? > > I am building from RHEL v4 Update 3. Also, unfortunately I do not > have another server in this VLAN that I can test the NFS from. I have > 12 servers in this VLAN. The first one I manually installed then > configured for kickstart/dhcp/tftp. > > I am booting from CD #1 for the second server and entering "ks". I find HTTP much easier to use and debug. It might be slightly different now that NFS is using TCP. But only having to ask for tcp/80 to be opened in one direction and being able to check a log-file for troubleshooting is worth my time :) The same firewall rule is then used for installing updates using apt (although in some environments we set up a remote tunnel using SSH). Kind regards, -- dag wieers, dag@xxxxxxxxxx, http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list This email is confidential and intended solely for the use of the individual to whom it is addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of Broadcasting Dataservices. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error please notify the sender