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

[Michael Fratoni]

-----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.

As a normal user, here is what you'll see:
slinky_devel/filesystem/dev/console
tar: slinky_devel/filesystem/dev/console: Cannot mknod: Operation not 
permitted

As a result, the slinky_devel/filesystem/dev/ directory will be nearly 
empty.

Please let me know if that helps,
- -- 
- -Michael

pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0|9 in 8M of RAM: http://www.rule-project.org/en/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/SgIZn/07WoAb/SsRAibAAJ43//qZXA0SOBISNfDfDV7+GkQj8gCghsN8
2ytIZA/NDJpoNrseI8UnZWk=
=mjz7
-----END PGP SIGNATURE-----