No, this is a crash, or, at least, a premature termination. It runs the installation wizard the first time through, then terminates. I was expecting that; I've seen that behaviour in older milestones. However, on the second and subsequent runs, it gets to the point in its startup process where it would normally open the browser window, and the program exits to the bash prompt without so much as a warning message. It never even opens any sort of X window. I went back and rmed my ~/.mozilla directory and let it go through the install process again, in case the old settings were confusing it somehow, with no luck.
M8 did the same thing to me... I think I skipped M7 for other reasons. M6 was the last one I had where apprunner worked.
That's the only serious bug I've run into with this version... I'm doing my browsing in the Mozilla viewer now, and it's working fine. And the form widgets work! (Can you tell I'm excited about that?;) )
This is good to hear. Despite all the crap the Slack guys have taken for sticking with libc5 for so long, I think their timing is perfect. When glibc2 first came out, a large portion of the software out there, which was all written for libc5, wouldn't compile against it without extensive tweaking. (My personal theory is that that's the reason that so many newbies (which tend to use Red Hat) are convinced that compiling is hard, but that's beside the point...)
Then we reached the point where some things were requiring glibc2, but many things still didn't compile under it, so Slack 4.0 included glibc2, but was still based on the old stable libc5. Now, however, most everything compiles under glibc2, so it's time to make the transition... and that's what Slackware's doing.
Slack 4.0 actually includes glibc2, it just doesn't use it for its primary libc. What it doesn't have that XMMS (which I run pretty constantly) and Mozilla (which I'm actually posting this with) require is thread-safe Xlibs. You can download and install those; it's simple. There's a handy link on the XMMS site, and you just uncompress the tarball into the Xlib directory, and you're good to go.
And.... we have form widgets! And they don't even jump out of the way when I click on them! Woohoo! Mozilla has just joined the ranks of usable web browsers... On the other hand, apprunner doesn't want to work... it crashes silently at the end of its startup spiel. viewer works fine, though. I'm okay with that... I don't need all the junk they packed into apprunner anyway. I've already got a mail client and a newsreader... I just want a good, solid, standards-compliant web browser... This post finely hand-crafted using Mozilla/5.0 (X11; Linux i686).
My dad's workplace used to have a mini (couldn't identify the type... I was very young at the time) that would play the Star-Spangled Banner on the AM band when it was shut down for the night. I think it was the same one where its only response to any kind of syntax error was "EH?", on the theory that, 90% of the time, you'd know what you did wrong without being told...
The text of the agreement has changed (again). So, yes, they've posted before (twice, I think) that NSI has changed their agreement, but that's because this is the third time they've changed the agreement.
There's nothing wrong with vision. Vision is great. Unfortunately, vision statements seldom have any noticable relationship to actual vision. They're usually the result of a bunch of marketroids with delusions of gender^Ograndeur sitting around a conference table with their ties choking off the flow of blood to their brains (if any) and stringing together a bunch of meaningless, polysyllabic words of the sort usually seen only on motivational posters and high-school graduation speeches.
"We will achieve greatness through enhancing the pulchritude of the dominant paradigm of customer-product interaction."
Near as we were able to determine the last time this article popped up, eternity is not the bitty machine, it's a regular old Digital Unix box that's acting as a SLIP router for the bitty machine. If you examine the HTTP response from eternity, you'll notice that it's actually a redirect to another IP and port. If you follow the redirect, you get the page. That's what I found last time, anyway... I can't seem to get through just now to paste the actual HTTP response up...
Xeon cache goes up to 4M, no? Current K7s don't have it yet, but I from what I've heard, the serious server version will have up to 8M... They probably need the new process for those, though...
*At the same clock speed* the PPC may be 30% faster. However, the G3's maximum clock speed is not as high as the Pentium's, so it evens out...
Bah. Doesn't matter... Alpha'll smack 'em both around. Faster than the PPC, Hz for Hz, and with a higher maximum clock than the Pentium...
Thought they had GHz already...
on
Athlon Reviews
·
· Score: 2
Yeah, Intel could drop their prices by 70% and continue making a profit. That's *why* AMD needs the K-7. They can't compete with Intel in the low-end desktop market that they currently hold, because Intel is able to drop their prices to undercut AMD, sell the Celeron at a loss, and make up the difference on overpriced Xeons.
Enter the K-7... performance that smacks the Xeon, Hz for Hz, plus a higher clock, and more scalable to boot... all with a price tag an order of magnitude lower. The K-7's not aimed at the low-end desktop market, it's aimed to take the high-end x86 server market, where all the money is, away from Intel in one fell swoop. With a little help from Compaq (Compaq == DEC && K7_mb == Alpha_mb), and if the new Dresden fab can keep up with demand, they just might be able to pull it off, too...
And didn't Kryotech already have a GHz K-7 prototype running? I could have sworn I saw an article about it here a month or two back...
Never said they'd have to. "Free source" doesn't mean "no binaries". What it means is that people who do know enough to install packages from source can install them on their platform of choice, making tweaks as necessary to get them to compile... and then roll the results up into an binary RPM or some such that ordinary users can learn to install.
People've been saying that for years, if not decades, and it hasn't happened yet. Both the architectures you mention have standard machines for normal end-users out... Corel's Netwinder, in ARM's case, and, as for PPC... well... can you say "Apple Macintosh"?
The problem is that massive base of x86 application code out there, with which any new platform must be binary-compatible in order to stand a chance. With luck, free-source software will change this, by allowing source-compatibility rather than binary-compatibility to be the key.
Wasn't saying they should give everyone a jet... this guy is the only one who tried to claim a Harrier during the period they were running that commercial, no? So give one to him and him only... everyone else missed their chance. And if they decide to advertise that they're giving away Harriers again, they might want to jack the Pepsi-point value up to 250 million or whatever...
I don't see what's so unreasonable about it... sure, jets are expensive, but the guy had to get seven million points for it. Anyone that dedicated deserves the thing. If Pepsi didn't want to give away a Harrier, they shouldn't have offered one. If I was them, I'd get him the jet and write it off as an advertising expense... I know if they did, I'd be buying all the Pepsi I could get my hands on next time they offered to give away a Harrier... I really want a Harrier. They rock.
How much does a Harrier cost, anyway? And what's Pepsi's annual net?
Well, there are the 2.2.xprey kernels... I suspect they don't get as widely tested as they should, though. I know I'm guilty of not trying them out... I try out some (though not all) of the 2.3.xprey kernels, but I've never tried a pre- kernel for one of the stable series, except for the 2.2.0prey kernels... they were more an extension of 2.1, though.
a) Linus decides, presumably based on the degree of change between the versions. I seem to recall seeing somewhere that he thought, in retrospect, that 2.0 should have been 1.4 and the 2.0 version number saved for what became 2.2... Either way, this next version will have only minor changes from 2.2, so it's clearly a 2.4.
b) A feature freeze is when they stop adding new features and concentrate solely on working the stuff that's already there. Some feature freezes are more frozen than others - framebuffers, for example, were added to 2.1 after Linus' announcement that 2.1 was frozen.:)
As for the second part of your question... there's a difference between "stable", "bug-free", and "perfect". If it doesn't crash but doesn't work quite right, either, it's stable but not bug-free. If it does everything correctly but doesn't do everything you want, it's bug-free but not perfect. If it doesn't crash, does everything you could want, and does it correctly, then it's stable, bug-free, and perfect.
Note that for non-trivial pieces of software, "bug-free" and "perfect" are only theoretical conditions... they never happen in practice. There's always one more bug. Some pieces of software get closer than others, though...
Slashdot Mirror
No, this is a crash, or, at least, a premature termination. It runs the installation wizard the first time through, then terminates. I was expecting that; I've seen that behaviour in older milestones. However, on the second and subsequent runs, it gets to the point in its startup process where it would normally open the browser window, and the program exits to the bash prompt without so much as a warning message. It never even opens any sort of X window. I went back and rmed my ~/.mozilla directory and let it go through the install process again, in case the old settings were confusing it somehow, with no luck.
;) )
M8 did the same thing to me... I think I skipped M7 for other reasons. M6 was the last one I had where apprunner worked.
That's the only serious bug I've run into with this version... I'm doing my browsing in the Mozilla viewer now, and it's working fine. And the form widgets work! (Can you tell I'm excited about that?
This is good to hear. Despite all the crap the Slack guys have taken for sticking with libc5 for so long, I think their timing is perfect. When glibc2 first came out, a large portion of the software out there, which was all written for libc5, wouldn't compile against it without extensive tweaking. (My personal theory is that that's the reason that so many newbies (which tend to use Red Hat) are convinced that compiling is hard, but that's beside the point...)
Then we reached the point where some things were requiring glibc2, but many things still didn't compile under it, so Slack 4.0 included glibc2, but was still based on the old stable libc5. Now, however, most everything compiles under glibc2, so it's time to make the transition... and that's what Slackware's doing.
Slack 4.0 actually includes glibc2, it just doesn't use it for its primary libc. What it doesn't have that XMMS (which I run pretty constantly) and Mozilla (which I'm actually posting this with) require is thread-safe Xlibs. You can download and install those; it's simple. There's a handy link on the XMMS site, and you just uncompress the tarball into the Xlib directory, and you're good to go.
And.... we have form widgets! And they don't even jump out of the way when I click on them! Woohoo! Mozilla has just joined the ranks of usable web browsers... On the other hand, apprunner doesn't want to work... it crashes silently at the end of its startup spiel. viewer works fine, though. I'm okay with that... I don't need all the junk they packed into apprunner anyway. I've already got a mail client and a newsreader... I just want a good, solid, standards-compliant web browser... This post finely hand-crafted using Mozilla/5.0 (X11; Linux i686).
Not only is my box connected 24x7, but I give my friends accounts on it, too, and have been known to sell space on it...
I'm not just an addict... I'm a dealer!
My dad's workplace used to have a mini (couldn't identify the type... I was very young at the time) that would play the Star-Spangled Banner on the AM band when it was shut down for the night. I think it was the same one where its only response to any kind of syntax error was "EH?", on the theory that, 90% of the time, you'd know what you did wrong without being told...
So, what they're trying to say is, it's illegal for anyone but Apple to sell tacky, non-upgradable computers?
I can see it now... "GM sues Ford, claims Ford has stolen its intellectual property by manufacturing cars in colors other than black."
Well, this is a small improvement, at least. They're no longer claiming to own my name, address, phone number, and other personal information.
Now if only NSI would abide by their own terms and stop using the database to send me spam...
The text of the agreement has changed (again). So, yes, they've posted before (twice, I think) that NSI has changed their agreement, but that's because this is the third time they've changed the agreement.
There's nothing wrong with vision. Vision is great. Unfortunately, vision statements seldom have any noticable relationship to actual vision. They're usually the result of a bunch of marketroids with delusions of gender^Ograndeur sitting around a conference table with their ties choking off the flow of blood to their brains (if any) and stringing together a bunch of meaningless, polysyllabic words of the sort usually seen only on motivational posters and high-school graduation speeches.
"We will achieve greatness through enhancing the pulchritude of the dominant paradigm of customer-product interaction."
Do you want to be the guy who has to debug a large, armed autonomous vehicle?
"I think we're OW! having a prob OW! lem with the OW! tracking system OW! again..."
Wow, I bet those would make a really great... oh... never mind. They did.
Try "cypherpunk s ". :)
Near as we were able to determine the last time this article popped up, eternity is not the bitty machine, it's a regular old Digital Unix box that's acting as a SLIP router for the bitty machine. If you examine the HTTP response from eternity, you'll notice that it's actually a redirect to another IP and port. If you follow the redirect, you get the page. That's what I found last time, anyway... I can't seem to get through just now to paste the actual HTTP response up...
Xeon cache goes up to 4M, no? Current K7s don't have it yet, but I from what I've heard, the serious server version will have up to 8M... They probably need the new process for those, though...
*At the same clock speed* the PPC may be 30% faster. However, the G3's maximum clock speed is not as high as the Pentium's, so it evens out...
Bah. Doesn't matter... Alpha'll smack 'em both around. Faster than the PPC, Hz for Hz, and with a higher maximum clock than the Pentium...
Yeah, Intel could drop their prices by 70% and continue making a profit. That's *why* AMD needs the K-7. They can't compete with Intel in the low-end desktop market that they currently hold, because Intel is able to drop their prices to undercut AMD, sell the Celeron at a loss, and make up the difference on overpriced Xeons.
Enter the K-7... performance that smacks the Xeon, Hz for Hz, plus a higher clock, and more scalable to boot... all with a price tag an order of magnitude lower. The K-7's not aimed at the low-end desktop market, it's aimed to take the high-end x86 server market, where all the money is, away from Intel in one fell swoop. With a little help from Compaq (Compaq == DEC && K7_mb == Alpha_mb), and if the new Dresden fab can keep up with demand, they just might be able to pull it off, too...
And didn't Kryotech already have a GHz K-7 prototype running? I could have sworn I saw an article about it here a month or two back...
Never said they'd have to. "Free source" doesn't mean "no binaries". What it means is that people who do know enough to install packages from source can install them on their platform of choice, making tweaks as necessary to get them to compile... and then roll the results up into an binary RPM or some such that ordinary users can learn to install.
People've been saying that for years, if not decades, and it hasn't happened yet. Both the architectures you mention have standard machines for normal end-users out... Corel's Netwinder, in ARM's case, and, as for PPC... well... can you say "Apple Macintosh"?
The problem is that massive base of x86 application code out there, with which any new platform must be binary-compatible in order to stand a chance. With luck, free-source software will change this, by allowing source-compatibility rather than binary-compatibility to be the key.
"Obfuscated Perl"? Isn't that redundant?
Yeah, I know... it's possible to write good Perl... it's way too easy to write bad Perl, though. You should see the mess I inherited at work...
Wasn't saying they should give everyone a jet... this guy is the only one who tried to claim a Harrier during the period they were running that commercial, no? So give one to him and him only... everyone else missed their chance. And if they decide to advertise that they're giving away Harriers again, they might want to jack the Pepsi-point value up to 250 million or whatever...
I don't see what's so unreasonable about it... sure, jets are expensive, but the guy had to get seven million points for it. Anyone that dedicated deserves the thing. If Pepsi didn't want to give away a Harrier, they shouldn't have offered one. If I was them, I'd get him the jet and write it off as an advertising expense... I know if they did, I'd be buying all the Pepsi I could get my hands on next time they offered to give away a Harrier... I really want a Harrier. They rock.
How much does a Harrier cost, anyway? And what's Pepsi's annual net?
Eh? 1.2.15? Was that a typo, or should I be upgrading my 1.2.13 laptop?
Well, there are the 2.2.xprey kernels... I suspect they don't get as widely tested as they should, though. I know I'm guilty of not trying them out... I try out some (though not all) of the 2.3.xprey kernels, but I've never tried a pre- kernel for one of the stable series, except for the 2.2.0prey kernels... they were more an extension of 2.1, though.
a) Linus decides, presumably based on the degree of change between the versions. I seem to recall seeing somewhere that he thought, in retrospect, that 2.0 should have been 1.4 and the 2.0 version number saved for what became 2.2... Either way, this next version will have only minor changes from 2.2, so it's clearly a 2.4.
:)
b) A feature freeze is when they stop adding new features and concentrate solely on working the stuff that's already there. Some feature freezes are more frozen than others - framebuffers, for example, were added to 2.1 after Linus' announcement that 2.1 was frozen.
As for the second part of your question... there's a difference between "stable", "bug-free", and "perfect". If it doesn't crash but doesn't work quite right, either, it's stable but not bug-free. If it does everything correctly but doesn't do everything you want, it's bug-free but not perfect. If it doesn't crash, does everything you could want, and does it correctly, then it's stable, bug-free, and perfect.
Note that for non-trivial pieces of software, "bug-free" and "perfect" are only theoretical conditions... they never happen in practice. There's always one more bug. Some pieces of software get closer than others, though...