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

Bug#79092: marked as done ([i386, need more info] writes bad lilo.conf)

Your message dated Wed, 5 Dec 2001 23:11:33 -0700
with message-id <20011205231133.A1192@Obsession>
and subject line lilo.conf problems in potato
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; 8 Dec 2000 13:15:57 +0000
>From HansJRauch@web.de Fri Dec 08 07:15:57 2000
Return-path: <HansJRauch@web.de>
Received: from pop3.web.de (smtp.web.de) [] 
	by master.debian.org with smtp (Exim 3.12 1 (Debian))
	id 144NNU-0004Qf-00; Fri, 08 Dec 2000 07:15:56 -0600
Received: from Sonne by smtp.web.de with smtp
	(freemail #2) id m144NNO-005FuSC; Fri, 8 Dec 2000 14:15 +0100
From: Hans-Joachim Rauch <HansJRauch@web.de>
To: debian.org <submit@bugs.debian.org>
Subject: boot problem
Date: Fri, 8 Dec 2000 13:53:38 +0100
X-Mailer: KMail [version 1.0.28]
Content-Type: text/plain
MIME-Version: 1.0
Message-Id: <00120814123100.00383@Sonne>
Content-Transfer-Encoding: 8bit
Delivered-To: submit@bugs.debian.org

Package: boot -cd
Version: debian gnu liux 2.2  (linuxland)

architecture: i386
model: cyrix 6x86 166 Mhz
memory: 128 mb edo
scsi: none
cd-rom: ATAPI 8x
network card: 3Com Fast Etherlink PCI
pcmcia: none
soundcard: SB 32 pnp
harddisk: FUJITSU 9773 mb w/2048 kb cache
videocard: ATI Rage IIc PCI 4mb


1) Kernelreport:	chmod: /etc/resolv.cont: no such file or directory

2) Kernelreport: 	starting internel superserver: inetd.
		/bin/sh: /sbin/termwrap: cannot execute: no such file etc.
		/bin/sh: exec: /sbin/termwrap: cannot execute: no such file etc.
		INIT:  ld "1" respawing too fast: disabled for 5 minutes

then after 5 minutes its starts with the same messages.but  no futher booting.

Before there was a old SUSE version on the disk with 3 partitions;
one for swap 128mb
one for /
one for /home

I used still this three partitions but I formatted the swap and / partitions
but not the /home
the installation makes no problem, only the booting  

any idea or helb?



Received: (at 79092-done) by bugs.debian.org; 6 Dec 2001 06:11:10 +0000
>From tillman@azstarnet.com Thu Dec 06 00:11:10 2001
Return-path: <tillman@azstarnet.com>
Received: from cepheus.azstarnet.com [] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16BrkT-0000JU-00; Thu, 06 Dec 2001 00:11:10 -0600
Received: from Obsession (toff@dhcp981.mc01.dsl.fastucson.net [])
	by cepheus.azstarnet.com (8.9.3/8.9.3) with SMTP id XAA09401;
	Wed, 5 Dec 2001 23:11:06 -0700 (MST)
X-Sent-via: StarNet http://www.azstarnet.com/
Received: by Obsession (sSMTP sendmail emulation); Wed, 5 Dec 2001 23:11:33 -0700
Date: Wed, 5 Dec 2001 23:11:33 -0700
From: Chris Tillman <tillman@azstarnet.com>
To: 79092-done@bugs.debian.org
Cc: HansJRauch@web.de
Subject: lilo.conf problems in potato
Message-ID: <20011205231133.A1192@Obsession>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.22i
Delivered-To: 79092-done@bugs.debian.org

The referenced report, regarding lilo.conf problems, is presumed to
have been fixed by now. Please let us know if this is still a problem
with current woody boot-floppies. The last message was added in Dec

*--v------ Installing Debian GNU/Linux 3.0 For PowerPC -----v----*
|  <http://mirrors.kernel.org/debian/dists/woody/main/disks-     |
|  (pause for breath)    powerpc/current/doc/install.en.html>    |
|         debian-imac: <http://debian-imac.sourceforge.net>      |
|            Chris Tillman        tillman@azstarnet.com          |
|                     May the Source be with you                 |

Reply to: