The morons actually used it to buy Bonzi Buddy. (and a $1500 camera on eBay)
That's how the typical CC scam/theft works. First they make a small transaction to see if the card works and then they use it shortly after for a large purchase.
The credit card companies have software that scans for this sort of a pattern, but it obviously is not foolproof.
And on a side note, how well does GPS work at that alt?
To prevent people from cheaply building their own missile guidance systems, commercial GPS receivers are limited to a maximum altitude of 60,000 feet and a maximum speed of 1000mph. Link here.
These are legal restrictions though, not technical ones. I have no idea what the "real" limits are.
So spending $x on a titanium seat bolt is usually a waste of money, in terms of performance.
What I think a lot of the gearheads that try to shave every last gram of their bike (and then ride it four times a year on sunny days) tend to forget is that the weight that really matters is the *total* weight of rider + bike + accessories.
Unless you're a super-skinny pro racer, it's much easier to lose several pounds off of that total by buying nothing and just riding more often. At least that's been my personal experience.:)
I've really noticed my speed and efficiency increase more from training and proper bike fit than any component upgrades.
5) *Steep* uphills are always going to be hard. This sorta ties into 4) but you'll find that your pain will reach a tolerable upper limit. ie: your thighs might ache the whole way up a steep hill but it never really hurts more than it did when you were at the base of the hill.
The best way to get up a long killer hill is variety: Spin for 30 seconds, then shift up a gear or two and get up out of the saddle for another 30. Repeat. This will work different muscles (including the upper body if you're doing it right) and help prevent you from burning out.
It also helps to have another rider in front of you to hunt down, or to at least pick landmarks close ahead on the road as little goals to reach.
And when you're at the top, zip down to the bottom and do it again!:)
...the -1 kills all of the current users processes. It seems the -1 option is a nice undocumented trick-- I've don't think I've seen it mentioned elsewhere...
RTFM!;) From the kill (1) manpage: -1 All processes with pid larger than 1 will be signaled.
This will send the signal (9 in this case) to all processes. Unless you're running as root, this will only kill -9 processes that are yours.
Some software gets cursory testing. I'm looking at my employer. It's like a burger - who cares if you get one pickle slice or two, as long as you get your burger?
Condiments are one thing, but if that burger isn't cooked right, I certainly care!
35mm Digital Camera does sound somewhat self-contradictory. My best guess would be a DSLR with a full-frame sensor, where the chip is the same size as a full frame of 35mm film.
On the other hand, FVWM doesn't even have desktop-icons...
And why should it? FVWM (and many other Unix window managers) follow the model that "objects" on the desktop are windows. You can have full, visible windows, and you can have minimized windows as icons. Microsoft copied this model for versions of Windows before 95 & NT4.
It all depends on what you are used to, but in my mind, this sort of a desktop metaphor makes much more sense than having files and other random objects as icons on the desktop.
I do the exact same thing. The left control key lines up perfectly with the slight bump from the joint of my little finger at the "corner" of the palm of my hand.
I can type about as fast with ctrl held down as without it by doing this.
Now try and do that where many of the clients are behind firewalls only allowing HTTP traffic through, are on slow connections, and are not permitted to install software like X Servers on their desktops.
Even better, edit/etc/inittab and change id:5:initdefault: to id:3:initdefault: for the time you're working on this.
That way, even an accidental reboot can't set your computer into a long loop of xdm restarting over and over and over and over again.
If that happens, though, most setups kill xdm if it respawns too much/too often. If you're not so lucky, turn off your monitor and ssh in from another box, or use Lilo/Grub to boot into single user mode and fix things from there.
...it's better to use Microsoft's own Terminal Services Client for PPC instead. It's significantly faster, although not cross platform, of course.
Maybe Microsoft's client isn't cross-platform, but there are alternatives: www.rdesktop.org.
Earlier versions (1.1) gave me some problems with random crashes, but 1.2 seems to be rock solid. Makes life at work a lot easier, especially with the new 'tsclient' GUI front-end for it that comes with KDE.
BTW, there is nothing like a MTB ride on freshly fallen snow in the middle of nowhere. Just doesn't get any better than that. Unless you hate the cold.;-)
Yep. The feeling of crashing and having ice cold snow and muck go up down your pants. NOTHING compares to that.;)
Work on your core strength. It'll help you with this. You can either get a gym pass and find some core-specific workouts, buy an excercise ball and use that, or just get an excercise mat and do some crunchies + other core-specific exercises at home every morning.
It'll improve your posture, shrink your belly, and make you feel good about yourself.
Of course I'm a huge hypocrit posting this as I tend to neglect this myself.
Back when I was a student, I spent a significant portion of my spare time at a computer. Even though my studies were in Computer Science, I still "enjoyed" spending a significant amount of my spare time surfing, playing games, and hacking together smaller projects of my own.
Now that I'm working, things are completely different. At work I spend a minimum of 8 hours a day sitting in front of a computer, sometimes much more. Sure I surf a bit, but most of my time is spent writing code, fixing bugs, and muttering at the damn machine that I spend most of my day struggling with.
When I get home, I still turn on my home box to check email and look up the occasional thing on line, but if I wanted to do something with a computer for more than an hour on my *own* time, I'd really have to force myself. Entire weekends go by where the computer is on for maybe 45 minutes.
What do I do with my spare time? I enjoy photography (I'm getting into digital, so that's puling me back infront of the computer a bit more), and I spend quite a bit of time with bikes (bicycles) -- both riding and tinkering. I'm planning on building a set of wheels soon...
I think if there was a way to do it in a profitable way, I'd ditch computers compeletely and open up a bike shop somewhere. Maybe that's how I'll end up "retiring".
Fair enough; we do our reviews a little differently.
We don't do very many "comprehensive" reviews with several people going over a complete feature. Instead, every single line of code that gets checked into source control MUST be reviewed by at least one other person; preferably someone familiar enough with the code to be able to see what it impacts.
For smaller changes to existing code, a diff of the "before" and "after" code is generally enough to see what was done. Bigger changes usually end up being reviewed by more than one person, just not all at once. All of this is done on the computer.
It's not perfect, but this works quite well for our situation-- and it saves us some paper as a side-effect.
except I WANT color highlighting to be printable! why is it that no programmer's editor cannot print the highlighting in color?
Could that be because most programmers don't really do that much printing of code? I haven't printed out any source since my form-feed dot matrix printer died years and years ago.
That said, pipe your code through GNU enscript to print it, and it should generate some decent syntax hilights. Also, if you're interested in publishing code with hilighting to a web page, Vim can output to html using the currently selected hilight mode.
The biggest limiting factor you're going to run into has nothing to do with core driver availability for your desktop OS, but what exactly you're trying to accomplish.
If all you want is the ability to transfer binary data between the PDA and the desktop, then any platform with a serial port should work.
If you want a bit more, you'll need a platform that the pilot-link libs + utilities can be ported to. That should give you the ability to "sync" data to and from specific programs on the Palm either by capturing raw text or the Palm's binary databases on the desktop. This may be sufficient to hack something that will work with some of the address-book/mail/PIM/whatever applications on the desktop. It will be a hack, it will be crude, but it may work. Calling this "supported" is a bit excessive though.
If you want full support for syncing the PDA with most of the major applications already found on the desktop, then you're limited to Windows + Mac, and possibly Linux if you're happy with how well the KDE or Gnome desktop applications sync with the PDA.
Of course, if you want support all for third-party apps that the user might install (either on the PDA or the desktop), then you're basically limited to just Windows.
Pick how much support you want and how much you need, and if you're not happy with where that leaves you for desktop OS choices, you'll either have to re-evaluate your needs or do a lot of hacking to get things to work.
Slashdot Mirror
Google can handle these conversions just fine... I've been using it all night to go the *other* way. :)
The morons actually used it to buy Bonzi Buddy. (and a $1500 camera on eBay)
That's how the typical CC scam/theft works. First they make a small transaction to see if the card works and then they use it shortly after for a large purchase.
The credit card companies have software that scans for this sort of a pattern, but it obviously is not foolproof.
And on a side note, how well does GPS work at that alt?
To prevent people from cheaply building their own missile guidance systems, commercial GPS receivers are limited to a maximum altitude of 60,000 feet and a maximum speed of 1000mph. Link here.
These are legal restrictions though, not technical ones. I have no idea what the "real" limits are.
So spending $x on a titanium seat bolt is usually a waste of money, in terms of performance.
:)
What I think a lot of the gearheads that try to shave every last gram of their bike (and then ride it four times a year on sunny days) tend to forget is that the weight that really matters is the *total* weight of rider + bike + accessories.
Unless you're a super-skinny pro racer, it's much easier to lose several pounds off of that total by buying nothing and just riding more often. At least that's been my personal experience.
I've really noticed my speed and efficiency increase more from training and proper bike fit than any component upgrades.
5) *Steep* uphills are always going to be hard. This sorta ties into 4) but you'll find that your pain will reach a tolerable upper limit. ie: your thighs might ache the whole way up a steep hill but it never really hurts more than it did when you were at the base of the hill.
:)
The best way to get up a long killer hill is variety: Spin for 30 seconds, then shift up a gear or two and get up out of the saddle for another 30. Repeat. This will work different muscles (including the upper body if you're doing it right) and help prevent you from burning out.
It also helps to have another rider in front of you to hunt down, or to at least pick landmarks close ahead on the road as little goals to reach.
And when you're at the top, zip down to the bottom and do it again!
Look at the numbers. Every seventh one is missing. They were probably printed in a different colour which has now faded away -- maybe red for Sundays?
It's interesting though how the weeks run top to bottom instead of left to right like they do on "our" calendars.
Feminist OS:
man bash
...the -1 kills all of the current users processes. It seems the -1 option is a nice undocumented trick-- I've don't think I've seen it mentioned elsewhere...
;) From the kill (1) manpage:
RTFM!
-1 All processes with pid larger than 1 will be signaled.
This will send the signal (9 in this case) to all processes. Unless you're running as root, this will only kill -9 processes that are yours.
Some software gets cursory testing. I'm looking at my employer. It's like a burger - who cares if you get one pickle slice or two, as long as you get your burger?
Condiments are one thing, but if that burger isn't cooked right, I certainly care!
35mm Digital Camera does sound somewhat self-contradictory. My best guess would be a DSLR with a full-frame sensor, where the chip is the same size as a full frame of 35mm film.
Not that I could afford one of those.
...found a nice elm mail sorting unit...
I prefer Pine for my email!
On the other hand, FVWM doesn't even have desktop-icons...
And why should it? FVWM (and many other Unix window managers) follow the model that "objects" on the desktop are windows. You can have full, visible windows, and you can have minimized windows as icons. Microsoft copied this model for versions of Windows before 95 & NT4.
It all depends on what you are used to, but in my mind, this sort of a desktop metaphor makes much more sense than having files and other random objects as icons on the desktop.
I do the exact same thing. The left control key lines up perfectly with the slight bump from the joint of my little finger at the "corner" of the palm of my hand.
I can type about as fast with ctrl held down as without it by doing this.
US gallon or Imperial gallon?
Now try and do that where many of the clients are behind firewalls only allowing HTTP traffic through, are on slow connections, and are not permitted to install software like X Servers on their desktops.
Step 4 seems to fade away quickly...
Even better, edit /etc/inittab and change id:5:initdefault: to id:3:initdefault: for the time you're working on this.
That way, even an accidental reboot can't set your computer into a long loop of xdm restarting over and over and over and over again.
If that happens, though, most setups kill xdm if it respawns too much/too often. If you're not so lucky, turn off your monitor and ssh in from another box, or use Lilo/Grub to boot into single user mode and fix things from there.
I think the article was a PC troll trying to point out that all-in-one Macs of the past 5 years are not video-upgradable.
And he was consipiring with other trolls, setting them up to use the "There are no games for the Mac!" line.
...it's better to use Microsoft's own Terminal Services Client for PPC instead. It's significantly faster, although not cross platform, of course.
Maybe Microsoft's client isn't cross-platform, but there are alternatives: www.rdesktop.org.
Earlier versions (1.1) gave me some problems with random crashes, but 1.2 seems to be rock solid. Makes life at work a lot easier, especially with the new 'tsclient' GUI front-end for it that comes with KDE.
Production or consumption?
BTW, there is nothing like a MTB ride on freshly fallen snow in the middle of nowhere. Just doesn't get any better than that. Unless you hate the cold.
Yep. The feeling of crashing and having ice cold snow and muck go up down your pants. NOTHING compares to that.
Work on your core strength. It'll help you with this. You can either get a gym pass and find some core-specific workouts, buy an excercise ball and use that, or just get an excercise mat and do some crunchies + other core-specific exercises at home every morning.
It'll improve your posture, shrink your belly, and make you feel good about yourself.
Of course I'm a huge hypocrit posting this as I tend to neglect this myself.
Back when I was a student, I spent a significant portion of my spare time at a computer. Even though my studies were in Computer Science, I still "enjoyed" spending a significant amount of my spare time surfing, playing games, and hacking together smaller projects of my own.
Now that I'm working, things are completely different. At work I spend a minimum of 8 hours a day sitting in front of a computer, sometimes much more. Sure I surf a bit, but most of my time is spent writing code, fixing bugs, and muttering at the damn machine that I spend most of my day struggling with.
When I get home, I still turn on my home box to check email and look up the occasional thing on line, but if I wanted to do something with a computer for more than an hour on my *own* time, I'd really have to force myself. Entire weekends go by where the computer is on for maybe 45 minutes.
What do I do with my spare time? I enjoy photography (I'm getting into digital, so that's puling me back infront of the computer a bit more), and I spend quite a bit of time with bikes (bicycles) -- both riding and tinkering. I'm planning on building a set of wheels soon...
I think if there was a way to do it in a profitable way, I'd ditch computers compeletely and open up a bike shop somewhere. Maybe that's how I'll end up "retiring".
Fair enough; we do our reviews a little differently.
We don't do very many "comprehensive" reviews with several people going over a complete feature. Instead, every single line of code that gets checked into source control MUST be reviewed by at least one other person; preferably someone familiar enough with the code to be able to see what it impacts.
For smaller changes to existing code, a diff of the "before" and "after" code is generally enough to see what was done. Bigger changes usually end up being reviewed by more than one person, just not all at once. All of this is done on the computer.
It's not perfect, but this works quite well for our situation-- and it saves us some paper as a side-effect.
except I WANT color highlighting to be printable! why is it that no programmer's editor cannot print the highlighting in color?
Could that be because most programmers don't really do that much printing of code? I haven't printed out any source since my form-feed dot matrix printer died years and years ago.
That said, pipe your code through GNU enscript to print it, and it should generate some decent syntax hilights. Also, if you're interested in publishing code with hilighting to a web page, Vim can output to html using the currently selected hilight mode.
The biggest limiting factor you're going to run into has nothing to do with core driver availability for your desktop OS, but what exactly you're trying to accomplish.
If all you want is the ability to transfer binary data between the PDA and the desktop, then any platform with a serial port should work.
If you want a bit more, you'll need a platform that the pilot-link libs + utilities can be ported to. That should give you the ability to "sync" data to and from specific programs on the Palm either by capturing raw text or the Palm's binary databases on the desktop. This may be sufficient to hack something that will work with some of the address-book/mail/PIM/whatever applications on the desktop. It will be a hack, it will be crude, but it may work. Calling this "supported" is a bit excessive though.
If you want full support for syncing the PDA with most of the major applications already found on the desktop, then you're limited to Windows + Mac, and possibly Linux if you're happy with how well the KDE or Gnome desktop applications sync with the PDA.
Of course, if you want support all for third-party apps that the user might install (either on the PDA or the desktop), then you're basically limited to just Windows.
Pick how much support you want and how much you need, and if you're not happy with where that leaves you for desktop OS choices, you'll either have to re-evaluate your needs or do a lot of hacking to get things to work.