Ok, so the cloners copy the design (that FTDI paid for), steal the VID (that FTDI paid for), and then by clear intention, use the FTDI driver (that FTDI paid for), and you say FTDI started a war?
Really? Good for FTDI. The supply chain will get purged of the counterfeit material faster this way then any lawsuit could.
And it isn't really "levels," it's "symbols." A symbol represents multiple bits in modems from 1200 bps up, and some of these symbols have identical levels. Instead, they differ in phase.
Yet again, the fact that Hollings is a Democrat escapes any mention, but a recent/. article about a Republican senator features HIS party affiliation right up front.
What's wrong, guys, does it hurt that badly to admit it isn't just Republicans that push to limit freedoms?
If you all you want is read-only access, I don't see too much of a problem - it would be sort of like a CD ROM. Don't expect a timestamp on last access....
But read/write would be tough, because then you'd have to deal with fragmentation of files and gaps after a delete. Neither tar nor *zip would like that at all....and copying over to a new archive file defeats the purpose.
The article putes quotes around the words "code" and "data" and that is the problem. In i386, CODE segments can either by read/execute or execute only. DATA segments can either by read/write or read only - not execute.
So what is an Intel-baesd, flat-mode program to do? It sets up two segments - one data, one code - pointing to the same memory. Goodbye hardware security.
Of course the VM doesn't protect against execution - that is the segmentation system's job. Linux (and anything else that assumes a 68k or VAX flat address space) just blows it off.
Simple solution - bring back seperate code and data. Excuse me, I and D. Just like the PDP-11 UNIX grew up on.
Those of us that suffer with Windows and Outlook know that the reply problems (original text below reply text) originate from Outlook's brain-dead available reply formats.
Even if you turn on "prefix each line" for replys in the traditional internet style, Outlook doesn't get the line wrap right, causing really ugly posts.
The only option I can think of is to show mailing list subscribers what a good reply looks like, and hope that they either (a) reformat replies by hand or (b) give up Outlook.
Having a PE when involved in high-visibility projects (publicly visible, that is) helps when asked to do stupid things for non-technical reasons. There is nothing like "I could lose my license over this" to wake people up. Now I use that with my customers (I'm a PE and I own the company).
On another note, don't view the PE like passing the bar. Engineers don't have similar educational requirements as lawyers or doctors. View the PE like the CPA license. Both engineers and accountants only need a BS/BA degree and both have exemptions for practicing without a license if working for a company. And both can have, long, productive careers either with or without a license, although I believe that you are more valuable in the market place with one.
It is kind of hard to put PalmOS, QNX and WinCE in the same boat. Yes, you could use each with a GUI, but each has very different design goals. QNX is realtime first, with a GUI second. PalmOS was built on top of Kadak's AMX (realtime first, GUI later). PalmOS added the GUI we know and love. WinCE is just gooey:-). Seriously, WinCE is GUI (really look-and-feel) first, realtime a distant second.
I don't know much about the PalmOS, but QNX DOES use the MMU, at least on the x86 version. For years, that was one of the big selling points of the OS. Same with WinCE.
I don't know that much about the Dragonball, but other 68k machines (I know, not quite the same) had user/supervisor modes that one could use to at least keep an application from crashing the OS.
Slashdot Mirror
Open the pod bay doors.
Then my garage opens...or not.
Wait - "FTDI has started an outright war?"
Ok, so the cloners copy the design (that FTDI paid for), steal the VID (that FTDI paid for), and then by clear intention, use the FTDI driver (that FTDI paid for), and you say FTDI started a war?
Really? Good for FTDI. The supply chain will get purged of the counterfeit material faster this way then any lawsuit could.
Seems like a clever solution to me.
Now we can refer to Eugene, OR as "Shelbyville."
And it isn't really "levels," it's "symbols." A symbol represents multiple bits in modems from 1200 bps up, and some of these symbols have identical levels. Instead, they differ in phase.
What's wrong, guys, does it hurt that badly to admit it isn't just Republicans that push to limit freedoms?
Like, say, a song you wrote?
I know you were thinking medical information. Just humor me.
If you all you want is read-only access, I don't see too much of a problem - it would be sort of like a CD ROM. Don't expect a timestamp on last access....
But read/write would be tough, because then you'd have to deal with fragmentation of files and gaps after a delete. Neither tar nor *zip would like that at all....and copying over to a new archive file defeats the purpose.
The article putes quotes around the words "code" and "data" and that is the problem. In i386, CODE segments can either by read/execute or execute only. DATA segments can either by read/write or read only - not execute.
So what is an Intel-baesd, flat-mode program to do? It sets up two segments - one data, one code - pointing to the same memory. Goodbye hardware security.
Of course the VM doesn't protect against execution - that is the segmentation system's job. Linux (and anything else that assumes a 68k or VAX flat address space) just blows it off.
Simple solution - bring back seperate code and data. Excuse me, I and D. Just like the PDP-11 UNIX grew up on.
Those of us that suffer with Windows and Outlook know that the reply problems (original text below reply text) originate from Outlook's brain-dead available reply formats.
Even if you turn on "prefix each line" for replys in the traditional internet style, Outlook doesn't get the line wrap right, causing really ugly posts.
The only option I can think of is to show mailing list subscribers what a good reply looks like, and hope that they either (a) reformat replies by hand or (b) give up Outlook.
Neither seems very likely to succeed, sad to say.
Having a PE when involved in high-visibility projects (publicly visible, that is) helps when asked to do stupid things for non-technical reasons. There is nothing like "I could lose my license over this" to wake people up. Now I use that with my customers (I'm a PE and I own the company).
On another note, don't view the PE like passing the bar. Engineers don't have similar educational requirements as lawyers or doctors. View the PE like the CPA license. Both engineers and accountants only need a BS/BA degree and both have exemptions for practicing without a license if working for a company. And both can have, long, productive careers either with or without a license, although I believe that you are more valuable in the market place with one.
Brian L. Bishop, PE
It is kind of hard to put PalmOS, QNX and WinCE in the same boat. Yes, you could use each with a GUI, but each has very different design goals. QNX is realtime first, with a GUI second. PalmOS was built on top of Kadak's AMX (realtime first, GUI later). PalmOS added the GUI we know and love. WinCE is just gooey :-). Seriously, WinCE is GUI (really look-and-feel) first, realtime a distant second.
I don't know much about the PalmOS, but QNX DOES use the MMU, at least on the x86 version. For years, that was one of the big selling points of the OS. Same with WinCE.
I don't know that much about the Dragonball, but other 68k machines (I know, not quite the same) had user/supervisor modes that one could use to at least keep an application from crashing the OS.