Looks like a decent start to me. I'm going to want better controls, obviously, as the SDL build seemed to think the world is a crappy touchscreen. I tried Disgaea (backup of my own disc), but it got stuck at the loading screen; not really sure what it was waiting for. I did rather expect the unimplemented functions it warned of, Atrac+ doesn't seem that popular - but it's used extensively by this game, which was what I bought the PSP for in the first place. When building, the inline assembly for CPUID didn't want to work (replaced it with cpuid device support), and I had to add a -march=core2 flag to enable SSE2.
Sorry, your description is just historically wrong. What you call DOS isn't at all based on removing the features of Unix; it grew from QDOS, which was a Quick and Dirty imitation of CP/M. It eventually acquired a few Unix type features like directories, I/O redirection and device names. Also, at the time, Unix (far from the first multiuser OS, but quite popular due to its portability) was not particularly concerned with networking; things like UUCP (Unix to Unix CoPy) and Fidonet handled such tasks before the Internet (begun as ARPAnet) spread. The growing security model in Windows comes from an entirely different model of threats; MS indeed feel that the user is the threat, since a large number of them do not know what the computer does. Their solution is MS taking more control over systems that aren't theirs, since they feel even more threatened by users who do know (or want to learn) what they're doing.
They used to. It started to get a bit less reliable somewhere around the 3000 series. At this point they're yet another PC manufacturer short on ideas with a legal department that considers customer hostility a good thing. It seems a common problem when a company grows enough to hire administrative people who aren't involved with the products.
You mean like w3m-img does? Or perhaps like xmlterm (apparently now defunct)? Although iirc xmlterm doesn't deal well with things like curses. The main reason we don't do this directly is it implies transforming your terminal from a text listing to a picture, and that eats much more memory and processing time. Not too good for those of us with half a dozen terminals each with a few thousand lines of scrollback buffer. Just not enough gain compared to running another VC with zgv, fbi or similar.
That is not an argument for abolishing the command line; and the lack of desire you describe stems for the most part in either fear of the unknown or ignorance of the possibilities. The point you should mind is when someone tries to force it on you, not just because someone else uses it. Also, as for the "wasted" claim, this is simply untrue - the command line tools are often what works behind the scenes as the graphical interfaces are tacked on, and mean less time spent doing something that we know can be done (UI writing, not infrequently done better by others) rather than working on what the new program does. And FWIW, my grandmother used the Minitel, and dislikes modern phones because it's inconsistent what each button (when there even are any) does. She wants more direct controls.
Slow story day,/.? This flamebait is a lot like saying "right, we've got street signs, now let's get rid of speech - noone needs to ask directions!" It's in a similar category to the regular "let's stop using X" arguments, and tends to come from an ignorance of what is being dissed. For a basic understanding of what a CLI is, I suggest The Command Line - The Best Newbie Interface?.
At first I thought it was one of those typical Frontpage-generated sites that overlap images with text, but it turns out he used screenshots and didn't even match the images with the windows he wanted to show, so we're seeing random garbage around them. The pink/green effect on the gray areas is indicative that he's using 16-bit, so yes, this guy could use a new graphics card. Fairly neat hack, but combine it with for instance ALE's video mode for proper effect.
I don't see where you find that pretense - slashdot hasn't ever been objective as far as I know, and it doesn't need to be. Guessing from the names you've listed but not motivated or described, you're trying to pin some other individuals' opinions on it. Frankly, as poorly written as the typical/. notice is, do you really think there's anything approaching that level of coordination?
Not that it's tied to DOS or anything.. that's the extended color scheme CGA uses in text mode, which it really shares with every other system using a digital RGB monitor. You'd need an EGA board to get it in graphics mode, though, since CGA boards can't use more than two bits per pixel in graphics mode. In short, it's way older than VGA.
I too would suggest the iRiver MP3 CD player. They have stated that they plan to add Ogg Vorbis support in a firmware update. The Rio Volt CD players are the same product. Personally I have a Philips MP3 CD player, but as far as I know it's not upgradable.
Actually, there's at least one screenshot of X on Tader's site. But PicoGUI is not X, although it does run under X (in at least three different ways that I know of).
"By way of example but not limitation, a Modification that adds support for other compression data such as MPEG-1 or MPEG-2 would be permissible, but only if the resulting Larger Work continues to support playback of VP3.2 data."
Seems pretty clear to me they mean that it still has to _support_ the original format. The phrasing is strange though, but given the included example in the license your post is incorrect.
If the research was Open Source, then the final product will not end up in the public domain.
This is dead wrong. There is not, nor has there ever been, a conflict between public domain and open source. You are probably confusing it with the GNU (Lesser) Public License, which places the additional requirent of passing on source along with any binaries (or ensuring the availability and knowledge of the source).
the C standard defines time as a long and a long as 32 bits No. C does not require time_t to be a long, and a long only has to be at least 32 bits. In Linux on Alpha, time_t is still an unsigned long, but a long is 64 bits.
Actually, I managed to buy a laptop without paying for windows. It was delivered with windows preinstalled.. the manufacturer couldn't get a hard disk without it. However, they have discontinued their PC line now, and even when they did sell those laptops they never announced that you could buy it without windows; it was a choice of 95 or 98 in the forms.
> It's super hot all the time Then you failed to use set6x86 to enable suspend-on-HLT. It's the one most important thing to do with Cyrix processors. I have myself used 5x86, 6x86 and MediaGXm processors, and they were quite efficient; while they did have slower FPUs than Intel or AMD, the 5x86 at 90mhz actually ran most applications faster than the Pentium II (a brand new one at the time). The best point about Cyrix CPUs imho is that they're all optimized for 486 code. The 6x86 (a 4x25mhz version) was sensitive to overclocking, but ran fine at 4x30 - not at 4x33 though.
The master process of Apache is not designed to be reboot all the time. Since Apache allow external modules so it is safe bit to assume that those modules can introduce memory leakage. I think it is clever design to let child process die when there is no much traffic.
Quite true. While writing PHP modules, I have very often caused memory leaks or page faults with incorrect pointers. The result is simple; the offending apache sub-process dies, the server stays up. Easily reproducible, easily fixed - and only the function I'm developing is affected.
To be fair, the Solaris systems I'm targeting aren't all that perfect. The linker has a tendency to crash on some.so files. But so far, I've always been able to get it running - and once it runs, it stays that way.
All the software on the CD is uncompressed and unencrypted, so you can easily copy their "firmware" even if you don't use the Windows software. There are several alternatives to "RCX code" available on the net (and they're needed!), the most popular of which is probably NQC, one of those that use the standard firmware. It includes the download abilities. There's also a free replacement OS, legOS, that you can use if you want to cross-compile directly for the Hitachi CPU using GCC. Again, communication tools are included.
Slashdot Mirror
Nope, it looks like this: â
ââzâ"â' âââââ'ââ'ââz âââzâzâ'â--âZâ
Are you saying you missed Vi Hart's instructions for Thanksgiving Turduckenen-duckenen?
Looks like a decent start to me. I'm going to want better controls, obviously, as the SDL build seemed to think the world is a crappy touchscreen. I tried Disgaea (backup of my own disc), but it got stuck at the loading screen; not really sure what it was waiting for. I did rather expect the unimplemented functions it warned of, Atrac+ doesn't seem that popular - but it's used extensively by this game, which was what I bought the PSP for in the first place.
When building, the inline assembly for CPUID didn't want to work (replaced it with cpuid device support), and I had to add a -march=core2 flag to enable SSE2.
Sorry, your description is just historically wrong. What you call DOS isn't at all based on removing the features of Unix; it grew from QDOS, which was a Quick and Dirty imitation of CP/M. It eventually acquired a few Unix type features like directories, I/O redirection and device names. Also, at the time, Unix (far from the first multiuser OS, but quite popular due to its portability) was not particularly concerned with networking; things like UUCP (Unix to Unix CoPy) and Fidonet handled such tasks before the Internet (begun as ARPAnet) spread. The growing security model in Windows comes from an entirely different model of threats; MS indeed feel that the user is the threat, since a large number of them do not know what the computer does. Their solution is MS taking more control over systems that aren't theirs, since they feel even more threatened by users who do know (or want to learn) what they're doing.
They used to. It started to get a bit less reliable somewhere around the 3000 series. At this point they're yet another PC manufacturer short on ideas with a legal department that considers customer hostility a good thing. It seems a common problem when a company grows enough to hire administrative people who aren't involved with the products.
You mean like w3m-img does? Or perhaps like xmlterm (apparently now defunct)? Although iirc xmlterm doesn't deal well with things like curses. The main reason we don't do this directly is it implies transforming your terminal from a text listing to a picture, and that eats much more memory and processing time. Not too good for those of us with half a dozen terminals each with a few thousand lines of scrollback buffer. Just not enough gain compared to running another VC with zgv, fbi or similar.
That is not an argument for abolishing the command line; and the lack of desire you describe stems for the most part in either fear of the unknown or ignorance of the possibilities. The point you should mind is when someone tries to force it on you, not just because someone else uses it. Also, as for the "wasted" claim, this is simply untrue - the command line tools are often what works behind the scenes as the graphical interfaces are tacked on, and mean less time spent doing something that we know can be done (UI writing, not infrequently done better by others) rather than working on what the new program does. And FWIW, my grandmother used the Minitel, and dislikes modern phones because it's inconsistent what each button (when there even are any) does. She wants more direct controls.
Slow story day, /.? This flamebait is a lot like saying "right, we've got street signs, now let's get rid of speech - noone needs to ask directions!"
It's in a similar category to the regular "let's stop using X" arguments, and tends to come from an ignorance of what is being dissed. For a basic understanding of what a CLI is, I suggest The Command Line - The Best Newbie Interface?.
At first I thought it was one of those typical Frontpage-generated sites that overlap images with text, but it turns out he used screenshots and didn't even match the images with the windows he wanted to show, so we're seeing random garbage around them. The pink/green effect on the gray areas is indicative that he's using 16-bit, so yes, this guy could use a new graphics card. Fairly neat hack, but combine it with for instance ALE's video mode for proper effect.
I rented a DVD of X-men 2, and was disappointed at the video quality.
I don't see where you find that pretense - slashdot hasn't ever been objective as far as I know, and it doesn't need to be. Guessing from the names you've listed but not motivated or described, you're trying to pin some other individuals' opinions on it. Frankly, as poorly written as the typical /. notice is, do you really think there's anything approaching that level of coordination?
Not that it's tied to DOS or anything.. that's the extended color scheme CGA uses in text mode, which it really shares with every other system using a digital RGB monitor. You'd need an EGA board to get it in graphics mode, though, since CGA boards can't use more than two bits per pixel in graphics mode. In short, it's way older than VGA.
I too would suggest the iRiver MP3 CD player. They have stated that they plan to add Ogg Vorbis support in a firmware update. The Rio Volt CD players are the same product. Personally I have a Philips MP3 CD player, but as far as I know it's not upgradable.
Actually, there's at least one screenshot of X on Tader's site. But PicoGUI is not X, although it does run under X (in at least three different ways that I know of).
Seems pretty clear to me they mean that it still has to _support_ the original format. The phrasing is strange though, but given the included example in the license your post is incorrect.
If the research was Open Source, then the final product will not end up in the public domain.
This is dead wrong. There is not, nor has there ever been, a conflict between public domain and open source. You are probably confusing it with the GNU (Lesser) Public License, which places the additional requirent of passing on source along with any binaries (or ensuring the availability and knowledge of the source).
the C standard defines time as a long and a long as 32 bits
No. C does not require time_t to be a long, and a long only has to be at least 32 bits. In Linux on Alpha, time_t is still an unsigned long, but a long is 64 bits.
Actually, I managed to buy a laptop without paying for windows. It was delivered with windows preinstalled.. the manufacturer couldn't get a hard disk without it. However, they have discontinued their PC line now, and even when they did sell those laptops they never announced that you could buy it without windows; it was a choice of 95 or 98 in the forms.
> It's super hot all the time
Then you failed to use set6x86 to enable suspend-on-HLT. It's the one most important thing to do with Cyrix processors.
I have myself used 5x86, 6x86 and MediaGXm processors, and they were quite efficient; while they did have slower FPUs than Intel or AMD, the 5x86 at 90mhz actually ran most applications faster than the Pentium II (a brand new one at the time). The best point about Cyrix CPUs imho is that they're all optimized for 486 code. The 6x86 (a 4x25mhz version) was sensitive to overclocking, but ran fine at 4x30 - not at 4x33 though.
Quite true. While writing PHP modules, I have very often caused memory leaks or page faults with incorrect pointers. The result is simple; the offending apache sub-process dies, the server stays up. Easily reproducible, easily fixed - and only the function I'm developing is affected.
To be fair, the Solaris systems I'm targeting aren't all that perfect. The linker has a tendency to crash on some .so files. But so far, I've always been able to get it running - and once it runs, it stays that way.
All the software on the CD is uncompressed and unencrypted, so you can easily copy their "firmware" even if you don't use the Windows software. There are several alternatives to "RCX code" available on the net (and they're needed!), the most popular of which is probably NQC, one of those that use the standard firmware. It includes the download abilities. There's also a free replacement OS, legOS, that you can use if you want to cross-compile directly for the Hitachi CPU using GCC. Again, communication tools are included.