Package: dropbear
Version: 2012.55-1
Severity: minor

Hi,

i have disabled networking for the initial ramdisk environment
via setting ip=none on the kernel commandline.

When booting up the ramdisk dropbear complains about not finding
a net-* file and obviously is useless without a running network.

Please allow for a way to not install dropbear to the ramdisk
or let the startup script be a bit smarter.

For example the run script (scripts/pre-mount/dropbear)
says

   for x in $(cat /proc/cmdline); do
        case "$x" in
                ip=*)
                        IPOPTS="${x#ip=}"
                        ;;
        esac
   done

but it could look like this

   for x in $(cat /proc/cmdline); do
        case "$x" in
                ip=none|ip=off)
                        # Do not start as networking is disabled.
                        :
                        ;;
                ip=*)
                        IPOPTS="${x#ip=}"
                        ;;
        esac
   done

Thank you!

   --lars

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages dropbear depends on:
ii  libc6   2.13-35
ii  zlib1g  1:1.2.7.dfsg-13

dropbear recommends no packages.

Versions of packages dropbear suggests:
ii  openssh-client  1:6.0p1-3
pn  runit           <none>
ii  udev            175-7
ii  xauth           1:1.0.7-1

-- no debconf information


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

Reply via email to