Re: Bug#263079: udev: missing mknod on ppp

[Luke Kenneth Casson Leighton <lkcl@lkcl.net>]

On Tue, Aug 03, 2004 at 07:52:25AM +0600, Alexander E. Patrakov wrote:
> Marco d'Itri wrote:
> 
> > On Aug 03, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> >
> >> thank you for pointing me at the README.Debian because it makes
> >> clear that for SE/Linux there are certain /dev entries that may not
> >> get fired up by udev, and consequently won't have se/linux
> >> permissions set!
> >
> > On debian, *all* devices are supposed to be created by udev if udev
> > is installed (because /dev is a tmpfs). I don't know why /dev/ppp is
> > not being created on your system.
> >
> Bedause the ppp-generic module is not autoloaded (put it into 
> /etc/modules or see below).
> 
> The same problem exists for all "non-hardware" modules. It can be solved 
> by explicitly loading all these non-hardware modules at system startup. 
> The following bootscriptlet loads all modules that potentially create 
> devices and don't need hardware (i.e. exactly those drivers that are 
> autoloaded on demand due to "char-major" aliases without udev):
> 
>    KVERSION=`uname -r`
>    for module in `egrep '^alias (char|block)-major' \
>        /lib/modules/$KVERSION/modules.alias /etc/modprobe.conf | \
>        grep -v 1394 | awk '{print $3;}'`
>    do
>        modprobe $module
>    done
> 

 okay.

 in addition to calling modprobe, it is necessary to set selinux
 permissions.

 now, modprobe  has a pretty name, but the command to call up the module
 contains no information about what node is going to be created in /dev.

 therefore, we have a problem.

 without the name of the inode, the only way to set the selinux file
 permissions is to either guess or to just... endeavour to set the
 whole lot with this:
 
	 setfiles /etc/selinux/.../file_contexts/file_contexts /dev

 this is totally yuk, but is a last resort measure.

 anyone got any better ideas?

 does anyone know whether doing the modprobe above will result in a
 hotplug event from the "non-hardware" devices, such that udev will
 be triggered, and a restorecon or createcon performed correctly?

 marco kindly mentioned to me that some devices haven't been hooked into
 the pci-hotplug stuff yet.

 l.



-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel