No, in this case the immune system attacked the worm that was put into his system. I believe it was quite experimental, in Europe somewhere. I'll post if I can find more info on it.
I have spotted a few places that do indeed say that increasing iodine intake does seem to counter some of the effects somewhat (one mentioned iodine in salt). I have not looked into this too much, so can't say anything definite.
As for the sugar thing, as I mentioned in another post, floride effects insulin effectiveness, which is of cause responsible for regulating carbohydrate metabolism. Google for 'fluoride insulin' for more (without quotes).
You don't have to roll around in dirt, you just have to not go all-out-war on cleaning things. Girms will grow and spread on their own, and reach you in normal moderate amounts.
"A totally sanitised environment is no problem to be raised in as long you are going to continue living in it forever"
Untrue. There are more problems with an untrained immune system than just the fact that it won't strengthen. At the low end of the scale are allergies, where you develop an immunoresponse to things that aren't actually dangerous, and have to start avoiding certain foods that you'd otherwise be able to eat. At the other end of the scale are autoimmune problems; where the immune system starts to attack you itself. I recall a case of a guy who's immune system was attacking his own intestines. They countered this by (yeah, I know) giving him *worms*, so that his immune system would turn against them instead, and, being occupied, allow his intestines to heal.
You immune system also fights many other things other than just outside invaders, such as cancer, which is a lot more common than you might think, but most of the time the immune system can take care of it and so it's not a problem.
So no, proper immuno development is essential, even if you can live in a sterilised environment all your life.
ever heard of scripts? As soon as there's a new version of say, apache out, I just run
dinst apache install
on each of the servers. It downloads, configures, compiles, and installs. It's a few more keypresses than 'yum update', but I'm a fast enough typer for that to be negligible. I also have clients who need apache/php/etc compiled with different flags, so my script remembers these and configures accordingly. It also does CPU detection to set cflags etc optimally, and after installing, restarts the services it needs to to put it into effect. I'm able to upgrade as soon as new versions/security fixes come out, without having to wait for the distro to make their own version and spread to mirrors etc. It's really not difficult, or time consuming, and when you need things set up your own way (such as when you offer custom services to your clients), distribution packages just don't work.
Just to point out tho, on the servers I do this for the larger packages. Stuff like bash or ncurses, there's little room for customising, and little need for up-to-the-second updates, so the distro does handly most of these.
I think people just want a kernel called 2.7... cuz they think incrementing the minor version one would make it cool again. I think for so many people, it's a name thing more than anything else.
Yeah... no. I like to work close to the source, as then it's more intuitive. If I change something, or want to compile something, it's exactly as the base system is, I don't have to figure out how this distro's decided to do thing this time.
So all packages I have to maintain (eg, on webservers) are compiled from source with the compile flags I need, into seperate directories to keep it tidier and... yeah, seperate. My kernel is compiled from source, and ready to load by itself (so I can jump between kernel versions without having to worry about keeping modules ready to be loaded for each one), and without having to keep some initrd updated for each kernel too.
What... what's wrong with being locked into a distro so you can't move in your own direction should you wish? Are you really asking me that question?
"The job of the distro is to keep all that taken care of for you"
Great, if you need someone else to take care of it for you, but one of the whole points of this open source malarkey is that you can have total control over your machine and the code it runs. Using a distro shouldn't mean signing over that control. Some people like to try the latest kernel, develop using it, or apply patches themselves without having to try get their distro to do it for them. Basically, different people have different needs and desires than you do, and while a distro lock-in might suit you, it doesn't everyone.
I didn't say "men and women are programmed to be into each other", dumbass, I said "we" are. For most of us, that's across gender, but for some, it's within the same. Your point?
"After only 3 months how can so much software be reliably tested?"
Which software exactly has only been tested for three months?
"I thought there was a bunch of static flying around about version 2.5 of the kernel"
The 2.5 kernel was a developers playground, experimentation etc, not meant to be a stable can-run-life-support OS. A place for the open exchange of ideas, that's all.
"If you build software on a broken foundation you will only get broken software"
Well what we're talking about here is people improving the quality and efficiency of the foundation, and releasing their work. This is a Good Thing(tm).
The stable/development branches might be a nice idea in theory, but in practice it doesn't work. Distros would ship, for example, a "stable" 2.4.xx kernel, except it wouldn't actually be that. They would spot nice features in the 2.5 kernel that they wanted to offer their users, and so back-port them... and any other nice patches floating around the net while they're at it. The result being that the kernels that ship with distros were so heavily modified, that stability (from one machine to another) went right out of the window. You couldn't go to kernel.org and download an updated kernel, as without all the patches, it wouldn't work. So you had to stick to the distro's kernels.
So instead, the 2.6 goal is to have development/stable parts of the cycle, rather than seperate branches. Roughtly: patches that could break things get submitted at the beginning of the cycle, and -pre1/-pre2 tarballs are released. If you want bleeding edge, you go here. Release candidates are released, where developers get chance to fix bugs etc in the code. Then, any code that's still [known to be] buggy gets dropped for the final release (eg, 2.6.17). The developer can work on it, and try add it again during subsequent cycles. When it works, it can be included in a final release.
During this cycle, security and other urgent bug fixes take place in the ultra-stable branch, with version such as 2.6.16.1, 2.6.16.2.
(This is the rough idea I believe, there could be some slight inaccuracies in how it actually takes place, I haven't followed it 100%, but this should be close enough to get the right idea).
What a load of crap. Firstly, the female form is a work of art (when things haven't gone horribly horribly wrong) that females can appreciate too. Secondly, unlike the things you bring issue with, the belief that women need to be sheltered, that they some how couldn't cope with a world not contrived to protect their fragile selves actually *is* sexist.
Guys will have female wallpaper because the female form is what they like to see. In the same way, girls will often like to see a bit of masculinity (granted most of slashdot and the like is more snide bitchiness than masculinity, which maybe has more to do with it). We're programmed to be into each other, it's natural, it's normal, and despite what religious teachings would have you believe, it's not dirty or wrong. Don't treat it as though it is.
I change the kernel more often than the hardware, to test the latest features, and compile all my drivers (network, filesystems etc) in, to make sure when the new kernel boots, I don't need to bother with my depmod / modules_install or anything like that. I even have enough memory to not notice a little bit taken up by a driver or two I'm not using. I like whatever I need to just be there, so whatever I'm doing with harddrives etc, doesn't matter. No more "crap, I can't access this filesystem without module x, which is -on- that filesystem" or anything like that. Simplicity.
"Step 1. In emergency, overwrite data with Chinese porn"
With their leaders faces superimposed over the pornstars faces? Saved in a directory called "spy results from china"? Then they'll -never- give Jack Bauer back!
"If you'll read my suggestion, it was to write an emulator (or API translator or whatever they require) and to build functionality into apps LIKE LINUX AND OTHER OS'S DO"
But this already IS the case. Different subsystems are provided by loading different libraries into the virtual memory space of the app that needs it. Just because they're including in the main windows install, doesn't mean they're built into the core. The windows install CD should be thought of more as a distribution that just a core OS. For example, in your system32 directory, there a files such as:
os2ss.exe - loads OS/2 subsystem (see also files in system32\os2) for OS/2 apps psxss.exe - likewise but for posix calls. win32k.sys - Win32 kmode subsystem, for fast GDI et al. ntvdm.exe - 16bit subsystem ("Virtual Dos Machine") for DOS and Win16 applications (further win16 support in windows\system directory).
These subsystems might not be shown to the end user as seperate applications, and you might not have "add/remove programs" for them, but that doesn't change what they are. In fact you can even add further subsystems, such as Win SFU,.Net, or Cygwin which is nothing to do with Microsoft (AND you can remove it).
The fact that Windows does all of this transparently, so you don't have to try compiling and/or configuring apps like WINE or DOSEmu, is one of it's key selling points.
"They want to modernize the OS and build in cool new features that will appeal to consumers, businesses, high performance users (story on Slashdot just a few days ago), handhelds (wait, Vista CE is coming), media players, Hollywood, and whatever else they can think of"
Firstly, CE is a different OS which runs different code, which shares the same name (for marketing purposes) and GUI style (for familiarity, and so they can use the same 'Windows' name, for the marketing thing). You're not gonna get CE by taking the main PC/OEM install CD, and removing some DLLs and switching some registry settings. So it's not the same OS trying to be two different things - it is two different things.
Secondly, whether it be media player, graphics workstation, servers, aimed at businesses or gamers, there's absolutely no reason why an OS shouldn't be able to do all this, and an OS that can't, isn't much of an OS at all. An equivalent: from your linux box, stop Apache, MySQL, vsftp, and start up KDE. Wow, it was a server, and now it's a desktop machine. All without rebooting and changing OS. It's the applications you run on top of the OS that decides its purpose, not the OS itself. The OS should stay out of the way enough to allow this (just like how the american government's supposed to keep out of it's people's affairs, to allow them to prosper and go in their own direction).
"Either that or write a really, really good emulator for their new OS. Otherwise they WILL eventually drown in legacy support"
You don't need emulators. What we have is something called an API, and Windows (as many other OSs) has something called 'subsystems', with different subsystems providing different API's. So, they can have their OS/2, Win16, Win32,.Net etc all there, next to each other, not intertwined. Just like Linux can provide Win16/Win32 API calls through Wine (which Is Not an Emulator), Windows can do the same. You don't need slow emulation when you use API layers.
Now maybe MS have made a mess of their code, but this is down to management, design and forward planning. It's not because of what they've tried to achieve, it's because of how they've tried to achieve it. Big difference.
Slashdot Mirror
Well it seems to have reached your brain, why wouldn't it reach your thyroid?
No, in this case the immune system attacked the worm that was put into his system. I believe it was quite experimental, in Europe somewhere. I'll post if I can find more info on it.
Yet I get modded flamebait!
I have spotted a few places that do indeed say that increasing iodine intake does seem to counter some of the effects somewhat (one mentioned iodine in salt). I have not looked into this too much, so can't say anything definite.
As for the sugar thing, as I mentioned in another post, floride effects insulin effectiveness, which is of cause responsible for regulating carbohydrate metabolism. Google for 'fluoride insulin' for more (without quotes).
"Care to site a source?"
this page: http://www.fluoridealert.org/health/thyroid/ lists a few. Try googling things like:
fluoride thyroid
Also effects carbohydrate metabolism thru interactions with insulin (also causing lethagy, weight gain), google for:
fluoride insulin
Note that on the insulin front, there will naturally be futher implications if someone already has insulin problems, such as diabetes.
This should be more than enough to get you started.
You don't have to roll around in dirt, you just have to not go all-out-war on cleaning things. Girms will grow and spread on their own, and reach you in normal moderate amounts.
Floride replaces iodine in the thyroid, upsetting the metabolism, causing weight gain and lethargy.
"A totally sanitised environment is no problem to be raised in as long you are going to continue living in it forever"
Untrue. There are more problems with an untrained immune system than just the fact that it won't strengthen. At the low end of the scale are allergies, where you develop an immunoresponse to things that aren't actually dangerous, and have to start avoiding certain foods that you'd otherwise be able to eat. At the other end of the scale are autoimmune problems; where the immune system starts to attack you itself. I recall a case of a guy who's immune system was attacking his own intestines. They countered this by (yeah, I know) giving him *worms*, so that his immune system would turn against them instead, and, being occupied, allow his intestines to heal.
You immune system also fights many other things other than just outside invaders, such as cancer, which is a lot more common than you might think, but most of the time the immune system can take care of it and so it's not a problem.
So no, proper immuno development is essential, even if you can live in a sterilised environment all your life.
ever heard of scripts? As soon as there's a new version of say, apache out, I just run
dinst apache install
on each of the servers. It downloads, configures, compiles, and installs. It's a few more keypresses than 'yum update', but I'm a fast enough typer for that to be negligible. I also have clients who need apache/php/etc compiled with different flags, so my script remembers these and configures accordingly. It also does CPU detection to set cflags etc optimally, and after installing, restarts the services it needs to to put it into effect. I'm able to upgrade as soon as new versions/security fixes come out, without having to wait for the distro to make their own version and spread to mirrors etc. It's really not difficult, or time consuming, and when you need things set up your own way (such as when you offer custom services to your clients), distribution packages just don't work.
Just to point out tho, on the servers I do this for the larger packages. Stuff like bash or ncurses, there's little room for customising, and little need for up-to-the-second updates, so the distro does handly most of these.
I think people just want a kernel called 2.7... cuz they think incrementing the minor version one would make it cool again. I think for so many people, it's a name thing more than anything else.
"Modern distros..."
Yeah... no. I like to work close to the source, as then it's more intuitive. If I change something, or want to compile something, it's exactly as the base system is, I don't have to figure out how this distro's decided to do thing this time.
So all packages I have to maintain (eg, on webservers) are compiled from source with the compile flags I need, into seperate directories to keep it tidier and... yeah, seperate. My kernel is compiled from source, and ready to load by itself (so I can jump between kernel versions without having to worry about keeping modules ready to be loaded for each one), and without having to keep some initrd updated for each kernel too.
Distros get in my way. Take me to the source.
"What's wrong with that?"
What... what's wrong with being locked into a distro so you can't move in your own direction should you wish? Are you really asking me that question?
"The job of the distro is to keep all that taken care of for you"
Great, if you need someone else to take care of it for you, but one of the whole points of this open source malarkey is that you can have total control over your machine and the code it runs. Using a distro shouldn't mean signing over that control. Some people like to try the latest kernel, develop using it, or apply patches themselves without having to try get their distro to do it for them. Basically, different people have different needs and desires than you do, and while a distro lock-in might suit you, it doesn't everyone.
I didn't say "men and women are programmed to be into each other", dumbass, I said "we" are. For most of us, that's across gender, but for some, it's within the same. Your point?
"After only 3 months how can so much software be reliably tested?"
Which software exactly has only been tested for three months?
"I thought there was a bunch of static flying around about version 2.5 of the kernel"
The 2.5 kernel was a developers playground, experimentation etc, not meant to be a stable can-run-life-support OS. A place for the open exchange of ideas, that's all.
"If you build software on a broken foundation you will only get broken software"
Well what we're talking about here is people improving the quality and efficiency of the foundation, and releasing their work. This is a Good Thing(tm).
The stable/development branches might be a nice idea in theory, but in practice it doesn't work. Distros would ship, for example, a "stable" 2.4.xx kernel, except it wouldn't actually be that. They would spot nice features in the 2.5 kernel that they wanted to offer their users, and so back-port them... and any other nice patches floating around the net while they're at it. The result being that the kernels that ship with distros were so heavily modified, that stability (from one machine to another) went right out of the window. You couldn't go to kernel.org and download an updated kernel, as without all the patches, it wouldn't work. So you had to stick to the distro's kernels.
So instead, the 2.6 goal is to have development/stable parts of the cycle, rather than seperate branches. Roughtly: patches that could break things get submitted at the beginning of the cycle, and -pre1/-pre2 tarballs are released. If you want bleeding edge, you go here. Release candidates are released, where developers get chance to fix bugs etc in the code. Then, any code that's still [known to be] buggy gets dropped for the final release (eg, 2.6.17). The developer can work on it, and try add it again during subsequent cycles. When it works, it can be included in a final release.
During this cycle, security and other urgent bug fixes take place in the ultra-stable branch, with version such as 2.6.16.1, 2.6.16.2.
(This is the rough idea I believe, there could be some slight inaccuracies in how it actually takes place, I haven't followed it 100%, but this should be close enough to get the right idea).
What a load of crap. Firstly, the female form is a work of art (when things haven't gone horribly horribly wrong) that females can appreciate too. Secondly, unlike the things you bring issue with, the belief that women need to be sheltered, that they some how couldn't cope with a world not contrived to protect their fragile selves actually *is* sexist.
Guys will have female wallpaper because the female form is what they like to see. In the same way, girls will often like to see a bit of masculinity (granted most of slashdot and the like is more snide bitchiness than masculinity, which maybe has more to do with it). We're programmed to be into each other, it's natural, it's normal, and despite what religious teachings would have you believe, it's not dirty or wrong. Don't treat it as though it is.
I change the kernel more often than the hardware, to test the latest features, and compile all my drivers (network, filesystems etc) in, to make sure when the new kernel boots, I don't need to bother with my depmod / modules_install or anything like that. I even have enough memory to not notice a little bit taken up by a driver or two I'm not using. I like whatever I need to just be there, so whatever I'm doing with harddrives etc, doesn't matter. No more "crap, I can't access this filesystem without module x, which is -on- that filesystem" or anything like that. Simplicity.
2.4.10... ahh, that brings back memories... that one rocked!
oh yeah :-/ so maybe encrypt it with the password alt+printscreen+b? That aught ta slow 'em down!!!
"Takes too long to drill the disks and insert the thermite, while your spy plane is spiralling down"
err... you'd drill and inject first, then if it goes down - detonate. From the inside. Not difficult.
Mac format the drive! That aught ta slow 'em down! ;-)
"Harddrive, if you get captured, you'll probably want to take your own life. Here, take this **passes hammer**"
I'm not sure an autonomous spy plane that's crashed could be relied on to hammer it's harddrive tho.
Why not just use volatile memory?
"Step 1. In emergency, overwrite data with Chinese porn"
With their leaders faces superimposed over the pornstars faces? Saved in a directory called "spy results from china"? Then they'll -never- give Jack Bauer back!
"or were you under the mistaken assumption that something actually moved when you hit that degauss button on your CRT monitor?"
:-)
:-p
If nothing moved, then it wouldn't make a noise. Every monitor I've ever hit degause on makes a noise, which means movement must be taking place
Okay, technically, this is effect not cause (which seems to be what you're talking about), but it's still movement
"If you'll read my suggestion, it was to write an emulator (or API translator or whatever they require) and to build functionality into apps LIKE LINUX AND OTHER OS'S DO"
.Net, or Cygwin which is nothing to do with Microsoft (AND you can remove it).
But this already IS the case. Different subsystems are provided by loading different libraries into the virtual memory space of the app that needs it. Just because they're including in the main windows install, doesn't mean they're built into the core. The windows install CD should be thought of more as a distribution that just a core OS. For example, in your system32 directory, there a files such as:
os2ss.exe - loads OS/2 subsystem (see also files in system32\os2) for OS/2 apps
psxss.exe - likewise but for posix calls.
win32k.sys - Win32 kmode subsystem, for fast GDI et al.
ntvdm.exe - 16bit subsystem ("Virtual Dos Machine") for DOS and Win16 applications (further win16 support in windows\system directory).
These subsystems might not be shown to the end user as seperate applications, and you might not have "add/remove programs" for them, but that doesn't change what they are. In fact you can even add further subsystems, such as Win SFU,
The fact that Windows does all of this transparently, so you don't have to try compiling and/or configuring apps like WINE or DOSEmu, is one of it's key selling points.
"They want to modernize the OS and build in cool new features that will appeal to consumers, businesses, high performance users (story on Slashdot just a few days ago), handhelds (wait, Vista CE is coming), media players, Hollywood, and whatever else they can think of"
.Net etc all there, next to each other, not intertwined. Just like Linux can provide Win16/Win32 API calls through Wine (which Is Not an Emulator), Windows can do the same. You don't need slow emulation when you use API layers.
Firstly, CE is a different OS which runs different code, which shares the same name (for marketing purposes) and GUI style (for familiarity, and so they can use the same 'Windows' name, for the marketing thing). You're not gonna get CE by taking the main PC/OEM install CD, and removing some DLLs and switching some registry settings. So it's not the same OS trying to be two different things - it is two different things.
Secondly, whether it be media player, graphics workstation, servers, aimed at businesses or gamers, there's absolutely no reason why an OS shouldn't be able to do all this, and an OS that can't, isn't much of an OS at all. An equivalent: from your linux box, stop Apache, MySQL, vsftp, and start up KDE. Wow, it was a server, and now it's a desktop machine. All without rebooting and changing OS. It's the applications you run on top of the OS that decides its purpose, not the OS itself. The OS should stay out of the way enough to allow this (just like how the american government's supposed to keep out of it's people's affairs, to allow them to prosper and go in their own direction).
"Either that or write a really, really good emulator for their new OS. Otherwise they WILL eventually drown in legacy support"
You don't need emulators. What we have is something called an API, and Windows (as many other OSs) has something called 'subsystems', with different subsystems providing different API's. So, they can have their OS/2, Win16, Win32,
Now maybe MS have made a mess of their code, but this is down to management, design and forward planning. It's not because of what they've tried to achieve, it's because of how they've tried to achieve it. Big difference.