virtualbox.org

Effective with the 3.2 release, you have discontinued a separate RPM for PCLinuxOS 2007 (which was compatible with the new 2010 release as well). Do you have any guidance on which other package would be best suited for PCLinuxOS? This problem resolved.

HOWEVER

New problem; no working USB on the non-OSE release of 3.2.0 on PCLinuxOS 2010.

Please provide a PCLinuxOS package. We are a very popular distribution and actively promote Virtualbox on our forums.

Texstar

Please provide a PCLinuxOS package. We are a very popular distribution and actively promote Virtualbox on our forums.

Texstar

I also ask that you please support a PCLinuxOS package. Thank you for your consideration.

-nixer-

nixer wrote:

Please provide a PCLinuxOS package. We are a very popular distribution and actively promote Virtualbox on our forums.

Texstar

I also ask that you please support a PCLinuxOS package. Thank you for your consideration.

-nixer-

I use PCLinuxOS as well and depend on VirtualBox for my business. I also would appreciate an .rpm for PCLinuxOS.

Thanks,
MCP

I agree with other post. Please give direct support to pclinus 2010

Thanks

I am a PCLOS 2010 user, and I am disappointed that the support for PCLinuxOS has not yet appeared.

As Texstar indicated, PCLinuxOS is a very popular distribution, and this oversight by the Virtualbox team is not a step in the right direction.

Please, continue to provide support for PCLinuxOS, and create a release for US....

Thanks...

DarwinX

alanbcohen wrote:Effective with the 3.2 release, you have discontinued a separate RPM for PCLinuxOS 2007 (which was compatible with the new 2010 release as well). Do you have any guidance on which other package would be best suited for PCLinuxOS?

It has been three days since my original post and no one has guidance on my question? I am disappointed.

Have you guys tried the "All distributions" run file release on the download page.
Download it to a directory, open a terminal, cd to that directory, and to install (assuming you don't have any other .run files in that directory) type:
sudo sh *.run

I have tried the 'all distributions' version of the 3.2.0 release unsuccessfully on a new install of PCLinuxOS 2010.1 (and all updates performed).
I get no results from selecting the 'Oracle VM VirtualBox' from the menus. When I tried to run it from the console, the old console command 'virtualbox' was not found. After browsing my /usr/bin directory, I found a 'VirtualBox' command and tried that from the concole with the following results:

[alanbcohen@localhost ~]$ virtualbox
bash: virtualbox: command not found
[alanbcohen@localhost ~]$ VirtualBox
VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory "/opt/VirtualBox/components": group and/or other writable (st_mode=040775)

I am very frustrated at the lack of response from this community on my original request.

User added to group vboxusers?

And please uninstall before all old versions.

And try "chmod 755 /opt/VirtualBox/components".

It appears Stefan had the answer; the new run script does not set the vboxusers group and left incorrect chmod values. I've reset both per his recommendations and I've been able to display the VM application and start one VM. Unfortunately, I have a second problem, almost as serious:
NO USB connections in 3.2.0

I think this a the Problem with sysfs.

Sometimes the VBOX Standard method fails. In this case its possible to setup USBFS. Look into the FAQ and the Manual, there are some examples for this. Sorry, but there is no Standard. I. E. for Suse 11.0 to 11.2 there were 3 approaches to do this.

The wrong group/user can only be the result of a wrong umask setting. The .run installer is not new but the fallback installer for every other Linux distribution next to the most relevant distributions (Fedora, Ubuntu, openSUSE). The download statistics show that only a few users actually downloaded the PCLinuxOS package and we cannot provide packages for every Linux distribution, there has to be a break somewhere.

So far we have very few complaints regarding the .run packages so these packages must actually work for someone. And no, it was always VirtualBox in the PUEL package, not virtualbox (AFAIR some OSE packages contains binaries named virtualbox.

Regarding your USB problem: The first step is to do
If all USB devices are unavailable that probably means that the permissions of the files (see the Address: line) are incorrect. Check the permissions of these files. And yes, for USB it is essential to be in the vboxusers group because there is an udev rule which makes all USB devices accessible for users in that group. Check by doing /bin/ls -l on these files.

alanbcohen wrote:It has been three days since my original post and no one has guidance on my question? I am disappointed.

Note that support in this forum is for FREE and on a best-effort basis. So you cannot expect a deadline for answering your questions. And such a forum does only work if users help each others. I didn't see any post from you where you was helping other users.