Your message dated Mon, 8 Jun 2009 17:56:53 +0200
with message-id <20090608155653.ga12...@bongo.bofh.it>
and subject line Re: Bug#532324: udev init script bash+dashism: assumes printf
is a builtin
has caused the Debian Bug report #532324,
regarding udev init script bash+dashism: assumes printf is a builtin
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 ow...@bugs.debian.org
immediately.)
--
532324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 0.141-1
Severity: serious
This was first discovered on Lenny, and I urge you to apply a fix
to the Lenny packages as well.
Debian Policy 10.4 mandates that #!/bin/sh scripts only use POSIX
(SUSv3) commands plus a number of listed extensions. Implementations
of it are (at least) bash, dash, mksh, posh, maybe ksh93 and/or zsh.
However, almost all of these shells implement more than the minimum
required for a /bin/sh by Policy. One example of this is that (at
least) bash and dash implement "printf" as a builtin (posh and mksh
don't).
The /etc/init.d/udev script uses printf, which is part of the Essen-
tial package coreutils, but resides in /usr/bin – which normally is
not a problem. But it also sets the PATH to /bin:/sbin which makes
this into a problem: due to being executed under "set -e", it aborts
under shells other than these implementing a printf builtin once it
is called, since /usr/bin/printf cannot be found.
An evil Würgaround would be to copy /usr/bin/printf to /bin/ (which
is possible if it only links against libraries from /lib/ but total-
ly non-standard), which is what I used for now to get my system to
boot correctly and be accessible via ssh again.
The correct fix would be to use the echo builtin as limited by the
Debian Policy description of it, I suppose.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-6-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages udev depends on:
ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy
ii libc6 2.9-13 GNU C Library: Shared libraries
ii libselinux1 2.0.71-1 SELinux shared libraries
ii libvolume-id1 0.141-1 libvolume_id shared library
ii lsb-base 3.2-22 Linux Standard Base 3.2 init scrip
udev recommends no packages.
udev suggests no packages.
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Jun 08, Thorsten Glaser <t...@mirbsd.de> wrote:
> And I have been running systems with mksh as /bin/sh for a while
> now.
Watch me not care.
Please do not waste your and my time by reopening this bug, if you
disagree feel free to pursue this with the CTTE.
--
ciao,
Marco
signature.asc
Description: Digital signature
--- End Message ---
