Joep L. Blom wrote:
Rance Hall wrote:
On Thu, Aug 27, 2009 at 10:02 AM, Joep L. Blom<[email protected]>
wrote:
I haven't seen the last few years BIOS's that didn't support USB
booting. I
use VMbox under Linux and yes I still have problems with permissions
and I
know I' not the only one.
If anybody could give me all the directories for ehich the
permissions have
to be right I would solve it in no time.
Joep
Joep:
I have seen a number of BIOSes that say they support usb booting but
in fact do not, they support some subset of usb booting.
like maybe only support usb-fdd and not usb-hdd
And according to H. Peter Anvin (author of isolinux, etc) There is a
wide variety of BIOS implementations out there when it comes to usb
boot support, and the inconsistency has caused the syslinux project
NOT to pursue usb booting officially yet (maybe ever)
I believe the same BIOS variety would impact vbox as well. They of
course write their own bios, but that makes vbox not as useful as a
testbed/dev platform when you know that what you can do in vbox you
cant do on any given real box.
As to your question about permissions on ubuntu
check into your udev configuration file. udev creates the device
nodes for usb devices as they are detected and udev can be configured
to make those device nodes with specified permissions so that they can
then be used by any given user/group.
I suggest you start there.
vbox on linux must run as the user that started vbox and with group
privs assigned to the vbox group.
fix udev to make new usb device nodes with at least read/write
user:group permissions, and owned by root:vbox
and that should fix your device permission problem.
HTH
Rance
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
Rance, Thanks a lot!
I will do as you suggests an start looking at the udev configuration. I
never thought of that.
With respect to BIOS and USB boot possibilities, I must confess I only
have experience with MSI and ASUS MB's which come resp. with AWARD and
AMI BIOS's and both give no problem (I have used it on a5 year old MSI
board). I have no idea what other motherboard manufacturers put in their
products.
But thanks again. I will report the results here.
Joep
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
Rance,
I followed your advice and looked into the udev files.
the udev.conf file only contains the standard errorlog definition.
The rules file for vbox is the following:
_______________________________________________________
KERNEL=="vboxdrv", NAME="vboxdrv", OWNER="root", GROUP="root", MODE="0600"
SUBSYSTEM=="usb_device", GROUP="vboxusers", MODE="0664"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GROUP="vboxusers", MODE="0664"
______________________________________________________________________
Which is equal to the settings in my hardy box where the USB-ports are
seen. I therefore think changing permissions would not help.
However, I know of another problem with serial ports. After booting your
system, the /dev/ttyS* ports have a permission of 0600. When you have a
process in user space no signal is received as the permissions are
wrong. You have to set the permissions to at least 0666 to get the
device available for the process that want to use it.
Is it possible the same problem is here the culprit. The problem is that
there are many devices in the /dev/ directory as /dev/usbdev* and
/dev/usbmon0 to /dev/usbmon4. The former are many and I don't know how
they are related to the physical ports.
You have any suggestions?
Joep
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
