The CMOS memory in your PC is only used for BIOS settings. Mr. Gates and Windows doesn't save anything there (can you imagine if they did ? Oh My God !!!!) and neither does Linux.
The "registry" is a system database used by Windows and is stored as a file (or several files if I remember correctly) on your HD (somewhere in C:\Windows). The function of the registry is to ensure that a Windows system is as unreliable and unmaintainable as possible and to cause maximum user/administrator frustration as frequently as possible.
Look on it as a kind of "all your eggs in one basket" approach to system status and configuration storage. If anything untoward happens to the registry then you can use the wonderful GUI application called the "registry editor" to totally hose your system beyond any hope of repair. "The registry" also ensures that when you reinstall your OS, you have to reinstall and configure all your apps again as it is not easily restored from backup (I've tried this a few times in the past, each time without success). I don't know what possessed the engineers at Microsoft to come up with something so totally, completely, utterly, incredibly and massively stupid. Insanity ! Honestly, what a tw*t the guy who thought it up must have been. The registry is a software equivalent of a "Crime against humanity" IMHO.
Linux on the other hand has no "registry" as such (thank The Lord). Everything to do with setup and configuration is stored in these wonderfully high tech things called, for want of a better word, "text files". Each app has it's own configuration "text file" which can be edited with a special registry editor called a "text editor". In 90% of cases, if anything untoward happens to one of these text files then, it has no particular effect on your system whatsoever, only the app to which it applies. If you reinstall your OS and have made a backup of these "text files" then you can just copy them back to their original place and everything is hunky dory again. Also, if you cock up one of the configuration text files that does have an adverse effect on your system, you can even boot from a rescue floppy and use a "text editor" to repair the file and fix things again.
Linux, thankfully has to share nothing with Windows with the exception of
Sorry folks, XP is suppose to be wanting to be able to use a few of bytes of programable cmos for an individual machine security identifier. Whether they get it in and working I don't know and yes there are some spare spots at the top although not all cmos recognizes the address thankfully which ?may slow them down a year or two. It's also suppose to tie devices in so swapping or changes can't be done illegally on warrenty hardware as most hardware nowadays has firmware that can be programmed. How it will affect swapping of modules and upgrading of hardware I don't know. scsijon ----- Original Message ----- From: "Sean Akers" <sean.akers@ntlworld.com> To: <suse-linux-e@suse.com> Sent: Thursday, May 31, 2001 8:23 PM Subject: Re: [SLE] The Registry. the MBR record and partition tables on your HD. So don't worry about dual booting.
Sean.
Geoff Bagley <geoff@gcbagley.demon.co.uk> 05/31/2001 09:50 AM CET
To: suse-linux-e@suse.com cc: bcc: Subject: [SLE] The Registry.
All our PCs have a "registry", usually in CMOS memory.
Our experience suggests that all sorts of horrid things may lurk there. To Windows users it is kept a dark secret.
Does this range of memory appear anywhere in our LINUX file structure, where would it be mounted, and what happens in a dual-boot system where we have to share it with Bill Gates ?
Regards. -- Geoff Bagley
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
They did this sort of thing with the tulip based Nics. They tied a feature into the win OS that would wake sleeping nics to access a systems for WOL and WOR (wake on Lan and wake on ring) features. I had to buy a new nic because my linksys used a tulip drivers. It did recognize the internal connection but wouldn't recongize the the external. Nothing like seeing the little green light that shows the computer is talking to the nic but not talking to the cable modem. Corel linux and the tulip drivers at the time weren't setup to wake/make active the sillything - essentially I had a Win-Nic (just great). the D-link used different technology and I had no problem (they had a fairly extensive article about them on the net about a year ago). If they start pulling this stunt then I and my friends will have to boycott/avoid computers that place access space for M$ code and products in their bios. Just MHO, Curtis On Thursday 31 May 2001 05:48 am, scsijon wrote:
Sorry folks, XP is suppose to be wanting to be able to use a few of bytes of programable cmos for an individual machine security identifier. Whether they get it in and working I don't know and yes there are some spare spots at the top although not all cmos recognizes the address thankfully which ?may slow them down a year or two. It's also suppose to tie devices in so swapping or changes can't be done illegally on warrenty hardware as most hardware nowadays has firmware that can be programmed. How it will affect swapping of modules and upgrading of hardware I don't know.
scsijon ----- Original Message ----- From: "Sean Akers" <sean.akers@ntlworld.com> To: <suse-linux-e@suse.com> Sent: Thursday, May 31, 2001 8:23 PM Subject: Re: [SLE] The Registry.
The CMOS memory in your PC is only used for BIOS settings. Mr. Gates and
Windows doesn't save anything there (can you imagine if they did ? Oh My God !!!!) and neither does Linux.
The "registry" is a system database used by Windows and is stored as a
file (or several files if I remember correctly) on your HD (somewhere in C:\Windows). The function of the registry is to ensure that a Windows system is as unreliable and unmaintainable as possible and to cause maximum user/administrator frustration as frequently as possible.
Look on it as a kind of "all your eggs in one basket" approach to system
status and configuration storage. If anything untoward happens to the registry then you can use the wonderful GUI application called the "registry editor" to totally hose your system beyond any hope of repair. "The registry" also ensures that when you reinstall your OS, you have to reinstall and configure all your apps again as it is not easily restored from backup (I've tried this a few times in the past, each time without success). I don't know what possessed the engineers at Microsoft to come up with something so totally, completely, utterly, incredibly and massively stupid. Insanity ! Honestly, what a tw*t the guy who thought it up must have been. The registry is a software equivalent of a "Crime against humanity" IMHO.
Linux on the other hand has no "registry" as such (thank The Lord).
Everything to do with setup and configuration is stored in these wonderfully high tech things called, for want of a better word, "text files". Each app has it's own configuration "text file" which can be edited with a special registry editor called a "text editor". In 90% of cases, if anything untoward happens to one of these text files then, it has no particular effect on your system whatsoever, only the app to which it applies. If you reinstall your OS and have made a backup of these "text files" then you can just copy them back to their original place and everything is hunky dory again. Also, if you cock up one of the configuration text files that does have an adverse effect on your system, you can even boot from a rescue floppy and use a "text editor" to repair the file and fix things again.
Linux, thankfully has to share nothing with Windows with the exception of
the MBR record and partition tables on your HD. So don't worry about dual booting.
Sean.
Geoff Bagley <geoff@gcbagley.demon.co.uk> 05/31/2001 09:50 AM CET
To: suse-linux-e@suse.com cc: bcc: Subject: [SLE] The Registry.
All our PCs have a "registry", usually in CMOS memory.
Our experience suggests that all sorts of horrid things may lurk there. To Windows users it is kept a dark secret.
Does this range of memory appear anywhere in our LINUX file structure, where would it be mounted, and what happens in a dual-boot system where we have to share it with Bill Gates ?
Regards. -- Geoff Bagley
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (3)
-
Curtis Rey -
scsijon -
Sean Akers