Your message dated Wed, 13 Oct 2004 16:36:59 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing old installation-reports
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Mar 2004 16:53:51 +0000
>From [EMAIL PROTECTED] Thu Mar 11 08:53:51 2004
Return-path: <[EMAIL PROTECTED]>
Received: from duke.poly.edu [128.238.2.92] (root)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1B1TRO-0005cA-00; Thu, 11 Mar 2004 08:53:51 -0800
Received: from [128.238.34.253] (polytope.poly.edu [128.238.34.253])
        by duke.poly.edu (8.9.0/8.9.0) with ESMTP id LAA13648;
        Thu, 11 Mar 2004 11:53:43 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v612)
To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Content-Type: multipart/alternative; boundary=Apple-Mail-5--214864640
Cc: =?ISO-8859-1?Q?Herv=E9_Br=F6nnimann?= <[EMAIL PROTECTED]>
Subject: Package: installation-reports 
From: =?ISO-8859-1?Q?Herv=E9_Br=F6nnimann?= <[EMAIL PROTECTED]>
Date: Thu, 11 Mar 2004 11:54:26 -0500
X-Mailer: Apple Mail (2.612)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_08 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no 
        version=2.60-bugs.debian.org_2004_03_08
X-Spam-Level: 


--Apple-Mail-5--214864640
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
        charset=ISO-8859-1;
        format=flowed


Package: installation-reports

Debian-installer-version:=20
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=20
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:  [EMAIL PROTECTED]:~$ lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host=20
bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge=20=

(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]=20
(rev 08)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP=20
(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] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D didn't try =
it

Comments/Problems:

1. When writing the partition table, I actually wanted to keep the=20
contents of my /home partition, but the warning wasn't clear enough and=20=

I was afraid it would rewrite over (it says "Warning: this will erase=20
any data on the partitions you have assigned a file system to"; this is=20=

incorrect, it would erase the data unless I chose the option 'keep and=20=

use data on this partition'). In fact, I trusted it and it did keep my=20=

partition while rewriting over / and /usr and /var, but the message=20
could have been clearer.

2. The kernel did not want to install. In fact, it did, but when I=20
looked at the /var/log/message, it complained that I was installing a=20
kernel over itself (same version) and hence that the modules would be=20
seriously messed up, and so better to stop.

3. Installing Lilo seemed to be pretty messed up: it complained it=20
didn't want to install on an unclean install (all right) but then when=20=

I said do it anyway, because the unclean was actually just created a=20
moment before, it started to reinstall everything (it seemed). It's=20
actually hard to figure what it was doing... since it complained left=20
and right, I started rebooting in the hope that things didn't go as bad=20=

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=20=

rebooted into the Debian installer... I rebooted again after manually=20
ejecting the disk, but I really shouldn't have to do that.

5. Because of all that, I restarted the whole process, actually changed=20=

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=20=

INSTALL FROM A NETWORK!!!  WHAT IS THIS???

6. So I reinstall from scratch again (5th time, by now). It never asks=20=

me for network settings but by now I know better. I ask to "Go Back"=20
before partitioning the disk, and ask to detect network hardware. Then=20=

I redo everything (partitioning, install base system). Never a chance=20
to install the secondary system inside the first system as is=20
promiseed, or even configuring the primary system. Or maybe this was=20
done automatically during the install. I trust the system and reboot.

This time, the system reboots and I *do* have an internet connection.=20
Plus I have to say I have been using dselect for so long, aptitude is a=20=

nice change.


Independent suggestion: I am reinstalling Debian because my machine was=20=

compromised. I cannot trust any of the programs. However, reinstalling=20=

the base system with the rescue disk broke down my libc and I end up=20
having to reinstall the whole system (not a bad thing anyway). It's=20
actually a good thing the Debian installer refuses to install over an=20
unclean installation.  Nevertheless, there should be an option for=20
rootkit (reinstalling the base packages and anything else that has been=20=

compromised, by examining the filesystem and checking if it corresponds=20=

to the apt database). This would be a welcome enhancement to the=20
installation process.


Thanks for the effort. Globally, I'm not unhappy to upgrade my machine,=20=

even though it was not what I planned...
--
Herv=E9=

--Apple-Mail-5--214864640
Content-Transfer-Encoding: quoted-printable
Content-Type: text/enriched;
        charset=ISO-8859-1



<fontfamily><param>Courier</param><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=20

Memory: 512MB

Root Device: /dev/hda (IDE)

Root Size/partition table:=20

    Name      Flags      Part Type    FS Type     Size (MB)   Mount

 -------------------------------------------------------------------

    hda1                   Primary     Linux ext3      98.71  /boot  =20

    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:  [EMAIL PROTECTED]:~$ 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] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D 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></fontfamily>


Thanks for the effort. Globally, I'm not unhappy to upgrade my
machine, even though it was not what I planned...

--

Herv=E9=

--Apple-Mail-5--214864640--


---------------------------------------
Received: (at 237455-done) by bugs.debian.org; 13 Oct 2004 21:47:39 +0000
>From [EMAIL PROTECTED] Wed Oct 13 14:47:39 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CHqyA-00078W-00; Wed, 13 Oct 2004 14:47:38 -0700
Received: from dragon.kitenet.net (unknown [66.168.94.144])
        (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
        (Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
        by kitenet.net (Postfix) with ESMTP id 2575B1810F;
        Wed, 13 Oct 2004 20:35:33 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
        id C6B796E111; Wed, 13 Oct 2004 16:36:59 -0400 (EDT)
Date: Wed, 13 Oct 2004 16:36:59 -0400
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED]
Subject: closing old installation-reports
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.5 required=4.0 tests=BAYES_00,SUSPICIOUS_RECIPS 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 8


--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I'm closing this old installation report, since it looks to me like all the
problems reported in it are old and fixed. There are much newer versions of
the debian installer available, that fix lots of bugs. If you're able to
try one and verify that the problems you reported are fixed (or file a new
report if not), that would be great.

Thanks for your installation report.

--=20
see shy jo

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBbZHrd8HHehbQuO8RAh+GAKDRX7bxhNlBf7bBpmM3BwnErCpeFQCfTvrK
q0ckVhnUPx+u+Pf9VD48lDs=
=Pdl/
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to