These statistical models work based on crime REPORTING. So you're saying citizens in urban centers are over-reporting crimes and whites are under-reporting crimes? It must be all those white people coming up with phrases like "Snitches get stitches" and "fuck da police"
Why do you want to reboot/shutdown the computer when you travel with it? Just shut the lid, my MacBook Pro stays in standby for 7 days without losing as much as 5% battery.
The problem is, most of them DO need to be on the Internet, whether it's the software phoning home or checking out a license or instrumentation/monitoring, or remote tech support, the documentation is only online or it needs to transfer data to/from the device.
A device that's not on the network is kind of useless these days and sneaker-netting things isn't much better because then people will find workarounds and lose unencrypted hard drives full of juicy personal data.
I've found one system on my network where we had disconnected it from the network for being Windows XP and the idiots purchased a USB WiFi adapter because that's what tech support for the device recommended to do.
I work with Med students. Even though the requirements are pretty high, there is no effort to keep people out for any reason.
The problem is that the majority of the people failing first year is because they want to be doctors for the money, they lack the drive to see it through when they are notified they'll have to spend 60h in a rotation for little to no pay.
Doctors don't make big money until well after college, often several years later being residents in various hospitals following around other doctors making $55k/year. ER doctors making $250k happens 10 years into your career after Med school.
If you have a background in electronics, you would know that it's relatively easy to detect a different kind of device. The White House has hundreds of visitors every month, dropping a tiny robot in a ceiling tile or one of those plug routers with some passive recording equipment would be much more effective and could be near undetectable. Still I think they would have detectors/sweeps for any rogue active broadcasts within the WH.
People are getting ASSAULTED for supporting Trump before and after the election. If you thought voter intimidation only happened in Nazi Germany, welcome the third wave of neo-Marxists.
"Mostly vegetarian" is not vegetarian. Being vegetarian/vegan takes a lot of energy to produce and consume your food. Even though I'm not recommending to eat 10kg of meat per day, humans have evolved to consume some meat/fish and evolved to eat it because it has a much higher energy density than plants so you can eat less of it and require less energy to consume it.
Because we consume way too much meat, I didn't say we are carnivores. Dogs are carnivores, bears have evolved to allow for the potential to be exclusively carnivores and will prefer meat over berries. Many animals (including dogs, but also many raccoons and even squirrels) have been found to get diabetes and heart disease if their diets are based on first world human food waste.
Current science also suggests that meat took less energy to produce and takes less energy to process in your body than plants, hence why we and many other animals prefer to eat meat if it's available.
If you have to raise your own crops and animals, then to a point you have to be mostly vegetarian, raising beef isn't done when you're poor, but keeping poultry and pigs is a good source of protein.
I'm not saying what we are consuming in the US is healthy, but religious practices across time and lands have established many rituals surrounding both eating, raising and subsequent sharing meat with the rest of the tribe as a valued commodity. If meat wasn't easy to do and more beneficial for us than eating plants, we would've never evolved to do that.
Meat protein, especially cooked, takes much less energy to produce and consume compared to plant meat.
Humans are omnivores, we evolved bigger brains because we learned to process meat and eventually started cooking it. Farming eventually allowed us to turn small plots of fast-growing but ultimately inedible crops into high protein/carb meat instead of working large swathes of land for little food value in plant material.
Some farming practices are indeed abysmal and we eat way too much meat right now, but totally removing it is impossible, unhealthy and would upset nature's balance more. Totally removing meat would require much more farm land to be devoted to edible crops to the point it may actually be impossible.
Being a vegetarian, in the end, is a luxury, not a necessity and only rich people can truly afford it.
Most likely Intel's code. The entire chipset is Intel, not Apple, they only put the wires in the right places. You can run Windows or Linux on it which would have the same issues.
CT is basically an X-ray with computers that do just that. So functionally there is little difference between an X-Ray and a CT scan, except that you use computers to analyze the X-Ray image and there is better resolution than a typical X-Ray machine because it uses hundreds of times more radiation.
The question is whether the radiation levels will cause any issues with electronics. Space missions have to have radiation-hardened chips for what amounts to equal or lesser radiation than a high-powered CT can put out.
You can regenerate all the keys in TPM chip. Linux provides a very nice interface for it. Windows won't like it and they'll probably reprogram 'their' keys in the TPM anyway.
Many newer Dells as well. A bunch of the new 5000 and 7000 Latitude series have soldered-on SSD now too. Pretty much anything that's portable these days have portable SSD. Still, I wouldn't rely on recovery tools, a good backup is absolutely necessary, spilling water fries the SSD as much as the logic board whether or not it's glued, soldered or not.
In many cases your laptop won't break but rather disappear (stolen, lost) and thus recovery options are rather scarce.
Copyright rulings have historically gone in favor of the preserving institution and the DMCA has gotten explicit exceptions for it.
In Nintendo's case they could argue they still sell the games in different formats (eg. on the Wii) though although some may argue that's "not the same game".
Dd is by default synced. Most likely op used some advice that setting async on everything made things faster (a lot of older ripoff-of-a-copy Linux guides give that advice to put it in for every fstab and mount option).
The OS should set those flags whenever the write operation has completed, not wait until a "clean shutdown" happens. There are lots of things that can happen between the file write and the time the partition gets unmounted (eg power or controller failure), not accounting for technical issues is a flaw.
but they should accommodate them - And that is where you don't understand the difference between a clock and a time representation. A clock keeps track of time, eg. how many 'ticks' since a certain epoch (eg. since the computer started or a job ended or since 1970/01/01 or every time a crystal under pressure emits a signal). So in programming you typically keep track of time this way, you count the number of ticks (eg. every millisecond or every second) has elapsed. You want to schedule something in the future, you add n ticks and wait for that number to equal the number in the register.
Time representation is when you tell the user "what time is it". Eg. you define United_States/New_York to be "your time zone" so it will do some library call to get the number of 'ticks' (the clock running in TIA/GPS) and then a translation for whatever your local politicians defined your time zone to be today. As of 2012 you also have to adjust for the difference between TIA and UTC. Leap seconds and leap days/years etc are part of the representation and depend on not only what you want to do but also what your user prefers or needs to use it for. In some cases, China may decide not to insert a leap second (they've already indicated they want to get rid of that system) and then your library call is either useless or wrong (and in most cases it will end up being wrong).
In this case, Microsoft wants to build into the low level library that when you call for the 'clock' it will return the arbitrary UTC time representation. Windows historically has not done true clock representation, they always set your system clock to your localized GMT+n time even though it's supposed to run in TIA or GPS (or at worst UTC/GMT+0). It's a complicated thing to implement calendaring and timing, but doing it in a low-level library is wrong because those calls are supposed to be stable and predictable. In this instance, you cannot use this library call for example to schedule things 6 months in the future, since you don't know what UTC will be 6 months in the future since it hasn't been decided yet whether a leap second will be inserted. Every 6 months the committee that decides when to insert leap seconds decides when to insert leap seconds next, that causes issues if you want to run a timer based on UTC for more than the delta between your current time and the insertion of the leap second.
Slashdot Mirror
These statistical models work based on crime REPORTING. So you're saying citizens in urban centers are over-reporting crimes and whites are under-reporting crimes? It must be all those white people coming up with phrases like "Snitches get stitches" and "fuck da police"
Why do you want to reboot/shutdown the computer when you travel with it? Just shut the lid, my MacBook Pro stays in standby for 7 days without losing as much as 5% battery.
The problem is, most of them DO need to be on the Internet, whether it's the software phoning home or checking out a license or instrumentation/monitoring, or remote tech support, the documentation is only online or it needs to transfer data to/from the device.
A device that's not on the network is kind of useless these days and sneaker-netting things isn't much better because then people will find workarounds and lose unencrypted hard drives full of juicy personal data.
I've found one system on my network where we had disconnected it from the network for being Windows XP and the idiots purchased a USB WiFi adapter because that's what tech support for the device recommended to do.
Hence why we have DD- and OpenWRT.
It's not uncommon either. Pregnant people can go in labor weeks early, stress of flying often exacerbates the issue.
I work with Med students. Even though the requirements are pretty high, there is no effort to keep people out for any reason.
The problem is that the majority of the people failing first year is because they want to be doctors for the money, they lack the drive to see it through when they are notified they'll have to spend 60h in a rotation for little to no pay.
Doctors don't make big money until well after college, often several years later being residents in various hospitals following around other doctors making $55k/year. ER doctors making $250k happens 10 years into your career after Med school.
If you have a background in electronics, you would know that it's relatively easy to detect a different kind of device. The White House has hundreds of visitors every month, dropping a tiny robot in a ceiling tile or one of those plug routers with some passive recording equipment would be much more effective and could be near undetectable. Still I think they would have detectors/sweeps for any rogue active broadcasts within the WH.
People are getting ASSAULTED for supporting Trump before and after the election. If you thought voter intimidation only happened in Nazi Germany, welcome the third wave of neo-Marxists.
Open your mouth. Unless you're a crackhead, you most likely have sharp front teeth and molars.
"Mostly vegetarian" is not vegetarian. Being vegetarian/vegan takes a lot of energy to produce and consume your food. Even though I'm not recommending to eat 10kg of meat per day, humans have evolved to consume some meat/fish and evolved to eat it because it has a much higher energy density than plants so you can eat less of it and require less energy to consume it.
Because we consume way too much meat, I didn't say we are carnivores. Dogs are carnivores, bears have evolved to allow for the potential to be exclusively carnivores and will prefer meat over berries. Many animals (including dogs, but also many raccoons and even squirrels) have been found to get diabetes and heart disease if their diets are based on first world human food waste.
Current science also suggests that meat took less energy to produce and takes less energy to process in your body than plants, hence why we and many other animals prefer to eat meat if it's available.
If you have to raise your own crops and animals, then to a point you have to be mostly vegetarian, raising beef isn't done when you're poor, but keeping poultry and pigs is a good source of protein.
I'm not saying what we are consuming in the US is healthy, but religious practices across time and lands have established many rituals surrounding both eating, raising and subsequent sharing meat with the rest of the tribe as a valued commodity. If meat wasn't easy to do and more beneficial for us than eating plants, we would've never evolved to do that.
Meat protein, especially cooked, takes much less energy to produce and consume compared to plant meat.
Which is what I said in the first place although vegetarians lack the energy to properly read.
Humans are omnivores, we evolved bigger brains because we learned to process meat and eventually started cooking it. Farming eventually allowed us to turn small plots of fast-growing but ultimately inedible crops into high protein/carb meat instead of working large swathes of land for little food value in plant material.
Some farming practices are indeed abysmal and we eat way too much meat right now, but totally removing it is impossible, unhealthy and would upset nature's balance more. Totally removing meat would require much more farm land to be devoted to edible crops to the point it may actually be impossible.
Being a vegetarian, in the end, is a luxury, not a necessity and only rich people can truly afford it.
Cook it for more than 2 minutes on each side and it starts resembling the taste of tofu.
Most likely Intel's code. The entire chipset is Intel, not Apple, they only put the wires in the right places. You can run Windows or Linux on it which would have the same issues.
CT is basically an X-ray with computers that do just that. So functionally there is little difference between an X-Ray and a CT scan, except that you use computers to analyze the X-Ray image and there is better resolution than a typical X-Ray machine because it uses hundreds of times more radiation.
The question is whether the radiation levels will cause any issues with electronics. Space missions have to have radiation-hardened chips for what amounts to equal or lesser radiation than a high-powered CT can put out.
You can regenerate all the keys in TPM chip. Linux provides a very nice interface for it. Windows won't like it and they'll probably reprogram 'their' keys in the TPM anyway.
Many newer Dells as well. A bunch of the new 5000 and 7000 Latitude series have soldered-on SSD now too. Pretty much anything that's portable these days have portable SSD. Still, I wouldn't rely on recovery tools, a good backup is absolutely necessary, spilling water fries the SSD as much as the logic board whether or not it's glued, soldered or not.
In many cases your laptop won't break but rather disappear (stolen, lost) and thus recovery options are rather scarce.
Copyright rulings have historically gone in favor of the preserving institution and the DMCA has gotten explicit exceptions for it.
In Nintendo's case they could argue they still sell the games in different formats (eg. on the Wii) though although some may argue that's "not the same game".
Dd is by default synced. Most likely op used some advice that setting async on everything made things faster (a lot of older ripoff-of-a-copy Linux guides give that advice to put it in for every fstab and mount option).
Microsoft OS keeps the modified partition table in memory until it gets cleanly unmounted or there is "time" to write it out.
There is no guarantee (what we're used to in real OS) that your operation was atomic.
The OS should set those flags whenever the write operation has completed, not wait until a "clean shutdown" happens. There are lots of things that can happen between the file write and the time the partition gets unmounted (eg power or controller failure), not accounting for technical issues is a flaw.
but they should accommodate them - And that is where you don't understand the difference between a clock and a time representation.
A clock keeps track of time, eg. how many 'ticks' since a certain epoch (eg. since the computer started or a job ended or since 1970/01/01 or every time a crystal under pressure emits a signal). So in programming you typically keep track of time this way, you count the number of ticks (eg. every millisecond or every second) has elapsed. You want to schedule something in the future, you add n ticks and wait for that number to equal the number in the register.
Time representation is when you tell the user "what time is it". Eg. you define United_States/New_York to be "your time zone" so it will do some library call to get the number of 'ticks' (the clock running in TIA/GPS) and then a translation for whatever your local politicians defined your time zone to be today. As of 2012 you also have to adjust for the difference between TIA and UTC. Leap seconds and leap days/years etc are part of the representation and depend on not only what you want to do but also what your user prefers or needs to use it for. In some cases, China may decide not to insert a leap second (they've already indicated they want to get rid of that system) and then your library call is either useless or wrong (and in most cases it will end up being wrong).
In this case, Microsoft wants to build into the low level library that when you call for the 'clock' it will return the arbitrary UTC time representation. Windows historically has not done true clock representation, they always set your system clock to your localized GMT+n time even though it's supposed to run in TIA or GPS (or at worst UTC/GMT+0). It's a complicated thing to implement calendaring and timing, but doing it in a low-level library is wrong because those calls are supposed to be stable and predictable. In this instance, you cannot use this library call for example to schedule things 6 months in the future, since you don't know what UTC will be 6 months in the future since it hasn't been decided yet whether a leap second will be inserted. Every 6 months the committee that decides when to insert leap seconds decides when to insert leap seconds next, that causes issues if you want to run a timer based on UTC for more than the delta between your current time and the insertion of the leap second.
UTC is a time representation, to be accurate and useful in programming, a clock cannot do the representation part.
Leap seconds are arbitrarily defined like time zones, clocks in low-level system calls should not care about them.
Leap second may be inserted at the end of some other hour (or half-hour or quarter-hour), depending on the local time zone