Nice idea! I wrote a similar game in 1983 on a VIC-20. There was a big crossroads full with moving cars (in every direction) and a phone booth somewhere on the screen. The player started out at the phone booth and had to cross traffic until they leave the crossroads.;-)
- trailer was made by somebody with a strict employer agreement on original works (anything I author that isn't "for the company" I need to register the material with my employer... or my employer owns it)
That's not possible. If you make something in your spare time at home with your own equipment, your employer can't not own it, no matter what is written in the employment contract.
On the other hand, if you use office equipment to make something and the employer has the leniency to grant you your rights anyway if you register the work with them, then that's an extra generous employer. Normally, everything you make in office with office equipment belongs to your employer.
Perchlorate might be the first step to terraforming Mars. Like with huge machines that heat soil components to produce oxygen, as was seen in the alien artifact of the movie Total Recall. It could also be used on smaller scale to create rocket fuel and oxygen for life support systems.
You can fix any Notes problem by deleting the Notes.ini file!;-) (only the NotesDirectory and another entry need to be retained! that's at least how it used to be, some years ago)
When you install files into a running system with a "make install", generated from an ordinary makefile created by a configure script, files that get (over-)written are NOT recorded in the package system. The best way to avoid system destruction is to create a package using the packaging system documentation for the host OS, and install that.
For the rest of the 99% of the world's computer users, it's an instant deal breaker.
Exactly. That's why more software companies need to publish software for Linux. Just a couple of days ago, I purchased a commercial software package for Linux. I think the time of Linux is just beginning.:-)
That goes along with the mantra of Linux, as LinuxHater pointed out: if something doesn't work in Linux, convince yourself you don't need it.
Exactly. Or make your own package, which requires skill and expertise. On the plus side, making a package for an app can benefit other people (if submitted to the distro). But it requires some work: First install it into a sandbox directory (using "configure --prefix=dir"), then make a package from it (distro dependent). Nowadays, luckily, there's enough stuff in most package directories even in BSD distros to satisfy almost every need. On BSD I had to recompile packages with optimization turned off, because the GCC version (3.x) they used had a bug-ridden optimizer. But this hardly occurs anymore on Linux, especially Ubuntu Linux, because GCC 4.x has become much better. Of course, you cannot bother ordinary users with such things. But those operating systems are getting better every day. The signs that Asus and AMD are beginning to sell Linux systems might be indicators that the time of Linux is just beginning.
Ubuntu is super-easy to use, if you stick to the available mechanisms for package installation and such. Don't try to install from source if you don't know exactly what you're doing. Also, they're the quickest when it comes to automatic updates. There's almost no day when there's not some updates flowing in. It certainly can't get any better than Ubuntu. Try the latest Ubuntu, 8.04 LTS Edition, it just rocks and is fast as lightning.
If you want clean directory structure, use a BSD. FreeBSD is for super-paranoid admins (ports collection with security auditing, for instance). OpenBSD is for people who want a straight UNIX, with no bells and whistles (excellent development platform). There's also NetBSD (never tried it, AFAIK it's aimed at resource-constrained platforms).
BSDs have an advantage there: The ports library. It can install multiple versions of applications in parallel. It knows how to build and install specific packages. Updating is also relatively easy. But to read the (very good) man pages is a MUST. Of the Linuxes, Ubuntu Linux has the best updating mechanism: automatic. And FWIW, for most systems it's the old proverb: Never touch a running system.
Big hint here: Don't install from source. Use the available packages. If an app isn't available as a package (or with binary install script), don't attempt to install it from source. The same applies to BSD as well, BTW. In BSD, you have two options: Package or Port. I learnt that the hard way by experimenting with various Linux and BSD systems. Now I only use readily available facilities, and don't even bother to try and make something running that possibly can't. If you want Linux the easy way, use Ubuntu Linux. For BSDs, FreeBSD and OpenBSD are good choices. OpenBSD is much simpler than FreeBSD. The BSDs are real UNIX systems in all their unforgiving glory. OpenBSD does exactly what you want. If you destroy it in the process, your problem.;-)
People just don't know how to use their Linux properly: Don't install apps from source, use the package manager. If an app isn't supported, don't use it. Big hint here: Use Ubuntu Linux. It provides automatic updates.
The bug affected divisions of particular number pairs. But it was no problem really, because Intel provided free CPU replacement. I had a P90 at that time, with that bug, and it was noticeable only with when you used a calculator app or something, because the digits after the decimal point were a bit off. My dealer gave me a free CPU replacement. BTW, P75's and P90's didn't have SIMD instructions, so they're using it only as the base core. BTW II: The reason for the FDIV bug was simply that a value in one of the division tables was wrong in the chip mask.
8/9 years ago, in 2000/1999, when I developed on real AIX and Solaris boxes, Motif was used for most applications. Of course, this might have changed nowadays, but on Solaris, for instance, GNOME is being used now. On most Linux systems, GNOME is the default. But compared to Motif, Qt has many more users now, that's for sure!;-)
Blue and Peachpuff are also easy on the eyes. A popular color scheme pack for VIM (see VIM website) included a scheme called Buttercream, which also was quite nice. I change color scheme as soon as my eyes feel uncomfortable. But in a sense, it's always a sign of being tired. I hope you were talking about GVIM not VIM, because in an ANSI terminal, VIM cannot set the colors that it wants. If a GUI is available, use GVIM instead of VIM (GVIM is the GUI version of VIM).
Slashdot Mirror
Nice idea! I wrote a similar game in 1983 on a VIC-20. There was a big crossroads full with moving cars (in every direction) and a phone booth somewhere on the screen. The player started out at the phone booth and had to cross traffic until they leave the crossroads. ;-)
- trailer was made by somebody with a strict employer agreement on original works (anything I author that isn't "for the company" I need to register the material with my employer ... or my employer owns it)
That's not possible. If you make something in your spare time at home with your own equipment, your employer can't not own it, no matter what is written in the employment contract.
On the other hand, if you use office equipment to make something and the employer has the leniency to grant you your rights anyway if you register the work with them, then that's an extra generous employer. Normally, everything you make in office with office equipment belongs to your employer.
Perchlorate might be the first step to terraforming Mars. Like with huge machines that heat soil components to produce oxygen, as was seen in the alien artifact of the movie Total Recall. It could also be used on smaller scale to create rocket fuel and oxygen for life support systems.
I think it's beautiful! :-)
Not all Europeans.
FYI, Duplo is manufactured by Lego as well. :-D
Duplo are the bricks for younger children, while Lego are for older ones.
People build houses in Europe too! :-D
You can fix any Notes problem by deleting the Notes.ini file! ;-) (only the NotesDirectory and another entry need to be retained! that's at least how it used to be, some years ago)
When you install files into a running system with a "make install", generated from an ordinary makefile created by a configure script, files that get (over-)written are NOT recorded in the package system. The best way to avoid system destruction is to create a package using the packaging system documentation for the host OS, and install that.
For the rest of the 99% of the world's computer users, it's an instant deal breaker.
Exactly. That's why more software companies need to publish software for Linux. Just a couple of days ago, I purchased a commercial software package for Linux. I think the time of Linux is just beginning. :-)
That goes along with the mantra of Linux, as LinuxHater pointed out: if something doesn't work in Linux, convince yourself you don't need it.
Exactly. Or make your own package, which requires skill and expertise. On the plus side, making a package for an app can benefit other people (if submitted to the distro). But it requires some work: First install it into a sandbox directory (using "configure --prefix=dir"), then make a package from it (distro dependent). Nowadays, luckily, there's enough stuff in most package directories even in BSD distros to satisfy almost every need. On BSD I had to recompile packages with optimization turned off, because the GCC version (3.x) they used had a bug-ridden optimizer. But this hardly occurs anymore on Linux, especially Ubuntu Linux, because GCC 4.x has become much better. Of course, you cannot bother ordinary users with such things. But those operating systems are getting better every day. The signs that Asus and AMD are beginning to sell Linux systems might be indicators that the time of Linux is just beginning.
Have a look at the list of supported hardware in the CUPS project (Common Unix Printing System).
BTW, there's also Xubuntu to get XFCEitis. ;-)
Ubuntu is super-easy to use, if you stick to the available mechanisms for package installation and such. Don't try to install from source if you don't know exactly what you're doing. Also, they're the quickest when it comes to automatic updates. There's almost no day when there's not some updates flowing in. It certainly can't get any better than Ubuntu. Try the latest Ubuntu, 8.04 LTS Edition, it just rocks and is fast as lightning.
Use Ubuntu Linux, which has a super-easy package manager (called "add/remove programs") with colorful icons, categories, search function and stuff. :-)
If you want clean directory structure, use a BSD. FreeBSD is for super-paranoid admins (ports collection with security auditing, for instance). OpenBSD is for people who want a straight UNIX, with no bells and whistles (excellent development platform). There's also NetBSD (never tried it, AFAIK it's aimed at resource-constrained platforms).
The solution to any Exchange problem is to use Lotus Notes! ;-)
BSDs have an advantage there: The ports library. It can install multiple versions of applications in parallel. It knows how to build and install specific packages. Updating is also relatively easy. But to read the (very good) man pages is a MUST. Of the Linuxes, Ubuntu Linux has the best updating mechanism: automatic. And FWIW, for most systems it's the old proverb: Never touch a running system.
Big hint here: Don't install from source. Use the available packages. If an app isn't available as a package (or with binary install script), don't attempt to install it from source. The same applies to BSD as well, BTW. In BSD, you have two options: Package or Port. I learnt that the hard way by experimenting with various Linux and BSD systems. Now I only use readily available facilities, and don't even bother to try and make something running that possibly can't. If you want Linux the easy way, use Ubuntu Linux. For BSDs, FreeBSD and OpenBSD are good choices. OpenBSD is much simpler than FreeBSD. The BSDs are real UNIX systems in all their unforgiving glory. OpenBSD does exactly what you want. If you destroy it in the process, your problem. ;-)
People just don't know how to use their Linux properly: Don't install apps from source, use the package manager. If an app isn't supported, don't use it. Big hint here: Use Ubuntu Linux. It provides automatic updates.
The bug affected divisions of particular number pairs. But it was no problem really, because Intel provided free CPU replacement. I had a P90 at that time, with that bug, and it was noticeable only with when you used a calculator app or something, because the digits after the decimal point were a bit off. My dealer gave me a free CPU replacement. BTW, P75's and P90's didn't have SIMD instructions, so they're using it only as the base core. BTW II: The reason for the FDIV bug was simply that a value in one of the division tables was wrong in the chip mask.
8/9 years ago, in 2000/1999, when I developed on real AIX and Solaris boxes, Motif was used for most applications. Of course, this might have changed nowadays, but on Solaris, for instance, GNOME is being used now. On most Linux systems, GNOME is the default. But compared to Motif, Qt has many more users now, that's for sure! ;-)
Blue and Peachpuff are also easy on the eyes. A popular color scheme pack for VIM (see VIM website) included a scheme called Buttercream, which also was quite nice. I change color scheme as soon as my eyes feel uncomfortable. But in a sense, it's always a sign of being tired. I hope you were talking about GVIM not VIM, because in an ANSI terminal, VIM cannot set the colors that it wants. If a GUI is available, use GVIM instead of VIM (GVIM is the GUI version of VIM).
In our own solar system, there are probably enough quantities of these elements for millenia. Just don't forget to space travel.
DKB III is available with labelled keys!