I remember learning to write software for OS/2 back in the early 90's. Multi-threaded programming was *the* model there, and had it been more popular, it would be pretty much standard practice today, making scaling to multiple cores pretty effortless, I'd think. It's a shame that the single-threaded model became so ingrained in everything, including linux. For an example that comes to mind, why do I need to wait for my mail program to download all headers from the IMAP server before I can compose a new message on initial startup? Same with a lot of things in firefox.
And you then need to expend the energy to empty the tube, or energy to shove the ship down. You've saved nothing, and lost efficiency in the energy required to stage the rocket under water.
I'm also confident that they could build those shoe-zappy thingies into the floor and save us at least that much trouble. I hate to be gratuitously cynical, but I have to wonder how much of this is just to be seen doing something security-ish.
Amen. I tell this to my friends as well. I'll soon be getting some beer, and maybe a nice dinner from a girl I have done a few bike rides with b/c she needs some help.
Giving his password to his secretary would seem a security policy violation to me. Who knows what type of classified information that secretary was now perusing. This type of thing should be brought up to the other chiefs and the legal department.
Rebooting the computer will, in fact, resolve many things. For a while. Ultimately, most problems will recur.
Then the reboot resolved nothing. It just hid the symptoms so it took you that much longer to *actually* fix the problem. On my *nix boxes, a reboot is absolutely the last thing I ever do to try to resolve a problem. Doubly so for high-visibility production stuff (mail servers, firewalls, etc). Syslogs are your friend.
Then again, the 'event viewer' in windows is pretty much useless. Without good information, fixing a problem becomes nearly impossible, so the SOP for windows boxes is to reboot often to mask the real problem in order to do some sort of work with the system before it goes legs up again.
My father is actually a great user security-wise, b/c he is afraid of doing something that will infect him with nefarious software so he actually does practice very good computer hygiene as a user to the point that antivirus software really doesn't do anything but waste cpu cycles on his computer. But, he does it to a fault, and needs to not be so afraid to explore.
He has definitely gotten better since teaching him how to listen to internet streams, and now that he bought himself a sansa mp3 player, I was even able to teach him how to rip all of his CDs so that he can listen on the road. In addition, he's an awesome photographer, and recently bought himself a digital SLR (he had his own darkroom in the 70's), and has taught himself how to edit and publish his work. Take something a user loves, and teach them how to use a computer to do it better, and you usually have no problems getting them to dive in and actually learn things on their own.
The funny tech support story is that last year I had given him an FM transmitter so that he can listen to his music easily in the main room on the main stereo while playing from the computer in the computer room.
Over thanksgiving this year, he came to me all perplexed as to why it sounded horrible. He had tried everything, including checking all wires, and changing the antenna's location. I took a look, and changed the channel on the transmitter to match the station on the stereo:) Apparently he had accidentally changed it when he bumped into it or something.
Having many years experience being both a sysadmin and support person, I've learned to always look at the simple solution first. It's probably the right one and also the one everyone else overlooked. Dad now knows this basic troubleshooting principle as well:)
It always happens to me when going through a spectacular crash, either on my bike or my snowboard. Like that time I hit a pile of snow that had solidified into ice while dropping in to a local drainage area at the grocery store. That split second as soon as I went over the lip and saw what was about to happen was very long, as I can totally remember thinking "This is gonna hurt" right before the front wheel hit and my fork snapped off.
This year I'm thinking of getting jerseys made and leading a team at the 24 hours of big bear as "Team V1@gra". Our motto, also on the jerseys, will be "Ride Hard"
Yup. He had no right to do anything to the guy. Now, if it was his own g/f, son, daughter, wife that this guy raped? THAT I could understand killing the fscker over. I'd likely do the same.
That said, maybe it should be legal to kill exactly one person in your lifetime without consequence (well, other than that person's relatives coming after you with THEIR free kill). Choose wisely:)
It is a sucky standard. Who cares? Not me. I'd sure rather it work than everybody cry about it.
I'd rather people focus the energy on stuff that makes our software stronger and more appealing, rather than trying to implement ill-defined 'open' specs. Mono on linux, for example, is a travesty to me.
And what is wrong with that? It's a flexible tool. Let those who use it come up with 'defining' its use. The fact that it is so flexible is a great thing, IMHO.
Isn't the DRM the 'extra feature?' So, since it takes more effort to add the DRM, shouldn't THAT cost more? And then, shouldn't the person who wants the DRM (the content provider) then be the one to pay the bill?
Don't teach 'software.' Teach concepts. Whatever you use that lets the kids be productive with the concept should be fine, right?
In college we used some sort of cad software that I don't even remember the name of. That didn't mean that the concept of snapping, lineto, center, tangent, etc didn't translate when I used autocad (which I most certainly did not take a class on) for a few things before becoming a full time computer geek. Same applies to firewalls and routers and such. If you know TCP/IP and Routing and such, how to configure the stuff is simply a matter of looking up how to do it on that particular device in the manual (how do I define a tunnel, how do I define a route, etc). I *hate* working with cisco guys who took their class, and can't think beyond the ciscoese (bringing up partner IPSec VPNs being the best example of this).
Except that until recently, pay as you go really meant "we charge you a dollar every day whether you used the phone or not, and the money you prepay is only good for a month or two, whether you used the phone or not". So you are still paying $30+ a month. Verizon recently began offering pay as you go where you only pay on the days you use the phone. I think the minutes still expire though, which I guess is ok, so long as the minimum purchase every month or two is $5 or less.
Where pay as you go really sucks is with data. I would like to use SMS with mailbiff, but at $.10 a message, I just don't bother. Internet use is also still expensive if you really use it each day. If you don't, there's not much point to using it on your phone in the first place.
I agree with you. But recently verizon started offering true pay as you go where you only pay the $.99 fee on days you use the service. Of course, you still have to make a payment every couple of months to keep the service active, and there may be a minimum on that, but it's better than paying a minimum of $30/month just to have the damned thing in case you need it.
Why is it OK for thousands of people to have their computers be rendered inoperable just because they run an operating system that you don't like? Oh, right, because Vista is the worst operating system in all of history and everyone that uses it somehow deserves their computer to be unusable.
Because THEY are the ones who are part of the friggin' botnets that kill my bandwidth, cause ISPs to block MY mail server, etc. Windoze users have a VERY real impact on my ability to use the bandwidth I am paying for thankyouverymuch.
If they are able to be killswitched by ANYONE, then they SHOULD BE.
Just get the same model keyboard, plug in the receiver, and fire up your favorite text editor? Granted, I'm not up on my wireless keyboard technology, but this would work with the old one that I have, that is also the model the CIO uses in his presentations to the company. Scary.
Slashdot Mirror
This is why I searched so long (and found! Yay!) a phone that still used 900MHz. One less thing to crowd the wireless at home.
I remember learning to write software for OS/2 back in the early 90's. Multi-threaded programming was *the* model there, and had it been more popular, it would be pretty much standard practice today, making scaling to multiple cores pretty effortless, I'd think. It's a shame that the single-threaded model became so ingrained in everything, including linux. For an example that comes to mind, why do I need to wait for my mail program to download all headers from the IMAP server before I can compose a new message on initial startup? Same with a lot of things in firefox.
Does anybody remember DeScribe?
And you then need to expend the energy to empty the tube, or energy to shove the ship down. You've saved nothing, and lost efficiency in the energy required to stage the rocket under water.
All of it?
http://en.wikipedia.org/wiki/Security_theater
I like it! :)
Amen. I tell this to my friends as well. I'll soon be getting some beer, and maybe a nice dinner from a girl I have done a few bike rides with b/c she needs some help.
Giving his password to his secretary would seem a security policy violation to me. Who knows what type of classified information that secretary was now perusing. This type of thing should be brought up to the other chiefs and the legal department.
Then the reboot resolved nothing. It just hid the symptoms so it took you that much longer to *actually* fix the problem. On my *nix boxes, a reboot is absolutely the last thing I ever do to try to resolve a problem. Doubly so for high-visibility production stuff (mail servers, firewalls, etc). Syslogs are your friend.
Then again, the 'event viewer' in windows is pretty much useless. Without good information, fixing a problem becomes nearly impossible, so the SOP for windows boxes is to reboot often to mask the real problem in order to do some sort of work with the system before it goes legs up again.
which leads to why are they employed in the first place? I swear, if your job requires some form of computer skill, shouldn't you, um, have it?
My father is actually a great user security-wise, b/c he is afraid of doing something that will infect him with nefarious software so he actually does practice very good computer hygiene as a user to the point that antivirus software really doesn't do anything but waste cpu cycles on his computer. But, he does it to a fault, and needs to not be so afraid to explore.
:) Apparently he had accidentally changed it when he bumped into it or something.
:)
He has definitely gotten better since teaching him how to listen to internet streams, and now that he bought himself a sansa mp3 player, I was even able to teach him how to rip all of his CDs so that he can listen on the road. In addition, he's an awesome photographer, and recently bought himself a digital SLR (he had his own darkroom in the 70's), and has taught himself how to edit and publish his work. Take something a user loves, and teach them how to use a computer to do it better, and you usually have no problems getting them to dive in and actually learn things on their own.
The funny tech support story is that last year I had given him an FM transmitter so that he can listen to his music easily in the main room on the main stereo while playing from the computer in the computer room.
Over thanksgiving this year, he came to me all perplexed as to why it sounded horrible. He had tried everything, including checking all wires, and changing the antenna's location. I took a look, and changed the channel on the transmitter to match the station on the stereo
Having many years experience being both a sysadmin and support person, I've learned to always look at the simple solution first. It's probably the right one and also the one everyone else overlooked. Dad now knows this basic troubleshooting principle as well
It always happens to me when going through a spectacular crash, either on my bike or my snowboard. Like that time I hit a pile of snow that had solidified into ice while dropping in to a local drainage area at the grocery store. That split second as soon as I went over the lip and saw what was about to happen was very long, as I can totally remember thinking "This is gonna hurt" right before the front wheel hit and my fork snapped off.
This year I'm thinking of getting jerseys made and leading a team at the 24 hours of big bear as "Team V1@gra". Our motto, also on the jerseys, will be "Ride Hard"
Yup. He had no right to do anything to the guy. Now, if it was his own g/f, son, daughter, wife that this guy raped? THAT I could understand killing the fscker over. I'd likely do the same.
:)
That said, maybe it should be legal to kill exactly one person in your lifetime without consequence (well, other than that person's relatives coming after you with THEIR free kill). Choose wisely
I'd rather people focus the energy on stuff that makes our software stronger and more appealing, rather than trying to implement ill-defined 'open' specs. Mono on linux, for example, is a travesty to me.
And what is wrong with that? It's a flexible tool. Let those who use it come up with 'defining' its use. The fact that it is so flexible is a great thing, IMHO.
Now chris hansen doesn't need to pay somebody to pretend to be a 13 year old girl in search of sex any more.
Isn't the DRM the 'extra feature?' So, since it takes more effort to add the DRM, shouldn't THAT cost more? And then, shouldn't the person who wants the DRM (the content provider) then be the one to pay the bill?
Why was this modded funny? It's spot on.
Don't teach 'software.' Teach concepts. Whatever you use that lets the kids be productive with the concept should be fine, right?
In college we used some sort of cad software that I don't even remember the name of. That didn't mean that the concept of snapping, lineto, center, tangent, etc didn't translate when I used autocad (which I most certainly did not take a class on) for a few things before becoming a full time computer geek. Same applies to firewalls and routers and such. If you know TCP/IP and Routing and such, how to configure the stuff is simply a matter of looking up how to do it on that particular device in the manual (how do I define a tunnel, how do I define a route, etc). I *hate* working with cisco guys who took their class, and can't think beyond the ciscoese (bringing up partner IPSec VPNs being the best example of this).
I vote for pop up tank traps :-)
Yeah. And how am I going to get out of the matrix now?
Except that until recently, pay as you go really meant "we charge you a dollar every day whether you used the phone or not, and the money you prepay is only good for a month or two, whether you used the phone or not". So you are still paying $30+ a month. Verizon recently began offering pay as you go where you only pay on the days you use the phone. I think the minutes still expire though, which I guess is ok, so long as the minimum purchase every month or two is $5 or less.
Where pay as you go really sucks is with data. I would like to use SMS with mailbiff, but at $.10 a message, I just don't bother. Internet use is also still expensive if you really use it each day. If you don't, there's not much point to using it on your phone in the first place.
I agree with you. But recently verizon started offering true pay as you go where you only pay the $.99 fee on days you use the service. Of course, you still have to make a payment every couple of months to keep the service active, and there may be a minimum on that, but it's better than paying a minimum of $30/month just to have the damned thing in case you need it.
Because THEY are the ones who are part of the friggin' botnets that kill my bandwidth, cause ISPs to block MY mail server, etc. Windoze users have a VERY real impact on my ability to use the bandwidth I am paying for thankyouverymuch.
If they are able to be killswitched by ANYONE, then they SHOULD BE.
Just get the same model keyboard, plug in the receiver, and fire up your favorite text editor? Granted, I'm not up on my wireless keyboard technology, but this would work with the old one that I have, that is also the model the CIO uses in his presentations to the company. Scary.