• Are Pi Zeros more fussy about SD cards than other Pis?

    From Chris Green@cl@isbd.net to comp.sys.raspberry-pi on Mon Aug 3 15:45:10 2026
    From Newsgroup: comp.sys.raspberry-pi

    I have a Pi Zero 2 W logging data once an hour, it's a 1Mb database
    that gets updated each hour. It has killed its SD card twice in less
    than a year and I'm wondering why.

    I have a similar logging system using a venerable Pi 2 that's been
    running for much longer and writing somewhat more data without any
    problems.

    The Pi Zero 2 W replaced a Beaglebone Black that had run for several
    years without any problems.

    Is the Pi Zero 2 W more fussy about its SD card, does it work the card
    harder. or have I just been unlucky?

    I'd welcome any recommendations for cards that last well.
    --
    Chris Green
    -+
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John R Walliker@jrwalliker@gmail.com to comp.sys.raspberry-pi on Mon Aug 3 18:05:37 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 03/08/2026 15:45, Chris Green wrote:
    I have a Pi Zero 2 W logging data once an hour, it's a 1Mb database
    that gets updated each hour. It has killed its SD card twice in less
    than a year and I'm wondering why.

    I have a similar logging system using a venerable Pi 2 that's been
    running for much longer and writing somewhat more data without any
    problems.

    The Pi Zero 2 W replaced a Beaglebone Black that had run for several
    years without any problems.

    Is the Pi Zero 2 W more fussy about its SD card, does it work the card harder. or have I just been unlucky?

    I'd welcome any recommendations for cards that last well.

    Samsung and Sandisk sell high endurance SD cards intended for
    security camera and dashcam applications. These are not
    particularly fast, but are designed to survive continuous
    writing of data.
    John

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Theo@theom+news@chiark.greenend.org.uk to comp.sys.raspberry-pi on Mon Aug 3 18:23:55 2026
    From Newsgroup: comp.sys.raspberry-pi

    John R Walliker <jrwalliker@gmail.com> wrote:
    On 03/08/2026 15:45, Chris Green wrote:
    I have a Pi Zero 2 W logging data once an hour, it's a 1Mb database
    that gets updated each hour. It has killed its SD card twice in less
    than a year and I'm wondering why.

    I have a similar logging system using a venerable Pi 2 that's been
    running for much longer and writing somewhat more data without any problems.

    The Pi Zero 2 W replaced a Beaglebone Black that had run for several
    years without any problems.

    Is the Pi Zero 2 W more fussy about its SD card, does it work the card harder. or have I just been unlucky?

    I'd welcome any recommendations for cards that last well.

    Samsung and Sandisk sell high endurance SD cards intended for
    security camera and dashcam applications. These are not
    particularly fast, but are designed to survive continuous
    writing of data.

    +1. There are also 'industrial' grade cards which are a step above 'high endurance' - better designed to handle things like power glitches or
    unplanned power outages. I think they use more robust flash (MLC not TLC,
    or TLC not QLC) which makes them more expensive per GB - but if you can get
    by with 4 or 8GB then it doesn't matter.

    Theo
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Mon Aug 3 18:29:55 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 03/08/2026 15:45, Chris Green wrote:
    I have a Pi Zero 2 W logging data once an hour, it's a 1Mb database
    that gets updated each hour. It has killed its SD card twice in less
    than a year and I'm wondering why.

    I have a similar logging system using a venerable Pi 2 that's been
    running for much longer and writing somewhat more data without any
    problems.

    The Pi Zero 2 W replaced a Beaglebone Black that had run for several
    years without any problems.

    Is the Pi Zero 2 W more fussy about its SD card, does it work the card harder. or have I just been unlucky?

    I'd welcome any recommendations for cards that last well.

    in the true 'if i wanted to go there i wouldn't be starting from here' tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change configurations,. Everything that writes is either stopped from writing
    or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out
    which
    --
    The higher up the mountainside
    The greener grows the grass.
    The higher up the monkey climbs
    The more he shows his arse.

    Traditional

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From s|b@me@privacy.invalid to comp.sys.raspberry-pi on Mon Aug 3 22:48:03 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 3 Aug 2026 18:05:37 +0100, John R Walliker wrote:

    Samsung and Sandisk sell high endurance SD cards intended for
    security camera and dashcam applications. These are not
    particularly fast, but are designed to survive continuous
    writing of data.

    +1 on SanDisk and Samsung. I use the SanDisk High Endurance microsd*,
    same as in my dashcam. Funny thing Theo mentioning industrial, because I
    just checked the dashcam's manufacturer, Viofo, and they now sell (what
    they call) industrial microsd cards.

    <https://www.viofo.com/products/viofo-industrial-grade-microsd-card-u3-a2-v30-high-speed-memory-card-with-adapter-support-ultra-hd-4k-video-recording32-64-128-256>

    I haven't tried these myself, but these cards are meant to go on and on
    since the dashcam is recording in time slots of 5 mins and it loops when
    the card is full.




    * <https://www.sandisk.com/en-ie/products/memory-cards/microsd-cards/sandisk-high-endurance-uhs-i-microsd?sku=SDSQQNR-064G-GN6IA>
    --
    s|b
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From s|b@me@privacy.invalid to comp.sys.raspberry-pi on Mon Aug 3 22:48:31 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here' tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change configurations,. Everything that writes is either stopped from writing
    or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out which

    This is helpful.
    --
    s|b
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Green@cl@isbd.net to comp.sys.raspberry-pi on Tue Aug 4 10:15:29 2026
    From Newsgroup: comp.sys.raspberry-pi

    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here' tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change configurations,. Everything that writes is either stopped from writing
    or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out which

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk
    writing, if so I'd like to know about them.
    --
    Chris Green
    -+
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Tue Aug 4 11:10:07 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 04/08/2026 10:15, Chris Green wrote:
    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here'
    tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change
    configurations,. Everything that writes is either stopped from writing
    or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out >>> which

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk writing, if so I'd like to know about them.

    Here is my 'if I ever have to reproduce this' cheat file
    HEATING CONTROLLER
    ==================
    user: admin
    password: fuckU
    file /etc/dhcpcd.conf
    ---------------------
    set static IP address 192.168.0.201
    set gateway 192.168.0.254
    set name-server 192.168.0.100

    apt-get update
    apt-get upgrade -y

    # web server
    #============
    apt-get install apache2
    chown -R www-data /var/www
    chgrp -R www-data /var/www
    chmod -R 775 /var/www/
    chmod g+s /var/www
    usermod -aG www-data me
    usermod -aG www-data admin
    mkdir /var/www/data
    chmod 775 /var/www/data
    # create an area to share data between processes...
    mkdir /var/www/data/volatile
    chmod 777 /var/www/data/volatile
    # create ram disks
    echo "tmpfs /var/www/data/volatile tmpfs nodev,nosuid,noexec,nodiratime,size=1M 0 0" >> /etc/fstab
    echo "tmpfs /var/ramlog tmpfs nodev,nosuid,noexec,nodiratime,size=25M,mode=0755 0 0" >> /etc/fstab




    ## fuck with shitsemd
    sed -i "s/#Storage=auto/Storage=volatile/" /etc/systemd/journald.conf
    sed -i "s/#RuntimeMaxUse=/RuntimeMaxUse=25M/" /etc/systemd/journald.conf
    sed -i "s/#ForwardToConsole=yes/ForwardToConsole=no/" /etc/systemd/journald.conf
    sed -i "s/#ForwardToWall=yes/ForwardToWall=no/" //etc/systemd/journald.conf


    Then it is a question of making sure the SD card filesystem is mounted
    with minimal write
    more /etc/fstab

    proc /proc proc defaults 0 0 PARTUUID=b8c9fbb7-01 /boot vfat defaults 0 2 PARTUUID=b8c9fbb7-02 / ext4 defaults,noatime 0 1
    # a swapfile is not a swap partition, no line here
    # use dphys-swapfile swap[on|off] for that
    tmpfs /var/www/data/volatile tmpfs
    nodev,nosuid,noexec,nodiratime,size=1M 0 0
    tmpfs /var/ramlog tmpfs
    nodev,nosuid,noexec,nodiratime,size=25M,mode=0755 0 0

    and picking through everything that might write to the logs to make it
    send data to the ramdisk...I though that I had included that in this
    guide, but looks like I didnt,. E.g. Apache log files go to the ram disk


    ls -l /var/ramlog
    total 944
    -rw-r----- 1 root adm 119044 Aug 4 10:55 auth.log
    -rw-r----- 1 root adm 55711 Aug 1 23:59 auth.log.1
    -rw-r----- 1 root adm 118243 Aug 4 10:47 daemon.log
    -rw-r----- 1 root adm 86611 Aug 2 00:00 daemon.log.1
    -rw-r----- 1 root adm 0 Aug 2 00:00 debug
    -rw-r----- 1 root adm 3111 Jul 31 20:41 debug.1
    -rw-r----- 1 root adm 241 Aug 4 00:00 error.log
    -rw-r----- 1 root adm 528 Aug 4 00:00 error.log.1
    -rw-r----- 1 root adm 81192 Aug 3 00:00 error.log.2.gz
    -rw-r----- 1 root adm 446 Aug 2 00:00 error.log.3.gz
    -rw-r--r-- 1 root root 347 Aug 1 00:00 error.log.4.gz
    -rw-r----- 1 root adm 0 Aug 2 00:00 kern.log
    -rw-r----- 1 root adm 31371 Jul 31 20:40 kern.log.1
    -rw-r----- 1 root adm 5111 Aug 2 13:02 mail.info
    -rw-r----- 1 root adm 14189 Aug 1 23:02 mail.info.1
    -rw-r----- 1 root adm 5111 Aug 2 13:02 mail.log
    -rw-r----- 1 root adm 14189 Aug 1 23:02 mail.log.1
    -rw-r----- 1 root adm 159 Aug 2 00:10 messages
    -rw-r----- 1 root adm 30557 Jul 31 20:40 messages.1
    -rw-r----- 1 root adm 190719 Aug 4 10:55 syslog
    -rw-r----- 1 root adm 163421 Aug 2 00:00 syslog.1


    Its not 100% complete, but its very close

    I've still got data going to /var/log that I ought to symlink to files
    in /var/ramlog

    ls -l /var/log
    total 288
    -rw-r--r-- 1 root root 653 Sep 6 2023 alternatives.log
    drwxr-xr-x 2 root root 4096 Nov 18 2025 apt
    -rw-rw---- 1 root utmp 8832 Jun 10 12:00 btmp
    -rw-r--r-- 1 root root 0 Nov 19 2025 dpkg.log
    -rw-r--r-- 1 root root 2400 Nov 18 2025 dpkg.log.1
    -rw-r--r-- 1 root root 464 Oct 16 2025 dpkg.log.2.gz
    -rw-r--r-- 1 root root 778 Sep 6 2023 dpkg.log.3.gz
    -rw-r--r-- 1 root root 584 Aug 11 2023 dpkg.log.4.gz
    -rw-rw-r-- 1 root utmp 292292 Aug 4 10:47 lastlog
    drwx------ 2 root root 4096 May 3 2023 private
    drwxr-xr-x 4 root root 4096 Aug 4 2023 runit
    drwxr-xr-x 2 root root 4096 Feb 2 2021 sysstat
    -rw-rw-r-- 1 root utmp 230016 Aug 4 10:47 wtmp


    ... lastlog and wtmp. I dont mind upgrade history being there tho
    A lazy way might be to just mount the ramdisk on /var/log, but I wasn't
    sure what I wanted volatile and what needed to be written to the SD card

    To date this has been utterly reliable for nearly 3 years now. Always
    reboots after a power cut.

    In practice various (Pi PICO W) units talk to it via its wifi TCP/IP connection - thermostats, the oil sensor.. and it controls the central
    heating system via some mains relays. Information and configuration is
    via a custom web interface.

    If I wanted to store a lot of changing data I would (probably) NFS mount
    the house server and stream data to that instead of locally. Or write
    some proprietary network code.
    --
    Microsoft : the best reason to go to Linux that ever existed.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From s|b@me@privacy.invalid to comp.sys.raspberry-pi on Tue Aug 4 14:56:57 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 4 Aug 2026 10:15:29 +0100, Chris Green wrote:

    s|b <me@privacy.invalid> wrote:

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    Exactly my point.

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk writing, if so I'd like to know about them.

    Maybe he's just 'not interested' in explaining.
    --
    s|b
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From s|b@me@privacy.invalid to comp.sys.raspberry-pi on Tue Aug 4 15:09:54 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 04 Aug 2026 14:56:57 +0200, s|b wrote:

    On Tue, 4 Aug 2026 10:15:29 +0100, Chris Green wrote:

    That's weird, neither Chris's posting as Philo's were shown when I
    posted my follow-up. They're both using ES as a newsserver while I'm
    using NIN. Another ES hickup?
    --
    s|b
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Tue Aug 4 15:10:42 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 04/08/2026 13:56, s|b wrote:
    On Tue, 4 Aug 2026 10:15:29 +0100, Chris Green wrote:

    s|b <me@privacy.invalid> wrote:

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    Exactly my point.

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk
    writing, if so I'd like to know about them.

    Maybe he's just 'not interested' in explaining.

    I already did
    --
    The difference bweteen a psychopath and a saint is that the psychpoath
    takes what he can and gives only what he must, but the saint gives
    everything he can and takes only what he needs.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Tue Aug 4 15:11:42 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 04/08/2026 14:09, s|b wrote:
    On Tue, 04 Aug 2026 14:56:57 +0200, s|b wrote:

    On Tue, 4 Aug 2026 10:15:29 +0100, Chris Green wrote:

    That's weird, neither Chris's posting as Philo's were shown when I
    posted my follow-up. They're both using ES as a newsserver while I'm
    using NIN. Another ES hickup?

    Quite likely

    Out of order threads were very common back in the days of UUCP over
    modems :-)
    --
    The difference bweteen a psychopath and a saint is that the psychpoath
    takes what he can and gives only what he must, but the saint gives
    everything he can and takes only what he needs.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Green@cl@isbd.net to comp.sys.raspberry-pi on Tue Aug 4 17:55:25 2026
    From Newsgroup: comp.sys.raspberry-pi

    s|b <me@privacy.invalid> wrote:
    On Tue, 04 Aug 2026 14:56:57 +0200, s|b wrote:

    On Tue, 4 Aug 2026 10:15:29 +0100, Chris Green wrote:

    That's weird, neither Chris's posting as Philo's were shown when I
    posted my follow-up. They're both using ES as a newsserver while I'm
    using NIN. Another ES hickup?

    I use both ES and NIN, via leafnode running on my desktop machine. NIN
    is stopping in September though isn't it?
    --
    Chris Green
    -+
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Green@cl@isbd.net to comp.sys.raspberry-pi on Tue Aug 4 17:53:57 2026
    From Newsgroup: comp.sys.raspberry-pi

    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here' >> > tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change
    configurations,. Everything that writes is either stopped from writing >> > or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out
    which

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk writing, if so I'd like to know about them.

    Wot I do:

    Replace /sbin/init with a shell script that sets up the minimal necessary

    So you don't run systemd? While that may be a 'good idea' in some ways
    it does require a **lot** of customisation.

    ... and current stable Debian is 13, I don't think I want to go back
    as far as you are! :-)
    --
    Chris Green
    -+
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Andy Burns@usenet@andyburns.uk to comp.sys.raspberry-pi on Tue Aug 4 18:08:12 2026
    From Newsgroup: comp.sys.raspberry-pi

    Chris Green wrote:

    I use both ES and NIN, via leafnode running on my desktop machine. NIN
    is stopping in September though isn't it?

    That's *next* september ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.raspberry-pi on Wed Aug 5 00:46:44 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 4 Aug 2026 17:53:57 +0100, Chris Green wrote:

    Ian
    <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:

    Replace /sbin/init with a shell script that sets up the minimal
    necessary

    So you don't run systemd? While that may be a 'good idea' in some
    ways it does require a **lot** of customisation.

    Not really. Mount the right filesystems, make sure you can find the
    right executables on your $PATH and that those executables can find
    the right shared libraries ... what more do you need?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ian@${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com to comp.sys.raspberry-pi on Wed Aug 5 08:30:16 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here' >> >> > tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change
    configurations,. Everything that writes is either stopped from writing >> >> > or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out
    which

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk
    writing, if so I'd like to know about them.

    Wot I do:

    Replace /sbin/init with a shell script that sets up the minimal necessary

    So you don't run systemd? While that may be a 'good idea' in some ways
    it does require a **lot** of customisation.

    Absolutely not :)

    It's not a general-purpose computer, it's a device that runs a single program (wot I wrote), and it isn't going to change, ever. Yes, figuring out how to
    get things like wifi and sshd to run took a few iterations, but now that's a solved problem.


    ... and current stable Debian is 13, I don't think I want to go back
    as far as you are! :-)

    This was created many moons ago. It works, it isn't accessible from any public network, and I have no reason to keep chasing the dragon updating it "just because".
    Ultimately it may be replaced, but that will be a complete replacement with something else, not an update.

    Something very similar should be possible with later versions, unless they've finally integreted systemd into the kernel!
    --
    Ian

    "Tamahome!!!" - "Miaka!!!"
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Wed Aug 5 11:37:28 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 05/08/2026 09:30, Ian wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here' >>>>>> tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change
    configurations,. Everything that writes is either stopped from writing >>>>>> or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out >>>>>> which

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk >>>> writing, if so I'd like to know about them.

    Wot I do:

    Replace /sbin/init with a shell script that sets up the minimal necessary >>
    So you don't run systemd? While that may be a 'good idea' in some ways
    it does require a **lot** of customisation.

    Absolutely not :)

    It's not a general-purpose computer, it's a device that runs a single program (wot I wrote), and it isn't going to change, ever. Yes, figuring out how to get things like wifi and sshd to run took a few iterations, but now that's a solved problem.


    ... and current stable Debian is 13, I don't think I want to go back
    as far as you are! :-)

    This was created many moons ago. It works, it isn't accessible from any public
    network, and I have no reason to keep chasing the dragon updating it "just because".
    Ultimately it may be replaced, but that will be a complete replacement with something else, not an update.

    Something very similar should be possible with later versions, unless they've finally integreted systemd into the kernel!



    I think this is very clear and relevant info: you don't need to install
    a whole distros cruft just to get an IOT working. Neither does it need upgrading for 'security reasons' if its inside a private network

    Plenty of people just use a busybox superstructure...
    --
    No Apple devices were knowingly used in the preparation of this post.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Green@cl@isbd.net to comp.sys.raspberry-pi on Wed Aug 5 12:45:10 2026
    From Newsgroup: comp.sys.raspberry-pi

    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here'
    tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change
    configurations,. Everything that writes is either stopped from writing
    or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out
    which

    This is helpful.

    What would be more helpful would be some guidance on how to implement
    it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk >> > writing, if so I'd like to know about them.

    Wot I do:

    Replace /sbin/init with a shell script that sets up the minimal necessary

    So you don't run systemd? While that may be a 'good idea' in some ways
    it does require a **lot** of customisation.

    Absolutely not :)

    It's not a general-purpose computer, it's a device that runs a single program (wot I wrote), and it isn't going to change, ever. Yes, figuring out how to get things like wifi and sshd to run took a few iterations, but now that's a solved problem.

    Ah, that's a bit different from my situation, I need a familiar OS on
    the system in question.
    --
    Chris Green
    -+
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Wed Aug 5 13:22:32 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 05/08/2026 12:45, Chris Green wrote:
    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    Ian <${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com> wrote:
    On 2026-08-04, Chris Green <cl@isbd.net> wrote:
    s|b <me@privacy.invalid> wrote:
    On Mon, 3 Aug 2026 18:29:55 +0100, The Natural Philosopher wrote:

    in the true 'if i wanted to go there i wouldn't be starting from here' >>>>>>> tradition if its a 2W why not send its data to somewhere more
    interesting and secure?

    My Pi zero W never writes to its SD car at all unless i change
    configurations,. Everything that writes is either stopped from writing >>>>>>> or writes to ram discs.

    Some SD cards are better than others, I am not interested in finding out
    which

    This is helpful.

    What would be more helpful would be some guidance on how to implement >>>>> it! :-)

    E.g. how do you stop systemd's logging from writing to 'hard' disk? >>>>> It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Maybe there are versions of the OS that are optimised for minimal disk >>>>> writing, if so I'd like to know about them.

    Wot I do:

    Replace /sbin/init with a shell script that sets up the minimal necessary >>>
    So you don't run systemd? While that may be a 'good idea' in some ways
    it does require a **lot** of customisation.

    Absolutely not :)

    It's not a general-purpose computer, it's a device that runs a single program
    (wot I wrote), and it isn't going to change, ever. Yes, figuring out how to >> get things like wifi and sshd to run took a few iterations, but now that's a >> solved problem.

    Ah, that's a bit different from my situation, I need a familiar OS on
    the system in question.

    Yes. having e.g,. Apache and PHP on my zeros is essential. Those ware
    wheels I dont want to reinvent
    --
    When plunder becomes a way of life for a group of men in a society, over
    the course of time they create for themselves a legal system that
    authorizes it and a moral code that glorifies it.

    Fr|-d|-ric Bastiat

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From s|b@me@privacy.invalid to comp.sys.raspberry-pi on Wed Aug 5 19:50:44 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 4 Aug 2026 17:55:25 +0100, Chris Green wrote:

    I use both ES and NIN, via leafnode running on my desktop machine. NIN
    is stopping in September though isn't it?

    <https://individual.net/>

    | Discontinuation of the NetNews / Usenet service as of 30 September 2027
    --
    s|b
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From s|b@me@privacy.invalid to comp.sys.raspberry-pi on Wed Aug 5 20:25:31 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 4 Aug 2026 15:11:42 +0100, The Natural Philosopher wrote:

    On 04/08/2026 14:09, s|b wrote:

    That's weird, neither Chris's posting as Philo's were shown when I
    posted my follow-up. They're both using ES as a newsserver while I'm
    using NIN. Another ES hickup?

    Quite likely

    First time in a long time that I've noticed this.

    Out of order threads were very common back in the days of UUCP over
    modems :-)

    I used a 56K and had to ask my mom if she wasn't planning on phoning
    anyone.

    <https://www.youtube.com/shorts/t-lEezejkPM>
    --
    s|b
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Sat Aug 8 00:29:37 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 04/08/2026 10:15, Chris Green wrote:
    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Here are the important lines of /etc/systemd/journald.conf

    [Journal]
    Storage=volatile
    RuntimeMaxUse=32M
    RuntimeMaxFileSize=8M
    RuntimeMaxFiles=4
    ForwardToConsole=no
    ForwardToWall=no


    That will log to RAM only, a maximum of 32M in up to 4 files, so it
    should automatically prune 25% when it gets full, but I'm often having
    to do it manually with:-

    journalctl --vacuum-files 3

    Maybe there are versions of the OS that are optimised for minimal disk writing, if so I'd like to know about them.

    It's the config that needs to be optimised.

    ---druck


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Green@cl@isbd.net to comp.sys.raspberry-pi on Sat Aug 8 08:59:09 2026
    From Newsgroup: comp.sys.raspberry-pi

    druck <news@druck.org.uk> wrote:
    On 04/08/2026 10:15, Chris Green wrote:
    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Here are the important lines of /etc/systemd/journald.conf

    [Journal]
    Storage=volatile
    RuntimeMaxUse=32M
    RuntimeMaxFileSize=8M
    RuntimeMaxFiles=4
    ForwardToConsole=no
    ForwardToWall=no


    That will log to RAM only, a maximum of 32M in up to 4 files, so it
    should automatically prune 25% when it gets full, but I'm often having
    to do it manually with:-

    journalctl --vacuum-files 3

    That last rather spoils things, I'm expecting the systems in question
    to run for months (at least) without any intervention from me.

    ... and systemd's journalling isn't the only thing that writes, it was
    just the first thing that I thought of (hence the 'E.g.').
    --
    Chris Green
    -+
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Sat Aug 8 12:25:23 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 08/08/2026 00:29, druck wrote:
    On 04/08/2026 10:15, Chris Green wrote:
    E.g.-a how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Here are the important lines of /etc/systemd/journald.conf

    [Journal]
    Storage=volatile
    RuntimeMaxUse=32M
    RuntimeMaxFileSize=8M
    RuntimeMaxFiles=4
    ForwardToConsole=no
    ForwardToWall=no


    That will log to RAM only, a maximum of 32M in up to 4 files, so it
    should automatically prune 25% when it gets full, but I'm often having
    to do it manually with:-

    journalctl --vacuum-files 3

    Maybe there are versions of the OS that are optimised for minimal disk
    writing, if so I'd like to know about them.

    It's the config that needs to be optimised.

    ---druck


    +1. And this actually works
    --
    rCLBut what a weak barrier is truth when it stands in the way of an hypothesis!rCY

    Mary Wollstonecraft

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Sat Aug 8 12:27:52 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 08/08/2026 08:59, Chris Green wrote:
    druck <news@druck.org.uk> wrote:
    On 04/08/2026 10:15, Chris Green wrote:
    E.g. how do you stop systemd's logging from writing to 'hard' disk?
    It would need a **lot** of reconfiguration before it would use a
    reasonable amount of space such as is available on a RAM drive.

    Here are the important lines of /etc/systemd/journald.conf

    [Journal]
    Storage=volatile
    RuntimeMaxUse=32M
    RuntimeMaxFileSize=8M
    RuntimeMaxFiles=4
    ForwardToConsole=no
    ForwardToWall=no


    That will log to RAM only, a maximum of 32M in up to 4 files, so it
    should automatically prune 25% when it gets full, but I'm often having
    to do it manually with:-

    journalctl --vacuum-files 3

    That last rather spoils things, I'm expecting the systems in question
    to run for months (at least) without any intervention from me.

    I haven't done mine manually. Ever.

    ... and systemd's journalling isn't the only thing that writes, it was
    just the first thing that I thought of (hence the 'E.g.').

    Well that was where a ramdisk is handy to replace /var/log

    There is a command that looks at real I/O calls to e.g. disk drives. It should return zero ponce you achieve Nirvana...
    --
    rCLBut what a weak barrier is truth when it stands in the way of an hypothesis!rCY

    Mary Wollstonecraft

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Mon Aug 10 19:06:57 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 08/08/2026 08:59, Chris Green wrote:
    druck <news@druck.org.uk> wrote:
    That will log to RAM only, a maximum of 32M in up to 4 files, so it
    should automatically prune 25% when it gets full, but I'm often having
    to do it manually with:-

    That last rather spoils things, I'm expecting the systems in question
    to run for months (at least) without any intervention from me.

    ... and systemd's journalling isn't the only thing that writes, it was
    just the first thing that I thought of (hence the 'E.g.').

    Exactly why I wish systemd would FOAD!

    ---druck

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Mon Aug 10 19:21:30 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 10/08/2026 19:06, druck wrote:
    On 08/08/2026 08:59, Chris Green wrote:
    druck <news@druck.org.uk> wrote:
    That will log to RAM only, a maximum of 32M in up to 4 files, so it
    should automatically prune 25% when it gets full, but I'm often having
    to do it manually with:-

    That last rather spoils things, I'm expecting the systems in question
    to run for months (at least) without any intervention from me.

    ... and systemd's journalling isn't the only thing that writes, it was
    just the first thing that I thought of (hence the 'E.g.').

    Exactly why I wish systemd would FOAD!

    ---druck


    Trust me, it can be done
    systenmd does NOT carry on logging. My system is up months at a time and
    I never need to manually shrink it

    Everything else is a matter of picking through anything that logss an
    either diverting it to a RAM disk at configuration level, or symlinking
    is entry in /var/log to a ramdisk
    It takes time and the thing you may well lack, patience.
    --
    Labour - a bunch of rich people convincing poor people to vote for rich
    people by telling poor people that "other" rich people are the reason
    they are poor.

    Peter Thompson

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.raspberry-pi on Tue Aug 11 00:03:39 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 10 Aug 2026 19:06:57 +0100, druck wrote:

    On 08/08/2026 08:59, Chris Green wrote:

    ... and systemd's journalling isn't the only thing that writes, it
    was just the first thing that I thought of (hence the 'E.g.').

    Exactly why I wish systemd would FOAD!

    Ironically, itrCOs the one thing you can configure to work exactly the
    way you want.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jim Jackson@jj@franjam.org.uk to comp.sys.raspberry-pi on Tue Aug 11 07:33:18 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 2026-08-11, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
    On Mon, 10 Aug 2026 19:06:57 +0100, druck wrote:

    On 08/08/2026 08:59, Chris Green wrote:

    ... and systemd's journalling isn't the only thing that writes, it
    was just the first thing that I thought of (hence the 'E.g.').

    Exactly why I wish systemd would FOAD!

    Ironically, it???s the one thing you can configure to work exactly the
    way you want.

    As long as its the systemd way :-)

    Actually linux has always been very configurable the way you want,
    probably too configurable, because the plethora of options/alternatives
    etc can put people off.




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Stephan Elinghaus@seli@spamgourmet.com to comp.sys.raspberry-pi on Tue Aug 11 12:49:34 2026
    From Newsgroup: comp.sys.raspberry-pi

    Chris Green <cl@isbd.net> schrieb:
    I'd welcome any recommendations for cards that last well.

    Since I began using industrial grade cards (e.g. Kingston industrial) I
    never had any issues with a defective card any more. Those cards may
    not be the fastest, but they have proven to be very reliable.
    --
    [place signature here]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.raspberry-pi on Wed Aug 12 01:25:45 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 11 Aug 2026 07:33:18 -0000 (UTC), Jim Jackson wrote:

    On Tue, 11 Aug 2026 00:03:39 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    Ironically, itrCOs the one thing you can configure to work exactly
    the way you want.

    As long as its the systemd way :-)

    The rCLsystemd wayrCY lets you send the logging wherever you want. Want it
    all to go to rsyslog? Send it there. Then you can blame rsyslog for
    eating your SD-card, not systemd.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jim Jackson@jj@franjam.org.uk to comp.sys.raspberry-pi on Thu Aug 13 16:55:03 2026
    From Newsgroup: comp.sys.raspberry-pi

    On 2026-08-12, Lawrence D?Oliveiro <ldo@nz.invalid> wrote:
    On Tue, 11 Aug 2026 07:33:18 -0000 (UTC), Jim Jackson wrote:

    On Tue, 11 Aug 2026 00:03:39 -0000 (UTC), Lawrence D???Oliveiro wrote:

    Ironically, it???s the one thing you can configure to work exactly
    the way you want.

    As long as its the systemd way :-)

    The ???systemd way??? lets you send the logging wherever you want.

    Oh dear you took it waaayyy too seriously! I never said it couldn't! I
    merely meant that, in the bits you edited out, that you could even
    Before Systemd "configure [it] to work exactly the way you want". But obviously I touched one of your buttons, as you did mine :-)


    And to be more on topic, I'd suggest to the original poster, that having
    a local syslog log server is useful. Configure your RPi machine to send
    the log entries to that. No SD writes and the logs are there even if the
    SD card gets corrupt for other reasons.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.sys.raspberry-pi on Thu Aug 13 23:29:10 2026
    From Newsgroup: comp.sys.raspberry-pi

    On Thu, 13 Aug 2026 16:55:03 -0000 (UTC), Jim Jackson wrote:

    I merely meant that, in the bits you edited out, that you could even
    Before Systemd "configure [it] to work exactly the way you want".

    As I recall, the original complaint was about logfiles shortening the
    life of SD cards. How would this have helped?
    --- Synchronet 3.22a-Linux NewsLink 1.2