On 31/10/10 22:12, Arno van der Veen wrote:
> <[email protected]> wrote:
> 
>> Guys,
>>
>> Just an FYI. I work in support , and if you modify the scripts , you
>> risk damaging your data , and do u think your firms would appreciate
>> your calling us , with a severity 1 , and at a data loss ?
>>
>> You risk warranty , as if you try to work around things , its not
>> supported.
>>
>> What would make more sense , is a constructive email , with precise
>> actions , like what you want to change , why , your hardware config ,
>> etc etc , and if it made sense , it could be reviewed and possibly
>> actioned .
>>
>> I am saying that valid feedback , with precise details , can be fed
>> back to product support.
>>
>> Thanks for listening
>> jeff

Jeff,

I have done just that. I reported this issue several months ago. I
opened a ticket with support about it. But it's still not resolved.

I share Tim Small's sentiment:

On 31/10/10 14:55, Tim Small wrote:
> Don't use Dell's buggy, overly-complex scripts (self-extracting shell
> scripts, which then install RPMs - makes me feel nauseous just thinking
> about the concept - what do you think this is?  Microsoft Windows?) -
> get the file out of them, and run the update manually instead using
megactl?

Any self-respecting admin will *not* blindly run shell scripts *as root*
which unpack a self-contained payload and perform actions which are not
auditable in advance.

I'm glad that Dell provide firmware updates and support hardware updates
under Linux, but really you could make the process an whole lot easier.

I personally mirror your repos and my firmware update process is
something like:

yum install $(bootstrap_firmware)
update_firmware --yes

Why do't you consider making that the "official" supported mechanism?

R.
-- 
"Feed that ego and you starve the soul" - Colonel J.D. Wilkes
http://www.theshackshakers.com/

_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Reply via email to