Re: Unix guide

This WebDNA talk-list message is from

2004

It keeps the original formatting. numero = 59840
interpreted = N
texte = Thanks Bill. Your comments in and of themselves were helpful. When I try out new programs I go through their own readme.txt files very carefully, and now realizing they should be considered independently I won't assume something I know about one program will apply to another one. Sometimes it's hard for me to know what the readme.txt is talking about, so I need to get down the lingo, like the concept of switches you mention. I found "Understanding Unix" at half.com.... a black book with a red X standing on an orange disk... that the one?TerryAt 2:00 AM -0800 11/2/04, devaulw@onebox.com Talk wrote:>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 -0500>To: "WebDNA Talk" >Subject: Re: shell question / Unix guide>>Okay; 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,-------------------------------------------------------------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: Unix Guide ( Terry Wilson 2004)
Re: Unix guide ( devaulw@onebox.com 2004)
Re: Unix guide ( Terry Wilson 2004)
Re: shell question / Unix guide ( devaulw@onebox.com 2004)
Re: shell question / Unix guide ( Terry Wilson 2004)

Thanks Bill. Your comments in and of themselves were helpful. When I try out new programs I go through their own readme.txt files very carefully, and now realizing they should be considered independently I won't assume something I know about one program will apply to another one. Sometimes it's hard for me to know what the readme.txt is talking about, so I need to get down the lingo, like the concept of switches you mention. I found "Understanding Unix" at half.com.... a black book with a red X standing on an orange disk... that the one?TerryAt 2:00 AM -0800 11/2/04, devaulw@onebox.com Talk wrote:>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 -0500>To: "WebDNA Talk" >Subject: Re: shell question / Unix guide>>Okay; 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,-------------------------------------------------------------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/ Terry Wilson

DOWNLOAD WEBDNA NOW!

Re: Unix guide

2004

Top Articles:

Related Readings: