[Mageia-dev] cauldron core/release udev-173-1.mga2

Colin Guthrie mageia at colin.guthr.ie
Fri Aug 26 00:47:42 CEST 2011

'Twas brillig, and Michael Scherer at 25/08/11 20:29 did gyre and gimble:
> Le jeudi 25 août 2011 à 15:33 +0100, Colin Guthrie a écrit :
>> 'Twas brillig, and D.Morgan at 25/08/11 15:22 did gyre and gimble:
>>> On Thu, Aug 25, 2011 at 4:18 PM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
>>>> 'Twas brillig, and Mageia Team at 25/08/11 09:56 did gyre and gimble:
>>>>> Name        : udev                         Relocations: (not relocatable)
>>>>> Version     : 173                               Vendor: Mageia.Org
>>>>> Release     : 1.mga2                        Build Date: Thu Aug 25 10:54:41 2011
>>>>> Install Date: (not installed)               Build Host: jonund
>>>>> Group       : System/Configuration/Hardware   Source RPM: (none)
>>>>> Size        : 745928                           License: GPLv2
>>>>> Signature   : (none)
>>>>> Packager    : Mageia Team <http://www.mageia.org>
>>>>> URL         : ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug
>>>>> Summary     : A userspace implementation of devfs
>>>>> Description :
>>>>> Udev is an implementation of devfs/devfsd in userspace using sysfs and
>>>>> /sbin/hotplug. It requires a 2.6 kernel to run properly.
>>>>> Like devfs, udev dynamically creates and removes device nodes from /dev/.
>>>>> It responds to /sbin/hotplug device events.
>>>>> misc <misc> 173-1.mga2:
>>>>> + Revision: 135235
>>>>> - fix description ( rpmlint error )
>>>>>   + tv <tv>
>>>>>     - fix file list
>>>>>     - new release
>>>>>     - rediff patch 0
>>>> So, with the new udev, it seems that udev-acl is removed. This is a step
>>>> towards systemd which now handles all the ACL application.
>>>> Do we really want this new udev now? If so, then we really need to step
>>>> up the systemd integration. Things are mostly working fine for me
>>>> without udev-acls, but even with the systemd package as presently
>>>> available, I have to edit my /etc/pamd.d/system-auth file to include the
>>>> pam_systemd stuff - see my earlier message to this list about that.
>>> what about doing like fedora ?
>>> %post
>>> # Make sure pam_systemd is enabled
>>> if ! /bin/grep -q pam_systemd /etc/pam.d/system-auth-ac ; then
>>>         /usr/sbin/authconfig --update --nostart >/dev/null 2>&1 || :
>>>         # Try harder
>>>         /bin/grep -q pam_systemd /etc/pam.d/system-auth-ac ||
>>> /usr/sbin/authconfig --updateall --nostart >/dev/null 2>&1 || :
>>> fi
> I think it may be easier to write a script around augeas than import
> authconfig, as I suspect that it would do much more change.

I'm not familiar with augeas... but this should be possible. Do the
tools we already have for e.g. configuring LDAP logins have routines for
editing the system-auth file perhaps?

>> Yup that's what I asked in my last email about this several weeks ago.
>> I've pinged it up to get more discussion about the topic.
> In fact, it was not clear that you asked a question in the mail :/

Hmm, I thought: "The question is, how should we handle this?" was a
pretty obvious question... I even used the word "question" :p :D

> We said that we would support booting without systemd-, so to me, this
> should be taken in account.

Yeah but I think using the "optional" word in pam config means that it's
quite safe even if systemd is not running, so I don't think this is an

That's why I suggested even just patching pam directly... but modifying
the file should also be possible as that what ldap auth configuration
does anyway, so it's no great shakes.


Colin Guthrie

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

More information about the Mageia-dev mailing list