On Mon, Oct 30, 2000 at 12:22:35PM +0200, Shaul Karl wrote: > [12:19:02 /tmp]$ dpkg -S /initrd/ > dpkg: /initrd/ not found. > [12:20:09 /tmp]$ locate initrd > /dev/initrd > /initrd > /usr/local/src/linux/kernel-source-2.2.17/arch/mips/boot/addinitrd.c > /usr/local/src/linux/kernel-source-2.2.17/arch/ppc/chrpboot/no_initrd.c > /usr/local/src/linux/kernel-source-2.2.17/arch/ppc/coffboot/no_initrd.c > /usr/local/src/linux/kernel-source-2.2.17/Documentation/initrd.txt > /usr/share/doc/kernel-doc-2.2.17/Documentation/initrd.txt.gz > /usr/share/man/man4/initrd.4.gz > [12:20:15 /tmp]$ zcat > /usr/share/doc/kernel-doc-2.2.17/Documentation/initrd.txt > .gz | head > Using the initial RAM disk (initrd) > =================================== > > Written 1996 by Werner Almesberger <[EMAIL PROTECTED]> and > Hans Lermen <[EMAIL PROTECTED]> > > > initrd adds the capability to load a RAM disk by the boot loader. This > RAM disk can then be mounted as the root file system and programs can be > run from it. Afterwards, a new root file system can be mounted from a > [12:20:28 /tmp]$ > > > > BTW: Is it a bug that dpkg -S can not locate the owner of the /initrd dir?
i wouldn't think so -- % dpkg -S /initrd dpkg: /initrd not found. % dpkg -S initrd manpages: /usr/share/man/man4/initrd.4.gz kernel-headers-2.2.17: /usr/src/kernel-headers-2.2.17/include/config/blk/dev/initrd.h isapnptools: /usr/share/doc/isapnptools/README.initrd the slash is not part of the filename pattern that dpkg -S searches for. -- self-reference, n: see self-reference. [EMAIL PROTECTED] *** http://www.dontUthink.com/
