The best example to support the fact that "a virus wants to hurt its host as little as possible" would be, say, herpes simplex. I heard at one point that 80% of the entire world population carries it, and carriers will be carriers for life. Herpes simplex (note: -not- genital herpes) is probably the best virus in existance today, evolutionarily.
What excatly dictates whether something will have support for this? The goggles, the card, the game, the OS, two, or three, or all four?
On a side note, I remember back in the day there was a series of games for win3.1 that was distributed with your old-skool red-blue goggles, and the game divided the graphics into red and blue. This was back in the day, so it wasn't great graphics, but it was a break from the usual. Also, no headaches with red-blue!
It's not hard to understand this change. I doubt that Radio Shack, like other companies, has ever been concerned about your privacy, before or now. What they do care about, on the other hand, is money. This just goes to show you that asking for that information was freaking out a whole bunch of people that didn't come back (to buy more stuff). Like one other person noted, in Europe they were Tandy but apparently they died out.
Step 1: More privacy
Step 2: Less freak-outs
Step 3: Profit!!
I've seen all these posts about how the BBC uses vans and the principle of heterodyning to sniff out people without a license.
I don't live in the UK and I don't know anything about it, but I'm curious now. What's the scoop on TV licensing in the IK?
Now maybe my flash plugin will work well. Every time I view some flash thing, it goes WAY too fast. If Macromedia appreciates open source maybe it won't write shit plugins for open source OSes. This may just be my thing - this didn't happen with Red Hat 7.1, but it does now with Mandrake 8.1.
DESCRIPTION fridged is a refrigerator server for use with LG Appli- ances systems. Is is part of the standard Internet Fridge distribution. It implements the FOOD protocol described in RFC 9999. With no arguments, fridged will configure based on /etc/food.conf and listen on port 61453 (0xF00D) for food requests based on FOOD. fridged should be run as root to access/var/foodtab, the internal storage of food data. The list of clients authorized to take food is stored in/etc/food.conf.
OPTIONS -allowfatass Allows FOOD clients to send multiple requests and stay-alive connections. By default, fridged will allow only a healthy number of connections by one client.
-c config-file Uses config-file as the configuration file instead of default/etc/food.conf.
DESCRIPTION fridge is a refrigerator client that sends food requests to a server implemeting the FOOD protocol described in RFC 9999. By default, fridge will send the requests to food://127.0.0.1 so you don't take things out of other peoples' fridged(8)'s. The FOOD server may require you to identify yourself and fridge will do so.
OPTIONS -e Eat the whole frickin' thing you requested right here. God, you pig. An instance of fridged(8) run without using the -allowfatass option will not respond to requests using the -e option.
-s food-server Connect to food-server instead of the default food://127.0.0.1
food-requested The FID (food ID of the food requested). An RFC 9999 compliant fridge-server will look up a plaintext name of the food and use that FID.
Slashdot Mirror
The best example to support the fact that "a virus wants to hurt its host as little as possible" would be, say, herpes simplex. I heard at one point that 80% of the entire world population carries it, and carriers will be carriers for life. Herpes simplex (note: -not- genital herpes) is probably the best virus in existance today, evolutionarily.
ANYTHING can be challenged. Evolution has been challenged. Gravity was challenged. This isn't new; just more evidence.
On a side note, I remember back in the day there was a series of games for win3.1 that was distributed with your old-skool red-blue goggles, and the game divided the graphics into red and blue. This was back in the day, so it wasn't great graphics, but it was a break from the usual. Also, no headaches with red-blue!
Could someone please explain what BBSes are used for now, in 2002? The Internet does a great job for warez and pr0ns of all sorts.
Note to moderators: I'm not trolling, or being offtopic, or being flamebait. This can be a legit discussion.
Step 1: More privacy
Step 2: Less freak-outs
Step 3: Profit!!
I've seen all these posts about how the BBC uses vans and the principle of heterodyning to sniff out people without a license. I don't live in the UK and I don't know anything about it, but I'm curious now. What's the scoop on TV licensing in the IK?
Now maybe my flash plugin will work well. Every time I view some flash thing, it goes WAY too fast. If Macromedia appreciates open source maybe it won't write shit plugins for open source OSes. This may just be my thing - this didn't happen with Red Hat 7.1, but it does now with Mandrake 8.1.
fridged(8)
/etc/food.conf and listen on port 61453 (0xF00D) for /var/foodtab, /etc/food.conf.
/etc/food.conf.
/etc/food.conf
/var/foodtab
NAME
fridged -- LG Internet Fridge server
SYNOPSIS
fridged [ -allowfatass ] [ -c config-file ]
DESCRIPTION
fridged is a refrigerator server for use with LG Appli-
ances systems. Is is part of the standard Internet
Fridge distribution. It implements the FOOD protocol
described in RFC 9999.
With no arguments, fridged will configure based on
food requests based on FOOD.
fridged should be run as root to access
the internal storage of food data.
The list of clients authorized to take food is stored
in
OPTIONS
-allowfatass
Allows FOOD clients to send multiple requests
and stay-alive connections. By default, fridged
will allow only a healthy number of connections
by one client.
-c config-file
Uses config-file as the configuration file
instead of default
FILES
Default configuration file
Table of stored food
SEE ALSO
fridge(8), RFC 9999.
fridge(8)
NAME
fridge -- LG Internet Fridge client
SYNOPSIS
fridge [ -e ] [-s food-server] food-requested
DESCRIPTION
fridge is a refrigerator client that sends food requests
to a server implemeting the FOOD protocol described in
RFC 9999. By default, fridge will send the requests to
food://127.0.0.1 so you don't take things out of other
peoples' fridged(8)'s. The FOOD server may require you
to identify yourself and fridge will do so.
OPTIONS
-e
Eat the whole frickin' thing you requested right
here. God, you pig.
An instance of fridged(8) run without using the
-allowfatass option will not respond to requests
using the -e option.
-s food-server
Connect to food-server instead of the default
food://127.0.0.1
food-requested
The FID (food ID of the food requested). An
RFC 9999 compliant fridge-server will look up
a plaintext name of the food and use that FID.
SEE ALSO
fridged(8), RFC 9999.