We recently discussed this issue at the International Plan 9 Workshop. Lack of driver documentation and time/people to write drivers is what will probably eventually kill using Plan 9 on real hardware.
There was a time when documenting your hardware was required for anyone to buy it.
Even a source code leve driver is not enough when you're not Linux/BSD.
Imagine writing a driver when you only have a driver for another OS as your documentation!
It's just someone else's view of the documentation they saw / reverse engineering they did.
To properly build executables for the Linux/ARM target platform, a Linux/i386 build platform must meet the following requirements:
* Red Hat Linux distribution version 7.2 - 9.0
* Java 2 Platform, Standard Edition (J2SE(TM)) Development Kit (JDK(TM)) version 1.4.2
* GNU Make version 3.79.1 or later
* GNU Cross Compiler (GCC) 3.4.6 or later
* Doxygen version 1.4.1
* Development Kit for the Java Card(TM) Platform 2.2.1
To set up the Linux/i386 build environment, you must do the following things:
* Acquire Monta Vista Developer Tools
* Set Linux platform environment variables
I think you'll find that the price of a game is set by what the market will bear, not the cost of production. So although the production costs are offset by the advertsing revenue, the saving is not passed directly on to the purchaser. Except to say that the availability of the game is perhaps made possible by the offset in prduction costs.
Advertisers will want to advertise in the the already successful franchise games such as the aforementioned PGR. How much different the game do you think the would be in both polish and price if it carried zero paid for advertising compared to whatever revenue it can generate through in-game ads? I would say zero.
Ergo, in-game advertising is a cost borne by the purchaser by having to experience them, not so bad in PGR but I find them quite annnoying in other games.
NT stand for Nested Task, it's a register in the 286 that helps preepmtive multi-tasking which is the feature of both OS/2 and NT that distinguishes them from Window 3.x/9x that used co-operative multi-tasking.
4.1.1 Systems Flags The systems flags of the EFLAGS register control I/O, maskable interrupts, debugging, task switching, and enabling of virtual 8086 execution in a protected, multitasking environment. These flags are highlighted in Figure 4-1 .
NT (Nested Task, bit 14)
The processor uses the nested task flag to control chaining of interrupted and called tasks. NT influences the operation of the IRET instruction .
Slashdot Mirror
> If the programmer was taught how to do things properly, then they would do things properly.
It is a programmer's responsibilty to find out what properly is.
A rare voice of sanity, thank you.
from the plan 9 fortune file :
Almost all good computer programs contain at least one random-number generator.
and I thought Perl was the king of write only code
Java sucks because it's Java
Virtualisation adds another attack vector, suddenly ALL of your programs could be vulnerable.
If your OS can only be trusted in a virtual environment, what's the point of using an OS at all?
58 sq km
So a bit bigger than Bermuda (zoom out) but a bit smaller than San Marino (zoom out)
We recently discussed this issue at the International Plan 9 Workshop. Lack of driver documentation and time/people to write drivers is what will probably eventually kill using Plan 9 on real hardware.
There was a time when documenting your hardware was required for anyone to buy it.
Even a source code leve driver is not enough when you're not Linux/BSD.
Imagine writing a driver when you only have a driver for another OS as your documentation!
It's just someone else's view of the documentation they saw / reverse engineering they did.
The Peer 2 Peer part is on the ToDo list :)
Congratulations, you found Glenda
take a look at http://www.rangboom.com/
Rangboom is a free service for securely sharing or accessing your files over the Internet.
It uses 9p
and appears as a shared drive in Windows
iLink
It used to be that one could say two good things about a Mac
1. It's not on Intel
2. It's not Unix
That's best analogy anyone came up for, for this issue.
http://yro.slashdot.org/comments.pl?sid=213268&cid =17344376
http://yro.slashdot.org/comments.pl?sid=213268&cid =17344376
Referrer headers are untrustworthy and should not be relied on for access restriction, or much else for that matter.
Some places strip them from outgoing requests at the packet filter / firewall
To properly build executables for the Linux/ARM target platform, a Linux/i386 build platform must meet the following requirements:
* Red Hat Linux distribution version 7.2 - 9.0
* Java 2 Platform, Standard Edition (J2SE(TM)) Development Kit (JDK(TM)) version 1.4.2
* GNU Make version 3.79.1 or later
* GNU Cross Compiler (GCC) 3.4.6 or later
* Doxygen version 1.4.1
* Development Kit for the Java Card(TM) Platform 2.2.1
To set up the Linux/i386 build environment, you must do the following things:
* Acquire Monta Vista Developer Tools
* Set Linux platform environment variables
Acquiring Monta Vista Developer Tools
To build phoneME Feature software for the Linux/ARM (P2 board) target platform, you must acquire the MontaVista CEE 3.1 ADK developer tools.
I would argue that taking ads out of the world make it more realistic.
I think you'll find that the price of a game is set by what the market will bear, not the cost of production.
So although the production costs are offset by the advertsing revenue, the saving is not passed directly on to the purchaser. Except to say that the availability of the game is perhaps made possible by the offset in prduction costs.
Advertisers will want to advertise in the the already successful franchise games such as the aforementioned PGR. How much different the game do you think the would be in both polish and price if it carried zero paid for advertising compared to whatever revenue it can generate through in-game ads? I would say zero.
Ergo, in-game advertising is a cost borne by the purchaser by having to experience them, not so bad in PGR but I find them quite annnoying in other games.
next stop - Microsoft binary Linux drivers for Suse - $799
s/Debian/FreeBSD/g
If only you;d know that when you started ... oh wait ...
> Windows NT does *NOT* stand for Nested Task.
They have better reading comprehension than you. I didn't say Windows NT stood for anything
NT stand for Nested Task, it's a register in the 286 that helps preepmtive multi-tasking which is the feature of both OS/2 and NT that distinguishes them from Window 3.x/9x that used co-operative multi-tasking.
6 /s04_01.htm
http://pdos.csail.mit.edu/6.828/2006/readings/i38
4.1.1 Systems Flags
The systems flags of the EFLAGS register control I/O, maskable interrupts, debugging, task switching, and enabling of virtual 8086 execution in a protected, multitasking environment. These flags are highlighted in Figure 4-1 .
NT (Nested Task, bit 14)
The processor uses the nested task flag to control chaining of interrupted and called tasks. NT influences the operation of the IRET instruction .
What's a "looser" ?