rule-list
[Top][All Lists]
Advanced

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

Re: [RULE] Re: State of the RULE and Slinky-Files wanted


From: C David Rigby
Subject: Re: [RULE] Re: State of the RULE and Slinky-Files wanted
Date: 25 Aug 2003 15:34:07 +0200

On Mon, 2003-08-25 at 14:33, Michael Fratoni wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Monday 25 August 2003 06:20 am, C David Rigby wrote:
> > Michael,
> >     I had a problem with slinky-v0.3.97.img for which I found a
> > work-around.  Please let me know if I did something goofy that caused
> > the problem in the first place.  Note that I have not done the obvious
> > stuff like downloading the tarball again!
> 
> >     I unpacked the tarball and created the boot disk in the usual fashion
> > with dd (all files & directories relative to the slinky_devel
> > directory):
> >
> >     as root:
> >     ./makedisk.sh
> >     not root:
> >     dd if=slinky-v0.3.97/slinky-v0.3.97.img of=/dev/fd0
> >
> >     When I booted the system (the computer named runaway in the testing
> > farm) with this disk, after the RAMDISK was loaded, I got an error
> > message to the effect that the system "could not open initial console."
> >
> >     It turned out that the problem was that there was no /dev/console in
> > the root filesystem in the disk image.  The quick workaround was to
> > simply copy the /dev/* directory structure from slinky-v0.3.96.img to
> > slinky-v0.3.97.  After that, the system booted fine.  Details of the
> > workaround are shown below.
> 
> Did you unpack the tar archive as root? The /dev/ files are there, but 
> normal users can't create device files.
> 

Oops!  That would certainly qualify as "the goofy thing I did."  When I
unpack the archive as root, all of the dev files are there.

Thanks
C David Rigby






reply via email to

[Prev in Thread] Current Thread [Next in Thread]