Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I would appreciate if some one can explain me why the two files do not exist?
How Android kernel’s virtual memory space and physical space be like without have the 2 files?
Edit:
I am having Android 2.3.7 (Cyanogen mod), the 2 files do not exist:
Edit2:
I have checked the Samsung Galaxy S3 running ICS, the 2 files exist
The
/dev/mem(c:1:1) and/dev/kmem(c:1:2) device nodes are merely an API thatdrivers/char/mem.cin the Linux kernel exposes to user-space. The kernel itself manages memory directly without use of these device nodes, and in general user-space does not need them either./devis simply a directory which (by tradition) contains device nodes, which are special “files”; there is no strict relation between what is available in/devand what the kernel provides. (There are tools likeudevormdevwhich create and destroy device nodes in/devin response to kernel events, but these are not always used in the embedded world where hardware is relatively fixed and known.) If you wish, you may try creating these nodes to interact with usingmknod(and this can live anywhere, not ncessarily in/dev). However, it is possible that the kernel has been configured withCONFIG_DEVKMEM=n, in which case these devices will not work anyways.