Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    GOLDED    |    GoldED Public Release discussion.    |    2,690 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,483 of 2,690    |
|    Kai Richter to David Gonzalez    |
|    Linux golded    |
|    30 Nov 24 12:14:28    |
      REPLY: 4:930/1 674a610b       MSGID: 2:240/77 674af3a0       CHRS: LATIN-1 2       TID: hpt/lnx 1.4.0-sta 09-04-05       Hello David!              29 Nov 24, David Gonzalez wrote to Kai Richter:               WV>>> Nobody told you to put 'set' in front of that command line!        WV>>> Blank lines is what you get when you do that.               KR>> A well known AI method can't be wrong: Just try any combination.               DG> Meaning?              Just try any meaning. ;-)              Sorry. Back to be serious again. In my point of view the whole world is based       on trial and error. It is fine if you try different ways. You don't need help       this way because you learn the working way by yourself. But on your own there       is a long list of fails that needs much time to be sorted out.              To reduce this time we are asking others if there is a known solution already.       We receive others experience and the best thing is: There is a filter that       sorts out known failures. If you read Wilfreds lines above than you see that       he does know that the line with "set" in front will not work. That is why       nobody told you to write "set...".              In this case "set..." may break things. You can set a previous correct working       parameter to fail. If your helper doesn't notice that other screws are turned       he will wonder why it does not work. Based on your outputs it have to work and       he could confirm the working solution on his system. And all because of some       missing communication.              Latest example: It took 11 days to sort out that you have two different       machines with differnt setups. To us it looked like you have two problems on       one machine. Nick found now that one software is not involved on one machine.       This would reduce the possible failures making things easier.              In short: It's easier to stay on the bridge if you want to cross the river.       And it's no fun to build a bridge and see people walking through the water.              Regards              Kai              --- GoldED+/LNX 1.1.4.7        * Origin: Monobox (2:240/77)       SEEN-BY: 18/200 103/705 105/81 106/201 124/5016 128/187 129/305 153/757       SEEN-BY: 153/7715 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110       SEEN-BY: 229/114 206 300 317 400 426 428 470 664 700 240/77 1120 2100       SEEN-BY: 240/5411 5413 5824 5832 5853 6309 266/512 280/464 5003 5006       SEEN-BY: 280/5555 282/1038 291/111 292/854 8125 301/1 310/31 320/219       SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 467/888       SEEN-BY: 633/267 280 410 412 418 420 509 2744 712/848 770/1 902/26       SEEN-BY: 2432/390 2454/119 5020/400       PATH: 240/77 5832 280/464 633/280 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca