commandlinefu.com is the place to record those command-line gems that you return to again and again.
Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/
You can sign-in using OpenID credentials, or register a traditional username and password.
First-time OpenID users will be automatically assigned a username which can be changed after signing in.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
this command will beep like an alarm for one minute from 18:57. you can change "1857" to your desired time.
you should have alsa-oss package installed, and you should also be root or part of "audio" group.
There are 2 alternatives - vote for the best!
If you can do better, submit your command here.
You must be signed in to comment.
You're probably better off with:
at 18:57
at > beep
+
You need the beep-package of course, and you may need to comment out "pcspkr" from /etc/modules.conf/blacklist.conf .
And you finish giving commands to "at" by pressing ctrl+D.
that is of course one way of doing that, but you should be root (or change the permissions of the command) and you should unmute the beep channel in alsamixer (which I have it always muted).
a one liner for your command would be:
echo beep < at 18:57
and you may also customize the command with some options like:
beep -f 5000 -l 100 -r 4
which will change the frequency and length, and will repeat the beep 4 times.
sorry, I meant: echo beep | at 18:57
I didn't think of putting an echo in front of beep.
This definitly works better than beep|at 18:57 (the latter beeping when I give the command AND at the given time...),
I don't understand why, though.