Re: Unix guide

This WebDNA talk-list message is from

2004


It keeps the original formatting.
numero = 59841
interpreted = N
texte = The book I have is "A Practical Guide to Understanding the Unix System" by Sobell. This is a great intro to Unix principles but it is an older book. I don't know the one you mentioned, but it may be OK. I think there is another one by Greenlaw that is supposed to be good. Bill -----Original Message----- From: Terry Wilson Sent: Tue, 2 Nov 2004 06:44:31 -0500 To: "WebDNA Talk" Subject: Re: Unix guide 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? Terry At 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/ ------------------------------------------------------------- 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:

    
  1. Re: Unix Guide ( Terry Wilson 2004)
  2. Re: Unix guide ( devaulw@onebox.com 2004)
  3. Re: Unix guide ( Terry Wilson 2004)
  4. Re: shell question / Unix guide ( devaulw@onebox.com 2004)
  5. Re: shell question / Unix guide ( Terry Wilson 2004)
The book I have is "A Practical Guide to Understanding the Unix System" by Sobell. This is a great intro to Unix principles but it is an older book. I don't know the one you mentioned, but it may be OK. I think there is another one by Greenlaw that is supposed to be good. Bill -----Original Message----- From: Terry Wilson Sent: Tue, 2 Nov 2004 06:44:31 -0500 To: "WebDNA Talk" Subject: Re: Unix guide 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? Terry At 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/ ------------------------------------------------------------- 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!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Zipcodes (1998) Speed Optimization - Mac (1997) FORMS: Returning a specific page (1997) [ShowNext] feature in 2.0 (1997) [WebDNA] Installing WebDNA 7 on OSX Mavericks Server - Instructions (2014) Newbie Help Needed (1998) Typhoon Rev. and PCS store problems (1999) GrandTotal not right (1997) need help please (1997) Great product and great job ! (1997) Three new problems, maybe a fourth (1997) syntax question, not in online refernce (1997) No luck with taxes (1997) multi-paragraph fields (1997) Problems adding stuff to the shopping cart. (1997) two unique banners on one page (1997) WCS Newbie question (1997) bug in [SendMail] (1997) [BULK] [WebDNA] Ubuntu 16.04 LTS & WebDNA (2017) $Replace with [founditems] (1997)