I've had those problems a lot. I highly doubt the fragmentation issues have been fixed though. Limiting the ARC can help a lot (via/boot/loader.conf). I gave up and moved to 64 bit and haven't had issues since.
Excuse me, but that troll you just pasted is over ten years old. I've perused my logs and found myself referencing said troll over two hundred times. Thank you.
The issue with iPhone 4 isn't about *gripping it*, it's about simply touching this spot to affect the signal.
Just yesterday I was on the phone and my pinky accidentally touched that spot... *instant* loss of sound quality to the point I couldn't understand anything for several seconds.
I went down to my local apple store and tested out 9 iPhone 4s. Of those 9, 4 showed the problem, while 5 were perfectly fine. The test was to place my thumb on the lower left spot, thus "shorting" the two antennas. I repeated my test on each one multiple times and it was consistent. This leads me to believe it's a production batch issue and not any of the other theories being floated around.
Any software fix will only be covering up the problem.
Of course, who doesn't use a case though?
It's a pretty common vulnerability. Bugs like this occurred in Linux recently, as well as FreeBSD (completely different kernel code bases obviously). Some things like DOS emulation require mapping at 0, but in most cases this is unnecessary. Both Linux and FreeBSD disallow mapping at address 0 now. OpenBSD has disallowed this by default of course for quite some time.
Yup, same here. Rarely am I getting a new release even in the first few *months* let alone 4 weeks. I've got a queue full of stuff, along with quite a bit in instant streaming queue. Love this news.
The summary forgets to mention that in return for the 28 day delay, WB is opening its library to Netflix for streaming. For the cheap price this service costs, waiting 4 weeks to see a crappy movie which I've already waited months to see since it was in theaters, really isn't a big deal.
Re:looks like it still loses history
on
BASH 4.0 Released
·
· Score: 1
Don't get me wrong, I really like bash, but the treatment of history is abysmal. The default behavior is to lose history due to a race condition when multiple bash sessions that are concurrently open are closed in arbitrary order.
IMNSHO, the default of any process should be to never lose data.
export PROMPT_COMMAND="history -a"
This will append every new line to the file immediately.
Slashdot Mirror
People never seem to understand this.
Deduplication requires even more RAM / CACHE than you could imagine. Don't hold your breath for it.
I've had those problems a lot. I highly doubt the fragmentation issues have been fixed though. Limiting the ARC can help a lot (via /boot/loader.conf). I gave up and moved to 64 bit and haven't had issues since.
Excuse me, but that troll you just pasted is over ten years old. I've perused my logs and found myself referencing said troll over two hundred times. Thank you.
Well said.
The issue with iPhone 4 isn't about *gripping it*, it's about simply touching this spot to affect the signal.
... *instant* loss of sound quality to the point I couldn't understand anything for several seconds.
Just yesterday I was on the phone and my pinky accidentally touched that spot
I went down to my local apple store and tested out 9 iPhone 4s. Of those 9, 4 showed the problem, while 5 were perfectly fine. The test was to place my thumb on the lower left spot, thus "shorting" the two antennas. I repeated my test on each one multiple times and it was consistent. This leads me to believe it's a production batch issue and not any of the other theories being floated around.
Any software fix will only be covering up the problem.
Of course, who doesn't use a case though?
Exactly. This is just like Hulu blocking Non-US. It's more about licensing and less about evil guys.
http://xkcd.com/651/
The same can be said about all projects. This is why OpenBSD is so secure. It's however lacking in performance and usability quite a bit :(
It's a pretty common vulnerability. Bugs like this occurred in Linux recently, as well as FreeBSD (completely different kernel code bases obviously). Some things like DOS emulation require mapping at 0, but in most cases this is unnecessary. Both Linux and FreeBSD disallow mapping at address 0 now. OpenBSD has disallowed this by default of course for quite some time.
In other news, Ben Affleck apparently died in pakistan
Yup, same here. Rarely am I getting a new release even in the first few *months* let alone 4 weeks. I've got a queue full of stuff, along with quite a bit in instant streaming queue. Love this news.
The summary forgets to mention that in return for the 28 day delay, WB is opening its library to Netflix for streaming. For the cheap price this service costs, waiting 4 weeks to see a crappy movie which I've already waited months to see since it was in theaters, really isn't a big deal.
On top of that, if anyone RTFA, they would see this was just an advertisement for his C++ web framework. Checkout that 'Hello World' app!
This seems like Half Life!
Mod parent up please.
Don't get me wrong, I really like bash, but the treatment of history is abysmal. The default behavior is to lose history due to a race condition when multiple bash sessions that are concurrently open are closed in arbitrary order.
IMNSHO, the default of any process should be to never lose data.
export PROMPT_COMMAND="history -a" This will append every new line to the file immediately.
ISP do in fact do this. http://www.exstatica.net/2008/06/27/documentation-of-hijacking-of-irc-servers-by-timewarneraolcox/ They hijack DNS to try and remove botnets via IRC. Sadly they hijack a lot of very valid and legitimate DNS.