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

Bug#283147: marked as done (kernel-image-2.6.8-1-k7: removes /initrd.img on upgrade)



Your message dated Sat, 27 Nov 2004 19:21:30 -0800
with message-id <41A9443A.3050505@triplehelix.org>
and subject line Bug#283147: kernel-image-2.6.8-1-k7: removes /initrd.img on upgrade
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; 26 Nov 2004 20:14:17 +0000
>From Thomas.Koenig@online.de Fri Nov 26 12:14:17 2004
Return-path: <Thomas.Koenig@online.de>
Received: from moutng.kundenserver.de [212.227.126.188] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CXmTw-0003RW-00; Fri, 26 Nov 2004 12:14:17 -0800
Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de)
	by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
	id 1CXmTv-0007b3-00
	for submit@bugs.debian.org; Fri, 26 Nov 2004 21:14:15 +0100
Received: from [80.141.198.197] (helo=meiner.onlinehome.de)
	by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
	id 1CXmTu-0005f9-00; Fri, 26 Nov 2004 21:14:15 +0100
Received: from ig25 by meiner.onlinehome.de with local (Exim 3.36 #1 (Debian))
	id 1CXmU0-000655-00; Fri, 26 Nov 2004 21:14:20 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Thomas Koenig <Thomas.Koenig@online.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: kernel-image-2.6.8-1-k7: removes /initrd.img on upgrade
X-Mailer: reportbug 3.2
Date: Fri, 26 Nov 2004 21:14:20 +0100
Message-Id: <[🔎] E1CXmU0-000655-00@meiner.onlinehome.de>
Sender: Thomas Koenig <Thomas.Koenig@online.de>
X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:82006718d44785d1b0aefbb6e084916e
Delivered-To: submit@bugs.debian.org
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=-6.2 required=4.0 tests=BAYES_00,DRASTIC_REDUCED,
	HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: kernel-image-2.6.8-1-k7
Version: 2.6.8-9
Severity: critical
Justification: breaks the whole system

... which is a Bad Thing.  I was lucky that I had other entries
in my /etc/lilo.conf .  lilo failed on upgrade, and
the recently installed kernel was
unbootable.

Here's my lilo.conf.

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt', or install a new kernel.  The |
# | computer will most likely fail to boot if a kernel-image      |
# | post-install script or you don't remember to run `lilo'.      |
# |                                                               |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
#    bios=0x81

#disk=/dev/sda
#    bios=0x80

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda4

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
prompt
timeout=150
#       prompt
#       single-key
#       delay=100
#       timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#
vga=normal

# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
append="hdc=ide-scsi hdd=ide-scsi max_scsi_luns=1"

# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
        label=Linux
        read-only
        initrd=/initrd.img
#       restricted
#       alias=1

image=/boot/vmlinuz-2.6.6-2-k7
        label=Linuxold
        read-only
        initrd=/boot/initrd.img-2.6.6-2-k7
        optional
#       restricted
#       alias=2

image=/boot/vmlinuz-2.4.26-1-k7
        label=2426
        read-only
        initrd=/boot/initrd.img-2.4.26-1-k7
        optional

# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#       label=HURD
#       restricted
#       alias=3
other=/dev/hda1
  label="WinNT(hda1)"

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=C, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages kernel-image-2.6.8-1-k7 depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  fileutils                     5.2.1-2    The GNU file management utilities 
ii  initrd-tools                  0.1.74     tools to create initrd image for p
ii  module-init-tools             3.1-rel-2  tools for managing Linux kernel mo

-- no debconf information

---------------------------------------
Received: (at 283147-done) by bugs.debian.org; 28 Nov 2004 03:21:32 +0000
>From joshk@triplehelix.org Sat Nov 27 19:21:31 2004
Return-path: <joshk@triplehelix.org>
Received: from smtp807.mail.sc5.yahoo.com [66.163.168.186] 
	by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
	id 1CYFcx-0005r0-00; Sat, 27 Nov 2004 19:21:31 -0800
Received: from unknown (HELO triplehelix.org) (edkwan@sbcglobal.net@68.126.237.170 with login)
  by smtp807.mail.sc5.yahoo.com with SMTP; 28 Nov 2004 03:21:31 -0000
Received: from [192.168.0.7] (darjeeling.wifi.triplehelix.org [192.168.0.7])
	by triplehelix.org (Postfix) with ESMTP id F0A852A9590;
	Sat, 27 Nov 2004 19:21:30 -0800 (PST)
Message-ID: <41A9443A.3050505@triplehelix.org>
Date: Sat, 27 Nov 2004 19:21:30 -0800
From: Joshua Kwan <joshk@triplehelix.org>
User-Agent: Mozilla Thunderbird 0.9 (X11/20041124)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Stephen Gran <sgran@debian.org>
Cc: 283147-done@bugs.debian.org
Subject: Re: Bug#283147: kernel-image-2.6.8-1-k7: removes /initrd.img on upgrade
References: <[🔎] E1CXmU0-000655-00@meiner.onlinehome.de> <20041126204146.GB14670__37411.2710626379$1101503091$gmane$org@www.lobefin.net> <[🔎] 41A91A73.1000202@triplehelix.org> <[🔎] 20041128023037.GA11574@www.lobefin.net> <[🔎] 41A939D0.6040502@triplehelix.org> <[🔎] 20041128031703.GB11574@www.lobefin.net>
In-Reply-To: <[🔎] 20041128031703.GB11574@www.lobefin.net>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: 283147-done@bugs.debian.org
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=-4.4 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
	UPPERCASE_25_50 autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephen Gran wrote:
| Looks fixed to me.

I'll take your word for it :)

Closing this bug.

- --
Joshua Kwan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQalEOqOILr94RG8mAQLhiRAAsV0tBMIXlznz1JeoCieln4rerxNAyywH
zG8pvZQQkdcj4DULtIIIt9Y/3dEctUfoWAO8Hn9j/SUH+IWodXnE3rLgypA1y/Nd
0Rg8rBvHPjHB4SB/k+6yLCCdnni8qsAV/9vWN6+0UvFppAkfOb/yzG0Wy14YQk1m
IvjD3XPG65GBXDb/Y/RG1Ete/Qd08yHJOcrHRRTnEVsDcBpSHTAmdhrYUhLRlX/o
kQgOnjb3mCONtNPyg2t931pN47y40ALfdToziwnCck0EgPDxG8os2NaEuKobrF5+
M+QUWaiv6w2q3x3a3keSBE4TK301OpG4lrRWCVLY+4TNspHy2Kf1e66/xUo2sWsv
WqZVv7UcKbU/z+Adw/iCrSjizKNGkQkzawYQTYoFwOYF7NbrHgFpP5flFYahTrJq
O92YrxmPVHD4e1D3FO554PrM2jikiDo7WwuTeDzDsFv6BKcwqBDiqlbnQJo9Njrb
/0xmnm9i82oq3MrFaB7qBPQ1O4R9ZwjeIjvCojnlLvipl0TTjIhp12FPXUV11tdq
jB1ZbfVwDpod2W/+Bk+q3EYqAc1OS+TTCcuXIYIFk3dfyGf+ZKvCsFNIihnyo/Zx
rQeUdYrlw06iXUKIdanCUgXE9SO3gKnwimsz6cR1lAMElXU8VOqTue21ujYeeRLD
GGIQWVqmTG8=
=pN0o
-----END PGP SIGNATURE-----



Reply to: