Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #64371 > unrolled thread
| Started by | "186282@ud0s4.net" <186283@ud0s4.net> |
|---|---|
| First post | 2025-01-14 23:37 -0500 |
| Last post | 2025-01-17 10:48 +0100 |
| Articles | 20 on this page of 389 — 17 participants |
Back to article view | Back to comp.os.linux.misc
News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-14 23:37 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-15 10:10 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-15 23:29 -0500
Re: News : ARM Trying to Buy AmpereComputing Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-16 05:03 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-16 11:58 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-16 11:18 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-16 17:12 +0100
Re: News : ARM Trying to Buy AmperComputing not@telling.you.invalid (Computer Nerd Kev) - 2025-01-17 07:35 +1000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-16 23:58 +0000
Re: News : ARM Trying to Buy AmperComputing Computer Nerd Kev <not@telling.you.invalid> - 2025-01-17 12:20 +1000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-17 00:46 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-17 07:05 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-17 03:20 -0500
Re: News : ARM Trying to Buy AmperComputing John Ames <commodorejohn@gmail.com> - 2025-01-17 08:17 -0800
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-17 10:32 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-17 19:37 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-18 11:39 +0100
Raspberry NAS, anyone? Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-01-18 14:57 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-18 20:05 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-19 11:47 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-19 13:14 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-19 23:02 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-20 09:07 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-19 18:33 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-20 10:30 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-20 10:10 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-20 13:51 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-20 21:58 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-20 20:04 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-21 10:13 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-21 18:55 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 10:28 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-22 18:50 +0000
Re: News : ARM Trying to Buy AmperComputing not@telling.you.invalid (Computer Nerd Kev) - 2025-01-23 06:47 +1000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 22:34 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 00:00 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 16:42 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 16:13 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 21:59 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-24 01:57 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-24 00:52 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-24 19:13 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 01:24 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 02:02 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 19:35 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 11:21 +0000
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-24 20:27 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 01:26 +0000
Re: News : ARM Trying to Buy AmperComputing Computer Nerd Kev <not@telling.you.invalid> - 2025-01-25 17:14 +1000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:24 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 11:16 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-24 19:16 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 00:58 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 11:04 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 22:29 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-22 23:58 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 16:40 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-23 00:37 +0000
Maker spaces Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-01-23 02:17 +0000
Re: Maker spaces rbowman <bowman@montana.com> - 2025-01-23 04:50 +0000
Re: Maker spaces Rich <rich@example.invalid> - 2025-01-23 13:38 +0000
Re: Maker spaces Joe Makowiec <makowiec@invalid.invalid> - 2025-01-24 01:48 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 16:46 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 16:32 +0000
Re: News : ARM Trying to Buy AmperComputing not@telling.you.invalid (Computer Nerd Kev) - 2025-01-24 06:22 +1000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 09:44 +0000
Re: News : ARM Trying to Buy AmperComputing Computer Nerd Kev <not@telling.you.invalid> - 2025-01-25 17:36 +1000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:39 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 19:41 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 21:38 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-23 04:56 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 20:34 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-23 05:07 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-23 03:10 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 09:15 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-23 08:58 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 15:08 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-23 17:58 +0000
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-23 13:44 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-23 09:05 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 15:06 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-23 10:15 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 15:57 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-23 17:55 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 22:07 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 16:53 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-21 19:30 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-22 07:50 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 10:35 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-21 09:43 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-20 21:53 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-20 19:42 -0500
Synology Diskstation architecture (was: Re: News : ARM Trying to Buy AmperComputing) vallor <vallor@cultnix.org> - 2025-01-21 02:48 +0000
Re: Synology Diskstation architecture (was: Re: News : ARM Trying to Buy AmperComputing) "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-20 23:29 -0500
Re: Synology Diskstation architecture (was: Re: News : ARM Trying to Buy AmperComputing) vallor <vallor@cultnix.org> - 2025-01-22 20:56 +0000
Re: Synology Diskstation architecture (was: Re: News : ARM Trying to Buy AmperComputing) "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 18:47 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-21 10:12 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-21 19:56 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-21 19:17 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 10:32 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 21:29 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 16:51 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-23 19:18 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-24 10:27 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 11:46 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-24 19:21 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-24 18:57 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-24 23:16 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 01:39 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 11:07 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-24 19:24 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-24 23:19 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 00:55 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 02:27 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 11:34 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:36 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 18:34 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 17:54 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 23:33 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 00:14 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 21:24 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 09:49 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 15:30 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 20:25 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 10:03 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-27 19:01 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 22:25 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 22:38 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 10:44 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:43 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 18:35 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 18:03 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 23:35 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 19:29 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 23:38 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 00:00 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 22:01 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:39 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 20:01 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 09:57 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 11:37 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 20:40 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 10:07 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-27 09:44 +0000
Political evolution (Libertarianism) Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-01-26 00:36 +0000
Re: Political evolution (Libertarianism) Steve Hayes <hayesstw@telkomsa.net> - 2025-01-26 05:31 +0200
Re: Political evolution (Libertarianism) "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 22:36 -0500
Re: Political evolution (Libertarianism) rbowman <bowman@montana.com> - 2025-01-26 19:25 +0000
Re: Political evolution (Libertarianism) D <nospam@example.net> - 2025-01-26 11:44 +0100
Re: Political evolution (Libertarianism) rbowman <bowman@montana.com> - 2025-01-26 19:33 +0000
Re: Political evolution (Libertarianism) D <nospam@example.net> - 2025-01-27 09:55 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 21:32 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 03:33 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-26 03:49 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 21:13 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-26 18:30 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-27 00:42 +0000
Re: News : ARM Trying to Buy AmperComputing "186283@ud0s4.net" <186284@ud0s4.net> - 2025-01-27 00:03 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-27 05:53 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-27 01:22 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-27 18:54 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-27 22:20 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-28 05:36 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-28 02:24 -0500
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-28 20:01 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-28 21:23 +0000
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-28 23:11 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-29 03:45 +0000
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-29 04:23 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-29 06:02 +0000
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-28 20:28 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-28 21:42 +0100
Re: News : ARM Trying to Buy AmperComputing not@telling.you.invalid (Computer Nerd Kev) - 2025-01-29 07:22 +1000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-29 15:14 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-28 23:58 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-29 15:19 +0100
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-28 16:20 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-29 15:12 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-30 01:15 +0000
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-30 05:43 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-30 01:01 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-30 10:37 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-30 10:01 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-30 18:41 +0100
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-30 05:08 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-30 18:43 +0100
Turn your Radio On Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-01-30 14:05 +0000
Re: Turn your Radio On D <nospam@example.net> - 2025-01-30 18:49 +0100
Re: Turn your Radio On rbowman <bowman@montana.com> - 2025-01-30 19:35 +0000
Re: Turn your Radio On D <nospam@example.net> - 2025-01-30 22:15 +0100
Re: Turn your Radio On rbowman <bowman@montana.com> - 2025-01-31 01:18 +0000
Re: Turn your Radio On D <nospam@example.net> - 2025-01-31 13:47 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-30 17:24 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-30 19:43 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-30 22:16 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-30 22:07 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 13:41 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 01:43 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-30 21:24 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 06:26 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 13:49 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 19:36 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 23:37 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-02-01 05:16 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-02-01 11:37 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 13:49 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 13:48 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-30 10:33 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-30 09:33 +0000
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-30 17:31 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-30 19:45 +0000
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-30 20:13 +0000
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-30 20:39 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-30 21:25 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-30 21:19 +0000
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-30 22:54 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-30 20:43 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 06:22 +0000
Re: News : ARM Trying to Buy AmperComputing not@telling.you.invalid (Computer Nerd Kev) - 2025-01-31 08:08 +1000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 01:35 +0000
Re: News : ARM Trying to Buy AmperComputing Robert Riches <spamtrap42@jacob21819.net> - 2025-01-31 04:49 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-31 00:44 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 06:49 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-31 02:09 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-31 10:33 +0000
Turn Your Radio On ... Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-01-31 16:48 +0000
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-01-31 23:03 +0100
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-31 20:08 -0500
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-01 04:36 +0000
Re: Turn Your Radio On ... Rich <rich@example.invalid> - 2025-02-01 05:05 +0000
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-01 01:52 -0500
Re: Turn Your Radio On ... Rich <rich@example.invalid> - 2025-02-01 17:40 +0000
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-01 08:14 +0000
Re: Turn Your Radio On ... Lars Poulsen <lars@cleo.beagle-ears.com> - 2025-02-01 19:47 +0000
Re: Turn Your Radio On ... Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-02-01 19:57 +0000
Re: Turn Your Radio On ... The Natural Philosopher <tnp@invalid.invalid> - 2025-02-01 20:13 +0000
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-02 00:24 +0000
Re: Turn Your Radio On ... Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-02-02 06:10 +0000
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-02 20:41 -0500
Re: Turn Your Radio On ... The Natural Philosopher <tnp@invalid.invalid> - 2025-02-02 10:20 +0000
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-02 20:27 +0000
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-02 21:00 -0500
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-01 17:08 -0500
Re: Turn Your Radio On ... The Natural Philosopher <tnp@invalid.invalid> - 2025-02-02 10:18 +0000
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-02 20:54 -0500
Re: Turn Your Radio On ... Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-02-01 19:49 +0000
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-01 01:22 -0500
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-01 11:28 +0100
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-01 18:42 +0000
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-02 11:39 +0100
Re: Turn Your Radio On ... The Natural Philosopher <tnp@invalid.invalid> - 2025-02-02 10:43 +0000
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-02 21:56 +0100
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-03 03:25 +0000
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-03 22:55 +0100
Re: Turn Your Radio On ... Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-02-04 00:36 +0000
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-03 22:52 -0500
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-04 17:35 +0100
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-04 17:28 +0100
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-02 20:31 +0000
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-02 21:59 +0100
Re: Turn Your Radio On ... "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-02-02 01:11 -0500
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-02 11:49 +0100
Re: Turn Your Radio On ... rbowman <bowman@montana.com> - 2025-02-01 04:28 +0000
Re: Turn Your Radio On ... D <nospam@example.net> - 2025-02-01 11:32 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 19:30 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 23:36 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-02-01 04:45 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-02-01 11:34 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-02-01 18:47 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-31 22:54 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-02-01 04:57 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-02-01 11:35 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-02-01 11:27 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-31 10:29 +0000
Re: News : ARM Trying to Buy AmperComputing Robert Riches <spamtrap42@jacob21819.net> - 2025-02-01 04:11 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-02-01 05:00 +0000
Re: News : ARM Trying to Buy AmperComputing Robert Riches <spamtrap42@jacob21819.net> - 2025-02-02 04:13 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 06:44 +0000
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-31 18:21 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-31 19:47 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-31 10:24 +0000
Re: News : ARM Trying to Buy AmperComputing Robert Riches <spamtrap42@jacob21819.net> - 2025-02-01 04:34 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 10:09 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-27 09:46 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 17:45 +0100
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-27 21:55 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-28 10:27 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-27 09:26 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-27 09:00 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:01 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 02:10 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 11:29 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:22 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 18:30 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 19:22 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 23:37 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 21:29 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:00 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 09:25 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:45 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 12:52 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 17:30 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 20:27 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 10:05 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-27 09:41 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 17:44 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-27 20:15 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 22:26 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-24 21:40 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 01:28 +0000
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 03:49 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 02:16 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 19:24 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 10:46 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-25 19:44 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 23:40 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 00:09 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 22:21 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 09:39 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:48 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 13:12 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 17:32 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 20:12 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 10:01 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-27 20:30 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 22:28 +0100
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-27 19:45 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-28 05:38 +0000
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-28 03:13 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-28 10:25 +0100
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-28 20:01 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-28 21:41 +0100
Re: News : ARM Trying to Buy AmperComputing "WokieSux282@ud0s4.net" <WokieSux283@ud0s4.net> - 2025-01-27 22:00 -0500
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 20:09 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-27 10:00 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:41 +0100
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 11:38 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 00:53 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 11:04 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-25 11:19 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 18:29 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 00:12 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 10:51 +0100
Re: News : ARM Trying to Buy AmperComputing Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2025-01-25 20:01 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-25 23:41 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 21:53 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:38 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-26 00:12 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-25 22:22 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-26 13:42 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-26 09:40 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-22 07:48 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 10:34 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-22 20:11 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-22 22:31 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-22 22:55 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 00:05 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-22 21:34 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 16:53 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-23 16:34 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-23 22:02 +0100
Re: News : ARM Trying to Buy AmperComputing Rich <rich@example.invalid> - 2025-01-22 20:08 +0000
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-22 23:55 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-21 18:22 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-17 10:20 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-17 10:33 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-17 16:46 +0100
Re: News : ARM Trying to Buy AmperComputing not@telling.you.invalid (Computer Nerd Kev) - 2025-01-18 07:45 +1000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-18 11:45 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-18 19:26 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-19 11:42 +0100
Re: News : ARM Trying to Buy AmperComputing rbowman <bowman@montana.com> - 2025-01-19 19:03 +0000
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-19 23:08 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-19 18:52 -0500
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-20 09:08 +0000
Re: News : ARM Trying to Buy AmpereComputing Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-20 23:29 +0000
Re: News : ARM Trying to Buy AmpereComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-20 20:26 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-20 10:36 +0100
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-19 18:44 -0500
Re: News : ARM Trying to Buy AmperComputing John Ames <commodorejohn@gmail.com> - 2025-01-20 08:14 -0800
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-20 16:39 +0000
Re: News : ARM Trying to Buy AmperComputing John Ames <commodorejohn@gmail.com> - 2025-01-20 09:00 -0800
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-20 13:56 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-20 21:57 +0100
Re: News : ARM Trying to Buy AmperComputing The Natural Philosopher <tnp@invalid.invalid> - 2025-01-17 10:19 +0000
Re: News : ARM Trying to Buy AmperComputing John Ames <commodorejohn@gmail.com> - 2025-01-17 08:04 -0800
Re: News : ARM Trying to Buy AmpereComputing Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-17 23:12 +0000
Re: News : ARM Trying to Buy AmperComputing "186282@ud0s4.net" <186283@ud0s4.net> - 2025-01-17 00:28 -0500
Re: News : ARM Trying to Buy AmperComputing D <nospam@example.net> - 2025-01-17 10:48 +0100
Page 18 of 20 — ← Prev page 1 … 16 17 [18] 19 20 Next page →
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-25 18:29 +0100 |
| Message-ID | <9f21593e-bd40-f199-da8c-daea5a233af1@example.net> |
| In reply to | #64775 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 25 Jan 2025, The Natural Philosopher wrote: > On 25/01/2025 05:53, 186282@ud0s4.net wrote: >> On 1/24/25 6:46 AM, The Natural Philosopher wrote: >>> On 24/01/2025 09:27, D wrote: >>>> This generated a small storm on my linkedin. I'v >>> >>> It's amazing how people believe that what Trump said to *get* elected, is >>> what he will do now he is, and in the same breath say that he is a born >>> liar... :-) >> >> "Politician" ... >> >> I'd trust Trump a little more than the long-career pols, >> but he's still a politician. >> >> And promises -vs- deliveries are PART of that. >> >>> Putin seems to have fallen into that trap.... >> >> Putin is a hyper-dangerous individual with >> a gigaton of nukes at his immediate command. >> Best to NOT group him in with USA/EU leaders. > > Putin is exactly what the EU would like to be, if it could entirely remove > that pesky democracy thing and have an army of its own. Amen!
[toc] | [prev] | [next] | [standalone]
| From | "186282@ud0s4.net" <186283@ud0s4.net> |
|---|---|
| Date | 2025-01-25 00:12 -0500 |
| Message-ID | <x9SdnSz_VMwk7wn6nZ2dnZfqnPqdnZ2d@earthlink.com> |
| In reply to | #64719 |
On 1/24/25 4:27 AM, D wrote: > > > On Thu, 23 Jan 2025, 186282@ud0s4.net wrote: > >> On 1/23/25 10:51 AM, D wrote: >>> >>> >>> On Wed, 22 Jan 2025, 186282@ud0s4.net wrote: >>> >>>>> Good stuff! I replicate between two countries for added resilience. >>>>> Both rsync and restic work great backing up to a tor hidden >>>>> service. To speed things up, the first backup can be done locally, >>>>> and after that, only deltas are sent from around the world. >>>> >>>> That's how we do it. >>> >>> It is a powerful way to do it! =) >>> >>>> Often you need just a few files from backup, ones somebody >>> >>> With restic you can do it from the client, or, you can mount the >>> backup and >>> navigate the file tree to get any files you like from the server. >>> I've tried the >>> server mount and it worked well, without any surprises. You can of >>> course do >>> full restores as well to a separate folder on the client and move >>> what you like. >>> >>>> oopsied, so huge zip archives can be a negative. OpenSSL >>>> works fast for encryption and the Winders version has >>>> almost exactly the same params. GPG is not so good in >>>> the file-by-file thing because it has a relatively >>>> long start-up time. >>>> >>>> Have never used restic, I'll have to give it a look. >>> >>> Let me know if you find any weaknesses. >>> >>>> Another way to back up is to 'fork' every file write >>>> to another, maybe even remote, drive. SoftRAID seems >>>> to know just what's being written but I've never >>>> figured out exactly how that works. The idea would >>>> be to feed the full file path/name of what's just >>>> been writ/modified into a (de-duplicated) list for >>>> some daemon or whatever to dupe to yer destination - >>>> local or cloud. This would be very quick and not bother >>>> the other gazillion unchanged files. >>> >>> At the dawn of time we used to setup replication between storage >>> systems, then >>> snapshot the replica at various times per day, and for extra >>> security, write out >>> the snapshots to tape for off site storage. That was backups for real >>> men!! >> >> >> Heh heh ... then I guess I was a Real Man right up >> until I retired :-) > > This is the truth! Based on an analysis of your texts it does indeed > seem like you are very manly! > >> Kept a 4-level scheme - main NAS, a mirror NAS that'd >> back up the main twice a day, a Pi+hdd in another >> building for the Most Important files pulled from >> the mirror NAS in the morning and then finally >> some cloud storage for a subset of the files. This >> seemed un-killable. >> >> Once had tapes, SLOW bastards, but that went by the >> wayside. PRICED a decent tape drive lately ??? Kept a >> subset on a disk in my personal box too - mostly >> the high holy payroll stuff. Hey, priorities ! :-) >> >> I think the new guys trust it all to Bill's Cloud. >> They're gonna get a rude surprise someday ... > > I got an article published in a smaller newspaper the other day on this > theme. What happens when Trump turns off the cloud for your country > because he doesn't like your politicians? Will the public sector and 99% > of the companies continue to work? I don't THINK he'd do that - Musk would likely talk him out of it - but he MIGHT. Of course Vlad/Xi can produce the same effect for imperialist reasons, but even worse - nothing left to 'turn on' again, at least in a usefully timely fashion. IMHO, 'cloud' is just too vulnerable to too many hostile interests. Should NEVER be your main backup, or working, repository. Can all go bye-bye tomorrow. A local NAS is far safer. But the people lobbying yer pointy-haired bosses will say the exact opposite .... > This generated a small storm on my linkedin. I've been harping on it for > years, but now that Trump is in power, it seems like the public was > finally ready for my message. ;) Even if he'd never do it - the potential THREAT is enough to Change Thinking ... hopefully towards the smarter.
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-25 10:51 +0100 |
| Message-ID | <0e206d1d-bcb7-432b-33ce-76a85337969d@example.net> |
| In reply to | #64750 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 25 Jan 2025, 186282@ud0s4.net wrote: >>> >>> I think the new guys trust it all to Bill's Cloud. >>> They're gonna get a rude surprise someday ... >> >> I got an article published in a smaller newspaper the other day on this >> theme. What happens when Trump turns off the cloud for your country because >> he doesn't like your politicians? Will the public sector and 99% of the >> companies continue to work? > > I don't THINK he'd do that - Musk would likely talk > him out of it - but he MIGHT. Of course Vlad/Xi can All is fair in the love and marketing! ;) It needs a bit of exaggeration to make it interesting and generate engagement. =) Another theory I have is that Trump could create a tax on all cloud services sold _to_ europe in order to rake back money europe is stealing with their GDPR fines. I think this will be a topic for another marketing article. =) > produce the same effect for imperialist reasons, but > even worse - nothing left to 'turn on' again, at > least in a usefully timely fashion. > > IMHO, 'cloud' is just too vulnerable to too many > hostile interests. Should NEVER be your main > backup, or working, repository. Can all go bye-bye > tomorrow. A local NAS is far safer. You are a wise man! I agree! It can be used as a complement, but never your only one. > But the people lobbying yer pointy-haired bosses > will say the exact opposite .... Sadly not only pointy-haired bosses, but the young and modern IT-generation who have been taught since childhood that "ze cloud" solves all problems magically. =( I try to rectify that when I teach. In every class there are about 5-9 people who "see the light" in Hank Williams words. They go on to become really skilled and passionate technologists! >> This generated a small storm on my linkedin. I've been harping on it for >> years, but now that Trump is in power, it seems like the public was finally >> ready for my message. ;) > > Even if he'd never do it - the potential THREAT is > enough to Change Thinking ... hopefully towards > the smarter. This is the truth! Trump plays european socialist politicians masterfully! It is quite beautiful to watch. =)
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2025-01-25 20:01 +0000 |
| Message-ID | <TqblP.1910725$bYV2.1668063@fx17.iad> |
| In reply to | #64766 |
On 2025-01-25, D <nospam@example.net> wrote:
> On Sat, 25 Jan 2025, 186282@ud0s4.net wrote:
>
>> IMHO, 'cloud' is just too vulnerable to too many
>> hostile interests. Should NEVER be your main
>> backup, or working, repository. Can all go bye-bye
>> tomorrow. A local NAS is far safer.
>
> You are a wise man! I agree! It can be used as a complement,
> but never your only one.
It's great for distribution, but not storage.
As the T-shirt says:
There is no Cloud.
It's just someone else's computer.
--
/~\ Charlie Gibbs | Growth for the sake of
\ / <cgibbs@kltpzyxm.invalid> | growth is the ideology
X I'm really at ac.dekanfrus | of the cancer cell.
/ \ if you read it the right way. | -- Edward Abbey
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-25 23:41 +0100 |
| Message-ID | <8c905774-e57f-bc5e-540d-d4590ea4d61c@example.net> |
| In reply to | #64800 |
On Sat, 25 Jan 2025, Charlie Gibbs wrote: > On 2025-01-25, D <nospam@example.net> wrote: > >> On Sat, 25 Jan 2025, 186282@ud0s4.net wrote: >> >>> IMHO, 'cloud' is just too vulnerable to too many >>> hostile interests. Should NEVER be your main >>> backup, or working, repository. Can all go bye-bye >>> tomorrow. A local NAS is far safer. >> >> You are a wise man! I agree! It can be used as a complement, >> but never your only one. > > It's great for distribution, but not storage. > > As the T-shirt says: > > There is no Cloud. > It's just someone else's computer. This is the truth! I had my class of students repeat that sentence 5 times two weeks ago! =D
[toc] | [prev] | [next] | [standalone]
| From | "186282@ud0s4.net" <186283@ud0s4.net> |
|---|---|
| Date | 2025-01-25 21:53 -0500 |
| Message-ID | <SR6cnaMa_-U9Pgj6nZ2dnZfqn_idnZ2d@earthlink.com> |
| In reply to | #64808 |
On 1/25/25 5:41 PM, D wrote: > > > On Sat, 25 Jan 2025, Charlie Gibbs wrote: > >> On 2025-01-25, D <nospam@example.net> wrote: >> >>> On Sat, 25 Jan 2025, 186282@ud0s4.net wrote: >>> >>>> IMHO, 'cloud' is just too vulnerable to too many >>>> hostile interests. Should NEVER be your main >>>> backup, or working, repository. Can all go bye-bye >>>> tomorrow. A local NAS is far safer. >>> >>> You are a wise man! I agree! It can be used as a complement, >>> but never your only one. >> >> It's great for distribution, but not storage. >> >> As the T-shirt says: >> >> There is no Cloud. >> It's just someone else's computer. > > This is the truth! > > I had my class of students repeat that sentence 5 times two weeks ago! =D Very good ! :-) Of course STRICTLY it's a bunch of redundant connected distributed other people's computers - which SEEMS more safe. Of course if Vlad's boyz have an in ... and they do ....... Did they tell you those multiple M$ cloud blackouts late last year were due to "updates" or something ? I highly HIGHLY doubt that ... more like Vlad's boyz just practicing. Xi's boyz were practicing on the US phone systems just this month. Trump has the "Diet Coke" button on his desk. Vlad and Xi probably have the big red "Internet Doom" button on theirs. We created this situation and eventually it's gonna BITE. I figure only 30 days of no/crap net/cell and all western economies would implode. The olde-tyme backups no longer exist and the people who would know how to use them - better raid the rest homes and bring a crate of whatever drugs they used to pep-up Biden for speeches ......
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-26 13:38 +0100 |
| Message-ID | <249921a7-6bfd-cef2-7e79-bcf843f17433@example.net> |
| In reply to | #64819 |
[Multipart message — attachments visible in raw view] — view raw
On Sat, 25 Jan 2025, 186282@ud0s4.net wrote: > On 1/25/25 5:41 PM, D wrote: >> >> >> On Sat, 25 Jan 2025, Charlie Gibbs wrote: >> >>> On 2025-01-25, D <nospam@example.net> wrote: >>> >>>> On Sat, 25 Jan 2025, 186282@ud0s4.net wrote: >>>> >>>>> IMHO, 'cloud' is just too vulnerable to too many >>>>> hostile interests. Should NEVER be your main >>>>> backup, or working, repository. Can all go bye-bye >>>>> tomorrow. A local NAS is far safer. >>>> >>>> You are a wise man! I agree! It can be used as a complement, >>>> but never your only one. >>> >>> It's great for distribution, but not storage. >>> >>> As the T-shirt says: >>> >>> There is no Cloud. >>> It's just someone else's computer. >> >> This is the truth! >> >> I had my class of students repeat that sentence 5 times two weeks ago! =D > > > Very good ! :-) Someone needs to take responsibility for the next generation! ;) > Of course STRICTLY it's a bunch of redundant connected > distributed other people's computers - which SEEMS more > safe. Of course if Vlad's boyz have an in ... and > they do ....... > > Did they tell you those multiple M$ cloud blackouts > late last year were due to "updates" or something ? > I highly HIGHLY doubt that ... more like Vlad's boyz > just practicing. Xi's boyz were practicing on the > US phone systems just this month. Wouldn't surprise me at all. > Trump has the "Diet Coke" button on his desk. Vlad > and Xi probably have the big red "Internet Doom" > button on theirs. We created this situation and > eventually it's gonna BITE. Don't forget the sleeper agents in the form of contributors to popular open source projects. Last year, someone almost successfully managed to sneak some naughty code into a compression library. I'm sure this is just the tip of the iceberg. > I figure only 30 days of no/crap net/cell and all > western economies would implode. The olde-tyme > backups no longer exist and the people who would > know how to use them - better raid the rest homes > and bring a crate of whatever drugs they used > to pep-up Biden for speeches ...... Let us study deeply together! Has there been, in recent history, any examples of 30 days of power outage in the US? If so, how long until everything descendet into chaos and anarchy?
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2025-01-26 00:12 +0000 |
| Message-ID | <lvlcuhFr3c2U3@mid.individual.net> |
| In reply to | #64800 |
On Sat, 25 Jan 2025 20:01:55 GMT, Charlie Gibbs wrote: > As the T-shirt says: > > There is no Cloud. > It's just someone else's computer. I am amused by the concept of a 'private cloud'. Oh, you mean we should run our own servers like we've been doing for the last 40 years and hang a sign on the server room door that says 'cloud'?
[toc] | [prev] | [next] | [standalone]
| From | "186282@ud0s4.net" <186283@ud0s4.net> |
|---|---|
| Date | 2025-01-25 22:22 -0500 |
| Message-ID | <HhidnW4oldzgNwj6nZ2dnZfqnPYAAAAA@earthlink.com> |
| In reply to | #64812 |
On 1/25/25 7:12 PM, rbowman wrote: > On Sat, 25 Jan 2025 20:01:55 GMT, Charlie Gibbs wrote: > >> As the T-shirt says: >> >> There is no Cloud. >> It's just someone else's computer. > > I am amused by the concept of a 'private cloud'. Oh, you mean we should > run our own servers like we've been doing for the last 40 years and hang a > sign on the server room door that says 'cloud'? Hey - you can then charge 5 times as much ! :-)
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-26 13:42 +0100 |
| Message-ID | <91499d92-5817-85e5-0934-6a3fd464a9ea@example.net> |
| In reply to | #64822 |
On Sat, 25 Jan 2025, 186282@ud0s4.net wrote: > On 1/25/25 7:12 PM, rbowman wrote: >> On Sat, 25 Jan 2025 20:01:55 GMT, Charlie Gibbs wrote: >> >>> As the T-shirt says: >>> >>> There is no Cloud. >>> It's just someone else's computer. >> >> I am amused by the concept of a 'private cloud'. Oh, you mean we should >> run our own servers like we've been doing for the last 40 years and hang a >> sign on the server room door that says 'cloud'? > > Hey - you can then charge 5 times as much ! :-) > This is the truth! It is very interesting to see successful startups moving back from the cloud due to the enormous cost advantages of running it themselves. Once you hit a certain size of the company, self-hosting will almost always be cheaper, with the added benefit of control over your own IT.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-01-26 09:40 +0000 |
| Message-ID | <vn4vv6$3k0li$8@dont-email.me> |
| In reply to | #64812 |
On 26/01/2025 00:12, rbowman wrote: > On Sat, 25 Jan 2025 20:01:55 GMT, Charlie Gibbs wrote: > >> As the T-shirt says: >> >> There is no Cloud. >> It's just someone else's computer. > > I am amused by the concept of a 'private cloud'. Oh, you mean we should > run our own servers like we've been doing for the last 40 years and hang a > sign on the server room door that says 'cloud'? That's the one Bob! -- “Those who can make you believe absurdities, can make you commit atrocities.” ― Voltaire, Questions sur les Miracles à M. Claparede, Professeur de Théologie à Genève, par un Proposant: Ou Extrait de Diverses Lettres de M. de Voltaire
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-01-22 07:48 +0000 |
| Message-ID | <vmq7sv$rr50$3@dont-email.me> |
| In reply to | #64647 |
On 21/01/2025 19:56, Rich wrote: > For SSD's, writes occur to an "erased" flash block (typically much > larger than a "disk sector" size used by the host) and given enough > writes over a short enough timeframe the SSD controller can run out of > "pre-erased" blocks to use, and when that happens write speed slows > down to the rate that can be done when a "block erase" has to occur > before the actual writes can hit the media. Note that this "block > erase" can also invove moving any partially used data sectors out of > the block into another block, creating a "write amplification" > situation as well. One of the best ways to gain speed and longevity is to buy an SSD that is way larger than you need. So it always has empty blocks available. And can do the block erases in background -- Climate Change: Socialism wearing a lab coat.
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-22 10:34 +0100 |
| Message-ID | <7b204573-ffba-79cc-e153-1dde4a00f2ad@example.net> |
| In reply to | #64653 |
On Wed, 22 Jan 2025, The Natural Philosopher wrote: > On 21/01/2025 19:56, Rich wrote: >> For SSD's, writes occur to an "erased" flash block (typically much >> larger than a "disk sector" size used by the host) and given enough >> writes over a short enough timeframe the SSD controller can run out of >> "pre-erased" blocks to use, and when that happens write speed slows >> down to the rate that can be done when a "block erase" has to occur >> before the actual writes can hit the media. Note that this "block >> erase" can also invove moving any partially used data sectors out of >> the block into another block, creating a "write amplification" >> situation as well. > > One of the best ways to gain speed and longevity is to buy an SSD that is way > larger than you need. So it always has empty blocks available. > > And can do the block erases in background Indutrial ssds do have spare space exactly in order to prolong lifetime. I think when ssds first came out, there was one vendor, STEC, if memory serves, that manufactured vastly over engineered drives in the beginning. They seemed to last forever. Then they learned of course, and started to reduce quality and lifetime to industry standards and of course the price as well.
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2025-01-22 20:11 +0000 |
| Message-ID | <vmrjcp$16674$2@dont-email.me> |
| In reply to | #64657 |
D <nospam@example.net> wrote: > > > On Wed, 22 Jan 2025, The Natural Philosopher wrote: > >> On 21/01/2025 19:56, Rich wrote: >>> For SSD's, writes occur to an "erased" flash block (typically much >>> larger than a "disk sector" size used by the host) and given enough >>> writes over a short enough timeframe the SSD controller can run out of >>> "pre-erased" blocks to use, and when that happens write speed slows >>> down to the rate that can be done when a "block erase" has to occur >>> before the actual writes can hit the media. Note that this "block >>> erase" can also invove moving any partially used data sectors out of >>> the block into another block, creating a "write amplification" >>> situation as well. >> >> One of the best ways to gain speed and longevity is to buy an SSD that is way >> larger than you need. So it always has empty blocks available. >> >> And can do the block erases in background > > Indutrial ssds do have spare space exactly in order to prolong lifetime. Even consumer SSD's have "spare space", for the same reason. They just, typically, don't have as much spare space as the "server class" drives do from the start. > I think when ssds first came out, there was one vendor, STEC, if > memory serves, that manufactured vastly over engineered drives in the > beginning. They seemed to last forever. Then they learned of > course, and started to reduce quality and lifetime to industry > standards and of course the price as well. Yes, the race to the bottom on price.
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-22 22:31 +0100 |
| Message-ID | <774d956a-d5e6-f7a5-00ae-8cfa4ffbb366@example.net> |
| In reply to | #64662 |
On Wed, 22 Jan 2025, Rich wrote: > D <nospam@example.net> wrote: >> >> >> On Wed, 22 Jan 2025, The Natural Philosopher wrote: >> >>> On 21/01/2025 19:56, Rich wrote: >>>> For SSD's, writes occur to an "erased" flash block (typically much >>>> larger than a "disk sector" size used by the host) and given enough >>>> writes over a short enough timeframe the SSD controller can run out of >>>> "pre-erased" blocks to use, and when that happens write speed slows >>>> down to the rate that can be done when a "block erase" has to occur >>>> before the actual writes can hit the media. Note that this "block >>>> erase" can also invove moving any partially used data sectors out of >>>> the block into another block, creating a "write amplification" >>>> situation as well. >>> >>> One of the best ways to gain speed and longevity is to buy an SSD that is way >>> larger than you need. So it always has empty blocks available. >>> >>> And can do the block erases in background >> >> Indutrial ssds do have spare space exactly in order to prolong lifetime. > > Even consumer SSD's have "spare space", for the same reason. They > just, typically, don't have as much spare space as the "server class" > drives do from the start. Interesting! Didn't know they did this in the consumer space. >> I think when ssds first came out, there was one vendor, STEC, if >> memory serves, that manufactured vastly over engineered drives in the >> beginning. They seemed to last forever. Then they learned of >> course, and started to reduce quality and lifetime to industry >> standards and of course the price as well. > > Yes, the race to the bottom on price. I read somewhere that the expected point of convergence between spinning and ssd in terms of dollar/GB is around 2030.
[toc] | [prev] | [next] | [standalone]
| From | Rich <rich@example.invalid> |
|---|---|
| Date | 2025-01-22 22:55 +0000 |
| Message-ID | <vmrt0u$18era$1@dont-email.me> |
| In reply to | #64666 |
D <nospam@example.net> wrote: > > > On Wed, 22 Jan 2025, Rich wrote: > >> D <nospam@example.net> wrote: >>> >>> >>> On Wed, 22 Jan 2025, The Natural Philosopher wrote: >>> >>>> On 21/01/2025 19:56, Rich wrote: >>>>> For SSD's, writes occur to an "erased" flash block (typically >>>>> much larger than a "disk sector" size used by the host) and given >>>>> enough writes over a short enough timeframe the SSD controller >>>>> can run out of "pre-erased" blocks to use, and when that happens >>>>> write speed slows down to the rate that can be done when a "block >>>>> erase" has to occur before the actual writes can hit the media. >>>>> Note that this "block erase" can also invove moving any partially >>>>> used data sectors out of the block into another block, creating a >>>>> "write amplification" situation as well. >>>> >>>> One of the best ways to gain speed and longevity is to buy an SSD >>>> that is way larger than you need. So it always has empty blocks >>>> available. >>>> >>>> And can do the block erases in background >>> >>> Indutrial ssds do have spare space exactly in order to prolong lifetime. >> >> Even consumer SSD's have "spare space", for the same reason. They >> just, typically, don't have as much spare space as the "server class" >> drives do from the start. > > Interesting! Didn't know they did this in the consumer space. Well, you do have to buy decent brands. If one buys the Shenshen knockoffs, one is likely to get an SSD that says it stores 1TB, only to find the flash chips inside store 64MB. All the extra writes just get "thrown away" for you. Effectively a Write Only Memory. >>> I think when ssds first came out, there was one vendor, STEC, if >>> memory serves, that manufactured vastly over engineered drives in >>> the beginning. They seemed to last forever. Then they learned of >>> course, and started to reduce quality and lifetime to industry >>> standards and of course the price as well. >> >> Yes, the race to the bottom on price. > > I read somewhere that the expected point of convergence between > spinning and ssd in terms of dollar/GB is around 2030. That will be interesting to see. Not there yet, but certianly can happen.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-01-23 00:05 +0000 |
| Message-ID | <vms14q$1965j$5@dont-email.me> |
| In reply to | #64668 |
On 22/01/2025 22:55, Rich wrote: >> I read somewhere that the expected point of convergence between >> spinning and ssd in terms of dollar/GB is around 2030. > That will be interesting to see. Not there yet, but certianly can > happen. Its not so far off anyway. Especially in the smaller sizes., There is a certain amount of mechanical complexity in a spinning rust affair that needs to be built before any storage is added. NVMe is also caseless and has a very low cost connector. 1TB in te UK is in the £40-£60 bracket 1TB spinning rust is in the £20-60 bracket. More buys you speed, but not as fast as NVMe. If you want the speed, NVMe SSD is already cheaper -- The lifetime of any political organisation is about three years before its been subverted by the people it tried to warn you about. Anon.
[toc] | [prev] | [next] | [standalone]
| From | "186282@ud0s4.net" <186283@ud0s4.net> |
|---|---|
| Date | 2025-01-22 21:34 -0500 |
| Message-ID | <BIKdnVHinsw3Nwz6nZ2dnZfqn_qdnZ2d@earthlink.com> |
| In reply to | #64657 |
On 1/22/25 4:34 AM, D wrote: > > > On Wed, 22 Jan 2025, The Natural Philosopher wrote: > >> On 21/01/2025 19:56, Rich wrote: >>> For SSD's, writes occur to an "erased" flash block (typically much >>> larger than a "disk sector" size used by the host) and given enough >>> writes over a short enough timeframe the SSD controller can run out of >>> "pre-erased" blocks to use, and when that happens write speed slows >>> down to the rate that can be done when a "block erase" has to occur >>> before the actual writes can hit the media. Note that this "block >>> erase" can also invove moving any partially used data sectors out of >>> the block into another block, creating a "write amplification" >>> situation as well. >> >> One of the best ways to gain speed and longevity is to buy an SSD that >> is way larger than you need. So it always has empty blocks available. >> >> And can do the block erases in background > > Indutrial ssds do have spare space exactly in order to prolong lifetime. > I think when ssds first came out, there was one vendor, STEC, if memory > serves, that manufactured vastly over engineered drives in the > beginning. They seemed to last forever. Then they learned of course, and > started to reduce quality and lifetime to industry standards and of > course the price as well. Even today, a 'large' SSD is maybe 4tb while a large HDD is 16tb. Tb-for-Tb the SSD is gonna be a lot more expensive too. SO ... where do you NEED speed and where do you NEED economy/volume ?
[toc] | [prev] | [next] | [standalone]
| From | D <nospam@example.net> |
|---|---|
| Date | 2025-01-23 16:53 +0100 |
| Message-ID | <e93adace-683d-2487-71f8-c667c7ab95fe@example.net> |
| In reply to | #64683 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, 22 Jan 2025, 186282@ud0s4.net wrote: > On 1/22/25 4:34 AM, D wrote: >> >> >> On Wed, 22 Jan 2025, The Natural Philosopher wrote: >> >>> On 21/01/2025 19:56, Rich wrote: >>>> For SSD's, writes occur to an "erased" flash block (typically much >>>> larger than a "disk sector" size used by the host) and given enough >>>> writes over a short enough timeframe the SSD controller can run out of >>>> "pre-erased" blocks to use, and when that happens write speed slows >>>> down to the rate that can be done when a "block erase" has to occur >>>> before the actual writes can hit the media. Note that this "block >>>> erase" can also invove moving any partially used data sectors out of >>>> the block into another block, creating a "write amplification" >>>> situation as well. >>> >>> One of the best ways to gain speed and longevity is to buy an SSD that is >>> way larger than you need. So it always has empty blocks available. >>> >>> And can do the block erases in background >> >> Indutrial ssds do have spare space exactly in order to prolong lifetime. I >> think when ssds first came out, there was one vendor, STEC, if memory >> serves, that manufactured vastly over engineered drives in the beginning. >> They seemed to last forever. Then they learned of course, and started to >> reduce quality and lifetime to industry standards and of course the price >> as well. > > > Even today, a 'large' SSD is maybe 4tb while a large HDD is 16tb. > Tb-for-Tb the SSD is gonna be a lot more expensive too. This is the truth! > SO ... where do you NEED speed and where do you NEED economy/volume ? For my use case I need maximum economy/volume, so SSDs are out.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2025-01-23 16:34 +0000 |
| Message-ID | <vmtr3b$1ll9u$22@dont-email.me> |
| In reply to | #64699 |
On 23/01/2025 15:53, D wrote: > >> SO ... where do you NEED speed and where do you NEED economy/volume ? > > For my use case I need maximum economy/volume, so SSDs are out. Fair enough, but at least you are making in informed choice -- For in reason, all government without the consent of the governed is the very definition of slavery. Jonathan Swift
[toc] | [prev] | [next] | [standalone]
Page 18 of 20 — ← Prev page 1 … 16 17 [18] 19 20 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web