Hi All! I've recently submitted a question about the UYOK option of the systemimager to the users list. I was advised to try oscar 5, and to use this list for further questions. I've managed to install oscar5 but I've had problems installing it. I don't know if these are bugs or features, but I thought I'd report them anyway. Here's a description of my adventures:
We are using RHEL4.2. The nodes are SUN X4100. We need the UYOK option because the scsi adapter on the x4100 needs drivers. Because of the UYOK thing, we used an x4100 as a server also. - The server had an oscar4.2 installation on it and that collided with the oscar5 installation, though we tried the start_over script. We decided to do it on a fresh linux installation. - I remembered from previous versions that the install_cluster script installs all the required RPMS that come with oscar (systemimager and such). It did not, and it didn't even give a proper error message. We installed the packages manually, though we had to guess which were needed through the error messages of missing perl scripts etc. This wasn't documented in the README or install guide. - After install_cluster finally brought up the gui, there was a problem with the installation of lam in the "install server packages" stage. It demanded some prerequisites, even after ee've installed them manually. We had to give up on lam (don't need it anyway). - UYOK worked great (had to install syslinux manually, of course). - We used the scsi.disk sample that comes with oscar. It names partitions 5 and 6. Problem was that the initrd that the systemimager created only has /dev/sda1-3. Our workaround was to add mknod commands to the installation script. I guess these files can be aded to the initrd image itself also. - Of course we needed a proper initrd in the image itself too. systemconfigurator creates an initrd file on the image, but for some reason it did not contain the proper modules. We added a [HARDWARE] directive to the systemconfigurator configuration file that's found inside the installation script, but that did not work. I thought kernel_picker takes care of the initrd on the image, but when we executed it, it didn't touch the initrd. It also created in the image a link to the Systemap that points to /val/lib/syste.../images/.../boot/Systemap-... which is of course a mistake. We copied the initrd from the server to the image, but systemconfigurator naturally points to its own created initrd file, so we had to add a [KERNEL] directive to the systemconfigurator configuration file that's found inside the installation script. - After installing an image to the node, there is a file created in the /tftpboot/pxelinux.cfg directory that overrides the /tftpboot/pxelinux.cfg/deault file. The content of this file is erroneous and the machine cannot have further pxe boots until this file is erased (or modified). I also have a related question. I want to keep on the same server differnet images for different architectures. This means that the network boot will be done using different kernels and initrd files. How do I separate these groups of nodes in the pxelinux.cfg? Thanks a lot! ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
