I once saw a page that said ``this page best viewed by coming over to my office and looking at it on my monitor.'' You don't often see honesty like that.
By the way, did you know that your apple laptop can be turned into a dumb firewire drive by holding down the 'T' key when booting?
It will boot up and show a big firewire logo on the screen, and then if you plug it into a second apple, the other system will mount the first machine's hard disk. (kind of a security problem actually)
I wonder if you could put a windows partition on the apple's hard disk and access it with the intel laptop...
You know, there are a lot of practical disadvantages to threads.
Threads can be a lot harder to debug. I don't think gdb really understands threads very well. Other application support is spotty as well. Actually, Solaris has pretty good thread-aware debugging and has good threading tools like deadlock tools.
People who write threaded applications also seem to think it makes life easier. They say - I'll just have a read thread and a write thread and a processing thread....except that the read thread is usually written with blocking reads and it's hard to recover when you want to kick that thread out of the read to terminate or restart cleanly. So people end up using select() anyway. And then they still need interprocess communication to kick the read thread out of the select sometimes.
I think you have to be a better programmer to use threads - you have to be aware of the normal issues plus all the threading issues. Avoid cancelling threads. You have to be very clear how you do signal handling. You have to lock all your data. Don't use fork+exec AND threads. You have to keep track of multiple threads, especially during error conditions.
And you have to be a much better debugger to debug someone else's threaded application.
Not that there aren't good applications for threads, just be aware of the complications.
Although you probably wouldn't want to control your washer, dryer, toaster or microwave through the internet, there is one reason it would be cool to have them connected...
Notification
It would be great to know when:
Your wash load is done.
Your washer has stopped, unbalanced load
The clothes in the dryer are ready. (repeat until clothes removed)
garage door is open
Refrigerator temperature high - door open To a lesser extent:
Your toaster has popped
Garbage disposal has run for more than 1 minute
The food in the microwave is ready and has cooled for a while Some appliances that would be nice to control are:
Thermostat, especially to know when somebody's home and when NOBODY is home
water heater on/off
Just the fridge door open could pay for the entire sensor (ever lost a fridge full of food?)
So notification is the real key here, not toasting bread through the internet.
I kind of avoided this whole issue. Self-employment can be a real hassle.
I found a job, then found a firm that would handle my contract billing and pay me W2. That worked out great. I billed at one rate, they kept 14% (and paid their part of the taxes out of it) and I got the remainder W2. I added medical for $1/hour. I would have had to give up a little more percent if I hadn't gotten the job. This worked out fine for many years.
Other contract firms usually took a minimum of 30% and up for the privilege of employment through them.
Yeah, but this breaks the tight coupling possible in a browser. For instance, with mozilla, you can right-click on an image and say "block images from this server". Of course, this sucks and should be expanded to give more control (like block from this server, block from this domain, look at the url and create your own regex, etc.)
Slashdot Mirror
Must be the AMD.
It's common knowledge that for hard drives, temperature and drive life are inversely proportional.
Just keep track of what machines can read what format disks.
TCP/IP removes this problem, but the data access will be slower.
This is very useful for Macs (just remember to drag the disk to the trash before unplugging!)
However, for his other systems, I don't believe they would be able to read the disk since it's in apple's HFS format.
"This is Head Radio... a Love Media station.
...300 TV stations...
...4 networks...
...3 satellites...
...10 senators... Hello!, Hello!!, Hello!!"
"Just one of 900 radio stations...
Sorry, I stand corrected. I was looking at the retail channel model for $1699. duh.
I was thinking it was kind of expensive since you could get a dual 867 for $50 more, but it has a monitor, etc...
OLD = DUAL 867's
NEW = SINGLE 1Ghz
Too bad GPS receivers don't work indoors... ;(
I think this would make the reminders somewhat less than reliable.
get a street bike
get a dirt bike
get a jetski
get a surfboard (and a wetsuit)
get a snowboard or skiis
forget bug repellant
get some sunblock
get some hiking boots
go to Fry's...etc...
By the way, did you know that your apple laptop can be turned into a dumb firewire drive by holding down the 'T' key when booting?
It will boot up and show a big firewire logo on the screen, and then if you plug it into a second apple, the other system will mount the first machine's hard disk. (kind of a security problem actually)
I wonder if you could put a windows partition on the apple's hard disk and access it with the intel laptop...
You know, there are a lot of practical disadvantages to threads.
...except that the read thread is usually written with blocking reads and it's hard to recover when you want to kick that thread out of the read to terminate or restart cleanly.
Threads can be a lot harder to debug.
I don't think gdb really understands threads very well. Other application support is spotty as well. Actually, Solaris has pretty good thread-aware debugging and has good threading tools like deadlock tools.
People who write threaded applications also seem to think it makes life easier. They say - I'll just have a read thread and a write thread and a processing thread.
So people end up using select() anyway. And then they still need interprocess communication to kick the read thread out of the select sometimes.
I think you have to be a better programmer to use threads - you have to be aware of the normal issues plus all the threading issues. Avoid cancelling threads. You have to be very clear how you do signal handling. You have to lock all your data. Don't use fork+exec AND threads. You have to keep track of multiple threads, especially during error conditions.
And you have to be a much better debugger to debug someone else's threaded application.
Not that there aren't good applications for threads, just be aware of the complications.
Maybe the rappers could hold walkie talkies...
... ;)
Worked for E.T.
(the E.T. re-release digitally changed all the guns the police were holding into walkie-talkies...)
I believe THIS is what you would get...
This is
The Best Switch Ad
of all...
Reminds me of that fake advertisement during the wierd al movie "UHF"...
SPATULA CITY!!
Nothing but spatulas!
Uh oh.
The gig is up.
Better sell my NASA stock and head on down to mexico.
Notification
It would be great to know when:
Your wash load is done.
Your washer has stopped, unbalanced load
The clothes in the dryer are ready. (repeat until clothes removed)
garage door is open
Refrigerator temperature high - door open
To a lesser extent:
Your toaster has popped
Garbage disposal has run for more than 1 minute
The food in the microwave is ready and has cooled for a while
Some appliances that would be nice to control are:
Thermostat, especially to know when somebody's home and when NOBODY is home
water heater on/off
Just the fridge door open could pay for the entire sensor (ever lost a fridge full of food?)
So notification is the real key here, not toasting bread through the internet.
I think these moderation totals on this post are almost (but not quite) as funny as the article...
I've never seen a total of 28
Well, you can understand a dog too...
With this Dog Translator you can interpret your dog's barking.
Sorry, body language isn't interpreted.
I kind of avoided this whole issue. Self-employment can be a real hassle.
I found a job, then found a firm that would handle my contract billing and pay me W2. That worked out great. I billed at one rate, they kept 14% (and paid their part of the taxes out of it) and I got the remainder W2. I added medical for $1/hour. I would have had to give up a little more percent if I hadn't gotten the job. This worked out fine for many years.
Other contract firms usually took a minimum of 30% and up for the privilege of employment through them.
Yeah, but this breaks the tight coupling possible in a browser. For instance, with mozilla, you can right-click on an image and say "block images from this server". Of course, this sucks and should be expanded to give more control (like block from this server, block from this domain, look at the url and create your own regex, etc.)
I think this would be a good idea and might help more than in just checking for cheaters.
You wonder what more eyeballs would have done with this fiasco analyzed by Bruce Tognazzini.
Whoops, I breezed over that qualification for densest server.
I stand corrected.
I saw a 4-mainboard in a 1u rack-mount server at linuxworld several years ago. That's the same density, nut earlier...
I know Kingstar used to have pretty high-density systems that would mount back-to-back.