I too thought this was something about some sort of Compact Flash/IDE type interface and was wondering why anyone actually cared too much about IDE drive interfaces, or using non flash drives, in 2014.
Crappy headline.
First of all, paragraphs are your friend.
Second of all, the solution you described already exists.
https://en.wikipedia.org/wiki/...
On that same page, there are a bunch of other solutions as well, this has already been thought of
GPS doesn't help so much when you are in an apartment building with 50 units.
I think in some regards being able to send an SMS in an emergency, with important details like the exact address(including quadrant in cities like Washington DC). There are often cases in DC where they send an ambulance or something to the correct street address but the wrong quadrant and end up being 5 miles away from where they need to be.
It's a little on the spendy side, but the Soekris net6501s are fairly small and reliable. They have a proper RS-232 serial port console too. Standard x86 cpus. The 6501 will boot both 64bit and 32bit kernels(even though the Intel Atom E6XX line only officially supports 32bit.
They're also stuck storing the fuel on site until the federal government comes up with a spent fuel storage solution.
All the best posts on
Oh and fuck beta
The limit you are looking for, the Shannon limit is explained here: https://en.wikipedia.org/wiki/...
It sounds like they just got awarded funding to do the research, which is nice and all. If money was the solution to all of the world's medical problems, surely we would have solved all sorts of issues by now, but science just doesn't work that way. Now don't get me wrong, I hope they succeed in producing a blood substitute, but I'll get excited when they have an available product.
His point is, slashdot doesn't even have an IPv6 address, he's using 6to4 NAT and can still reach the site. The IPv4 address for slashdot is embedded in the IPv6 address.
$ ping6 slashdot.org
PING6(56=40+8+8 bytes) 2001:8b0:ca12:3193:7dc2:1078:67fb:31f4 --> 2001:8b0:6464::666:616:d822:b52d
16 bytes from 2001:8b0:6464::666:616:d822:b52d, icmp_seq=0 hlim=241 time=165.418 ms
16 bytes from 2001:8b0:6464::666:616:d822:b52d, icmp_seq=1 hlim=241 time=121.267 ms
The IPv6 address he was pinging was as follows: 2001:8b0:6464::666:616:d822:b52d
The d822:b52d in the IPv6 address, is actually the IPv4 address for slashdot:
d8 = 216
22 = 34
b5 = 181
2d = 45
$ host -t a slashdot.org
slashdot.org has address 216.34.181.45
Make sense?
How does LibreSSL fix users who do stupid things? This I'd like to know...
Today's cars and electronics will be 30 year old some day. Are you sure you want to integrate them?
Most cars on the road today certainly aren't going to be on the road in 30 years. Especially not cars with out of date radio systems. This is on purpose you know? Automakers want you to buy a new car every 3-5 years, not every 20 to 30 years. They *WANT* the cars to feel outdated in 5 years. You don't make money selling reliable cars anymore. You make money selling an endless line of lemons that mostly do the job of driving while otherwise having the interior fall apart into exploding bits of plastic over time.
I've got a flex fuel suv, that I do run E85 in from time to time, when I can find it. Even then, I will only typically fill up on E85 when its at least 20% cheaper per gallon that gasoline. Otherwise, you are paying more for less energy. I usually see a reduction in MPG running on E85, if its a full tank, usually close to 20%. With that said, if you are planning longer trips, through the midwest, E85 can possibly save you a little bit of cash in some places. I took the trip out to the Dayton Hamvention this year, running mostly on E85.
Like they say, YMMV.
I do pretty much all of my text editing(coding etc) with JOE as well. I too started out as a Slackware user in the mid 90s. I had jumped straight from DOS(where I was used to WordStar) to Slackware, so JOE made me feel pretty much at home...20 years later, I'm still using JOE.
I disagree. Look at multiarch support in Linux. There is little reason to support 32-bit binaries on 64-bit architectures, _especially_ for FOSS software.
Not all platforms are as brain damaged as the x86. On SPARC64 type systems, you'll find that most all software is run in 32bit mode, as the ABI still allows you full register access. Most software doesn't need to access more than 4GB of memory anyways.
Also there is a lot of non-FOSS software that is only available as Linux x86 32bit executables, keeping that 32 ABI compatiblity sure is useful as well on a 64bit system.
It's not entirely unthinkable to run a 64bit kernel on X86-64 and run entirely a 32bit userspace, in fact, it might run a little bit faster as a lot of the software would have a smaller cache footprint, yet the kernel would still support large amounts of physical memory without PAE tricks.
Just because *YOU* think is convoluted and not useful, doesn't mean it doesn't make sense to someone else.
"What man has done, man can aspire to do." -- Jerry Pournelle, about space flight
