In your scenario, the bioluminescent gene would be a major survival disadvantage. Any glowing bugs would be killed much quicker than their non-glowing counterparts, and the glowing gene wouldn't propagate. The only genes which will be passed on to successive generations are the ones which convey some sort of advantage. That's how evolution works.
The 0.3 code that code.shtml links to has many known bugs. A lot of those have been fixed in 0.3-3.7, available here. There is a mailing list, slash-help, for help with Slash problems.
Hmm, I have Cablevision (Optimum Online) cablemodem. It's great - fast, the only software needed is dhcpcd, "practically static" IPs (theoretically they could change, but according to tech support "that will only happen if something goes really wrong.") with really static IPs in the near future, and only something like $40/mo
Okay, here's what I did to get it working. First, install the GLX package from nvidia at http://www.n vidia.com/Marketing/Products/Pages.nsf/pages/linux download. Make sure you put the 'Load "glx.so"' stuff in XF86Config as per NVidia's instructions. Copy the libGL.so that comes with GLX into the q3demoTEST directory. Then, start X in 16bpp mode. Once X starts, cd q3demoTEST ;./linuxquake3 and frag away.
Either the doctor and patient could and sign each other's PGP keys when they meet for a checkup. That only works if doctors and patients physically meet at some point. If that doesn't happen, you can just take whatever system you have for giving out usernames/passwords and have it sign PGP keys instead.
Well the messages would be stored encrypted on the computers. Attacking the computers could get you the private keys, but you would still need the passphrase.
Why don't you just have the patient send an email to the doctor signed with the patient's PGP key and encrypted with to the doctor's PGP key? Doctor->patient messages would work the same way. That would be more secure and not difficult to implement.
For help on Slash, check out the Slash-Help mailing list at this address. Allowing anyone to post a toplevel story shouldn't be too difficult a modification to make - just move some code out of admin.pl.
Oh, and you might have better work with Slash 0.3-3.7 than the stock versions that Rob puts out. Those versions are quite buggy. Oh, btw, there's also NNTP support for Slash.
I'm the one who put out newsd and the 0.3-3.7 tarball. I also seem to be making the most noise about adding functionality to Slash on slash-help. In fact, someone just offered to host a Slash CVS repository for me and I'm forking the code (see slash-help - especially the recent YA0.4W thread - for the gory details of why.)
(I've sent a copy of this reply to the original poster via email since I don't know if he's still reading this story or not.)
(Camera opens on an overworked housewife, looking at a BSOD.) "Not again! If only I had a way to get rid of those stubborn blue screens!"
Announcer: "Here, try the new Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM)!"
(screen sparkles and is replaced by big smiley penguin. Housewife no longer works overworked and has new hair-do) Housewife: "Thank you Mr. Tux!"
Announcer: "The Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) gets rid of blue screens in a flash! It forks! It blits! Look at those fantastic pixels! It surfs the web! You could even host an ISP with it!
(Camera shows Happy Guy sitting at desk with placard: President, SurfTheWeb Co.) "Thank you Mr. Tux!"
Announcer: All this an hundred more handy-dandy functions, including the patented Gates-Be-Gone(TM), can be yours for only four easy payments of $4.95! It's not sold in any stores! But wait, there's more! Order now and you'll also get "The Complete Guide To Debian"
(camera shows Happy Brother and Sister holding Debian book) Happy Kids: "That's super, Mr. Tux!"
(camera shows Tux) "When a complete stranger walks up to you and says 'Gee, your server smells terrific!', you know you're using the right operating system. I'm not only the president Tux-co, I'm also a user. I liked the product so much, I bought the company. The new Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) has my personal guarantee." (small print: "not a guarantee")
Announcer: "Just call 1-800-4-DEBIAN to order the new Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM)! Operators are standing buy! Have your Visa or MasterCard ready, or send a check or money order to P.O. Box 34146, Blair, NE 10013. Sorry, no C.O.D.s accepted.
I think that a lot of the trouble could be avoided if authors showed more discretion in what they posted. IMHO, Slashdot shouldn't be posting rumors unless there's a high degree of truth to them. Why would the Prix Arxs Electronica jury be announcing that MS was making a Linux distro? Slashdot had no business posting that. Maybe there could even be a seperate section for rumors.
How to secure a Linux machine that people will have physical access to:
Disable booting from anything but HD in the BIOS
Set a BIOS password
In/etc/lilo.conf, set a password on all linux images. Use the restricted option so you only need the password if you're modifying LILO parameters (normal boot will work w/o password, but linux init=/bin/sh won't).
Encrypt the filesystem on the hard disk. Store the key on a floppy that you'll need to put in whenever you reboot. Guard this floppy with your life.
There, now your box should be secure against physical attacks.
Yes, but with operating systems such as Linux and OpenBSD where the source code is available, White Hats can look for security holes preemptively. With Windows, there might be huge gaping flaws that are known internally at Microsoft but ignored because "no one will figure them out."
Slashdot Mirror
There is a program available, which I wrote, which adds NNTP support to Slash. The newsd home page has a link.
In your scenario, the bioluminescent gene would be a major survival disadvantage. Any glowing bugs would be killed much quicker than their non-glowing counterparts, and the glowing gene wouldn't propagate. The only genes which will be passed on to successive generations are the ones which convey some sort of advantage. That's how evolution works.
The 0.3 code that code.shtml links to has many known bugs. A lot of those have been fixed in 0.3-3.7, available here. There is a mailing list, slash-help, for help with Slash problems.
There's an effort getting started to bring the current Slash code up to snuff. The homepage is here.
Hemos didn't say that, the person who submitted the story did.
Did you click on the "next" link at the bottom of the page?
"first wave of the pallet of the beginning"
Hmm, I have Cablevision (Optimum Online) cablemodem. It's great - fast, the only software needed is dhcpcd, "practically static" IPs (theoretically they could change, but according to tech support "that will only happen if something goes really wrong.") with really static IPs in the near future, and only something like $40/mo
Okay, here's what I did to get it working. First, install the GLX package from nvidia at http://www.n vidia.com/Marketing/Products/Pages.nsf/pages/linux download. Make sure you put the 'Load "glx.so"' stuff in XF86Config as per NVidia's instructions. Copy the libGL.so that comes with GLX into the q3demoTEST directory. Then, start X in 16bpp mode. Once X starts, cd q3demoTEST ; ./linuxquake3 and frag away.
It works beautifully with my Riva TNT2.
The word is denature.
Either the doctor and patient could and sign each other's PGP keys when they meet for a checkup. That only works if doctors and patients physically meet at some point. If that doesn't happen, you can just take whatever system you have for giving out usernames/passwords and have it sign PGP keys instead.
Well the messages would be stored encrypted on the computers. Attacking the computers could get you the private keys, but you would still need the passphrase.
Why don't you just have the patient send an email to the doctor signed with the patient's PGP key and encrypted with to the doctor's PGP key? Doctor->patient messages would work the same way. That would be more secure and not difficult to implement.
Help for people trying to run the Slash engine is available from The Slash-Help Mailing List.
Could you accomplish the same effect by having every workstation be a node in a cluster?
Oh, and you might have better work with Slash 0.3-3.7 than the stock versions that Rob puts out. Those versions are quite buggy. Oh, btw, there's also NNTP support for Slash.
I'm the one who put out newsd and the 0.3-3.7 tarball. I also seem to be making the most noise about adding functionality to Slash on slash-help. In fact, someone just offered to host a Slash CVS repository for me and I'm forking the code (see slash-help - especially the recent YA0.4W thread - for the gory details of why.)
(I've sent a copy of this reply to the original poster via email since I don't know if he's still reading this story or not.)
(Camera opens on an overworked housewife, looking at a BSOD.) "Not again! If only I had a way to get rid of those stubborn blue screens!"
Announcer: "Here, try the new Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM)!"
(screen sparkles and is replaced by big smiley penguin. Housewife no longer works overworked and has new hair-do) Housewife: "Thank you Mr. Tux!"
Announcer: "The Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) gets rid of blue screens in a flash! It forks! It blits! Look at those fantastic pixels! It surfs the web! You could even host an ISP with it!
(Camera shows Happy Guy sitting at desk with placard: President, SurfTheWeb Co.) "Thank you Mr. Tux!"
Announcer: All this an hundred more handy-dandy functions, including the patented Gates-Be-Gone(TM), can be yours for only four easy payments of $4.95! It's not sold in any stores! But wait, there's more! Order now and you'll also get "The Complete Guide To Debian"
(camera shows Happy Brother and Sister holding Debian book) Happy Kids: "That's super, Mr. Tux!"
(camera shows Tux) "When a complete stranger walks up to you and says 'Gee, your server smells terrific!', you know you're using the right operating system. I'm not only the president Tux-co, I'm also a user. I liked the product so much, I bought the company. The new Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM) has my personal guarantee."
(small print: "not a guarantee")
Announcer: "Just call 1-800-4-DEBIAN to order the new Tuxomatic 2200(TM) with patented Gates-Be-Gone(TM)! Operators are standing buy! Have your Visa or MasterCard ready, or send a check or money order to P.O. Box 34146, Blair, NE 10013. Sorry, no C.O.D.s accepted.
I think that a lot of the trouble could be avoided if authors showed more discretion in what they posted. IMHO, Slashdot shouldn't be posting rumors unless there's a high degree of truth to them. Why would the Prix Arxs Electronica jury be announcing that MS was making a Linux distro? Slashdot had no business posting that. Maybe there could even be a seperate section for rumors.
There, now your box should be secure against physical attacks.
Debian has a package called dhcp-dns which I believe implements DDNS.
mSQL: M-S-Q-L
PostgreSQL: POSTgrehs-Q-L
Yes, but with operating systems such as Linux and OpenBSD where the source code is available, White Hats can look for security holes preemptively. With Windows, there might be huge gaping flaws that are known internally at Microsoft but ignored because "no one will figure them out."
Hmm, I hope "first post" is TM-able. That way Rob can trademark it and sue all the ACs who use it without his permission!