What are the kernel option required for udev in 2.6.28 kernel.

What are the kernel option required for udev in 2.6.28 kernel.

[unni krishnan]

Hi All,

  I just want to know the exact options that we need to enable in the
kernel configuration for the latest udev. Some options specified in
http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html is
not available ( or changed position ) in the 2.6.28 kernel.

I know that copying the existing config file from linux distro will do
it. But want to know about the exact kenel modules/support needed for
udev to get everything working. Please help.

---------------------
With regards,
Unni

"A candle loses nothing by lighting another candle"

Re: What are the kernel option required for udev in 2.6.28 kernel.

[Greg KH]

On Thu, Jun 11, 2009 at 05:18:48PM +0530, unni krishnan wrote:
> Hi All,
> 
>   I just want to know the exact options that we need to enable in the
> kernel configuration for the latest udev. Some options specified in
> http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html is
> not available ( or changed position ) in the 2.6.28 kernel.
> 
> I know that copying the existing config file from linux distro will do
> it. But want to know about the exact kenel modules/support needed for
> udev to get everything working. Please help.

What have you tried that did not work properly for you?

thanks,

greg k-h

Re: What are the kernel option required for udev in 2.6.28 kernel.

[Greg KH]

On Thu, Jun 11, 2009 at 09:01:15PM +0530, unni krishnan wrote:
> Hi Greg,
> 
>   I am able to compile the custom kernel using the existing conf that
> I got from /proc/config.gz in My Arch linux. Also the Udev is working
> fine. I just want to make sure that the config options :
> 
> -----------------------------------------------
> CONFIG_HOTPLUG=y
> #
> # File systems
> #
> # Pseudo filesystems
> #
> CONFIG_PROC_FS=y
> CONFIG_PROC_KCORE=y
> CONFIG_SYSFS=y
> CONFIG_TMPFS=y
> CONFIG_RAMFS=y
> #
> -----------------------------------------------
> 
> are applicable for the latest kernel also. Is here any change ?

With these options, no.

But make sure that CONFIG_SYSFS_DEPRECATED_V2 is not set, that is the
most important one these days.

hope this helps,

greg k-h

Re: What are the kernel option required for udev in 2.6.28 kernel.

[unni krishnan]

Hi Greg,

  I am able to compile the custom kernel using the existing conf that
I got from /proc/config.gz in My Arch linux. Also the Udev is working
fine. I just want to make sure that the config options :

-----------------------------------------------
CONFIG_HOTPLUG=y
#
# File systems
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
#
-----------------------------------------------

are applicable for the latest kernel also. Is here any change ?

I have not tried disabling each and every option because that will
take time to compile the kernel each time. If there anyone knows the
changes ( if any ) I can save lots of time needed to compile the
kernel, if not, I need to go for the second way :-)

Thanks for your help.

On Thu, Jun 11, 2009 at 8:42 PM, Greg KH<greg@kroah.com> wrote:
> On Thu, Jun 11, 2009 at 05:18:48PM +0530, unni krishnan wrote:
>> Hi All,
>>
>>   I just want to know the exact options that we need to enable in the
>> kernel configuration for the latest udev. Some options specified in
>> http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html is
>> not available ( or changed position ) in the 2.6.28 kernel.
>>
>> I know that copying the existing config file from linux distro will do
>> it. But want to know about the exact kenel modules/support needed for
>> udev to get everything working. Please help.
>
> What have you tried that did not work properly for you?
>
> thanks,
>
> greg k-h
>



-- 
---------------------
With regards,
Unni

"A candle loses nothing by lighting another candle"

Re: What are the kernel option required for udev in 2.6.28 kernel.

[Kay Sievers]

On Thu, Jun 11, 2009 at 17:31, unni krishnan<unnikrishnan.a@gmail.com> wrote:
>  I am able to compile the custom kernel using the existing conf that
> I got from /proc/config.gz in My Arch linux. Also the Udev is working
> fine. I just want to make sure that the config options :
>
> -----------------------------------------------
> CONFIG_HOTPLUG=y
> #
> # File systems
> #
> # Pseudo filesystems
> #
> CONFIG_PROC_FS=y
> CONFIG_PROC_KCORE=y
> CONFIG_SYSFS=y
> CONFIG_TMPFS=y
> CONFIG_RAMFS=y
>
> are applicable for the latest kernel also. Is here any change ?

You need:
  CONFIG_HOTPLUG=y
  CONFIG_UEVENT_HELPER_PATH=""
  CONFIG_NET=y
  CONFIG_UNIX=y
  CONFIG_PROC_FS=y
  CONFIG_SYSFS=y
  CONFIG_TMPFS=y
  CONFIG_TMPFS_POSIX_ACL=y

New versions will also depend on:
  CONFIG_INOTIFY=y
  CONFIG_SIGNALFD=y

CONFIG_UNIX=m *might* work, but it may also go wrong in "interesting" ways.

Kay

Re: What are the kernel option required for udev in 2.6.28 kernel.

[Kay Sievers]

On Thu, Jun 11, 2009 at 18:00, unni krishnan<unnikrishnan.a@gmail.com> wrote:
>  So these are the modules needed :
>
> ------------------------------------------
> CONFIG_HOTPLUG=y
>  CONFIG_UEVENT_HELPER_PATH=""
>  CONFIG_NET=y
>  CONFIG_UNIX=y
>  CONFIG_PROC_FS=y
>  CONFIG_SYSFS=y
>  CONFIG_TMPFS=y
>  CONFIG_TMPFS_POSIX_ACL=y
> CONFIG_INOTIFY=y
>  CONFIG_SIGNALFD=y
> ------------------------------------------
>
>  To get the Udev working in latest linux kernel. Thanks Kay.

Yeah, SIGNALFD only in the next, the to be released version, and as
Greg mentioned, the SYSFS_DEPRECATED option must not be set to work
reliably. It's not only udev which will fail without that. That broken
SYSFS_DEPRECATED thing should just be removed from the kernel some
day.

I've added the list to the udev README file now:
  http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=README;hb=HEAD

Thanks,
Kay

Re: What are the kernel option required for udev in 2.6.28 kernel.

[unni krishnan]

Hi,

  So these are the modules needed :

------------------------------------------
CONFIG_HOTPLUG=y
 CONFIG_UEVENT_HELPER_PATH=""
 CONFIG_NET=y
 CONFIG_UNIX=y
 CONFIG_PROC_FS=y
 CONFIG_SYSFS=y
 CONFIG_TMPFS=y
 CONFIG_TMPFS_POSIX_ACL=y
CONFIG_INOTIFY=y
 CONFIG_SIGNALFD=y
------------------------------------------

  To get the Udev working in latest linux kernel. Thanks Kay.

On Thu, Jun 11, 2009 at 9:21 PM, Kay Sievers<kay.sievers@vrfy.org> wrote:
> On Thu, Jun 11, 2009 at 17:31, unni krishnan<unnikrishnan.a@gmail.com> wrote:
>>  I am able to compile the custom kernel using the existing conf that
>> I got from /proc/config.gz in My Arch linux. Also the Udev is working
>> fine. I just want to make sure that the config options :
>>
>> -----------------------------------------------
>> CONFIG_HOTPLUG=y
>> #
>> # File systems
>> #
>> # Pseudo filesystems
>> #
>> CONFIG_PROC_FS=y
>> CONFIG_PROC_KCORE=y
>> CONFIG_SYSFS=y
>> CONFIG_TMPFS=y
>> CONFIG_RAMFS=y
>>
>> are applicable for the latest kernel also. Is here any change ?
>
> You need:
>  CONFIG_HOTPLUG=y
>  CONFIG_UEVENT_HELPER_PATH=""
>  CONFIG_NET=y
>  CONFIG_UNIX=y
>  CONFIG_PROC_FS=y
>  CONFIG_SYSFS=y
>  CONFIG_TMPFS=y
>  CONFIG_TMPFS_POSIX_ACL=y
>
> New versions will also depend on:
>  CONFIG_INOTIFY=y
>  CONFIG_SIGNALFD=y
>
> CONFIG_UNIX=m *might* work, but it may also go wrong in "interesting" ways.
>
> Kay
>



-- 
---------------------
With regards,
Unni

"A candle loses nothing by lighting another candle"

Re: What are the kernel option required for udev in 2.6.28 kernel.

[unni krishnan]

Hello Kay,

 Thanks you very much for adding that to the readme file. I had
already checked the previous readme file to get the answer to this
question. But there was not much information. The new readme will help
the users like me :-) Thanks.

On Thu, Jun 11, 2009 at 9:38 PM, Kay Sievers<kay.sievers@vrfy.org> wrote:
> On Thu, Jun 11, 2009 at 18:00, unni krishnan<unnikrishnan.a@gmail.com> wrote:
>>  So these are the modules needed :
>>
>> ------------------------------------------
>> CONFIG_HOTPLUG=y
>>  CONFIG_UEVENT_HELPER_PATH=""
>>  CONFIG_NET=y
>>  CONFIG_UNIX=y
>>  CONFIG_PROC_FS=y
>>  CONFIG_SYSFS=y
>>  CONFIG_TMPFS=y
>>  CONFIG_TMPFS_POSIX_ACL=y
>> CONFIG_INOTIFY=y
>>  CONFIG_SIGNALFD=y
>> ------------------------------------------
>>
>>  To get the Udev working in latest linux kernel. Thanks Kay.
>
> Yeah, SIGNALFD only in the next, the to be released version, and as
> Greg mentioned, the SYSFS_DEPRECATED option must not be set to work
> reliably. It's not only udev which will fail without that. That broken
> SYSFS_DEPRECATED thing should just be removed from the kernel some
> day.
>
> I've added the list to the udev README file now:
>  http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=README;hb=HEAD
>
> Thanks,
> Kay
>



-- 
---------------------
With regards,
Unni

"A candle loses nothing by lighting another candle"

Re: What are the kernel option required for udev in 2.6.28 kernel.

[Olaf]

Kay Sievers wrote:
> You need:
>   CONFIG_HOTPLUG=y
>   CONFIG_UEVENT_HELPER_PATH=""
>   CONFIG_NET=y
>   CONFIG_UNIX=y
>   CONFIG_PROC_FS=y
>   CONFIG_SYSFS=y
>   CONFIG_TMPFS=y
>   CONFIG_TMPFS_POSIX_ACL=y
>
> New versions will also depend on:
>   CONFIG_INOTIFY=y
>   CONFIG_SIGNALFD=y
>
> CONFIG_UNIX=m *might* work, but it may also go wrong in "interesting" ways.
>   

Isn't CONFIG_TMPFS_POSIX_ACL optional?


thanks,

Olaf

Re: What are the kernel option required for udev in 2.6.28 kernel.

[Kay Sievers]

On Thu, Jun 11, 2009 at 19:37, Olaf<mailinglists@ban-solms.de> wrote:
> Kay Sievers wrote:
>>
>> You need:
>>  CONFIG_HOTPLUG=y
>>  CONFIG_UEVENT_HELPER_PATH=""
>>  CONFIG_NET=y
>>  CONFIG_UNIX=y
>>  CONFIG_PROC_FS=y
>>  CONFIG_SYSFS=y
>>  CONFIG_TMPFS=y
>>  CONFIG_TMPFS_POSIX_ACL=y
>>
>> New versions will also depend on:
>>  CONFIG_INOTIFY=y
>>  CONFIG_SIGNALFD=y
>>
>> CONFIG_UNIX=m *might* work, but it may also go wrong in "interesting"
>> ways.
>>
>
> Isn't CONFIG_TMPFS_POSIX_ACL optional?

Yes, it is, kind of. Udev itself does not really care. Things in
udev-extras do. Without PROCFS it might work too, I never tried, and
it's definitely nothing people should do.

Without ACLs you need to use groups for users, which you should never
do on any multi-user system, because people can use all devices
regardless of their actual session state. They can break your cdrom
burning task from ssh sessions, and all sorts of other things.
And and they could log into your box over ssh and can listen to your
microphone, which could be not exactly what you want in some
situations. :)

Kay