It appears to me that most of the people who have commented on this do not understand the real significance of the article.
As someone who has been scouring the Internet for several days looking for detailed, informative and useful information about how to create a bootable Linux CD, I find this article to be a godsend. In particular, it indicates why the boot image must be in diskette format, and how to fit what's needed into 1440K.
And finally, gaming is just one application. Others are limited only by the imagination.
Close, I think. Wine has been plugging away at a moving target for many years, and is still nowhere near ready for prime time. My guess is M$ wants Corel's Wine developers so they can engineer a Wine-like product that really works, though perhaps proprietary. That would be a huge insurance policy against the success of Linux.
The way to deal with this is to design in a hardware-level interface that abstracts out the trade secrets. The driver should just be an interface to the operating system, not the essence of the product.
We've investigated a number of possible solutions, but they all have shortcomings.
Why didn't you tell us what solutions you looked at, and why they were not acceptable??? This question as asked is grossly inconsiderate, guaranteed to waste your time and ours with useless replies.
After reading the article, and as one who has done a fair bit of programming using TCP, I can only see this as a solution to a non-problem. One you've figured out your client/server application requirements, implementing what you need on top of TCP or UDP in a suitable way is just not that big a deal.
I wish all these brilliant minds would work on providing unique and interesting Internet content, which is the part that is sorely needed now.
Gnucash is written in such a way that the transaction engine is independent of the front end. In this way, it would be a relatively straightforward task to write the front-end for KDE...
It already works under KDE. You don't need the Gnome desktop, just its libraries.
Recently I set up a dual-boot Linux and Win98SE for a client. I purchased the latter from one of my distributors. On opening it up, I saw on the included manual it said that the computer vendor was required to affix the Certificate of Authenticity to the computer's case.
Beats me what requires me to do that - certainly nothing I agreed to! I stuck it on the manual, and would have preferred to stick it somewhere else, except he wasn't around.
Have you ever tried installing Windows 9x on one system and then move it to a system with different components? The OS will barf when it boots. It will see a million different components fro the last time it booted and it will simply barf.
True.
It would be very similar to installing linux one one system with a custom kernel, and then moving that drive to another system. There is a good chance it wont boot because all of the drivers are wrong.
Not true. Linux is very tolerant of changes in the platform. I do this all the time in the course of building systems for clients. Just avoid Kudzu.
The stock market might be considered the best estimator of how this will all play out. Investors as a whole are pretty savvy, otherwise they couldn't afford to do what they do.
MS stock is currently around, oh, 60-70% of where it might be without the antitrust situation. Considering the company's market capitalization, that's one hell of an impact.
I think everyone knows it will be a couple of years before MS has to actually comply with anything. However what has happened that matters is a very formal, very public, very credible statement by the court that MS is managed and controlled by a collection of lying, ruthless, untrustworthy scoundrels.
The other thing that's real is Linux, KDE, Gnome and the rapidly increasing credibility of alternative computing solutions, especially on the desktop. We're not there yet, but another 1-2 years and it will be a whole new ball game. When the investment community wakes up to that realization, the shit will be hitting the fan in earnest.
First of all, QT is not "KDE's". Secondly, KDE can be easily compiled from source to install to any desired directory. Thirdly, QT doesn't have to be in the same directory structure - if you insist, put it in/opt and KDE in/usr/local. Finally, QT is free for this purpose. Sheesh.
I'm still learning LyX, and maybe there's something I'm missing, but it sure seems like it leaves you completely out in the cold when it comes to making new document classes. I.e., if you're not happy with its canned style of writing a letter and you want your own textclass/documentclass and associated environments, don't plan on coming up for air for a while.
... of preconfigured Linux boxes, we've had excellent results with the Asus K7M and K7V and the old MSI 6167. The MSI 6195 didn't seem to work, but it could have been just a defective board.
As one who has lived at both the top and bottom of corporate structure, I couldn't agree more. It reflects the horribly broken state of management architecture in most companies. People get promoted to management positions because they were good at something else, not because they are good at management.
And because IT career advancement requires job-hopping, managers and other employees will advocate new technologies for their resume-padding value rather than their real value to the company.
Slashdot Mirror
'Nuff said, but /. wouldn't let me post without a body....
Gopher.ptloma.edu sure is slow...
It appears to me that most of the people who have commented on this do not understand the real significance of the article.
As someone who has been scouring the Internet for several days looking for detailed, informative and useful information about how to create a bootable Linux CD, I find this article to be a godsend. In particular, it indicates why the boot image must be in diskette format, and how to fit what's needed into 1440K.
And finally, gaming is just one application. Others are limited only by the imagination.
Thank you Yamamori Takenori!
Close, I think. Wine has been plugging away at a moving target for many years, and is still nowhere near ready for prime time. My guess is M$ wants Corel's Wine developers so they can engineer a Wine-like product that really works, though perhaps proprietary. That would be a huge insurance policy against the success of Linux.
The way to deal with this is to design in a hardware-level interface that abstracts out the trade secrets. The driver should just be an interface to the operating system, not the essence of the product.
Why didn't you tell us what solutions you looked at, and why they were not acceptable??? This question as asked is grossly inconsiderate, guaranteed to waste your time and ours with useless replies.
I wish all these brilliant minds would work on providing unique and interesting Internet content, which is the part that is sorely needed now.
I can't believe these guys. A couple of days ago I was predicting 18 months before Windows is in big trouble, but now it's looking more like 6.
It already works under KDE. You don't need the Gnome desktop, just its libraries.
Beats me what requires me to do that - certainly nothing I agreed to! I stuck it on the manual, and would have preferred to stick it somewhere else, except he wasn't around.
True.
It would be very similar to installing linux one one system with a custom kernel, and then moving that drive to another system. There is a good chance it wont boot because all of the drivers are wrong.
Not true. Linux is very tolerant of changes in the platform. I do this all the time in the course of building systems for clients. Just avoid Kudzu.
MS stock is currently around, oh, 60-70% of where it might be without the antitrust situation. Considering the company's market capitalization, that's one hell of an impact.
I think everyone knows it will be a couple of years before MS has to actually comply with anything. However what has happened that matters is a very formal, very public, very credible statement by the court that MS is managed and controlled by a collection of lying, ruthless, untrustworthy scoundrels.
The other thing that's real is Linux, KDE, Gnome and the rapidly increasing credibility of alternative computing solutions, especially on the desktop. We're not there yet, but another 1-2 years and it will be a whole new ball game. When the investment community wakes up to that realization, the shit will be hitting the fan in earnest.
First of all, QT is not "KDE's". Secondly, KDE can be easily compiled from source to install to any desired directory. Thirdly, QT doesn't have to be in the same directory structure - if you insist, put it in /opt and KDE in /usr/local. Finally, QT is free for this purpose. Sheesh.
I'm still learning LyX, and maybe there's something I'm missing, but it sure seems like it leaves you completely out in the cold when it comes to making new document classes. I.e., if you're not happy with its canned style of writing a letter and you want your own textclass/documentclass and associated environments, don't plan on coming up for air for a while.
... of preconfigured Linux boxes, we've had excellent results with the Asus K7M and K7V and the old MSI 6167. The MSI 6195 didn't seem to work, but it could have been just a defective board.
-- Rod
http://www.sunsetsystems.com/
And because IT career advancement requires job-hopping, managers and other employees will advocate new technologies for their resume-padding value rather than their real value to the company.