Login Form






Lost Password?
No account yet? Register

Syndicate


SUSE 9.1 Professional PDF Print E-mail
 
During the last week I had the opportunity to test the Proffesional new version of SUSE 9.1. As is usually the first impression is often BlackBerry Software Links patrocinados no Google Bungalow the most important, I was afraid to open the box. Collected a little courage I opened it. I could not go with admiration. SUSE AG postarala really to give SUSE. Yes it should appear each boxed version of GNU / Linux. In the middle of a consumer who bought the package is 2 books dealing with Linux: Administration moto.motors-blog.co.uk Free Phone Cards ostsee Guide "and" User Guide ", a package of CDs and the 2 disc DVD bilateral (DVD1 and DVD2 installation source), plus a package of regular CD needed for installation - total 7 discs. In addition, SUSE AG, the plate with a full version of the database SQL Anywhere ® Studio for Linux v9.0 and SUSE extra sticker with the logo - with the chameleon. That was a first impression.


FireBoard
Welcome, Guest
Please Login or Register.    Lost Password?
linux information Bug#506345: linux-image-2.6-486: Facility to allow falsified information in /proc/cpuinfo (1 viewing) (1) Guests
Go to bottom Post Reply Favoured: 0
TOPIC: linux information Bug#506345: linux-image-2.6-486: Facility to allow falsified information in /proc/cpuinfo
#2164
Mark Hobley (Visitor)
Click here to see the profile of this user
Birthdate:
linux information Bug#506345: linux-image-2.6-486: Facility to allow falsified information in /proc/cpuinfo  
Package: linux-image-2.6-486 Version: 2.6.26+16 Severity: wishlist It would be useul to have the facility to provide a generic entry in /proc/cpuinfo rather than revealing processor specific information. This could possibly be done via a boot option, such as cpuinfo=486 or cpuinfo=pentium This would enable the computer to act as a generic _base_ level computer for a specific architecture, providing backward compatibility with lower level machines. This would enable a machine to appear as a generic 486 machine or as a generic Pentium machine, without revealing the machine is actually a higher level machine 686 machine (or using an IBM compatible processor, supplied by an alternative manufacturer such as a Cyrix 686, or an AMD K6 or AMD K7.) One of the problems that I am encountering is that build and runtime systems appear to be taking information from /proc/cpuinfo, and this is influencing compiler or program behaviour. All of my machines are using 486 (IA-32) compatible processors. However, not all machines are true 486 machines. I have 586, 686 and K7 series processors on some machines, and the processors are made by various manufacturers (such as Intel, Cyrix and AMD.) I require all machines to behave with lowest common denominator behaviour, and for all compiled binaries to be generic enough to move across machines. I am finding that distribution provided binaries, and third party provided build _script_s are detecting that the machine doing the build is a 686, and is utilizing features for that architecture, even though the target architecture is generic 486. I know that a workaround for this would be to modify all of the build _script_s in every single package, and find a way of rebuilding the entire Debian distribution from source, but I feel that a falsified /proc/cpuinfo would be much less of a headache. I propose that the boot time switch cpuinfo=pentium provides the following falsified information in /proc/cpuinfo: vendor_id       : GenuineIntel cpu family      : 5 model           : 2 model name      : Pentium 75 - 200 Maybe the vendor_id, model and model name could be simply be set to Unknown or Generic if the boot switch is used. I am not sure what effect this would have, but hopefully it would mean generic behaviour.
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop