Joe Auty wrote:
erstazi wrote:
On 06/01/2010 02:35 PM, Joe Auty wrote:
I came up with this set of instructions mostly for myself, but feel
free to correct anything that is mistaken here, pass them on, whatever:
http://www.netmusician.org/2010/06/compilevirtualboxose/
Instead of your current instructions you could just do:
cd VirtualBoxSources;
vi Config.kmk
Uncomment #VBOX_WITH_VNC = 1 to just VBOX_WITH_VNC = 1
save and close and then run:
dpkg-buildpackage -b -us -uc
dpkg -i virtualbox_packagename.deb
This would eliminate your whole process there and it automatically
modprobe's all the modules.
Interesting, I've never done that before...
What's with requiring java2-runtime and gsoap though? Is that normal?
# dpkg-buildpackage -b -us -uc
dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value:
-Wl,-Bsymbolic-functions
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package virtualbox-ose
dpkg-buildpackage: source version 3.2.0
dpkg-buildpackage: source changed by Oracle Corporation
<[email protected]>
dpkg-buildpackage: host architecture amd64
dpkg-checkbuilddeps: Unmet build dependencies: java2-runtime gsoap
dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied;
aborting.
dpkg-buildpackage: warning: (Use -d flag to override.)
#
Then
for
healthy concern, I wouldn't give /dev/vboxdrv read/write
access for the current user but instead do:
sudo usermod -G vboxusers -a `whoami`
Great! I've modified my instructions to include this...
I spoke to soon on this... It looks like more is needed here. By
default the permissions are:
$ ls -l /dev/vboxdrv
crw-rw---- 1 root root 10, 53 2010-06-02 00:20 /dev/vboxdrv
after adding myself to vboxusers:
$ grep vboxusers /etc/group
vboxusers:x:133:root,me
and then doing a:
chown root:vboxusers /dev/vboxdrv
I'm still getting the inaccessible errors... Plus, there must be a way
to change the default permissions of this module to something other
than root:root if we are to do this?
This
adds
the current user (non-root) to the vboxusers group which owns
vboxdrv and other things.
Another benefit of building the package is that the vbox devs provide
the debian build process and also, the binaries are in the correct
paths, not in out/linux.x86/release/bin but like in /usr/bin/, for
instance.
Just a thought.
I'd love to get your directions working, I'll play around with this
some more... The above questions demonstrate my lack of familiarity
with rolling my own deb files!
------------------------------------------------------------------------------
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
--
Joe Auty, NetMusician
 NetMusician
helps
musicians, bands and artists create beautiful,
professional, custom designed, career-essential websites that are easy
to maintain and to integrate with popular social networks.
www.netmusician.org
[email protected]
------------------------------------------------------------------------------
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
--
Joe Auty, NetMusician
 NetMusician
helps musicians, bands and artists create beautiful,
professional, custom designed, career-essential websites that are easy
to maintain and to integrate with popular social networks.
www.netmusician.org
[email protected]
|
------------------------------------------------------------------------------
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
