these error messages are harmless, but they are fixed in 1.4.
-tduffy
On Mon, 9 Oct 2000, Ken Murchison wrote:
> Just ran into another problem with ProPak 1.3 on my SGI 1400. I
> installed the security update containing the SGI_32 kernels. I'm trying
> to create the initrd images and run into this error:
>
> mkinitrd /boot/initrd-2.2.15-3SGI_32smp-bigmem.img
> 2.2.15-3SGI_32smp-bigmem
> cp: /dev/ram: No such file or directory
> cp: /dev/systty: No such file or directory
>
>
> I've compiled my own kernels and made initrd images before, but this is
> a new one for me. I'm guessing that this is some devfs weirdness. I've
> checked an SGI 1200 with ProPak 1.3 installed at the factory, and these
> device files are not there either (nor can I run mkinitrd). Another SGI
> 1200 running ProPak 1.2 DOES have both devices.
>
> What's up with this? Somehow the factory created the initrd images for
> the SGI_32 kernels, but not by following the README that comes with the
> security update.
>
> Thanks,
> Ken
>
|