Older blog entries for harald (starting at number 5)

Moved my blog (diary) to my homepage.

Discovered ignalum (mentioned in an article), which is basically an extended RH or Fedora. Suggested on their sourceforge feature tracker to work more upstream, as they seem to modify one of my config tool, without ever mailing with me (system-config-network). Checked their CVS for useful modifications. Found none.

Updated my sourceforge account information (saturn_de).

Returned from Global Company Meeting and a following week vacation in the US. New Orleans seems to have a party problem :)

Fixed my patch for kdelibs, to support the freedesktop systemtray protocol (client side).

Discovered the coverage.py module and put it in my small unittest testsuite for rhpl.conf.

The interesting code looks like this:

def suite():
    suite = unittest.TestSuite()
    suite = unittest.makeSuite(TestConf,'test')
    return suite
 if __name__ == "__main__":
    import coverage
    coverage.erase()
    coverage.start()
    from rhpl import Conf
    testRunner = unittest.TextTestRunner(verbosity=2)
    result = testRunner.run(suite())
    coverage.stop()
    coverage.the_coverage.report(Conf, show_missing=0 )
    sys.exit(not result.wasSuccessful())

which outputs s.th. like this:

Ran 4 tests in 0.685s
OK
Name        Stmts   Exec  Cover
-------------------------------
rhpl.Conf    1287    387    30%

Pushed out udev-024-3 to Fedora Core Development:

• added central config file for udev /etc/sysconfig/udev which contains

  # set USE_UDEV to yes, if you want to use udev
  #
  USE_UDEV="yes"
  # if selinux file attributes
  # should be restored (leave to yes, if unsure)
  UDEV_SELINUX="yes"
  # if console permissions (pam_console)
  # should be restored (leave to yes, if unsure)
  UDEV_CONSOLE="yes"
  # if dbus messages should be sent
  UDEV_DBUS="no"
  # if actions should be logged
  UDEV_LOG="no"
  

  for that, I had to make /etc/hotplug.d/default/udev.hotplug a shell script, which tests for USE_UDEV and then exec's udevsend
• added dbus, selinux and pam_console support through these scripts:

      /etc/dev.d/default/dbus.dev
      /etc/dev.d/default/pam_console.dev
      /etc/dev.d/default/selinux.dev
  

  • dbus.dev calls /usr/sbin/udev_dbus which has Kay's latest dbus patch.
  • pam_console.dev calls pam_console_setowner, which is basically a modified pam_console_apply, which only modifies one file. (no glob on /dev, thus no readdir on /dev every time)
  • selinux.dev just calls

        # restorecon $DEVNAME
    

    which makes udev_selinux somehow obsolete. There have be selinux policies written yet to let udev execute scripts from /etc/dev.d.
• set up the config file to use directories for permissions and rules and wrote some basic rules and permissions as used by us

      /etc/udev/permissions.d/
      /etc/udev/permissions.d/00-udev.permissions
      /etc/udev/rules.d/
      /etc/udev/rules.d/00-udev.rules
  

  The directories can be used as a drop in for vendors and customers.