[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#251170: Package: installation-reports



You sent a very usefull installation report, thank you.

On 27.V.2004 Pete Shinners wrote:
> 
> First, I spent a few times going into the partion tool. Each time 
> starting I got a long pause on the "partition scan". Checking with the 
> other terminals I noticed it was scanning partitions on 
> /dev/cdroms/cdrom0. This part of the scan took a long time. I would 
> recommend not scanning anything under /dev/cdroms when looking for drive 
> partitions.

Can you remember the title of the progress bar.  Was it "Scanning
disks..." or "Detecting file systems..."? How you decided that the
partitioner scanned /dev/cdroms/cdrom0? There is a (not so long) pause
on "Detecting file systems..." and it is unavoidable but I hope that
the partitioner doesn't try to detect CDROM devices.  Did you see the
CDROM as a device in the main partitioning dialog?

> The little symbols on the partition screen are a bit confusing. Read the 
> help for them, but still never learned what the lightning bolt was for 
> (boot?). A legend of the symbols and their meanings directly on the 
> partition page would be helpful.

I think that there is already a description of the lightning bolt in the
help.  A legend directly on the partition page seams impossible as it 
has to stay on top of the screen (due to limitation of the debconf
interface that d-i uses) and as a result the partition table will be
invisible.

> I have two existing EXT3 partitions that I wanted to mount under /home 
> and /xandros. (you can see from my current partion mount list they are 
> working.) But I could not get them mounted with the partioner tool. Each 
> one gave me the following error, "This ext2 filesystem has a rather 
> strange layout! Parted can't resize this (yet)."

This will be fixed.

> My last note here is just an observation. Since I was working with 
> existing partitions a bit, I was wondering If there was any difference 
> between the top level "Do not use this partition" option, or just 
> setting the mount point to "no mount point". I ended up going with the 
> "The do not use...", but was wondering if there was a difference.

You reported a usability problem of the installer.  Another problem is
that when the method is "do not use" the user is not allowed to set a
mount point and it is not obvious that the method should be changed in
order to set mount point.

> Oh, and one last thing. When booting now I get an ugly message about 
> problems with the partition tables not matching. This happens early in 
> the boot and scrolls away faster than I can really read. The error 
> doesn't show up in dmesg either. I haven't been getting this before, 
> don't know if it's a problem I had previosly and only 2.6.x kernels 
> detect. Or if the debian installer did something funny with the partitions?

I don't know about this.

Anton Zinoviev





Reply to: