What you say doesn't really make any sense, especially the bits about limits. There's nothing especially contradictory about anything in the derivation either as long as you only worry about real numbers. f'(x) comes out to x^(1/x) * (1 - log x) / x^2 and its zero is at x=e.
Yeah, I think it's pretty sensible. If you want to be able to log in as root, it's as simple as adding an ssh key or 'sudo passwd'. But of course there are some well-known advantages to never actually logging in as root.
Come on. I've got satellite here, so I receive probably almost 50,000 program-hours per week. Of that, I know of about two hours of regularly-scheduled, worthwhile programming per week (and one of those is currently preempted by postseason baseball). On the other hand, it was good when BBC America ran through the Blackadder series.
It's a handy one; in fact, as I understand it it's possible to build a universal computer (as powerful as a turing machine) having only two operations: "increment" and "decrement and test for zero". x86 provides this functionality in the form of an opcode called simply "loop" because it's so handy for counting loops.
By the same token, I could criticize your statements as dubiously adherent to an entrenched model that you probably know far less about than you're letting on.
You could, but you'd still be in the uncomfortable position of finding (if you ever bothered to do your own investigation into the matter) that GP's theories fit very well with our current understanding of the universe, and that you don't have a better alternative. It's a "put up or shut up" kind of deal.
I'd say that's a bit out of date. Current parts are usually expected to get 1 million write cycles per block "minimum", and if you get good ones, you can approach 10 million. And provided that you don't rewrite every single piece of data every time, wear leveling will help you out too. So the parent is probably right. You would have to work really hard (or get a number of lousy chips) to kill a decent-sized drive with writes in a year.
And if you think OOo 1.1 is prettier than OOo 2, please go back to your Motif desktop and leave the rest of us alone.
I think OOo 1.1 is ugly and mismatched in a way that happens to be relatively low-key/traditional, which makes it easy to ignore after a while. 2, on the other hand, is ugly and mismatched in a way that doesn't have anything going for it. It's a lot like the mistake that Java made 10 years ago that they're just finally fixing now.
The problem might actually be Linux, not KDE, especially if you run 2.6; the swappiness controls are pretty well b0rken sometimes. In fact, you can argue that the vm's been out of whack since 2.2. You might see whether Con Kolivas' patches can improve your performance.
You can use one of those doodads that lets you read and write memory cards on a PC, or you can run an app on an already-modded PS2 that writes the file to the card. Admittedly, it's not dead-easy, but at least you only need to do it once:)
That doesn't quite follow -- the important number is the pressure difference between the two sides of the glass. In the shuttle, you've got 1 atm on the inside, or maybe less, and ~0 atm on the outside, for a difference of no more than 1 atm. On the other hand, the pressure deep in the ocean is (lotso) atm, and up here it's ~1 atm, for a difference of about (lotso - 1) atm. Harder than keeping a space shuttle together;)
When booting a PSX disc, the PS2 reads a file from the memory card for some silly purpose like providing icons for memory card files. As it turns out, the code that reads that file is vulnerable to a buffer overflow, and if exploited properly it allows one to execute any arbitrary ELF code stored on the memory card, the effect of which you can easily imagine.
Yes, I know all that. The point remains that any _released_ kernel (version number without any -pre or -rc or -m2u4+2df) within the 2.6 series is (theoretically) stable. All of the brokenness is supposed to happen in between.
Slashdot Mirror
Weak ;)
(20000a + 250 + 2b - 250) / 2
10000a + b
What you say doesn't really make any sense, especially the bits about limits. There's nothing especially contradictory about anything in the derivation either as long as you only worry about real numbers. f'(x) comes out to x^(1/x) * (1 - log x) / x^2 and its zero is at x=e.
using LyX (and later kLyx -- whatever happened to that?)
:)
kLyx is long dead, but recent versions of LyX will use Qt instead of that awful XForms. Good enough for me.
It really does do a better job of making sure that dependencies won't break, and when doing a dist-upgrade you need that ability more than ever.
Yeah, I think it's pretty sensible. If you want to be able to log in as root, it's as simple as adding an ssh key or 'sudo passwd'. But of course there are some well-known advantages to never actually logging in as root.
so that the forces of common sense may prevail over those of narrowmindedness
Come on. I've got satellite here, so I receive probably almost 50,000 program-hours per week. Of that, I know of about two hours of regularly-scheduled, worthwhile programming per week (and one of those is currently preempted by postseason baseball). On the other hand, it was good when BBC America ran through the Blackadder series.
Java is a pile of Gosling's steaming shit.
It's a handy one; in fact, as I understand it it's possible to build a universal computer (as powerful as a turing machine) having only two operations: "increment" and "decrement and test for zero". x86 provides this functionality in the form of an opcode called simply "loop" because it's so handy for counting loops.
By the same token, I could criticize your statements as dubiously adherent to an entrenched model that you probably know far less about than you're letting on.
You could, but you'd still be in the uncomfortable position of finding (if you ever bothered to do your own investigation into the matter) that GP's theories fit very well with our current understanding of the universe, and that you don't have a better alternative. It's a "put up or shut up" kind of deal.
Not quite, but there is this guy Alligator Descartes
When I have an incoming text message, I get the sender and a choice to READ or CANCEL, and if I cancel, I don't pay.
-1: People like you are the biggest problem this world faces.
s/parent/grandparent/ # and now it's the great-grandparent
I'd say that's a bit out of date. Current parts are usually expected to get 1 million write cycles per block "minimum", and if you get good ones, you can approach 10 million. And provided that you don't rewrite every single piece of data every time, wear leveling will help you out too. So the parent is probably right. You would have to work really hard (or get a number of lousy chips) to kill a decent-sized drive with writes in a year.
And if you think OOo 1.1 is prettier than OOo 2, please go back to your Motif desktop and leave the rest of us alone.
I think OOo 1.1 is ugly and mismatched in a way that happens to be relatively low-key/traditional, which makes it easy to ignore after a while. 2, on the other hand, is ugly and mismatched in a way that doesn't have anything going for it. It's a lot like the mistake that Java made 10 years ago that they're just finally fixing now.
Now just explain why it's larger, slower, uglier, and harder to use than the previous release, and we'll be good!
Pretty stable, lately; Con's been pretty conservative. Things that are more "out there" tend to land in -mm.
The problem might actually be Linux, not KDE, especially if you run 2.6; the swappiness controls are pretty well b0rken sometimes. In fact, you can argue that the vm's been out of whack since 2.2. You might see whether Con Kolivas' patches can improve your performance.
Ya I'm a girl
A transgendered, bilingual girl, at that!
You can use one of those doodads that lets you read and write memory cards on a PC, or you can run an app on an already-modded PS2 that writes the file to the card. Admittedly, it's not dead-easy, but at least you only need to do it once :)
That doesn't quite follow -- the important number is the pressure difference between the two sides of the glass. In the shuttle, you've got 1 atm on the inside, or maybe less, and ~0 atm on the outside, for a difference of no more than 1 atm. On the other hand, the pressure deep in the ocean is (lotso) atm, and up here it's ~1 atm, for a difference of about (lotso - 1) atm. Harder than keeping a space shuttle together ;)
When booting a PSX disc, the PS2 reads a file from the memory card for some silly purpose like providing icons for memory card files. As it turns out, the code that reads that file is vulnerable to a buffer overflow, and if exploited properly it allows one to execute any arbitrary ELF code stored on the memory card, the effect of which you can easily imagine.
Yes, I know all that. The point remains that any _released_ kernel (version number without any -pre or -rc or -m2u4+2df) within the 2.6 series is (theoretically) stable. All of the brokenness is supposed to happen in between.
Okay, how about this: why does kernel.org say it's stable? :)