All of lore.kernel.org
 help / color / mirror / Atom feed
From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: 1250
Date: Thu, 19 May 2005 06:23:58 +0000	[thread overview]
Message-ID: <3EDBEA1A.8070908@paradyne.com> (raw)
In-Reply-To: <200306021011.37032.decibel8@charter.net>

devfs could be it. no other good ideas at the moment.

David wrote:
> ls -l /proc/sys/dev/sensors
> total 0
> -rw-r--r--    1 root     root            0 Jun  2 10:05 chips
> dr-xr-xr-x    2 root     root            0 Jun  2 09:49 via686a-isa-6000
> 
> ls -l /proc/sys/dev/sensors/via*
> total 0
> -r--r--r--    1 root     root            0 Jun  2 10:06 alarms
> -rw-r--r--    1 root     root            0 Jun  2 10:06 fan1
> -rw-r--r--    1 root     root            0 Jun  2 10:06 fan2
> -rw-r--r--    1 root     root            0 Jun  2 10:06 fan_div
> -rw-r--r--    1 root     root            0 Jun  2 10:06 in0
> -rw-r--r--    1 root     root            0 Jun  2 10:06 in1
> -rw-r--r--    1 root     root            0 Jun  2 10:06 in2
> -rw-r--r--    1 root     root            0 Jun  2 10:06 in3
> -rw-r--r--    1 root     root            0 Jun  2 10:06 in4
> -rw-r--r--    1 root     root            0 Jun  2 10:06 temp1
> -rw-r--r--    1 root     root            0 Jun  2 10:06 temp2
> -rw-r--r--    1 root     root            0 Jun  2 10:06 temp3
> 
> But even when I change the via686a-isa-6000 folder to have root write 
> permissions it doesn't work.
> 
> ls -l /proc/sys/dev/sensors
> total 0
> -rw-r--r--    1 root     root            0 Jun  2 10:07 chips
> drwxr-xr-x    2 root     root            0 Jun  2 09:49 via686a-isa-6000
> 
> So still get: 
> sensors -s
> via686a-isa-6000: Can't access /proc file for writing;
> Run as root?
> 
> I don't think the permission is staying either. Would devfs have something to 
> do with this?
> 

  parent reply	other threads:[~2005-05-19  6:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:23 1250 David
2005-05-19  6:23 ` 1250 Philip Pokorny
2005-05-19  6:23 ` 1250 Philip Pokorny
2005-05-19  6:23 ` 1250 Philip Pokorny
2005-05-19  6:23 ` Mark D. Studebaker  [this message]
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 DAVID
2005-05-19  6:24 ` 1250 Philip Pokorny
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare
2005-05-19  6:24 ` 1250 David
2005-05-19  6:24 ` 1250 Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EDBEA1A.8070908@paradyne.com \
    --to=mds@paradyne.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.