Bug#538685: busybox: dc require whitespace between language elements (fixed?)

I think this bug is fixed. The example works correctly for me. $ echo '10 2+f'|busybox dc 12 $ dpkg -s busybox | grep Version Version: 1:1.27.2-1 $ -- Edward.

Re: modem use

Gonzalez Jorge-QJG005 <[EMAIL PROTECTED]> wrote: > Package: potato > Version: 2.2r3 > > When installing Debian, the book says to include a serial driver in the > kernel. The driver should be in the misc category. I did not see any > serial drivers in there. I can't use the modem, wvdial gives

should ext2 be formated to support 2.0 kernels?

Adam Di Carlo <[EMAIL PROTECTED]> wrote: > > On another topic: currently, the default ext2 partition formatting > > provides backward support for 2.0 kernels. Would anyone object if I > > change the default to 2.2 (and later) kernels? I noticed that the arm > > message (in utilities/dbootstrap/

Re: id -d invocation

Adam Di Carlo <[EMAIL PROTECTED]> wrote: > Oy. What provides ID on the root system? busybox I assume. We just > need to slap a big heavy bug on busybox (or whatever package provides > 'id' on the root filesystem) and move on. I am confused, what is `id -d' meant to do? -- Don't worry -- sh

Re: Extended floppy : summary

Thierry Laronde <[EMAIL PROTECTED]> wrote: > 1) Because these formats are unusual, the BIOS doesn't automagically > recognize them, and try to access them as normal 1.44 Mb floppies -> you > need a bootloader to manage the format, and dd'ing Linux can not work I might be wrong, but I do not think

Re: busybox vs modutils

Adam Di Carlo <[EMAIL PROTECTED]> wrote: > > Package: busybox > Version: 0.49pre-1 > Severity: wishlist > > busybox seems to include insmod, lsmod, and rmmod. However, there's > not really any point to using this in woody boot-floppies unless we > can also replace ksyms and modprobe as well, wh

Re: Call-for-help: modconf

Randolph Chung <[EMAIL PROTECTED]> wrote: > We need to rethink how we want modconf - aka a kernel modules > configuration utility - to work. As I see it, the biggest problem with > modconf is that there's no easy way to get the description of modules, > so we are left with a hack that is difficult

Bug#65606: Close the bug

Well I recommend closing the bug. What do the maintainer and submitter think? -- Don't worry -- shop. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]