Asus will be happy with the treatment of their lovely nVidia board. I guess there's no such thing as bad publicity.
I do think the author omitted to mention that a hammer and baseball bat were required for the procedure. These will be necessary if the machine somehow still manages to boot.
Back in '94 Windows NT reportedly supported a POSIX interface (I've never seen anyone use it in all these years). However the implementation routed thru the WIN32 interface, which pretty much guaranteed that Windows apps under NT would be more effecient than Unix apps using the POSIX subsystem.
Can someone seriously propose doing the same with device drivers? Perhaps if they did I could use my ATI 9700 PRO under FreeBSD running X, but why bother? It would make using such a graphics card redundant.
I think we're entering dangerous territory here. Management like to think in terms of these layers of compatibility, but in the long run they produce unsupportable solutions. When it breaks where do you begin to look and how much will it cost to find the problem and sort it?
You also have the problem of evolving file formats. Take the.doc format for example. This file format has continued to change and the only time us poor old users find out is when we can't read a document or it "seems wrong". The whole thing is undocumented and the world is forced to upgrade as newer versions of.doc files are propogated.
Personally, I was happy with Word 6.0. From my perspective, Word 95 added long file names, Word 97 added incompatibilites, Word 2000 attempted to fix them and Word XP does away with MDI. I don't need anything newer than Word 95, but have to use Word 2000 because of incompatible.doc files.
My network has FreeBSD, RH Linux, OpenBSD, BeOS , NT and 2K. By running this configuration for some time I've learned the following that I think is relevant.
You don't need or want to share everything across all platforms. My kids XBoing scores are not relevant to BeOS or Windows for example. Whereas I need to view my invoices in all but BeOS. My mail is held in Netscape under Windows and Mozilla elsewhere. The files are almost the same but not exactly, making it unwise to keep copying them.
You need to decide what data needs to be available on each box and make the necessary arrangements to place it there. That may mean using Samba or NFS or resorting to scp/ftp.
Remember Windows file attributes are different and so you'll have issues with them when moving files to and from unix. BeOS has more attributes that simply get lost durinf transfer. And the ubiqutous end of line between Windows and everyone else...
The bottom line is you have to think about what you want (or even why you have the particular heterogenous mix of boxes) and make provisions for your requirement.
Slashdot Mirror
Asus will be happy with the treatment of their lovely nVidia board. I guess there's no such thing as bad publicity. I do think the author omitted to mention that a hammer and baseball bat were required for the procedure. These will be necessary if the machine somehow still manages to boot.
Back in '94 Windows NT reportedly supported a POSIX interface (I've never seen anyone use it in all these years). However the implementation routed thru the WIN32 interface, which pretty much guaranteed that Windows apps under NT would be more effecient than Unix apps using the POSIX subsystem.
Can someone seriously propose doing the same with device drivers? Perhaps if they did I could use my ATI 9700 PRO under FreeBSD running X, but why bother? It would make using such a graphics card redundant.
I think we're entering dangerous territory here. Management like to think in terms of these layers of compatibility, but in the long run they produce unsupportable solutions. When it breaks where do you begin to look and how much will it cost to find the problem and sort it?
You also have the problem of evolving file formats. Take the .doc format for example. This file format has continued to change and the only time us poor old users find out is when we can't read a document or it "seems wrong". The whole thing is undocumented and the world is forced to upgrade as newer versions of .doc files are propogated.
Personally, I was happy with Word 6.0. From my perspective, Word 95 added long file names, Word 97 added incompatibilites, Word 2000 attempted to fix them and Word XP does away with MDI. I don't need anything newer than Word 95, but have to use Word 2000 because of incompatible .doc files.
My network has FreeBSD, RH Linux, OpenBSD, BeOS , NT and 2K. By running this configuration for some time I've learned the following that I think is relevant.
You don't need or want to share everything across all platforms. My kids XBoing scores are not relevant to BeOS or Windows for example. Whereas I need to view my invoices in all but BeOS. My mail is held in Netscape under Windows and Mozilla elsewhere. The files are almost the same but not exactly, making it unwise to keep copying them.
You need to decide what data needs to be available on each box and make the necessary arrangements to place it there. That may mean using Samba or NFS or resorting to scp/ftp.
Remember Windows file attributes are different and so you'll have issues with them when moving files to and from unix. BeOS has more attributes that simply get lost durinf transfer. And the ubiqutous end of line between Windows and everyone else...
The bottom line is you have to think about what you want (or even why you have the particular heterogenous mix of boxes) and make provisions for your requirement.