Bug#94435: possible explanation
On Fri, Jun 29, 2001 at 09:00:44AM -0700, email@example.com wrote:
> On Fri, Jun 29, 2001 at 08:54:51AM -0600, Matt Kraai wrote:
> > I believe that the problem is caused by the root filesystem
> > already being mounted on /dev/ram. Could you please try
> > installing to an NFS root again and, after booting, switch to tty2
> > and run `mount' to print the current mountpoints. If this shows
> > /dev/ram to already be in use, then we'll need to either (a) use a
> > different /dev/ram device when copying this image over or (b)
> > change m68k (and possibly other architectures as well) to use
> > /dev/ram0 for its root device.
> I'll have to wait until I get another m68k machine to test on, alas.
> My Quadra 605 decided to burn out not too long after submitting this
> bug. Appears to need a new hard drive and new CPU.
OK, further investigation indicates that this probably isn't the
problem anyway. As a kernel parameter, it appears that /dev/ram
is equivalent to /dev/ram0, whereas the /dev/ram device is
equivalent to /dev/ram1. Argh.