On Wed, 2007-10-17 at 07:13 +0530, Kenneth Gonsalves wrote:
On 16-Oct-07, at 7:27 PM, Gabin Kattukaran wrote:
List out your requirements and we'll (or at leat, I'll ) set it up for you with a word of honour that your install will run without any hicouhgs for a mutually agreed pre-determined duration.
he is not talking about *his* install. He deals in hardware and is talking about his frustrations in trying to get his customers to switch to linux without losing his customers. So you need to go along with him to his customers and make them happy
That makes it a little more complicated, doesn't it?
So, let's see if this can be done in a more structured manner. (Clearly, exchanging anecdotes won't get us anywhere.)
There appears to be two clear kinds of issues.
The first - my linux app does not behave in a manner similar to my windows app. This, as pointed out by JTD, is not really a linux problem or even a problem at all. No two apps even on the same platform can't be expected to present identical interfaces. Each app has its own vision, philosophies, goals etc. As a user, you pick the app that comes closest to your own. Complaining that <esc>:q does not work on emacs won't you anywhere.
The second - random snafus on an installed system is more difficult to handle. Having, presumably, done many installs, you would be in the best position to try and recognise patterns. Given that there is a significant population that does not face the problems that your customers do, there has to be some rational explanation. Of course, you should not forget that many users (people like your customers, not lug'ers or power users) are probably going to face similar problems on a Windows system as well. They just don't get highlighted for several reasons. So, have you seen any patterns? Or, are they as just random? If there are patterns, I'm sure we can find fixes. I should say that the fix may not be a software fix. It could just as well be an attitude fix or a usage style fix in the user :)
-gabin