We have created a great innovation: the abolishment of passwords. In their place, we introduce the new Windows Active DRM Passphrases.NET XP (TM) web service.
To add to that, in Canada (at least in Saskatchewan, and as far as I understand, it's the same in every province) there is a difference between laying off someone, and firing someone.
If you (as an employer) are laying someone off, you don't need to show cause, but you have to give prior notice, or pay in lieu of notice.
If you are firing someone, you can do it immediately, but if they sue you for wrongful dismissal, they will probably win unless you can show cause.
The question is not "why *shouldn't* you be able to get a patent", but "is there a significant net benefit to society to enforce a patent on your behalf, versus not doing so?"
If all my personal files are erased, what do I care that/usr is still intact?
The *only* reason I'd care is that I can still probably trust the system binaries (e.g. programs like sha1sum won't be trojan horses). As an admin, that's great. As a user, I just don't care, since my files/PGP keys/mp3z/etc are all gone.
Of course, with the number of local root holes in GNU/Linux systems lately, I basically can't really trust the system anyway.
Virtual packages are used extensively in Debian. I've generated a list of Debian virtual packages from the packages available via apt-cache dumpavail to demonstrate this.
The list was constructed by taking the set of all packages that are Provided by other packages, and removing the set of all real packages and the set of packages that are Replaced by other packages. (This is more accurate than aptitude's algorithm, which apparently doesn't account for Replaced packages.)
Here is the result - 608 virtual packages (note that a few of them, such as mplayer, are from third-party package sources):
[Sigh. I've also crammed them all onto one line, since Slashdot complained that my "comment has too few characters per line (currently 14.2)".]
No electronic contrivance is ever going to be more reliable than a spring loaded hammer released by a lever (trigger),
I disagree. LEDs, for example, are much more reliable than that. However, no electronic contrivance that controls a spring-loaded hammer released by a lever is ever going to be more reliable than a spring-loaded hammer released by a lever on its own.
gvim has a nice interface. The only thing you need to know is to press "i" to turn on insert mode (and if you use "easy mode", you don't even have to do that).
Slashdot Mirror
+1, Informative? Heh.
Patents pending.
Or, in French, you'd tell them to Google ça .
My god, have you ever actually *used* Microsoft Windows? I'd hardly call it "good and usable".
Avoiding inter-frame compression means that, if you have some small amount of data corruption, you only get one, maybe two corrupted frames of video.
And if your system's security is ever compromised, then the *attacker* will know about it, too. This would result in two things:
The problem is that secure password authentication schemes like SRP are patented. We'll see secure password-based systems in 10-20 years.
If you (as an employer) are laying someone off, you don't need to show cause, but you have to give prior notice, or pay in lieu of notice.
If you are firing someone, you can do it immediately, but if they sue you for wrongful dismissal, they will probably win unless you can show cause.
That's my understanding of it, anyway.
What for? That pretty much goes against the whole concept of free software.
There is no EULA prompt when you use the installer. If you don't have Windows, you can download the zip file.from my site.
Permission to copy, display and distribute this document is available at: http://msdn.microsoft.com/library/en-us/odcXMLRef/ html/odcXMLRefLegalNotice.asp
IIRC, SSH is illegal in China.
The problem with that is that suddenly "oh, he wanted me to kill him" becomes every murderer's excuse.
The question is not "why *shouldn't* you be able to get a patent", but "is there a significant net benefit to society to enforce a patent on your behalf, versus not doing so?"
I don't think it's the same guys running it. Jay Miner, for example, died over a decade ago.
GAMES! Well, and genlocking. ;-)
Note, a lot of the stuff mentioned didn't work on OS 1.x, which might have been all that was available at the time, so don't feel too badly.
On the other hand, *my* Rev 5 A500 only had Kickstart 1.2, and it still kicked butt for years! :-)
The *only* reason I'd care is that I can still probably trust the system binaries (e.g. programs like sha1sum won't be trojan horses). As an admin, that's great. As a user, I just don't care, since my files/PGP keys/mp3z/etc are all gone.
Of course, with the number of local root holes in GNU/Linux systems lately, I basically can't really trust the system anyway.
Virtual packages are used extensively in Debian. I've generated a list of Debian virtual packages from the packages available via apt-cache dumpavail to demonstrate this.
The list was constructed by taking the set of all packages that are Provided by other packages, and removing the set of all real packages and the set of packages that are Replaced by other packages. (This is more accurate than aptitude's algorithm, which apparently doesn't account for Replaced packages.)
Here is the result - 608 virtual packages (note that a few of them, such as mplayer, are from third-party package sources):
[Sigh. I've also crammed them all onto one line, since Slashdot complained that my "comment has too few characters per line (currently 14.2)".]
alias alsa alsadriver alsalib-dev alsaplayer-interface alsaplayer-output amarok-engine apache2-dev apache2-modules aptitude-doc asd aspell-dictionary audio-mixer autoinstall-arch automaken awk babel bacula-director beecrypt-dev blas2 blas2-dev bnlib-dev bochs-gui c++-compiler c-compiler c-compiler-avr c-compiler-m68hc11 c-sharp-compiler c-shell cfengine-skolelinux cheetah chill-compiler cl-imho-web-connector cl-sql-backend cl-uncommonsql-backend clanlib0-display clanlib0-input cli-common cli-runtime cli-virtual-machine conch console-utilities cracklib-dev ctags cyphesis-cpp-game debconf-2.0 dict-client dict-server diskless-image docbk-xml doom-engine doom-wad doom-wad-editor dotfile-module dtp-i2o-raidutils dyndns-client ecpg editor elf-binutils elf-libgdbm emacsen endeavour enlightenment-theme entity-perl epic4-script epos-sound-data exim4-config-2 ext2fs-dev ezpublish festival-voice fftw-double-dev fftw-single-dev fftw2-double fftw2-single finger-server firebird2-server flask flite-dev fortran-compiler fortran77-compiler fortran95-compiler fortune-cookie-db freeciv-client freecraft-data freeglut-dev freetds freetype2-dev fsck-backend fwbuilder-backend fwbuilder-frontend gap-pkg-ctbllib gap-pkg-matrixss gap-pkg-tomlib gap-prim gap-small gap-trans gcc-docs gcompris-sound gdk-imlib gdk-imlib-development gforge-db gforge-dns gforge-ftp gforge-ldap gforge-lists gforge-mta gforge-shell gforge-web ggz-core-client ggz-graphical-client ghc-hopengl ghc-prof giflib-dev gift-client gift-plugin gimp2.0 glibc-2.3.2.ds1-20 gmt-coastline-data gnue-forms gnustep-base-dev gnustep-gui-dbg gnustep-gui-dev gnustep-xgps gopher-client gopher-server gstreamer-audiosink gstreamer-videosink gstreamer0.8-audiosink gstreamer0.8-colorspace gstreamer0.8-videosink gtk+2.0-directfb0-udeb gtkgl-dev gtkglarea-dev guile gvim haskell-compiler hostap-modules httpd httpd-cgi i18ndata i2c-mod-2.9 i386 ifupdown-scripts ike-server imap-client imaze imho imlib imlib-development inetd info-browser iraf-common irc ispell-dictionary itcl-dev itcl-doc itclsh itk-dev itk-doc itkwish iwidgets-doc j2re1.3 j2re1.5 j2sdk1.3 j2sdk1.5 jabberd2 java-compiler java-virtual-machine java1-runtime kakasi-dev kde-i18n kernel-doc-2.2 kernel-doc-2.4 kernel-doc-2.6 kernel-headers kernel-image kernel-source kernel-tree-2.4.24-1 kernel-tree-2.4.25-1 kernel-tree-2.4.26-1 kernel-tree-2.4.27-1 kernel-tree-2.6.10-1 kernel-tree-2.6.8-1 kernel-tree-2.6.9-1 killustrator koffice-i18n konversation-doc kwave-doc kworldwatch ladspa-host ladspa-plugin lambdamoo-core lambdamoo-server langband-variant lapack2 lapack2-dev ldap-client ldap-server lg-issue libacme-brainfuck-perl libadasockets-dev liballegro3.9.37-dev libannodex-dev libapache-mod-roaming libapr-dev libapt-inst-libc6.3-5-1.0 libapt-pkg-libc6.3-5-3.3 libardour-dev libarpack libaspell11 libasprintf-dev libasprintf0 libastro-fits-header-cfitsio libatlas-3.so libatlas.so.3 libatm-dev libawe-dev libblas-3.so libblas.so.3 libbluetooth-dev libc-dbg libc-dev libc-pic libcairo-dev libcgi-kwiki-perl libcgicc-dev libchipcard-dev libchipcard-pcsc-card-perl libclamav libclamav-dev libcmml-dev libcomerr-kth-compat libcupsimage-dev libcupsys-dev libdancer-xml-dev libdb++-dev libdb-dev libdb-java li
apt-get install debsums
Here's a guess.
I disagree. LEDs, for example, are much more reliable than that. However, no electronic contrivance that controls a spring-loaded hammer released by a lever is ever going to be more reliable than a spring-loaded hammer released by a lever on its own.
Why? People have been using length+data encodings for decades.
Transistors? Pah! Those can't even survive the EMP from a nuclear blat!
gvim has a nice interface. The only thing you need to know is to press "i" to turn on insert mode (and if you use "easy mode", you don't even have to do that).