Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #87133 > unrolled thread
| Started by | c186282 <c186282@nnada.net> |
|---|---|
| First post | 2026-05-26 02:21 -0400 |
| Last post | 2026-05-26 17:21 +0200 |
| Articles | 20 on this page of 336 — 16 participants |
Back to article view | Back to comp.os.linux.misc
Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-26 02:21 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-26 08:46 +0200
Re: Redundancy/Survival Marco Moock <mm@dorfdsl.de> - 2026-05-26 09:49 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-26 04:47 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-26 11:25 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-05-26 09:53 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-26 04:38 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-26 11:35 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-05-26 22:09 +0000
Re: Redundancy/Survival John Ames <commodorejohn@gmail.com> - 2026-05-26 16:17 -0700
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-05-27 00:02 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-27 00:11 -0400
Re: Redundancy/Survival Marco Moock <mm@dorfdsl.de> - 2026-05-28 10:32 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-05-27 08:41 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-27 11:04 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 03:31 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-28 09:18 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-28 13:42 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-28 15:01 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 21:34 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-29 11:07 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-29 12:55 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-29 12:14 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-29 13:36 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-29 13:26 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-29 19:36 +0200
Re: Redundancy/Survival Richard Kettlewell <invalid@invalid.invalid> - 2026-05-29 17:24 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-29 19:37 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-29 19:36 +0100
Re: Redundancy/Survival Richard Kettlewell <invalid@invalid.invalid> - 2026-05-29 22:34 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-30 04:29 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-30 13:09 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-30 23:29 -0400
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-05-31 21:45 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 12:15 +0200
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-01 18:53 -0400
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-02 01:46 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-02 03:01 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-02 18:12 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 10:16 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-02 18:09 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 21:26 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 12:48 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 14:35 +0000
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 17:25 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-04 03:51 +0000
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-04 04:30 +0000
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 09:34 +0100
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-04 16:06 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 20:20 +0200
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-04 18:27 +0000
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 09:30 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 19:24 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 20:04 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 22:25 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-04 04:15 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 07:36 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 02:19 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 08:34 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 10:26 -0400
Re: Redundancy/Survival Andy Burns <usenet@andyburns.uk> - 2026-06-04 08:18 +0100
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-04 09:48 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 10:36 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-04 17:58 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 14:56 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-04 22:07 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 22:18 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 03:40 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 00:29 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 07:06 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 04:11 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 17:17 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 00:10 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 05:16 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 01:46 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 19:40 +0000
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-05 00:13 +0000
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-05 03:12 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 00:15 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-07 13:25 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-07 19:54 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-08 00:37 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-07 19:18 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-08 00:42 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 04:26 +0000
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-06 03:10 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 05:41 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 01:52 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 20:03 +0000
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-07 03:16 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-06 11:47 +0200
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-07 03:20 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-07 04:59 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-07 19:27 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-08 00:50 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 23:38 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 06:48 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 03:05 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-08 00:52 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-08 09:33 +0200
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-05 19:21 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 00:36 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 05:51 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 02:26 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 20:12 +0000
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-07 03:11 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 03:51 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 01:47 -0400
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-05 19:21 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-02 02:58 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-02 11:11 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-02 22:15 -0400
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-02 22:32 -0400
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 02:33 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 11:57 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 14:40 +0000
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 09:31 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-05-29 04:30 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-29 01:34 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-29 06:36 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-31 00:38 -0400
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-05-31 05:09 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-31 03:10 -0400
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-05-31 07:14 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-01 00:49 -0400
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-01 04:57 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 03:20 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 19:45 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 18:30 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 22:27 +0200
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 10:49 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 13:16 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 00:00 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 14:43 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-02 18:35 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-02 18:21 +0000
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 18:25 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 21:36 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:06 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 11:32 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 11:43 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 13:05 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 12:14 +0100
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 12:31 +0100
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 14:43 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 19:28 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 20:10 +0100
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-03 18:00 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 22:27 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 12:13 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 14:48 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-03 18:58 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 14:46 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-01 19:00 -0400
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-02 17:44 +0000
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 17:54 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-02 16:57 -0400
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 21:02 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 11:41 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:13 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 11:47 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-04 01:01 +0100
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-03 21:18 -0400
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-04 04:30 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-04 18:02 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 07:44 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 09:48 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 00:26 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 07:53 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 11:49 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 01:03 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 10:07 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 10:57 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 16:31 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 12:08 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-05 11:34 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 22:31 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 05:48 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 01:56 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 19:56 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-07 05:40 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-07 19:25 +0000
Re: Redundancy/Survival Andy Burns <usenet@andyburns.uk> - 2026-06-07 20:37 +0100
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-08 00:57 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-08 00:23 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-08 14:45 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-08 01:00 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-08 00:38 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-08 16:50 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-04 18:13 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 15:03 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-04 22:27 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 22:45 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 04:42 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 02:01 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:10 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-02 22:29 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 11:52 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-04 19:18 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 21:28 +0200
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-03 18:00 +0000
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-06-05 03:14 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 00:25 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-05 07:20 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 04:15 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-05 12:33 +0200
Re: Redundancy/Survival Andy Burns <usenet@andyburns.uk> - 2026-06-05 11:55 +0100
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-05 19:21 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-05 22:01 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-05 22:15 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 05:53 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-06 12:01 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-07 05:08 -0400
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-07 20:40 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-08 00:44 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-07 23:06 -0400
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-08 04:36 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-08 00:43 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-08 09:08 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-08 09:29 +0100
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-08 14:34 +0000
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-05 19:21 +0000
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-06-06 00:23 +0000
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-06 18:52 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-06 00:43 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 11:49 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 00:30 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 07:55 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-04 09:51 +0100
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 11:56 +0100
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-03 18:00 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 02:11 -0400
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-29 02:17 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 03:50 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-01 01:07 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 12:47 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 17:36 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 22:33 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:25 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 02:12 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 12:03 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 12:06 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 00:46 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 08:09 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 12:02 +0100
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-03 18:00 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 22:31 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-04 01:36 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-01 12:26 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 17:31 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 22:49 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:37 +0000
Re: Redundancy/Survival not@telling.you.invalid (Computer Nerd Kev) - 2026-05-30 09:09 +1000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-30 13:17 +0200
Re: Redundancy/Survival not@telling.you.invalid (Computer Nerd Kev) - 2026-05-31 07:33 +1000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-31 00:14 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-31 12:09 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-01 00:51 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-01 12:28 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-31 12:58 +0200
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-05-27 20:51 +0000
Re: Redundancy/Survival John Ames <commodorejohn@gmail.com> - 2026-05-27 14:02 -0700
Re: Redundancy/Survival not@telling.you.invalid (Computer Nerd Kev) - 2026-05-28 08:54 +1000
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-05-28 05:04 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 03:54 -0400
Re: Redundancy/Survival Andy Burns <usenet@andyburns.uk> - 2026-05-28 09:15 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 12:29 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-28 13:45 +0200
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-05-29 02:50 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-29 01:17 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-29 06:48 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-30 04:25 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-30 13:20 +0200
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-05-30 14:16 +0000
Re: Redundancy/Survival Robert Riches <spamtrap42@jacob21819.net> - 2026-05-30 04:00 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-26 23:41 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-27 14:09 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 03:51 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-28 17:08 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 22:14 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-29 04:41 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-29 01:53 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-29 06:32 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 13:19 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 22:52 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:46 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-03 00:27 -0400
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 03:26 -0400
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-03 21:30 -0400
Re: Redundancy/Survival Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-04 04:30 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-04 08:13 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 03:03 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 12:12 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 12:08 +0100
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-03 12:33 +0100
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-03 14:45 +0100
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 13:08 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 22:55 +0200
Re: Redundancy/Survival Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-02 10:39 +0100
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 13:21 +0200
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-03 02:57 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-26 22:39 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-27 14:10 +0100
Re: Redundancy/Survival not@telling.you.invalid (Computer Nerd Kev) - 2026-05-28 09:05 +1000
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-28 08:19 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 03:52 -0400
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-05-28 09:20 +0100
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-28 20:34 -0400
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-05-28 21:07 -0400
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 13:40 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-01 19:12 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 10:28 +0200
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-02 12:15 -0400
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 16:19 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 18:30 +0200
Re: Redundancy/Survival The Natural Philosopher <tnp@invalid.invalid> - 2026-06-02 18:29 +0100
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-02 16:49 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-03 12:18 +0200
Re: Redundancy/Survival Marco Moock <mm@dorfdsl.de> - 2026-06-02 17:38 +0200
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 15:48 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 00:39 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 17:55 +0200
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 16:03 +0000
Re: Redundancy/Survival InterLinked <usenet@phreaknet.org> - 2026-06-02 12:22 -0400
Re: Redundancy/Survival TheLastSysop <thelastsysop@dev.null> - 2026-06-02 16:36 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-02 18:39 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-06-03 00:48 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-29 01:21 +0000
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-29 02:08 -0400
Re: Redundancy/Survival rbowman <bowman@montana.com> - 2026-05-29 06:41 +0000
Re: Redundancy/Survival Rich <rich@example.invalid> - 2026-06-01 13:23 +0000
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-06-01 23:00 +0200
Re: Redundancy/Survival Marco Moock <mm@dorfdsl.de> - 2026-05-26 09:44 +0200
Re: Redundancy/Survival c186282 <c186282@nnada.net> - 2026-05-26 04:45 -0400
Re: Redundancy/Survival "Carlos E.R." <robin_listas@es.invalid> - 2026-05-26 11:38 +0200
Re: Redundancy/Survival "Worst Case" <fritz@spamexpire-202605.rodent.frell.theremailer.net> - 2026-05-26 17:21 +0200
Page 10 of 17 — ← Prev page 1 … 8 9 [10] 11 12 … 17 Next page →
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-07 05:40 -0400 |
| Message-ID | <iVidndfKs8I0obj3nZ2dnZfqnPSdnZ2d@giganews.com> |
| In reply to | #87616 |
On 6/6/26 15:56, rbowman wrote: > On Sat, 6 Jun 2026 01:56:59 -0400, c186282 wrote: > >> So, 'wireless' is the modern choice - even when it sucks for the >> customers. Hey, just TELL 'em it's So Great .... > > I can't complain about Verizon's wireless. It works for me. My phone is > Mint so I get ads from Mint about their 5G plans that are cheaper than > Verizon. The website says it's not available where I am. It's the T- > Mobile network. The phone is usually 4G although there are a few dead > spots indoors. MY 5g just SUCKS. Too far from the tower, concrete house, steel roof. NEVER gonna get more than one or two bars EVER. It's actually a tad less reliable than my old Gen-2 DSL. But ... all the OTHER providers use the SAME towers. > I keep looking at StarLink. Maybe I'll wait until Musk gets a million LEOs > up. It was more a proof of concept than anything useful but I remember > being out in the backyard waiting to see Echo 1 transit the sky. I don't > think you can see any of the LEOs with the naked eye anymore. Just as well > as it would probably look like a cloud of bluebottle flies orbiting a road > killed deer on a hot august day. StarLink has good potential as a BACKUP, Just In Case. Doesn't allow lots of bytes, but you could still do yer online banking and such. Dammit ... 5AM again. Can't stay awake in the day, can't sleep at night. Welcome to Retirement - it all just starts to blend together .......... Kinda interesting surreality actually ....
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-07 19:25 +0000 |
| Message-ID | <n8lut9Fec78U10@mid.individual.net> |
| In reply to | #87642 |
On Sun, 7 Jun 2026 05:40:39 -0400, c186282 wrote: > StarLink has good potential as a BACKUP, Just In Case. > Doesn't allow lots of bytes, but you could still do yer online > banking and such. I'm going to give it a try. They claim 100 Mbps, no data cap, and no charge for the hardware for $55 / month for residential. There's a 30 day trial period too. Installation is DIY, mostly putting the receiver someplace and running an ethernet cable to the router. It's power over ethernet so no other messing around. It even has some scheme to automatically heat the receiver when it snows. I downloaded the app to the phone last night. You do a 360 degree scan of the sky to find a suitable location. I don't know if what shows up as you scan is the real satellites but if it is there are a hell of a lot of them.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2026-06-07 20:37 +0100 |
| Message-ID | <n8lvjuFo9i0U1@mid.individual.net> |
| In reply to | #87657 |
rbowman wrote: > I downloaded the app to the phone last night. You do a 360 degree scan of > the sky to find a suitable location. I don't know if what shows up as you > scan is the real satellites but if it is there are a hell of a lot of > them. <https://satellitemap.space/constellation/starlink>
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-08 00:57 +0000 |
| Message-ID | <n8mic2FqrflU2@mid.individual.net> |
| In reply to | #87659 |
On Sun, 7 Jun 2026 20:37:20 +0100, Andy Burns wrote: > https://satellitemap.space/constellation/starlink Thanks! That's about what it looked like on the phone app. I don't know whether I should be impressed or appalled. https://subseacables.blogspot.com/2025/07/the-low-satellite-life- expectancy-of.html That's a lot of stuff that will come down in a few years and hopefully burn up on reentry. I'd rather not think about the long term results of the celestial dumpster fire. Anyway, I'll see how it goes. The gear is supposed to arrive towards the end of the month. S&H was $20 and no charge for the electronics. When I looked a year or two ago the gear was around $300 iirc. Musk is no fool and I'm sure he isn't running a charity so I'm not going to check a gift horse's teeth.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-08 00:23 -0400 |
| Message-ID | <InGdndvgSotm3rv3nZ2dnZfqn_qdnZ2d@giganews.com> |
| In reply to | #87657 |
On 6/7/26 15:25, rbowman wrote: > On Sun, 7 Jun 2026 05:40:39 -0400, c186282 wrote: > >> StarLink has good potential as a BACKUP, Just In Case. >> Doesn't allow lots of bytes, but you could still do yer online >> banking and such. > > I'm going to give it a try. They claim 100 Mbps, no data cap, and no > charge for the hardware for $55 / month for residential. There's a 30 day > trial period too. Installation is DIY, mostly putting the receiver > someplace and running an ethernet cable to the router. It's power over > ethernet so no other messing around. It even has some scheme to > automatically heat the receiver when it snows. > > I downloaded the app to the phone last night. You do a 360 degree scan of > the sky to find a suitable location. I don't know if what shows up as you > scan is the real satellites but if it is there are a hell of a lot of > them. There are various StarLink plans for my area ... I think including an "unlimited" plan though they DO seem to get their money anyhow. 100mbps is pretty slow by today's GB+ standards, but it's still good enough to do the usual online biz and banking stuff in case of emergency. Need JUST enough power to fire up the box and a laptop for like 30 minutes a day. So, yea, really MAY go that way. "Security" COSTS a bit ... but can be WELL worth it when the bovine offal hits the proverbial oscillatory airfoil.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-08 14:45 +0000 |
| Message-ID | <n8o2t7FqrflU10@mid.individual.net> |
| In reply to | #87679 |
On Mon, 8 Jun 2026 00:23:27 -0400, c186282 wrote: > 100mbps is pretty slow by today's GB+ standards, but it's still good > enough to do the usual online biz and banking stuff in case of > emergency. Need JUST enough power to fire up the box and a laptop for > like 30 minutes a day. Are you shitting me? https://fiber.google.com/speedtest/ shows 6.5 Mbps down. https:// www.speedtest.net/ shows 3.59 Mbps down. Neither show upload which I assume is related to the Verizon IP juggling. I watch streaming movies and TV shows, youtube videos, and so forth with no buffering, No, I don't have a houseful of kids playing HD games or streaming HD videos.
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2026-06-08 01:00 +0000 |
| Message-ID | <110547i$2soi0$5@dont-email.me> |
| In reply to | #87503 |
c186282 <c186282@nnada.net> wrote: > On 6/4/26 11:31, The Natural Philosopher wrote: >> On 04/06/2026 15:57, c186282 wrote: >>> The sheer mass of copper often meant it was less likely to "flap in >>> the breeze" compared to a skinny fiber. The entire south and east >>> coast of the USA get big HURRICANES ... so 'flapping' is relevant. >>> >> Christ on a bike, Is there no end to your ignorance? NOTHING goes >> overhead without a steel support core. > > NOW, typically. Not THAT long ago, it was just a PVC clad wire. > Expect LOTS of 'legacy' installs. Bzzt... No, wrong again. There's always a steel cable somewhere, and has always been one for a very long time. Either it is external, and the "PVC bundle" is wired to it for support, or it is actually inside the PVC clad wire as the central core. But there is a steel cable somewhere. Copper is much too ductile to take the strain of self-support between poles, and fiber simply does not appreciate much of any tension in the cable at all. Physics dictates the steel cable be present.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-08 00:38 -0400 |
| Message-ID | <SCudnXen6J_Z2rv3nZ2dnZfqn_ednZ2d@giganews.com> |
| In reply to | #87672 |
On 6/7/26 21:00, Rich wrote: > c186282 <c186282@nnada.net> wrote: >> On 6/4/26 11:31, The Natural Philosopher wrote: >>> On 04/06/2026 15:57, c186282 wrote: >>>> The sheer mass of copper often meant it was less likely to "flap in >>>> the breeze" compared to a skinny fiber. The entire south and east >>>> coast of the USA get big HURRICANES ... so 'flapping' is relevant. >>>> >>> Christ on a bike, Is there no end to your ignorance? NOTHING goes >>> overhead without a steel support core. >> >> NOW, typically. Not THAT long ago, it was just a PVC clad wire. >> Expect LOTS of 'legacy' installs. > > Bzzt... No, wrong again. Bzzt ... been there, SEEN it, STILL see it. But I don't live in the Big City. > There's always a steel cable somewhere, and > has always been one for a very long time. Either it is external, and > the "PVC bundle" is wired to it for support, or it is actually inside > the PVC clad wire as the central core. But there is a steel cable > somewhere. Copper is much too ductile to take the strain of > self-support between poles, and fiber simply does not appreciate much > of any tension in the cable at all. Physics dictates the steel cable > be present. For not TOO long runs, the jacketing material plus the copper are (usually) Strong Enough.
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2026-06-08 16:50 +0000 |
| Message-ID | <1106rs0$3cc4j$1@dont-email.me> |
| In reply to | #87682 |
c186282 <c186282@nnada.net> wrote: > On 6/7/26 21:00, Rich wrote: >> c186282 <c186282@nnada.net> wrote: >>> On 6/4/26 11:31, The Natural Philosopher wrote: >>>> On 04/06/2026 15:57, c186282 wrote: >>>>> The sheer mass of copper often meant it was less likely to "flap in >>>>> the breeze" compared to a skinny fiber. The entire south and east >>>>> coast of the USA get big HURRICANES ... so 'flapping' is relevant. >>>>> >>>> Christ on a bike, Is there no end to your ignorance? NOTHING goes >>>> overhead without a steel support core. >>> >>> NOW, typically. Not THAT long ago, it was just a PVC clad wire. >>> Expect LOTS of 'legacy' installs. >> >> Bzzt... No, wrong again. > > Bzzt ... been there, SEEN it, STILL see it. Then you missed something.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-04 18:13 +0000 |
| Message-ID | <n8dthvFfaguU3@mid.individual.net> |
| In reply to | #87499 |
On Thu, 4 Jun 2026 10:57:24 -0400, c186282 wrote: > Note those fiber-guided weapons, that fiber is hair-thin, > not intended to be any kind of permanent comm link. > > Interesting though how the mil went from wire-guided, to RF/Laser, > and now back to a version of "wire". I remember reading about TOW missiles beck in the '70s or '80s. My first thought was if you had to keep the aiming device on target you were exposed. To keep the math simple, if you targeted something near the maximum range of 3000 m with a missile moving at 300 m/sec you were in the breeze for a long time. I think I would prefer a fire-and-forget missile.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-04 15:03 -0400 |
| Message-ID | <N_WdnRefmcZhVrz3nZ2dnZfqnPgAAAAA@giganews.com> |
| In reply to | #87508 |
On 6/4/26 14:13, rbowman wrote: > On Thu, 4 Jun 2026 10:57:24 -0400, c186282 wrote: > >> Note those fiber-guided weapons, that fiber is hair-thin, >> not intended to be any kind of permanent comm link. >> >> Interesting though how the mil went from wire-guided, to RF/Laser, >> and now back to a version of "wire". > > I remember reading about TOW missiles beck in the '70s or '80s. My first > thought was if you had to keep the aiming device on target you were > exposed. To keep the math simple, if you targeted something near the > maximum range of 3000 m with a missile moving at 300 m/sec you were in the > breeze for a long time. I think I would prefer a fire-and-forget missile. On the whole I agree fully - shoot and DUCK ! In Ukraine though, the target may be 30+ KM away, you're not likely to have someone immediately shooting back at you. JAMMING is the big problem with RF manual guidance. In the news I'm seeing more and more stories about how both Russian and Ukrainian drones are suddenly showing up in the wrong countries - both sides are using jammers on them. Laser-spot guidance ... at least in the day it's harder to track the beam back to YOU, but at night ... Oh well, the usual - what one side comes up with the other will discover how to thwart the next week.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-04 22:27 +0000 |
| Message-ID | <n8ecevFg3jkU3@mid.individual.net> |
| In reply to | #87514 |
On Thu, 4 Jun 2026 15:03:07 -0400, c186282 wrote: > In Ukraine though, the target may be 30+ KM away, > you're not likely to have someone immediately shooting back at you. https://www.thinkdefence.co.uk/2023/05/fibre-optic-guided-missiles-efog-m- polyphem-and-others/ I find many articles about long range fiber optic guided missiles but most of them end with the program being terminated. Interesting idea though. It might get messy with 30 km long strands of fibers draped over trees and so forth. They probably weren't biodegradable too and might put wildlife at risk. I was curious about the short range TOWs too.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-04 22:45 -0400 |
| Message-ID | <lNCcnecBefD_pb_3nZ2dnZfqn_udnZ2d@giganews.com> |
| In reply to | #87518 |
On 6/4/26 18:27, rbowman wrote: > On Thu, 4 Jun 2026 15:03:07 -0400, c186282 wrote: > >> In Ukraine though, the target may be 30+ KM away, >> you're not likely to have someone immediately shooting back at you. > > https://www.thinkdefence.co.uk/2023/05/fibre-optic-guided-missiles-efog-m- > polyphem-and-others/ > > I find many articles about long range fiber optic guided missiles but most > of them end with the program being terminated. Interesting idea though. It > might get messy with 30 km long strands of fibers draped over trees and so > forth. They probably weren't biodegradable too and might put wildlife at > risk. > > I was curious about the short range TOWs too. I'm sure it gets "messy" trailing 30-50km long naked ultra-thin fibers. VERY good chance they'll get broken en-route. But, if the opponent gets too good at jamming projectiles using other tech ...... This IS apparently the case now. Russia has been jamming conventional GPS for quite awhile now - throwing off coords by a good KM or so. Ukraine MAY have been given access to US/NATO special GPS sats, but no doubt Russia has salvaged such guidance systems and reverse-engineered one or more solutions. A new alt is super-rez 'inertial' guidance using light-loop tech. Set yer start coords EXACTLY and they're good for a fair distance and time. I read that Poland and the Baltics were looking into this once Russia started jamming GPS. Smallish cheapish chips now. I think they're used in some civvie drones already. A company came by to demonstrate its drone - hovered perfectly still even in kinda gusty winds. You could poke at it and it'd bounce back almost instantly. That's not GPS, its super-sensitive tri-axis accelerometers.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-05 04:42 +0000 |
| Message-ID | <n8f2ehFl49dU4@mid.individual.net> |
| In reply to | #87522 |
On Thu, 4 Jun 2026 22:45:45 -0400, c186282 wrote: > A new alt is super-rez 'inertial' guidance > using light-loop tech. Set yer start coords EXACTLY and they're good > for a fair distance and time. I read that Poland and the Baltics were > looking into this once Russia started jamming GPS. Smallish cheapish > chips now. Full circle. One of the drivers for GPS is if you fire a ballistic missile from a submarine it helps to know exactly where you are. > I think they're used in some civvie drones already. A company came by > to demonstrate its drone - hovered perfectly still even in kinda > gusty winds. You could poke at it and it'd bounce back almost > instantly. That's not GPS, > its super-sensitive tri-axis accelerometers. https://www.techgearlab.com/reviews/cool-gadgets/drones/dji-tello It's so light but it can maintain position in a gentle breeze. No GPS. It uses a down facing camera. Neat idea and it came with a SDK to control it over BlueTooth. It was $99 when I bought it. I've got a larger drone but it's strictly manual control like an old-time RC plane.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-05 02:01 -0400 |
| Message-ID | <Jz-dneQY7bX7-7_3nZ2dnZfqnPSdnZ2d@giganews.com> |
| In reply to | #87534 |
On 6/5/26 00:42, rbowman wrote: > On Thu, 4 Jun 2026 22:45:45 -0400, c186282 wrote: > >> A new alt is super-rez 'inertial' guidance >> using light-loop tech. Set yer start coords EXACTLY and they're good >> for a fair distance and time. I read that Poland and the Baltics were >> looking into this once Russia started jamming GPS. Smallish cheapish >> chips now. > > Full circle. One of the drivers for GPS is if you fire a ballistic missile > from a submarine it helps to know exactly where you are. Yep, kinda "full circle". The new/better tech was, big surprise, more VULNERABLE in more WAYS. >> I think they're used in some civvie drones already. A company came by >> to demonstrate its drone - hovered perfectly still even in kinda >> gusty winds. You could poke at it and it'd bounce back almost >> instantly. That's not GPS, >> its super-sensitive tri-axis accelerometers. > > https://www.techgearlab.com/reviews/cool-gadgets/drones/dji-tello > > It's so light but it can maintain position in a gentle breeze. No GPS. It > uses a down facing camera. Neat idea and it came with a SDK to control it > over BlueTooth. It was $99 when I bought it. Hmm ... wouldn't have immediately thought of using a camera ground image as a reference. Not THE best, but apparently CAN work within limits. What happens if the drone is going over WATER ??? The accelerometers, now hyper-sensitive AND cheap, are the current Best Option. > I've got a larger drone but it's strictly manual control like an old-time > RC plane. Good enough for fun. "Commercial" though, much better IS expected. Fully self-navigating especially. GPS is pretty good in a friendly zone, but NOT in a tech war zone now. Where I worked DID hire the mentioned drone firm to do various things In The Field. You could launch it from anywhere, it'd zoom to EXACT coordinates and then begin its complicated runs. Then it'd return exactly to like a one meter circle after. These were not terribly large drones either ... might carry 20-40 lbs of stuff. We USED to use airplanes for such things ... but the pop density became too great, MANY complaints from people thinking they were being attacked - or super-annoyed with the noise. So, little drones. Mostly they didn't even see them.
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2026-06-03 02:10 +0000 |
| Message-ID | <10vo2eb$3b3aj$2@dont-email.me> |
| In reply to | #87349 |
InterLinked <usenet@phreaknet.org> wrote: > On 6/1/2026 2:30 PM, Rich wrote: >> Carlos E.R. <robin_listas@es.invalid> wrote: >>> On 2026-06-01 05:20, Rich wrote: >>> What could happen is mandating the router or ONT have a battery backup >>> included, or at least optional. As simple as installing a bunch of AA >>> batteries. >> >> Yep, that's already what Verizon does with their FIOS service. One >> gets either a lead acid battery (UPS style battery) that will power the >> ONT for "some time" on a power fail, or one gets a rather large box >> that holds something like 12 D sized alkaline cell batteries as the >> "backup power" should mains be out. I'm not sure if the different >> types arrive based on price level purchased, or just on "previously, >> they privided this, now they provide that". > > The lead acid is the older variety and the D cell is the newer one. I > had to buy the older kind on eBay as they are not really available > anymore. Ah, that sounds reasonable, and is very in keeping with cheapening the product as time goes on. > Neither is sufficient, you can get 8-24 hours of standby power > with these kinds, but that's woefully inadequate in an extended outage, Yep. What they provide is, hopefully, enough time to call the electric utility to report your power being out. But for extended outages, yes, within at most one day (and that assumes the batteries still contain their original energy amounts) you'll be out of communication. > and both are now a significant cost that consumers are now expected > to bear. Also true. They supply the original battery, but you get to pay to replace it when it wears out over time. And both wear out over time. The lead acid from being kept charged, the D cells from self discharge.
[toc] | [prev] | [next] | [standalone]
| From | InterLinked <usenet@phreaknet.org> |
|---|---|
| Date | 2026-06-02 22:29 -0400 |
| Message-ID | <10vo3hu$3bkkd$1@dont-email.me> |
| In reply to | #87397 |
On 6/2/2026 10:10 PM, Rich wrote: > InterLinked <usenet@phreaknet.org> wrote: >> and both are now a significant cost that consumers are now expected >> to bear. > > Also true. They supply the original battery, but you get to pay to > replace it when it wears out over time. And both wear out over time. > The lead acid from being kept charged, the D cells from self discharge. Worse! They don't even supply the original battery! I had to buy my own as well as the unit. And most people don't even bother and then are surprised when their phone doesn't work when the power goes out. At one point the battery was low on my original battery and the ONT did start beeping every 15 minutes, which was annoying. A Verizon tech happened to be visiting for something else and he got a kick out of seeing some vintage telephones around the home, so I got lucky and he gave me a free replacement battery from the truck. Not sure if that was any skin off his nose... but might have to fake a service call the next time it runs low and see if I can pull the same trick!
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-06-03 11:52 +0200 |
| Message-ID | <63a5fmxucn.ln2@Telcontar.valinor> |
| In reply to | #87401 |
On 2026-06-03 04:29, InterLinked wrote: > On 6/2/2026 10:10 PM, Rich wrote: >> InterLinked <usenet@phreaknet.org> wrote: >>> and both are now a significant cost that consumers are now expected >>> to bear. >> >> Also true. They supply the original battery, but you get to pay to >> replace it when it wears out over time. And both wear out over time. >> The lead acid from being kept charged, the D cells from self discharge. > > Worse! They don't even supply the original battery! I had to buy my own > as well as the unit. And most people don't even bother and then are > surprised when their phone doesn't work when the power goes out. > > At one point the battery was low on my original battery and the ONT did > start beeping every 15 minutes, which was annoying. A Verizon tech > happened to be visiting for something else and he got a kick out of > seeing some vintage telephones around the home, so I got lucky and he > gave me a free replacement battery from the truck. Not sure if that was > any skin off his nose... but might have to fake a service call the next > time it runs low and see if I can pull the same trick! Here the normal thing is to connect traditional phones to the ONT. They maintain the fantasy that everything was as it were (and charge the same prices). Actually, if you ask them, it is not possible to connect real VoIP phones. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2026-06-04 19:18 +0000 |
| Message-ID | <10vsj2n$k3v6$1@dont-email.me> |
| In reply to | #87418 |
Carlos E.R. <robin_listas@es.invalid> wrote: > On 2026-06-03 04:29, InterLinked wrote: >> On 6/2/2026 10:10 PM, Rich wrote: >>> InterLinked <usenet@phreaknet.org> wrote: >>>> and both are now a significant cost that consumers are now expected >>>> to bear. >>> >>> Also true. They supply the original battery, but you get to pay to >>> replace it when it wears out over time. And both wear out over time. >>> The lead acid from being kept charged, the D cells from self discharge. >> >> Worse! They don't even supply the original battery! I had to buy my own >> as well as the unit. And most people don't even bother and then are >> surprised when their phone doesn't work when the power goes out. >> >> At one point the battery was low on my original battery and the ONT did >> start beeping every 15 minutes, which was annoying. A Verizon tech >> happened to be visiting for something else and he got a kick out of >> seeing some vintage telephones around the home, so I got lucky and he >> gave me a free replacement battery from the truck. Not sure if that was >> any skin off his nose... but might have to fake a service call the next >> time it runs low and see if I can pull the same trick! > > Here the normal thing is to connect traditional phones to the ONT. They > maintain the fantasy that everything was as it were (and charge the same > prices). Actually, if you ask them, it is not possible to connect real > VoIP phones. Same here with Verizon FIOS. My ONT has an ethernet port, a coax port for cable TV, and either a modular jack or screw down terminals for POTS wiring (or it might have both the modular jack and the screw down terminals). If I had their phone service, the ONT would act as the "central office" and provide the 48v standby, 60v RMS AC ring signal, and handle the D/A and A/D conversion from old analog POTS to however Verizon carries digitized voice phone data over FIOS when that feature is enabled. Effectively, the ONT is /acting like/ one of those POTS to VOIP adapters, just using whatever protocol Verizon uses behind the scenes to carry the data. That protocol might just be VOIP, it might be something else, needless to say, they do not tell customers what it is nor provide us any normal access into that part of the system.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E.R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-06-04 21:28 +0200 |
| Message-ID | <f709fmxarr.ln2@Telcontar.valinor> |
| In reply to | #87515 |
On 2026-06-04 21:18, Rich wrote: > Carlos E.R. <robin_listas@es.invalid> wrote: >> On 2026-06-03 04:29, InterLinked wrote: >>> On 6/2/2026 10:10 PM, Rich wrote: >>>> InterLinked <usenet@phreaknet.org> wrote: >>>>> and both are now a significant cost that consumers are now expected >>>>> to bear. >>>> >>>> Also true. They supply the original battery, but you get to pay to >>>> replace it when it wears out over time. And both wear out over time. >>>> The lead acid from being kept charged, the D cells from self discharge. >>> >>> Worse! They don't even supply the original battery! I had to buy my own >>> as well as the unit. And most people don't even bother and then are >>> surprised when their phone doesn't work when the power goes out. >>> >>> At one point the battery was low on my original battery and the ONT did >>> start beeping every 15 minutes, which was annoying. A Verizon tech >>> happened to be visiting for something else and he got a kick out of >>> seeing some vintage telephones around the home, so I got lucky and he >>> gave me a free replacement battery from the truck. Not sure if that was >>> any skin off his nose... but might have to fake a service call the next >>> time it runs low and see if I can pull the same trick! >> >> Here the normal thing is to connect traditional phones to the ONT. They >> maintain the fantasy that everything was as it were (and charge the same >> prices). Actually, if you ask them, it is not possible to connect real >> VoIP phones. > > Same here with Verizon FIOS. My ONT has an ethernet port, a coax port > for cable TV, and either a modular jack or screw down terminals for > POTS wiring (or it might have both the modular jack and the screw down > terminals). > > If I had their phone service, the ONT would act as the "central office" > and provide the 48v standby, 60v RMS AC ring signal, and handle the D/A > and A/D conversion from old analog POTS to however Verizon carries > digitized voice phone data over FIOS when that feature is enabled. > > Effectively, the ONT is /acting like/ one of those POTS to VOIP > adapters, just using whatever protocol Verizon uses behind the scenes > to carry the data. That protocol might just be VOIP, it might be > something else, needless to say, they do not tell customers what it is > nor provide us any normal access into that part of the system. In my case, it is actually VoIP and you can connect to it on your computer. The details have been reverse engineered. -- Cheers, Carlos. ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
Page 10 of 17 — ← Prev page 1 … 8 9 [10] 11 12 … 17 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web