On Thu, Jan 12, 2006 at 01:04:14AM +0100, Blaisorblade wrote: > recompile UML with make defconfig - you have a screwed config. Guess Unix > Domain sockets are disabled or modular, which is often not nice.
this is a debian package and we try to use the same config as for the debian kernel (and just recompile it for the arch=um). For consistency we would try to use the same config for both kernels. > > I mount this AFTER the modprobe process got dispatched. Later on > > modprobe finds the module and it works and the error goes away. > > It would be best to add the bind-mount command on the uml command > > line, somehow. Does anyone know how that could work? > > ln -s /usr/lib/uml/modules /lib/modules ? we would not want to fiddle with the host's filesystem if at all possible. uml (and rootstrap) should work more or less independently of the host setup. > > Alternatively one could try to set the enrivonment variable > > MODPROBE_OPTIONS, redirecting modprobe to /usr/lib/uml/modules. > > It is not clear to me what the variable should contain, though > > and it would have the same startup problem. Or can i specify > > environment vars on the uml commandline? > > Yep, like for normal kernel. VAR=value on the cmd line. > > They're passed to init, but some process (login ?) clears the env for its > child. Probably they are retained for init scripts, not sure however. this is very usefull, thanks. > > The second problem with devfs seems trickier. devfs used to > > clobber /dev and a /dev/ubd/disc1 was garanteed to be present > > (and used with mkfs and mount later on). If rootstrap uses the > > host's /dev it can not rely on /dev/ubdX to be present, since > > those devices are non-standard. > Host means "physical machine" - it's not expected to have /dev/ubd* or such. > You maybe talk about the guest (UML machine)? since the guest uses the host's filesystem initially it ends up looking at the same /dev/ directory as the host, too, and would find the /dev/ubdX devices there that it needs. > > such a oops looks like this: > > This is not an oops. what is it? > > what exactly does this mean? how can i fix it? > To my knowledge (seeing one other user getting it, the CC'ed Rob Landley) > ignore it since _this_ doesn't give any problem it gives me one of there for each ending (or starting?) process. so i get TONS of them and it makes my output useless. i cant ignore them. > > since udev is a fat userspace program with lots of config etc i > > dont expect using it will fix the problem. or would it? if so, > > how? > > Just use it (on the guest) - it gets all its data from the kernel, and it > would auto-create /dev/ubda and such (for defined drives) in the guest. i tried that, it is not so trivial. i will look into it some more. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
