Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Agreed - cpuinfo reflects what's installed, and if you want to change it you need to install a different CPU. To say it another way, I can't really think of any useful reason to "change it". That's sort of like saying "I've got a 40G drive, but I want it to appear as though it is a 100G drive". It doesn't make any sense, and doesn't match reality. Rather than to change cpuinfo, you might want to ask the other guys at your security company why they disabled their software for Celeron D processors.
alternatively he can just change the L2 cache of 256 to 128kb so that it becomes in class of Celeron and Not CELERON-D ..... so no kinda overclocking or risk of hangups?????..........that might have happened if he did from 256 to 512kb which made it a Pentium ?
But why such an apparently dumb and useless security feature?....... I bet its for microsoft's vista
Location: kinda transient right now. Utah is Home, staying in Ohio
Distribution: Mandrake 9.1/Windows XP
blaaaaaahahahahahah! i fell out of my chair. they should make a forum section for the funniest posts ever, and an option to rate veiwed posts as criteria for humor raiting. i'd vote for this one to be put there for sure.
#1 response, this guy:
He probably wants to boast of a faster cpu than he really has got. Maybe if you copy everything in proc into a diffrent directory, than disable proc in fstab.
Maybe you could change the directory of proc in fstab into /tmp/proc, and put up links of everything into /proc, then you could edit the cpuinfo file manually
Have not tried this though, and I belive quite a few programs use proc. I think that's the reason why we keep it around. After all we do have sysfs now.
however, someone may actually follow your directions and that would be nasty.
Last edited by AmphetaminePhreak; 08-02-2006 at 07:56 AM.