Modify a linux command
Modify a linux command
Looking for ways to alter Linux commands and enhance their capabilities? Let me know!
You can locate source code for commands like ls and poweroff in documentation or repositories related to the operating system you're using. Check official developer websites, community forums, or package managers for references.
Determine the package it is part of, then locate its source code repository. For instance, basic tools like `ls` come from the GNU coreutils package, available at http://git.savannah.gnu.org/cgit/coreutils.git/tree/src, where you can view the file at http://git.savannah.gnu.org/cgit/coreuti...e/src/ls.c.
On a Debian-based system you can determine the package by running dpkg -S /bin/ls. This will indicate it's part of coreutils. Next, use apt-cache show coreutils to retrieve details like the homepage and source code. You can also download the package's source via apt, for example from the provided link.
You're asking about specific adjustments you'd like to make. There are more straightforward options available—like creating a custom alias for "ls" or using another tool such as exa. Updating and recompiling the software isn't recommended since it could interrupt updates and cause issues with essential functions.
I have a raspberry pi and I want it to show a message on a nokia screen right before powering off to know when it's safe to unplug it. The problem is that showing this image before executing the command won't cut it since in the case where the poweroff command takes too much time the user could unplug it without it being safe. There is a method to show the PI's status with an LED and GPIO pins but it isn't acceptable in my case. My thinking was to run the script once the bulk of the shutting down was done. If you think of a better way I'm all ears because I agree with you, mine is extremely janky... This is necessary since the screen stays on/doesn't clear once the pi shuts down.
A systemd service could help manage this. The ExecStop feature lets you execute a script when the service stops. Running it before starting ensures the script runs last, which is useful for cleanup before shutdown. This works with Raspbian, but if you're using a different init system, you'll need to adjust accordingly.
I'm using raspbian. Your setup looks much neater! Regarding your question, what's the optimal order for starting services?