Back to top

Technology

Broadly defined "technology" e.g. software, water pumps

MySQL - Drop all Tables in a Database Using a Single Command Line Command

Let's say you need to drop all tables in a mysql database. How do you do that?

You could use a gui, but that's not fun.

You're a shell jockey so you want a commandline:

 mysql -u uname dbname -e "show tables" | grep -v Tables_in | grep -v "+" | \
gawk '{print "drop table " $1 ";"}' | mysql -u uname dbname

(that's all one line, but if I do it as a line then it screws up my theme - go figure).

This assumes that you are running in passwordless mode. See "man mysql" for tips on how to pass in passwords in another manner.

What this does is

Category: 
People Involved: 
timeline: 

radio spectrum in trouble - sign the moveon petition now! or not.

I was recently sent a link to this petition from MoveOn.org and asked what I thought about it. I'll quote a section from the petition:

Use the public airwaves for the public good, or turn them over to big companies who will stifle competition, innovation, and the wireless Internet revolution. We're urging the FCC to mandate that whoever wins the auction cannot stifle competition and innovation.

First, I generally dislike MoveOn.org because they water down the issue into platitudes so that you have to agree with their position in the petition. Who wants to support anticompetitive regulations? Who wants to stifle innovation? Obviously I should be in favor of their position, right? But they water down the issue in such a way that you can't research it either the issue or their actual position. What is the issue? What is their actual position on the issue?

I don't know so, here's what I have to say in broader terms.

Researching Geek Topics and Spectrum Use

When it comes to geek topics, the place that has the best articles, news, and commentary weighing boths sides is generally slashdot. I went to their page for Communications Articles which shows this was discussed exactly zero times over the last 30 articles which goes back to December of 2006. So, not discussed at all. MoveOn doesn't scoop slashdot. So this is apparently unimportant to slashdot which means I don't care either.

Category: 
People Involved: 
timeline: 

linux screen cheat sheet

Let's say that you are running a command on a linux shell and it's taking a long time. Further, you need to disconnect your session to get on the bus or your session gets disconnected because your net connection is flakey.

Screen to the rescue

Imagine if you could just disconnect from your shell session and then reconnect. Well, you can :)

People Involved: 
timeline: 

denver postgresql training

I recently attended a training that Kevin Kempter hosted. It was a really great two night session aimed at experienced DBAs/Developers so that they could learn PostgreSQL. Kevin has a lot of experience with postgres and wanted to help share that experience with other folks. He's finding a growing need for PgSQL developers in the Denver area and wants to build up a user group and network here so that companies deciding whether to use PostgreSQL or not will see an available local talent pool here in Colorado.

People Involved: 
timeline: 
Location: 

RFC - Security Bounties in Open Source

The other day I broached the idea of a security bounty in the Drupal project. I had first heard about this concept from the Mozilla Foundation's Security Bug Bounty which appears to be the most famous of these.

Why Security Bug Bounty's are a good idea

This is pretty simple:

  1. It provides at least some motivation for folks to actually look at the code and find security bugs making the software more secure.
  2. More folks looking at the code is always a good thing.
  3. Just the concept and the existence of the program reminds people that we take security seriously, and informs them of the proper way to report a bug.
  4. In the case of the Drupal Association - which can't make decisions about the code based about the statutes (en pdf) (more formats/languages).

Generalized Security Bug Bounty System

This concept seems to me like it could be generalized for any software project. Here are the rules I came up with, based upon the Mozilla foundation's rules.

<

ul>

  • Security bug must be original and previously unreported.
  • Security bug must be a remote exploit.
  • Security bug is present in the most recent version of the Mozilla Suite, Firefox, and/or Thunderbird, as released by the Mozilla Foundation.
  • Security bugs in or caused by additional 3rd-party software (e.g. Java, plugins, extensions) are excluded from the Bug Bounty program.
  • Submitter must not be the author of the buggy code nor otherwise involved in its contribution to the project (such as by providing check-in reviews).
  • Employees of the project (if applicable) are ineligible.
  • If multiple people report the bug the reward will be split among them equally.
  • People Involved: 
    timeline: 

    Pages

    Subscribe to RSS - Technology