Why not? Given the amount of pain you've endured under Linux, the costs of a transition to a new platform are small. Your time isn't free. Use the right tool for the job, man.
Because the cost to migrate the data to a new OS is prohibitive.
It's called being nice to normal users, something which won't make sense to a lot of people on slashdot. A lot of people with netbooks, old monitors and so on wouldn't be able to cope with anything more.
That's some twisted logic there. Think about it for a little bit. No matter what, the guy with the small screen will never be able to see more than what fits on his small screen - whether the page is forced to 800x600 or just left to scroll freely.
So that isn't 'being nice' to anyone. You aren't making the 'user experience' one iota better for the guys with small screens, but you are screwing it up for the guys with big screens AND you are crippling it for everyone - big or small screen. How so? Ever try to search 10 different pages for a keyword? That's 10 "click next" plus 10 control-f's at a minimum. Compared to having the entire article on one page which is just a single control-f - or if their are multiple hits you can easily bounce on the control-f rather than having to grab the mouse to hit "next" and then let go and move your hands back to the keyboard for every new page.
So if you are a real web-developer who justifies that brain-damaged design of pretending that web pages don't scroll - you need to start thinking about how the web really works rather than play that faux ivory tower baloney you got going on right now.
FSCache will crash your system unless you are using the version that is part of Kernel >= 2.6.30.
Way past that kernel rev.
Accessing local files over an NFS loopback is nuts though. You's be far better off mounting your FS journal on an SSD.
Nope I wouldn't because its not journal updates that are the problem. Especially since the performance goes in the toilet because of read-only accesses - as in they don't cause journal updates.
There may be other problems too, my cursory examination of the kernel backtraces I got didn't necessarily indicate a deadlock, but I'm not overly familiar with linux backtraces either. My impression is that nfs over loopback is pretty rare - I think the automounter is smart enough to use bind mounts for local filesystems rather than nfs, which is pretty much the only commonly used form.
I've read such docs as your summary before - it's obviously an important issue. The writer rather over exerts himself:
Ok, you've now just self-identified as more than just a skeptic. Using the "methinks thou doth protest too much" fallacy kinda disqualifies you from any claim to rational perspective. That you then want to pick and choose which hadith you want to apply just reinforces your lack of skepticism.
My point was very simple - there is no definitive proof of Aisha's age, there are plenty of historical reports, including various haditha with conflicting information, it is therefore an unknown. The anti-muslim extremists just like to pick and choose the reports they want to believe because they've got an agenda. And while not foaming at the mouth like many of them, you're approach to the subject mirrors theirs and suggests a similar agenda.
Well yeah, caching is not the problem its a possible solution.
The raid6 is on an areca, and it was deliberately tuned for streaming reads and writes over random access - in retrospect separate raid volumes might have been better as the need for random access was not part of the initial requirements. I'm also using jfs and it appears to have a problem with fadvise, although that's been with POSIX_FADVISE_DONTNEED on streaming reads rather than POSIX_FADVISE_RANDOM.
I will look into playing with the kb_read_ahead setting, although I've my doubts because what I see with sar suggests the problem is in the areca-- when random accesses are occurring sar shows vastly reduced tps and rd_sec/s with 100% utilization. If it were buffercache readaheads, I would expect those values to equal or at least be in the neighborhood of the values during pure streaming access. I've already played with areca's own firmware settings for read-ahead aggressiveness without much benefit. Plus, readahead is good for all the streaming work, its just that a small amount of random access has a disproportionate impact on the streaming access.
I agree with your post, but what does a mainstream Muslim have in common with these people?
Didja ya miss the part where he directed the question at any "techno-savvy hard-line Muslim reading this post?" It isn't like all sunni are hard-line or even close to it.
Bunch of cowards running things at Comedy Central administration. They clearly didn't learn the lesson of the Cartoon Wars episodes, every time you give in to bullies, you only embolden them to ask for more next time.
Sounds like what's needed is for someone to threaten them unless they take the beeps out.
Also if you rotate a 1920 X 1200 display into vertical position you get what you want.
I'll second that. I keep a second monitor, rotated to 1200x1920, dedicated to web browsing on my main system.
It totally rocks, I hardly ever have to scroll. However, I am constantly reminded that far too many web designers have their heads firmly stuck in a box of about 800x600 and do the multiple page thing forcing me to click "next" every couple of paragraphs and leaving around half of my screen wasted on empty space.
I have a similar problem and I tried the FSCache approach:
I've got two raids. One is optimized for big ass files read contiguously and has raid6 redundancy. The other is a much smaller JBOD that I can reconfigure via mdraid to anything that linux supports in software.
The problem is that 5% of the big ass files need read-only random access and that kills throughput for anything else going on. It takes me down from ~400MB/s to 15MB/s.
So, I thought I'd use the FSCache approach and use the JBOD as the cache. I did an NFS mount over loopback and pointed the fscache to the JBOD. It worked great got practically full throughput for contiguous access, for about 10 hours and then crashed the system.
Apparently NFS over loopback is well known to be broken in linux and has been since, essentially, forever. I was stunned, it had never even occurred to me that NFS over loopback would be broken. Its freaking 2010 - that something I had been using on Sun0S 3 a bazillion years ago didn't work on linux today had not even entered my mind.
I've also tried replicating the files from the raid6 to the jbod, but that quickly turned into a hassle keeping everything syncronized between the files on disk and the applications that create the files on the raid6 and the apps that use the files on the JBOD. Plus, it doesn't scale out past the size of the JBOD, which I also ran into.
So now, I'm looking at putting the apps that need random access reads to the data in a VM and NFS mounting it with cache to the VM hoping to avoid the NFS-broken-over-loopback problem. I haven't had time to implement it yet, and personally and leery of doing so since I have to wonder what new "known-broken" problems will bite me in the ass.
So, if there is a better way, I am dying to hear it, unfortunately solaris/freebsd is not an option...
It's also illegal to repeat anything I've received that was broadcast over certain frequencies - like those of cell phones, pagers and some other radio bands.
The line can only be drawn at "no expectation of DNA privacy for anyone". Each of us sheds millions of skin cells every day, everywhere we go, leaving our DNA samples on everything we touch. Anyone who considers their DNA their property should kindly not litter and keep it to themselves.
I'll be right there with you, just as soon as the laws preventing me from doing whatever I damn well please with the electromagnetic signals broadcast onto my property are repealed.
Yeah, and Bukhari was the guy who was like 70 years old when he wrote that long after the fact. Guys like you are just extreme regurgitators, probably just cut-n-pasted it from one of those hate-rationalizing websites. Here's a clue - the terrorists have exactly the same kind of erroneous rationalizing-hate websites about people like you.
I don't think that's what he was saying. He's saying this will lend itself to overly simplistic interpretations. Which is a good prediction in climatology, considering what people got out of "climategate."
100% agree. But nothing in life is free. The hoi polloi will continue the mutual masturbation fest, but actual scientists with the right backgrounds to do something useful with the data will now have a much greater opportunity to do something useful with the data.
It's funny that you would pick a random web page that spends one sentence on the topic and cite it as if it were controlling.
I'm certainly not about to waste my time digging through 5 year old edit wars on wikipedia to dig up the citations made at the time. I doubt that you are either given your lol-quality lackadaisical attempt at a citation above.
But I will spend a couple of minutes googling for you in order to find this summary of many of the points illustrating significant ambiguity in the reporting of Aisha's age. You will note that it is chock-full of bibliographic references which you are free to pursue or not.
Actually, you are the one not getting this with that simple-cut-and-paste from the much excised discussion page.
Previous edits of Aisha's article on wikipedia contained supporting references. Not whatever that "ilovewhoever" site is. I'm not talking about edits from a year ago. This Aisha thing has been edit-warred for nearly a decade now. I first looked into it roughly 5 years ago. As someone with a family full of reference librarians, I'm no nube at this.
Ripping a DVD for your own use is legal. DECRYPTING it with an unauthorized backup tool is not thanks to the DMCA
NO that is FALSE.
As the act itself says: Nothing in this section shall affect rights, remedies, limitations, or defenses to copyright infringement, including fair use, under this title.
Decrypting is legal - possession of said tool is legal, it is the distribution of said tool that is illegal.
Witness Slysoft's corporate move to Antigua, where distribution of such tools is legal, as a means to circumvent the DMCA and european equivalents's restrictions on distribution of copy-prevention circumvention tools.
Take someone who has been playing Contra for years, and stick them in front of Quake 3, and see how well developed their "gaming skills" really are, as opposed to their "Contra skills".
Yeah, up up, down down, left right, left right, B A doesn't work in Quake 3. So much for memorization.
Go read the edits on Aisha's page itself, all this information has been posted there along with supporting references. That it is not in the current article is more an abuse of the POV 'requirement' than anything else.
Slashdot Mirror
Why not? Given the amount of pain you've endured under Linux, the costs of a transition to a new platform are small. Your time isn't free. Use the right tool for the job, man.
Because the cost to migrate the data to a new OS is prohibitive.
It's called being nice to normal users, something which won't make sense to a lot of people on slashdot. A lot of people with netbooks, old monitors and so on wouldn't be able to cope with anything more.
That's some twisted logic there.
Think about it for a little bit.
No matter what, the guy with the small screen will never be able to see more than what fits on his small screen - whether the page is forced to 800x600 or just left to scroll freely.
So that isn't 'being nice' to anyone. You aren't making the 'user experience' one iota better for the guys with small screens, but you are screwing it up for the guys with big screens AND you are crippling it for everyone - big or small screen. How so? Ever try to search 10 different pages for a keyword? That's 10 "click next" plus 10 control-f's at a minimum. Compared to having the entire article on one page which is just a single control-f - or if their are multiple hits you can easily bounce on the control-f rather than having to grab the mouse to hit "next" and then let go and move your hands back to the keyboard for every new page.
So if you are a real web-developer who justifies that brain-damaged design of pretending that web pages don't scroll - you need to start thinking about how the web really works rather than play that faux ivory tower baloney you got going on right now.
FSCache will crash your system unless you are using the version that is part of Kernel >= 2.6.30 .
Way past that kernel rev.
Accessing local files over an NFS loopback is nuts though. You's be far better off mounting your FS journal on an SSD.
Nope I wouldn't because its not journal updates that are the problem. Especially since the performance goes in the toilet because of read-only accesses - as in they don't cause journal updates.
http://kbase.redhat.com/faq/docs/DOC-22461
There may be other problems too, my cursory examination of the kernel backtraces I got didn't necessarily indicate a deadlock, but I'm not overly familiar with linux backtraces either. My impression is that nfs over loopback is pretty rare - I think the automounter is smart enough to use bind mounts for local filesystems rather than nfs, which is pretty much the only commonly used form.
I've read such docs as your summary before - it's obviously an important issue. The writer rather over exerts himself:
Ok, you've now just self-identified as more than just a skeptic. Using the "methinks thou doth protest too much" fallacy kinda disqualifies you from any claim to rational perspective. That you then want to pick and choose which hadith you want to apply just reinforces your lack of skepticism.
My point was very simple - there is no definitive proof of Aisha's age, there are plenty of historical reports, including various haditha with conflicting information, it is therefore an unknown. The anti-muslim extremists just like to pick and choose the reports they want to believe because they've got an agenda. And while not foaming at the mouth like many of them, you're approach to the subject mirrors theirs and suggests a similar agenda.
Well yeah, caching is not the problem its a possible solution.
The raid6 is on an areca, and it was deliberately tuned for streaming reads and writes over random access - in retrospect separate raid volumes might have been better as the need for random access was not part of the initial requirements. I'm also using jfs and it appears to have a problem with fadvise, although that's been with POSIX_FADVISE_DONTNEED on streaming reads rather than POSIX_FADVISE_RANDOM.
I will look into playing with the kb_read_ahead setting, although I've my doubts because what I see with sar suggests the problem is in the areca-- when random accesses are occurring sar shows vastly reduced tps and rd_sec/s with 100% utilization. If it were buffercache readaheads, I would expect those values to equal or at least be in the neighborhood of the values during pure streaming access. I've already played with areca's own firmware settings for read-ahead aggressiveness without much benefit. Plus, readahead is good for all the streaming work, its just that a small amount of random access has a disproportionate impact on the streaming access.
Only religious apologists can come up with bullshit like this.
That's funny seeing as how I'm an atheist.
I agree with your post, but what does a mainstream Muslim have in common with these people?
Didja ya miss the part where he directed the question at any "techno-savvy hard-line Muslim reading this post?"
It isn't like all sunni are hard-line or even close to it.
Bunch of cowards running things at Comedy Central administration. They clearly didn't learn the lesson of the Cartoon Wars episodes, every time you give in to bullies, you only embolden them to ask for more next time.
Sounds like what's needed is for someone to threaten them unless they take the beeps out.
Also if you rotate a 1920 X 1200 display into vertical position you get what you want.
I'll second that. I keep a second monitor, rotated to 1200x1920, dedicated to web browsing on my main system.
It totally rocks, I hardly ever have to scroll. However, I am constantly reminded that far too many web designers have their heads firmly stuck in a box of about 800x600 and do the multiple page thing forcing me to click "next" every couple of paragraphs and leaving around half of my screen wasted on empty space.
Isn't summer of code for kids?
With a UID like that, I don't think he's a kid.
I have a similar problem and I tried the FSCache approach:
I've got two raids.
One is optimized for big ass files read contiguously and has raid6 redundancy.
The other is a much smaller JBOD that I can reconfigure via mdraid to anything that linux supports in software.
The problem is that 5% of the big ass files need read-only random access and that kills throughput for anything else going on. It takes me down from ~400MB/s to 15MB/s.
So, I thought I'd use the FSCache approach and use the JBOD as the cache.
I did an NFS mount over loopback and pointed the fscache to the JBOD.
It worked great got practically full throughput for contiguous access, for about 10 hours and then crashed the system.
Apparently NFS over loopback is well known to be broken in linux and has been since, essentially, forever.
I was stunned, it had never even occurred to me that NFS over loopback would be broken. Its freaking 2010 - that something I had been using on Sun0S 3 a bazillion years ago didn't work on linux today had not even entered my mind.
I've also tried replicating the files from the raid6 to the jbod, but that quickly turned into a hassle keeping everything syncronized between the files on disk and the applications that create the files on the raid6 and the apps that use the files on the JBOD. Plus, it doesn't scale out past the size of the JBOD, which I also ran into.
So now, I'm looking at putting the apps that need random access reads to the data in a VM and NFS mounting it with cache to the VM hoping to avoid the NFS-broken-over-loopback problem. I haven't had time to implement it yet, and personally and leery of doing so since I have to wonder what new "known-broken" problems will bite me in the ass.
So, if there is a better way, I am dying to hear it, unfortunately solaris/freebsd is not an option...
Date on the article is April 30th, 2009.
So, does anyone know if basic math skills prevailed?
It's also illegal to repeat anything I've received that was broadcast over certain frequencies - like those of cell phones, pagers and some other radio bands.
You're not only missing the point, you're avoiding it entirely. Do you think researchers have the right to do research on YOU without your permission?
FYI, there is a term for this sort of issue: Informational self-determination.
The line can only be drawn at "no expectation of DNA privacy for anyone". Each of us sheds millions of skin cells every day, everywhere we go, leaving our DNA samples on everything we touch. Anyone who considers their DNA their property should kindly not litter and keep it to themselves.
I'll be right there with you, just as soon as the laws preventing me from doing whatever I damn well please with the electromagnetic signals broadcast onto my property are repealed.
I could care less if the newsgroup counterpart went offline tomorrow; for me, it'd just mean less spam and no more invalid "From" addresses in posts.
And no more contributions from the people who use comp.lang.python.
If your family were full of brain surgeons, would you be qualified to perform operations?
Nope, but I'd be a hell of a lot more knowledgeable on the topic than you.
Yeah, and Bukhari was the guy who was like 70 years old when he wrote that long after the fact. Guys like you are just extreme regurgitators, probably just cut-n-pasted it from one of those hate-rationalizing websites. Here's a clue - the terrorists have exactly the same kind of erroneous rationalizing-hate websites about people like you.
I don't think that's what he was saying. He's saying this will lend itself to overly simplistic interpretations. Which is a good prediction in climatology, considering what people got out of "climategate."
100% agree. But nothing in life is free. The hoi polloi will continue the mutual masturbation fest, but actual scientists with the right backgrounds to do something useful with the data will now have a much greater opportunity to do something useful with the data.
It's funny that you would pick a random web page that spends one sentence on the topic and cite it as if it were controlling.
I'm certainly not about to waste my time digging through 5 year old edit wars on wikipedia to dig up the citations made at the time. I doubt that you are either given your lol-quality lackadaisical attempt at a citation above.
But I will spend a couple of minutes googling for you in order to find this summary of many of the points illustrating significant ambiguity in the reporting of Aisha's age. You will note that it is chock-full of bibliographic references which you are free to pursue or not.
Actually, you are the one not getting this with that simple-cut-and-paste from the much excised discussion page.
Previous edits of Aisha's article on wikipedia contained supporting references. Not whatever that "ilovewhoever" site is.
I'm not talking about edits from a year ago. This Aisha thing has been edit-warred for nearly a decade now. I first looked into it roughly 5 years ago.
As someone with a family full of reference librarians, I'm no nube at this.
Ripping a DVD for your own use is legal. DECRYPTING it with an unauthorized backup tool is not thanks to the DMCA
NO that is FALSE.
As the act itself says:
Nothing in this section shall affect rights, remedies, limitations, or defenses to copyright infringement, including fair use, under this title.
Decrypting is legal - possession of said tool is legal, it is the distribution of said tool that is illegal.
Witness Slysoft's corporate move to Antigua, where distribution of such tools is legal, as a means to circumvent the DMCA and european equivalents's restrictions on distribution of copy-prevention circumvention tools.
Take someone who has been playing Contra for years, and stick them in front of Quake 3, and see how well developed their "gaming skills" really are, as opposed to their "Contra skills".
Yeah, up up, down down, left right, left right, B A doesn't work in Quake 3. So much for memorization.
Go read the edits on Aisha's page itself, all this information has been posted there along with supporting references.
That it is not in the current article is more an abuse of the POV 'requirement' than anything else.