Hi all,
I have Raspberries in different locations. One of them, more than 100
miles away didn't come back from a reboot. Hence, I suspect the SDCard to
be corrupted. This one worked one and a half year without any trouble,
but now its time seems over.
I have to install a new one. Well. But:
Since I have only little time when visiting, I'd like to prepare a fresh install and put the card into the RPi when I am there.
Reason for asking is, that I have different machine type, and not two are
the same.
The card I have to install now is for machine type "Raspberry A" (SDCard / Micro-SD with adapter), and the machines on which I could do the setup
here are "Raspberry 3 / quad core proc." or "Raspberry Zero / WLAN".
Can this work at all -- according to you experience -- to install on one machine type and use in a completely different one?
Thanks for info!
Best regards,
Markus
100I have Raspberries in different locations. One of them, more than
SDCardmiles away didn't come back from a reboot. Hence, I suspect the
to be corrupted.
Why not hedge your bets (it could be an RPi complete failure) and get a
new one to set up from scratch.
On Thu, 22 Oct 2020 14:13:25 +0100 Dave Liquorice wrote:
On Thu, 22 Oct 2020 13:33:56 +0100, Chris Elvidge wrote:
100I have Raspberries in different locations. One of them, more than
SDCardmiles away didn't come back from a reboot. Hence, I suspect the
to be corrupted.
Why not hedge your bets (it could be an RPi complete failure) and get
a new one to set up from scratch.
That would be wise. A Zero is not exactly expensive... Also "didn't
come back from a reboot" is a bit vague. Is that just waiting after
issuing a reboot command or after a shut down and power cycle? Has it
been power cycled? Has the SD card been reseated and the power cycled?
Is there a micro SD to SD card adpater in use?
Hi, what I've done in short:
I start a python script via crontab every 10 minutes which reads I2C
data from a BME280 sensor. This script calculates the temperature,
relative humidity and relative air pressure and sends it to a webserver.
This works perfectly.
To be on the safe side I make / made a reboot every night. From this the questioned machine didn't return, now. I see in the log that the last transmission was ok, then the reboot was started and the connection was
lost. So, I doubt that the machine completely broke down. Most likely
the SDCard gave up.
So, I also have to re-think if it is a good idea to make daily reboots
even though the resources are not locked or eaten up. Maybe one reboot
per week will also do?
P.S. I'd rather prefer to use "Raspberry Zero / WLAN" only for
installation, since it has only Wifi and the network there is cable
based.
Best regards,
Markus
On Thu, 22 Oct 2020 13:33:56 +0100, Chris Elvidge wrote:
100I have Raspberries in different locations. One of them, more than
SDCardmiles away didn't come back from a reboot. Hence, I suspect the
to be corrupted.
Why not hedge your bets (it could be an RPi complete failure) and get a
new one to set up from scratch.
That would be wise. A Zero is not exactly expensive... Also "didn't come
back from a reboot" is a bit vague. Is that just waiting after issuing a reboot command or after a shut down and power cycle? Has it been power cycled? Has the SD card been reseated and the power cycled? Is there a
micro SD to SD card adpater in use?
1st rule of Linux :-
Reboots are for hardware changes only
1st rule of Linux :-Or a kernel upgrade
Reboots are for hardware changes only
I start a python script via crontab every 10 minutes which reads I2C
data from a BME280 sensor. This script calculates the temperature,
relative humidity and relative air pressure and sends it to a webserver.
To be on the safe side I make / made a reboot every night. From this the questioned machine didn't return, now. I see in the log that the last transmission was ok, then the reboot was started and the connection was
lost. So, I doubt that the machine completely broke down. Most likely
the SDCard gave up.
P.S. I'd rather prefer to use "Raspberry Zero / WLAN" only for
installation, since it has only Wifi and the network there is cable
based.
To be on the safe side I make / made a reboot every night. From this the
On Thu, 22 Oct 2020 17:35:12 -0000 (UTC), Markus Robert Kessler wrote:
I start a python script via crontab every 10 minutes which reads I2C
data from a BME280 sensor. This script calculates the temperature,
relative humidity and relative air pressure and sends it to a
webserver.
Can't help think why you start the script every 10 mins instead of
having in a loop with a 10 minute sleep. If you want *exactly* 10
minutes between each sample one would have to code around the (variable)
time taken for the data sampling, processing and up load but that's not difficult.
To be on the safe side I make / made a reboot every night. From this
the questioned machine didn't return, now. I see in the log that the
last transmission was ok, then the reboot was started and the
connection was lost. So, I doubt that the machine completely broke
down. Most likely the SDCard gave up.
So it hasn't been power cycled and/or the SD card reseated? It could
just be a build up of corrosion in the slot connections. Almost all
Rapsberry boot problems I've had have been down to the latter or a bad
micro SD to SD adapater.
Not sure why you think you need to reboot if it's only running a simple script. A Pi Zero here:
pi@PiZ-StoveB:~ $ w
19:37:30 up 49 days, 10:24,
That Pi has extra hardware attached: An ENC28J60 ethernet port, ex nokia
LCD phone display (both on SPI buses), a rotary encoder and a PWM driven solid state relay (4 GPIO's). It's talking on two 1-Wire buses (2 more GPIO's) with eight or so devices across the two buses. Every minute it
reads all the 1-Wire devices, updates the display, logs the data (over ethernet and locally), decides if the PWM drive to the SSR is correct
for the data it gathered and adjusts as required. The display has an
animated "heartbeat" symbol that shows the system is alive when the PWM
is off. If the PWM is on it rotates the symbol at the appropiate speed.
This is all under a multi threaded python script. Oh almost forgot a
bi-color LED that flashes green as the 1-Wire buses are read or pulses
red at rate determined by the PWM.
It's also running a web server (nginx) that can produce plots of the
logged data on demand.
It's also running pi-hole.
As you can see it's doing all that and been up nearly 50 days... I've
never known it crash in use.
P.S. I'd rather prefer to use "Raspberry Zero / WLAN" only for
installation, since it has only Wifi and the network there is cable
based.
Don't follow that either. B-) How does the WLAN help with getting an ethernet connection?
On Thu, 22 Oct 2020 17:35:12 -0000 (UTC), Markus Robert Kessler
wrote:
I start a python script via crontab every 10 minutes which reads I2C
data from a BME280 sensor. This script calculates the temperature,
relative humidity and relative air pressure and sends it to a webserver.
Can't help think why you start the script every 10 mins instead of
having in a loop with a 10 minute sleep. If you want *exactly* 10
Re: Re: SDCard -- install here and deploy there?
By: Markus Robert Kessler to All on Thu Oct 22 2020 05:35 pm
To be on the safe side I make / made a reboot every night. From this
the
I know I am not helping, but rebooting "just because" is bad practice.
If anything, reboot the service you need to reboot. And it is still bad.
Much better to have a watchdog or something email you if there is any
issue.
On Thu, 22 Oct 2020 20:11:45 +0100 Dave Liquorice wrote:
On Thu, 22 Oct 2020 17:35:12 -0000 (UTC), Markus Robert Kessler wrote:
I start a python script via crontab every 10 minutes which reads I2C
data from a BME280 sensor. This script calculates the temperature,
relative humidity and relative air pressure and sends it to a
webserver.
Can't help think why you start the script every 10 mins instead of
having in a loop with a 10 minute sleep. If you want *exactly* 10
minutes between each sample one would have to code around the
(variable)
time taken for the data sampling, processing and up load but that's not
difficult.
To be on the safe side I make / made a reboot every night. From this
the questioned machine didn't return, now. I see in the log that the
last transmission was ok, then the reboot was started and the
connection was lost. So, I doubt that the machine completely broke
down. Most likely the SDCard gave up.
So it hasn't been power cycled and/or the SD card reseated? It could
just be a build up of corrosion in the slot connections. Almost all
Rapsberry boot problems I've had have been down to the latter or a bad
micro SD to SD adapater.
Not sure why you think you need to reboot if it's only running a simple
script. A Pi Zero here:
pi@PiZ-StoveB:~ $ w
19:37:30 up 49 days, 10:24,
That Pi has extra hardware attached: An ENC28J60 ethernet port, ex
nokia LCD phone display (both on SPI buses), a rotary encoder and a PWM
driven solid state relay (4 GPIO's). It's talking on two 1-Wire buses
(2 more GPIO's) with eight or so devices across the two buses. Every
minute it reads all the 1-Wire devices, updates the display, logs the
data (over ethernet and locally), decides if the PWM drive to the SSR
is correct for the data it gathered and adjusts as required. The
display has an animated "heartbeat" symbol that shows the system is
alive when the PWM is off. If the PWM is on it rotates the symbol at
the appropiate speed. This is all under a multi threaded python script.
Oh almost forgot a bi-color LED that flashes green as the 1-Wire buses
are read or pulses red at rate determined by the PWM.
It's also running a web server (nginx) that can produce plots of the
logged data on demand.
It's also running pi-hole.
As you can see it's doing all that and been up nearly 50 days... I've
never known it crash in use.
P.S. I'd rather prefer to use "Raspberry Zero / WLAN" only for
installation, since it has only Wifi and the network there is cable
based.
Don't follow that either. B-) How does the WLAN help with getting an
ethernet connection?
WLAN doesn't help at all since at that site Wifi is deactivated. So, replacing an RPI-A with a RPI-Zero means one has to attach an eth-to-usb module. Better use it just for installing a new SDCard and then put this
card into the RPI-A.
Well, some months ago I wrote here about lost SDCards during reboot on RPI-Zero. Every 10 or 20 reboots the card was no longer found during
reboot and had to be put into a desktop Linux PC. Then the partitions on
the card were found instantly and the card worked again even in a RPI-
Zero. Whoever I asked -- no clue why.
So I decided to use RPI-Zero only for testing purposes and for logging
data I use RPI-A, RPI-B and RPI-3.
So, still interested in getting infos about if or not it is possible to install a new SDCard in a different RPI and then just put it into the mentioned RPI-A and it works?
Thanks again,
best regards,
Markus
Sorry, forget to mention:
Yes, I try to install Raspbian OS.
Reason for asking all this, is, that once I saw a warning saying that >installing newer Raspberry machines like "Rpi-Zero" will only be possible
by using the most recent Raspbian versions. Older ones cannot do.
So, it seems that there are indeed some differences regarding accessing
the hardware architecture, but hopefully newer OS-es -- once installed --
can serve older hardware like "RPI-A" as well.
On Thu, 22 Oct 2020 20:11:45 +0100 (BST), "Dave Liquorice" <allsortsnotthisbit@howhill.com> declaimed the following:
On Thu, 22 Oct 2020 17:35:12 -0000 (UTC), Markus Robert Kessler
wrote:
I start a python script via crontab every 10 minutes which reads I2C
data from a BME280 sensor. This script calculates the temperature,
relative humidity and relative air pressure and sends it to a webserver.
Can't help think why you start the script every 10 mins instead of
having in a loop with a 10 minute sleep. If you want *exactly* 10
That aspect is quite logical... Using a crontab entry means if the script failed at some point for some reason, a fresh process will be
started 10 minutes later (give or take OS overhead).
While an internal loop might support more precise 10-minute intervals, if the script dies then nothing will be left running.
For a remote sensor node that relays readings to another server, I do think I'd want as many temporary files as possible to be running in RAM
disk, and not off the SD card.
On Thu, 22 Oct 2020 14:48:10 +1300 Richard Falken wrote:
Re: Re: SDCard -- install here and deploy there?
By: Markus Robert Kessler to All on Thu Oct 22 2020 05:35 pm
> To be on the safe side I make / made a reboot every night. From this
> the
I know I am not helping, but rebooting "just because" is bad practice.
If anything, reboot the service you need to reboot. And it is still bad.
Much better to have a watchdog or something email you if there is any
issue.
on my RPI-3 I used to have a watchdog service. But by some reason the
system hung instead of doing a hardware-reboot. Maybe there was a kernel module mismatch. So, I switched it off.
Besides this, a watchdog may put your SDCard in a state where an fsck is demanded for. So, the system does not start non-interactively next time.
1st rule of Linux :-
Reboots are for hardware changes only
Re: Re: SDCard -- install here and deploy there?
By: Markus Robert Kessler to All on Thu Oct 22 2020 05:35 pm
To be on the safe side I make / made a reboot every night. From this the
I know I am not helping, but rebooting "just because" is bad practice.
1st rule of Linux :-Or a kernel upgrade
Reboots are for hardware changes only
Reason for asking all this, is, that once I saw a warning saying that installing newer Raspberry machines like "Rpi-Zero" will only be possible
by using the most recent Raspbian versions. Older ones cannot do.
So, it seems that there are indeed some differences regarding accessing
the hardware architecture, but hopefully newer OS-es -- once installed --
can serve older hardware like "RPI-A" as well.
On 22/10/2020 23:15, Markus Robert Kessler wrote:
Reason for asking all this, is, that once I saw a warning saying that
installing newer Raspberry machines like "Rpi-Zero" will only be possible
by using the most recent Raspbian versions. Older ones cannot do.
So, it seems that there are indeed some differences regarding accessing
the hardware architecture, but hopefully newer OS-es -- once installed --
can serve older hardware like "RPI-A" as well.
You should always do a fresh install with the latest version in any case.
However, you may want to move an existing set up to a newer Pi, and this
can be done even if that older install wouldn't work on the new Pi. What
you need to do while running on the old Pi is to do a:-
sudo rpi-update
This will install all the newer components in /boot to allow use of any
Pi. There is one gotcha though, you need to ensure your boot partition is
big enough for al the new files. Older installs may have only had a 64MB
boot partition, but 256MB is recommended now.
You can use gparted to enlarge the boot partition, but that requires
moving the root partition upwards, which may take a long time for a large card. It may then be quicker to reformat and reinstall.
However, you may want to move an existing set up to a newer Pi, and this
can be done even if that older install wouldn't work on the new Pi. What
you need to do while running on the old Pi is to do a:-
sudo rpi-update
On 2020-10-22, Richard Falken <nospam.Richard.Falken@f1.n770.z5613.fidonet.org> wrote:
Re: Re: SDCard -- install here and deploy there?
By: Markus Robert Kessler to All on Thu Oct 22 2020 05:35 pm
To be on the safe side I make / made a reboot every night. From this
the
I know I am not helping, but rebooting "just because" is bad practice.
Go easy on him, he probably started out as a Microsoft vict^H^H^H^Huser.
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon.
That was one of the reasons for
inventing repeated reboots. On more sophisticated RPIs with 1 GB this is
not necessary of course.
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad programming! That has never been acceptable in my book since times when
256Mb was a dream as disc capacity.
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under
load this amount will be eaten up soon. That was one of the reasons
for inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad
programming! That has never been acceptable in my book since times when
256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more efficient to reboot a server or invest time debugging leaky code. Time
is money.
Can I be arsed to start again from scratch, installing onto the 32 GB
card (but not via NOOBS!) and then doing all the configuration again? TVHeadend is a real pig to configure, because it "sees" all the regional versions of ITV1 as having the same name, whereas I want to call them
"ITV1 London", "ITV1 Yorkshire (West)" etc so I can watch/record
whichever local news happens to have greater coverage than the national
news for a local story. It's a case of going through looking at PIDs and matching them against a list such as https://www.lyngsat.com/Astra-2E-2F-2G.html. Tedious, but I'd got it set
up just right - and then discovered the low free space and thought how restricting it would be if I want to install anything extra.
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for
bad programming! That has never been acceptable in my book since times
when 256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more efficient to reboot a server or invest time debugging leaky code. Time
is money.
On Sat, 24 Oct 2020 12:43:03 +0100
Pancho <Pancho.Dontmaileme@outlook.com> wrote:
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load >>>> this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for
bad programming! That has never been acceptable in my book since times
when 256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more
efficient to reboot a server or invest time debugging leaky code. Time
is money.
Out here in my bit of the real world if we create a service that we can't stop leaking then we arrange to restart the *service* periodically because our customers look on unexpected reboots with great disfavour. They like their expensive servers to be serving not rebooting.
On Sat, 24 Oct 2020 12:43:03 +0100
Pancho <Pancho.Dontmaileme@outlook.com> wrote:
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load >>>> this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for
bad programming! That has never been acceptable in my book since times
when 256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more
efficient to reboot a server or invest time debugging leaky code. Time
is money.
Out here in my bit of the real world if we create a service that we can't stop leaking then we arrange to restart the *service* periodically because our customers look on unexpected reboots with great disfavour. They like their expensive servers to be serving not rebooting.
On Sat, 24 Oct 2020 12:43:03 +0100, Pancho wrote:
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under
load this amount will be eaten up soon. That was one of the reasons
for inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad
programming! That has never been acceptable in my book since times when
256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more
efficient to reboot a server or invest time debugging leaky code. Time
is money.
But seeing that the code is leaky is dead simple: just run top and look
at the display every so often.
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under
load this amount will be eaten up soon. That was one of the reasons
for inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad
programming! That has never been acceptable in my book since times when
256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more efficient to reboot a server or invest time debugging leaky code. Time
is money.
On 24/10/2020 12:50, Martin Gregorie wrote:
On Sat, 24 Oct 2020 12:43:03 +0100, Pancho wrote:Yes, it is often dead simple to see that code doesn't work, however
On 24/10/2020 12:19, Ahem A Rivet's Shot wrote:
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under
load this amount will be eaten up soon. That was one of the reasons
for inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad
programming! That has never been acceptable in my book since times
when 256Mb was a dream as disc capacity.
Yeah, back in the real world it's an optimisation problem. Is it more
efficient to reboot a server or invest time debugging leaky code. Time
is money.
But seeing that the code is leaky is dead simple: just run top and look
at the display every so often.
fixing it....
Yeah, back in the real world it's an optimisation problem. Is it more
efficient to reboot a server or invest time debugging leaky code. Time
is money.
I this type of thinking is precisely why there is so much bad code with security vulnerabilities in the wild.
If you cant afford to do it right how on earth can you afford the losses
from a data breach?
On Fri, 23 Oct 2020 17:16:40 +0000 Charlie Gibbs wrote:
On 2020-10-22, Richard Falken
<nospam.Richard.Falken@f1.n770.z5613.fidonet.org> wrote:
Re: Re: SDCard -- install here and deploy there?
By: Markus Robert Kessler to All on Thu Oct 22 2020 05:35 pm
To be on the safe side I make / made a reboot every night. From this
the
I know I am not helping, but rebooting "just because" is bad practice.
Go easy on him, he probably started out as a Microsoft vict^H^H^H^Huser.
Vict-what? -- Victim?
At work I use to boot my machines only every few months and some even
once per year. For headless servers this is sufficient. But these have typically 16 GB of RAM or even more.
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots. On more sophisticated RPIs with 1 GB this is
not necessary of course.
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad programming! That has never been acceptable in my book since times when
256Mb was a dream as disc capacity.
"Ahem A Rivet's Shot" <steveo@eircom.net> wrote in message news:20201024121940.637fbc604370d7cfa1860012@eircom.net...
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad programming! That has never been acceptable in my book since times when 256Mb was a dream as disc capacity.
256 Mb. So 64 MB? <four Yorkshiremen>That's luxury!</four Yorkshiremen>
I can remember when I bought my first computer, in 1981, a CPM/3-based
"Wren" (*). I decided that I could just about afford the RAM upgrade from
256 Mb. So 64 MB? <four Yorkshiremen>That's luxury!</four Yorkshiremen>
"Ahem A Rivet's Shot" <steveo@eircom.net> wrote:
256Mb was a dream as disc capacity.
256 Mb. So 64 MB? <four Yorkshiremen>That's luxury!</four Yorkshiremen>
I first learned to program in Algol 60 on an Elliott 503 with 8 Kwords
(39 bit words) with input on paper tape and output on a lineprinter.
256 Mb. So 64 MB? <four Yorkshiremen>That's luxury!</four Yorkshiremen>
I can remember when I bought my first computer, in 1981, a CPM/3-based
"Wren" (*). I decided that I could just about afford the RAM upgrade
from 16 KB to 256 KB, but I couldn't justify or afford the disk upgrade
from 2 floppies to 1 floppy and a 5 MB hard disk.
My first IBM-compatible PC, based on an 8086, came with a 20 MB HDD. It
ran MS-DOS fine, but it wasn't up to running Windows 1 - and I used up
most of the HDD even installing it from the multitude of diskettes that
I borrowed from work to try it out of curiosity.
(*) I remember it was the first time I'd even driven in London, in the
car that I'd bought a few weeks earlier after passing my test -
navigating along the A40, Marylebone Road/Euston Road, Gray's Inn Road
to Theobalds Road where the shop was. I even managed to find my way back
home again ;-) The Wren still worked until I last tried it a few years
ago, when I found that the PSU (a very obsolete design) had finally
packed up.
Actually true, a trip to Watford Electronics via Edgeware Rd, a shop
that specialised in bits for the Acorn BBC B.
On Sun, 25 Oct 2020 22:58:40 -0000 (UTC)
Martin Gregorie <martin@mydomain.invalid> wrote:
I first learned to program in Algol 60 on an Elliott 503 with 8 Kwords
(39 bit words) with input on paper tape and output on a lineprinter.
Lucky sod! Dartmouth BASIC[10] on a 4K word (32 bit) IBM 1130, but there was a 1442 card reader/punch attached as well as the paper tape
reader and a 1403 (not N1 so I missed out on that joy).
NY <me@privacy.invalid> wrote:
"Ahem A Rivet's Shot" <steveo@eircom.net> wrote:
256Mb was a dream as disc capacity.
256 Mb. So 64 MB? <four Yorkshiremen>That's luxury!</four Yorkshiremen>
32, you mean. Also, technically, it's MiB. https://en.wikipedia.org/wiki/Mebibyte
On Sun, 25 Oct 2020 20:23:17 -0000
"NY" <me@privacy.invalid> wrote:
"Ahem A Rivet's Shot" <steveo@eircom.net> wrote in message
news:20201024121940.637fbc604370d7cfa1860012@eircom.net...
On Sat, 24 Oct 2020 10:39:35 -0000 (UTC)
Markus Robert Kessler <no_reply@dipl-ing-kessler.de> wrote:
We are talking about a "Raspberry A" with 256 MB (MegaByte). Under
load
this amount will be eaten up soon. That was one of the reasons for
inventing repeated reboots.
Reboots to cure memory leaks ? IOW reboots as a workaround for bad
programming! That has never been acceptable in my book since times when
256Mb was a dream as disc capacity.
256 Mb. So 64 MB? <four Yorkshiremen>That's luxury!</four Yorkshiremen>
<grin>
I can remember when I bought my first computer, in 1981, a CPM/3-based
"Wren" (*). I decided that I could just about afford the RAM upgrade from
A bit later than 1981 I think - CP/M 3 didn't come out until 1983
CPN for the Torch (1982) was based on CP/M 2.2, I'd have just ported CP/M
3
if it had been available.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 66:33:21 |
| Calls: | 6,654 |
| Files: | 12,200 |
| Messages: | 5,331,881 |