@Ron: never apologize for making an effort to develop your understanding of a topic.

Two ways you can verify if a program is installed.  Replace "program" with anacron:
A) which program
The which command will print the full path of your program.  If it isn't in your executables path, the output will be blank.  If you want to check which directories are in your path, run "echo $PATH".   Note that root has different folders in their path than normal users, including /sbin.
B) find / -iname *program*
This will take awhile, but if it is anywhere in your system, it should find it.  This works for any file or directory, by the way.  -iname will ignore case (uppercase or lowercase) differences.  The asterisks (*) is a bash wildcard; in this case, find will find any file or folder with the string "anacron".

There are many more ways, but I prefer these.

You may want to research cron.daily and the others.

To reiterate, I'm not sure why you're pointing cron to a script that runs a simple command.  I would use a script if there were a series of lines.

Yesterday, Gnuser linked to an interesting case regarding anacron.  I'm assuming you read it.  No idea if it applies to your situation.  In any case, reinstalling  or installing anacron is trivial.

The way you add commands will depend on whether or not you use cron or anacron.  Each application has rich usage, and may require restarting its own daemon.  I cannot say with certainty because it's been a long time since I've needed to add or modify a cron or anacron job.  (I've also never modified cron commands on a Mint system, so I have no idea if the "Mint way" follows a different approach.)  However, the links below should provide ample documentation, or at least direction, for task scheduling on Debian/Devuan/Miyo.

https://debian-administration.org/artic … _with_cron
https://wiki.debian.org/CronAnacronAtBatchSchedulers

To be clear, I'm leaving the documentation because I'm not sure what kind of system you're using; on a server, I only use cron, but I've heard other users swear by anacron on laptops or other systems that are routinely powered-off/suspended/hibernated.

Based on the output, it looks like you mislaunched the command.  Research how to launch a custom script in a linux shell.

Also, I have no idea why you didn't just run:

/sbin/fstrim --all || true

directly in a root shell.

You can also specify backported packages with the "-t [repo]" option (eg, "-t jessie-backports").  Then you can keep the bpo repo uncommented and use only when needed.

I am assuming you understand what this command does and why.

Have you ran this command in devuan yet (not as a cron job, just a command)?  If not, understand that there is a slight opportunity for misbehavior; because the developer hasn't messed with SSDs, you will basically be playing the role of tester.

If all you want is to know how to set up the cron job, then figure out which cron application your version of Mint uses first.  In devuan, you can either...
a) learn the cron version and syntax that miyo uses and create a new job for your needs; or,
b) if you really want, and if it's in the devuan repos, use the version of cron that Mint ships.  Just try to understand that you may end up setting up more than anticipated if it's not a miyo default.

crunkbong 0.7.9 is released!
https://sourceforge.net/projects/crunkb … o/download

Changelog, 4/20/2018:
-Edited the openbox right-click menu for common gui apps.  crunkbong doesn't ship with many gui apps at all, so the featured ones are really the most important imo.  I decided to stick with this method because traditional menus and approaches required more dependencies -- and storage space -- than desired.  It isn't worth it since most of the apps are cli-based.
-Switched the default shell back to bash.  I'll probably end up changing it back to ksh once I figure out sensible keybindings/completion.
-Added a readme file for common apps/scripts.  Most of it is console-based, so this is more of a quick overview.
-Separated the proprietary network firmware to .debs in a folder.  This was a direct inspiration from refracta (thanks, fsmithred).
-Added xfe as the primary file manager.  Minus all the ridiculous dependencies.
-Added a line in .xinitrc to give dwm a small tray with battery, date, and time.  Thanks to Head_on_a_Stick.

Works in progress:
-Still looking for the leanest menu solution known to man.
-Beginning migration to ascii
-Still open to testers' advice and suggestions.

@Panopticon: I'll certainly take that into consideration XD  the irony is that my friend had the same idea when we first started this.
@wdq: would you mind sharing your strategies for keeping ram usage that low?

Honestly, if this comment alone had been the entire first post, I think it would have saved a lot of people a lot of headache.

Then fork the original: bleach it, rebrand it, and share it.  Setting up a personal github is easy.  I'm sure someone is bound to use it.

crunkbong (my project) is intended to focus on security, mostly through minimalism.  I'm one step away from updating the kernel to 4.15.x for full meltdown mitigation (still deciding whether or not to use liquorix).  The biggest issue I foresee you having with it is proprietary wifi drivers, which are the only proprietary components, and can be easily disabled or uninstalled before any network connection is established.  (I'm actually trying to determine the best way to address this, btw, and I'm open to suggestions.)

If you're daring enough to boot it, and can post tangible findings regarding any proprietary-firmware-based exploits, I'd definitely love to hear back.

Not that I recommend it for daily use, aside from (I guess) being a sensible base, but it uses refractainstaller -- can't remember if this is the "default" devuan installer that this conversation is criticizing.  Alternatively, one could easily manually partition a disk and debootstrap a base system.  This process isn't far removed from using apt, as far as I can tell.

http://dev1galaxy.org/viewtopic.php?id=1976

Short answer: I just needed a name.
Less-short answer: it's a nonsense quasi-homonym for "crunchbang."

I used crunchbang for about three years.  A few years ago -- when Newborough made the official announcement to call it quits, but before BunsenLabs chimed in -- I considered all options, and deterimined to just follow Newborough's footsteps and make my own iteration in its spirit, but with some other features I find really useful. 

The name was always a placeholder, but I never found a need to change it.  The immature teenager in me looks forward to a future where people seriously announce absurd release names like "Crunkbong 1.0 (Bingbong)".

http://forums.debian.net/viewtopic.php? … 39#p671120

This was perfect, thanks.