Your message dated Fri, 30 Nov 2007 08:55:59 -0600
with message-id <[EMAIL PROTECTED]>
and subject line sudo needs to be configured correctly before being used
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)

--- Begin Message ---
Subject: kernel-package: Despite passing --initrd option, no initrd-image was 
built.
Package: kernel-package
Version: 10.068
Severity: important

*** Please type your report below this line ***

Hi,


I did the following in /usr/src.

wget http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.21.1.tar.bz2
tar xjvf linux-2.6.21.1.tar.bz2
cd linux-2.6.21.1
cp /boot/config-2.6.20-1-686 .
make menuconfig --> load /usr/src/config-2.6.20-1-686 ; enable DEBUG for
HDI devices
make-kpkg --initrd kernel_image --revision=pm.0 --rootcmd sudo
sudo dpkg -i linux-image-2.6.21.1_pm.0_i386.deb
sudo shutdown -r now

The linux kernel was displayed in GRUB, but did not fully boot, because
it could not access the root filesystem. Looking in /boot/grub/menu.lst
the entries for 2.6.21.1 did not have an initrd line and I did not find
a corresponding image under /boot/ .

Doing

sudo update-initramfs -c -k 2.6.21.1

and editing /boot/grub/menu.lst gave me a bootable linux kernel.


Did I do something wrong? Thanks.

Paul

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21.1 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages kernel-package depends on:
ii  dpkg                          1.13.25    package maintenance system
for Deb
ii  dpkg-dev                      1.13.25    package building tools for
Debian
ii  file                          4.20-5     Determines file type using
"magic"
ii  gcc [c-compiler]              4:4.1.1-15 The GNU C compiler
ii  gcc-4.0 [c-compiler]          4.0.3-7    The GNU C compiler
ii  gcc-4.1 [c-compiler]          4.1.1-21   The GNU C compiler
ii  gettext                       0.16.1-1   GNU Internationalization
utilities
ii  make                          3.81-3     The GNU version of the
"make" util
ii  perl                          5.8.8-7    Larry Wall's Practical
Extraction 
ii  po-debconf                    1.0.8      manage translated Debconf
template

Versions of packages kernel-package recommends:
ii  bzip2                         1.0.3-6    high-quality block-sorting
file co
ii  libc6-dev [libc-dev]          2.5-4      GNU C Library: Development
Librari

-- no debconf information

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


--- End Message ---
--- Begin Message ---
Hi,

        From the sudo man page:

       There are two distinct ways to deal with environment variables.
       By default, the env_reset sudoers option is enabled.  This causes
       commands to be executed with a minimal environment containing
       TERM, PATH, HOME, SHELL, LOGNAME, USER and USERNAME in addition
       to variables from the invoking process permitted by the env_check
       and env_keep sudoers options.  There is effectively a whitelist
       for environment variables.

       If, however, the env_reset option is disabled in sudoers, any
       variables not explicitly denied by the env_check and env_delete
       options are inherited from the invoking process.  In this case,
       env_check and env_delete behave like a blacklist.  Since it is
       not possible to blacklist all potentially dangerous envi‐ronment
       variables, use of the default env_reset behavior is encouraged.

       In all cases, environment variables with a value beginning with
       () are removed as they could be inter‐preted as bash functions.
       The list of environment variables that sudo allows or denies is
       contained in the output of sudo -V when run as root.

        manoj

-- 
You will never amount to much. Munich Schoolmaster, to Albert Einstein,
age 10
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


--- End Message ---

Reply via email to