Regressions Of GNU\Linux - Revision history

ViciousCarnivore: /* Homogenization of Software */

2026-04-07T08:33:26Z

Homogenization of Software

2026-04-07T08:30:45Z

Homogenization of Software

2026-04-07T08:30:04Z

Divide and Conquer: Wayland

2026-04-05T08:46:35Z

Cron Environment: Again

2026-04-05T08:46:23Z

Cron Environment: Again

2026-04-05T08:44:32Z

Cron Environment: Again

2026-04-05T08:44:00Z

Cron Environment: Again

2026-04-05T08:27:59Z

Cron Environment: Again

2026-04-05T08:24:56Z

Cron Environment

2026-03-04T22:26:53Z

Cron Bad Design: Having 0 be an incorrect value

@@ Line 373: / Line 373: @@
 Don't ask questions, just use it, like everyone else. Conform. Get in line.
-Unfortunately, Monocultures are bad.
+Unfortunately, Monocultures are bad. Single point of failure. Single point to corrupt.
 ==Related Links==

@@ Line 369: / Line 369: @@
 Everyone use docker.
-Don't ask questions, just use it, like everyone else.
+Everyone use systemd.
 Unfortunately, Monocultures are bad.

@@ Line 363: / Line 363: @@
 Those are some pretty significant names. If you break steam, you break one of the best things going for Linux at the moment.
 Then there is the post by dedoimedo. https://www.dedoimedo.com/computers/wayland-2024.html In any case, this will be fun to watch.
 ==Related Links==

@@ Line 322: / Line 322: @@
 If you run into this, you can do 'some' troubleshooting with proper output/stderr redirection. It took me a while to realize that the proper way to output is to do
   ./myscript.sh 1> stdout.log 2> stderr.log
-The trick, or the trap here, is to avoid the 2>&1 syntax, which is code golf which obfuscates what is more clearly written as the 1> and 2> instructions. Syntax hell. Covered [https://stackoverflow.com/questions/818255/what-does-21-mean here]
+The trick, or the trap here, is to avoid the 2>&1 syntax, which is code golf which obfuscates what is more clearly written as the 1> and 2> instructions. Syntax hell. Covered on stack overflow [https://stackoverflow.com/questions/818255/what-does-21-mean here]
 ====Cron Bad Design: Having 0 be an incorrect value====

@@ Line 322: / Line 322: @@
 If you run into this, you can do 'some' troubleshooting with proper output/stderr redirection. It took me a while to realize that the proper way to output is to do
   ./myscript.sh 1> stdout.log 2> stderr.log
-The trick, or the trap here, is to avoid the 2>&1 syntax, which is code golf which obfuscates what is more clearly written as the 1> and 2> instructions. Syntax hell.
+The trick, or the trap here, is to avoid the 2>&1 syntax, which is code golf which obfuscates what is more clearly written as the 1> and 2> instructions. Syntax hell. Covered [https://stackoverflow.com/questions/818255/what-does-21-mean here]
 ====Cron Bad Design: Having 0 be an incorrect value====

@@ Line 320: / Line 320: @@
 I'm not accepting the answer from stack exchange that "You need to add the relevant paths, bla bla bla." That is horseshit. Not acceptable. I specified the user. Cron is just broken.
-If you run into this, you can do 'some' troubleshooting with proper output/stderr redirection. It took me a while to realize that the proper way to output is to do myscript.sh 1> stdout.log 2> stderr.log. The trick, or the trap here, is to avoid the 2>&1 syntax, which is code golf which obfuscates what is more clearly written as the 1> and 2> instructions. Syntax hell.
+If you run into this, you can do 'some' troubleshooting with proper output/stderr redirection. It took me a while to realize that the proper way to output is to do
 ====Cron Bad Design: Having 0 be an incorrect value====

← Older revision		Revision as of 08:44, 5 April 2026
Line 319:		Line 319:

	I'm not accepting the answer from stack exchange that "You need to add the relevant paths, bla bla bla." That is horseshit. Not acceptable. I specified the user. Cron is just broken.		I'm not accepting the answer from stack exchange that "You need to add the relevant paths, bla bla bla." That is horseshit. Not acceptable. I specified the user. Cron is just broken.
		+
		+	If you run into this, you can do 'some' troubleshooting with proper output/stderr redirection. It took me a while to realize that the proper way to output is to do myscript.sh 1> stdout.log 2> stderr.log. The trick, or the trap here, is to avoid the 2>&1 syntax, which is code golf which obfuscates what is more clearly written as the 1> and 2> instructions. Syntax hell.

	====Cron Bad Design: Having 0 be an incorrect value====		====Cron Bad Design: Having 0 be an incorrect value====

← Older revision		Revision as of 08:27, 5 April 2026
Line 317:		Line 317:

	Cron is supposed to run as a user. So you specify the user. But, cron doesn't include all the relevant path information. So in fact, cron is not running as the user. This is subversive mind fucking troll tech. It just doesn't work. That's it. It's shit.		Cron is supposed to run as a user. So you specify the user. But, cron doesn't include all the relevant path information. So in fact, cron is not running as the user. This is subversive mind fucking troll tech. It just doesn't work. That's it. It's shit.
		+
		+	I'm not accepting the answer from stack exchange that "You need to add the relevant paths, bla bla bla." That is horseshit. Not acceptable. I specified the user. Cron is just broken.

	====Cron Bad Design: Having 0 be an incorrect value====		====Cron Bad Design: Having 0 be an incorrect value====

← Older revision		Revision as of 08:24, 5 April 2026
Line 312:		Line 312:

	Otherwise, cron is gold.		Otherwise, cron is gold.
		+
		+	====Cron Environment: Again====
		+	The funny thing is, you can define this real simple.
		+
		+	Cron is supposed to run as a user. So you specify the user. But, cron doesn't include all the relevant path information. So in fact, cron is not running as the user. This is subversive mind fucking troll tech. It just doesn't work. That's it. It's shit.

	====Cron Bad Design: Having 0 be an incorrect value====		====Cron Bad Design: Having 0 be an incorrect value====

← Older revision		Revision as of 22:26, 4 March 2026
Line 326:		Line 326:

	So what happens is that you accidentally enter in a 0 for month or day of the month, and then the cron is invalid, and doesn't run at all. This is just bad design. It should run in a broken state (i.e. 0 gets converted to 1 with a warning), and not simply error out. Note that day of the week, could very well have been 1-7, yet they allowed 0, yet the did NOT allow 0 for day of month or month. This is not how a reasonable person would have designed the date entry. This seems slightly malicious. I.e. a trap.		So what happens is that you accidentally enter in a 0 for month or day of the month, and then the cron is invalid, and doesn't run at all. This is just bad design. It should run in a broken state (i.e. 0 gets converted to 1 with a warning), and not simply error out. Note that day of the week, could very well have been 1-7, yet they allowed 0, yet the did NOT allow 0 for day of month or month. This is not how a reasonable person would have designed the date entry. This seems slightly malicious. I.e. a trap.
		+
		+	Regardless, you should probably have something monitoring services in case they don't run.

	===Divide and Conquer: Wayland===		===Divide and Conquer: Wayland===