Hi,
I've made mysqlf a RPM and installed it.
After that i did what i shouldn' do: remove the files it installed.
Now, i wnat to install it agai and i can't.
Already rebuilt the rpm database ( rpm -vv --rebuilddb), used --force, --replacepkgs, --replacefiles, --justdb, --erase, --initdb, but no good.
Been at rpm.org, but found nothing that i already know.
Any help would be appreciated.
Warm regards, Mário Gamito
Mario,
First delete the rpm you installed with "rpm -e --force <rpmname>". That should do it. If not report back the error it gives when executing that command. Then you can install the rpm again.
Regards, Tim
On 3/3/07, Mário Gamito gamito@gmail.com wrote:
Hi,
I've made mysqlf a RPM and installed it.
After that i did what i shouldn' do: remove the files it installed.
Now, i wnat to install it agai and i can't.
Already rebuilt the rpm database ( rpm -vv --rebuilddb), used --force, --replacepkgs, --replacefiles, --justdb, --erase, --initdb, but no good.
Been at rpm.org, but found nothing that i already know.
Any help would be appreciated.
Warm regards, Mário Gamito _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi,
First delete the rpm you installed with "rpm -e --force <rpmname>". That should do it. If not report back the error it gives when executing that command. Then you can install the rpm again.
[root@mail rpms]# rpm -e --force mysql-5.0.33-1.i386.rpm rpm: only installation, upgrading, rmsource and rmspec may be forced [root@mail rpms]#
I tried [root@mail rpms]# rpm -ivh -e --force mysql-5.0.33-1.i386.rpm Preparing... ########################################### [100%] 1:mysql ########################################### [100%]
but in fact it doesn't get installed.
:(
Any ideas ?
Warm Regards, Mário Gamito
On 3/3/07, Mário Gamito gamito@gmail.com wrote:
First delete the rpm you installed with "rpm -e --force <rpmname>". That should do it. If not report back the error it gives when executing that command. Then you can install the rpm again.
[root@mail rpms]# rpm -e --force mysql-5.0.33-1.i386.rpm rpm: only installation, upgrading, rmsource and rmspec may be forced [root@mail rpms]#
I tried [root@mail rpms]# rpm -ivh -e --force mysql-5.0.33-1.i386.rpm Preparing... ########################################### [100%] 1:mysql ########################################### [100%]
but in fact it doesn't get installed.
First do "rpm -e mysql". Then everything should be gone, so check that. Then the "rpm -ivh mysql..." should work. You can't delete and install at the same time.
Regards, Tim
Hi,
Things are dificult.
First do "rpm -e mysql". Then everything should be gone, so check that. Then the "rpm -ivh mysql..." should work. You can't delete and install at the same time.
[root@mail rpms]# rpm -e mysql-5.0.33-1.i386.rpm error: package mysql-5.0.33-1.i386.rpm is not installed [root@mail rpms]#
[root@mail rpms]# rpm -ivh mysql-5.0.33-1.i386.rpm Preparing... ########################################### [100%] package mysql-5.0.33-1 is already installed
Contradictions....
Warm Regards, Mário Gamito
On Saturday 03 March 2007 9:05:25 am Mário Gamito wrote:
Hi,
Things are dificult.
First do "rpm -e mysql". Then everything should be gone, so check that. Then the "rpm -ivh mysql..." should work. You can't delete and install at the same time.
[root@mail rpms]# rpm -e mysql-5.0.33-1.i386.rpm error: package mysql-5.0.33-1.i386.rpm is not installed
Use 'rpm -e mysql', leave off the version info.
Tim
On 3/3/07, Mário Gamito gamito@gmail.com wrote:
Hi,
Use 'rpm -e mysql', leave off the version info.
Tried that too. I removed it with yum, but still can't install it again :(
Send the ouput from :
rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}.rpm\n'
Regards, Tim
--- Mário Gamito gamito@gmail.com wrote:
Hi,
rpm -qa --qf
'%{name}-%{version}-%{release}.%{arch}.rpm\n' I ran it, but no mysql appears
(Too much stuff to post here).
Warm Regards, Mário Gamito _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
try rpm -qa |grep 'mysql*'
Steven
"On the side of the software box, in the 'System Requirements' section, it said 'Requires Windows or better'. So I installed Linux."
On Saturday 03 March 2007 9:49:28 am Mário Gamito wrote:
Hi,
Use 'rpm -e mysql', leave off the version info.
Tried that too. I removed it with yum, but still can't install it again :(
Please be more verbose. What errors are you getting when you try to install the rpm? You can't expect help unless you tell us more information. I don't know about anyone else, but my mind reading capabilities suck.
Tim
Hi,
Please be more verbose. What errors are you getting when you try to install the rpm? You can't expect help unless you tell us more information. I don't know about anyone else, but my mind reading capabilities suck.
I've decided to reinstall and do things right. Now it's kicking ass :)
Thank you.
Warm regards, Mário Gamito
Probably an odd question, but, as I have said many times before, I'm more than a little bit rusty on this stuff. I know I can use gdb to debug the running kernel, but I'm not sure how to invoke it properly for CentOS.
Please advise.
Thanks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 01:01:48PM -0500, Mark Hull-Richter wrote:
Probably an odd question, but, as I have said many times before, I'm more than a little bit rusty on this stuff. I know I can use gdb to debug the running kernel, but I'm not sure how to invoke it properly for CentOS.
Please advise.
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the kernel, and one for the debuger. These computers should be connected using a serial (RS232) cable.
Please take notice I haven't done this since the 2.0 days, so things might have changed, but I don't expect they changed much.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
I thought there was a way to debug the kernel live on its own machine, as long as you have more than one processor (we do) and you don't set a breakpoint in synchronization code.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rodrigo Barbosa Sent: Tuesday, March 06, 2007 11:01 AM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the
kernel,
and one for the debuger. These computers should be connected using a serial (RS232) cable.
Please take notice I haven't done this since the 2.0 days, so things might have changed, but I don't expect they changed much.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Humm, not that I know of. And considering we are talking about PC hardware here (are we?), I can't imagine how it can be possible.
On Tue, Mar 06, 2007 at 03:24:26PM -0500, Mark Hull-Richter wrote:
I thought there was a way to debug the kernel live on its own machine, as long as you have more than one processor (we do) and you don't set a breakpoint in synchronization code.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rodrigo Barbosa Sent: Tuesday, March 06, 2007 11:01 AM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the
kernel,
and one for the debuger. These computers should be connected using a serial (RS232) cable.
Please take notice I haven't done this since the 2.0 days, so things might have changed, but I don't expect they changed much.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Humm, not that I know of. And considering we are talking about PC hardware here (are we?), I can't imagine how it can be possible.
I'm definately no expert here, but PC hardware has many hardware level debuging hooks that apps such as oprofile take advantage of.
Cheers...james
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 03:48:01PM -0500, James Olin Oden wrote:
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Humm, not that I know of. And considering we are talking about PC hardware here (are we?), I can't imagine how it can be possible.
I'm definately no expert here, but PC hardware has many hardware level debuging hooks that apps such as oprofile take advantage of.
Sure does, but how does one recover from a hardware lockup ?
Even if it were possible to have that kind of debugging, it would be fairly limited.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 03:48:01PM -0500, James Olin Oden wrote:
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Humm, not that I know of. And considering we are talking about PC hardware here (are we?), I can't imagine how it can be possible.
I'm definately no expert here, but PC hardware has many hardware level debuging hooks that apps such as oprofile take advantage of.
Sure does, but how does one recover from a hardware lockup ?
Well say the PCI buses timing gets hosed and the whole system seizes up what do you intened to do at that point (that is a hardware lockup)? And what does that thing you do have to do with debuging a kernel? Just curious.
Even if it were possible to have that kind of debugging, it would be fairly limited.
When you say "hardware" I start thinking jtag interfaces, or even more interesting was this thing we would place every pin of the processor through and then connect to the socket on the motherboard, but I think I missing something.
Cheers...james
[]s
Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFF7dU5pdyWzQ5b5ckRAulTAJoCkLfle7XdVtdkslQA/dtarhi7dwCgqhcP J7gca8LOUB+8j+5pXjaAf2A= =PS7U -----END PGP SIGNATURE----- _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 04:38:21PM -0500, James Olin Oden wrote:
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
Humm, not that I know of. And considering we are talking about PC
hardware
here (are we?), I can't imagine how it can be possible.
I'm definately no expert here, but PC hardware has many hardware level debuging hooks that apps such as oprofile take advantage of.
Sure does, but how does one recover from a hardware lockup ?
Well say the PCI buses timing gets hosed and the whole system seizes up what do you intened to do at that point (that is a hardware lockup)? And what does that thing you do have to do with debuging a kernel? Just curious.
A hardware lockup can be induced by software (quite easily, actually). On a 2 computers debug environment, you can see it happening and get enough data to fix it.
Even if it were possible to have that kind of debugging, it would be fairly limited.
When you say "hardware" I start thinking jtag interfaces, or even more interesting was this thing we would place every pin of the processor through and then connect to the socket on the motherboard, but I think I missing something.
Oh, I remember that one. SoftICE it was called, I think. I'm not sure. That was many years ago. Yes, that is one option but, if I remember correctly, that debugging hardware had a small processor of its own, completely independant.
And yes, jtag is also quite nice, but I never saw anything like that on a PC. Used them on some MIPS boards.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
When you say "hardware" I start thinking jtag interfaces, or even more interesting was this thing we would place every pin of the processor through and then connect to the socket on the motherboard, but I think I missing something.
Oh, I remember that one. SoftICE it was called, I think. I'm not sure. That was many years ago. Yes, that is one option but, if I remember correctly, that debugging hardware had a small processor of its own, completely independant.
those were _REAL_ ICE (In Circuit Emulators), I haven't seen an ICE since the days of hte i286.
SoftICE was a software debugger that had some ICE like functionality, I remember it as a Windows kernel debugger. I believe its now history, the company that created it was swallowed by someone else who later decided they didn't know what to do with it so they buried it.
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 04:38:21PM -0500, James Olin Oden wrote:
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
Humm, not that I know of. And considering we are talking about PC
hardware
here (are we?), I can't imagine how it can be possible.
I'm definately no expert here, but PC hardware has many hardware level debuging hooks that apps such as oprofile take advantage of.
Sure does, but how does one recover from a hardware lockup ?
Well say the PCI buses timing gets hosed and the whole system seizes up what do you intened to do at that point (that is a hardware lockup)? And what does that thing you do have to do with debuging a kernel? Just curious.
A hardware lockup can be induced by software (quite easily, actually).
I'm still not following you. Its one thing for the "kernel" to lockup and its another for the hardware to lockup. Could you give an example?
On a 2 computers debug environment, you can see it happening and get enough data to fix it.
Provided the processor is still functioning in some way, sure.
Even if it were possible to have that kind of debugging, it would be fairly limited.
When you say "hardware" I start thinking jtag interfaces, or even more interesting was this thing we would place every pin of the processor through and then connect to the socket on the motherboard, but I think I missing something.
Oh, I remember that one. SoftICE it was called, I think. I'm not sure. That was many years ago. Yes, that is one option but, if I remember correctly, that debugging hardware had a small processor of its own, completely independant.
And yes, jtag is also quite nice, but I never saw anything like that on a PC. Used them on some MIPS boards.
Its definately on higher end Intel and AMD boards.
Cheers...james
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 05:40:30PM -0500, James Olin Oden wrote:
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
On Tue, Mar 06, 2007 at 04:38:21PM -0500, James Olin Oden wrote:
On 3/6/07, Rodrigo Barbosa rodrigob@darkover.org wrote:
Humm, not that I know of. And considering we are talking about PC
hardware
here (are we?), I can't imagine how it can be possible.
I'm definately no expert here, but PC hardware has many hardware level debuging hooks that apps such as oprofile take advantage of.
Sure does, but how does one recover from a hardware lockup ?
Well say the PCI buses timing gets hosed and the whole system seizes up what do you intened to do at that point (that is a hardware lockup)? And what does that thing you do have to do with debuging a kernel? Just curious.
A hardware lockup can be induced by software (quite easily, actually).
I'm still not following you. Its one thing for the "kernel" to lockup and its another for the hardware to lockup. Could you give an example?
Not from the top of my head, no. I haven't messed around with kernel code for something like 6 years. But I do remember seeing this kind of thing happening. Maybe some MMU related function, but I'm not sure.
On a 2 computers debug environment, you can see it happening and get enough data to fix it.
Provided the processor is still functioning in some way, sure.
You will get the data previous to the lockup, since kgdb would first then the debug data, and then execute the function. gdb itself would be running on the second computer.
And yes, jtag is also quite nice, but I never saw anything like that on a PC. Used them on some MIPS boards.
Its definately on higher end Intel and AMD boards.
JTAG ? Nice. I'll start looking for those on my next boards. Tkx for the tip.
[]s
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
There may be, I just don't know the specics. I know IBM at one point was working on something called dprobes, and there have been other things like it proposed and worked on to some degree:
http://directory.fsf.org/all/DynamicProbes.html
Hope that helps...james
On 3/6/07, Mark Hull-Richter mhull-richter@datallegro.com wrote:
I thought there was a way to debug the kernel live on its own machine, as long as you have more than one processor (we do) and you don't set a breakpoint in synchronization code.
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rodrigo Barbosa Sent: Tuesday, March 06, 2007 11:01 AM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the
kernel,
and one for the debuger. These computers should be connected using a serial (RS232) cable.
Please take notice I haven't done this since the 2.0 days, so things might have changed, but I don't expect they changed much.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Okay, if I do it that way, is there a how-to somewhere on this, or does kgdb come with something like that or am I on my own here? :-)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rodrigo Barbosa Sent: Tuesday, March 06, 2007 11:01 AM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the
kernel,
and one for the debuger. These computers should be connected using a serial (RS232) cable.
Please take notice I haven't done this since the 2.0 days, so things might have changed, but I don't expect they changed much.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 08:28:26PM -0500, Mark Hull-Richter wrote:
Okay, if I do it that way, is there a how-to somewhere on this, or does kgdb come with something like that or am I on my own here? :-)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rodrigo Barbosa Sent: Tuesday, March 06, 2007 11:01 AM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the
kernel,
and one for the debuger. These computers should be connected using a serial (RS232) cable.
Please take notice I haven't done this since the 2.0 days, so things might have changed, but I don't expect they changed much.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
On Tue, 6 Mar 2007, Rodrigo Barbosa wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue, Mar 06, 2007 at 01:01:48PM -0500, Mark Hull-Richter wrote:
Probably an odd question, but, as I have said many times before, I'm more than a little bit rusty on this stuff. I know I can use gdb to debug the running kernel, but I'm not sure how to invoke it properly for CentOS.
Please advise.
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the kernel, and one for the debuger. These computers should be connected using a serial (RS232) cable.
Would VMWare let you run the kernel you're debugging in a VM and watch it from the host?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Mar 22, 2007 at 04:25:41PM -0400, Lists wrote:
On Tue, 6 Mar 2007, Rodrigo Barbosa wrote:
On Tue, Mar 06, 2007 at 01:01:48PM -0500, Mark Hull-Richter wrote:
Probably an odd question, but, as I have said many times before, I'm more than a little bit rusty on this stuff. I know I can use gdb to debug the running kernel, but I'm not sure how to invoke it properly for CentOS.
Please advise.
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the kernel, and one for the debuger. These computers should be connected using a serial (RS232) cable.
Would VMWare let you run the kernel you're debugging in a VM and watch it from the host?
That is a very good question. Last time I used kgdb, it was done using a serial (RS232) cable. These days, I really don't know.
- -- Rodrigo Barbosa "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Rodrigo Barbosa Sent: Thursday, March 22, 2007 1:34 PM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Mar 22, 2007 at 04:25:41PM -0400, Lists wrote:
On Tue, 6 Mar 2007, Rodrigo Barbosa wrote:
Using gdb to debug the kernel is not an easy trick. You will need a kgdb patch for the kernel, and 2 computers. 1 for running the
kernel,
and one for the debuger. These computers should be connected using
a
serial (RS232) cable.
Would VMWare let you run the kernel you're debugging in a VM and
watch
it
from the host?
That is a very good question. Last time I used kgdb, it was done using
a
serial (RS232) cable. These days, I really don't know.
It can be done on certain processors, but I don't have one of them - the Pentium-D has the necessary 64 bit capability, but this is a mere P-4 - no such lock (thought of that! :-).
Mark Hull-Richter wrote:
Probably an odd question, but, as I have said many times before, I'm more than a little bit rusty on this stuff. I know I can use gdb to debug the running kernel, but I'm not sure how to invoke it properly for CentOS.
Please advise.
I have some advice for you. Please don't break threading.
Mike
You caught me - that was actually my evil, diabolical plan!
Curses! Foiled again!
Er, I mean, I guess you're referring to the mailing list threading - I heard about that one already, but thanks for the reminder.
I think I've mentioned that I'm new to a lot of this stuff - I'm learning, bear with me, I learn fast.
:-)
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Mike McCarty Sent: Thursday, March 08, 2007 9:55 AM To: CentOS mailing list Subject: Re: [CentOS] How do I debug the kernel?
I have some advice for you. Please don't break threading.
Mark Hull-Richter wrote:
You caught me - that was actually my evil, diabolical plan!
Curses! Foiled again!
Er, I mean, I guess you're referring to the mailing list threading - I heard about that one already, but thanks for the reminder.
I think I've mentioned that I'm new to a lot of this stuff - I'm learning, bear with me, I learn fast.
:-)
Not a problem, just don't do it again, or I'll have to have Vinnie give you a little ride in his car.
:-)
Mike
-
Barry Brimer -
James Olin Oden -
John R Pierce -
Lists -
Mark Hull-Richter -
Mike McCarty -
Mário Gamito -
Rodrigo Barbosa -
Steven Vishoot -
Tim Verhoeven -
Tim Wunder