How we plan to expose cloud-based filesystems in Samba:
How we plan to expose cloud-based filesystems in Samba:
Actually, I think its because many of the comments disparage the reporters writing the articles. Usually for good cause... the quality of most news articles these days is pretty horrible. But news organizations don't like to be told that they are idiots.
But there are certainly also lots of instances where the commenters start fighting among themselves... usually it devolves down into politics or religion. People with very strong views often come up against the hard, harsh wall of reality and the result is typically fireworks.
You need to kill and restart your firefox if it is eating 21GB. It will return to eating ~1-2 GB, but then start building up again over time. I usually have to completely close my firefox browsers at least once a week.
Honestly, these days if it has two memory slots I stuff it with 16GB of ram. If it has four, then 32GB of ram. Simple as that. Hell, I just put together a 'gaming box' for the son of a friend of mine a few weeks ago and thought 16GB would be enough (4x 4GB). I didn't even follow my own rule because I was being cost conscious. The first thing he did with it? Run minecraft with a visibility setting that ate up all 16GB of ram.
Even more important than ram, stuffing a SSD into the box is what really makes everything more responsive. And even if it has to do a bit of paging it's hardly noticeable when its paging to/from a SSD. And if you do both, the box will stay relevant for a very long time, probably 10 years.
But more to the point, why not?
I know you're just a random slashdot poster, and I really shouldn't expect any better, but would it hurt you to look at the list of Document Foundation (the Org behind LibreOffice) and look at the list of supporters:
"Chris DiBona, Open Source Programs Manager at Google, Inc., has commented: "The creation of The Document Foundation is a great step forward in encouraging further development of open source office suites. Having a level playing field for all contributors is fundamental in creating a broad and active community around an open source software project. Google is proud to be a supporter of The Document Foundation and participate in the project".
Hint - supporters mean we fund them. I represent Google on the Board of Directors, and yes, nagging them about getting a full Android port is something I do *every* meeting.
I now return you to your regularly scheduled slashdot poster 2-minute-hate on "Big Corporations".
Most time consuming bug - The AMD cpu stack corruption bug. Errata 721. It took me a year to track it down. Half that period I thought it was a software bug in the kernel, for a month I thought it was memory corruption in gcc. And most of the rest of the time was spent trying to reproduce it reliably and examine the cores from gcc to characterize the bug. Somewhere in there I realized it was a cpu bug. It took a while to reduce the cases enough to be able to reproduce the bug within 60 seconds. And the last week was putting the whole thing together into a bootable USB stick image to send to AMD so they could boot up the test environment and reproduce the bug themselves.
Bug that was the most fun - The 6522 I/O chip was a wonderful multi-feature chip with a lot of capability. There was a hardware timer bug which could jam the timer interrupt if it timed out at just the wrong time.
My general advice: Add assertions for complex pre-conditions instead of assuming that said complex pre-conditions are always properly in place. The more non-stupid assertions you have in your code, the earlier you detect the bug and the easier it is to fix.
Yup, they sure do. Not only is HTML5 video in ads happening a lot more these days, some sites insert the ads in-line with the article making it difficult for adblock software to distinguish them from graphs and other things that are part of the article.
I've got adblock installed in chrome, but not firefox yet. For some reason some sites think I'm on a chromebook when I use chrome, instead of DragonFly, which I find hilarious. Adblock in firefox is next.
No flash for ages. Last thing I would ever do. HTML5 or nothing, baby! I complain to sites like Pandora that still have flash requirements for certain browsers, but not for others.
We finally get video and sound working properly and it's just been driving me BATTY when I have 30 firefox tabs open and can't figure out which one is making all the noise.
My absolute favorite is actually when a video site has video ads on the side bars that play over the video in the article. Sometimes more than one at once.
On the bright side, it finally caused me to get off my duff and map the mute and volume keys into X.
Because DragonFly defaults to public key only operation. No passworded access is allowed unless the user explicitly enables it, and we've recommended against enabling it for years now.
Just in case you didn't know, SATA and SAS use the same physical interface on the drive side. For systems with a small number of drives there isn't a whole lot of difference. The main issue comes down to how fan-out is handled when a large number of drives are available but the driver is simply so that vendors can pump up the price for the controllers and drives (double, triple, etc for basically the same hardware). The SATA protocol was intentionally hobbled in order to not compete with the SAS protocol. However, for a small number of drives, performance will basically be the same and the cost difference has driven lots of vendors to simply support both and use point-to-point links instead of fan-out anyway.
Sure, but having the bitcoin sitting in the bitcoin wallet doing nothing makes it kinda worthless, yah? The whole idea is to use it for commerce, at which point you are vulnerable to all sorts of scams and theft that you would normally be protected from.
Then there's liquidity. Most transactions are off-block-chain (as in one block-chain transaction per every ~400 or so off-block-chain transactions). They have to be, because putting a transaction on the block-chain takes too long. This means that you must inherently hold a balance, in bitcoin, with a third party, if you actually want to be able to use your bitcoin for general commerce. There are currently no protections whatsoever against that balance.
And then of course there's the volatility of the buying power of bitcoin itself. It's one of the most unstable and volatile currencies in existence.
That said it is better than nothing and certainly better vs certain emerging market currencies undergoing hyper-inflation.
But it isn't better than the dollar or any western currency and never will be.
This isn't correct. Banks can only lend out what they have. They can't manufacture leverage out of thin air. Leverage is a function of being lent money, not of lending out money.
The correct example is that the bank receives $1,000 in deposits from Alice and is allowed to lend out $900 of that. However, this means that the bank only has $100 cash on-hand so it cannot return Alice's $1,000, at least not immediately.
This does not mean that banks do not employ leverage, banks do borrow money, typically in the form of a preferred stock issuance. Just that they basically aren't allowed to in the example you gave. This is all laid out in bank financials. for example, for 2014 Wells Fargo had assets of $1.7 trillion and loans of $863 billion. The Deposit base is around $1.1 trillion.
So, $863 billion in loans on a deposit base of $1.1 trillion.
The mortgage crisis created a situation where loan losses exceeded the regulatory pad for many banks, and in several cases made them effectively insolvent. The Fed provided liquidity temporarily to give the banks time to become profitable again in order to be able to get back into compliance. Which most did. Most of those that did not, such as Washington Mutual, were either forced to be sold (at the beginning) or became desirable assets sold to other banks who were able to take over the deposit base without incurring losses to depositors. Most of the FDIC's losses (since recovered) occurred with smaller banks who had gone so deep into the red that they could not recover even with the extra few years the Fed gave them to become profitable again.
That's the reality. You don't have to like it, but people who deeply believe in bad information tend to wind up unhappy their entire lives when it turns out not to be true, over and over again. There's been a lot of that, too.
For renters it is pushing out people with lower incomes. Not everyone (due to rent control in areas), but still quite a lot of people are getting pushed out I think.
For existing lower-income homeowners it creates an opportunity to get a really good price for their home and then move to cheaper environs. (aka Gentrification).
The remaining pre-existing homeowners are not necessarily going anywhere. Prop 13 means that their property taxes are not changing radically and living costs are otherwise on a less steep ramp.
Gentrification is a two-edged sword, for sure, but I'm not sure that anything can really be done about it. The people protesting the changing nature of their neighborhoods are in the same economic class as many of the people selling and moving away. A person from group A can't really force a person from group B to not sell their home.
Blame posix for making all the goddamn pthread *_timedlock() calls take an absolute real time instead of a monotonic clock.
In anycase, I'm not even going to bother doing anything fancy. I'll let the system suddenly be one second off and then correct itself over the next hour. I'm certainly not going to do something stupid like letting the seconds field increment to 60. Having the ntp base time even go through these corrections is already dumb enough. Base time should be some absolute measure and leap seconds should just be adjusted after the fact in a manner similar to timezones.
The only TRIM use I recommend is running on it on an entire partition, e.g. like the swap partition, at boot, or before initializing a new filesystem. And that's it. It's an EXTREMELY dangerous command which results in non-deterministic operation. Not only do SSDs have bugs in handling TRIM, but filesystem implementations almost certainly also have ordering and concurrency bugs in handling TRIM. It's the least well-tested part of the firmware and the least well-tested part of the filesystem implementation. And due to cache effects, it's almost impossible to test it in a deterministic manner.
You can get close to the same performance and life out of your SSD without using TRIM by doing two simple things. First, use a filesystem with at least a 4KB block size so the SSD doesn't have to write-combine stuff on 512-byte boundaries. Second, simply leave a part of the SSD unused. 5% is plenty. In fact, if you have swap space configured on your SSD, that's usually enough on its own (since swap is not usually filled up during normal operation), as long as you TRIM it on boot.
Computers are useless. They can only give you answers. -- Pablo Picasso