If you're trying to get permissions correct to eliminate these type of prompts in a corporate environment (or make an app work in a locked down pre-Vista environment) I can't recommend LUA Buglight highly enough. Basically it provides a way to record exactly what rights an application is requesting as you run it. I've used it mostly to get temperamental programs running as locked down users under Citrix but it should work fine to help reduce the amount of UAC messages under Vista.
How about the operators of each Root server signs their own copy of the root? That way if one entity implements policies that you don't agree with you simply remove them from your hints file. There's a reason there's multiple root servers and putting the signing authority in the hands of one entity inherently makes the system less diverse and fault tolerant.
Here's justification for you: The soliciting party is engaged in a lawsuit against the city over a similar plan by the city, until the lawsuit is concluded the city is unsure of how they will move forward with their deployment and if the soliciting parties proposal will interfere with the cities plans. Once the lawsuit is concluded the city will finalize their plans and evaluate the soliciting parties request for permission to dig, the city will provide a detailed plan to the soliciting party no later than 90 days after the conclusion of the lawsuit.
Most commercial offerings already support multiple DB's and doing so in your own apps should be trivial with a sane design, the SQL calls should all be abstracted into their own chunk of code so only that piece needs to be touched. I think either extreme approach is a bit insane, use a bit of both a know when each is appropriate.
Your definition of huge is funny, I have tables that are growing a million rows a month and that's for a small S&P 500 company. I have a friend who does joins on multiple tables with 300+M rows every day. I'm not bragging because my DB is huge (it's not) but more commenting on the fact that so many slashdotters seem to lack a perspective on what a truly large DB is.
That advice is only appropriate in the expected query results are small, on large tables using stored procedures can significantly reduce the load on the DB by not requiring it to handle open connections while a large amount of data is streamed to the remote client.
Doesn't matter, you can have the concentrator check the client, unless someones figured out how to fake the cryptographic signature with a tampered binary there's no real chance of a secure network being compromised.
Doesn't everyone know that the front page rankings are worthless and it's the per area/major rankings and the detailed information that's important? Also the rankings are only a place to start, you need to do an extended visit to your top 5 schools to see how likely you are to be compatible with the school.
You can set the polling interval on a per service or monitor basis in WhatsUp as well. It also includes remediation in the base price (though it doesn't include any functionality other than restart service out of the box, but that's usually custom anyways). Their discounts would have to be like 90% to be cost competitive, do you have any idea what their site licensing costs are like? I don't feel like being pestered by a sales puke for information that should be right on their website.
Hyperic looks cool but the support costs are insane, ~$800/2CPU's/year? I only paid around $1,600 for WhatsUp and pay a fraction of that per year in maintenance to monitor up to 1,000 devices. It's not perfect but I can deal with some warts for that kind of savings!
The GP said: explicitly defines VDD as 1.5 V +/- 0.075 V for DDR3-compliant memory modules
1.5*.05 =.075 so the spec only allows for 5% variance up or down for VDD, this is half as much as most specs allowed for. For example DDR1 was 2.5V +/-.2V
My big fear is Obama wins and actually does what will be needed which is cutting spending and raising taxes like Carter did and we end up with 12 years or Republicans claiming the good economy is all their doing.
I've never noticed it in gaming, but matching the latency to the CPU timing can noticeably affect video encoding. Changing my ram from stock 3-3-3-5 to it's full supported 2-2-2-3 decreased encoding time significantly with no other changes to the machine.
Actually plenty of OEM's bin parts from ATI/NVidia and sell parts that are overclocked according to the chip supplier. These part's are often labeled OC and carry a price premium but have a full manufacturer warranty.
Wow, the spec is pretty tight, traditionally PC specs allowed for +/- 10% for voltages to allow for cheaper PSU's, I guess the power filtering on newer motherboards needs to be pretty good to stay in spec.
What kind of disk's? There are a lot of ways to do disks in a virtualization environment and they are definitely not equal. For production DB's the best I've seen is ESX 3.5 with raw FC access and native volumes, only an ~10% I/O penalty which can be acceptable depending on the workload and cost/benifit analysis. Using 3.0 or Xen with NFS volumes was terribly painful for DB stuff.
Cruising altitude isn't a problem at all, that's only a max of ~8 miles, I talk to a tower further away than that most of the time at home with 2 bars and an EDGE data connection. In fact we know that phones will work on a plane at full speed due to 9/11, many people called their loved ones from the plane to say their farewells.
Actually, pure GSM SMS is carried in the status message that the phone and tower trade whenever they talk which is why it is so limited in length. Today most phones will attempt to use the data service if available and fallback to the old method only if the data connection doesn't work.
Slashdot Mirror
If you're trying to get permissions correct to eliminate these type of prompts in a corporate environment (or make an app work in a locked down pre-Vista environment) I can't recommend LUA Buglight highly enough. Basically it provides a way to record exactly what rights an application is requesting as you run it. I've used it mostly to get temperamental programs running as locked down users under Citrix but it should work fine to help reduce the amount of UAC messages under Vista.
Permitting is normally controlled by the council or a committee thereof, only in the largest of cities is it performed by an unelected bureaucrat.
How about the operators of each Root server signs their own copy of the root? That way if one entity implements policies that you don't agree with you simply remove them from your hints file. There's a reason there's multiple root servers and putting the signing authority in the hands of one entity inherently makes the system less diverse and fault tolerant.
Here's justification for you: The soliciting party is engaged in a lawsuit against the city over a similar plan by the city, until the lawsuit is concluded the city is unsure of how they will move forward with their deployment and if the soliciting parties proposal will interfere with the cities plans. Once the lawsuit is concluded the city will finalize their plans and evaluate the soliciting parties request for permission to dig, the city will provide a detailed plan to the soliciting party no later than 90 days after the conclusion of the lawsuit.
Non-Part 15 devices....
Most commercial offerings already support multiple DB's and doing so in your own apps should be trivial with a sane design, the SQL calls should all be abstracted into their own chunk of code so only that piece needs to be touched. I think either extreme approach is a bit insane, use a bit of both a know when each is appropriate.
Your definition of huge is funny, I have tables that are growing a million rows a month and that's for a small S&P 500 company. I have a friend who does joins on multiple tables with 300+M rows every day. I'm not bragging because my DB is huge (it's not) but more commenting on the fact that so many slashdotters seem to lack a perspective on what a truly large DB is.
That advice is only appropriate in the expected query results are small, on large tables using stored procedures can significantly reduce the load on the DB by not requiring it to handle open connections while a large amount of data is streamed to the remote client.
Doesn't matter, you can have the concentrator check the client, unless someones figured out how to fake the cryptographic signature with a tampered binary there's no real chance of a secure network being compromised.
Doesn't everyone know that the front page rankings are worthless and it's the per area/major rankings and the detailed information that's important? Also the rankings are only a place to start, you need to do an extended visit to your top 5 schools to see how likely you are to be compatible with the school.
You can set the polling interval on a per service or monitor basis in WhatsUp as well. It also includes remediation in the base price (though it doesn't include any functionality other than restart service out of the box, but that's usually custom anyways). Their discounts would have to be like 90% to be cost competitive, do you have any idea what their site licensing costs are like? I don't feel like being pestered by a sales puke for information that should be right on their website.
Hyperic looks cool but the support costs are insane, ~$800/2CPU's/year? I only paid around $1,600 for WhatsUp and pay a fraction of that per year in maintenance to monitor up to 1,000 devices. It's not perfect but I can deal with some warts for that kind of savings!
The GP said:
.075 so the spec only allows for 5% variance up or down for VDD, this is half as much as most specs allowed for. For example DDR1 was 2.5V +/- .2V
explicitly defines VDD as 1.5 V +/- 0.075 V for DDR3-compliant memory modules
1.5*.05 =
Athlon64 X2 4200+ low power. Relatively small cache compared to the processing power.
My big fear is Obama wins and actually does what will be needed which is cutting spending and raising taxes like Carter did and we end up with 12 years or Republicans claiming the good economy is all their doing.
Exactly, for most sites today encryption would be a rounding error in their CPU budget.
If the encryption is computationally cheaper, then the decryption is computationally cheaper.
Not at all true, 3DES is much more secure than about 90% of the more computationally expensive encryption options.
Yeah and IPv6 makes this particular scheme unneeded by universally supporting IPSEC.
I've never noticed it in gaming, but matching the latency to the CPU timing can noticeably affect video encoding. Changing my ram from stock 3-3-3-5 to it's full supported 2-2-2-3 decreased encoding time significantly with no other changes to the machine.
Actually plenty of OEM's bin parts from ATI/NVidia and sell parts that are overclocked according to the chip supplier. These part's are often labeled OC and carry a price premium but have a full manufacturer warranty.
Wow, the spec is pretty tight, traditionally PC specs allowed for +/- 10% for voltages to allow for cheaper PSU's, I guess the power filtering on newer motherboards needs to be pretty good to stay in spec.
Except modern receivers CAN use signal strength to account for phase shift due to atmospheric conditions.
What kind of disk's? There are a lot of ways to do disks in a virtualization environment and they are definitely not equal. For production DB's the best I've seen is ESX 3.5 with raw FC access and native volumes, only an ~10% I/O penalty which can be acceptable depending on the workload and cost/benifit analysis. Using 3.0 or Xen with NFS volumes was terribly painful for DB stuff.
Cruising altitude isn't a problem at all, that's only a max of ~8 miles, I talk to a tower further away than that most of the time at home with 2 bars and an EDGE data connection. In fact we know that phones will work on a plane at full speed due to 9/11, many people called their loved ones from the plane to say their farewells.
Actually, pure GSM SMS is carried in the status message that the phone and tower trade whenever they talk which is why it is so limited in length. Today most phones will attempt to use the data service if available and fallback to the old method only if the data connection doesn't work.