Your message dated Wed, 08 Sep 2010 03:58:04 +0000 with message-id <E1OtBnQ-0004qX-1h@ravel.debian.org> and subject line Closing old installation report #327047 has caused the Debian Bug report #327047, regarding Successful installation of Sarge on a SparcStation5 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.) -- 327047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327047 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Successful installation of Sarge on a SparcStation5
- From: Christian Aichinger <Greek0@gmx.net>
- Date: Wed, 7 Sep 2005 11:35:06 +0200
- Message-id: <20050907093506.GD22403@orest.greek0.net>
- Mail-followup-to: Christian Aichinger <Greek0@gmx.net>, submit@bugs.debian.org
Package: installation-reports INSTALL REPORT Debian-installer-version: 2005-09-06, Sparc32 netboot image from http://http.us.debian.org/debian/dists/stable/main/installer-sparc/current/images/sparc32/netboot/boot.img uname -a: Linux antigone 2.6.8-2-sparc32 #1 Wed Mar 23 02:20:49 EST 2005 sparc GNU/Linux Date: 2005-09-06 Method: Used a serial console and told the OpenBoot PROM to netboot ('boot net' on the console). Setup a boot server on my laptop using rarpd/bootp/tftpd. Used the boot.img file from the above address as boot image. Then I basically did a normal netinstall, no proxies or simmilar involved. Packages source: ftp://ftp.es.debian.org (sarge) Machine: Sun SparcStation 5, 110MHz Processor: Fujitsu MB86904, 110MHz Memory: 64Mb Root Device: SCSI (0:0:3:0), ST32171W SUN2.1G Root Size/partition table: Disk /dev/sda (Sun disk label): 66 heads, 62 sectors, 1015 cylinders Units = cylinders of 4092 * 512 bytes Device Flag Start End Blocks Id System /dev/sda1 0 48 98208 83 Linux native /dev/sda2 48 947 1839354 83 Linux native /dev/sda3 0 1015 2076690 5 Whole disk /dev/sda4 947 1015 139128 82 Linux swap /dev/sda1 on /boot type ext2 (rw) /dev/sda2 on / type ext2 (rw,errors=remount-ro) Output of lspci and lspci -n: No output with both commands Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked: [O] Configure network HW: [O] Config network: [O] Detect CD: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [E] Create file systems: [E] Mount partitions: [E] Install base system: [O] Install boot loader: [O] Reboot: [O] Comments/Problems: Everything worked pretty well actually, just partitioning/creating file systems was a bit problematic. I chose automatic partitioning of my HDD with a sun partition table (one large partition for everything). That didn't work, failing with "Can't partition this way, probably too many primary partitions" (or something like that). So I tried other partition table formats: msdos (which gave the same error with auto partitioning) and bsd (which worked, but the partitions weren't recognized by the kernel/devfs, so I couldn't mount them). Finally I chose sun partition table format again and partitioned manually, which finally worked. Creating ext3 on the / partition failed again though, with an opaque "Couldn't create ext3 filesystem on /" error. So I chose ext2 for /boot and /, which worked. Everything else worked just fine. Cheers, Christian AichingerAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 327047-done@bugs.debian.org
- Subject: Closing old installation report #327047
- From: Christian Perrier <bubulle@debian.org>
- Date: Wed, 08 Sep 2010 03:58:04 +0000
- Message-id: <E1OtBnQ-0004qX-1h@ravel.debian.org>
We are closing this installation report for one of the following reasons: - it was reported with a pre-lenny version of Debian Installer. - indications in the installation report give the feeling that the reported problem waslying in another software, unrelated to D-I, which we can't easily identify. - indications in the installation report suggest that it may have been fixed in a more recent version of a D-I component - it was successful and we forgot closing it..:-) - it has no information we consider useful The D-I team is currently in the process of cleaning out the old spool of installation reports that haven't bene processed yet. In case you think that the problem you reported has chances to be still present, please reiterate your installation test with a more recent image of D-I, if you're in position of doing this. You'll find daily builds at http://www.debian.org/devel/debian-installer. We recommend you choose the netboot image, in the "daily builds section", then choose to install "squeeze" when prompted. If some problems are found, please report them with a new bug sent against installation-reports. Many thanks for your understanding and your help improving Debian, past and present.
--- End Message ---