On Sun, 2012-07-29 at 00:46 +0300, Veli-Pekka Kestilä wrote:
> On 28.7.2012 18:39, Aaron Konstam wrote:
> > On Sat, 2012-07-28 at 15:50 +0300, Veli-Pekka Kestilä wrote:
> >> On 28.7.2012 15:07, Patrick Dupre wrote:
> >>> So, I mounted the defectuous installation, and I did a chroot to it.
> >>> It works except that I have an error message:
> >>> so such file or directory : /dev/urandom
> >> If you really need some device nodes in chroot environment you can run
> >> after chroot, "MAKEDEV /dev/urandom" it should just create the device
> >> (presuming the defective installation does still have MAKEDEV command in
> >> sbin)
> >> -vpk
> > I thought of MAKEDEV but does not seem to exist anymore on the system.
> [root@localhost ~]# rpm -qf /sbin/MAKEDEV
> Atleast it seems to in the f17 system I have set up for doing some
> virtualisation testing. Granted it wasn't in the default installation
> and I had to install it manually. But you could have found this yourself
> by just doing yum search makedev.
You are correct but what is confusing is that makedev is on the system
even though MAKEDEV was not.
Athena Desktop Environment! In your hearts, you *know* it's the right
* Knghtbrd THWAPS xtifr
Aaron Konstam telephone: (210) 656-0355 e-mail: email@example.com
users mailing list
To unsubscribe or change subscription options:
Have a question? Ask away: http://ask.fedoraproject.org