On Tue 27 Feb 2024 at 15:35:07 (+0000), Michael Kjörling wrote: > On 27 Feb 2024 10:15 -0500, from [email protected] (Gary Dale):
> In this case you might even want the second to execute only when the > first completes _successfully_, so: > > @reboot /usr/sbin/modprobe brcmfmac && echo 13b1 0bdc > > /sys/bus/usb/drivers/brcmfmac/new_id I wondered whether that might cause any error message to be lost in normal booting output (assuming you've asked for it). > _That said_, if you want to load a module on boot, the generally > recommended way these days is to add it to a *.conf file in > /etc/modules-load.d. See modules-load.d(5) for details. The old way > was to add it to the file /etc/modules. In which case, I'd write the remaining cron line as: @reboot sleep 99 && echo 13b1 0bdc > /sys/bus/usb/drivers/brcmfmac/new_id where you can choose a better estimate than 99. > > Anyway, that got me down the rabbit hole to try to find where the crontab > > file is. > > Per-user crontabs are in /var/spool/cron/crontabs, or at least are in > Bookworm (and this has been the case for what feels like forever). > This is mentioned in the DIAGNOSTICS section of the crontab(1) man > page, as well as in the NOTES section of the cron(8) man page. If you lose track of where a crontab was originally generated from¹, the filename is in the second line of /var/spool/cron/crontabs/<username>. Note that you won't see the first three lines of crontabs/<username> listed by crontab -l or at the top of the file edited by crontab -e because they're stripped out and reinserted by crontab². See the DEBIAN SPECIFIC section in man 1 crontab. ¹ Assuming you use crontab filename. Otherwise, the filename in crontabs/<username> will be of little interest. ² This behaviour can be overridden with CRONTAB_NOHEADER='N' Cheers, David.
