Sponsored Content
Full Discussion: Hacking buddy
The Lounge What is on Your Mind? Hacking buddy Post 302981893 by wisecracker on Wednesday 21st of September 2016 05:12:06 AM
Old 09-21-2016
Quote:
Shell scripting is great for automatising stuff thats for sure. How did you start to learn?
(First of all I am NOT a coder, I am a hobbyist coder and I do have bad habits. I am however a retired electronics engineer.)

By BRAGGING I could do something different that the shell and terminal were not designed for although I had no idea what I was talking about.
I had no idea whether my future creation would even get off of the ground but hey I said it would so take a look, this is nealy 4 years old now. Gained 5 stars here, had a magazine write up and the Admins on here have allowed it to flow - MANY THANKS GUYS. This is the site that gets the latest version FIRST, there is another but this one is always at least one week ahead.

I have thanked the big guns for their help that they in fact volunteered without me even asking and at least 50% of their help is incorporated is said script with subtle changes to suit my coding style. Only download the latest version if you want to see it but do read how this huge script has evolved over the period. I am actually having a break from it at the moment but I am removing legacy stuff to bring it into the 21st century... ;oD

Still loads to do however, getting there but it is slow now as the really difficult bits are hard to work out. One is using a counter for DC input. This is seriously difficult on ths MBP.
Chopper and VCO methods for DC input are built but Chopper mode is not coded for yet.

The Start Of A Simple Audio Scope Shell Script...

I have started some other things on here that I will get back too when this baby is finished but building hardware as well as coding for it takes mega-time to get working...

So to finish I jumped in at the deep end - literally - not knowing a thing about terminals or shells but learnt a lot by doing something so bizarre that no one has ever done before...

So don't underestimate the terminal and shell along with transient commands at your disposal. To be truthful it was the terminal and its escape codes that initiated this project as I just love doing everything in text mode...

You could say I am a minimalist... ;oD

Bazza...
 

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Hacking

I asked my firend about hacking so he told me to come here. I want to know how to get Volumes I, II and III. Does anyone know how to help me and help me become a good hacker? This is what i came here to do!!!!!! (2 Replies)
Discussion started by: nfsu2
2 Replies

2. Linux

Hacking

Im wondering how i can chat to some one (1 Reply)
Discussion started by: Neas
1 Replies

3. Cybersecurity

hacking

I want to start with hacking and learning it from the scratch! I have googled and found thousands of pages but I would like to know how to start really! It's always good to hear from security experts. please give me some links. the ones which are related to unix hacking. (1 Reply)
Discussion started by: messi777
1 Replies
wuzzah(1)							      Wuzzah?								 wuzzah(1)

NAME
wuzzah - keep an eye out for friends on a local system SYNOPSIS
wuzzah [OPTIONS...] DESCRIPTION
wuzzah is a program that just sits around and scans the utmpx entries to watch when your friends log in and out. By default upon invoca- tion, wuzzah looks for the file ${HOME}/.wuzzah, and loads the list of buddies contained therein (which are separated by newlines), and then sits and watches. If no file is found, and no other readable file is specified (see OPTIONS), wuzzah will attempt to just watch for whomever the current uid maps, and failing that will just quit. OPTIONS
-h, --help an informative usage summary, though nothing you don't see here... -a, --all-users watches for all users on the system, period. -c, --exec-cmd=CMD execute CMD upon a login. NOTE: this is done with a call to system(2), so you can do things like piping and whatever else you can do with sh -c -f, --buddy-file=FILE use FILE as buddyfile. naturally FILE must be readable, and consists of usernames, one to a line. optionally, these usernames can be followed by a colon, and then a wuzzah command-line to override wuzzah's behavior for this specific user. -F, --no-buddyfile tells wuzzah to not bother loading any config files. -i, --interval=NUM sleep NUM seconds between each polling -m, --message=STRING use STRING as a message template to greet logged-in buddies. See the section FORMATS for more information. -n, --no-newline don't end the messages with newlines (normally does by default) -o, --process-once scan the login records once, then exit -p, --process-current by default wuzzah doesn't message users who were already logged in when started up. this option overrides such behavior and mes- sages them anyways (only useful with the -w/-c options) -q, --silent don't message buddies when they log in (default). -s, --status-message=STRING use STRING as a template for displaying the status of people logging in and out. See FORMATS for more information. -u, --users=LIST adds every user in LIST (a space/comma/colon separated list of users) to the buddy list -v, --version the current version and copyright. -w, --write-buddies turns on messaging of buddies as they log in. NOTE: this can get quite annoying rather quickly. tune in soon for a less annoying solution FORMATS
message templates can be defined as normal character strings, interspersed with special format characters. format characters consist of a `%', followed by a character, which defines situation-specific data. The current list of these characters is as follows: a the alert character ('a') b the name of the buddy who has logged in/out d the date, currently in HH:MM:SS format h and H the remote hostname or IP address (respectively) of your buddy's login l the line in/out on which the buddy is logged (typically, something like /dev/pts/9 or /dev/ttyS0) m whether or not you have just messaged your buddy (really only useful for the -s option) n an embedded newline character o your buddy's online status ("logged on" or "logged off") u your own username, as can best be determined by the program. EXAMPLES
a simple invocation: username@machine$ wuzzah (13:45:39) foo logged in on :0 (not messaging). (13:45:39) bar logged in on pts/11 (not messaging). Message from username@machine on pts/11 at 14:00 ... (wuzzah) username says: "shoutout to my homie foo." EOF an example with a little more user customization: username@machine$ wuzzah --message="hey, %b, it's %u. nice to see you at %d!" and when foo logs in, foo will get a message like so: Message from username@machine on pts/11 at 14:00 ... hey, foo, it's username. nice to see you at (14:00:00)! EOF FILES
$HOME/.wuzzah the default file containing the list of users to watch BUGS
don't know of any, but reports (and patches too) are always welcome. feel free to send them to the author. AUTHOR
sean finney <seanius@seanius.net> sean finney Sun Nov 17 02:41:45 EST 2002 wuzzah(1)
All times are GMT -4. The time now is 08:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy