David, On Saturday 20 October 2007, David Baron wrote: > 1. Noticed that the installation is looking for udev stuff. I do not use > udev so it does not find it. Installation proceeds without it.
And there should be no further problem at all if udev was not found. The udev rule is just there to ensure the correct permissions of /dev/vboxdrv. If udev is not used, /etc/init.d/vboxdrv does the job of changing the permissions. > Seems that a lot of things look for either a udev subdirectory to place > their rules (useful if udev is used) or some command to get such > information. Several packages have placed udev as a dependency because of > this and now I cannot upgrade them. > One can live quite well without udev and good old hotplug does its job just > fine. Maybe udev is great (many post about problems, however), but if it > not be really needed, then please do not make it a dependency in future > upgrades. Installation scripts can get around the presence or absence of > udev in a correct and friendly manner. I made the directory to get around > such an installation problem. Harmless enough. I still do not understand the problem. Did the installation script fail on your distribution? BTW: What distribution are you using? > 2. Noticed that a "host networking" is "stopped" and then successfully > started by the installation. New feature? Usage? Do you mean the /etc/init.d/vboxnet script? Kind regards, Frank -- Dr.-Ing. Frank Mehnert innotek GmbH, http://www.innotek.de
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
