The BAD thing about a single PIM database, like on the old Palm devices, was if the unified database didn't support something a third-party developer wanted, they had to either have a separate app-specific database (in addition to the main one), OR sneakily encode the data in the existing database in a non-standardized way (e.g., base-64 encoded in a comment field).
Messy. Either way, migration isn't as simple as you might like.
So, Submitter says that the right-wing Chicagoboyz blog says that Congressman Culberson says that Congrassman Brady says that Congressman Capuano says that Majority Leader Pelosi says she wants to stifle free spech?
For some reason I'm afraid to visit "justballs.com" to see if they're still selling . . . um . . . balls. To play with. You know, I feel like I'm just digging deeper here.
Anyway, if not, I can only speculate as to who might have been interested in that domain.
I see your point, which is probably theoretically true to some extent, but have you actually TRIED a microdrive? They're terrible! Slow to spin up, slow to seek, slow to transfer. Less energy than regular drives, sure, but quite a bit more than flash.
I have an 8 GB MicroSDHC card that's the size of my fingernail and about as thick. Four of those would be less than 0.5 cm^3. When you have a fast mechanical drive in the same form factor, let's talk.
The U.S. patent system is authorized by Article I, Section 8 of the U.S. Constitution. That doesn't sound like something that would be reserved for "special cases."
I'm having a hard time thinking of uncopyrighted things that can be put onto a CD that might be troublesome . . . hmmm . . . confidential business records, perhaps?
There's ip.com's Legal Safeguarding Agent, which has Windows software that will automatically (or manually, if you prefer) compute a document hash for pretty much anything; the company then publishes a daily digest of hashes -- and they even get printed in hardcopy format.
I don't know the specifics of their hash algorithm, other than it's some combination of MD5 and SHA-1.
I luuuuuuuuv my Kensington Expert Mouse. But I can't get it to be fully functional in Linux.
Does anyone know the super-secret voodoo-fu incantation in xorg.conf to get all of the buttons (four around the ball, scroll wheel, and six more across the top) working? I can't find the top six buttons anywhere in/dev/input or via xev.
There don't seem to be enough of these trackballs in use for anyone to have bothered hosting a page on configuration, or at least I haven't been able to Google one up.
Having been burned by ATI drivers in both Windows and Linux, I now buy *only* Nvidia, and will continue to do so until all their talk about drivers is backed by action. Hell, even Intel's crappy integrated graphics work better in xorg than ATI.
This isn't an open-source rant either. I'd be happy with a free-as-in-beer proprietary driver that didn't suck.
I want to see results. And then, and only then, will I let myself get suckered in again.
I *intentionally* set gedit to have a different color background when run as root, so I can know at-a-glance whether (a) saving my file might break something important, or (b) if trying to perform some operation isn't having the desired effect, it's because I'm stupid and I don't have the necessary privileges.
My Ubuntu experience is to the contrary. It does subpixel rendering, but it does it poorly and without the bytecode hinting interpreter. Installing patched font rendering packages improves the situation dramatically, but that's not part of the default install.
The Apple II family had 280 x 192 graphics; each row was 40 bytes of 7 single-bit pixels. The eighth bit per byte, as others have pointed out, is a position shift: when high, it shifted each of the other seven pixels one half-pixel to the right. Because of NTSC chrominance timing, this changed the color of those pixels (usually Green->Orange, and Purple->Blue).
There were some odd consequences of this. You usually couldn't have adjacent green and orange pixels, unless they were represented in separate adjacent bytes. Each byte's seventh pixel, if the half-pixel shift was in effect, would also be truncated to a half-pixel in length if the adjacent byte to the right was unshifted. So occasionally you'd get brown when you expected orange, or dark blue when you expected blue, unless you knew of the phenomenon and compensated for it manually.
Weird stuff. I learned programming on these machines. Lots of really fun, poorly documented "features" were there to play with. I too fondly remember the Beagle Bros. tools.
I recently hosed a partition (whoops!) and had to reinstall Ubuntu, and while I was at it I decided to upgrade from Edgy to Feisty beta. I wiped clean the root and/usr partitions (/home was elsewhere), and let the installer do its thing.
When it finished, I logged in and found my desktop almost *exactly* as I left it, except for some launchers referencing applications that weren't there yet. Same background, same icons in the same places, etc. This long-time Windows user was taken aback. It was nearly painless. I installed Thunderbird from the repository with a couple of clicks and up popped all my archived email. Wonderful!
If I had known to do that dpkg --get/set thing it would have been even easier.
Vista uglier than Ubuntu? Uglier than seven-shades-of-fleshy-brownish? I've had infections that look better than Ubuntu's default desktop. I rendered fonts better than Ubuntu back when I was in kindergarten.
The BAD thing about a single PIM database, like on the old Palm devices, was if the unified database didn't support something a third-party developer wanted, they had to either have a separate app-specific database (in addition to the main one), OR sneakily encode the data in the existing database in a non-standardized way (e.g., base-64 encoded in a comment field).
Messy. Either way, migration isn't as simple as you might like.
Pentax/Samsung DSLRs can shoot in DNG, and there may also be others.
Yeah, it's Speaker Pelosi, I know that but my typin' fingers got mixed up.
So, Submitter says that the right-wing Chicagoboyz blog says that Congressman Culberson says that Congrassman Brady says that Congressman Capuano says that Majority Leader Pelosi says she wants to stifle free spech?
EVERYBODY PANIC!
En puhu suomi, olette tunteettomia clod!
For some reason I'm afraid to visit "justballs.com" to see if they're still selling . . . um . . . balls. To play with. You know, I feel like I'm just digging deeper here.
Anyway, if not, I can only speculate as to who might have been interested in that domain.
I'm going to have to look into their "application balls" -- the applications I have now are all effete and neutered.
Exactly: "No. The database contains our confidential and proprietary information."
End of conversation.
I see your point, which is probably theoretically true to some extent, but have you actually TRIED a microdrive? They're terrible! Slow to spin up, slow to seek, slow to transfer. Less energy than regular drives, sure, but quite a bit more than flash.
I have an 8 GB MicroSDHC card that's the size of my fingernail and about as thick. Four of those would be less than 0.5 cm^3. When you have a fast mechanical drive in the same form factor, let's talk.
I can provide a citation suggesting the contrary.
The U.S. patent system is authorized by Article I, Section 8 of the U.S. Constitution. That doesn't sound like something that would be reserved for "special cases."
Seriously weak. I don't see anything in these patent claims that wasn't in Xerox DPRL in the late 1990s.
I'm having a hard time thinking of uncopyrighted things that can be put onto a CD that might be troublesome . . . hmmm . . . confidential business records, perhaps?
Nah, I give up.
U.S. companies outsourcing jobs to foreign countries: bad for the U.S.
Foreign companies outsourcing jobs to the U.S.: bad for the U.S.
Well, the Predator had a sexy little fishnet get-up.
There's ip.com's Legal Safeguarding Agent, which has Windows software that will automatically (or manually, if you prefer) compute a document hash for pretty much anything; the company then publishes a daily digest of hashes -- and they even get printed in hardcopy format.
I don't know the specifics of their hash algorithm, other than it's some combination of MD5 and SHA-1.
I luuuuuuuuv my Kensington Expert Mouse. But I can't get it to be fully functional in Linux.
/dev/input or via xev.
Does anyone know the super-secret voodoo-fu incantation in xorg.conf to get all of the buttons (four around the ball, scroll wheel, and six more across the top) working? I can't find the top six buttons anywhere in
There don't seem to be enough of these trackballs in use for anyone to have bothered hosting a page on configuration, or at least I haven't been able to Google one up.
I bet this is actually the CIA providing faux-random numbers in order to gain access to sensitive data encrypted using these numbers as seeds.
Boy, this tinfoil hat sure is itchy.
Having been burned by ATI drivers in both Windows and Linux, I now buy *only* Nvidia, and will continue to do so until all their talk about drivers is backed by action. Hell, even Intel's crappy integrated graphics work better in xorg than ATI.
This isn't an open-source rant either. I'd be happy with a free-as-in-beer proprietary driver that didn't suck.
I want to see results. And then, and only then, will I let myself get suckered in again.
Call me immature but I still get a mild chuckle out of, er, expert-sex-change-dot-com and part-sex-press-dot-com. Wait, what's the other part?
For me that's a feature, not a bug.
I *intentionally* set gedit to have a different color background when run as root, so I can know at-a-glance whether (a) saving my file might break something important, or (b) if trying to perform some operation isn't having the desired effect, it's because I'm stupid and I don't have the necessary privileges.
My Ubuntu experience is to the contrary. It does subpixel rendering, but it does it poorly and without the bytecode hinting interpreter. Installing patched font rendering packages improves the situation dramatically, but that's not part of the default install.
The Apple II family had 280 x 192 graphics; each row was 40 bytes of 7 single-bit pixels. The eighth bit per byte, as others have pointed out, is a position shift: when high, it shifted each of the other seven pixels one half-pixel to the right. Because of NTSC chrominance timing, this changed the color of those pixels (usually Green->Orange, and Purple->Blue).
There were some odd consequences of this. You usually couldn't have adjacent green and orange pixels, unless they were represented in separate adjacent bytes. Each byte's seventh pixel, if the half-pixel shift was in effect, would also be truncated to a half-pixel in length if the adjacent byte to the right was unshifted. So occasionally you'd get brown when you expected orange, or dark blue when you expected blue, unless you knew of the phenomenon and compensated for it manually.
Weird stuff. I learned programming on these machines. Lots of really fun, poorly documented "features" were there to play with. I too fondly remember the Beagle Bros. tools.
Awesome. Thanks for this.
/usr partitions (/home was elsewhere), and let the installer do its thing.
I recently hosed a partition (whoops!) and had to reinstall Ubuntu, and while I was at it I decided to upgrade from Edgy to Feisty beta. I wiped clean the root and
When it finished, I logged in and found my desktop almost *exactly* as I left it, except for some launchers referencing applications that weren't there yet. Same background, same icons in the same places, etc. This long-time Windows user was taken aback. It was nearly painless. I installed Thunderbird from the repository with a couple of clicks and up popped all my archived email. Wonderful!
If I had known to do that dpkg --get/set thing it would have been even easier.
Vista uglier than Ubuntu? Uglier than seven-shades-of-fleshy-brownish? I've had infections that look better than Ubuntu's default desktop. I rendered fonts better than Ubuntu back when I was in kindergarten.
Read and internalize the Filesystem Hierarchy Standard.
It's a pretty easy read, and you'll understand where everything goes on a Linux system and why.