In comp.os.linux.advocacy, Hadron
<hadronquark@xxxxxxxxxxxxxx>
wrote
on Thu, 03 Jul 2008 10:58:11 +0200
<g4i4b4$4ce$4@xxxxxxxxxxxxxxxxxxxxxxxxx>:
> "Moshe Goldfarb." <brick_n_straw@xxxxxxxxx> writes:
>
>> On Wed, 2 Jul 2008 15:38:19 -0700, The Ghost In The Machine wrote:
>>
>>> In comp.os.linux.advocacy, Hadron
>>> <hadronquark@xxxxxxxxxxxxxx>
>>> wrote
>>> on Wed, 02 Jul 2008 23:31:47 +0200
>>> <g4gs45$jdd$2@xxxxxxxxxxxxxxxxxxxxxxxxx>:
>>>> The Ghost In The Machine <ewill@xxxxxxxxxxxxxxxxxxxxxxx> writes:
>>>
>>> [snippage]
>>>
>>>>> The greatest lie is self-delusion. Keep that in mind;
>>>>> it applies to both sides.
>>>>
>>>> Jeb would have been proud of that. Did you just pick it up from a
>>>> fortune cookie?
>>>>
>>>
>>> Somebody has to write them. :-P
>>
>> You may not like or agree with what I write, but at least I actually *write
>> something*...
>> Jebbediah talks in circles.
>>
>> Example: Linux tends to be unstable on my P4 system...
>> Jeb: Unstable can be a function of some other process going on.
>>
>> or such....
>
> Heh! Good one.
>
Well, maybe between the two of you there might actually
be some additional information as to the root cause of
this instability? Or at least how to elicit the symptoms?
Saying "a system is unstable" doesn't help a whole lot.
I once installed some RAM on my Athlon and it started
behaving in little, peculiar ways. Memtest identified it
as a problem with the RAM. I've also had Linux fail in
little, peculiar ways on another system, long ago; that was
also a hardware problem (probably an underpowered machine,
and I mean that literally -- overdrawn power supplies can
cause a fair amount of strangeness).
--
#191, ewill3@xxxxxxxxxxxxx
Useless C++ Programming Idea #12995733:
bool f(bool g, bool h) { if(g) h = true; else h = false; return h;}
** Posted from http://www.teranews.com **
|
|
