Email Address Password
Remember Me

Or Create a (Free) Account.
2004JanFebMarAprMayJunJul Aug Sep Oct Nov Dec
2005 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
2006 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Oct Oct

Wed 26th Oct 2011 @ 00:16 2011: Shell Scripting book update

It's not often, but I occasionally look at the figures that Amazon give on book sales. These figures are updated hourly, and this is a book which sells by the month and year, rather than by the hour, so there is nothing really useful to be gleaned. But still, it's nice to see one's own book at the top of the "Linux & Unix Programming" and "Shell Scripting & Programming" categories at the same time.

Shell Scripting book

Post a Comment               

Tue 4th Oct 2011 @ 23:42 2011: Not Responding

Yet another "note to self" blog post - when my dual-core single CPU laptop fails to boot Linux with a message "Not responding" (a message you'll be lucky to actually read, as it immediately reboots), adding "maxcpus=1" to the cmdline has always fixed it for me.

I'm not entirely sure what it says about the state of the CPU though!

Under grub2, press "e" at the Grub menu (press "p" first and enter the password if Grub is password-protected) then go down to the kernel line, add "maxcpus=1" at any point (putting it at the end is safest) then press Control and X (^X) to boot

Post a Comment               

Tue 4th Oct 2011 @ 21:14 2011: Free 24-part lock-picking course on YouTube

Lockpicking seems to be something that fascinates a lot of technical people. Schuyler Towne offers a free 24-part course on YouTube. I must get around to watching it some time

Post a Comment               

Tue 4th Oct 2011 @ 20:57 2011: Sorry for the silence

Sorry for the blog silence; a move to a new server meant that some of my PHP broke, and I haven't got around to fixing it until now. It should all be working fine again now, so you've got my boring comments back again, I'm afraid!

Post a Comment               

Tue 4th Oct 2011 @ 20:55 2011: tcpdump tip

When ssh'd into a remote server, running tcpdump can be counterproductive - the output itself creates more traffic as it sends it back to you, which it then has to report on, feeding a vicious circle as you create more and more uninteresting traffic.

If you are looking for port 80 only, you can specify the port:

# tcpdump port 80

However, if you want everything, but are happy to exclude all ssh traffic, this can be a useful syntax. The backslash (\!) is necessary to escape the exclamation mark from the shell:

# tcpdump port \!22

Post a Comment               

Steve's urandom blog
Share on Twitter Share on Facebook Share on LinkedIn Share on Share on StumbleUpon
My Shell Scripting Book:
    Shell Scripting, Expert Recipes for Linux, Bash and more
is available online and from all good booksellers: