My latest article for LWN explains (!) soft updates. The "(!)" is because soft updates are notoriously difficult to understand. If you go to a file systems conference and get people drunk, they will eventually confide to you that they don't really understand soft updates either.
Soft updates, hard problems
This is a free link; if you like the article, please consider subscribing to LWN. You'll still need an account if you want to make snide comments on the article. :)
8 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
 |
|
I recently visited the National Museum of Nuclear Science and History - or, as I knew it growing up in Albuquerque, the Atomic Museum. The museum has a brand new full size building, with enough room to display most of their catalog for the first time, but not quite enough money to do so professionally. The result is a brief, magic window in which rare artifacts are finally out on display, but you can touch them and bang on them and crawl around in them. Many of the larger items, including a disassembled B-52 bomber and many rocket engines, are simply dumped in rows in a dirt courtyard in back.
Somehow, I expected that I would traipse through the museum, looking at old photographs and brushing up on my nuclear weapons trivia, with perhaps some solemn moments of reflection in front of the reproductions of Fat Man and Little Boy. Instead, I found myself oscillating between uncontrollable sobbing and open-mouthed technological awe. It went something like this: "Wow, a cyclotron! Holy crap, the Potsdam declaration. (Muffled sob.) A real nose-cone from an ICBM, cool! Whoa, photos of ground zero at Hiroshima. (Fountain of tears.)" I went back the next day to take some original photographs with the intention of writing a thoughtful, well-researched article on my personal experience.
Unfortunately, I have discovered that I seem to know almost nothing about the history of nuclear arms testing and development - and this is from someone whose parents worked on the Strategic Defense Initiative (Reagan's "Star Wars"), who read Richard Rhodes' "The Making of the Atomic Bomb" AND "The Making of the Hydrogen Bomb", who grew up in New Mexico, home of the Manhattan Project. More accurately, I knew some of the relevant facts, but in a vague sort of manner devoid of any connection with everyday life. They were numbers of megatons in a reference book, fictional movie plots involving lost nuclear weapons, and contrived acronyms for arms reduction treaties.
But walking through the museum, I saw brass Nazi goggles and notebooks, the car that carried the Trinity bomb to the test site, a copy of the Potsdam Declaration, movies of ordinary Japanese citizens clearing rubble with hand baskets in Hiroshima and Nagasaki, and the dented shells of nuclear missiles that were, for reals, lost in a midair collision over Spain and recovered after a multi-million dollar search. (Far more were lost and never found, in or over the ocean.) I saw, and touched, and yet still almost could not believe in, the outer shell of a "Davy Crockett" miniature tactical nuke - a literal "backpack nuke," small enough that I could encircle it in my arms. I thought backpack nukes were only a theoretical possibility, and yet they were manufactured, assembly line style. I was particularly struck by how heavily the shoulder straps of the backpack were padded - a consideration so practical and down-to-earth in the face of the incomprehensible horror of the weapon itself.
And then I really got myself in trouble: I bought a copy of Michael Light's 100 Suns from the book shop. It is a collection of 100 photographs of nuclear explosions from the U.S. nuclear testing program, during the time when nuclear tests were conducted above ground. I knew, intellectually, that Enewetak and Bikini Atolls had been practically obliterated by thermonuclear bomb tests, but seeing a 20"x26" color photograph of the fireball of a 11 megaton explosion is... entirely different. And entirely different than seeing it on the computer screen - the image below has nothing like the power of that in the book.
Each photograph in this book symbolizes and encapsulates the conflicting and overpowering feelings I had in the museum: awe, excitement, and deep grief. My favorite photos are ones of the people watching the tests - most of them are bored, or matter-of-fact, but a few of the faces show the same awe and awareness that I feel when I look at the photos of the explosions, decades after the fact. The photos are accompanied by short footnotes at the end of the book, describing the technical and political circumstances and fallout (literal and figurative) of each test. And here, yet again, I learned how little I knew: that several of the thermonuclear bombs accidentally exceeded expected yield by several megatons and accidentally sickened people (How!? can something as complex as a thermonuclear bomb go wrong - and result in even greater power?? That's not how computers work!), that we actually exploded nuclear weapons above the atmosphere and were surprised by the resultant EMP (I thought physicists predicted it, not that we knocked out Hawaii's power grid by accident and worked backwards from there), that the largest nuclear explosion ever was a 50-megaton test by the Soviets in the Arctic ("test" - it was entirely for political effect), that we exploded thermonuclear bombs in the continental U.S., that U.S. soldiers were put in trenches close to bomb tests in Nevada so that they could conduct maneuvers within a few hundred feet of the smoking, radioactive craters immediately afterwards. It never even occurred to me that thousands (hundreds of thousands?) of people had witnessed nuclear tests and that I could go talk to one of these people and ask them what it was like. And I never would have guessed that I would be jealous of them, because more than likely, no human will ever witness a nuclear explosion first-hand ever again. I don't know what to do now. Maybe most people already know these things, in which case it will be difficult to communicate my awe. Maybe they don't know these things, but I won't be able to cross the boundary between intellectual knowledge, like what I knew before I went to the museum, and the intense visceral awareness that the physical objects and photos gave me. Maybe I can't do better than Michael Light's magnificent book and I should just write him a positive Amazon review. Maybe I can do better, if I use all the resources available to me on this here World Wide Web. Questions for you, dear reader: - Which of the above facts surprised you? What is the most shocking thing you know about nuclear weapons and the Cold War?
- Do you know anyone who saw a nuclear explosion in real life? Have you asked them about it? Are they willing to talk about it?
- What is the movie/book/web site/whatever about nuclear weapons that you would recommend the most?
- Any advice for me on what (if anything) to do with this project?
Thank you for reading all the way through this.
27 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
My friend Kristen complains that she can't get a good photo of me because I'm always making some kind of face. She's right, I read too much Calvin and Hobbes growing up and now automatically make a Calvin face for every photo. But I made a heroic effort last night and got this one:
I know what you are thinking - someone who wears that much jewelry can't possibly understand cryptographic hash functions! That's totally untrue - although I did have to throw out my copy of Applied Cryptography to make room for my earring collection.
18 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
Bruce Schneier predicts we'll see the first SHA-1 hash collision within a year, based on recent cryptanalytic results:
Bruce Schneier: Ever Better Cryptanalytic Results Against SHA-1
In other words, systems relying on the lack of collisions in SHA-1 (such as BitTorrent) for correct operation will start having interesting bugs in the next year, as I predicted in 2003.
I updated The code monkey's guide to cryptographic hash functions (and moved it to my own web site). I also created a summary page of my writings on cryptographic hashes, including the most up-to-date version of the "Breakout Chart" of cryptographic hash life cycles.
[Humorous hyperbole deleted since humor + intertubes = fail.] I don't think it made sense to write this paper, since I don't think anyone changed their software as a result of reading it, and it didn't have a positive effect for me personally either.
[Added so the comments don't fill up with git-related flamewars.] Git and rsync are fine, as are any hash-based systems which only allow trusted users to add data to the system. (Trusted not to deliberately add colliding inputs, that is.) BitTorrent, Venti, CAS-based shared caches, and anything else which allows potentially malicious users to add data to the system is another story.
28 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
Did anyone else watch "Mathnet" growing up? It was a show in which detectives used elementary mathematics to solve crimes. Fun, but silly - or so I thought.
As I noted in my Made-up-ness Quotient post, people are bad at making up numbers - that is, when they make up numbers, they often don't match obvious statistical patterns that appear in real numbers. Turns out that the people in charge of making up numbers for the election in Iran were also bad at it:
The probability that a fair election would produce both too few non-adjacent digits and the suspicious deviations in last-digit frequencies described earlier is less than .005. In other words, a bet that the numbers are clean is a one in two-hundred long shot.
-- The Devil Is in the Digits, Washington Post
Note to future election-stealers: Hire a statistician!
7 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
"Whatever happened to chunkfs?" Y'all can stop asking me now...
LWN article on chunkfs (the usual, pay-only for the first week, really teeny payment)
If $5/month is beyond your means, all the source data is here:
This article is by no means a research paper and I feel that keenly, but the ennui is so strong that this is the best I could do. I gave a chunkfs talk at a friend's company yesterday and I could barely bring myself to finish the slides.
Oh, yes, please consider designing your storage system for fast check and repair (see papers above for ideas). Your system will get corrupted, you will have to fix it, and you will thank yourself for thinking about in advance. :)
2 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
I am a Vernor Vinge completionist, so it was with great horror that I realized I'd somehow missed his 2004 novella, "The Cookie Monster." I managed to find the first half of "The Cookie Monster" online in Analog, but got stumped trying to find the rest of it in-print. It's apparently in back issues of Analog and some IEEE related magazine (!) - no luck finding those. I even ordered the wrong anthology on Amazon because it mentioned "The Cookie Monster" in the foreword and a different story by Vinge was in the collection. Fortunately, the author took pity on me and pointed me at the only in-print version available: Nebula Awards Showcase 2006.
After all this work, one might reasonably expect to be let down by the actual story (via the laws of Comic Effect). No such thing - this was a killer, give-you-goose-bumps story and left me with a whole new appreciation of cookies (in the software engineering sense).
Spoiler alert: Don't read the Wikipedia article on "The Cookie Monster" - you can hardly glance at it without ruining the whole plot.
4 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
Sometimes, computer programs have more insight than people. I just found NNDB and here is Keith Henson's entry:
That's right, Keith is a professional victim. Ironic, eh?
And I just love that it's so hard to find any reason why he's notable that people cite this:
In Metamagical Themas Douglas Hofstadter credits Henson's wife, Arel Lucas, for suggesting that the study of memes be called memetics.
Yep, that's my dad.
6 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
|
|
Many years ago (when I had long hair and glasses), I wrote a silly little hack - the Made-up-ness Quotient calculator - to run a simple statistical test on the numbers in company's SEC filings. The idea is very simple: when humans make up numbers, the distribution of digits in those numbers is very different from those generated by actual true data. In particular, human-generated numbers don't follow Benford's Law, whereas real financial data generally will. People thought it was cool, but I never took it public because (a) if it had a bug and people made investment decisions based on that, I would feel bad and maybe get sued, (b) the obvious thing to do is write a generic framework to perform these analyses and share the results.
Last night I opened my copy of Wired and discovered that Jesper Andersen and Toby Segaran have done exactly that with FreeRisk.org. It's still in the early stages, but it looks promising!
And with that, I am free to make my Made-up-ness Quotient calculator public again:
http://valerieaurora.org/sec.html
First person to implement a Benford's Law test on this system wins a Friends help friends use Linux shirt.
3 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
|
Chris Mason can't make it to OSCON this year, so I'm giving a talk on btrfs for him. Most open source programmers (much less users) still haven't heard of btrfs, so this seems like a good opportunity to raise awareness. Note that my personal contribution to btrfs is limited to boring Chris with unsolicited advice.
OSCON is in San Jose this year, not Portland. If you are thinking of going, you can get a 15% discount with the following code:
OS09PGM
|
1 Comment | Post A Comment | Add to Memories | Tell a Friend | Link
Recently, I've been more in love with San Francisco than usual. I'm
not sure why - perhaps the weather, perhaps moving to a neighborhood I
like more, perhaps visiting my home town - but I am in love, and will
continue to be for some time.
I love long, narrow San Francisco shops that need mirrors on the walls
so people don't feel claustrophobic. I love drinking wine on the
sidewalk while waiting for a table in a tiny French restaurant. I
love sidewalks with stairs in them. I love that you can get a better
view from the J-Church street car than from the window of any
restaurant in the city.
I love taking the California cable car to somewhere. I love
that nervous tourists sit on the benches facing outward and bored
black-clad commuters sit inside and read the Wall Street Journal. I
love that there are people who dream of being a cable car operator,
and that they get to live their dream and clatter up and down Nob Hill
all day long.
I love that Market and 4th feels like Manhattan, and that the
Embarcadero feels like nowhere else on earth.
I love the clouds and the fog and the mist on the edge of the ocean.
I love standing on Nob Hill and watching the sun turn pale and fade
away as it sets. I love the way the clouds pour endlessly over the
mountains and dissolve away into nothing before they touch the ground.
I love that you can see this every day for months when you drive down
I-280 to Mountain View.
I love wearing a coat in June. I love not sweating. I love sitting
on the grass in Dolores Park with a thousand other happy people. I
love that there's a guy who practices hula hoop for hours in the
center of the park, listening to his iPod and lost to the world.
I love brunch that doesn't even start until 11am.
I love deciding which bar to go to. I love hailing a cab when I'm
tired and knowing I'll be home in a few minutes. I love listening to
the cab driver talking to his friends on his cell phone and not having
the faintest idea what language he is speaking.
I love San Francisco.
11 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
|
|
I'm having a fabulous time on my vacation. I should do this more often!
I spent the first week visiting family and friends in New Mexico. I lived there from 1988 to 2002 in various towns - the famous Albuquerque, poky little Edgewood, and Socorro, where I went to college. I wasn't sure what I was going to do this time around; my favorite thing to do in New Mexico is hiking (White Sands (national monument AND missile range!), El Malpais, Sandia Peak) and hiking is not in the cards for me right now. But by the time I arrived, I had something scheduled for every day of the week and hardly had time to sleep, much less get bored.
I flew in Wednesday night and immediately headed out to dinner at The Artichoke Cafe with my little sister Virginia. It's always interesting to come back to NM and eat at the restaurants I thought were exceptional when I lived there; sometimes they are just exceptional for Albuquerque and sometimes they are still exceptional. By SF standards, Artichoke Cafe was okay but overpriced.
Thursday I had lunch at The Grove with Kevin, who also went to New Mexico Tech but before my time. I always mean to talk to him about nanotechnology but I can only remember one brief conversation about nanodots. While standing in line to order, we bumped in to some of Kevin's friends, despite the fact that nearly all of them were at Grand Outlandish. While the population of New Mexico is about 2 million people and Albuquerque itself contains about 600,000 of them, you'd never guess it from, e.g., how often I run into someone from my high school (400 students in a tiny town 40 miles from Albuquerque - and I only attended part-time for one year).
Thursday evening I went to sushi with my big sister Windy, her boyfriend Joel, and my nieces, Anna and Marya. We picked a restaurant at random on Central Avenue in downtown, Sushi-Hama, and somehow managed to pick the most, uh, challenged one. The "Help Wanted" sign in the window seemed innocuous enough, but we quickly found that the kitchen was closed for the night - at 8pm. I suspect someone quit at 7:45pm. No problem, the sushi bar is still open and that's what we want anyway. We ordered some drinks - Asahi and sake - and discovered in short order that our server was (a) overworked, (b) unable to distinguish the words "Asahi" and "sake." We even tried "hot sake" and still got a large (cold) Asahi. This seems like an important skill to be missing as a server in a Japanese restaurant. The sushi arrived just as we were preparing to walk out. Apparently we should have gone to Sushi King instead.
A significant portion of my weekend plans were devoted to lying around the hotel pool and drinking white wine, but the hotel pool was closed for renovation (why, oh why do they not tell you these things when you are making a reservation?). It didn't matter anyway because Albuquerque was cold, rainy, and overcast the entire weekend. I was a little relieved; figuring out how to get around Albuquerque using public transit led me to imagine/remember standing in the noonday sun at a bus stop. Heat stroke! Sunburn!
Friday we all went to the Albuquerque zoo. I find zoos terribly depressing in nearly all cases, especially when the bears and large cats are pacing back and forth on the edges of their cages. It's painful enough watching them execute the exact same steps, and turn at the exact same place each time, but then you notice the shiny spot they've worn in the wall from brushing against it a hundred thousand times... There has to be a better way than this to get kids interested in wildlife conservation. Even the famously roomy San Diego zoo makes me ill. All that being said, I was somewhat surprised at the animals that even the dinky Albuquerque zoo could afford to keep. Apparently polar bears and condors are not that difficult to acquire.
Friday night I went to Marble Brewery with Kevin and Rich and closed the place out at 2am. Marble Brewery is good, not good for New Mexico. Particular standouts were the oatmeal stout and the apricot sour. I was expecting something like Pyramid Apricot Ale, but it was even more delicate and, well, sour. The IPA was pretty good too.
Saturday I took the Rail Runner up to Santa Fe. New Mexico is trying out passenger rail again and the result is pretty fun as an excursion but not winning any awards for speed or efficiency. Some of the stops are literally less than a mile from each other. However, it's a beautiful, smooth, pleasant ride that only takes a little bit longer than driving and costs only $9 round-trip on the most expensive days. Wireless is in testing phase. And the bell to signal doors closing sounds like the Warner Brothers' roadrunner "Be-beep!" Guaranteed to send the kids into paroxysms. I met Meghan and Ben at the station and did a little shopping downtown, and then had dinner at the Second Street Brewery. Through some bizarre conjunction of aborted social plans and random meetings, we ended up with a crowd of 15-20 people and a ride home with friends I haven't seen in a while.
Sunday I swallowed my pride and made a day trip to Grand Outlandish to say hello to old friends. The clincher was that the Tynkers would be there. My sister and I sort of grew up together with the Tynkers, learning handstands and magic tricks. They took it a little bit farther, of course, given that they are a professional circus troupe now. I have very mixed feelings about the Society for Creative Anachronism. On the one hand, I got to dress up in medieval clothes, fight shoulder-to-shoulder with one thousand of my best comrades, and drink without driving. On the other hand, I spent a lot of evenings and weekends planning, researching, and making the exact right 15th century Flemish belt which, in retrospect, I wish I had spent on my career, my friends, and my family. It's hard to play in the SCA only a little bit and I quit the whole thing - twice. The last time was after I was Queen of the West - a typical day on the throne for me:
For a while, that was the picture on my home page. My friends kept asking me why I had a picture of myself frowning as a portrait; the honest truth is that I didn't realize I was frowning. That's what I looked like for most of my 20s. Fortunately, Virginia still plays in the SCA and brought all my old clothes, so all I had to do was show up, get dressed, and wander around for a few hours before heading back to my hotel room. Here we are:
I'm wearing 15th c. Flemish, she's wearing the current best interpretation of 8th c. Norse (as deduced from rotting shreds in mound burials and very low-res images from jewelry). Both are heavily modified for New Mexico weather.
Monday I headed down to Socorro, my old college town, to meet a few friends. First I drove up to South Baldy and the lightning laboratory with Patti in my Zipcar Mini. On the way down, we blew out the right front tire. No problem! I know how to change tires and even enjoy it if I'm not in a hurry - I haven't had to change a flat tire in probably 7 years now. Unfortunately, we ran into a tiny problem: locking hubs and no hub key, and we had no cell reception. Just then, New Mexico small-world-ness struck and some old college friends drove by. They gave us a ride out to cell phone range, whereupon I ascertained that Zipcar had no idea where the hub key was either. (Zipcar just started a three-car outpost at the University of New Mexico and this probably the first time they've ever had a flat tire on this car.) Many hilarious hijinks ensued, as when the poor Zipcar employee attempted to find my location using Google Maps, and then informed me tremulously that while they usually aim to have roadside assistance on-site within 45 minutes, they wouldn't be able to satisfy that standard due to the remoteness of my location.
After I turned over the car to the tow truck, we went to Frank and Lupe's El Sombrero for a later-than-expected lunch, the putative goal of my expedition to Socorro. Kscott, Bob, Cathy, and Patti and her husband joined us. I was relieved and ecstatic to find that El Sombrero is good, period, not good for New Mexico. The memory of my Frank's enchilada plate with green chile, chicken, and egg over easy will sustain me for another year. When the check came, I wrested Bob for it - literally - and won!
On the drive back to Albuquerque, the poor confused tow truck driver kept calling me trying to figure out where to take the car. "It's not my car," I said, "I don't know where to take it. Call Zipcar." But he persisted, and I eventually figured out that he was supposed to take it back to the Zipcar lot where I picked it up. "There's no garage or building or people, it's just a space in the parking lot with a sign saying 'Zipcar'." "Well, I'm here in the lot and I don't see it." "Okay, walk to the corner where you turned right, now look at the first spot..." "There's a sign here. It says, uh... 'Zipcar.'" "Yes, put it there." "Okay... What do I do with the key?" "I'll call Zipcar and they will lock it from the satellite." "Okay..." New Mexico, this is Zipcar. Zipcar, New Mexico.
On my way through security in Albuquerque Sunport (lord, how I hate cutesy airport nicknames - take that, Phoenix Skyhook) I ended up in the line for the millimeter wave scanner. No freaking way, I'm not letting TSA personnel look at me basically naked while any random traveler can look over their shoulder. I look at the X-ray scanning monitors all the time. The sign said I could opt for a pat-down instead, so I went for it. As I suspected, the screener I was waved over to just sent me through the metal detector.
All in all, a great trip, if a little exhausting.
2 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
I've been noodling on the unioning file system problem for a few months now, the results of which are summarized here:
Unioning file systems for Linux
Yesterday, Jan Blunck posted his latest union mount patchset with my implementation of readdir():
VFS based Union Mount (V3)
The basic idea is that on the first readdir() of a unioned directory, we copy up all the visible entries from lower down in the file system into the topmost directory as a special kind of directory entry called a "fallthru." A fallthru tells the VFS to look for that entry in a lower level of the union. Then we can use the native readdir() implementation of the topmost file system and everything Just Works.
This patch set isn't ready for merging yet, but I think it is on the right track. If you're interested in working on it too, here are a few of the known problems:
- We check to see if a directory is logically empty by calling vfs_readdir() from the rmdir() code. This is an icky interface violation. We could instead call union_copyup_dir() directly.
- readdir() only works if the topmost file system is writable, so readdir() won't work on unions of all read-only file systems. We can mount a tmpfs layer on top to support this, but it would be nice if it were transparent to the user. Also, it would be nice if the tmpfs layer could kick out dentries created for readdir() when they are not being used.
- copyup on write only works for regular files and directories. block/char/fifo etc. don't work (and maybe shouldn't work?).
- symlinks are untested.
- The locking scheme currently allows for several potential deadlocks, mainly because we acquire locks in union stack order, and file systems can be in different orders in different union stacks. The key to this might be the fact that writeable file systems are only allowed on the top layer of the union; all the other layers are read-only.
If you want to work on any of these issues, talk to Jan Blunck first and see if he's already solved them. (I am going on vacation for two weeks starting tomorrow and he's the best person to talk to in any case.)
Post A Comment | Add to Memories | Tell a Friend | Link
The requirements for correctly supporting readdir() are convoluted and arcane. I can usually reason them out from first principles given a few minutes, but I'd much rather just read Ted T'so's excellent summary, posted to the btrfs list in January:
Requirements to support readdir()
In particular, the requirement for a 32-bit cookie that is stable across reboots comes directly from NFSv2 readdir(). Otherwise, readdir()/telldir()/seekdir() only has to be stable between open() and close() on that fd. If you don't support NFSv2 exports, then supporting readdir() on your file system becomes quite a bit easier (something we are specifying for union mounts - hey, maybe I should post about that...).
Post A Comment | Add to Memories | Tell a Friend | Link
I have always wanted to write (English) more; turns out that in order to write you need something called "time." I have finally succeeded in carving out time to write (thank you, Red Hat) and now I have the luxury of wondering what to write. I have my own ideas, but perhaps you, gentle reader, have some thoughts on the matter?
23 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
I love this shirt and I'm trying to remember who I saw wearing it. If it was you, send me an email!
(You can purchase the shirt at Zareason, a Linux hardware shop.)
5 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
Andreas Dilger recently posted the Lustre test programs to check that block devices and ext4 file systems behave properly beyond the 32-bit boundary. Finding these programs is a bit of a pain, so I'm posting them here directly for my use and hopefully that of others. Both programs compile just fine without any fancy arguments - gcc -Wall -o thingy thingy.c - and are GPL.
64-bit device tester
64-bit ext4 file system tester
And if you are a brave, hardy soul, you can download my 64-bit e2fsprogs and create a 64-bit ext4 file system. Nick Dokos of HP has put in a lot of effort to test and fix bugs over the last month. The latest is in the shared-64bit branch.
git://git.kernel.org/pub/scm/fs/ext2/val/e2fsprogs.git
Don't put data you care about on it!
Post A Comment | Add to Memories | Tell a Friend | Link
Update your Val Spotting Guide with this nostril-riffic pic:
At the end of June, I am moving a couple of miles, from the Mission to SOMA. My new place is near 2nd and Harrison. If you're in the neighborhood, let's hang out.
I am visiting New Mexico over Memorial Day weekend. My hotel is in Albuquerque and I'll be making day trips from there. If you're in the area, let's hang out.
I am going to try working in the Red Hat office in Mountain View three days a week. If you're in Mountain View, let's also hang out.
7 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
While discussing the recent Sun buyout drama, I tried to describe the Sun Strategy Spinner to a few people but failed to capture the full awesomeness of it all. Fortunately, it's been updated and you can find it at the top of the latest Ars Technica article:
6 Comments | Post A Comment | Add to Memories | Tell a Friend | Link
Okay, I'm ready to take the training wheels off - my Twitter feed is now public. Follow away. (My apologies if you tried to follow earlier and were denied.)
FYI, I'm using Twitterberry with notifications turned on only for direct messages and replies.
Post A Comment | Add to Memories | Tell a Friend | Link
|
![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
