A reader writes:
So, I’m partway through your book, and I want to check on hard links. When you say it creates another door to the same body of data, is that literally true? For example, if all I have in my ./Documents directory is 001.doc (size 512K), and I hard link as hardlink.doc then run ls, do I see A or B?
A) 001.doc 512K
hardlink.doc 512K
total 1024KB) 001.doc 512K
hardlink.doc 512K
total 512KIf it’s not B, I’m not sure what the point is, other than maybe not changing the timestamp.
A reader writes:
Every *nix implementation is different. But I’m seeing some some shared behavior between HPUX and Solaris with script #52 Killing Processes by Name. The problem is that the script is trying to kill the “tty” name, instead of the pid.
Wish I understood the following line better so I could make it grab the right columns. :-\
pids=$(ps cu -U $user | awk “/ $1$/ { print \$2 }”)
A reader writes:
First, thanks for writing Wicked Cool Shell Scripts. I’ve found them quite useful and I’ve learned many things from those scripts.
I just have a question and I was wondering if you could point me in the right direction.I’m trying to write a shell script that will pull the top-level directories out of a list of file paths, example:
list of files:
/usr/local/test
/usr/bin/test
/opt/Tivoli/dat
/opt/lib/test
/tmp/files/test
/tmp/local/testOutput after script:
/usr
/opt
/tmp
After hearing a lot about it, I went over to SitePoint and read an interesting article by a “search engine optimization expert” wherein he enumerates his list of fifteen of the most egregious techniques by which companies and individuals “spam” the search engines. What’s search engine spam, you ask? It’s using inappropriate and deceitful methods of manipulating the HTML or other elements of a site to generate a higher ranking than the site would otherwise be granted by a typical search engine relevance calculation.
A reader writes in with the following note:
I’ve just picked up your book Wicked Cool Shell Scripts, and there are a lot of nifty things in
it. I too have accumulated a lot of things generally in small scripts
or more frequently in bourne/bash functions. I was particularly tickled
to see a lot of very similar code, one such that jumped out at me was
your gmk function in one script (I called mine kmg).Would you be interested in some constructive criticism?
In script #52 Killing Processes by Name, I think that instead of:
awk “/ $1$/{ print \$2 }”
you might consider using
awk “$NF==”$1″ { print \$2 }”That way, you’re not dependent on whitespace.
A reader sent me the following question:
“I recently purchased your book Creating Cool Websites with html, xhtml, and css. When I arrived to chapter 2 and you said to go to note pad, I followed your instuctions and I couldn’t find it. So I went to run and typed in notepad and BAM! it pulled up.
You say to save it to your desktop, if I do that will the program always run from there? Should I seek out a tech to move the program to where you said I should of found it. “
In a rather lengthy email message, a reader writes to me that:
I am following your book Creating Cool Web Sites with HTML, XHTML and CSS and am trying to protect a subdirectory on my website. The following is the .htaccess code
AuthUserFile /www.bvg.us/uswholesale/uspasswords/passwords.txt AuthGroupFile /dev/null AuthName "Please enter your login name and password" AuthType Basic <Limit GET> require user weiyang require user annawei </Limit>The “passwords.txt” reads
user weiyang:wy user annawei:awBy doing so, I can get the “log in” box but can not login with the info that I set. Could you help me on this?
I have received a number of queries from people in the Unix/Linux community asking for the details of ownership and copyright for the scripts included in my best-selling Wicked Cool Shell Scripts. When I first started programming and distributing my works online (in the early 1980’s) no-one really worried about any of that and if the original author’s name stayed intact, we’d think that was a wonderful thing.
