Bug#237455: Package: installation-reports
<x-tad-bigger>Package: installation-reports
Debian-installer-version: http://gluck.debian.org/cdimage/testing/daily/i386/current/
uname -a: Linux geometry 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686 GNU/Linux
Date: Tue Feb 24 08:11:13 EST 2004
Method: Network (broadband) / Aptitude
Machine: VA Linux Dual
Processor: Dual PIII (Katmai) 500 MHz
Memory: 512MB
Root Device: /dev/hda (IDE)
Root Size/partition table:
Name Flags Part Type FS Type Size (MB) Mount
-------------------------------------------------------------------
hda1 Primary Linux ext3 98.71 /boot
hda2 Boot Primary Linux ext3 13802.02 /
hda3 Primary Linux swap 551.10 /usr
hdb1 Primary Linux ext3 139.83 /tmp
hdb2 Primary Linux ext2 14311.99 /home
Output of lspci: herve@geometry2:~$ lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:11.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [E]
Create file systems: [O]
Mount partitions: [O]
Install base system: [E]
Install boot loader: [E]
Reboot: [E]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
1. When writing the partition table, I actually wanted to keep the contents of my /home partition, but the warning wasn't clear enough and I was afraid it would rewrite over (it says "Warning: this will erase any data on the partitions you have assigned a file system to"; this is incorrect, it would erase the data unless I chose the option 'keep and use data on this partition'). In fact, I trusted it and it did keep my partition while rewriting over / and /usr and /var, but the message could have been clearer.
2. The kernel did not want to install. In fact, it did, but when I looked at the /var/log/message, it complained that I was installing a kernel over itself (same version) and hence that the modules would be seriously messed up, and so better to stop.
3. Installing Lilo seemed to be pretty messed up: it complained it didn't want to install on an unclean install (all right) but then when I said do it anyway, because the unclean was actually just created a moment before, it started to reinstall everything (it seemed). It's actually hard to figure what it was doing... since it complained left and right, I started rebooting in the hope that things didn't go as bad as it said... and
4. The disk I got couldn't certify itself (MD5Sum was wrong).
5. Reboot did not eject the disk prior to reboot, and so as a result I rebooted into the Debian installer... I rebooted again after manually ejecting the disk, but I really shouldn't have to do that.
5. Because of all that, I restarted the whole process, actually changed my partition table and now everything worked OK. I could reboot.
AND NOW THE KILLER! I CAN ONLY INSTALL FROM PPP! THERE IS NO OPION TO INSTALL FROM A NETWORK!!! WHAT IS THIS???
6. So I reinstall from scratch again (5th time, by now). It never asks me for network settings but by now I know better. I ask to "Go Back" before partitioning the disk, and ask to detect network hardware. Then I redo everything (partitioning, install base system). Never a chance to install the secondary system inside the first system as is promiseed, or even configuring the primary system. Or maybe this was done automatically during the install. I trust the system and reboot.
This time, the system reboots and I *do* have an internet connection. Plus I have to say I have been using dselect for so long, aptitude is a nice change.
Independent suggestion: I am reinstalling Debian because my machine was compromised. I cannot trust any of the programs. However, reinstalling the base system with the rescue disk broke down my libc and I end up having to reinstall the whole system (not a bad thing anyway). It's actually a good thing the Debian installer refuses to install over an unclean installation. Nevertheless, there should be an option for rootkit (reinstalling the base packages and anything else that has been compromised, by examining the filesystem and checking if it corresponds to the apt database). This would be a welcome enhancement to the installation process.
</x-tad-bigger>
Thanks for the effort. Globally, I'm not unhappy to upgrade my machine, even though it was not what I planned...
--
Hervé
Reply to: