Sad thing is, most baby bells are no longer including long distance bills in the regular phone statement. What used to be one combined bill for local and long distance is now two separate bills. If you want the bills combined, there's an extra surcharge.
NT is NOT "based" on VMS. David Cutler lead the design of both and they are sure to share similarities because of it, but one is not BASED on the other and to say that NT is some "clone" of VMS is flat wrong.
I would bet that if you had a VMS guru and UNIX guru sit down in front of an NT box for the first time, the VMS guru would feel more at home.
There's presumably a lot of work and evidence to get a court order for such records. If any copyright holder were to demand such records from Verizon without needing a court order, they (Verizon) could quickly be swamped with the number of requests coming in.
Verizon is trying to maintain that the courts should act as a bottleneck to cut down the number of frivilous requests for identity. Otherwise, they'll spend far too much time and money even handling the requests.
They're on our side, but for very different reasons.
This is what I get for making a hypothetical situation (I drink too, nor have I assaulted anyone).
The point is that finding the reason why crimes are commited and working backwards, you can prevent crimes from happening in the first place. This isn't a situation of "lock everyone up that looks at you funny" nor is it "send everyone to AA". This is about balance.
Why can machines be broken into so easily? Three big reasons: shoddy coding, shoddy administration, and social engineering. This isn't because there are big bad h4x0rs out there looking specifically for you, it's because you left the keys in the ignition and the door unlocked. Why don't you just attach a bit to your TCP header that says "I don't run antivirus software and my admin password is null".
While correcting these three issues won't solve all situations, I'd wager that it would take care of greater than 3/4 of the security issues out there right now.
The focus should be on preventing crime in the first place, not punishing someone after the fact.
Spending $10k to have someone go to AA to treat his alcoholism is a whole lot less than the $40k/year when he's in jail after beating his wife in a drunken rage, no?
Same idea here. You prevent the ability to commit a crime, and it can't happen (or the results are less severe). If you let them happen, you often times get an overraction from the authorities.
IIRC, it would look at your notes and automagically insert todos/meetings. Writing a note that read "closing on house next tuesday at 10AM", it would insert a meeting for 4/29 at 10AM (next tuesday for me) with the contents of the note. Or a pointer.
My wife gave birth last thanksgiving morning, so my daughter is now ~4 mos old.
When she first got preganant, she didn't want to go to an OB/GYN, but instead go to a birth center and be with midwives. I thought it a bit granola at first, but went to the open house to see what they had.
The place was across the street from the hospital, and they commented on how they can get a mother from the birth center to the delivery room/OR of the hospital in 3 minutes in case there's a problem (like an emergency C-section). The midwives (in MA) are certified. Then they showed us the rooms, which looked more like a bedroom than a delivery room. Then I got to see the "closet of infinite medical gear", which pretty much sealed it for me.
On the plus side to all this, our HMO paid for everything except the $10/visit copay. The attitude there was a lot nicer than going to a hospital/doctor office. You go in, get the checkup, talk about what's going on, and leave. Almost all our appointments had less than 5 minutes of waiting after we arrived. We didn't get the sense they were trying to rush us out the door to see the next patient.
Next tip: breast feed. The diapers are less stinky.
Tip #3: Take as much time off work as you can. I took ~6 wks off and thus did not kill my co-workers (hi Rich) due to lack of sleep.
Futurama had an episode where Amy got a call on her cell phone. It was about the size of a fingernail, and she had to hold it to her mouth to speak, then move it to her ear to hear.
The charger was about the size of a standard beige PC.
About 6 years ago, we had some Sparc 10s acting as the NIS server. Each morning, about 7AM, it would spontaneously reboot. Nothing in the logs, no other information to tell us what happened, and it was on a UPS.
But we figured out what the problem was.
The local power company 'switched caps' at 7AM in the morning for the ramp up to the day's power usage. The UPS wasn't fast enough to supply power to the Sun, so it got a quick power blink and reboot.
Strange thing was, if we took it off the UPS, it didn't lose power in the morning.
Sonicare toothbrushes (teethbrushes?) can already do this, and there are a few other bathroom-type things (elec. razors) that have this capability. This allows the items themselves to be sealed, so you can drop it in the sink, etc. without destroying it.
When PHP first came out, Perl was the swiss army knife of programming, so I could tie perl, our remedy server, and the web server together and do online reports.
As time went on, it became a bit more cumbersome to work with perl. Mostly because of figuring out how to deal with mod_perl and debugging scripts. I'll admit it - I'm a generally sloppy programmer (which is why I don't do it full time).
PHP gives me a bit more flexibility. It's also becoming a swiss army knife, allowing me to tie a bunch of applications together. But due to the (sloppy) way I code, PHP is better suited to me.
A few years ago I had arguments with a friend over Perl or Python programming for the web. I argued perl, he argued python. At about the same time, we both saw PHP and didn't look back.
How about you put your money where your mouth is and wardial someone's 800 number (that they pay for). See how long it takes before the FBI shows up. See how long it is before they don't pay the phone company for it.
Unsolicited commercial calls to a cell phone are illegal for a reason. You're paying per minute or per call. If you did not request those calls, or they're harassing, you can have it disputed. Calls to your cell phone that reach your voice mail are charged to you, so even if you don't answer the cell phone, you still pay for it.
In addition, the phone company has the resources to accturately determine who called you, complete with a physical address where the phone is installed, or the billing address if it's a cell phone.
For one thing, the packets go down the wire wether the service is running or not. Thousands of requests per second to a box that isn't running the service still has to respond and say "sorry, not running here". Even if it's a few bytes per, it adds up quickly.
Should a customer be charged for requests coming in for a service they don't offer? No, that's the point of the firewall (or packet filter really).
ISPs could have a new revenue stream by looking at this problem differently.
They can offer a firewall for a per-month fee and waive any bandwith increases as a result of DDOS attack or other work-checking that could be blocked by the firewall. An active firewall could proxy HTTP requests, also filtering out common IIS exploits.
User doesn't want the firewall? Fine, you're responsible for all charges.
This would at least give end users an option instead of what will border on collusion when all the AUP/TOSs change to read the same thing.
This is incoming bandwidth - that is, the customer may be fully patched, but the bursts are coming from outside the network. This would be more analagous to the electric company hitting sending 220V (or 440v) to your house for two days. Who's at fault, them for allowing a change in what is coming down the pipe, or you for not protecting each piece of equipment in your house? At best, it's a combination. The electric company should know better than to give you more than you know you need, and you should not rely on someone else to protect your gear.
The only way to really take care of this is to put a firewall in front of the box doing the metering. If the firewall rules are written properly, things like the MSSQL bug won't make it past the firewall.
I was at a user meeting for a 'grid computing' company, where they had a bunch of customers come in and give presentations about how they were using it in their environment.
Every single person that got up had a different definition for grid computing. Even employees of said company had different definitions.
This is exactly like saying something is 'web enabled' back in 1995. Everything had to be web enabled, and everything was, so long as your definition was very vague.
Ecch. It's pretty broken, especially if you're going cross-platform. autofs doesn't support indirect (or was it direct?) mapping, ypbind frequently times out while attempting to contact a NIS server (even though we have 6 in the subnet that are all relatively unloaded), and the usual NFS fixes.
C'mon, we've known that 1024 recv and xmit are really bad values, why is that still the default instead of 8192?
Slashdot Mirror
Sad thing is, most baby bells are no longer including long distance bills in the regular phone statement. What used to be one combined bill for local and long distance is now two separate bills. If you want the bills combined, there's an extra surcharge.
It's stunning, since it implies that gnutella is legal as well. And probably bittorrent.
You now have 4 p2p networks that are legal for trading files. Certainly a change from when Napster was in the same position.
Using their profits from $15 CDs to fund that fight. *sigh*
I would bet that if you had a VMS guru and UNIX guru sit down in front of an NT box for the first time, the VMS guru would feel more at home.
There's presumably a lot of work and evidence to get a court order for such records. If any copyright holder were to demand such records from Verizon without needing a court order, they (Verizon) could quickly be swamped with the number of requests coming in.
Verizon is trying to maintain that the courts should act as a bottleneck to cut down the number of frivilous requests for identity. Otherwise, they'll spend far too much time and money even handling the requests.
They're on our side, but for very different reasons.
Where's the "duck hunt" option for that web site?
This is what I get for making a hypothetical situation (I drink too, nor have I assaulted anyone).
The point is that finding the reason why crimes are commited and working backwards, you can prevent crimes from happening in the first place. This isn't a situation of "lock everyone up that looks at you funny" nor is it "send everyone to AA". This is about balance.
Why can machines be broken into so easily? Three big reasons: shoddy coding, shoddy administration, and social engineering. This isn't because there are big bad h4x0rs out there looking specifically for you, it's because you left the keys in the ignition and the door unlocked. Why don't you just attach a bit to your TCP header that says "I don't run antivirus software and my admin password is null".
While correcting these three issues won't solve all situations, I'd wager that it would take care of greater than 3/4 of the security issues out there right now.
The focus should be on preventing crime in the first place, not punishing someone after the fact.
Spending $10k to have someone go to AA to treat his alcoholism is a whole lot less than the $40k/year when he's in jail after beating his wife in a drunken rage, no?
Same idea here. You prevent the ability to commit a crime, and it can't happen (or the results are less severe). If you let them happen, you often times get an overraction from the authorities.
IIRC, it would look at your notes and automagically insert todos/meetings. Writing a note that read "closing on house next tuesday at 10AM", it would insert a meeting for 4/29 at 10AM (next tuesday for me) with the contents of the note. Or a pointer.
Pricy but WAY worth it.
The web interface rocks, it has an intelligent remote control interface, and my wife hasn't busted it in frustration yet.
Can someone speaking relatively technical* explain what is so cool about NPTL?
*as in, I'm not a coder, but am an experienced sys admin.
My wife gave birth last thanksgiving morning, so my daughter is now ~4 mos old.
When she first got preganant, she didn't want to go to an OB/GYN, but instead go to a birth center and be with midwives. I thought it a bit granola at first, but went to the open house to see what they had.
The place was across the street from the hospital, and they commented on how they can get a mother from the birth center to the delivery room/OR of the hospital in 3 minutes in case there's a problem (like an emergency C-section). The midwives (in MA) are certified. Then they showed us the rooms, which looked more like a bedroom than a delivery room. Then I got to see the "closet of infinite medical gear", which pretty much sealed it for me.
On the plus side to all this, our HMO paid for everything except the $10/visit copay. The attitude there was a lot nicer than going to a hospital/doctor office. You go in, get the checkup, talk about what's going on, and leave. Almost all our appointments had less than 5 minutes of waiting after we arrived. We didn't get the sense they were trying to rush us out the door to see the next patient.
Next tip: breast feed. The diapers are less stinky.
Tip #3: Take as much time off work as you can. I took ~6 wks off and thus did not kill my co-workers (hi Rich) due to lack of sleep.
Futurama had an episode where Amy got a call on her cell phone. It was about the size of a fingernail, and she had to hold it to her mouth to speak, then move it to her ear to hear.
The charger was about the size of a standard beige PC.
Yay progress.
About 6 years ago, we had some Sparc 10s acting as the NIS server. Each morning, about 7AM, it would spontaneously reboot. Nothing in the logs, no other information to tell us what happened, and it was on a UPS.
But we figured out what the problem was.
The local power company 'switched caps' at 7AM in the morning for the ramp up to the day's power usage. The UPS wasn't fast enough to supply power to the Sun, so it got a quick power blink and reboot.
Strange thing was, if we took it off the UPS, it didn't lose power in the morning.
Sonicare toothbrushes (teethbrushes?) can already do this, and there are a few other bathroom-type things (elec. razors) that have this capability. This allows the items themselves to be sealed, so you can drop it in the sink, etc. without destroying it.
It's personal preference at this point.
When PHP first came out, Perl was the swiss army knife of programming, so I could tie perl, our remedy server, and the web server together and do online reports.
As time went on, it became a bit more cumbersome to work with perl. Mostly because of figuring out how to deal with mod_perl and debugging scripts. I'll admit it - I'm a generally sloppy programmer (which is why I don't do it full time).
PHP gives me a bit more flexibility. It's also becoming a swiss army knife, allowing me to tie a bunch of applications together. But due to the (sloppy) way I code, PHP is better suited to me.
A few years ago I had arguments with a friend over Perl or Python programming for the web. I argued perl, he argued python. At about the same time, we both saw PHP and didn't look back.
How about you put your money where your mouth is and wardial someone's 800 number (that they pay for). See how long it takes before the FBI shows up. See how long it is before they don't pay the phone company for it.
Unsolicited commercial calls to a cell phone are illegal for a reason. You're paying per minute or per call. If you did not request those calls, or they're harassing, you can have it disputed. Calls to your cell phone that reach your voice mail are charged to you, so even if you don't answer the cell phone, you still pay for it.
In addition, the phone company has the resources to accturately determine who called you, complete with a physical address where the phone is installed, or the billing address if it's a cell phone.
How shortsighted.
For one thing, the packets go down the wire wether the service is running or not. Thousands of requests per second to a box that isn't running the service still has to respond and say "sorry, not running here". Even if it's a few bytes per, it adds up quickly.
Should a customer be charged for requests coming in for a service they don't offer? No, that's the point of the firewall (or packet filter really).
ISPs could have a new revenue stream by looking at this problem differently.
They can offer a firewall for a per-month fee and waive any bandwith increases as a result of DDOS attack or other work-checking that could be blocked by the firewall. An active firewall could proxy HTTP requests, also filtering out common IIS exploits.
User doesn't want the firewall? Fine, you're responsible for all charges.
This would at least give end users an option instead of what will border on collusion when all the AUP/TOSs change to read the same thing.
This is incoming bandwidth - that is, the customer may be fully patched, but the bursts are coming from outside the network. This would be more analagous to the electric company hitting sending 220V (or 440v) to your house for two days. Who's at fault, them for allowing a change in what is coming down the pipe, or you for not protecting each piece of equipment in your house? At best, it's a combination. The electric company should know better than to give you more than you know you need, and you should not rely on someone else to protect your gear.
The only way to really take care of this is to put a firewall in front of the box doing the metering. If the firewall rules are written properly, things like the MSSQL bug won't make it past the firewall.
Even defining it doesn't help.
I was at a user meeting for a 'grid computing' company, where they had a bunch of customers come in and give presentations about how they were using it in their environment.
Every single person that got up had a different definition for grid computing. Even employees of said company had different definitions.
This is exactly like saying something is 'web enabled' back in 1995. Everything had to be web enabled, and everything was, so long as your definition was very vague.
Noone can really define it, everyone wants an app that can do it, and companies that claim to do it are getting a lot of interest.
Ecch.
LVM comes with the RedHat 8.0 install. It's pretty sweet. You need to make /boot a regular partition, but the remaining partitions can be LVM.
Ecch. It's pretty broken, especially if you're going cross-platform. autofs doesn't support indirect (or was it direct?) mapping, ypbind frequently times out while attempting to contact a NIS server (even though we have 6 in the subnet that are all relatively unloaded), and the usual NFS fixes.
C'mon, we've known that 1024 recv and xmit are really bad values, why is that still the default instead of 8192?
Yea. Think 'embrace-and-extend'. It's a standard in that all MS products use it, and proprietary in that noone else can.
Best-of-breed makes me crack up every time, especially when they're using it to describe something like IIS or MS Exchange.
That being said, OSS needs to have a *real* exchange killer (that includes calendaring).