Bug#271740: marked as done ((no subject))
Your message dated Wed, 08 Sep 2010 03:57:39 +0000
with message-id <E1OtBn1email@example.com>
and subject line Closing old installation report #271740
has caused the Debian Bug report #271740,
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 firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
Debian-installer-version: RC1, sarge-i386-netinst.iso
uname -a: Linux apex 2.6.7-1-686 #1 Thu Jul 8 05:36:53 EDT 2004 i686 GNU/Linux
Date: 06-Sep-2004 02:06 AM EDT
Method: Booted netinstall from CD-ROM, installed base system from CD-ROM,
installed testing distro from debian.mirrors.pair.com.
Machine: HP Pavilion zt1135
Processor: Intel Celeron 1.2 GHz
Memory: 256 MB
Root Device: IDE hard disk, /dev/hda2
Root Size/partition table:
Device Boot Start End Blocks Id System
/dev/hda1 1 62 497983+ 82 Linux swap
/dev/hda2 * 63 4864 38572065 83 Linux (/)
Output of lspci and lspci -n:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8605 [ProSavage PM133]
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8605 [PM133 AGP]
0000:00:04.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller
0000:00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:10.0 Communication controller: ESS Technology ES2838/2839 SuperLink Modem (rev 01)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8231 [PCI-to-ISA Bridge] (rev 10)
0000:00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1e)
0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1e)
0000:00:11.4 Bridge: VIA Technologies, Inc. VT8235 ACPI (rev 10)
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 40)
0000:01:00.0 VGA compatible controller: S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02)
0000:00:00.0 0600: 1106:0605
0000:00:01.0 0604: 1106:8605
0000:00:04.0 0607: 1524:1410
0000:00:0d.0 0200: 10ec:8139 (rev 10)
0000:00:10.0 0780: 125d:2838 (rev 01)
0000:00:11.0 0601: 1106:8231 (rev 10)
0000:00:11.1 0101: 1106:0571 (rev 06)
0000:00:11.2 0c03: 1106:3038 (rev 1e)
0000:00:11.3 0c03: 1106:3038 (rev 1e)
0000:00:11.4 0680: 1106:8235 (rev 10)
0000:00:11.5 0401: 1106:3058 (rev 40)
0000:01:00.0 0300: 5333:8d01 (rev 02)
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: [E]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [E]
Install base system: [O]
Install boot loader: [O]
I selected 802.11b card for installation. Excellent job with wireless
configuration prompts, by the way. However, the installer initially
detected my neighbor's access point, but the first indication of this
was that DHCP failed. Then it gave me a chance to specify an ESSID, with
the incorrect name filled in. Ok, so I put in the correct name and all
If it is possible, I think it would be nice to get a list of all
detected APs and let the user select one. If that's not possible, at
least say "I detected a wireless access point with ESSID <essid>. Is
this the correct AP? (Yes/No)" If no, give the user the manual ESSID
When setting up the hard disk, we wanted to re-use an existing ext3
filesystem. We had moved the data from the Gentoo install that was on
that filesystem into a directory named "save", and deleted all other
root-level contents. (Yeah, we also made a backup on another machine.)
However, we totally missed the option to use an existing partition and
filesystem, because it is buried several levels down.
I was looking for a choice like "install on an existing partition".
Instead, I had to go into the manual partitioner (even though I wasn't
changing the partition table at all) and change some settings for the
existing linux partition. I believe I had to change the filesystem type
from "do not use" to "ext3" and tell it not to make a new filesystem.
I think part of the confusion comes from the fact that the partitioning
step and the mkfs step are combined in a single screen. I like this in
general, as it doesn't force you to think about the difference between a
partition and the filesystem on a partition. But there are a couple of
First, this screen shouldn't be called "Partition Disks", since it
combines partitioning, formatting, and setting mount points and mount
options. Maybe "Configure Disks" would be more appropriate.
Second, when first selecting the existing linux partition, I was given a
"Use As" menu. In addition to "do not use" and a list of filesystems,
I'd like to see an option "Use existing filesystem (ext3)". I shouldn't
have to know or care what filesystem I'm already using -- just that I
want to keep using it!
I think fixing the nomenclature would go a long way towards making the
partitioner easy to use. While refering to the entire process of
partitioning, formatting, and setting mount points/options as
"partitioning" may work for newbies, experienced linux users know that
partitioning is just a part of the process. I propose "Configure Disks".
Also, I'd like to see a summary of what's going to be done before any of
it happens. Then I'd be sure that it wasn't going to sneakily rewrite my
partition table or reformat my drive.
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
- it was reported with a pre-lenny version of Debian
- 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
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---