mgedmin

That's false: systemd handles a separate /usr just fine. It prints a warning, because most systems don't support a separate /usr partition reliably, no matter which /sbin/init they use. Consider udev scripts that rely on binaries or libraries from /usr and are triggered on hardware cold plug events, before /usr is mounted: poof, some of your hardware magically doesn't work on boot, until you re-plug. Have fun debugging it.

Could you elaborate? In what ways do you find Chromium's Inspector inferior?

OpenID doesn't replace user accounts. It replaces account passwords. A site, instead of verifying a user's password, contacts the user's OpenID provider asking them to verify the user's identity.

Instead of using the same username + password combination for all the sites on the Internet (and suffering from Gawker-like incidents), or writing down a bazillion passwords in my keyring, I use my OpenID when I want to comment on random people's blogs or sites like StackOverflow.

details?

I've found that Tesseract's accuracy was much improved when I converted my grayscale images to bitmaps with GIMP's Threshold tool.

(Those pictures were not-very-hight quality snaps of a few pages of a book taken with a 3.2 Mpix digital camera.)

I used to have a different prompt color when SSH_CONNECTION was in my environment, to distinguish local terminals from remote connections. And also root/non-root, although I didn't know about $EUID and used the less-effective $(id -u).

That was footnote #1 in the article.

When the GNOME project was founded, they looked around for a widget toolkit, and found Gtk+, that was created for GIMP at that point.

Specifically, the talk mentions that the 6502 was pipelined and could do many instructions in 2 clock cycles, while the Z80 needed at least 4.

This translates to 2x the speed at the same clock rate.

In which case why call them cars that run on water?

Could you elaborate on that?

Actually, my takeaway from this paper was exactly the opposite: if you understand how floats work, you can trust the results of floating-point calculation.

Turbo Pascal 5.5 With Objects was the first version to support OOP, IIRC. It was the version I started on, when I was 11 in 1991.

The Internet didn't reach me until about 1995 ...

Mine was

"This deterministic approach has the advantage that migration of code from one imaginary symbol to another is as easy as:

sed -e 's/k/l/' -e 's/j/k/' -e 's/i/j/' -e 's/l/i/'

provided that you restrict yourself not to use the characters i, j, k or l in identifiers, keywords or strings in the source code."

The deb conflict could be solved rather neatly by using dpkg diversions: http://www.debian.org/doc/debian-policy/ap-pkg-diversions.ht...

The content is why I googled for the Readability bookmarklet instead of just closing the browser tab.

For those of us who haven't been tracking Dropbox closely, how long did it actually take?

That was supposed to say

    >>> isPower2(2**31)
    False

mutter why no preview button on HN mutter

>>> isPower2(231) False

Floating point gets you approximate answers.

This is often the story with the latest hardware: you have to wait 6 months for it to be supported in Linux :(

When I got my T61, the current Ubuntu (breezy, IIRC) didn't run on it. I installed the alpha of the upcoming version (gutsy) and it kind of limped along; all the newer versions worked just fine out of the box.

There are various kinds of web-dev. OSX might be perfect for front-end development (Photoshop, HTML, CSS) while sucking for back-end development (3rd-party Python libraries with random C/C++/Fortran--NumPy, if I'm not mistaken--extensions).

Intel wireless cards should be a safe choice.

Broadcom wireless cards ought to be avoided at all costs (except they finally saw the light and released an open driver for their latest 802.11N, yay, but likely it's not integrated in any distro yet).

I've no idea what "ThinkPad wireless" actually is.

I love my TrackPoint -- zero-click copy (just select some text), one-click paste (middle-button).

I've a T61 and a desktop LCD next to it (Samsung 193p+). The colour profiles are noticeably different (and I grumble about lack of just-working color correction in Linux), but I don't notice any qualitative differences.

Do you prefer glossy or matte laptop screens? Thinkpads are all matte, which makes the screen easier to read in various lighting conditions (no reflections), but makes the colours less vibrant.

Not really. Most of it is lack of proper power management in the drivers, especially graphic drivers. Work is ongoing, things will improve. In a few years.

I have only about 2--2.5 hours of battery life in my T61 under Ubuntu (standard 6-cell battery, 3 years old). Luckily that's sufficient for my needs.

My T61 has both, and I use them about equally often.

My sister's Dell has a touchpad that's basically unusable.

And if you want something in the middle, get Ubuntu.

I would go with a T or X series ThinkPad with Intel graphics and Ubuntu.

I've seen a team of Python web developers with MacBook Pros. They all used Ubuntu virtual machines for the actual development.

I miss that "NO".

I expected to see "YES!", or maybe "MAYBE" in its place, but there's nothing there.

I understood that to refer to printf-style format specifiers that printk() uses. GCC can do type-checking for those: http://www.ohse.de/uwe/articles/gcc-attributes.html#func-for... -- but not if you invent your own % codes.