I really take issue with Jim's memo - the feature list MS is trying to fulfill, the list they say is what their customers want, still does not include a decent, 21st-century web browser! I mean, come on. This is rediculous. They have to bundle a decent browser.
What constitutes a decent browser? One that has built-in vector graphics rendering would be nice (no plug-in). One that has complete and really good CSS1 support. One that does not render really broken pages would be nice, too. One that is not easy to 0wn. One that has good popup controls. Tabbed browsing would be good, too.
I use CF cards for totin' stuff home quite a bit. The readers are $30. I've heard you can't countinuously rewrite them, but for dumping files off at the end of the day, I've never had a problem.
2GB cards appear to start at $133 on pricewatch.
I've heard other folks have had trouble with these wearing out, though.
Sources reveal the general plot of the new movie is as follows:
- The Klingons, in the early days of interstellar travel, bump up with the Federation starship USS Ronald Reagan.
- Fast forward several years, and the Klingons are shown in peace treaty negotiations with the Feds.
- Admiral Dumbass of the Reagan opens a mail attachment from the Klingons and nudges it in his SUN 3-D file browser he keeps aroud for nostalgia. The ancient ELF binary he executed exploits a new mmap() bug previously unknown to humankind. The Federation starship computers still have fragments of the memory management code from an old computer system kernel called Linux, which the Klingons obtained by extracting from one of millions of old CD-R's they detected in landfills while touring the earth's surface.
- The bloodthirsty Klingons attempt to terminate humankind turing their computers against them, adapting the instructions in the Linux Coffemaker-HOWTO to generate saber-wielding androids from scrap Macintoshes and Mr. Coffees.
- After a long battle, the Federation regains control of earths computers by writing a worm which replaced the infected computers' kernels with a Mach microkernel-derivative.
- Richard Stallman, who became a member of the Q continuum, appears to Admiral Dumbass to congratulate him for his part in saving humanity (his Spock/Data variant character, of course, came up with the viral cure, but gets no credit). He proceeds to tell Admiral Dumbass that the Federation should really be called the GNU/Federation...
...an airhead guinea pig! But thank the Lord he is doing OK. It is wonderful to hear just plain good technologically-related news once in awhile amidst the controversy surrounding most news.
They are in violation of the part of the.COM TLD Agreement which specifies that they must comply with the IETF RFC's, and probably are similarly in violation of their other contracts.
It seems the author of the article wished to place emphasis on certain words in the article. I contend that he went about achieving his end with the incorrect means.
HTML has provided authors with a means of deliniating emphasized content since version 2.0 and this means has not been depricated since.
The following is taken from RFC 1866:
5.7.1.3. Emphasis: EM
The <EM> element indicates an emphasized phrase, typically
rendered as italics. For example:
A singular subject <em>always</em> takes a singular verb.
This is the best way for authors to indicate emphasized content because user agents may then style the content according to a stylesheet. For example, a user agent may perform a text transform to all capitals (which would achieve the effect he created), boldface the content, or raise the volume of the content (for an aural browser).
It should be noted that Slashdot is written in accordance with the HTML 3.2 Reccomendation from the W3. Comments, since they are displayed under this doctype, should follow spec.
One more crippling bombshell hit the already beleaguered SCO* executives when IDC confirmed that SCO* market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that SCO* has lost more market share, this news serves to reinforce what we've known all along. SCO* is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin [amdest.com] to predict SCO's future. The hand writing is on the wall: SCO faces a bleak future. In fact there won't be any future at all for SCO because SCO* is dying. Things are looking very bad for SCO. As many of us are already aware, SCO* continues to lose market share. Red ink flows like a river of blood.
SCO UnixWare is the most endangered of them all, having lost 93% of its support contracts. The sudden and unpleasant departures of long time SCO licensees IBM and Sequent after their compelled release by Novell only serve to underscore the point more clearly. There can no longer be any doubt: SCO* is dying.
Let's keep to the facts and look at the numbers.
SCO leader Darl McBride states that there are 7000000 users of SCO SVRX IP. How many users of SVRX IP are there? Let's see. The number of lines of code contributed by IBM/Sequent to Linux versus other developers is roughly in ratio of 1 to 50000. Wait, who gives a shit, because IBM and Sequrent own the frikkin copyrights to their own homemade code. Therefore, there are about 70,000 users of SCO SVRX IP, when they use the cash registers between burger flips at MickeyD's. A recent article put SCO * at about 0 percent of the *NIX market. Therefore there are a hell of a lot of *NIX users out there, but pretty much all of them think SCO * sucks, probably even the current SCO * users. This is consistent with the vendor lock-in and litigation business models which SCO is no doubt attempting to patent.
Due to the troubles of SVRX licensing, abysmal sales and so on, Novell went out of the *NIX business and and turned its aboslutely worthless IP over to gullable SCO. Now SCO is dead, its corpse turned over to yet another charnel house. All that remains of Caldera is a legal team and a stupid-ass CEO.
All major surveys show that SCO * has steadily declined in market share. SCO * is very sick and its long term survival prospects are very dim. If SCO * is to survive at all it will be among POS POS boxen found on Ebay. SCO * continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, SCO * is dead.
I think this would either require truly programmable pointer hardware (which I don't think exists) or some new functions built into Xlib (which may or may not be easy to do). You may know better than I, but I think that Xlib actually translates pointer button patterns into abstracted events and sends them to applications that way (a double click is sent as a double click, not as two clicks in quick succession). I have not read the Xlib docs, but I will. IMHO, you raise a very important issue. Kudos.
I think that the questioner has some misconceptions about "mice" as they relate to "Linux".
Mice are not (generally) programmable. You can change the way your computer programs handle the input given them by the Linux kernel from mice. Most programs do not talk to the kernel directly about mice; they use a "middleman" program, which is in most cases X (for GUI applications) or gpm.
These middleman programs have ways of swapping the meanings of the pressed buttons. The link in the parent comment shows how to do it for graphical applications running as clients to an XFree86 X server, which is likely the middleman program for the software the questioner wants to use on pretty much any stock GNU/Linux or BSD system.
If SCO is going to seek damages for its distribution of AIX after license termination (which Novell and IBM claim it cannot do), can we then as folks who have contributed code to GNU and Linux and all the GPL'd goodies not seek damages from SCO in a class action suit for their violations of the GPL? It seems that they revoked their copy permission long ago by distributing GPL'd works linked to code they licensed non-freely. And they still distribute schtuff to Caldera clients. I'm sure someone would be willing to bankroll that.
Although the article doesn't say a whole lot, I've got to agree with the whole need for clustering thing. Although there is some clustering software that runs *on top* of Linux, two Linux separate kernels on two separate CPU's on two separate motherboards have yet to be able to share the same SCSI bus. I'm talking VMS-style clustering. DEC handled most of that stuff in the kernel.
I know the focus has been on the desktop lately, but that stuff is largely not a concern to kernel folks. It really has nothing to do with Linux at all - so why does it keep cropping up in discussion about Linux? Frankly, I could care less what kernel underlies my GNU, X11 and KDE or GNOME as long as the hardware interfacing, scheduling and memory management are good.
Linux's thing-going-for-it right now is hardware interfacing. Linux probably supports more pieces of hardware than any other kernel, including the NT kernels and UNIX kernels. If that could be cluster-abstracted, it would be a beautiful thing.
Lets all take a look at what Netcraft has to say about SCO's hosting setup today...
Hmmm... looks like they switched operating systems on January 27, 2004. Notice the table at the bottom of the page. They used to be running Apache on a Linux kernel up until today. Now it is Apache on 'unknown'. Perhaps that explains the downtime.
/me places tounge in cheek
They might be switching from GNU/Linux systems to something a little bit more suited to enterprise environments.
Slashdot Mirror
AAA Internet TripTik is very good and works in Firefox. I think you have to be a member of AAA, though. It allows multiple destinations, etc.
AAA website
Yes, you can, if the particular item is in the public domain. Libraries inventory media both encumbered by copyright and unencumbered (public domain).
They are public libraries.
I really take issue with Jim's memo - the feature list MS is trying to fulfill, the list they say is what their customers want, still does not include a decent, 21st-century web browser! I mean, come on. This is rediculous. They have to bundle a decent browser.
What constitutes a decent browser? One that has built-in vector graphics rendering would be nice (no plug-in). One that has complete and really good CSS1 support. One that does not render really broken pages would be nice, too. One that is not easy to 0wn. One that has good popup controls. Tabbed browsing would be good, too.
I use CF cards for totin' stuff home quite a bit. The readers are $30. I've heard you can't countinuously rewrite them, but for dumping files off at the end of the day, I've never had a problem.
2GB cards appear to start at $133 on pricewatch.
I've heard other folks have had trouble with these wearing out, though.
Imagine a Beowulf cluster of those!
Parallel extermination!
http://www.caldera.com/developers/gabi/2000-07-17/ contents.html
Tin-foil key fob covers... patent pending.
Pascal is a great learning language, especially for procedural programming. It sucks for OOP, but who cares? This is your mom.
It's got all you need - libraries (units), pointers, easy syntax (Begin, End, etc). Compilers are free, and it translates well into C.
Sources reveal the general plot of the new movie is as follows:
- The Klingons, in the early days of interstellar travel, bump up with the Federation starship USS Ronald Reagan.
- Fast forward several years, and the Klingons are shown in peace treaty negotiations with the Feds.
- Admiral Dumbass of the Reagan opens a mail attachment from the Klingons and nudges it in his SUN 3-D file browser he keeps aroud for nostalgia. The ancient ELF binary he executed exploits a new mmap() bug previously unknown to humankind. The Federation starship computers still have fragments of the memory management code from an old computer system kernel called Linux, which the Klingons obtained by extracting from one of millions of old CD-R's they detected in landfills while touring the earth's surface.
- The bloodthirsty Klingons attempt to terminate humankind turing their computers against them, adapting the instructions in the Linux Coffemaker-HOWTO to generate saber-wielding androids from scrap Macintoshes and Mr. Coffees.
- After a long battle, the Federation regains control of earths computers by writing a worm which replaced the infected computers' kernels with a Mach microkernel-derivative.
- Richard Stallman, who became a member of the Q continuum, appears to Admiral Dumbass to congratulate him for his part in saving humanity (his Spock/Data variant character, of course, came up with the viral cure, but gets no credit). He proceeds to tell Admiral Dumbass that the Federation should really be called the GNU/Federation...
but no more spoilers. You will have to go see it.
Live Long and Prosper
...they want their protocol back!
...an airhead guinea pig! But thank the Lord he is doing OK. It is wonderful to hear just plain good technologically-related news once in awhile amidst the controversy surrounding most news.
Verisign has very explicit contracts for operating the TLD's and their respective nameservers.
.COM TLD Agreement which specifies that they must comply with the IETF RFC's, and probably are similarly in violation of their other contracts.
They are in violation of the part of the
I should have said that since the code output from Slash is topped by an HTML 3.2 DOCTYPE declaration, Slashdot is intended to be written in HTML 3.2.
+1 Humility
It seems the author of the article wished to place emphasis on certain words in the article. I contend that he went about achieving his end with the incorrect means.
HTML has provided authors with a means of deliniating emphasized content since version 2.0 and this means has not been depricated since.
The following is taken from RFC 1866:
5.7.1.3. Emphasis: EM
The <EM> element indicates an emphasized phrase, typically
rendered as italics. For example:
A singular subject <em>always</em> takes a singular verb.
This is the best way for authors to indicate emphasized content because user agents may then style the content according to a stylesheet. For example, a user agent may perform a text transform to all capitals (which would achieve the effect he created), boldface the content, or raise the volume of the content (for an aural browser).
It should be noted that Slashdot is written in accordance with the HTML 3.2 Reccomendation from the W3. Comments, since they are displayed under this doctype, should follow spec.
It is official; Netcraft confirms: SCO* is dying.
One more crippling bombshell hit the already beleaguered SCO* executives when IDC confirmed that SCO* market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that SCO* has lost more market share, this news serves to reinforce what we've known all along. SCO* is collapsing in complete disarray, as fittingly exemplified by failing dead last [samag.com] in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin [amdest.com] to predict SCO's future. The hand writing is on the wall: SCO faces a bleak future. In fact there won't be any future at all for SCO because SCO* is dying. Things are looking very bad for SCO. As many of us are already aware, SCO* continues to lose market share. Red ink flows like a river of blood.
SCO UnixWare is the most endangered of them all, having lost 93% of its support contracts. The sudden and unpleasant departures of long time SCO licensees IBM and Sequent after their compelled release by Novell only serve to underscore the point more clearly. There can no longer be any doubt: SCO* is dying.
Let's keep to the facts and look at the numbers.
SCO leader Darl McBride states that there are 7000000 users of SCO SVRX IP. How many users of SVRX IP are there? Let's see. The number of lines of code contributed by IBM/Sequent to Linux versus other developers is roughly in ratio of 1 to 50000. Wait, who gives a shit, because IBM and Sequrent own the frikkin copyrights to their own homemade code. Therefore, there are about 70,000 users of SCO SVRX IP, when they use the cash registers between burger flips at MickeyD's. A recent article put SCO * at about 0 percent of the *NIX market. Therefore there are a hell of a lot of *NIX users out there, but pretty much all of them think SCO * sucks, probably even the current SCO * users. This is consistent with the vendor lock-in and litigation business models which SCO is no doubt attempting to patent.
Due to the troubles of SVRX licensing, abysmal sales and so on, Novell went out of the *NIX business and and turned its aboslutely worthless IP over to gullable SCO. Now SCO is dead, its corpse turned over to yet another charnel house. All that remains of Caldera is a legal team and a stupid-ass CEO.
All major surveys show that SCO * has steadily declined in market share. SCO * is very sick and its long term survival prospects are very dim. If SCO * is to survive at all it will be among POS POS boxen found on Ebay. SCO * continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, SCO * is dead.
Fact: SCO * is dying
I think this would either require truly programmable pointer hardware (which I don't think exists) or some new functions built into Xlib (which may or may not be easy to do). You may know better than I, but I think that Xlib actually translates pointer button patterns into abstracted events and sends them to applications that way (a double click is sent as a double click, not as two clicks in quick succession). I have not read the Xlib docs, but I will. IMHO, you raise a very important issue. Kudos.
I think that the questioner has some misconceptions about "mice" as they relate to "Linux".
Mice are not (generally) programmable. You can change the way your computer programs handle the input given them by the Linux kernel from mice. Most programs do not talk to the kernel directly about mice; they use a "middleman" program, which is in most cases X (for GUI applications) or gpm.
These middleman programs have ways of swapping the meanings of the pressed buttons. The link in the parent comment shows how to do it for graphical applications running as clients to an XFree86 X server, which is likely the middleman program for the software the questioner wants to use on pretty much any stock GNU/Linux or BSD system.
Here is the xmodmap documentation you are looking for.
If SCO is going to seek damages for its distribution of AIX after license termination (which Novell and IBM claim it cannot do), can we then as folks who have contributed code to GNU and Linux and all the GPL'd goodies not seek damages from SCO in a class action suit for their violations of the GPL? It seems that they revoked their copy permission long ago by distributing GPL'd works linked to code they licensed non-freely. And they still distribute schtuff to Caldera clients. I'm sure someone would be willing to bankroll that.
Although the article doesn't say a whole lot, I've got to agree with the whole need for clustering thing. Although there is some clustering software that runs *on top* of Linux, two Linux separate kernels on two separate CPU's on two separate motherboards have yet to be able to share the same SCSI bus. I'm talking VMS-style clustering. DEC handled most of that stuff in the kernel.
I know the focus has been on the desktop lately, but that stuff is largely not a concern to kernel folks. It really has nothing to do with Linux at all - so why does it keep cropping up in discussion about Linux? Frankly, I could care less what kernel underlies my GNU, X11 and KDE or GNOME as long as the hardware interfacing, scheduling and memory management are good.
Linux's thing-going-for-it right now is hardware interfacing. Linux probably supports more pieces of hardware than any other kernel, including the NT kernels and UNIX kernels. If that could be cluster-abstracted, it would be a beautiful thing.
Lets all take a look at what Netcraft has to say about SCO's hosting setup today...
/me places tounge in cheek
Hmmm... looks like they switched operating systems on January 27, 2004. Notice the table at the bottom of the page. They used to be running Apache on a Linux kernel up until today. Now it is Apache on 'unknown'. Perhaps that explains the downtime.
They might be switching from GNU/Linux systems to something a little bit more suited to enterprise environments.