Alpine - Revision history

ViciousCarnivore: /* Compiling a Kernel in Alpine or ARM and DTS / DTB */

2025-05-22T00:11:54Z

Compiling a Kernel in Alpine or ARM and DTS / DTB

ViciousCarnivore: /* Compiling a Kernel in Alpine */

2025-05-22T00:10:26Z

Compiling a Kernel in Alpine

ViciousCarnivore: /* Building a package in Alpine */

2025-05-22T00:09:43Z

Building a package in Alpine

ViciousCarnivore: /* NTP: Chronyd not updating the time */

2025-04-09T09:24:49Z

NTP: Chronyd not updating the time

ViciousCarnivore: /* NTP: Chronyd not updating the time */

2025-04-09T09:23:30Z

NTP: Chronyd not updating the time

ViciousCarnivore: /* NTP: Chronyd not updating the time */

2025-04-09T09:22:27Z

NTP: Chronyd not updating the time

ViciousCarnivore: /* NTP: Chronyd not updating the time */

2025-04-09T09:21:24Z

NTP: Chronyd not updating the time

ViciousCarnivore: /* NTP: Chronyd not updating the time */

2025-04-09T09:14:05Z

NTP: Chronyd not updating the time

ViciousCarnivore: /* apk Update Between Versions */

2025-04-09T09:03:29Z

apk Update Between Versions

ViciousCarnivore: /* /etc/crontab */

2024-12-31T06:21:44Z

/etc/crontab

@@ Line 11: / Line 11: @@
 See above, also
 * https://wiki.alpinelinux.org/wiki/Odroid-C2
 ===Xorg video playback stutters upon suspend / resume===

@@ Line 8: / Line 8: @@
 * https://wiki.alpinelinux.org/wiki/Custom_Kernel
-===Compiling a Kernel in Alpine===
+===Compiling a Kernel in Alpine or ARM and DTS / DTB===
 See above, also
 * https://wiki.alpinelinux.org/wiki/Odroid-C2

@@ Line 4: / Line 4: @@
 ===Building a package in Alpine===
-https://wiki.alpinelinux.org/wiki/Category_talk:Developer_Documentation#Building_from_source_and_creating_packages
+* https://wiki.alpinelinux.org/wiki/Category_talk:Developer_Documentation#Building_from_source_and_creating_packages
-https://wiki.alpinelinux.org/wiki/Custom_Kernel
+* https://wiki.alpinelinux.org/wiki/Custom_Kernel
 ===Xorg video playback stutters upon suspend / resume===

@@ Line 125: / Line 125: @@
 NTP clients started from cron with no delay.
 </pre>
-Hilarious. I don't know who is really at fault here... Do you blame the users, cron programmers, or the ntp client programmers...? Whom is expected to deal with this complexity? (The answer is probably the NTP Client programmers, because they are the experts, not the users).
+Hilarious. I don't know who is really at fault here... Do you blame the users, cron programmers, or the ntp client programmers...?
 ===lbu===

@@ Line 125: / Line 125: @@
 NTP clients started from cron with no delay.
 </pre>
-Hilarious. I don't know who is really at fault here... Can you blame the users, or should you blame the crontab designers.
+Hilarious. I don't know who is really at fault here... Do you blame the users, cron programmers, or the ntp client programmers...? Whom is expected to deal with this complexity? (The answer is probably the NTP Client programmers, because they are the experts, not the users).
 ===lbu===

← Older revision		Revision as of 09:21, 9 April 2025
Line 110:		Line 110:

	https://stackoverflow.com/questions/49730407/how-to-do-one-shot-time-sync-using-chrony		https://stackoverflow.com/questions/49730407/how-to-do-one-shot-time-sync-using-chrony
		+
		+	The official docs at chrony-project.org are also worth looking at. Good website design, and the FAQ answers
		+	the oneshot question from stack overflow above (which, the official answer is to use chronyc -q <server> not -a makestep.
		+	Here's an interesting tidbit from the FAQ:
		+	<pre>
		+	It is not recommended to run chronyd with the -q option periodically
		+	(e.g. from a cron job) as a replacement for the daemon mode, because it
		+	performs significantly worse (e.g. the clock is stepped and its
		+	frequency is not corrected). If you must run it this way and you are
		+	using a public NTP server, make sure chronyd does not always start
		+	around the first second of a minute, e.g. by adding a random sleep
		+	before the chronyd command. Public servers typically receive large
		+	bursts of requests around the first second as there is a large number of
		+	NTP clients started from cron with no delay.
		+	</pre>
		+	Hilarious.

	===lbu===		===lbu===

@@ Line 103: / Line 103: @@
 Setting the time can be done manually with:
   chronyc -a makestep
-This can be put in a cron job. Alternatively, you can add makestep to the /etc/chrony/chrony.conf file.
+This can be put in a cron job. Alternatively, you can add makestep 1 -1 to the /etc/chrony/chrony.conf file.
 The wiki's (alpine, gentoo) only list what the man page says, which is makestep 0.1 3, but I think (have
 not tested) you don't want that as it only syncs three times, according to the man page. See also:
 ===lbu===

@@ Line 90: / Line 90: @@
 * If you run out of space in boot (as I did) just back up or delete the old kernel and initramfs (they will be in a folder, e.g. 202012) then mkinitfs and grub-mkimage again. should boot.
 * If you get errors on apk, there is an apk fix. This might also run mkinitfs and grub again.
 ===lbu===

← Older revision		Revision as of 06:21, 31 December 2024
Line 104:		Line 104:

	This is a bit confusing. Busybox does not use /etc/crontab, and you can't add it in via /etc/conf.d/crond as a -c (that is for directories only). Debian uses vixie-cron which is not available in alpine (check community repos). You may be able to add it via runparts in the cron -e for root (put an entry for /etc/crontab and run it every minute). I did this, as well as installed cronie, and after updating the run levels appropriately (it tells you what to do when installing), removing busybox cron and adding cronie, then restarting, i was able to get /etc/crontab to start. I need to test if you can get the same behavior by just restarting busybox cron, without installing cronie. In any case, it will work with cronie. See: https://bbs.archlinux.org/viewtopic.php?id=193568 https://wiki.archlinux.org/title/Cron#Cronie_2		This is a bit confusing. Busybox does not use /etc/crontab, and you can't add it in via /etc/conf.d/crond as a -c (that is for directories only). Debian uses vixie-cron which is not available in alpine (check community repos). You may be able to add it via runparts in the cron -e for root (put an entry for /etc/crontab and run it every minute). I did this, as well as installed cronie, and after updating the run levels appropriately (it tells you what to do when installing), removing busybox cron and adding cronie, then restarting, i was able to get /etc/crontab to start. I need to test if you can get the same behavior by just restarting busybox cron, without installing cronie. In any case, it will work with cronie. See: https://bbs.archlinux.org/viewtopic.php?id=193568 https://wiki.archlinux.org/title/Cron#Cronie_2
		+
		+	/etc/crontab is a 'simple' way to do cron, and I think it is enough.

	===Misc===		===Misc===