Bug#364039: Patch for /dev/i2o/hdX
Package: initrd-tools Version: 0.81.1 Followup-For: Bug #318120 tags 318120 patch Hello atached youll find a small patch which fixes the mkinitrd-detection of /dev/i2o/hdx on our testmachines, should work generally. Regards Ingo Steuwer -- * Besuchen Sie uns auf dem LinuxTag06 in Wiesbaden: Halle 9, Stand 929 * Ingo Steuwer [EMAIL PROTECTED] fon: +49 421 22 232- 0 EntwicklungLinux for Your Business Univention GmbHhttp://www.univention.de/ fax: +49 421 22 232-99 --- initrd-tools-0.1.81.1.orig/mkinitrd 2005-05-23 05:43:04.0 +0200 +++ initrd-tools-0.1.81.1/mkinitrd 2006-04-21 08:07:23.0 +0200 @@ -690,6 +690,9 @@ 98) echo ubd ;; + 80) + echo i2o_block + ;; *) type= case $(awk '
Bug#349011: Isn't as bad as it sounds
Hi the behaviour I described isn't that bad, the segfault depends on the position of the "moduleload"-statement in slapd.conf. It occures if slapd.conf has this structure: - moduleload back-bdb.so moduleload back-null.so - but doesn't occure if the moduleloads are one after another: - moduleload back-bdb.so moduleload back-null.so ----- Regards Ingo Steuwer -- Ingo Steuwer [EMAIL PROTECTED] fon: +49 421 22 232- 0 EntwicklungLinux for Your Business Univention GmbHhttp://www.univention.de/ fax: +49 421 22 232-99 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#349011: Segmentation Fault with moduleload
Package: slapd Version: 2.2.23-8 Include any modualized backend using "moduleload " in slapd.conf like moduleload back_null will cause a Segmentation fault of slapd during the next startup: # slapd -d 64 [..] line 71 (access to * by * read) line 75 (include "/etc/ldap/replica.conf") reading config file /etc/ldap/replica.conf line 77 (moduleload back_null) loaded module back_null module back_null: null module registered Segmentation fault Greetings Ingo Steuwer -- Ingo Steuwer [EMAIL PROTECTED] fon: +49 421 22 232- 0 EntwicklungLinux for Your Business Univention GmbHhttp://www.univention.de/ fax: +49 421 22 232-99 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#338292: nfs-kernel-server won't start if exports are qouted
Package: nfs-kernel-server Version: 1:1.0.6-3.1 Tags: patch To export directories containing spaces you need to qoute them (else exportfs uses the second part of the directory as options). If I export only shares which are qouted /etc/init.d/nfs-kernel-server says "Not starting nfs-kernel-server: No exports.". The init-script uses grep to determine if exports are definied and to decide if the server should be started. The regular expression doesn't care about qoutes. Attached you'll find a small patch fixing this. Greetings Ingo Steuwer -- Ingo Steuwer [EMAIL PROTECTED] fon: +49 421 22 232- 0 EntwicklungLinux for Your Business Univention GmbHhttp://www.univention.de/ fax: +49 421 22 232-99 --- nfs-utils-1.0.7.orig/debian/nfs-kernel-server.init Sat Dec 4 22:39:05 2004 +++ nfs-utils-1.0.7/debian/nfs-kernel-server.init Wed Nov 9 09:01:03 2005 @@ -55,7 +55,7 @@ case "$1" in start) cd / # daemons should have root dir as cwd - if grep -q '^/' /etc/exports + if egrep -q '^["]{0,1}/' /etc/exports then do_modprobe nfsd do_mount nfsd $PROCNFSD_MOUNTPOINT || NEED_SVCGSSD=no