Bug#803115: flash-kernel: please provide an option to disable creation of backup files

2015-10-26 Thread Eric Cooper 
Package: flash-kernel
Version: 3.46
Severity: wishlist

I'd like an option (configurable in /etc/default/flash-kernel ideally)
to prevent flash-kernel from creating .bak files for uImage, uInitrd,
and dtb, in order to same space on my system.  I'm willing to live
dangerously and keep a serial and JTAG cable handy :-)

Bug#804359: flash-kernel: Little-endianness is tested incorrectly for NSLU2

2015-11-07 Thread Eric Cooper 
Package: flash-kernel
Version: 3.48
Severity: normal
Tags: patch

The nslu2_swap() function incorrectly tests $little_endian and will
always think it is true.

Untested patch attached since I don't have a slug.
>From e719eabe8f4640fb192dae4ce44235653ce8e803 Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 7 Nov 2015 12:58:04 -0500
Subject: [PATCH] Test $little_endian correctly in nslu2_swap()

Signed-off-by: Eric Cooper 
---
 functions | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/functions b/functions
index ea69df7..35d872b 100644
--- a/functions
+++ b/functions
@@ -425,7 +425,7 @@ sercomm_header() {
 }
 
 nslu2_swap() {
-	if [ "$little_endian" ]; then
+	if [ "$little_endian" -eq 1 ]; then
 		devio "<<$1" "xp $,4"
 	else
 		cat "$1"
-- 
2.6.2

Bug#803115: flash-kernel: please provide an option to disable creation of backup files

2015-11-07 Thread Eric Cooper 
Package: flash-kernel
Version: 3.48
Followup-For: Bug #803115

Here's a patch, tested on my Seagate Dockstar.

Default behavior:
$ sudo flash-kernel
DTB: kirkwood-dockstar.dtb
Installing kirkwood-dockstar.dtb into 
/boot/dtbs/4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb
Taking backup of kirkwood-dockstar.dtb.
Installing new kirkwood-dockstar.dtb.
flash-kernel: installing version 4.2.0-0.bpo.1-kirkwood
flash-kernel: appending 
/usr/lib/linux-image-4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb to kernel
Generating kernel u-boot image... done.
Taking backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Taking backup of uInitrd.
Installing new uInitrd.
Taking backup of dtb.
Installing new dtb.

New behavior with NO_BACKUP_FILES=true set in /etc/default/flash-kernel:

$ sudo flash-kernel
DTB: kirkwood-dockstar.dtb
Installing kirkwood-dockstar.dtb into 
/boot/dtbs/4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb
Skipping backup of kirkwood-dockstar.dtb.
Installing new kirkwood-dockstar.dtb.
flash-kernel: installing version 4.2.0-0.bpo.1-kirkwood
flash-kernel: appending 
/usr/lib/linux-image-4.2.0-0.bpo.1-kirkwood/kirkwood-dockstar.dtb to kernel
Generating kernel u-boot image... done.
Skipping backup of uImage.
Installing new uImage.
Generating initramfs u-boot image... done.
Skipping backup of uInitrd.
Installing new uInitrd.
Skipping backup of dtb.
Installing new dtb.
>From e111d107a0e9453d0af0eb0ed4708a1aea1f901e Mon Sep 17 00:00:00 2001
From: Eric Cooper 
Date: Sat, 7 Nov 2015 13:15:39 -0500
Subject: [PATCH] Add NO_BACKUP_FILES option to /etc/default/flash-kernel.

If set, no backups of kernel, initrd, and dtb files will be created,
to save space on systems with limited storage.

Signed-off-by: Eric Cooper 
---
 README|  9 ++---
 functions | 18 --
 2 files changed, 22 insertions(+), 5 deletions(-)

diff --git a/README b/README
index 4ca5a22..bc7493c 100644
--- a/README
+++ b/README
@@ -191,9 +191,12 @@ Configuration files currently supported:
   script snippets. See "Adding U-Boot Commands for Pre-Boot Execution"
   below for more details.
 
-* /etc/default/flash-kernel currently contains a single variable,
-  LINUX_KERNEL_CMDLINE, which should be used by bootscripts to set kernel
-  options.
+* /etc/default/flash-kernel currently contains the following variables:
+- LINUX_KERNEL_CMDLINE, which should be used by bootscripts to set kernel
+  options.
+- NO_BACKUP_FILES, which if set to "true" or "yes" will prevent
+  flash-kernel from creating backup versions of kernel, initrd,
+  and dtb files.
 
 
 Adding U-Boot Commands for Pre-Boot Execution
diff --git a/functions b/functions
index 35d872b..9bbef2c 100644
--- a/functions
+++ b/functions
@@ -404,13 +404,27 @@ mkimage_multi() {
 	echo "done." >&2
 }
 
+# Return a nonempty string *unless* NO_BACKUP_FILES is set.
+get_backup_preference() {
+. /etc/default/flash-kernel
+	case $(echo "$NO_BACKUP_FILES" | tr '[:upper:]' '[:lower:]') in
+	true|yes|1) ;;
+	*) echo yes ;;
+	esac
+}
+
 backup_and_install() {
 	local source="$1"
 	local dest="$2"
+	local do_backups=$(get_backup_preference)
 
 	if [ -e "$dest" ]; then
-		echo "Taking backup of $(basename "$dest")." >&2
-		mv "$dest" "$dest.bak"
+		if [ -n "$do_backups" ]; then
+			echo "Taking backup of $(basename "$dest")." >&2
+			mv "$dest" "$dest.bak"
+		else
+			echo "Skipping backup of $(basename "$dest")." >&2
+		fi
 	fi
 	echo "Installing new $(basename "$dest")." >&2
 	mv "$source" "$dest"
-- 
2.6.2

Bug#759657: console-setup w/ systemd forgets font setting

2015-11-19 Thread Eric Cooper 
Package: console-setup
Version: 1.134
Followup-For: Bug #759657

I see the same problem on every reboot.

While booting, it looks like the font switches from VGA to Terminus
during the boot messages.  But then the screen is cleared and the
getty login prompts are back in VGA.  If I run "setupcon" manually, it
changes to Terminus.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages console-setup depends on:
ii  console-setup-linux 1.134
ii  debconf 1.5.58
ii  keyboard-configuration  1.134
ii  xkb-data2.16-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.19-22
ii  lsb-base  9.20150917

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.58
ii  initscripts 2.88dsf-59.2
ii  liblocale-gettext-perl  1.07-1

Versions of packages console-setup-linux depends on:
ii  kbd 1.15.5-2
ii  keyboard-configuration  1.134

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common  
pn  console-data
pn  console-tools   
ii  kbd 1.15.5-2

-- debconf information:
  keyboard-configuration/modelcode: ibm_spacesaver
  keyboard-configuration/store_defaults_in_debconf_db: true
* console-setup/charmap47: UTF-8
  console-setup/framebuffer_only:
  keyboard-configuration/xkb-keymap: us
  keyboard-configuration/layoutcode: us
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  keyboard-configuration/toggle: No toggling
  console-setup/guess_font:
  console-setup/fontsize-text47: 8x16
  keyboard-configuration/optionscode: ctrl:nocaps
* console-setup/fontsize-fb47: 8x16
  keyboard-configuration/unsupported_layout: true
* keyboard-configuration/compose: No compose key
* console-setup/fontface47: Terminus
  keyboard-configuration/variantcode:
  console-setup/use_system_font:
  console-setup/fontsize: 8x16
* keyboard-configuration/variant: English (US)
* keyboard-configuration/unsupported_config_options: true
  keyboard-configuration/other:
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/layout:
  debian-installer/console-setup-udeb/title:
  console-setup/store_defaults_in_debconf_db: true
  console-setup/codesetcode: Lat15
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/unsupported_options: true
* keyboard-configuration/model: IBM Space Saver
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/ctrl_alt_bksp: false

Bug#759657: console-setup w/ systemd forgets font setting

2015-12-12 Thread Eric Cooper 
On Sat, Dec 12, 2015 at 01:52:29PM +, Brian Potkin wrote:
> On Thu 10 Dec 2015 at 03:47:24 +0100, Michael Biebl wrote:
>
> > Am 10.12.2015 um 00:55 schrieb Samuel Thibault:
> > > Eric Cooper, on Thu 19 Nov 2015 13:31:57 -0500, wrote:
> > >> While booting, it looks like the font switches from VGA to Terminus
> > >> during the boot messages.  But then the screen is cleared and the
> > >> getty login prompts are back in VGA.  If I run "setupcon" manually, it
> > >> changes to Terminus.
> > >
> > > So it seems like something is resetting the font back to VGA (and it's
> > > not console-setup, which loads Terminus).
> > >
> > > systemd people, do you have any idea?  This has started happening with
> > > the switch to systemd.
> >
> > From a cursory look, it doesn't seem to be caused by systemd itself but
> > it's a race condition and the way console-setup works. And the timing
> > under systemd might simply the different then under sysvinit (it's
> > usually faster).
> >
> > When Karsten added the dependency on udev settle, it probably just
> > changed the timing (by delaying it a little) so made it less likely to
> > happen.
> >
> > It might be, that loading the KMS module resets the font.
> > So maybe console-setup should run when hardware shows up.
> > This is a shot in the dark, but can you try and create the following
> > udev rules file:
> >
> > $ cat /etc/udev/rules.d/90-setupcon.rules
> > ACTION=="add", SUBSYSTEM=="vtconsole", KERNEL=="vtcon*",
> > RUN+="/bin/setupcon"
>
> This file does it for me up to now. After about 10 reboots the font is
> not being reset back to VGA.

Yes, this solves the problem for my system too.  Please consider
adding this to the console-setup package.

--
Eric Cooper e c c @ c m u . e d u

Re: Debian has failed us

2007-01-11 Thread Eric Cooper 
On Thu, Jan 11, 2007 at 07:18:24PM +0100, Frans Pop wrote:
> [...]
> False: it was not compiled into the standard Debian kernel. The installer
> does not use custom kernels. This was explained to you at the time.
> [...]
> Please check your facts before sending such mails:
> [...] 
> I'll ignore the rest of your rant as it is obviously based on false
> assumptions.
> [...]

This is an incredibly arrogant and hostile response to a long-time,
technically competent Debian user who posted a calm and informative
message.

> P.S. Some apologies would be appreciated.

On the contrary, he attacked nobody personally, and his tone was not
inflammatory. Your response made an unfortunate situation worse.  It's
you who should apologize.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#408408: installation-guide-i386: possible typo in "Submitting Installation Reports"

2007-01-25 Thread Eric Cooper 
Package: installation-guide-i386
Version: http://d-i.alioth.debian.org/manual/en.i386
Severity: normal

Section ch05s03.html#submit-bug says:
run the command reportbug installation-report
Shouldn't this be
run the command reportbug installation-reports

i.e., against the installation-reports pseudo-package, not the actual
installation-report package?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#297536: installation-guide-powerpc: netbooting from open firmware

2007-02-04 Thread Eric Cooper 
Package: installation-guide-powerpc
Version: http://d-i.alioth.debian.org/manual/en.powerpc/ch05s01.html
Followup-For: Bug #297536

On my gray & white G4, I had to use the OF command
   boot enet:0,yaboot
instead of just "boot enet:0" as specified in the manual.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#547218: debootstrap: cannot create squeeze chroot

2009-09-17 Thread Eric Cooper 
Package: debootstrap
Version: 1.0.15
Severity: important
Tags: patch

debootstrap currently fails to create a squeeze chroot.  The log
output shows that readline-common depends either on dpkg >= 1.15.4
(which is not yet in squeeze) or on install-init (which isn't being
installed), so it fails.

If I add
--include=install-init
to the command line to break the cycle it works correctly.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (400, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages debootstrap depends on:
ii  binutils  2.19.51.20090723-1 The GNU assembler, linker and bina
ii  wget  1.11.4-4   retrieves files from the web

Versions of packages debootstrap recommends:
ii  gnupg 1.4.9-4GNU privacy guard - a free PGP rep

debootstrap suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#509937: installation-guide-i386: suggested image for memory-stick booting does not contain network drivers

2009-02-16 Thread Eric Cooper 
Package: installation-guide-i386
Version: lenny
Followup-For: Bug #509937

Section 4.3.1 ("Copying the files -- the easy way") says:
There is an all-in-one file hd-media/boot.img.gz which contains
all the installer files (including the kernel) as well as syslinux
and its configuration file.

As far as I can tell, this image does not contain any network drivers.
At least, the installer on this image could not detect the Intel
Gigabit Ethernet hardware on my box (which the etch installer had no
problem with).  There is no /lib/modules/.../drivers/net subdirectory,
and there doesn't appear to be any compiled-in support in the kernel
either.

-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (400, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#509937: installation-guide-i386: suggested image for memory-stick booting does not contain network drivers

2009-02-16 Thread Eric Cooper 
On Mon, Feb 16, 2009 at 08:02:04PM +0100, Frans Pop wrote:
> This has absolutely nothing to do with this bug report! Please report your 
> issue separately, but first verify that you are doing things correctly.
> 
> hd-media/boot.img.gz indeed does not contain any net drivers: it does not 
> need them! They get loaded later during the installation.

I booted from the memory stick, and chose the basic install.  After
searching the local disks, it reported that it couldn't find any ISO
images and said I'd have to net boot (fine).  I continued, and it
attempted to set up networking, which failed because it couldn't
discover any networking hardware. At that point, I assumed (maybe
incorrectly) I wouldn't be able to net boot, because the only menu
choices were to go back and re-try what I had already tried.

> You are simply not using the installer correctly.

If there was something else I was supposed to do, it certainly wasn't
obvious.

By comparison, I wiped that memory stick and recreated it the "hard
way" using syslinux and the linux and initrd images from the
netboot/debian-installer directory.  That worked fine.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Bug#509937: installation-guide-i386: suggested image for memory-stick booting does not contain network drivers

2009-02-16 Thread Eric Cooper 
On Mon, Feb 16, 2009 at 09:40:08PM +0100, Frans Pop wrote:
> Did you actually copy a CD image (ISO file) onto the USB stick?
> Exactly what image did you copy?

You're right -- I completely skipped that.  Somehow I must have
thought everything was in the boot.img.gz file.  
In my defense, there is some misleading language in the 4.3.1
paragraph:
"all-in-one file" ... "contains all the installer files ..."
"To use this image you *only* have to extract it directly to your
USB stick" (emphasis mine)

I suggest changing "only" to "first".  And perhaps the paragraph
beginning "After that, mount the USB memory stick " could be
emphasized somehow (bold face or whatever).

Anyway, sorry for the noise, and thanks and congratulations for the
lenny release.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: Emdebian sprint / runtime device fingerprinting in bootloader

2011-02-23 Thread Eric Cooper 
On Wed, Feb 23, 2011 at 04:45:25PM +, Andy Green wrote:
> Maybe Steve Sakoman can suggest some example boards that will be
> difficult to tell apart at runtime, but it matters?

Here's one example: the Seagate DockStar is very similar to the
Marvell Sheevaplug (same Kirkwood SoC), but has a different amount of
SDRAM, different GPIOs, UART, etc.  Many of the other systems based on
this chip ("plug computers") would be similarly difficult to
distinguish at runtime.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110223182122.GG2845@localhost

Re: Emdebian sprint / runtime device fingerprinting in bootloader

2011-02-24 Thread Eric Cooper 
On Thu, Feb 24, 2011 at 07:09:51AM +, Andy Green wrote:
> Well saying that it's very similar, then listing differences like
> GPIOs that could easily be runtime-detectable, doesn't really pin
> down whether that's a problem or not.

See the arch/arm/mach-kirkwood directory in the Linux tree.  All the
*-setup.c files declare different sets of GPIOs in static structures.
If you know a way to "easily" detect them at runtime, that could unify
a lot of this code.  I'm sure a patch would be welcome.

> What does "different amount of UART" mean when it is the "same
> Kirkwood SoC"?

(Note that I didn't say what you quoted.)  But it was a brain slip; I
was just remembering a difference in the physical connectors for the
serial ports.

-- 
Eric Cooper e c c @ c m u . e d u


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110224130819.GA6487@localhost

Bug#572013: bashism in /usr/share/udhcpc/default.script causes network setup to fail

2010-05-20 Thread Eric Cooper 
Package: udhcpc
Version: 1:1.15.3-1
Severity: normal

The proposed fix -- $((metric += 1)) -- doesn't have the same
semantics.  The routing table metric will start at 1 rather than 0.

You need to increment $metric in a separate command, after using it in
the route command:

for i in $router; do
/sbin/route add default gw $i dev $interface metric $metric
metric=$((metric + 1))
done

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udhcpc depends on:
ii  busybox   1:1.15.3-1 Tiny utilities for small and embed

udhcpc recommends no packages.

udhcpc suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100520210108.30723.48811.report...@stratocaster.home

Bug#591436: busybox-syslogd: initscript prints many error messages

2010-08-02 Thread Eric Cooper 
Package: busybox-syslogd
Version: 1:1.15.3-1
Severity: normal

The busybox-syslogd and -klogd initscripts generate lots of error messages like 
this:
cut: /proc/447/stat: No such file or directory
cut: /proc/452/stat: No such file or directory
cut: /proc/453/stat: No such file or directory
Please redirect the stderr output to /dev/null in the initscripts.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100803011606.7285.1781.report...@stratocaster.home

Bug#594616: busybox-syslogd: typos in initscript messages

2010-08-27 Thread Eric Cooper 
Package: busybox-syslogd
Version: 1:1.17.1-2
Severity: minor

"busybox' syslogd implementation" should be either "busybox's syslogd
implementation" if you want the correct possessive form, or just
"busybox syslogd implmentation" if you want to use busybox as just an
adjective modifying syslogd.  I personally like the 2nd form better,
since it's less busy.

Similarly for the message about klogd.

Thanks for packaging this.
-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20100827183153.9931.38200.report...@stratocaster.home

Bug#684596: udhcpc avoid default.script dependency on net-tools

2012-08-11 Thread Eric Cooper 
Package: udhcpc
Version: 1:1.20.0-6
Severity: normal
Tags: patch

If I remove net-tools from my system, udhcpc breaks because its
default.script relies on ifconfig and route, but udhcpc doesn't depend
on net-tools.

Since versions of these are built into busybox, the attached
quick-and-dirty patch just uses those.  A better approach might be to
use the "ip" command, either by depending on iproute2 or using the one
built into busybox.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udhcpc depends on:
ii  busybox  1:1.20.0-6

udhcpc recommends no packages.

udhcpc suggests no packages.

-- Configuration Files:
/etc/udhcpc/default.script changed [not included]

-- no debconf information
--- /etc/udhcpc/default.script.orig	2012-04-11 15:04:56.0 -0400
+++ /etc/udhcpc/default.script	2012-08-11 11:56:13.0 -0400
@@ -11,15 +11,15 @@
 	[ -n "$broadcast" ] && BROADCAST="broadcast $broadcast"
 	[ -n "$subnet" ] && NETMASK="netmask $subnet"
 
-	/sbin/ifconfig $interface $ip $BROADCAST $NETMASK
+	/bin/busybox ifconfig $interface $ip $BROADCAST $NETMASK
 
 	if [ -n "$router" ]; then
 	echo "$0: Resetting default routes"
-	while /sbin/route del default gw 0.0.0.0 dev $interface; do :; done
+	while /bin/busybox route del default gw 0.0.0.0 dev $interface; do :; done
 
 	metric=0
 	for i in $router; do
-		/sbin/route add default gw $i dev $interface metric $metric
+		/bin/busybox route add default gw $i dev $interface metric $metric
 		metric=$(($metric + 1))
 	done
 	fi
@@ -45,7 +45,7 @@
 	if [ -x /sbin/resolvconf ]; then
 	resolvconf -d "${interface}.udhcpc"
 	fi
-	/sbin/ifconfig $interface 0.0.0.0
+	/bin/busybox ifconfig $interface 0.0.0.0
 	;;
 
 leasefail)