Guest theeldergeek Posted February 22, 2010 Posted February 22, 2010 Trying to follow the instructions at deploystudio - Verifying DNS Integrity and I'm falling at the first hurdle. If I put in % hostname I get -bash: fg: %: no such job My head hurts
LosOjos Posted February 22, 2010 Posted February 22, 2010 (edited) Ignore the "%" hostname EDIT: just as a matter of interest, I see "%" before linux commands on a lot of websites, anybody know why this is used? I always presumed it was just to shorthand for terminal Edited February 22, 2010 by LosOjos Additional Info
mac_shinobi Posted February 22, 2010 Posted February 22, 2010 why have they got the % symbols in the instructions
LosOjos Posted February 22, 2010 Posted February 22, 2010 Also, I can't see on my linux netbook what the result would be as I'm not connected to a server, but I think you need to run hostname -f to get the FQDN
DMcCoy Posted February 22, 2010 Posted February 22, 2010 Different shells have different prompts. It's like the > on windows command line. Understanding Shell Prompts - O'Reilly Media
mac_shinobi Posted February 22, 2010 Posted February 22, 2010 Different shells have different prompts. It's like the > on windows command line. Understanding Shell Prompts - O'Reilly Media not to hi jack this thread but is there a good site that explains the difference between the shells and which is better to use or what they are better at etc etc
AntonioRocco Posted February 22, 2010 Posted February 22, 2010 (edited) Hi @ macshinobi DMCoy is on the right lines. For a brief explanation and possibly some links: Shell Programming! If you want to learn Shell Scripting this is a good place to start: Advanced Bash-Scripting Guide I've not read it all (it's rather large) but I would not be surprised if the Tee-Cee and Korn shells are in there somewhere? Different shells have different strengths and are good at achieving certain things depending on what you want. The Bourne Again Shell (bash) which is predominantly used on OSX is a good all rounder but it's not the only shell available. For example keying in "tcsh" (minus quotes) in Terminal will put you in the Tee-Cee Shell. You know when you're in tcsh because the percent sign will follow the username. The bash shell uses the dollar sign. Keying "ksh" presents the dollar sign and nothing else. Keying "bash" gets you back again. To find out more from the command line itself simply launch Terminal and key in: man bash (for the Bourne Again Shell) man tcsh (for the Tee-Cee Shell) man ksh (for the Korn Shell) No doubt there are plenty of other shells/programming environments (the POSIX World is vast) which may or may not be available in OSX. Half the "fun" is discovering them for yourself. A fairly general rule of thumb is if there is a downloadable binary available you should be able to "make/compile" on OSX. Macports and fink are two examples. This would also be true of Linux. A good resource for UNIX on OSX is here: Apple - Support - Discussions - Unix Antonio Rocco (ACSA) Edited February 22, 2010 by AntonioRocco
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now