Stan Goodman wrote:
At 11:53:49 on Tuesday Tuesday 16 March 2010, Joachim Schrod <jschrod@acm.org> wrote:
This will never work; since there is no package with the same name as the RPM. As others have posted, the correct command to remove VirtualBox is
rpm -e VirtualBox-3.1
That produced the reponse: # rpm -e VirtualBox-3.1 insserv: script lpd: service cupsd already provided! insserv: script portmap: service portmap already provided!
That's more or less OK; at this time VirtualBox got removed. Those two warnings are unrelated to VMware and rpm. They tell that you have two package implementations of the same service installed. If you want to get rid of them: you can find the culprit by grep 'Provides.*cupsd' /etc/init.d/* which should list (at least) two files. You can use rpm -qf to find out the package(s) for these files and deinstall the one that you don't need. Ditto for portmap. (For printing, use cups and remove the other. For portmap, use rpcbind and remove the other.)
# rpm -U VirtualBox-3.1* warning: VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae
Creating group 'vboxusers'. VM users must be member of that group!
insserv: script lpd: service cupsd already provided! insserv: script portmap: service portmap already provided! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Success!
WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko: No such file or directory WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko: No such file or directory
# find -name "vbox*.ko" ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxdrv.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxdrv.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko
So the "missing" files are indeed present. Why does VB think otherwise?
Normally entries in weak-updates/ are symlinks to some updates/ directory of an older kernel. Therefore I would check if /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko is a symlink and where it points to. From the list above, I suppose it should point to /lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.o. Furthermore, I would check /var/log/vbox-install.log for any error messages, or to discover where the newly build kernel modules were placed. That said, you should note that I don't know VirtualBox and have never used it. I'm knowledgable about rpm and hoped to help you with your problems there -- for actual VirtualBox problems I have to refer to other pundits. Best, Joachim PS: No need to send a copy of your replies to me personally. I'll read and answer on the list, if necessary and appropriate. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 21:19:58 on Tuesday Tuesday 16 March 2010, Joachim Schrod <jschrod@acm.org> wrote:
Stan Goodman wrote:
At 11:53:49 on Tuesday Tuesday 16 March 2010, Joachim Schrod
<jschrod@acm.org> wrote:
This will never work; since there is no package with the same name as the RPM. As others have posted, the correct command to remove VirtualBox is
rpm -e VirtualBox-3.1
That produced the reponse: # rpm -e VirtualBox-3.1 insserv: script lpd: service cupsd already provided! insserv: script portmap: service portmap already provided!
That's more or less OK; at this time VirtualBox got removed.
Those two warnings are unrelated to VMware and rpm. They tell that you have two package implementations of the same service installed. If you want to get rid of them: you can find the culprit by
grep 'Provides.*cupsd' /etc/init.d/*
which should list (at least) two files. You can use rpm -qf to find out the package(s) for these files and deinstall the one that you don't need. Ditto for portmap. (For printing, use cups and remove the other. For portmap, use rpcbind and remove the other.)
~> grep 'Provides *cupsd' /etc/init.d/* grep: /etc/init.d/spamd: Permission denied stan@poblano:~> su Password: # grep 'Provides.*cupsd' /etc/init.d/* # which doesn't look like what was expected. For what it's worth, the system has been rebooted since receipt of your note.
# rpm -U VirtualBox-3.1* warning: VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae
Creating group 'vboxusers'. VM users must be member of that group!
insserv: script lpd: service cupsd already provided! insserv: script portmap: service portmap already provided! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Success!
WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko: No such file or directory WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko: No such file or directory
# find -name "vbox*.ko" ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxdrv.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxdrv.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko
So the "missing" files are indeed present. Why does VB think otherwise?
Normally entries in weak-updates/ are symlinks to some updates/ directory of an older kernel. Therefore I would check if /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko is a symlink and where it points to. From the list above, I suppose it should point to /lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.o.
# dir /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko lrwxrwxrwx 1 root root 53 2010-03-03 15:24 /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko # As you said.
Furthermore, I would check /var/log/vbox-install.log for any error messages, or to discover where the newly build kernel modules were placed.
I have done that and see no error or warning messages in the log, other than the two warnings that we have already seen. I do not see references to directories that belong to other kernel versions. I understand that I should now insert correct links for the two "missing" files instead of the mistaken ones. I'll report (briefly, I hope) after I have done that.
That said, you should note that I don't know VirtualBox and have never used it. I'm knowledgable about rpm and hoped to help you with your problems there -- for actual VirtualBox problems I have to refer to other pundits.
Best, Joachim
PS: No need to send a copy of your replies to me personally. I'll read and answer on the list, if necessary and appropriate.
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany
-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
At 13:36:05 on Wednesday Wednesday 17 March 2010, Stan Goodman <stan.goodman@hashkedim.com> wrote:
At 21:19:58 on Tuesday Tuesday 16 March 2010, Joachim Schrod
<jschrod@acm.org> wrote:
Stan Goodman wrote:
At 11:53:49 on Tuesday Tuesday 16 March 2010, Joachim Schrod
<jschrod@acm.org> wrote:
This will never work; since there is no package with the same name as the RPM. As others have posted, the correct command to remove VirtualBox is
rpm -e VirtualBox-3.1
That produced the reponse: # rpm -e VirtualBox-3.1 insserv: script lpd: service cupsd already provided! insserv: script portmap: service portmap already provided!
That's more or less OK; at this time VirtualBox got removed.
Those two warnings are unrelated to VMware and rpm. They tell that you have two package implementations of the same service installed. If you want to get rid of them: you can find the culprit by
grep 'Provides.*cupsd' /etc/init.d/*
which should list (at least) two files. You can use rpm -qf to find out the package(s) for these files and deinstall the one that you don't need. Ditto for portmap. (For printing, use cups and remove the other. For portmap, use rpcbind and remove the other.)
~> grep 'Provides *cupsd' /etc/init.d/* grep: /etc/init.d/spamd: Permission denied stan@poblano:~> su Password: # grep 'Provides.*cupsd' /etc/init.d/* #
which doesn't look like what was expected. For what it's worth, the system has been rebooted since receipt of your note.
# rpm -U VirtualBox-3.1* warning: VirtualBox-3.1-3.1.4_57640_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae
Creating group 'vboxusers'. VM users must be member of that group!
insserv: script lpd: service cupsd already provided! insserv: script portmap: service portmap already provided! No precompiled module for this kernel found -- trying to build one. Messages emitted during module compilation will be logged to /var/log/vbox-install.log.
Success!
WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko: No such file or directory WARNING: Can't read module /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko: No such file or directory
# find -name "vbox*.ko" ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.45-0.1-default/misc/vboxdrv.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-default/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-trace/misc/vboxdrv.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetadp.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxnetflt.ko ./lib/modules/2.6.27.39-0.2-debug/misc/vboxdrv.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxvfs.ko ./lib/modules/2.6.27.45-0.1-trace/weak-updates/updates/vboxadd.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.ko ./lib/modules/2.6.27.42-0.1-trace/updates/vboxadd.ko
So the "missing" files are indeed present. Why does VB think otherwise?
Normally entries in weak-updates/ are symlinks to some updates/ directory of an older kernel. Therefore I would check if /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko is a symlink and where it points to. From the list above, I suppose it should point to /lib/modules/2.6.27.42-0.1-trace/updates/vboxvfs.o.
# dir /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko lrwxrwxrwx 1 root root 53 2010-03-03 15:24 /lib/modules/2.6.27.45-0.1-default/weak-updates/updates/vboxvfs.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko #
As you said.
Furthermore, I would check /var/log/vbox-install.log for any error messages, or to discover where the newly build kernel modules were placed.
I have done that and see no error or warning messages in the log, other than the two warnings that we have already seen. I do not see references to directories that belong to other kernel versions.
I understand that I should now insert correct links for the two "missing" files instead of the mistaken ones. I'll report (briefly, I hope) after I have done that.
I'm back; sorry I had to take a couple of days off to deal with other matters. In a nutshell, the problem has been reduced to redirecting the two symlinks to kernel modules of the proper version. At present, they are as follows: vboxvfs.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxvfs.ko vboxadd.ko -> /lib/modules/2.6.27.42-0.1-default/updates/vboxadd.ko whereas they should be instead ~vboxvfs.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko ~vboxadd.ko -> /lib/modules/2.6.27.45-0.1-default/updates/vboxadd.ko and I should do (from the directory containing the links: ln -sf vboxvfs /lib/modules/2.6.27.45-0.1-default/updates/vboxvfs.ko ln -sf vboxadd /lib/modules/2.6.27.45-0.1-default/updates/vboxadd But the two target files do not exist, s can't do that. If it is true that the files are kernel-dependent, they are not likely to be in the rpm from which I installed. How am I to make these files? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Joachim Schrod -
Stan Goodman