[Sisuite-users] Re: found bug in Server.pm

[Mark Seger]

Thinking about this some more AND trying to move this forward with a solid recommendation.  My original thought had been to patch SystemComfigurator, but what if SC is called outside of the SystemImager context?  Architecturally, since SystemImager is the source of the problem SystsemImager should be responsible for fixing it.  Furthermore, since this problem only exists during the execution of the autoinstall script until the system reboots, ANY code thay may be added to that script that uses 'df', be it SystemImager future enhancements or unsuspecting slobs like me, won't have a clue what's happening. Therefore I recommend the following: - BIG comment in autoinstall script that /etc/mtab is empty and commands that depend on it like 'df' will fail. - add some code that rebuilds /etc/mtab, later on in the script (and I'm not sure where the best place is to do this, but perhaps right after the rsync calls), put in a line of code also with a BIG comments,  that tests for a zero length mtab and if found recreates it.  As to how to recreate it, since we're only worried about available file systems perhaps "grep ext /proc/mounts> /etc/mtab" wil be sufficient. Can anyone offer any opinions why this isn't a good idea?  Is there any reason why this fix can't go into the next point release? -mark Message: 1 Date: Wed, 19 May 2004 07:57:33 -0400 From: Mark Seger <[EMAIL PROTECTED]> Organization: Consulting and Architecture To: [EMAIL PROTECTED] Cc: dann frazier <[EMAIL PROTECTED]> Subject: [Sisuite-users] Re: found bug in Server.pm Reply-To: [EMAIL PROTECTED] This is a multi-part message in MIME format. --------------090001010806080607080705 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Whats interesting, is that recently I had a problem with grub-install in which the golden image did not have any mtab file and I simply created an empty one. This caused systemconfigurator to work properly, just touching that file. I wonder why in that instance having a blank file worked? We should find the answer to this question before we implement a fix. This could prove to be a "stupid easy" fix, if what you say will work consistently. Can you find out _why_ this worked? Just so people don't spend endless hours (like I have been doing) trying to make systemconfigurator work is to see what it takes to make 'df' work as that's the root problem. grub-install does this ni the find_device funtion as follows: tmp_fname=`df $1/ | sed -n 's%.*\(/dev/[^ ]*\).*%\1%p'` Just as another data point, I thought dann frazier had said SystemImager DID work with grub and the only problem that remained was getting it to work with the SmartArray. dann - did I misunderstand? This particular bug doesn't feel like it has anything to do with SmartArrays -dann