get a list of all addresses that bounced the last 24 hours?
run the program that indexes the file list (say, updatedb), and after that start the web server again
find the IP address of the box, then send that per mail to the administrator?
Or, to put it more bluntly: your examples are carefully chosen to reflect the kindergarten interface of Windos, but has nothing to do with the Real World. In the Real World, the end user does not know anything about such thing as "color depth", "mounted disks" (come on!) "kernel modules". Show me your login while you're fdisk'ing around. Whose prompt does it show you? Root's? So let root do the tasks that are root's, and lusers tasks that are lusers'.
users frequently perceive easy tasks as being slower than harder ones, even though the reverse is true.
Now you suggest that the GUI is "easy" and the CLI is "hard". What you should suggest, however, is that they're on a different level of "learning". Jerome Bruner, a well known child psychologist, used the terms "kinestethic" (you slam your front door, it makes a sound), "iconic" (you slam any door) and "symbolic" (let's invent types of doors that cannot be slammed) for three levels of learning. A GUI is iconic, CLI is symbolic - whereas IMHO most computer users use their computer as kinestethic.
A GUI is good for things that have icons. "Open the text" - can easily have an icon. However, "tell me which E-mails I sent to the slashdot domain that were bounced" cannot possibly have an icon, and even if it had, the explanation of the icon would be very long and thus make it useless.
Thus, a GUI is good for standardised tasks - those that have an icon equivalent. A CLI is more up to non-standardised stuff.
You don't believe me? Think of a word processor. Starting the word processor is done by an icon. Writing the letter itself is done in plain text. Unless you only want to do a mail merge, in which case most of the text will be referenced to by icons, instead of a text interface.
Thinking of one being a harder task than the other is simply not true. Suggesting that system administration should be done in GUI is IMHO stupid, for the same reason: if it has an icon, it is standard and should not need to be clicked. And if it's non standard, you'ld need a CLI anyway.
Taking bets now: 2.4.X 2.2.Y
on
Linux 2.4.13
·
· Score: 1
Soon X>Y, in 2.4.X and 2.2.Y. Only 6 more to go...
We at Slashdot can help them. Please end the information anarchy. Please stop releasing critical information about Microsoft's managers. It's high time the free speech community stops providing blueprints for writing critical essays about Microsoft's responsibility.
And it's high time that people insisted that the free speech community live up to its obligation to protect them from reality.
Time for a new type of firewall: one where you can actually shoot those nasty packets down - before they infect your IIS.
Moderators with the wrong attitude
on
A New Kind of War
·
· Score: 1
I happened to have 5 moderator points today, and used them.
Something weird struck me. A lot of postings that tried to put the war on terrorism in some kind of perspective (like, for example, someone who wrote about the UK situation, where there's a 30 year history of "war on IRA", nothing won, much lost) seemed to get a "0" penalty.
I better not try to put such moderation in perspective, for I will probably be modded down, too. Draw your own conclusions.
That's silly. Do you really think that a worm will do anything with the HTTP-headers it receives in the answer? The worm connects, does a GET and sends more junk, but no way it listens to a "Redirect:" header.
Ah, must be some windows user who thinks that system administration is done through local keyboard and mouse.
I never visit my customers for upgrades. We do even upgrades remotely. The only thing the customer needs to do is turn on the remote access station and leave it on during the weekend.
It would be quite easy to shut down those PCs, if
there were a "shutdown" command on NT/2k. There isn't; there is one in the Resource Kit but not in the default installation.
Having said that, you could kill off a Windows PC by issueing
GET/scripts/root.exe?/c+SHUTDOWN
Other commands are possible as well:
GET/scripts/root.exe?/c+dir+/s+\ gives you the recursive directory tree. Formatting, starting Fdisk and the like are possible, too.
If someone could post a shutdown.exe somewhere, I'll be glad to provide a simple script that downloads the executable and starts it, thus stopping the IIS machine. Or maybe this is our chance to create Tuxissa:)
The Cringely piece basically says "Mircosoft could misuse its market power to replace TCP/IP", then blah-blahs about how it [cw]ould do that, how it [cw]ould buzz it etc.
Is Slashdot going to publish any article like this? Expect articles about how MS could replace mp3, wav (with wma), html (with ms-html), smtp, pop3 (with mapi), doc (with doc 6.0), etc etc.
Mircosoft is a monopoly. They can change any standard. Nothing can stop them. (Yet).
I remember is Gentus Linux - don't click the link, it is dead now:)
I think Gentus found out that by not releasing modifications, you shoot yourself in the foot: maintenance will be much harder, as the upstream will never incorporate - or even consider - your changes. A new upstream version now means work, instead of relief.
OK. So here is summary number 3. I hope the that because of the citations and the structure it is still a useful addition to the others:)
INTRODUCTION
[...]
MONOPOLIZATION
[...] "The offense of monopolization has two elements: (1)the possession of monopoly power in the relevant market and (2)the willful acquisition or maintenance of that power as distinguished from growth or development as a consequence of a superior product,business acumen,or historic accident." [...]
A. Monopoly Power
[...] "While merely possessing monopoly power is not itself an antitrust violation,[...] it is a necessary element of a monopolization charge [...]...we uphold the District Court s finding of monopoly power in its entirety."
B. Anticompetitive Conduct
[some explanations of principles follow, then the court considers MS's objections]
Licenses Issued to Original Equipment Manufacturers
[...]
"In sum,we hold that with the exception of the one restriction prohibiting automatically launched alternative interfaces,
all the OEM license restrictions at issue represent uses of Microsoft s market power to protect its monopoly,unredeemed by any legitimate justification.The restrictions therefore violate 2 of the Sherman Act."
Integration of IE and Windows
[...]
"Accordingly,Microsoft may not be held liable for this aspect of its product design."
Agreements with Internet Access Providers
[...]
"Accordingly,we affirm the District Court s deci-sion holding that Microsoft s exclusive contracts with IAPs are exclusionary devices,in violation of 2 of the Sherman Act."
Dealings with Internet Content Providers,Independent Software Vendors,and Apple Computer
[...]
Accordingly,we hold that the exclusive deal with Apple is exclusionary,in violation of 2 of the Sherman Act..
Java
a. The incompatible JVM
[...] "Therefore,we reverse the District Court s imposition of liability for Microsoft s development and promotion of its JVM."
b. The First Wave Agreements
[...] "we hold that the provisions in the First Wave Agreements requiring use of Microsoft s JVM as the default are exclusionary,in violation of the Sherman Act."
c. Deception of Java developers
[...] "Accordingly,we conclude this conduct is exclusionary, in violation of 2 of the Sherman Act."
d. The threat to Intel
[...] "Therefore we affirm the conclusion that Microsoft s threats to Intel were exclusionary,in violation of 2 of the Sherman Act."
Course of Conduct
[...] "Because the District Court identifies no other specific acts as a basis for course of conduct liability,we reverse its conclusion that Microsoft s course of conduct separately violates 2 of the Sherman Act."
C. Causation
"[...]Microsoft urges this court to reverse on the monopoly maintenance claim, because plaintiffs never established a causal link between Microsofts anticompetitive conduct, [...]and the maintenance of Microsofts operating system monopoly."
[...]
"We disagree."
ATTEMPTED MONOPOLIZATION
[...] "This,in turn,requires plaintiffs (1)to define the relevant market and (2)to demonstrate that substantial barriers to entry protect that market. Because plaintiffs have not carried their burden on either prong,we reverse without remand."
TYING
[...]
"Accordingly,we vacate the District Court s finding of a per se tying violation and remand the case.Plaintiffs may on remand pursue their tying claim under the rule of reason."
TRIAL PROCEEDINGS AND REMEDY
[...]
"We conclude,however,that the District Courts remedies decree must be vacated for three independent reasons:(1)the court failed to hold a remedies-specific evidentiary hearing when there were disputed facts;(2)the court failed to provide adequate reasons for its decreed remedies; and (3)this Court has revised the scope of Microsoft s liability and it is impossible to determine to what extent that should affect the remedies provisions."
JUDICIAL MISCONDUCT
"[the law] requires federal judges to avoid public comment on the merits of [ ]pending or impending cases [...] avoid impropriety and the appearance of impropriety in all activities, on the bench and off [...] to initiate or consider ex parte communications on the merits of pending or impending proceedings [...] to recuse themselves when their impartiality might reasonably be questioned. [...] All indications are that the District Judge violated each of these ethical precepts by talking about the case with reporters. The violations were deliberate,repeated,egregious,and flagrant. The only serious question is what consequences should follow."
"[...] leads us to conclude that the appropriate remedy for the violations of 455(a)is disqualification of the District Judge retroactive only to the date he entered the order breaking up Microsoft.We therefore will vacate that order in its entirety and remand this case to a different District Judge,but will not set aside the existing Findings of Fact or Conclusions of Law (except insofar as specific findings are clearly erroneous or legal conclusions are incorrect)."
CONCLUSION
The judgment of the District Court is affirmed in part, reversed in part,and remanded in part.We vacate in full the Final Judgment embodying the remedial order,and remand the case to the District Court for reassignment to a different trial judge for further proceedings consistent with this opinion.
OSI Open Source definition reads:
9. The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software. [italics are mine].
This is obviously an attempt to make something which can never be approved as an Open Source license. MS is learning fast, don't you think?;-)
You actually need four hours to install an OS? Last Linux machine I installed (an AMD 700/64Mb) took me exactly 45 minutes. Yes, 45 minutes, including E-mail, desktop, "service packs" (you mean: "latest software", don't you??) and dual boot. I did that remotely, by having the machine boot from NFS so I could log into it. (Well all right, the customer changed a floppy disk). This was done without a disk image. So don't you tell me "Windows installation is easy". It's a bloody nightmare. Yes, I'm serious: you need to be on-site, sit there, change CD's, answer stupid questions, wait, wait and wait. "And get paid" yeah right. Yuck!
So if Kevin Reichard cannot run Linux on his desktops, Linux on the desktop is dead?
I work in a small IT company that supports Linux on desktops in various, non-IT-related companies. It works like a charm. But not, I repeat, not if you try to run Linux as the regular computer OS where the user is supposed to help clicking to keep the machine running. That is stupid. The idea of building GUI applications to control the underlying OS is stupid. No, this is not a troll. I'm just sharing my experiences of 2 years of system maintenance on Linux machines. Adding a user is 2 minutes of work. But once you install webmin, you'll get called three times for every simple task, to ask if this or that should really be clicked, how it works, where the home directory should be, etc etc. Once you let the Kevin Reichards on this planet do system maintenance, they start whining because they can't find this-or-that.
The great thing about Linux on the desktop is that it works and keeps working, without bit rot. You can install, maintain and upgrade the machine remotely. The associated costs with various "now this problem", "now that problem" is near to zero. No viruses, no "non corporate" looks on the desktop because the luser installed some nasty screen saver;-)
The Corel and Eazel cases are not chosen that well either. Corel tried to build a distro that anyone could install. They succeeded. But no one was waiting for it and we all knew that beforehand. Same with Eazel. A file manager with services, like "easy software upgrades" (AFAIK). Isn't that root's job?
The remark that "nothing that works as well as MS Office" is not true. The German C'T Magazine (from Heisse Verlag) tests office suites once in a while. StarOffice is as good as MS Office (and a lot better when it comes to correct text/table/graphics placement. There's simply no software around that works as weird as Word in this case).
I'd like to invite Kevin Reichard to come over to the Netherlands, to view a law firm, a publisher, a stock broker or a consultancy firm, all running linux on the desktop. For two years now, doing daily work. And still going strong.
The 7805 is a passive regulator. That means if your CD player needs like 1A, 5V, your 7805 will dissipate 1A * (12-5)V = 7 W. That is a *lot* of heat, (the case is 50/W junction/ambient). Then take into consideration that cars are not too cold anyway and might want to consider active voltage regulation.
There is a date/time stamp on the Yahoo story, and it's just what it looks like: May 14, 2001. The Slashdot crew is not to blame here: Yahoo! Small Business, Technology section made it a feature today. The link to entrepreneur.com that Yahoo has, has no references to this story. It seems Yahoo! is at fault here.
Tweakers.net ran the same story today, but instead it said "Microsoft opens up source". Cough!
In fact, once you've read the MS sources, you've effectively left the Open Source camp, as any MS NDA these days is incompatible with GPL or even BSD license.
Microsoft is against freedom of speech!, how's that for FUD?;-)
Slashdot Mirror
We're awaiting x>y (in 2.4.x and 2.2.y).
- get a list of all addresses that bounced the last 24 hours?
- run the program that indexes the file list (say, updatedb), and after that start the web server again
- find the IP address of the box, then send that per mail to the administrator?
Or, to put it more bluntly: your examples are carefully chosen to reflect the kindergarten interface of Windos, but has nothing to do with the Real World. In the Real World, the end user does not know anything about such thing as "color depth", "mounted disks" (come on!) "kernel modules". Show me your login while you're fdisk'ing around. Whose prompt does it show you? Root's? So let root do the tasks that are root's, and lusers tasks that are lusers'.Now you suggest that the GUI is "easy" and the CLI is "hard". What you should suggest, however, is that they're on a different level of "learning". Jerome Bruner, a well known child psychologist, used the terms "kinestethic" (you slam your front door, it makes a sound), "iconic" (you slam any door) and "symbolic" (let's invent types of doors that cannot be slammed) for three levels of learning. A GUI is iconic, CLI is symbolic - whereas IMHO most computer users use their computer as kinestethic.
A GUI is good for things that have icons. "Open the text" - can easily have an icon. However, "tell me which E-mails I sent to the slashdot domain that were bounced" cannot possibly have an icon, and even if it had, the explanation of the icon would be very long and thus make it useless.
Thus, a GUI is good for standardised tasks - those that have an icon equivalent. A CLI is more up to non-standardised stuff.
You don't believe me? Think of a word processor. Starting the word processor is done by an icon. Writing the letter itself is done in plain text. Unless you only want to do a mail merge, in which case most of the text will be referenced to by icons, instead of a text interface.
Thinking of one being a harder task than the other is simply not true. Suggesting that system administration should be done in GUI is IMHO stupid, for the same reason: if it has an icon, it is standard and should not need to be clicked. And if it's non standard, you'ld need a CLI anyway.
Soon X>Y, in 2.4.X and 2.2.Y. Only 6 more to go...
And it's high time that people insisted that the free speech community live up to its obligation to protect them from reality.
Time for a new type of firewall: one where you can actually shoot those nasty packets down - before they infect your IIS.
Something weird struck me. A lot of postings that tried to put the war on terrorism in some kind of perspective (like, for example, someone who wrote about the UK situation, where there's a 30 year history of "war on IRA", nothing won, much lost) seemed to get a "0" penalty.
I better not try to put such moderation in perspective, for I will probably be modded down, too. Draw your own conclusions.
(Going to metamoderate right away :)
Oh jeetje. Dit is een test die minpunten moet krijgen.
That's silly. Do you really think that a worm will do anything with the HTTP-headers it receives in the answer? The worm connects, does a GET and sends more junk, but no way it listens to a "Redirect:" header.
How about saying 8 centimeters if it is 8 centimeters?
Ah, must be some windows user who thinks that system administration is done through local keyboard and mouse.
I never visit my customers for upgrades. We do even upgrades remotely. The only thing the customer needs to do is turn on the remote access station and leave it on during the weekend.
Having said that, you could kill off a Windows PC by issueing
GET /scripts/root.exe?/c+SHUTDOWN
Other commands are possible as well: GET /scripts/root.exe?/c+dir+/s+\ gives you the recursive directory tree. Formatting, starting Fdisk and the like are possible, too.
If someone could post a shutdown.exe somewhere, I'll be glad to provide a simple script that downloads the executable and starts it, thus stopping the IIS machine. Or maybe this is our chance to create Tuxissa :)
Is Slashdot going to publish any article like this? Expect articles about how MS could replace mp3, wav (with wma), html (with ms-html), smtp, pop3 (with mapi), doc (with doc 6.0), etc etc.
Mircosoft is a monopoly. They can change any standard. Nothing can stop them. (Yet).
I think Gentus found out that by not releasing modifications, you shoot yourself in the foot: maintenance will be much harder, as the upstream will never incorporate - or even consider - your changes. A new upstream version now means work, instead of relief.
[...]
[...] "The offense of monopolization has two elements: (1)the possession of monopoly power in the relevant market and (2)the willful acquisition or maintenance of that power as distinguished from growth or development as a consequence of a superior product,business acumen,or historic accident." [...]
[...] "While merely possessing monopoly power is not itself an antitrust violation,[...] it is a necessary element of a monopolization charge [...]
[some explanations of principles follow, then the court considers MS's objections]
[...] "In sum,we hold that with the exception of the one restriction prohibiting automatically launched alternative interfaces,
all the OEM license restrictions at issue represent uses of Microsoft s market power to protect its monopoly,unredeemed by any legitimate justification.The restrictions therefore violate 2 of the Sherman Act."
[...] "Accordingly,Microsoft may not be held liable for this aspect of its product design."
[...] "Accordingly,we affirm the District Court s deci-sion holding that Microsoft s exclusive contracts with IAPs are exclusionary devices,in violation of 2 of the Sherman Act."
[...] Accordingly,we hold that the exclusive deal with Apple is exclusionary,in violation of 2 of the Sherman Act..
[...] "Therefore,we reverse the District Court s imposition of liability for Microsoft s development and promotion of its JVM."
[...] "we hold that the provisions in the First Wave Agreements requiring use of Microsoft s JVM as the default are exclusionary,in violation of the Sherman Act."
[...] "Accordingly,we conclude this conduct is exclusionary, in violation of 2 of the Sherman Act."
[...] "Therefore we affirm the conclusion that Microsoft s threats to Intel were exclusionary,in violation of 2 of the Sherman Act."
[...] "Because the District Court identifies no other specific acts as a basis for course of conduct liability,we reverse its conclusion that Microsoft s course of conduct separately violates 2 of the Sherman Act."
C. Causation
"[...]Microsoft urges this court to reverse on the monopoly maintenance claim, because plaintiffs never established a causal link between Microsofts anticompetitive conduct, [...]and the maintenance of Microsofts operating system monopoly." [...]
"We disagree."
ATTEMPTED MONOPOLIZATION
[...] "This,in turn,requires plaintiffs (1)to define the relevant market and (2)to demonstrate that substantial barriers to entry protect that market. Because plaintiffs have not carried their burden on either prong,we reverse without remand."
TYING
[...] "Accordingly,we vacate the District Court s finding of a per se tying violation and remand the case.Plaintiffs may on remand pursue their tying claim under the rule of reason."
TRIAL PROCEEDINGS AND REMEDY
[...] "We conclude,however,that the District Courts remedies decree must be vacated for three independent reasons:(1)the court failed to hold a remedies-specific evidentiary hearing when there were disputed facts;(2)the court failed to provide adequate reasons for its decreed remedies; and (3)this Court has revised the scope of Microsoft s liability and it is impossible to determine to what extent that should affect the remedies provisions."
JUDICIAL MISCONDUCT
"[the law] requires federal judges to avoid public comment on the merits of [ ]pending or impending cases [...] avoid impropriety and the appearance of impropriety in all activities, on the bench and off [...] to initiate or consider ex parte communications on the merits of pending or impending proceedings [...] to recuse themselves when their impartiality might reasonably be questioned. [...] All indications are that the District Judge violated each of these ethical precepts by talking about the case with reporters. The violations were deliberate,repeated,egregious,and flagrant. The only serious question is what consequences should follow."
"[...] leads us to conclude that the appropriate remedy for the violations of 455(a)is disqualification of the District Judge retroactive only to the date he entered the order breaking up Microsoft.We therefore will vacate that order in its entirety and remand this case to a different District Judge,but will not set aside the existing Findings of Fact or Conclusions of Law (except insofar as specific findings are clearly erroneous or legal conclusions are incorrect)."
CONCLUSION
The judgment of the District Court is affirmed in part, reversed in part,and remanded in part.We vacate in full the Final Judgment embodying the remedial order,and remand the case to the District Court for reassignment to a different trial judge for further proceedings consistent with this opinion.
Better ask yourself if programming needs this kind of promotion.
OSI Open Source definition reads: ;-)
9. The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software. [italics are mine].
This is obviously an attempt to make something which can never be approved as an Open Source license. MS is learning fast, don't you think?
Duh. Where's the killer rabbit?
I don't think it's a problem. You don't need to click a word that has a smart tag - only if you want to. That's what Microsoft has been good at all the time: do what the users ask for.
Linux dead? Duh. That's what they said about Elvis.
You actually need four hours to install an OS? Last Linux machine I installed (an AMD 700/64Mb) took me exactly 45 minutes. Yes, 45 minutes, including E-mail, desktop, "service packs" (you mean: "latest software", don't you??) and dual boot. I did that remotely, by having the machine boot from NFS so I could log into it. (Well all right, the customer changed a floppy disk). This was done without a disk image. So don't you tell me "Windows installation is easy". It's a bloody nightmare. Yes, I'm serious: you need to be on-site, sit there, change CD's, answer stupid questions, wait, wait and wait. "And get paid" yeah right. Yuck!
I work in a small IT company that supports Linux on desktops in various, non-IT-related companies. It works like a charm. But not, I repeat, not if you try to run Linux as the regular computer OS where the user is supposed to help clicking to keep the machine running. That is stupid. The idea of building GUI applications to control the underlying OS is stupid. No, this is not a troll. I'm just sharing my experiences of 2 years of system maintenance on Linux machines. Adding a user is 2 minutes of work. But once you install webmin, you'll get called three times for every simple task, to ask if this or that should really be clicked, how it works, where the home directory should be, etc etc. Once you let the Kevin Reichards on this planet do system maintenance, they start whining because they can't find this-or-that.
The great thing about Linux on the desktop is that it works and keeps working, without bit rot. You can install, maintain and upgrade the machine remotely. The associated costs with various "now this problem", "now that problem" is near to zero. No viruses, no "non corporate" looks on the desktop because the luser installed some nasty screen saver ;-)
The Corel and Eazel cases are not chosen that well either. Corel tried to build a distro that anyone could install. They succeeded. But no one was waiting for it and we all knew that beforehand. Same with Eazel. A file manager with services, like "easy software upgrades" (AFAIK). Isn't that root's job?
The remark that "nothing that works as well as MS Office" is not true. The German C'T Magazine (from Heisse Verlag) tests office suites once in a while. StarOffice is as good as MS Office (and a lot better when it comes to correct text/table/graphics placement. There's simply no software around that works as weird as Word in this case). I'd like to invite Kevin Reichard to come over to the Netherlands, to view a law firm, a publisher, a stock broker or a consultancy firm, all running linux on the desktop. For two years now, doing daily work. And still going strong.
The 7805 is a passive regulator. That means if your CD player needs like 1A, 5V, your 7805 will dissipate 1A * (12-5)V = 7 W. That is a *lot* of heat, (the case is 50/W junction/ambient). Then take into consideration that cars are not too cold anyway and might want to consider active voltage regulation.
V.
In fact, once you've read the MS sources, you've effectively left the Open Source camp, as any MS NDA these days is incompatible with GPL or even BSD license.
Microsoft is against freedom of speech!, how's that for FUD? ;-)