Reply to: Mac Terminal help

[petergriffin]

Not sure what you mean mate? it's a manually typed command, not a script. (sorry, new to the Mac terminal...)

If you want to know if a particular command is a shell script or a proper binary you can use 'which' and 'file':

bash-4.2$ which firefox
/usr/local/bin/firefox
bash-4.2$ file /usr/local/bin/firefox 
/usr/local/bin/firefox: symbolic link to `/opt/firefox/firefox'
bash-4.2$ file /opt/firefox/firefox
/opt/firefox/firefox: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), stripped

root@local:~# which slackpkg
/usr/sbin/slackpkg
root@local:~# file /usr/sbin/slackpkg 
/usr/sbin/slackpkg: POSIX shell script, ASCII text executable

EDIT: the above was done on Slackware, on the Mac you'll have different results of course.

[Sysman]

I've got the O'Reilly Sed and Awk which is quite comprehensive (Second Edition which came out in 1997 - don't suppose much has changed; it was the equivalent of 25 quid then).

The BBEdit folks reckon that Chapter 8 of their User Manual is good for learning regular expressions. PDF available from the BBEdit Support Page. BBEdit is the paid version of TextWrangler, with a pile of extra goodies that folks obviously find worth the price.

[Platypus]

I'd still get a grounding in Sed and Awk though in case you come across them in existing scripts and examples

Man pages for sed and awk are indecipherable IMO. But this book is excellent:
http://www.amazon.co.uk/sed-Nutshell...6576757&sr=8-1

I'm not sure that awk is used very much these days, perl seems to be prevalent now.

I'm surprised it's £20 though

[Sysman]

the other cool way to learn unix commands is to cd into the directories /usr/bin and /usr/sbin and run the ls command

now look at all the commands and pick several per day and read the man page for them

for instance for a starter i would look at
man ls
man ifconfig
man grep & zgrep
man awk
man sed

Although Sed and Awk are redundant because you have perl installed and it has far better pattern and string manipulation

(stands back and waits for a holy war to start!)

I'd still get a grounding in Sed and Awk though in case you come across them in existing scripts and examples.

Man reading tip: If you find it hard work scrolling back and forth in the man utility , look for their web equivalents:
Mac OS X Manual Pages
Yet another way to read beautifully formatted man pages

[Sysman]

If you're interested in learning more about the MAC command line, I recommend you get a copy of Mac OS X Unix 101 Byte-Sized Projects - Adrian Mayo - Google Books

A mate of mine wrote it.

Mac OS X Unix 101 Byte-Sized Projects

Peachpit Press, Dec 15, 2005 - 614 pages
Unix is no longer someone else's OS. With Mac OS X built on top of it, Unix is becoming a household name, and more and more Mac users are ready to take it on. This book is for them! Based on a popular series of Unix tips, this book promises to deliver what most other Unix guides fail to: comprehensive tutorials and instruction on specific Unix subjects, commands, and projects, not just a handy reference guide. Arranged into 101 mini tutorials in 11 key technology areas, this book provides all the tricks, techniques, and training that you need to understand how the system works and start using it immediately. You will quickly learn the basics to working with the Unix command line as well as work on specific tutorials/exercises, including: browsing and searching the directory file-system; viewing, searching, and processing file content; using text editors; shell scripting; cool commands; and more.

Using Mac OS X is indeed a good way to learn Unix, because you can do it at your own pace.

That book looks excellent. I wish I'd come across it when it was first published.

[bobspud]

Not a bad suggestion.

(There, that surprised the sh!t out of you, didn't it?)

Yes! I just fell off my chair!

[SupremeSpod]

the other cool way to learn unix commands is to cd into the directories /usr/bin and /usr/sbin and run the ls command

now look at all the commands and pick several per day and read the man page for them

for instance for a starter i would look at
man ls
man ifconfig
man grep & zgrep
man awk
man sed

Although Sed and Awk are redundant because you have perl installed and it has far better pattern and string manipulation


(stands back and waits for a holy war to start!)

Not a bad suggestion.

(There, that surprised the sh!t out of you, didn't it?)

[bobspud]

the other cool way to learn unix commands is to cd into the directories /usr/bin and /usr/sbin and run the ls command

now look at all the commands and pick several per day and read the man page for them

for instance for a starter i would look at
man ls
man ifconfig
man grep & zgrep
man awk
man sed

Although Sed and Awk are redundant because you have perl installed and it has far better pattern and string manipulation


(stands back and waits for a holy war to start!)

[SupremeSpod]

If you're interested in learning more about the MAC command line, I recommend you get a copy of Mac OS X Unix 101 Byte-Sized Projects - Adrian Mayo - Google Books

A mate of mine wrote it.

[scooby]

In terminal:

./adb

(that's dot - slash - adb)

This is because your current directory isn't in your path, and that's probably how you want to keep it for development work.

Legend!!!

I think he means you should manually type

./abd


and not just type

abd

as you seem to say you have done in your post

Am being a little thick!! Thanks both.

[Sysman]

Yes, The "./" bit means "look in the current directory".

[Pondlife]

Guys, what am i doing wrong? am at step 6, terminal open, but when i enter the commands, it says

Scoobys-MacBook-Prolatform-tools Scooby$ abd
-bash: abd: command not found
But i can see the file:

Scooby$ ls
NOTICE.txt hboot-eng.img
aapt lib
adb
Walkthrough and guide here (all steps done and installed etc): HTC Desire Z: Rooting - CyanogenMod Wiki Firmware

Am i being stupid??

Maybe

[Sysman]

And the first time around you were typing abd instead of adb.

[chef]

I think he means you should manually type

./abd


and not just type

abd

as you seem to say you have done in your post

[scooby]

In terminal:

./adb

(that's dot - slash - adb)

This is because your current directory isn't in your path, and that's probably how you want to keep it for development work.

Not sure what you mean mate? it's a manually typed command, not a script. (sorry, new to the Mac terminal...)

corrected link: HTC Desire Z: Rooting - CyanogenMod Wiki