/proc and is state of deprecation ..

dividingbyzero · 01-26-2009, 11:59 PM

Hi.

I'm wondering. When I build a kernel with 'make menuconfg' I usually comes across the part to include the "deprecated" /proc filesystem that "has been replaced with /sys" in the menu. I ask the question if I should still use /proc, because I use it to check the state of my battery's charge with 'cat /proc/acpi/battery/BAT1/state '. Is there a way with the /sys filesystem to check my battery's charge state, etc., and should I NOT use /proc anymore?

Thanks

aus9 · 01-27-2009, 12:58 AM

hi

I have seen that as well. I use diff cats of proc

eg cat /proc/interrupts
cat /proc/asound/card0/codec#0

so the answer is as I do not have a laptop...do a search of sys and see if you can get the same info
or...install lm-sensors and a frontend like gkrellm and use sensors instead.

if your kernel is desperate for ram...because its a laptop...cull proc...but then compare how much juice you are using to run gkrellm?

dividingbyzero · 01-27-2009, 01:05 AM

thanks. Not short on RAM; I have 3 gigs on my IBM lenovo 3000 G530 (Awesome laptop, for cheap

), but yeah, I'm gonna read up on /sys.

Thanks again

maginotjr · 01-27-2009, 04:25 AM

well, there is already a thread to discuss that, https://www.linuxquestions.org/quest...in-2.6-317088/

[ ]'s

allend · 01-27-2009, 07:18 AM

Quote:

Is there a way with the /sys filesystem to check my battery's charge state, etc.

On my laptop, 'cat /sys/class/power_supply/BAT1/*' provides similar information to that provided by 'cat /proc/acpi/battery/BAT1/state'.
I believe that there is a move to standardise the interface between devices and user space using /sys so that it is hardware and distribution agnostic. For an example of this, look at pm-utils, introduced into Slackware 12.2.
From /usr/doc/pm-utils-1.2.3/README:

Quote:

Why do we need it?

* All the main distributions are re-implementing the same
functionality to support common power management
operations. pm-utils provides a standardized distribution agnostic
layout and interface for common power management tasks, which frees
software and hardware vendors from having to maintain
distribution-specific suspend/resume functionality.