Your message dated Mon, 05 May 2008 10:23:24 +0200 with message-id <1209975804.523220.28663.nullmailer@xanadu.blop.info> and subject line initrd-tools has been removed from Debian, closing #312037 has caused the Debian Bug report #312037, regarding initrd-tools vmware bug + solution to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 312037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312037 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: initrd-tools vmware bug + solution
- From: Dirk Heuvels <dheuvels@web.de>
- Date: Sun, 05 Jun 2005 04:04:32 +0200
- Message-id: <A37661C2530717DA101083A4@p213.54.179.80.tisdip.tiscali.de>
Package: initrd-tools Version: 0.1.79+ mkinitrd fails on machines running kernel 2.4, when vmware is installed. Problem seems to be, that mkinitrd is looking for *.ko files in/lib/modules/{version} to decide whether to use modutils or module-init-tools.Because vmware installs vmhgfs.ko and vmxnet.ko, mkinitrd will never set $oldstyle to "yes" and thus fail using module-init-tools with 2.4 kernels. I attached a patch. Regards, DirkAttachment: mkinitrd-vmware.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
- To: 312037-done@bugs.debian.org
- Subject: initrd-tools has been removed from Debian, closing #312037
- From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
- Date: Mon, 05 May 2008 10:23:24 +0200
- Message-id: <1209975804.523220.28663.nullmailer@xanadu.blop.info>
Version: 0.1.84.2+rm The initrd-tools package has been removed from Debian testing, unstable and experimental, so I am now closing the bugs that were still opened against it. For more information about this package's removal, read http://bugs.debian.org/393092 . That bug might give the reasons why this package was removed, and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. Thank you for your contribution to Debian. -- Lucas
--- End Message ---