Re: shell question / Unix guide

This WebDNA talk-list message is from

2004

It keeps the original formatting. numero = 59831
interpreted = N
texte = Unix is complicated in that there is a lot hidden in the syntax (the difference between an upper and lowercase switch for example). That's not to say you can't find simple tutorials and examples of syntax, but to understand Unix, you need to learn its "philosophy." Concepts like inherent multi-user permissions, stdin/out, piping, man pages, shell scripting etc. are not apparent from reading/using commands. However, a good book will explain them to you. I have a book at home on my desk that I will recommend to you later. I think it is called "Understanding Unix" or something like that. It is old, so it may be out of print. One important thing to remember is that Unix (at least from the POV of the average WebCatalog programmer) is a collection of small, efficient programs. You can string them together, but you need to know what switches to use and avoid for each of the programs. Some programs (sed/awk/vi/emacs/pine) have their own books, so it is hard to say there is one Unix book that is adequate unless you have a very specific goal. Additionally, one of the most important (at least to me) components is not really a program. Regular expression matching is used by many Unix programs and is a subject unto itself. Bill-----Original Message-----From: Terry Wilson Sent: Mon, 1 Nov 2004 09:29:21 -0500To: "WebDNA Talk" Subject: Re: shell question / Unix guideOkay; I've solved it by eventually figuring out a single string that worked (not a two-step workaround).Can anyone recommend a good, CONCISE Unix guide, either online or in book form, so I don't have to resort so much to trial and error?Thanks,Terry>From: Terry Wilson >Sent: Fri, 29 Oct 2004 21:42:32 -0400>To: "WebDNA Talk" >Subject: shell question>>I installed this Unix program, and can get it to work on the >desktop. But I can't figure out how to write the [shell] equivalent. >I have to enter a line, hit return, stuff displays in the terminal, >then enter the (webcat) data for something useful to happen. I >tried separating the two lines with a semicolon and a pipe, and with >a carriage return code, but it didn't do any good.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: shell question / Unix guide ( devaulw@onebox.com 2004)
Re: shell question / Unix guide ( Terry Wilson 2004)

Unix is complicated in that there is a lot hidden in the syntax (the difference between an upper and lowercase switch for example). That's not to say you can't find simple tutorials and examples of syntax, but to understand Unix, you need to learn its "philosophy." Concepts like inherent multi-user permissions, stdin/out, piping, man pages, shell scripting etc. are not apparent from reading/using commands. However, a good book will explain them to you. I have a book at home on my desk that I will recommend to you later. I think it is called "Understanding Unix" or something like that. It is old, so it may be out of print. One important thing to remember is that Unix (at least from the POV of the average WebCatalog programmer) is a collection of small, efficient programs. You can string them together, but you need to know what switches to use and avoid for each of the programs. Some programs (sed/awk/vi/emacs/pine) have their own books, so it is hard to say there is one Unix book that is adequate unless you have a very specific goal. Additionally, one of the most important (at least to me) components is not really a program. Regular expression matching is used by many Unix programs and is a subject unto itself. Bill-----Original Message-----From: Terry Wilson Sent: Mon, 1 Nov 2004 09:29:21 -0500To: "WebDNA Talk" Subject: Re: shell question / Unix guideOkay; I've solved it by eventually figuring out a single string that worked (not a two-step workaround).Can anyone recommend a good, CONCISE Unix guide, either online or in book form, so I don't have to resort so much to trial and error?Thanks,Terry>From: Terry Wilson >Sent: Fri, 29 Oct 2004 21:42:32 -0400>To: "WebDNA Talk" >Subject: shell question>>I installed this Unix program, and can get it to work on the >desktop. But I can't figure out how to write the [shell] equivalent. >I have to enter a line, hit return, stuff displays in the terminal, >then enter the (webcat) data for something useful to happen. I >tried separating the two lines with a semicolon and a pipe, and with >a carriage return code, but it didn't do any good.-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ devaulw@onebox.com

DOWNLOAD WEBDNA NOW!

Re: shell question / Unix guide

2004

Top Articles:

Related Readings: