http://bugzilla.novell.com/show_bug.cgi?id=502930 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=502930#c7 --- Comment #7 from Scott Couston <alpha096@virginbroadband.com.au> 2009-08-03 23:08:15 MDT --- I would just us to comment under this bugs context that we... seriously need to reconsider our current default unattended installation. I dont know why we want to re-invent the wheel or rewrite history. History made it quite clear in the low 90'2 that the market would not put-up with unattended installations. Unattended Installations were completely abandoned in 95, but remained optional along with admin installations and client installations. I think we need to concentrate on auto Yast instead of any default unattended installations. Let some one else spend millions on market research and usability issues. I am not suggesting that we follow, but we need to learn free lessons from history as our market has NOT changed and is not going to in the near future. We need to stop making technocratic decisions and base everything we do on past demonstrated usability mistakes. We know quite clearly that hardware vendors will no longer be dictated to, nor large companies of late. The continued attitude that an O/S will dictate to Hardware is over! This sounds loud and clear and hit at immeasurable expense to other O/S. Large companies also joined in ringing this bell. No one wants to commit corporate suicide with a new or different O/S or environments. Usability is everything! We keep our current users close and our oppositions closer. With respect to the answer in comment #5...I describe 'failure' as any early termination of the GUI installation that a re-boot can not recover nor solve. One of the problems is we write the user preferences to swap in a automated installation (I think is swap) and if we re-boot we still recover those same images so the error that caused the 'failure' will still occur. I would suggest that if an installation 'fails' we flush the swap and reboot the PC, and pick up on the Installation where set decision have been made and then continue, rather than currently re-boot and re-read the image in swap that caused the 'failure' in the first instance. Please let me know if I have made any unsound technical statements about the writing of installation setup files based on environment above. I used a lot of logic in this comment, but perhaps my limitation on actuals may not be sound...;-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.