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!
Notices
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.
The /proc filesystem is a virtual one, the files in there aren't real and the filesystem as a whole is simply an interface to some of the information the kernel is holding in memory.
Can I ask why you would want to edit that file in the first place?
I'll answer the question as yes you could edit the file with vi and save changes given that the user has privelages to do so. Root is probably the only one.
Now would those changes completely fubar your system? I don't know, I see no reason to change that information. Like cs-cam, I'm interested in the Why question.
-- edit --
bummer, I click on cs-cam's link. It said my brain was eaten
Last edited by musicman_ace; 07-31-2006 at 02:18 AM.
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.
Thanks a lot every body for the kind reply of my issue
The only reason why do i need to modify /proc/cpuinfo was because i'm working for security software.
The software will ignore if the system running with Celeron "D" processor
The idea if i could change the information on /proc/cpuinfo so the problem solved
I got frustated with this issue, ihope sombody could help me
I beleave there is a way to do that, some thing like doing path may be
/proc/cpuinfo reflects what is actually installed in your machine. I think one respondent had it right: "Change /proc/info by putting in a different cpu/".
I suggest that you give us some more details as to what you are up to. WHAT security SW??
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
It is not for Microsoft product, the software I've developt is for Military waepon, before the program getting up, my program will check hardware routine...
My company doesn't supply the hardware they use, that why we must protect our software... we just don't know the software don't work perfectly in Celeron...
So, when the user start the program it will doing check first.. if found celeron it will turn it off automatically..
That why i need to modify the information on /proc/cpuinfo
if i just modify the description "Celeron(R)" to "Pentium(R)" all my problem will solve.
alternatively we could by a new pentium... but the government already purchace 1000 celeron...
Location: kinda transient right now. Utah is Home, staying in Ohio
Distribution: Mandrake 9.1/Windows XP
Posts: 46
Rep:
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:
Quote:
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.
//funnyFlag 1
Last edited by AmphetaminePhreak; 08-02-2006 at 06:56 AM.
Heh, yea just tell us all about this military weapon we could do something about it..patches for you, you know..like backdoors that only open using some arabic letters or something..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.