Your message dated Sun, 25 Aug 2013 14:25:50 +0200 with message-id <201308251426.17126.hol...@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #690913, regarding (no subject) 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 ow...@bugs.debian.org immediately.) -- 690913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/kfreebsd-amd64/iso-cd/debian-wheezy-DI-b3-kfreebsd-amd64-netinst.iso Date: Fri Oct 19 11:02:24 JST 2012 Machine: QEMU 0.12.1.2 Processor: Xeon X5675 Memory: 2G Partitions: Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/ada0s1 ufs 38924012 484050 35326042 2% / devfs devfs 1 1 0 100% /dev linprocfs linprocfs 4 4 0 100% /proc /sys sysfs 4 4 0 100% /sys fdescfs fdescfs 1 1 0 100% /dev/fd tmpfs tmpfs 3682524 52 3682472 1% /run tmpfs tmpfs 5120 4 5116 1% /run/lock tmpfs tmpfs 408 4 404 1% /run/shm Output of lspci -nn and lspci -vnn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Flags: fast devsel, IRQ 255 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Flags: bus master, medium devsel, latency 0, IRQ 255 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] (prog-if 80 [Master]) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Flags: bus master, medium devsel, latency 0, IRQ 255 I/O ports at c000 00:01.2 USB controller [0c03]: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] [8086:7020] (rev 01) (prog-if 00 [UHCI]) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c020 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100] Flags: medium devsel, IRQ 9 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] Flags: fast devsel, IRQ 255 Memory at f0000000 (32-bit, prefetchable) Memory at f2000000 (32-bit, non-prefetchable) Expansion ROM at f2010000 [disabled] 00:03.0 Ethernet controller [0200]: Intel Corporation 82540EM Gigabit Ethernet Controller [8086:100e] (rev 03) Subsystem: Red Hat, Inc Device [1af4:1100] Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f2020000 (32-bit, non-prefetchable) I/O ports at c040 Expansion ROM at f2040000 [disabled] 00:04.0 RAM memory [0500]: Red Hat, Inc Virtio memory balloon [1af4:1002] Subsystem: Red Hat, Inc Device [1af4:0005] Flags: fast devsel, IRQ 11 I/O ports at c080 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Install base system: [O] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install: [E] Comments/Problems: When Partition disks, it get the forrowing warning: Could not get identify of device /dev/ada0 - Inappropriate ioctl for device<<attachment: kfreebsd.png>>
--- End Message ---
--- Begin Message ---Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they were caused by broken hardware and/or - they have been from a development phase where things were not stable and/or - they are quite old (and thus likely fixed today) and/or - moreinfo was asked and not given. If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
