At 13:36:04 on Saturday Saturday 15 May 2010, "Carlos E. R." wrote:

On Saturday, 2010-05-15 at 13:17 +0300, Stan Goodman wrote:

...

The answer to that seemed to be to uninstall it and install afresh, but instead I was told that there was nothing to uninstall. So it both is and isn't.

How to recover from this?

Paste the exact command and response you use and get.

Guess: check the case of letters.

The case of letters didn't play a part. I went to the directory with the rpm, which contained only that single file, did "dir", and pasted the name of the file into the command "rpm -Uvh <filename>". I always do that when long filenames are involved, in order to prevent errors.

-- Cheers, Carlos E. R.

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 19:19:01 on Saturday Saturday 15 May 2010, Tejas Guruswamy wrote:

On 15/05/10 16:12, Stan Goodman wrote:

...

The case of letters didn't play a part. I went to the directory with the rpm, which contained only that single file, did "dir", and pasted the name of the file into the command "rpm -Uvh <filename>". I always do that when long filenames are involved, in order to prevent errors.

You are intentionally using "dir"? That's meant for newbies trying to break msdos habits, it's just an alias for the real command, "ls". Try using that instead, it will be more flexible.

I know about ls. I know the difference between the two. "dir" is what comes to mind when it doesn't make any difference. I regret the discomfort if this discloses lack of rogor.

But anyway what I really wanted to say is that there is no need to go through this filename copying process with TAB-completion in modern shells. If you don't know what this is, just type the first few letters of a filename, press TAB, and the rest of the filename appears, guaranteed to be in a format that the shell understands.

Different strokes for different folks.

If you are finding yourself doing repetitive typing (or even copy-pasting) in a Linux shell, you're probably doing it wrong!

I'm sure you're right.

Regards, Tejas

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2010-05-15 at 18:12 +0300, Stan Goodman wrote:

At 13:36:04 on Saturday Saturday 15 May 2010, "Carlos E. R." <> wrote:

...

Paste the exact command and response you use and get.

Guess: check the case of letters.

The case of letters didn't play a part. I went to the directory with the rpm, which contained only that single file, did "dir", and pasted the name of the file into the command "rpm -Uvh <filename>". I always do that when long filenames are involved, in order to prevent errors.

That will succeed for install and fail for remove - as you got. You are pasting the full filename, version part included, and probably the extension... As I said, I need the exact command and results you used and got to be sure >:-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkvvQkgACgkQtTMYHG2NR9UAJwCeLKhzEu/rN/WSSQfPknlo8sT7 EjEAoJBCV2Q9hiIUdKmmT0zgRNWC8m6Q =B+r9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Recompiling VirtualBox kernel module failed  (Look at /var/log/vbox-install.log to find out what went wrong) # vi /var/log/vbox-install.log

***** /usr/share/virtualbox/src/vboxdrv/build_in_tmp: line 95: make: command not found *****

hmmm... it seems you lack some package. Install "Kdevelop" as it has all necessary packages. + "Linux kernel development" section from Yast.

# rpm -Uvh VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm warning: VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae Preparing...                ########################################### [100%]        package VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64 is already installed # rpm -e VirtualBox error: package VirtualBox is not installed #

Use: # rpm -e VirtualBox-3.1 I wrote (old) documentation for VirtualBox on openSUSE: (16.5.2010) http://chorgan.provo.novell.com/lfl/.html/virtualbox.html It corresponds to VirtualBox-1.3 + openSUSE 10.2/10.3 -- -Alexey Eromenko "Technologov" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 12:39:51 on Sunday Sunday 16 May 2010, Tejas Guruswamy wrote:

On 16/05/10 09:31, Alexey Eremenko wrote:

...

...

Recompiling VirtualBox kernel module failed (Look at /var/log/vbox-install.log to find out what went wrong) # vi /var/log/vbox-install.log

***** /usr/share/virtualbox/src/vboxdrv/build_in_tmp: line 95: make: command not found *****

hmmm... it seems you lack some package.

Install "Kdevelop" as it has all necessary packages. + "Linux kernel development" section from Yast.

Kdevelop? That's massive overkill, just install make. (Like it tells you to!)

zypper in make gcc kernel-source

is all that is needed to install the VirtualBox kernel drivers.

Regards, Tejas

make was all it took. I couldn't believe that gcc etc. would have been installed without installing make as well. Thanks. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, 2010-05-17 at 10:09 -0500, Regis Matejcik wrote:

...

make was all it took. I couldn't believe that gcc etc. would have been installed without installing make as well. Thanks.

-- Stan Goodman Qiryat Tiv'on Israel

Ya know, this is a good point. Just out of curiosity, does the default install of gcc not include make?

which brings the question, of what use is a compiler that doesn't have make?

They are separate packages. There is more than one variant on gnu make. And other make-like systems that can replace make, calling gcc as needed. In addition, make need not run gcc. I use make to build documentation and packages and even run Windows apps. So, make and gcc often work together. But that is only one use. For that reason, they are separate. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, 16 May, 2010 at 10:31:53 +0200, Alexey Eremenko wrote:

...

Recompiling VirtualBox kernel module failed  (Look at /var/log/vbox-install.log to find out what went wrong) # vi /var/log/vbox-install.log

***** /usr/share/virtualbox/src/vboxdrv/build_in_tmp: line 95: make: command not found *****

hmmm... it seems you lack some package.

Install "Kdevelop" as it has all necessary packages. + "Linux kernel development" section from Yast.

While installing 'Kdevelop' would pull in the needed tools, it might also pull in stuff that's neither needed nor wanted. I'd take the 'minimalist' route: make: commnad not found running 'cnf make' should come up with the name of the package that has 'make', in this case 'make'. so: zypper install make try starting the app again, and if something else is missing; cnf next-missing-item zypper install 'name of package as provided by cnf' lather, rinse, repeat

...

# rpm -Uvh VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm warning: VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae Preparing...                ########################################### [100%]        package VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64 is already installed # rpm -e VirtualBox error: package VirtualBox is not installed #

Use: # rpm -e VirtualBox-3.1

Yeah, sometimes it's not immediately apparent where the package 'name' ends, and where the 'version' begins... (although there are rules) It is possible to have rpm only print the 'package name' (without the version info) - but unless one is already familiar with how to do that, I think the quickest way is to: Find the binary: jon@nx8220:~> which VirtualBox /usr/bin/VirtualBox Find the 'name+version' of the package that 'owns' the binary: jon@nx8220:~> rpm -qf /usr/bin/VirtualBox virtualbox-ose-3.0.6-9.11.2.i586 jon@nx8220:~> rpm -qi virtualbox-ose-3.0.6-9.11.2.i586 | grep Name Name : virtualbox-ose Relocations: (not relocatable) So if I wanted to remove this, the command would be: rpm -e virtualbox-ose /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Sun, 16 May, 2010 at 07:58:50 -0400, Ken Schneider - openSUSE wrote:

On 05/16/2010 05:53 AM, Jon Clausen pecked at the keyboard and wrote:

...

On Sun, 16 May, 2010 at 10:31:53 +0200, Alexey Eremenko wrote:

...

...

...

# rpm -e VirtualBox error: package VirtualBox is not installed #

Use: # rpm -e VirtualBox-3.1

Yeah, sometimes it's not immediately apparent where the package 'name' ends, and where the 'version' begins... (although there are rules)

...

jon@nx8220:~> rpm -qi virtualbox-ose-3.0.6-9.11.2.i586 | grep Name Name : virtualbox-ose Relocations: (not relocatable)

So if I wanted to remove this, the command would be:

rpm -e virtualbox-ose

/jon

Or simply:

rpm -qa|grep -i virtu

will produce the name of the package to remove.

Hmmm... yeah, I guess you're right... The point of the excercise was 'how to get the <name> only of the package', with no abiguity, even if <name> includes dashes, number and dots - as in the case of VirtualBox-3.1 above. I could have sworn that 'rpm -e' wouldn't accept the complete <name>-<version>-<arch> - but apparantly I am wrong about that (I just tested to be sure)... ...I wonder where I got that idea from... But 'rpm -qf $(which <command>)' is still valid. Quicker and less ambiguos than 'rpm -qa | grep <something>'... /jon -- YMMV -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 21:48:46 on Sunday Sunday 16 May 2010, "Carlos E. R." wrote:

On 2010-05-16 11:53, Jon Clausen wrote:

...

On Sun, 16 May, 2010 at 10:31:53 +0200, Alexey Eremenko wrote:

cnf next-missing-item zypper install 'name of package as provided by cnf'

lather, rinse, repeat

«Did you hear about the programmer they found dead in his shower? He was clutching an shampoo bottle with the instructions "Lather. Rinse. Repeat."»

...

...

Use: # rpm -e VirtualBox-3.1

Yeah, sometimes it's not immediately apparent where the package 'name' ends, and where the 'version' begins... (although there are rules)

Yep, that's why I asked the OP about the command used.

And he sent it yesterday. --

Cheers / Saludos,

Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Minas Tirith))

-- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 05/15/2010 09:21 AM, Mark Goldstein pecked at the keyboard and wrote:

Stan,

On Sat, May 15, 2010 at 1:17 PM, Stan Goodman wrote:

...

The package is: VirtualBox-3.1-3.1.8_6139_openSUSE111-1.x86_64.rpm. According to the VB download page this is suitable for both oS 11.1 and 11.2. The system is 11.2.

Installing VirtualBox is very easy, I have done it several times. This time, however, I failed to install the kernel sources first.

I installed the sources after being reminded by the installation, and tried again, only to be told that VirtualBox is already installed.

The answer to that seemed to be to uninstall it and install afresh, but instead I was told that there was nothing to uninstall. So it both is and isn't.

How to recover from this?

Probably there is a way to cleanup the database, but I would try downloading the package VirtualBox-3.1-3.1.8_6139_openSUSE111-1.x86_64.rpm from repository and then installing it locally with rpm -i --force. I guess, this will override the partial info in the package db.

The better way would be to use -u --oldpackage instead of --force. --force should only be used as an absolutely last ditch effort. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 17:41:31 on Saturday Saturday 15 May 2010, "Ken Schneider - openSUSE" wrote:

On 05/15/2010 09:21 AM, Mark Goldstein pecked at the keyboard and wrote:

...

Stan,

On Sat, May 15, 2010 at 1:17 PM, Stan Goodman

wrote:

...

The package is: VirtualBox-3.1-3.1.8_6139_openSUSE111-1.x86_64.rpm. According to the VB download page this is suitable for both oS 11.1 and 11.2. The system is 11.2.

Installing VirtualBox is very easy, I have done it several times. This time, however, I failed to install the kernel sources first.

I installed the sources after being reminded by the installation, and tried again, only to be told that VirtualBox is already installed.

The answer to that seemed to be to uninstall it and install afresh, but instead I was told that there was nothing to uninstall. So it both is and isn't.

How to recover from this?

Probably there is a way to cleanup the database, but I would try downloading the package VirtualBox-3.1-3.1.8_6139_openSUSE111-1.x86_64.rpm from repository and then installing it locally with rpm -i --force. I guess, this will override the partial info in the package db.

The better way would be to use -u --oldpackage instead of --force.

# rpm -u --oldpackage VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm -u: unknown option # rpm -U --oldpackage VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm warning: VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 6dfbcbae package VirtualBox-3.1-3.1.8_61349_openSUSE111-1.x86_64 is already installed # I tried again to load VB, so that I could report the response, and received a different reaction from previously. It seems that there is a kernal-source mismatch. I says that it the currently installed kernel is: 2.6.31.12-0.2-desktop, while the kernel-source file that I installed yesterday is 2.6.31.12-0.2.1 (no "desktop"). So apparently the kernel has not been updated. I have now installed the updated kernel, rebooted, and run . This failed, and directed me to the log at /var/log/vbox-install.log. This tells me that: /usr/share/virtualbox/src/vboxdrv/build_in_tmp: line 95: make: command not found ??? -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

At 23:48:14 on Saturday Saturday 15 May 2010, "Rajko M." wrote:

On Saturday 15 May 2010 15:23:01 Stan Goodman wrote: ...

...

/usr/share/virtualbox/src/vboxdrv/build_in_tmp: line 95: make: command not found

Install basic development pattern, and that will install all that is needed to compile kernel module.

-- Regards Rajko,

In two days of searching, I have been unable to find how to install a pattern, where to fine the basic development pattern, or what packages are contained in this specific pattern. Packages installed on this system are: cpp44 gcc gcc44 libgcc44 libgcc-32bit I suppose that, if these were installed from the DVD, it is likely that any other packages needed for compiling the kernel would also have been installed. But if something essential is missing, I would like to make up the lack -- if I knew what it was. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org