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

Bug#329614: -o relative-file puts it inside the build directory, which gets deleted



Package: initrd-tools
Version: 0.1.82
Severity: normal

If I am in /boot and I run mkinitrd -o foo 2.4.27, then I expect it to
output to a file foo in the current directory. Instead it writes the
output file somewhere inside the temporary tree, which is deleted when
mkinitrd exits. Only if I run it with an absolute path do I get a file
out.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages initrd-tools depends on:
ii  coreutils [fileutils]         5.2.1-2.1  The GNU core utilities
ii  cpio                          2.6-5      GNU cpio -- a program to manage ar
ii  cramfsprogs                   1.1-6      Tools for CramFs (Compressed ROM F
ii  dash                          0.5.2-7    The Debian Almquist Shell
ii  fileutils                     5.2.1-2.1  The GNU file management utilities 
ii  util-linux                    2.12p-8    Miscellaneous system utilities

initrd-tools recommends no packages.

-- no debconf information

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


Reply to: