Your message dated Fri, 19 Jul 2013 17:06:44 +0200 with message-id <201307191706.48258.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #588119, regarding Cannot login After Install 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.) -- 588119: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588119 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: "submit@bugs.debian.org" <submit@bugs.debian.org>
- Subject: Cannot login After Install
- From: John Frankish <j-frankish@slb.com>
- Date: Mon, 5 Jul 2010 05:56:09 +0200
- Message-id: <6AC5A55546F64545AE996F8200E3AC4E0333C8D2E3@NL0105EXC01V01.eur.slb.com>
Package: installation-reports Hi, I just installed Debian 5 (testing) on a laptop, but cannot login as user or root on the first (re)boot. Although the installation referred to hda1 as the partition on which debian was installed, the only way to get it to boot afterwards was to refer to sda1 (it is an IDE drive, not scsi) Booting using another os on hda2, I note there is nothing under /home and only a few files under /root - although the installation step to create users/passwords did not report errors. 1. Is it possible to delete certain files to be able to reset the root password? Which ones? 2. What command should I use to (re)create a user from the console prompt? Note: booted with: title debian root (hd0,0) kernel /boot/vmlinuz-2.6.32-5-686 root=/dev/sda1 initrd /boot/initrd.img-2.6.32-5-686 Regards John Package: installation-reports Boot method: <CD?> Image version: <40MB CD image> Date: <21:00 04 July 2010> Machine: <Toshiba Portege M100> Processor: <Intel Pentium M 1.2GHz> Memory: <1GB> Partitions: <hda1 ext3, hda2 ext2, hda3 swap> Output of lspci -knn (or lspci -nn): <n/a> Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system: [O] Clock/timezone setup: [O] User/password setup: [O] Install tasks: [O] Install boot loader: [O] Overall install: [E] Comments/Problems: <See above for error report - suggest that if a user skips the install grub/lilo loader step, the installation routine proposes a grub menu.lst entry to be appended to an existing entry.>
--- End Message ---
--- Begin Message ---
- To: 588119-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Fri, 19 Jul 2013 17:06:44 +0200
- Message-id: <201307191706.48258.holger@layer-acht.org>
Hi, thank you for submitting installation reports, much appreciated. I read through all the bugs mentioned here (and I'm sure they were read by several people at the time they were submitted) and am closing them now as/if - they (finally) indicated success and/or - I know from first hand experience that the functionality is working in Wheezy and/or - they only contained very little information and/or - they contained user errors and/or - they have been from a development phase where things were not stable and/or - they are very old, more than 2.5 years. If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll do if requested) or just file a new one - thats often better, as the bug log will be clearer and shorter and not contain cruft. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---