From 09bf92e0f025d16a2ced08e1b7638cf209e99a88 Mon Sep 17 00:00:00 2001
From: Dominik Kohler <18621527+kohlerdominik@users.noreply.github.com>
Date: Mon, 30 Apr 2018 16:25:40 +0200
Subject: [PATCH] Keep cron package

Is there any reason, why cron should be removed?
I think, for a lot of application it's still a usefull function.

Of course, we should keep fake-hwclock as well, like #4 suggests. Or, if there are any reasons to remove hwclock, then maybe we can install "ntp" instead?
---
 read-only-fs.sh | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/read-only-fs.sh b/read-only-fs.sh
index 72f6a67..5ed9b0c 100644
--- a/read-only-fs.sh
+++ b/read-only-fs.sh
@@ -178,12 +178,12 @@ echo "Updating package index files..."
 apt-get update
 
 echo "Removing unwanted packages..."
-#apt-get remove -y --force-yes --purge triggerhappy cron logrotate dbus \
-# dphys-swapfile xserver-common lightdm fake-hwclock
+#apt-get remove -y --force-yes --purge triggerhappy logrotate dbus \
+# dphys-swapfile xserver-common lightdm
 # Let's keep dbus...that includes avahi-daemon, a la 'raspberrypi.local',
 # also keeping xserver & lightdm for GUI login (WIP, not working yet)
-apt-get remove -y --force-yes --purge triggerhappy cron logrotate \
- dphys-swapfile fake-hwclock
+apt-get remove -y --force-yes --purge triggerhappy logrotate \
+ dphys-swapfile
 apt-get -y --force-yes autoremove --purge
 
 # Replace log management with busybox (use logread if needed)