Thanks for your comments, Mark. You raise a number of good points. Some comments below...
Thus spake Mark Seger ([EMAIL PROTECTED]): >As I said in my note I believed they were warnings and my installation >didn't fail so no harm was done. I just presented the notion of "what >if" it failed and am trying to get the point across that there are a lot >of places in the whole process of getting images and imaging them out >where one gets a random collection of of undefined variables and has no >idea if this is a bug, a warning or just careless programming. For all >one knows, even if the image successfully boots, what if some >configuration was done incorrectly? How is one to know? To avoid ambiguity and potential differences between image and installed client, very few configuration changes are made at installation time. And most every file that gets modified ends up listed in /etc/systemimager/updateclient.local.exclude. That being said, a client can be verified against an image by running si_updateclient with the --dry-run option. This will show you any files that are different, with the exclusion of those listed in /etc/systemimager/updateclient.local.exclude, but will not apply any changes. >IMO, with some ranting, is that SystemImager is an environment which >works most of the time but occasionally doesn't and when it doesn't >someone has to try and figure out what went wrong. I've spent many >hours tracking down undefined variable warnings only to find out it was >just careless programming which could have easily been corrected. In my estimation, most of the problems that users have experienced over the last couple of years have had to do with driver problems. That is, the standard SystemImager kernel not having the necessary driver. So, the current unstable development series (3.7.x) includes a number of big chunks of new code, many of which are related to the new UYOK (Use Your Own Kernel) support. UYOK addresses the driver issue, and will hopefully allow us as developers to spend more time addressing features and "bullet proofing" (as you mention below), rather than spending a majority of time simply trying to keep up with the latest driver support. >This >generates a lot of user frustration. Just tracking down my problems >with 3.7.3 cost me a day's worth of effort and probably a couple of >hours (or more) for you and Andrea. Please bear in mind that 3.7.3 is not a stable release. It is a development release, and it is and should be considered unstable. It may add features that some people find attractive, or even critical, but we are still working the bugs out. >A little more care on the part of >error trapping could have saved a lot of our time. My intent of >including the snippets below is to try and get that point across. If we >want SI to gain even more users it needs to be bullet-proof or when >there is a problem at least make it real clear where that problem lies >and where it doesn't but not having random warnings that look like >errors. I totally agree with this, Mark. It's probably worth noting that this error you are seeing is from part of the UYOK code (files in /dev/ error). I've added an item to the TODO list to handle this kind of harmless error message gracefully. >But just to be clear, I'm a big fan... That's also good to hear. :-) And if you have more error output that you think would be useful to us in squashing bugs prior to a stable release, or even suggestions for modifications to certain code snippets, that'd be most appreciated too. Thanks, -Brian >-mark > >Bernard Li wrote: > >>Hi Mark: >> >>Those are just warnings. >> >>It would help if you post detailed log message regarding how your image >>install fails. >> >>Cheers, >> >>Bernard >> >> >> >>>-----Original Message----- >>>From: [EMAIL PROTECTED] >>>[mailto:[EMAIL PROTECTED] On >>>Behalf Of Mark Seger >>>Sent: Wednesday, July 05, 2006 13:05 >>>To: [email protected] >>>Subject: [Sisuite-devel] more warnings/errors with 3.7.3 >>> >>>I just ran prepareclient on a new, rhel4/update3 system and >>>got errors >>>once again, are these serious or not? I'm guessing they're not, but >>>later on if my install image fails, how am I to know whether it's a >>>problem with the server of the way I generated the client? >>> >>>Continue? (y/[n]): y >>>Signaling xinetd to restart... >>>Using "sfdisk" to gather information about disk: >>> /dev/cciss/c0d0 >>> >>>Use of uninitialized value in hash element at >>>/usr/lib/systemimager/perl/SystemImager/Common.pm line 1237, >>><FH_IN> line 8. >>> >>>then later on... >>> >> tar -C /tmp/.systemimager.0 -cf - . | tar -C >>>/tmp/.systemimager.1 -xf - >>>tar: ./dev/gpmctl: socket ignored >>>tar: ./dev/log: socket ignored >>> >>>-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-devel mailing list >>>[email protected] >>>https://lists.sourceforge.net/lists/listinfo/sisuite-devel >>> >>> >>> > > >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-devel mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/sisuite-devel -- Brian Elliott Finley Mobile: 630.631.6621 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
