I think I finally got to the bottom of my question in the previous note - it looks like the errors don't do any harm because all they do is define the variable $part which I think is only used for display purposes. This really should be cleaned up because it does look like something is very wrong when it isn't.
That said I tried to install an image. This time it bombed out in the very beginning of the install script where it looks at /proc/diskstats or /proc/partitions. This is 2.4.25-boel and so it looks in /proc/partitions only there aren't any entries and so the script doesn't see any devices. Any thoughts how that might happen? I was wondering if I might have the wrong version of boel installed, but here's what I show: [EMAIL PROTECTED] systemimager]# rpm -qa | grep systemimager systemimager-common-3.6.3-1 systemimager-i386boot-standard-3.6.3-1 systemimager-server-3.6.3-1 and here's boel itself -rw-r--r-- 1 root root 4771267 Apr 14 11:24 /usr/share/systemimager/boot/i386/standard/boel_binaries.tar.gz Also, if I do 'ls /dev/cciss' there's nothing there either Any suggestions on how to proceed would be appreciated... -mark 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 _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
