Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.folklore.computers > #159496 > unrolled thread

Ransomware

Started by"Osmium" <r124c4u102@comcast.net>
First post2016-02-16 10:37 -0600
Last post2016-02-19 12:55 -0600
Articles 20 on this page of 317 — 37 participants

Back to article view | Back to alt.folklore.computers


Contents

  Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-16 10:37 -0600
    Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-16 09:54 -0800
      Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-16 19:41 +0100
        Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-16 21:11 +0100
          Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-17 02:16 +0100
          Re: Ransomware usenet@only.tnx (Questor) - 2016-02-17 22:05 +0000
            Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-17 23:35 +0100
              Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-18 13:58 +0000
            Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-17 18:41 -0700
        Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-16 18:52 -0700
        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-17 14:13 +1100
          Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-17 04:53 +0100
            Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-17 04:21 +0000
            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-17 17:24 +1100
              Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-17 15:07 +0100
                Re: Ransomware usenet@only.tnx (Questor) - 2016-02-17 23:02 +0000
        Re: Ransomware Huge <Huge@nowhere.much.invalid> - 2016-02-17 08:03 +0000
          Re: Ransomware usenet@only.tnx (Questor) - 2016-02-17 23:02 +0000
      Re: Ransomware Huge <Huge@nowhere.much.invalid> - 2016-02-17 08:01 +0000
        Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-17 18:07 +0000
          Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-17 14:01 -0500
            Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-17 18:41 -0700
              Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-17 18:09 -0800
                Re: Ransomware Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-02-17 20:45 -0700
                  Re: Ransomware Jon Elson <elson@pico-systems.com> - 2016-02-17 22:34 -0600
                  Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-18 11:16 -0600
                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 05:44 +1100
                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-18 15:00 +1100
              Re: Ransomware Roger Blake <rogblake@iname.invalid> - 2016-02-18 02:12 +0000
              Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-17 22:47 -0500
                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-18 15:10 +1100
                  Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-17 21:29 -0800
                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-18 17:56 +1100
                      Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-17 23:15 -0800
                        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-18 18:35 +1100
                    Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-18 17:58 -0800
                      Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 13:44 +1100
              Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-17 20:44 -0800
                Re: Ransomware Lawrence Statton <lawrence@senguio.mx> - 2016-02-18 08:03 -0600
                  Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-18 17:14 -0600
                    Re: Ransomware Lawrence Statton <lawrence@senguio.mx> - 2016-02-18 19:10 -0600
                      Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-18 20:13 -0800
                        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 15:26 +1100
                      Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 09:34 -0600
                        Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 16:26 +0000
                          Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 14:58 -0600
                            Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-19 18:21 -0500
                              Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 18:43 -0700
                                Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-19 23:32 -0500
                            Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 19:34 -0800
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 19:59 +1100
                              Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-20 07:25 -0500
                              Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:30 -0600
                                Re: Ransomware Dave Garland <dave.garland@wizinfo.com> - 2016-02-20 10:58 -0600
                                  Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 04:25 +1100
                                  Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-20 19:56 +0000
                                  Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-20 18:15 -0700
                                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 13:26 +1100
                                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 04:16 +1100
                                  Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-20 18:15 -0700
                                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 13:22 +1100
                          Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-19 17:36 -0500
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 10:01 +1100
                            Re: Ransomware Gene Wirchenko <genew@telus.net> - 2016-02-20 16:26 -0800
                              Re: Ransomware Gene Wirchenko <genew@telus.net> - 2016-02-21 13:52 -0800
                                Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-21 18:51 -0500
                          Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 19:18 -0800
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 15:03 +1100
                            Re: Ransomware Andrew Swallow <am.swallow@btinternet.com> - 2016-02-20 16:12 +0000
                        Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-19 15:59 -0600
                          Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 09:59 +1100
                            Re: Ransomware Dave Garland <dave.garland@wizinfo.com> - 2016-02-19 18:43 -0600
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 14:36 +1100
                          Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 17:01 -0600
                            Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-19 18:54 -0600
                              Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 19:48 -0600
                                Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-20 16:20 -0600
                                  Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 18:17 -0600
                              Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 19:53 -0800
                            Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 18:43 -0700
                              Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-19 21:33 -0500
                                Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:23 -0600
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 14:48 +1100
                              Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 19:56 -0800
                              Re: Ransomware Michael Black <et472@ncf.ca> - 2016-02-19 23:18 -0500
                                Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:35 -0600
                              Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:12 -0600
                              Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-20 15:33 -0600
                                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 12:11 +1100
                            Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 18:43 -0700
                              Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 20:00 -0800
                                Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-20 01:51 -0700
                                Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:34 -0600
                              Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:19 -0600
                            Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 19:40 -0800
                            Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-20 15:18 +0000
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 03:46 +1100
                    Re: Ransomware Dave Garland <dave.garland@wizinfo.com> - 2016-02-18 23:55 -0600
                      Re: Ransomware mausg@mail.com - 2016-02-19 10:48 +0000
                        Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-19 05:56 -0500
                          Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 09:50 -0600
                            Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 16:29 +0000
                              Re: Ransomware Stan Barr <plan.b@bluesomatic.org> - 2016-02-19 16:54 +0000
                                Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-19 17:55 +0000
                                  Re: Ransomware Stan Barr <plan.b@bluesomatic.org> - 2016-02-20 08:30 +0000
                                    Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-20 15:29 +0000
                                    Re: Ransomware Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-02-20 10:06 -0600
                                      Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-20 11:03 -0600
                                        Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 16:14 -0600
                                  Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 16:27 -0600
                                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-23 09:49 +1100
                                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 05:29 +1100
                                  Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-19 18:53 +0000
                                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 09:42 +1100
                                Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-19 14:24 -0500
                              Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 14:58 -0600
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 05:24 +1100
                        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 04:53 +1100
                        Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-19 18:15 +0000
                      Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 17:55 -0800
                Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-18 11:19 -0500
                Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-18 10:19 -0600
                  Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-18 11:46 -0500
                    Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-18 18:01 +0000
                      Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-18 14:36 -0500
                        Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-19 11:23 +0000
                          Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-19 09:28 -0500
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 05:19 +1100
                Re: Ransomware Dave Garland <dave.garland@wizinfo.com> - 2016-02-18 11:06 -0600
                  Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-18 10:24 -0700
                    Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-18 12:27 -0800
                      Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 10:22 +1100
                        Re: Ransomware Dave Garland <dave.garland@wizinfo.com> - 2016-02-19 00:07 -0600
                          Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 18:34 +1100
                            Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-19 05:41 -0500
                              Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-19 07:43 -0600
                                Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 16:13 +0000
                              Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-19 08:01 -0600
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 04:50 +1100
                    Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-18 21:34 +0000
                  Re: Ransomware Lawrence Statton <lawrence@senguio.mx> - 2016-02-18 13:34 -0600
                Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 17:34 -0500
                  Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 10:33 +1100
                    Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 21:04 -0500
                      Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 13:46 +1100
                        Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-19 05:34 -0500
                          Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 04:47 +1100
                  Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-19 14:24 +0000
              Re: Ransomware Walter Banks <walter@bytecraft.com> - 2016-02-18 11:03 -0500
              Re: Ransomware Ibmekon <Ibmekon> - 2016-02-18 19:21 +0000
                Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-18 20:56 +0000
                  Re: Ransomware Ibmekon <Ibmekon> - 2016-02-18 21:19 +0000
                    Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 13:48 +0000
                      Re: Ransomware Ibmekon <Ibmekon> - 2016-02-19 14:12 +0000
                        Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 09:54 -0600
                          Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-20 15:18 +0000
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 03:29 +1100
                            Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-20 10:42 -0600
                              Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-21 15:48 +0000
                                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-22 03:43 +1100
                                Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-21 12:55 -0600
                                  Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-22 07:53 +1100
                                  Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-23 13:13 +0000
                                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-24 04:49 +1100
                                Re: Ransomware Ibmekon <Ibmekon> - 2016-02-21 19:56 +0000
                        Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 16:19 +0000
                          Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 18:08 -0800
                          Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-19 18:18 -0800
                        Re: Ransomware mausg@mail.com - 2016-02-19 18:10 +0000
                          Re: Ransomware Ibmekon <Ibmekon> - 2016-02-19 21:43 +0000
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 09:52 +1100
                            Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-19 16:53 -0800
                Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-18 18:37 -0600
            Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-18 13:58 +0000
              Re: Ransomware "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-02-19 05:32 +1100
      Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-17 11:13 -0600
    Re: Ransomware Roger Blake <rogblake@iname.invalid> - 2016-02-16 17:57 +0000
      Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-16 14:19 -0600
        Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-17 03:42 +0000
          Re: Ransomware Huge <Huge@nowhere.much.invalid> - 2016-02-17 08:05 +0000
          Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-17 12:03 +0000
            Re: Ransomware Morten Reistad <first@last.name,invalid> - 2016-02-17 15:21 +0100
            Re: Ransomware Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-02-17 07:38 -0700
            Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-17 18:07 +0000
              Re: Ransomware "Charles Richmond" <numerist@aquaporin4.com> - 2016-02-18 12:10 -0600
                Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-18 21:34 +0000
          Re: Ransomware "Charles Richmond" <numerist@aquaporin4.com> - 2016-02-18 12:06 -0600
      Re: Ransomware Quadibloc <jsavard@ecn.ab.ca> - 2016-02-16 12:49 -0800
        Re: Ransomware Lawrence Statton <lawrence@senguio.mx> - 2016-02-16 16:55 -0600
          Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-16 17:31 -0600
        Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-16 16:11 -0800
        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-17 14:26 +1100
        Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-17 11:19 -0600
          Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-17 12:05 -0600
            Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-17 17:58 -0600
              Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-17 18:41 -0700
                Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-17 18:39 -0800
    Re: Ransomware Mike Spencer <mds@bogus.nodomain.nowhere> - 2016-02-16 16:44 -0400
      Re: Ransomware Jon Elson <jmelson@wustl.edu> - 2016-02-16 15:30 -0600
        Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-17 00:20 +0100
          Re: Ransomware usenet@only.tnx (Questor) - 2016-02-17 23:03 +0000
            Re: Ransomware Michael Black <et472@ncf.ca> - 2016-02-17 18:48 -0500
              Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-18 13:58 +0000
                Re: Ransomware Morten Reistad <first@Last.name.invalid> - 2016-02-18 16:46 +0100
                  Re: Ransomware Gene Wirchenko <genew@telus.net> - 2016-02-18 11:06 -0800
                    Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-18 14:43 -0500
                      Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-18 14:06 -0600
                        Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-18 15:48 -0500
                          Re: Ransomware "Osmium" <r124c4u102@comcast.net> - 2016-02-18 15:36 -0600
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 10:30 +1100
                            Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-18 19:38 -0500
                          Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-18 21:43 +0000
                          Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-19 00:51 +0100
                            Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 13:45 +0000
                              Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-19 15:00 +0100
                              Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 07:01 -0700
                                Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-19 10:16 -0500
                                  Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 11:15 -0700
                                    Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 11:19 -0700
                                      Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-19 18:55 +0000
                                        Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-19 12:54 -0700
                                          Re: Ransomware Gene Wirchenko <genew@telus.net> - 2016-02-20 17:46 -0800
                                      Re: Ransomware JimP <solosam90@gmail.com> - 2016-02-19 15:08 -0600
                                Re: Ransomware "Charles Richmond" <numerist@aquaporin4.com> - 2016-02-23 16:01 -0600
                                  Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-23 21:24 -0500
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-20 04:58 +1100
                          Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-19 13:40 +0000
                      Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-19 14:24 +0000
                        Re: Ransomware "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-02-20 05:06 +1100
                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-19 10:11 +1100
                    Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-18 21:44 +0100
                    Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-19 14:24 +0000
                      Re: Ransomware "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-02-20 05:13 +1100
                  Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-19 14:24 +0000
                    Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-19 17:08 +0100
                      Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-20 15:18 +0000
                        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 03:41 +1100
                        Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-20 18:15 -0700
                          Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-21 09:35 +0100
                          Re: Ransomware Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-21 10:18 +0000
                            Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-21 16:48 +0100
                          Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-21 18:40 -0600
                            Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-22 01:53 +0100
                              Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-21 18:36 -0700
                              Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 00:12 -0600
                                Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-22 09:37 +0100
                                  Re: Ransomware Dan Espen <despen@verizon.net> - 2016-02-22 09:17 -0500
                                    Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-22 15:29 +0100
                                      Re: Ransomware using libc Dan Espen <despen@verizon.net> - 2016-02-22 09:42 -0500
                                        Re: Ransomware using libc Melzzzzz <mel@zzzzz.com> - 2016-02-22 15:52 +0100
                                          Re: Ransomware using libc Dan Espen <despen@verizon.net> - 2016-02-22 10:23 -0500
                                            Re: Ransomware using libc scott@slp53.sl.home (Scott Lurndal) - 2016-02-22 17:24 +0000
                                              Re: Ransomware using libc Melzzzzz <mel@zzzzz.com> - 2016-02-22 20:29 +0100
                                                Re: Ransomware using libc Ahem A Rivet's Shot <steveo@eircom.net> - 2016-02-22 19:38 +0000
                                                  Re: Ransomware using libc Melzzzzz <mel@zzzzz.com> - 2016-02-22 21:31 +0100
                                          Re: Ransomware using libc Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-22 17:17 +0000
                                          Re: Ransomware using libc Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 14:41 -0600
                                            Re: Ransomware using libc Melzzzzz <mel@zzzzz.com> - 2016-02-22 22:07 +0100
                                  Re: Ransomware Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-02-22 09:16 -0700
                                    Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-22 17:21 +0100
                                      Re: Ransomware Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-02-22 09:34 -0700
                                  Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 11:11 -0600
                                    Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-22 18:25 +0100
                                      Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 15:15 -0600
                                        Re: Ransomware Melzzzzz <mel@zzzzz.com> - 2016-02-22 22:28 +0100
                                          Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-22 21:46 -0600
                    Re: Ransomware "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-02-20 05:05 +1100
                Re: Ransomware "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-02-19 05:31 +1100
                Re: Ransomware Jon Elson <jmelson@wustl.edu> - 2016-02-18 13:56 -0600
                  Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-19 14:24 +0000
                    Re: Ransomware "Rod Speed" <rod.speed.aaa@gmail.com> - 2016-02-20 05:16 +1100
                    Re: Ransomware Jon Elson <jmelson@wustl.edu> - 2016-02-19 17:09 -0600
                      Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-20 15:18 +0000
                        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 03:55 +1100
                        Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-20 19:56 +0000
                          Re: Ransomware Jon Elson <jmelson@wustl.edu> - 2016-02-22 14:07 -0600
                            Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-23 07:15 +1100
                            Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-22 18:30 -0500
                              Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-23 01:49 +0000
                                Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-23 13:09 +1100
                              Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-23 13:03 +1100
            Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-19 13:12 -0600
          Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 06:29 -0500
            Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-19 13:35 -0600
              Re: Ransomware Huge <Huge@nowhere.much.invalid> - 2016-02-20 09:55 +0000
                Re: Ransomware Peter Flass <peter_flass@yahoo.com> - 2016-02-20 07:30 -0700
                  Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-20 11:11 -0500
                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-21 04:05 +1100
                  Re: Ransomware Huge <Huge@nowhere.much.invalid> - 2016-02-21 11:55 +0000
                    Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-21 14:04 +0100
                      Re: Ransomware Huge <Huge@nowhere.much.invalid> - 2016-02-21 13:57 +0000
                        Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-21 23:28 +0000
                      Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-22 03:34 +1100
                    Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-22 03:32 +1100
                    Re: Ransomware Dave Garland <dave.garland@wizinfo.com> - 2016-02-21 12:14 -0600
                      Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-22 07:47 +1100
        Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-17 14:03 +0000
          Re: Ransomware Jon Elson <jmelson@wustl.edu> - 2016-02-17 15:20 -0600
            Re: Ransomware scott@slp53.sl.home (Scott Lurndal) - 2016-02-17 21:31 +0000
            Re: Ransomware Stan Barr <plan.b@bluesomatic.org> - 2016-02-18 08:23 +0000
              Re: Ransomware Jon Elson <elson@pico-systems.com> - 2016-02-18 11:42 -0600
        Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 06:23 -0500
          Re: Ransomware Jon Elson <elson@pico-systems.com> - 2016-02-18 11:43 -0600
            Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 17:48 -0500
      Re: Ransomware hancock4@bbs.cpcn.com - 2016-02-16 17:04 -0800
        Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-17 14:42 +1100
        Re: Ransomware Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-02-17 04:17 +0000
          Re: Ransomware Mike Spencer <mds@bogus.nodomain.nowhere> - 2016-02-17 04:08 -0400
            Re: Ransomware usenet@only.tnx (Questor) - 2016-02-17 23:04 +0000
          Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 06:38 -0500
            Re: Ransomware Morten Reistad <first@last.name.invalid> - 2016-02-18 13:38 +0100
              Re: Ransomware "J. Clarke" <j.clarke.873638@gmail.com> - 2016-02-18 17:57 -0500
      Re: Ransomware "hgww" <hgww@gmail.com> - 2016-02-17 14:24 +1100
      Re: Ransomware usenet@only.tnx (Questor) - 2016-02-17 23:03 +0000
        Re: Ransomware Anne & Lynn Wheeler <lynn@garlic.com> - 2016-02-17 16:43 -0800
        Re: Ransomware jmfbahciv <See.above@aol.com> - 2016-02-18 13:58 +0000
      Re: Ransomware Stephen Sprunk <stephen@sprunk.org> - 2016-02-19 12:55 -0600

Page 11 of 16 — ← Prev page 1 … 9 10 [11] 12 13 … 16  Next page →


#159616

Fromusenet@only.tnx (Questor)
Date2016-02-17 23:03 +0000
Message-ID<56c4fc34.6738599@nntp2.rawbw.com>
In reply to#159529
On Wed, 17 Feb 2016 00:20:49 +0100, Morten Reistad <first@last.name.invalid>
wrote:
>My mom was very careful with the web sites she visited, and still her XP
>machines had ~100 new instances of malware after a month. It got to be a
>quite tall order to keep cleaning.
>
>There are lots of "spelling trapdoors" out there, like micros0ft.com, etc.

Not letting your relatives run as admin makes cleanup a *lot* easier.

[toc] | [prev] | [next] | [standalone]


#159618

FromMichael Black <et472@ncf.ca>
Date2016-02-17 18:48 -0500
Message-ID<alpine.LNX.2.02.1602171847260.23886@darkstar.example.org>
In reply to#159616
On Wed, 17 Feb 2016, Questor wrote:

> On Wed, 17 Feb 2016 00:20:49 +0100, Morten Reistad <first@last.name.invalid>
> wrote:
>> My mom was very careful with the web sites she visited, and still her XP
>> machines had ~100 new instances of malware after a month. It got to be a
>> quite tall order to keep cleaning.
>>
>> There are lots of "spelling trapdoors" out there, like micros0ft.com, etc.
>
> Not letting your relatives run as admin makes cleanup a *lot* easier.
>
>
Someone locally, who is an actual system administrator, he set up Linux 
for his grandmother (I think it was) and kept the root account for 
himself.  And he administers it remotely, just like at work on a big 
system.

  Michael

[toc] | [prev] | [next] | [standalone]


#159666

Fromjmfbahciv <See.above@aol.com>
Date2016-02-18 13:58 +0000
Message-ID<PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>
In reply to#159618
Michael Black wrote:
> On Wed, 17 Feb 2016, Questor wrote:
>
>> On Wed, 17 Feb 2016 00:20:49 +0100, Morten Reistad
<first@last.name.invalid>
>> wrote:
>>> My mom was very careful with the web sites she visited, and still her XP
>>> machines had ~100 new instances of malware after a month. It got to be a
>>> quite tall order to keep cleaning.
>>>
>>> There are lots of "spelling trapdoors" out there, like micros0ft.com, etc.
>>
>> Not letting your relatives run as admin makes cleanup a *lot* easier.
>>
>>
> Someone locally, who is an actual system administrator, he set up Linux
> for his grandmother (I think it was) and kept the root account for
> himself.  And he administers it remotely, just like at work on a big
> system.

The biggest problem is that there is no documentation available for the
grandmother to know what she has to do to be a sysadmin.  Most of the
docs available are addressed to a user, not an owner, of a system.

/BAH

[toc] | [prev] | [next] | [standalone]


#159673

FromMorten Reistad <first@Last.name.invalid>
Date2016-02-18 16:46 +0100
Message-ID<qi5hpc-531.ln1@sambook.reistad.name>
In reply to#159666
In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
jmfbahciv  <See.above@aol.com> wrote:
>Michael Black wrote:
>> On Wed, 17 Feb 2016, Questor wrote:
>>
>>> On Wed, 17 Feb 2016 00:20:49 +0100, Morten Reistad
><first@last.name.invalid>
>>> wrote:
>>>> My mom was very careful with the web sites she visited, and still her XP
>>>> machines had ~100 new instances of malware after a month. It got to be a
>>>> quite tall order to keep cleaning.
>>>>
>>>> There are lots of "spelling trapdoors" out there, like micros0ft.com, etc.
>>>
>>> Not letting your relatives run as admin makes cleanup a *lot* easier.
>>>
>>>
>> Someone locally, who is an actual system administrator, he set up Linux
>> for his grandmother (I think it was) and kept the root account for
>> himself.  And he administers it remotely, just like at work on a big
>> system.
>
>The biggest problem is that there is no documentation available for the
>grandmother to know what she has to do to be a sysadmin.  Most of the
>docs available are addressed to a user, not an owner, of a system.
>
>/BAH

Barb, you need to fast forward from ca 1996, when this was a valid
complaint. 

Now you can pick and choose the materials you like. A lot of it is
available on the net, and is well indexed. I usually just ask google, 
and get a list of at least a dozen good answers whenever I do.

-- mrr

[toc] | [prev] | [next] | [standalone]


#159708

FromGene Wirchenko <genew@telus.net>
Date2016-02-18 11:06 -0800
Message-ID<3e5ccbhu2kg2dn3mfl7qm76gnoikngfaid@4ax.com>
In reply to#159673
On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
<first@Last.name.invalid> wrote:

>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>jmfbahciv  <See.above@aol.com> wrote:

[snip]

>>The biggest problem is that there is no documentation available for the
>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>docs available are addressed to a user, not an owner, of a system.

>Barb, you need to fast forward from ca 1996, when this was a valid
>complaint. 
>
>Now you can pick and choose the materials you like. A lot of it is
>available on the net, and is well indexed. I usually just ask google, 
>and get a list of at least a dozen good answers whenever I do.

     Why a dozen answers?  Are they all the same?  If so, then it
really just one answer.  If they are different, how does a
non-technical person determine which is the correct answer?  How does
such a person determine that any of the answers are good in the first
place?

Sincerely,

Gene Wirchenko

[toc] | [prev] | [next] | [standalone]


#159712

FromDan Espen <despen@verizon.net>
Date2016-02-18 14:43 -0500
Message-ID<na56o1$egs$1@dont-email.me>
In reply to#159708
Gene Wirchenko <genew@telus.net> writes:

> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
> <first@Last.name.invalid> wrote:
>
>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>jmfbahciv  <See.above@aol.com> wrote:
>
> [snip]
>
>>>The biggest problem is that there is no documentation available for the
>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>docs available are addressed to a user, not an owner, of a system.
>
>>Barb, you need to fast forward from ca 1996, when this was a valid
>>complaint. 

Pointless to tell her.  She got the same answer multiple times over
the years I read her crap.  Wooden head.

>>Now you can pick and choose the materials you like. A lot of it is
>>available on the net, and is well indexed. I usually just ask google, 
>>and get a list of at least a dozen good answers whenever I do.
>
>      Why a dozen answers?  Are they all the same?  If so, then it
> really just one answer.  If they are different, how does a
> non-technical person determine which is the correct answer?  How does
> such a person determine that any of the answers are good in the first
> place?

You get different answers because there is more than one solution.
This works well.  Take a look at stackexchange where the users vote
on the best answer.  You get multiple answers and it's pretty clear
which ones work best.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]


#159715

From"Osmium" <r124c4u102@comcast.net>
Date2016-02-18 14:06 -0600
Message-ID<dimmhnFauj3U1@mid.individual.net>
In reply to#159712
"Dan Espen" wrote:

> Gene Wirchenko <genew@telus.net> writes:
>
>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>> <first@Last.name.invalid> wrote:
>>
>>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>jmfbahciv  <See.above@aol.com> wrote:
>>
>> [snip]
>>
>>>>The biggest problem is that there is no documentation available for the
>>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>docs available are addressed to a user, not an owner, of a system.
>>
>>>Barb, you need to fast forward from ca 1996, when this was a valid
>>>complaint.
>
> Pointless to tell her.  She got the same answer multiple times over
> the years I read her crap.  Wooden head.
>
>>>Now you can pick and choose the materials you like. A lot of it is
>>>available on the net, and is well indexed. I usually just ask google,
>>>and get a list of at least a dozen good answers whenever I do.
>>
>>      Why a dozen answers?  Are they all the same?  If so, then it
>> really just one answer.  If they are different, how does a
>> non-technical person determine which is the correct answer?  How does
>> such a person determine that any of the answers are good in the first
>> place?
>
> You get different answers because there is more than one solution.
> This works well.  Take a look at stackexchange where the users vote
> on the best answer.  You get multiple answers and it's pretty clear
> which ones work best.

That shows that reliable and non-harmful communication _can be_ possible. 
But you happened to know the secret word, stackexchange.  Now visualize 
grandma in her living room surrounded by several big empty cardboard boxes 
and a bunch of little black wire ties, and no secret word. 

[toc] | [prev] | [next] | [standalone]


#159717

FromDan Espen <despen@verizon.net>
Date2016-02-18 15:48 -0500
Message-ID<na5agu$u3m$1@dont-email.me>
In reply to#159715
"Osmium" <r124c4u102@comcast.net> writes:

> "Dan Espen" wrote:
>
>> Gene Wirchenko <genew@telus.net> writes:
>>
>>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>>> <first@Last.name.invalid> wrote:
>>>
>>>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>>jmfbahciv  <See.above@aol.com> wrote:
>>>
>>> [snip]
>>>
>>>>>The biggest problem is that there is no documentation available for the
>>>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>>docs available are addressed to a user, not an owner, of a system.
>>>
>>>>Barb, you need to fast forward from ca 1996, when this was a valid
>>>>complaint.
>>
>> Pointless to tell her.  She got the same answer multiple times over
>> the years I read her crap.  Wooden head.
>>
>>>>Now you can pick and choose the materials you like. A lot of it is
>>>>available on the net, and is well indexed. I usually just ask google,
>>>>and get a list of at least a dozen good answers whenever I do.
>>>
>>>      Why a dozen answers?  Are they all the same?  If so, then it
>>> really just one answer.  If they are different, how does a
>>> non-technical person determine which is the correct answer?  How does
>>> such a person determine that any of the answers are good in the first
>>> place?
>>
>> You get different answers because there is more than one solution.
>> This works well.  Take a look at stackexchange where the users vote
>> on the best answer.  You get multiple answers and it's pretty clear
>> which ones work best.
>
> That shows that reliable and non-harmful communication _can be_
> possible. But you happened to know the secret word, stackexchange.
> Now visualize grandma in her living room surrounded by several big
> empty cardboard boxes and a bunch of little black wire ties, and no
> secret word. 

No secret knowledge required.

Type in the subject, error message, whatever.
Google comes back and stackexchange presents itself.

That's not the only site with good info either.

I have never gone directly to stackexchange for an answer, that just one
of many sites where good help is freely available.

Also notable, the forums for Ubuntu, Arch Linux, Fedora.
Mozilla makes a good showing too.


-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]


#159723

From"Osmium" <r124c4u102@comcast.net>
Date2016-02-18 15:36 -0600
Message-ID<dimrr1Fcb86U1@mid.individual.net>
In reply to#159717
"Dan Espen" wrote:

> "Osmium" <r124c4u102@comcast.net> writes:
>
>> "Dan Espen" wrote:
>>
>>> Gene Wirchenko <genew@telus.net> writes:
>>>
>>>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>>>> <first@Last.name.invalid> wrote:
>>>>
>>>>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>>>jmfbahciv  <See.above@aol.com> wrote:
>>>>
>>>> [snip]
>>>>
>>>>>>The biggest problem is that there is no documentation available for 
>>>>>>the
>>>>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>>>docs available are addressed to a user, not an owner, of a system.
>>>>
>>>>>Barb, you need to fast forward from ca 1996, when this was a valid
>>>>>complaint.
>>>
>>> Pointless to tell her.  She got the same answer multiple times over
>>> the years I read her crap.  Wooden head.
>>>
>>>>>Now you can pick and choose the materials you like. A lot of it is
>>>>>available on the net, and is well indexed. I usually just ask google,
>>>>>and get a list of at least a dozen good answers whenever I do.
>>>>
>>>>      Why a dozen answers?  Are they all the same?  If so, then it
>>>> really just one answer.  If they are different, how does a
>>>> non-technical person determine which is the correct answer?  How does
>>>> such a person determine that any of the answers are good in the first
>>>> place?
>>>
>>> You get different answers because there is more than one solution.
>>> This works well.  Take a look at stackexchange where the users vote
>>> on the best answer.  You get multiple answers and it's pretty clear
>>> which ones work best.
>>
>> That shows that reliable and non-harmful communication _can be_
>> possible. But you happened to know the secret word, stackexchange.
>> Now visualize grandma in her living room surrounded by several big
>> empty cardboard boxes and a bunch of little black wire ties, and no
>> secret word.
>
> No secret knowledge required.
>
> Type in the subject, error message, whatever.
> Google comes back and stackexchange presents itself.
>
> That's not the only site with good info either.
>
> I have never gone directly to stackexchange for an answer, that just one
> of many sites where good help is freely available.
>
> Also notable, the forums for Ubuntu, Arch Linux, Fedora.
> Mozilla makes a good showing too.

I once got some nasty malware from clicking on a google provided link on the 
first page of results.  YMMV. 

[toc] | [prev] | [next] | [standalone]


#159735

From"hgww" <hgww@gmail.com>
Date2016-02-19 10:30 +1100
Message-ID<din2hfFdvt7U1@mid.individual.net>
In reply to#159723

"Osmium" <r124c4u102@comcast.net> wrote in message 
news:dimrr1Fcb86U1@mid.individual.net...
> "Dan Espen" wrote:
>
>> "Osmium" <r124c4u102@comcast.net> writes:
>>
>>> "Dan Espen" wrote:
>>>
>>>> Gene Wirchenko <genew@telus.net> writes:
>>>>
>>>>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>>>>> <first@Last.name.invalid> wrote:
>>>>>
>>>>>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>>>>jmfbahciv  <See.above@aol.com> wrote:
>>>>>
>>>>> [snip]
>>>>>
>>>>>>>The biggest problem is that there is no documentation available for 
>>>>>>>the
>>>>>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>>>>docs available are addressed to a user, not an owner, of a system.
>>>>>
>>>>>>Barb, you need to fast forward from ca 1996, when this was a valid
>>>>>>complaint.
>>>>
>>>> Pointless to tell her.  She got the same answer multiple times over
>>>> the years I read her crap.  Wooden head.
>>>>
>>>>>>Now you can pick and choose the materials you like. A lot of it is
>>>>>>available on the net, and is well indexed. I usually just ask google,
>>>>>>and get a list of at least a dozen good answers whenever I do.
>>>>>
>>>>>      Why a dozen answers?  Are they all the same?  If so, then it
>>>>> really just one answer.  If they are different, how does a
>>>>> non-technical person determine which is the correct answer?  How does
>>>>> such a person determine that any of the answers are good in the first
>>>>> place?
>>>>
>>>> You get different answers because there is more than one solution.
>>>> This works well.  Take a look at stackexchange where the users vote
>>>> on the best answer.  You get multiple answers and it's pretty clear
>>>> which ones work best.
>>>
>>> That shows that reliable and non-harmful communication _can be_
>>> possible. But you happened to know the secret word, stackexchange.
>>> Now visualize grandma in her living room surrounded by several big
>>> empty cardboard boxes and a bunch of little black wire ties, and no
>>> secret word.
>>
>> No secret knowledge required.
>>
>> Type in the subject, error message, whatever.
>> Google comes back and stackexchange presents itself.
>>
>> That's not the only site with good info either.
>>
>> I have never gone directly to stackexchange for an answer, that just one
>> of many sites where good help is freely available.
>>
>> Also notable, the forums for Ubuntu, Arch Linux, Fedora.
>> Mozilla makes a good showing too.
>
> I once got some nasty malware from clicking on a google provided link on 
> the first page of results.  YMMV.

Trivially avoidable by running a decent antivirus that checks the links. 

[toc] | [prev] | [next] | [standalone]


#159742

FromDan Espen <despen@verizon.net>
Date2016-02-18 19:38 -0500
Message-ID<na5o01$g2h$1@dont-email.me>
In reply to#159723
"Osmium" <r124c4u102@comcast.net> writes:

> "Dan Espen" wrote:
>
>> "Osmium" <r124c4u102@comcast.net> writes:
>>
>>> "Dan Espen" wrote:
>>>
>>>> Gene Wirchenko <genew@telus.net> writes:
>>>>
>>>>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>>>>> <first@Last.name.invalid> wrote:
>>>>>
>>>>>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>>>>jmfbahciv  <See.above@aol.com> wrote:
>>>>>
>>>>> [snip]
>>>>>
>>>>>>> The biggest problem is that there is no documentation available
>>>>>>> for the
>>>>>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>>>>docs available are addressed to a user, not an owner, of a system.
>>>>>
>>>>>>Barb, you need to fast forward from ca 1996, when this was a valid
>>>>>>complaint.
>>>>
>>>> Pointless to tell her.  She got the same answer multiple times over
>>>> the years I read her crap.  Wooden head.
>>>>
>>>>>>Now you can pick and choose the materials you like. A lot of it is
>>>>>>available on the net, and is well indexed. I usually just ask google,
>>>>>>and get a list of at least a dozen good answers whenever I do.
>>>>>
>>>>>      Why a dozen answers?  Are they all the same?  If so, then it
>>>>> really just one answer.  If they are different, how does a
>>>>> non-technical person determine which is the correct answer?  How does
>>>>> such a person determine that any of the answers are good in the first
>>>>> place?
>>>>
>>>> You get different answers because there is more than one solution.
>>>> This works well.  Take a look at stackexchange where the users vote
>>>> on the best answer.  You get multiple answers and it's pretty clear
>>>> which ones work best.
>>>
>>> That shows that reliable and non-harmful communication _can be_
>>> possible. But you happened to know the secret word, stackexchange.
>>> Now visualize grandma in her living room surrounded by several big
>>> empty cardboard boxes and a bunch of little black wire ties, and no
>>> secret word.
>>
>> No secret knowledge required.
>>
>> Type in the subject, error message, whatever.
>> Google comes back and stackexchange presents itself.
>>
>> That's not the only site with good info either.
>>
>> I have never gone directly to stackexchange for an answer, that just one
>> of many sites where good help is freely available.
>>
>> Also notable, the forums for Ubuntu, Arch Linux, Fedora.
>> Mozilla makes a good showing too.
>
> I once got some nasty malware from clicking on a google provided link
> on the first page of results.  YMMV. 

I've seen that, those Windows download sites come up as the only hits
and I think they're all not to be trusted.

I'm not going to find any malware for Linux no matter how hard I look.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]


#159724

FromCharlie Gibbs <cgibbs@kltpzyxm.invalid>
Date2016-02-18 21:43 +0000
Message-ID<na5dt60fav@news7.newsguy.com>
In reply to#159717
On 2016-02-18, Dan Espen <despen@verizon.net> wrote:

> "Osmium" <r124c4u102@comcast.net> writes:
>
>> "Dan Espen" wrote:
>>
>>> Gene Wirchenko <genew@telus.net> writes:
>>>
>>>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>>>> <first@Last.name.invalid> wrote:
>>>>
>>>>> In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>>> jmfbahciv  <See.above@aol.com> wrote:
>>>>
>>>> [snip]
>>>>
>>>>>> The biggest problem is that there is no documentation available for the
>>>>>> grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>>> docs available are addressed to a user, not an owner, of a system.
>>>>>
>>>>> Barb, you need to fast forward from ca 1996, when this was a valid
>>>>> complaint.
>>>
>>> Pointless to tell her.  She got the same answer multiple times over
>>> the years I read her crap.  Wooden head.
>>>
>>>>> Now you can pick and choose the materials you like. A lot of it is
>>>>> available on the net, and is well indexed. I usually just ask google,
>>>>> and get a list of at least a dozen good answers whenever I do.
>>>>
>>>>      Why a dozen answers?  Are they all the same?  If so, then it
>>>> really just one answer.  If they are different, how does a
>>>> non-technical person determine which is the correct answer?  How does
>>>> such a person determine that any of the answers are good in the first
>>>> place?
>>>
>>> You get different answers because there is more than one solution.
>>> This works well.  Take a look at stackexchange where the users vote
>>> on the best answer.  You get multiple answers and it's pretty clear
>>> which ones work best.
>>
>> That shows that reliable and non-harmful communication _can be_
>> possible. But you happened to know the secret word, stackexchange.
>> Now visualize grandma in her living room surrounded by several big
>> empty cardboard boxes and a bunch of little black wire ties, and no
>> secret word. 
>
> No secret knowledge required.
>
> Type in the subject, error message, whatever.
> Google comes back and stackexchange presents itself.
>
> That's not the only site with good info either.
>
> I have never gone directly to stackexchange for an answer, that just one
> of many sites where good help is freely available.
>
> Also notable, the forums for Ubuntu, Arch Linux, Fedora.
> Mozilla makes a good showing too.

"But I don't want to do all that work!  I want to click on a button
and have it work by itself!"

And along comes Apple, or Microsoft, or some fly-by-night operator,
claiming that they do have this magic button - and the lusers fall
for it.  (There is no magic button, but the myth is so seductive...)

-- 
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  HTML will DEFINITELY be ignored.  Join the ASCII ribbon campaign!

[toc] | [prev] | [next] | [standalone]


#159767

FromMorten Reistad <first@last.name.invalid>
Date2016-02-19 00:51 +0100
Message-ID<f02ipc-kd2.ln1@sambook.reistad.name>
In reply to#159717
In article <na5agu$u3m$1@dont-email.me>, Dan Espen  <despen@verizon.net> wrote:
>"Osmium" <r124c4u102@comcast.net> writes:
>
>> "Dan Espen" wrote:
>>
>>> Gene Wirchenko <genew@telus.net> writes:
>>>
>>>> On Thu, 18 Feb 2016 16:46:02 +0100, Morten Reistad
>>>> <first@Last.name.invalid> wrote:
>>>>
>>>>>In article <PM00052C0B6D1C5E03@aca4282e.ipt.aol.com>,
>>>>>jmfbahciv  <See.above@aol.com> wrote:
>>>>
>>>> [snip]
>>>>
>>>>>>The biggest problem is that there is no documentation available for the
>>>>>>grandmother to know what she has to do to be a sysadmin.  Most of the
>>>>>>docs available are addressed to a user, not an owner, of a system.
>>>>
>>>>>Barb, you need to fast forward from ca 1996, when this was a valid
>>>>>complaint.
>>>
>>> Pointless to tell her.  She got the same answer multiple times over
>>> the years I read her crap.  Wooden head.
>>>
>>>>>Now you can pick and choose the materials you like. A lot of it is
>>>>>available on the net, and is well indexed. I usually just ask google,
>>>>>and get a list of at least a dozen good answers whenever I do.
>>>>
>>>>      Why a dozen answers?  Are they all the same?  If so, then it
>>>> really just one answer.  If they are different, how does a
>>>> non-technical person determine which is the correct answer?  How does
>>>> such a person determine that any of the answers are good in the first
>>>> place?
>>>
>>> You get different answers because there is more than one solution.
>>> This works well.  Take a look at stackexchange where the users vote
>>> on the best answer.  You get multiple answers and it's pretty clear
>>> which ones work best.
>>
>> That shows that reliable and non-harmful communication _can be_
>> possible. But you happened to know the secret word, stackexchange.
>> Now visualize grandma in her living room surrounded by several big
>> empty cardboard boxes and a bunch of little black wire ties, and no
>> secret word. 
>
>No secret knowledge required.
>
>Type in the subject, error message, whatever.
>Google comes back and stackexchange presents itself.
>
>That's not the only site with good info either.
>
>I have never gone directly to stackexchange for an answer, that just one
>of many sites where good help is freely available.
>
>Also notable, the forums for Ubuntu, Arch Linux, Fedora.
>Mozilla makes a good showing too.

Ubuntu and respbian both come up with links right there on
the front page of the first boot screen. All the documentation
you can reasonably as for is a network access away.

-- mrr

[toc] | [prev] | [next] | [standalone]


#159781

Fromscott@slp53.sl.home (Scott Lurndal)
Date2016-02-19 13:45 +0000
Message-ID<y%Exy.149$gn2.72@fx18.iad>
In reply to#159767
Morten Reistad <first@last.name.invalid> writes:
>In article <na5agu$u3m$1@dont-email.me>, Dan Espen  <despen@verizon.net> wrote:

>>Also notable, the forums for Ubuntu, Arch Linux, Fedora.
>>Mozilla makes a good showing too.
>
>Ubuntu and respbian both come up with links right there on
>the front page of the first boot screen. All the documentation
>you can reasonably as for is a network access away.

 Another example from my Fathers ubuntu system - last week he
could no longer get network access.    How do you debug that
without network access (fortunately he has an ipad and another
desktop system as a backup)?

 It appears that either an update has hosed his ethernet device
driver or the ethernet chip has gone bad (again I'm diagnosing from
2000 miles away).   The link light on the switch and on the PHY on
the computer is illuminated, but ethtool shows 'link detected: no'.

 Attempting to read the kernel logs over the phone is fruitless
when the person on the other end has no idea what to look for.

 Solution is to order a usb-ethernet adapter and give that a try when
it arrives this weekend.

[toc] | [prev] | [next] | [standalone]


#159784

FromMelzzzzz <mel@zzzzz.com>
Date2016-02-19 15:00 +0100
Message-ID<20160219150006.4ad8b625@maxa-pc>
In reply to#159781
On Fri, 19 Feb 2016 13:45:02 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:

> Morten Reistad <first@last.name.invalid> writes:
> >In article <na5agu$u3m$1@dont-email.me>, Dan Espen
> ><despen@verizon.net> wrote:  
> 
> >>Also notable, the forums for Ubuntu, Arch Linux, Fedora.
> >>Mozilla makes a good showing too.  
> >
> >Ubuntu and respbian both come up with links right there on
> >the front page of the first boot screen. All the documentation
> >you can reasonably as for is a network access away.  
> 
>  Another example from my Fathers ubuntu system - last week he
> could no longer get network access.    How do you debug that
> without network access (fortunately he has an ipad and another
> desktop system as a backup)?
> 
>  It appears that either an update has hosed his ethernet device
> driver or the ethernet chip has gone bad (again I'm diagnosing from
> 2000 miles away).   The link light on the switch and on the PHY on
> the computer is illuminated, but ethtool shows 'link detected: no'.
> 
>  Attempting to read the kernel logs over the phone is fruitless
> when the person on the other end has no idea what to look for.
> 
>  Solution is to order a usb-ethernet adapter and give that a try when
> it arrives this weekend.

I don't let my parents update at all. I perform that every 3 months or
so ;p

[toc] | [prev] | [next] | [standalone]


#159786

FromPeter Flass <peter_flass@yahoo.com>
Date2016-02-19 07:01 -0700
Message-ID<528816624.477582927.161579.peter_flass-yahoo.com@news.eternal-september.org>
In reply to#159781
Scott Lurndal <scott@slp53.sl.home> wrote:
> Morten Reistad <first@last.name.invalid> writes:
>> In article <na5agu$u3m$1@dont-email.me>, Dan Espen  <despen@verizon.net> wrote:
> 
>>> Also notable, the forums for Ubuntu, Arch Linux, Fedora.
>>> Mozilla makes a good showing too.
>> 
>> Ubuntu and respbian both come up with links right there on
>> the front page of the first boot screen. All the documentation
>> you can reasonably as for is a network access away.
> 
>  Another example from my Fathers ubuntu system - last week he
> could no longer get network access.    How do you debug that
> without network access (fortunately he has an ipad and another
> desktop system as a backup)?
> 
>  It appears that either an update has hosed his ethernet device
> driver or the ethernet chip has gone bad (again I'm diagnosing from
> 2000 miles away).   The link light on the switch and on the PHY on
> the computer is illuminated, but ethtool shows 'link detected: no'.
> 
>  Attempting to read the kernel logs over the phone is fruitless
> when the person on the other end has no idea what to look for.
> 
>  Solution is to order a usb-ethernet adapter and give that a try when
> it arrives this weekend.
> 

This stuff's a bitch.  I don't know what the testing process is, but the
developers can't possibly test all combinations of H/W and S/W.  Windoze
has such a large user base that a bad update will be smoked out quickly. 
Apple solves the problem by restricting the variety of hardware it runs on.
 Linux is pretty good, but a larger user base to help catch this stuff
would be good.

I spent a lot of time trying to get Fedora to run with a Radeon video chip.
I posted several reports to bugzilla and tried a lot of different stuff
myself.  Finally a switch to Ubuntu solved my problem.

-- 
Pete

[toc] | [prev] | [next] | [standalone]


#159800

FromDan Espen <despen@verizon.net>
Date2016-02-19 10:16 -0500
Message-ID<na7bee$6of$1@dont-email.me>
In reply to#159786
Peter Flass <peter_flass@yahoo.com> writes:

> Scott Lurndal <scott@slp53.sl.home> wrote:
>> Morten Reistad <first@last.name.invalid> writes:
>>> In article <na5agu$u3m$1@dont-email.me>, Dan Espen  <despen@verizon.net> wrote:
>> 
>>>> Also notable, the forums for Ubuntu, Arch Linux, Fedora.  Mozilla
>>>> makes a good showing too.
>>> 
>>> Ubuntu and respbian both come up with links right there on the front
>>> page of the first boot screen. All the documentation you can
>>> reasonably as for is a network access away.
>> 
>>  Another example from my Fathers ubuntu system - last week he could
>> no longer get network access.  How do you debug that without network
>> access (fortunately he has an ipad and another desktop system as a
>> backup)?
>> 
>>  It appears that either an update has hosed his ethernet device
>> driver or the ethernet chip has gone bad (again I'm diagnosing from
>> 2000 miles away).  The link light on the switch and on the PHY on the
>> computer is illuminated, but ethtool shows 'link detected: no'.
>> 
>>  Attempting to read the kernel logs over the phone is fruitless when
>> the person on the other end has no idea what to look for.
>> 
>>  Solution is to order a usb-ethernet adapter and give that a try when
>> it arrives this weekend.
>> 
>
> This stuff's a bitch.  I don't know what the testing process is, but
> the developers can't possibly test all combinations of H/W and S/W.
> Windoze has such a large user base that a bad update will be smoked
> out quickly.  Apple solves the problem by restricting the variety of
> hardware it runs on.
>  Linux is pretty good, but a larger user base to help catch this stuff
> would be good.
>
> I spent a lot of time trying to get Fedora to run with a Radeon video
> chip.  I posted several reports to bugzilla and tried a lot of
> different stuff myself.  Finally a switch to Ubuntu solved my problem.

You might have found the cause in /var/log/Xorg.0.log.  Look for lines
containing "(EE)".

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]


#159828

FromPeter Flass <peter_flass@yahoo.com>
Date2016-02-19 11:15 -0700
Message-ID<964728277.477597839.291774.peter_flass-yahoo.com@news.eternal-september.org>
In reply to#159800
Dan Espen <despen@verizon.net> wrote:
> Peter Flass <peter_flass@yahoo.com> writes:
> 
>> Scott Lurndal <scott@slp53.sl.home> wrote:
>>> Morten Reistad <first@last.name.invalid> writes:
>>>> In article <na5agu$u3m$1@dont-email.me>, Dan Espen  <despen@verizon.net> wrote:
>>> 
>>>>> Also notable, the forums for Ubuntu, Arch Linux, Fedora.  Mozilla
>>>>> makes a good showing too.
>>>> 
>>>> Ubuntu and respbian both come up with links right there on the front
>>>> page of the first boot screen. All the documentation you can
>>>> reasonably as for is a network access away.
>>> 
>>> Another example from my Fathers ubuntu system - last week he could
>>> no longer get network access.  How do you debug that without network
>>> access (fortunately he has an ipad and another desktop system as a
>>> backup)?
>>> 
>>> It appears that either an update has hosed his ethernet device
>>> driver or the ethernet chip has gone bad (again I'm diagnosing from
>>> 2000 miles away).  The link light on the switch and on the PHY on the
>>> computer is illuminated, but ethtool shows 'link detected: no'.
>>> 
>>> Attempting to read the kernel logs over the phone is fruitless when
>>> the person on the other end has no idea what to look for.
>>> 
>>> Solution is to order a usb-ethernet adapter and give that a try when
>>> it arrives this weekend.
>>> 
>> 
>> This stuff's a bitch.  I don't know what the testing process is, but
>> the developers can't possibly test all combinations of H/W and S/W.
>> Windoze has such a large user base that a bad update will be smoked
>> out quickly.  Apple solves the problem by restricting the variety of
>> hardware it runs on.
>> Linux is pretty good, but a larger user base to help catch this stuff
>> would be good.
>> 
>> I spent a lot of time trying to get Fedora to run with a Radeon video
>> chip.  I posted several reports to bugzilla and tried a lot of
>> different stuff myself.  Finally a switch to Ubuntu solved my problem.
> 
> You might have found the cause in /var/log/Xorg.0.log.  Look for lines
> containing "(EE)".
> 

Did that, but the root cause was unclear.  It first looked like a X
problem.  I finally realized it was a driver problem, but then spent a lot
of time trying to nail it down and search for a (nonexistant) solution.


-- 
Pete

[toc] | [prev] | [next] | [standalone]


#159832

FromPeter Flass <peter_flass@yahoo.com>
Date2016-02-19 11:19 -0700
Message-ID<638046162.477598608.022083.peter_flass-yahoo.com@news.eternal-september.org>
In reply to#159828
Peter Flass <peter_flass@yahoo.com> wrote:
> Dan Espen <despen@verizon.net> wrote:
>> Peter Flass <peter_flass@yahoo.com> writes:
>> 
>>> Scott Lurndal <scott@slp53.sl.home> wrote:
>>>> Morten Reistad <first@last.name.invalid> writes:
>>>>> In article <na5agu$u3m$1@dont-email.me>, Dan Espen  <despen@verizon.net> wrote:
>>>> 
>>>>>> Also notable, the forums for Ubuntu, Arch Linux, Fedora.  Mozilla
>>>>>> makes a good showing too.
>>>>> 
>>>>> Ubuntu and respbian both come up with links right there on the front
>>>>> page of the first boot screen. All the documentation you can
>>>>> reasonably as for is a network access away.
>>>> 
>>>> Another example from my Fathers ubuntu system - last week he could
>>>> no longer get network access.  How do you debug that without network
>>>> access (fortunately he has an ipad and another desktop system as a
>>>> backup)?
>>>> 
>>>> It appears that either an update has hosed his ethernet device
>>>> driver or the ethernet chip has gone bad (again I'm diagnosing from
>>>> 2000 miles away).  The link light on the switch and on the PHY on the
>>>> computer is illuminated, but ethtool shows 'link detected: no'.
>>>> 
>>>> Attempting to read the kernel logs over the phone is fruitless when
>>>> the person on the other end has no idea what to look for.
>>>> 
>>>> Solution is to order a usb-ethernet adapter and give that a try when
>>>> it arrives this weekend.
>>>> 
>>> 
>>> This stuff's a bitch.  I don't know what the testing process is, but
>>> the developers can't possibly test all combinations of H/W and S/W.
>>> Windoze has such a large user base that a bad update will be smoked
>>> out quickly.  Apple solves the problem by restricting the variety of
>>> hardware it runs on.
>>> Linux is pretty good, but a larger user base to help catch this stuff
>>> would be good.
>>> 
>>> I spent a lot of time trying to get Fedora to run with a Radeon video
>>> chip.  I posted several reports to bugzilla and tried a lot of
>>> different stuff myself.  Finally a switch to Ubuntu solved my problem.
>> 
>> You might have found the cause in /var/log/Xorg.0.log.  Look for lines
>> containing "(EE)".
>> 
> 
> Did that, but the root cause was unclear.  It first looked like a X
> problem.  I finally realized it was a driver problem, but then spent a lot
> of time trying to nail it down and search for a (nonexistant) solution.
> 
> 

Followup:  The (EE) messages were issued by the X client.  Much earlier in
the log there was a _warning_ message that identified the problem.
Designing good error messages is an art.

-- 
Pete

[toc] | [prev] | [next] | [standalone]


#159839

FromAhem A Rivet's Shot <steveo@eircom.net>
Date2016-02-19 18:55 +0000
Message-ID<20160219185553.0cfa96dd0cee468efd9ee8b3@eircom.net>
In reply to#159832
On Fri, 19 Feb 2016 11:19:38 -0700
Peter Flass <peter_flass@yahoo.com> wrote:

> Followup:  The (EE) messages were issued by the X client.  Much earlier in
> the log there was a _warning_ message that identified the problem.
> Designing good error messages is an art.

	What ? Sorry ? How ?

	TBF they were better than many much more verbose error messages
I've seen.

-- 
Steve O'Hara-Smith                          |   Directable Mirror Arrays
C:>WIN                                      | A better way to focus the sun
The computer obeys and wins.                |    licences available see
You lose and Bill collects.                 |    http://www.sohara.org/

[toc] | [prev] | [next] | [standalone]


Page 11 of 16 — ← Prev page 1 … 9 10 [11] 12 13 … 16  Next page →

Back to top | Article view | alt.folklore.computers


csiph-web