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.
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
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
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!
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