[clue-tech] SYSFS_DEPRECIATED_V2

[mike havlicek]

Hello,

In the kernel v2.6.28.6 configuration (I am using make gconfig) the SYSFS_DEPRECIATED_V2 option has this description:

--------------------------------------------------------------------------
Create deprecated sysfs files SYSFS_DEPRECATED_V2

This option creates deprecated symlinks such as the
"device"-link, the <subsystem>:<name>-link, and the
"bus"-link. It may also add deprecated key in the
uevent environment.
None of these features or values should be used today, as
they export driver core implementation details to userspace
or export properties which can't be kept stable across kernel
releases.

If enabled, this option will also move any device structures
that belong to a class, back into the /sys/class hierarchy, in
order to support older versions of udev and some userspace
programs.

If you are using a distro with the most recent userspace
packages, it should be safe to say N here.
--------------------------------------------------------------------------

-Mike


--- On Thu, 2/19/09, dennisjperkins at comcast.net <dennisjperkins at comcast.net> wrote:

> From: dennisjperkins at comcast.net <dennisjperkins at comcast.net>
> Subject: Re: [clue-tech] SYSFS_DEPRECIATED_V2
> To: mhavlicek1 at yahoo.com, "CLUE technical discussion" <clue-tech at cluedenver.org>
> Date: Thursday, February 19, 2009, 10:26 AM
> If you are using HAL and D-Bus, you want sysfs enabled. I
> would be very surprised if CentOS does not use them. 
> 
> I don't know why you mention a SYSFS_DEPRECATED_V2 in
> the header. Is there a newer version in the kernel? 
> 
> ----- Original Message ----- 
> From: "mike havlicek"
> <mhavlicek1 at yahoo.com> 
> To: clue-tech at cluedenver.org 
> Sent: Thursday, February 19, 2009 9:27:00 AM GMT -07:00
> US/Canada Mountain 
> Subject: [clue-tech] SYSFS_DEPRECIATED_V2 
> 
> Hello, 
> 
> I am building a v2.6.28.6 kernel for use with CentOS 5.2.
> In general whats a definitative way to determine if a distro
> needs this feature? 
> 
> I have done a "find /sys/class | xargs ls -l | grep
> l" and get entries like 
> 
> lrwxrwxrwx 1 root root 0 Feb 19 08:10 \ 
> device -> ../../../devices/pci0000:00/0000:00:0f.2 
> 
> which leads me to believe the stock running kernel
> (2.6.18-92el5PAE) on 
> this machine has "some" SYSFS enabled. The
> question is whether it is necessary. 
> 
> Ultimately I am trying to alleviate some more irritating
> problems that I see from this vanilla install: 
> 
> - calls to hwclock fail 
> - kjournald eventually fails 
> 
> I also get messages of the form: 
> 
> EXT3-fs error (device dm-3) in start_transaction: Journal
> has aborted 
> 
> and from syslogd 
> 
> kernel: journal commit I/O error. 
> 
> Other than /boot being on /dev/sda2 (ext3), the rest of the
> system is installed on a single lvm2 volgroup with 5 logical
> volumes: all with ext3 
> except a swap. 
> 
> When these things happen, I think methods of logging are
> confined to 
> stylo & papier ... and I haven't had that subsystem
> fully functioning. 
> 
> Thanks, 
> 
> -Mike 
> 
> 
> 
> 
> 
> _______________________________________________ 
> clue-tech mailing list 
> clue-tech at cluedenver.org 
> http://www.cluedenver.org/mailman/listinfo/clue-tech