An SNR of 124dB is 89.1 times as good as approximately 105dB. When your speakers are around 80-90 dB and CD quality input around 100dB (less for most heavily compressed input and MP3s), that 105dB SNR for your internal audio is already the least important component in the chain for sound quality. I suspect though that that is for digital output. The analogue stages in onboard audio do leave a lot to be desired.
The vendor supplied tools may be Windows only, but chances are there is a gcc backend available for the target architecture these days. I wouldn't like to be using an ARM board for my cross compiling though, getting QEMU set up for any compilation steps that need to run on the target architecture is enough of a nightmare on Intel, let alone other architectures that noone has used that way before.
I said vim, not vi. I'm well aware that vi goes back further, but nobody in their right mind would consider using the original vi as their primary development tool these days. And Emacs goes back to 1985, not 1972. Sure, it can trace its roots back to ed, from 1972, but it is even less like ed than vim is like vi.
In 1980, a kernel or driver developer was entering data into a mainframe using punchcards in binary (or if they were lucky, an assembler was available for the architecture they were targeting). Version control consisted of a row of 7 cabinets, one for each day of the week, where you stored your most recent stacks of punchcards. They most certainly weren't using vim/emacs, gcc and git and debugging in a VM.
It's called the Kyoto protocol. US keeps promising to sign (leaving government-less Somalia as the final non-signatory) if Maldives grants them one last favor.
On the flip side, taxi drivers have many more hours behind the wheel [aka sleep deprivation]. I thinks it's fair to say that there are many factors which contribute to both raise and lower a taxi's risk of getting into an accident.
So far we've only come up with factors that raise the risk. What are the factors that lower it?
Yeah, really. So is that Boston Red Line car length or Boston Blue Line car length. London Underground Circle Line car length perhaps? BART car length?
Quit being so pedantic. It's obvious that they meant one of these.
Easy solution in this case is to remove all Qualcomm code from the Linux kernel.
In the short term this will cause a lot of pain for end users and companies that use Qualcomm hardware in their products, but in the long run this will effectively shut Qualcomm out of a very large portion of their market and serve as an excellent example to others why the DMCA should be used with great care.
I'd think that any company selling Android based mobile phone, tablet or other Linux based device built from GPL code they received directly from Qualcomm would have good standing to take this to court. End users not so much.
Maybe Qualcomm really have made the decision that they only want their chips used in Windows Phone devices from now on, because this is the signal they are sending to manufacturers that rely on their hardware support for Linux and Android with this move.
I though driving by an open hotspot on the highway was enough time to use it.
Only with 802.11p which allows data transfer without associating to the access point, and maybe the still under development 802.11ai, which aims to speed up the time required for association to under 100ms.
Its the scan of nearby networks bit where it needs to send out the WiFi networks it wants to connect to. That's why making your SSID hidden is a security anti-pattern. Tell the owners of the networks you connect to to stop doing it - anyone nearby can see all the clients making requests to join your network, so it isn't adding any security in your near vicinity, and elsewhere, others can still see your clients trying to connect to your network wherever they are, because to connect to hidden networks you have to go out and proactively look for them.
The headline also fails to mention that only manually configured networks are affected (or perhaps old versions of Android, I don't remember the details from the comments to the story about 6 months ago regarding the exact same "flaw" in iOS). This is why it is a BAD idea for security to turn off access point beacons - because if your access point is not sending out beacons to identify itself, then the clients need to send out connection requests blindly - wherever they are.
I seem to recall only two floppies were needed, one for the kernel and one for userspace. But that was a bare bones command line install. As there were no distros yet, everything else was downloaded to my 40MB hard drive and compiled from source (including a replacement kernel that had all the drivers for my hardware, once the bootstrapping was out of the way).
So dude doesn't want his name's first search result to be an over-hyped headline.
I don't know if it was the first search result (I am well outside the EU, but don't see it anywhere in the first 5 pages, so maybe Google's takedown was wider than TFS suggests), but based on what I did see, he's got his work cut out recovering his reputation this way - there are similar articles in NYT, Time, WSJ and pretty much every other major news source outside the jurisdiction of the EU dominating at least the first five pages of results.
That's OK, he doesn't need to work for you any more, his life is fulfilled now that he's met Barbara Streisand in person. Apparently they had so much in common.
I had the same experience with Vodafone UK. Eventually I got a refund, but only after I asked "is this call being recorded?" after demonstrating to the customer service rep that they had no evidence whatsoever of 1) me subscribing to the premium SMS spamming service or 2) that the T&Cs for premium SMS services were being complied with by the scammer. They also informed me at the end of the call about the STOP ALL message, which at that time (about 10 years ago) was not public knowledge, and which they could have told me at the start of the call instead of telling me to contact the company I'd subscribed from - and no they can't tell me who owns that number due to privacy restrictions.
They are getting 4 years of updates, because Apple is keeping them on the shelf for 3 1/2 years. iPhone 4 got iOS 7, because it was still on the shelves when it was announced (though taken off the shelves on the day it was released). The original iPad, which came out 3 months earlier with much the same level of hardware, did not even get iOS 6, because it was withdrawn from sale as soon as the iPad 2 came out.
The main difference here is the rate of release of new phones. Apple likes to keep 3 models of iPhones in the market for budget, midrange and high-end, and until the iPhone 5c, the midrange and budget categories were both covered by old models. Google tends to keep just one model in the market. Both companies continue to support minor releases on their most recently obsoleted hardware, but generally not major releases. Other companies selling Android phones do tend to abandon their low end models on release, but the high end ones are generally just as well supported as Apple and Google, with a little lag in release dates which is improving as Google tackles the issues which cause porting delays.
People like to beat up Android for ongoing support of devices, but Google is no different than Apple and other companies in this respect. The Nexus One was contemporary with the iPhone 3G, which was only supported up to iOS 4.2.1, released in June 2010, on the same day that sales of the iPhone 3G were discontinued. Nexus One was supported until Android 2.3.7, which was released around a year after sales were discontinued.
...which is run from within my editor of choice, emacs.
...which I run in a shell.
You seem to be confused about the program that emacs is replacing. It is not replacing vi, it is replacing init. Once you realize that, you will find it perfectly natural to run your shell inside Emacs.
Slashdot Mirror
An SNR of 124dB is 89.1 times as good as approximately 105dB. When your speakers are around 80-90 dB and CD quality input around 100dB (less for most heavily compressed input and MP3s), that 105dB SNR for your internal audio is already the least important component in the chain for sound quality. I suspect though that that is for digital output. The analogue stages in onboard audio do leave a lot to be desired.
People create random original things all the time. It's the hardware fluke bar they'd have trouble passing.
The vendor supplied tools may be Windows only, but chances are there is a gcc backend available for the target architecture these days. I wouldn't like to be using an ARM board for my cross compiling though, getting QEMU set up for any compilation steps that need to run on the target architecture is enough of a nightmare on Intel, let alone other architectures that noone has used that way before.
One decade maybe. But the primary development environment for kernel and driver work today still looks very different than in 1980.
I said vim, not vi. I'm well aware that vi goes back further, but nobody in their right mind would consider using the original vi as their primary development tool these days. And Emacs goes back to 1985, not 1972. Sure, it can trace its roots back to ed, from 1972, but it is even less like ed than vim is like vi.
In 1980, Xenix did not exist yet.
In 1980, a kernel or driver developer was entering data into a mainframe using punchcards in binary (or if they were lucky, an assembler was available for the architecture they were targeting). Version control consisted of a row of 7 cabinets, one for each day of the week, where you stored your most recent stacks of punchcards. They most certainly weren't using vim/emacs, gcc and git and debugging in a VM.
It's called the Kyoto protocol. US keeps promising to sign (leaving government-less Somalia as the final non-signatory) if Maldives grants them one last favor.
So far we've only come up with factors that raise the risk. What are the factors that lower it?
Quit being so pedantic. It's obvious that they meant one of these.
Easy solution in this case is to remove all Qualcomm code from the Linux kernel. In the short term this will cause a lot of pain for end users and companies that use Qualcomm hardware in their products, but in the long run this will effectively shut Qualcomm out of a very large portion of their market and serve as an excellent example to others why the DMCA should be used with great care.
I'd think that any company selling Android based mobile phone, tablet or other Linux based device built from GPL code they received directly from Qualcomm would have good standing to take this to court. End users not so much.
Maybe Qualcomm really have made the decision that they only want their chips used in Windows Phone devices from now on, because this is the signal they are sending to manufacturers that rely on their hardware support for Linux and Android with this move.
Only with 802.11p which allows data transfer without associating to the access point, and maybe the still under development 802.11ai, which aims to speed up the time required for association to under 100ms.
Its the scan of nearby networks bit where it needs to send out the WiFi networks it wants to connect to. That's why making your SSID hidden is a security anti-pattern. Tell the owners of the networks you connect to to stop doing it - anyone nearby can see all the clients making requests to join your network, so it isn't adding any security in your near vicinity, and elsewhere, others can still see your clients trying to connect to your network wherever they are, because to connect to hidden networks you have to go out and proactively look for them.
The headline also fails to mention that only manually configured networks are affected (or perhaps old versions of Android, I don't remember the details from the comments to the story about 6 months ago regarding the exact same "flaw" in iOS). This is why it is a BAD idea for security to turn off access point beacons - because if your access point is not sending out beacons to identify itself, then the clients need to send out connection requests blindly - wherever they are.
I seem to recall only two floppies were needed, one for the kernel and one for userspace. But that was a bare bones command line install. As there were no distros yet, everything else was downloaded to my 40MB hard drive and compiled from source (including a replacement kernel that had all the drivers for my hardware, once the bootstrapping was out of the way).
I don't know if it was the first search result (I am well outside the EU, but don't see it anywhere in the first 5 pages, so maybe Google's takedown was wider than TFS suggests), but based on what I did see, he's got his work cut out recovering his reputation this way - there are similar articles in NYT, Time, WSJ and pretty much every other major news source outside the jurisdiction of the EU dominating at least the first five pages of results.
That's OK, he doesn't need to work for you any more, his life is fulfilled now that he's met Barbara Streisand in person. Apparently they had so much in common.
Unlike phone carriers, ISPs do not take a substantial cut of the spammers profit.
I had the same experience with Vodafone UK. Eventually I got a refund, but only after I asked "is this call being recorded?" after demonstrating to the customer service rep that they had no evidence whatsoever of 1) me subscribing to the premium SMS spamming service or 2) that the T&Cs for premium SMS services were being complied with by the scammer. They also informed me at the end of the call about the STOP ALL message, which at that time (about 10 years ago) was not public knowledge, and which they could have told me at the start of the call instead of telling me to contact the company I'd subscribed from - and no they can't tell me who owns that number due to privacy restrictions.
I imagine a Canadian could post the same sort of story about farmers in the bible belt as a way of taking a dig at their southern neighbors too eh.
They are getting 4 years of updates, because Apple is keeping them on the shelf for 3 1/2 years. iPhone 4 got iOS 7, because it was still on the shelves when it was announced (though taken off the shelves on the day it was released). The original iPad, which came out 3 months earlier with much the same level of hardware, did not even get iOS 6, because it was withdrawn from sale as soon as the iPad 2 came out.
The main difference here is the rate of release of new phones. Apple likes to keep 3 models of iPhones in the market for budget, midrange and high-end, and until the iPhone 5c, the midrange and budget categories were both covered by old models. Google tends to keep just one model in the market. Both companies continue to support minor releases on their most recently obsoleted hardware, but generally not major releases. Other companies selling Android phones do tend to abandon their low end models on release, but the high end ones are generally just as well supported as Apple and Google, with a little lag in release dates which is improving as Google tackles the issues which cause porting delays.
People like to beat up Android for ongoing support of devices, but Google is no different than Apple and other companies in this respect. The Nexus One was contemporary with the iPhone 3G, which was only supported up to iOS 4.2.1, released in June 2010, on the same day that sales of the iPhone 3G were discontinued. Nexus One was supported until Android 2.3.7, which was released around a year after sales were discontinued.
You seem to be confused about the program that emacs is replacing. It is not replacing vi, it is replacing init. Once you realize that, you will find it perfectly natural to run your shell inside Emacs.
It was as much the fault of the idiot who wrote the form as the oaf who filled it out, as far as I could make out from the reports.