Fedora Core 3

[insomnia]

I must say that so far I have not had a freeze with this new driver on FC3 (Geforce4) so I'll keep my fingers crossed..

I was indeed one version behind...
Now it all seems to work

[Void Main]

hmmm I must be smoking some Crack that's so good I don't even know I'm smoking it :shock: How did I completely forget about /etc/apt/sources.list.d/? Anywho... forget everything I said above. I still have a problem, but now, at least,m working on the right files in the right directory! :oops:

Heh heh, I used the FreshRPMS apt for a long time but now I use Dag's apt. He doesn't have one labeled for FC3 yet but here's the one I use:
http://apt.sw.be/fedora/3/en/i386/RPMS. ... g.i386.rpm

After installing check to make sure all the *list files in /etc/apt/sources.list.d point to the FC3 directory and not the FC2 directory.

I would uninstall the existing one and remove the /etc/apt/apt.conf so when you install the new one a good clean apt.conf is installed.

[Void Main]

I must say that so far I have not had a freeze with this new driver on FC3 (Geforce4) so I'll keep my fingers crossed..

I was indeed one version behind...
Now it all seems to work :)

Cool! On a side note, my son had a freeze this evening when exiting a GL game. I just ssh'd into the machine and did "init 3;init 5" which brought X down and back up and got him going again. Too bad they can't get this thing right.

[lovswr]

hmmm I must be smoking some Crack that's so good I don't even know I'm smoking it How did I completely forget about /etc/apt/sources.list.d/? Anywho... forget everything I said above. I still have a problem, but now, at least,m working on the right files in the right directory!

Heh heh, I used the FreshRPMS apt for a long time but now I use Dag's apt. He doesn't have one labeled for FC3 yet but here's the one I use:
http://apt.sw.be/fedora/3/en/i386/RPMS. ... g.i386.rpm

After installing check to make sure all the *list files in /etc/apt/sources.list.d point to the FC3 directory and not the FC2 directory.

I would uninstall the existing one and remove the /etc/apt/apt.conf so when you install the new one a good clean apt.conf is installed.

Well Void I would do as you say, but now even rpm -q apt-get does not work. I have really messed up rpm, apt-get & synaptic on my system. Somehow I can not install or unistall anything. Is there some kind of manual way that I could get rpm, at least, to work?

[Void Main]

Did you encounter the "RPM Lockup" problem that has been around since RH8? If so here's how you fix it:

http://voidmain.is-a-geek.net/redhat/fe ... round.html

I figured this wouldn't occur any more but maybe it still does. That would definitely mess up all rpm related commands (rpm, apt, synaptic, etc).

[worker201]

Did you encounter the "RPM Lockup" problem that has been around since RH9? If so here's how you fix it:

http://voidmain.is-a-geek.net/redhat/fe ... round.html

I figured this wouldn't occur any more but maybe it still does. That would definitely mess up all rpm related commands (rpm, apt, synaptic, etc).

I had a problem with that when I first started with FC1, but I used your solutions and haven't seen it since, even though I reinstalled FC1 twice, FC2 twice, and FC3 once. Do you or Redhat have any idea what causes it? Is there a certain rpm out there that writes over the database somehow? Or is it maybe a bad disk sector, and rewriting the dbs puts them in better locations? Like I said, I haven't had a problem with this for a long while now, but it was one of the most frustrating things I ever came across.

On the brighter side, since rpm didn't work, I learned how to build from source, which is always a good thing. And I learned a bunch of the various commands for rpm too. So maybe it's not a bug - it's a feature designed to force us into learning Linux

[Void Main]

I had a problem with that when I first started with FC1, but I used your solutions and haven't seen it since, even though I reinstalled FC1 twice, FC2 twice, and FC3 once. Do you or Redhat have any idea what causes it?

I haven't seen it in quite some time as well. It was pretty bad in RH8 but seems to happen less often with the later releases. I haven't had it happen in FC2 or FC3 that I recall. I figured out I could pretty much make it happen at will by pressing a ^C while installing an RPM. I don't really have any idea why the problem just came out of the blue in RH8 and hung around for as long as it did. Might find something in some mailing lists somewhere...

Is there a certain rpm out there that writes over the database somehow? Or is it maybe a bad disk sector, and rewriting the dbs puts them in better locations?

No because whenever I ran into the problem and then fixed it using the instructions in my tip I could immediately retry the installation of the RPM file that I was installing when it hung and it would work. I think where I used to run into trouble is sometimes an RPM would take a while to install and I would think it was hung and then tried to break out of the install with a ^C which actually caused the problem. I think in most cases if I had waited the command would have eventually finished. I do know that some times it would hang anyway. If it hasn't installed after a couple of minutes it's not going to install. When this happens I can't even break out with a ^C and have to resort to a "kill -9" on the rpm command, followed by the removal of those __*.db lock files.

[lovswr]

Did you encounter the "RPM Lockup" problem that has been around since RH8? If so here's how you fix it:

http://voidmain.is-a-geek.net/redhat/fe ... round.html

I figured this wouldn't occur any more but maybe it still does. That would definitely mess up all rpm related commands (rpm, apt, synaptic, etc).

WOOOOOHOOOOO Void U R DA MAAAAAN!!!!!!

I did as per that thread. I was able to finally get rid of synaptic & then I discovered that I had the following:



apt-0.5.15cnc6-3.1.fc2.dag
apt-0.5.15cnc6-1.1.fc3.fr


well I got rid of the fc2 (no offense dag) & now it seems to be running smoothly. I think I will just hang out with apt, since yums structure has been changed.

[Void Main]

Cool beans!

[lovswr]

Did you encounter the "RPM Lockup" problem that has been around since RH8? If so here's how you fix it:

http://voidmain.is-a-geek.net/redhat/fe ... round.html

I figured this wouldn't occur any more but maybe it still does. That would definitely mess up all rpm related commands (rpm, apt, synaptic, etc).

WOOOOOHOOOOO Void U R DA MAAAAAN!!!!!!

I did as per that thread. I was able to finally get rid of synaptic & then I discovered that I had the following:



apt-0.5.15cnc6-3.1.fc2.dag
apt-0.5.15cnc6-1.1.fc3.fr


well I got rid of the fc2 (no offense dag) & now it seems to be running smoothly. I think I will just hang out with apt, since yums structure has been changed.

Well that didn't last long. I figured that since I had an apt that was for fc3, then it would get the correct yum too. It seems that I was correct as yum update produced 148 rpms (all with fc3 appended at the end) inculding such gems as kdebase & lame.

As an aside the print function has gotten much easier (at least for me). Fc3 is the first linux distro that I have ever gotten to work with any printer I ever owned. I just plugged my Canon USB S400 in, ran the print utility & viola! test page goodness What's really wierd is that same printer stopped working on my XP Pro box!..(although a couple failed upgrades to SP@ may have something to do with that ) Now if I can get samba to work right., I'll just leave it on the FC3 box.

[insomnia]

As for Apt and mixing repositories,
DAG just added the following to it's FAQ:

D. Compatibility and mixing repositories
D1. What about compatibility with Fedora ?
My Fedora repository is designed to work 100% with the Fedora Core packages. You should have no problems applying these packages to Fedora Core. If you do find a problem, please let me know asap so that I can look into it.

Beware that this repository is not compatible with fedora.us, livna.org or Fedora Extras. I would like to be compatible with these repositories, but they have a policy to not work together with other repositories. Compatibility works in 2 directions and if one party is refusing to care, it's impossible to make it work. I still hope fedora.us, livna.org or Fedora Extras change their minds and drop this policy. In the meantime I advice you not to use these 3 repositories.

One of the many examples is that they introduce new packages that already existed in my repository for 2 years. Sadly, they then use other package names so that it clashes with my already available packages. In many cases it is hard or even impossible to work around that. With other repositories we care about such clashes and discuss and prevent this from happening. Other repositories are willing to fix inter-repository compatibility, fedora.us, livna.org and Fedora Extras are not.

Other reasons for not choosing fedora.us packages: only i386 is supported (no x86_64, pcc, sparc or alpha packages), only Fedora Core packages are provided (no support for RHEL, Yellow Dog, Aurora, SuSE), no open development or publicized SPEC files (following development is very hard), only resulting source RPMs are availble.

D2. What repositories can I mix ?
Most repositories should already work well together. If you do find a problem, the best thing to get this fixed is by reporting this to both repository maintainers. If it is a genuine problem, it will be fixed promptly.

The repositories I mix myself are: FreshRPMS, Dries, NewRPMS and PlanetCCRMA.

FreshRPMS, PlanetCCRMA, Dries and DAG (RPMforge.net) build their packages together from the same sources. This ensures much greater cooperation and compatibility and will eventually lead to a merger. If you are a skilled packager and interested to join, don't hesitate to contact us.

http://dag.wieers.com/home-made/apt/FAQ.php#D

[Ice9]

I guess this is the explanation for the few problems I've been having over the last year and a half.
Since I really don't like Fedora's implementation of KDE I've been using the kde-redhat version since my RH9 days.

Installation always went smoothlt with apt but if you don't include the Fedora US repositories you run into problems sooner than later, I experienced that with RH9.
On the other hand the only problem I ever had was duplicate packages and until now I always removed the oldest package and my system still works.

[Void Main]

I pointed that same Dag FAQ link out in another thread the other day:

viewtopic.php?t=1254&p=8262#8262

I have also been preaching for the last couple years about not mixing certain repositories together whenever someone complains about apt problems. I use apt on a lot of machines and have only had one major problem and a couple of minor ones, all because I mixed repositories that had similar packages with different names.

Here is a thread dealing with a problem Ice9 had almost 2 years ago that I have on my apt tip:

viewtopic.php?p=496#496

This is regarding CCRMA being mixed with other repos. It was before several good ons got together and got there act together. Back when I used FreshRPMS only I never had a problem. For the last 6 months to a year I have been using the 4 repos that are listed on the dag site and have never had a problem. I've been trying to preach this but it almost seems like nobody is hearing me.

[Ice9]

Void Main wrote:

I've been trying to preach this but it almost seems like nobody is hearing me.

I heard you the first time when you solved my problem with pygtk2 and when I started to use kde-redhat I removed all the other repositories than Fedora US but unfortunately it doesn't contain nearly as much packages than Dag's so eventually after a while I added Dag's and Dries' repositories again.

What I do now is comment them out and only enable them when I want to install a particular package I can't find on Fedora US, this seems to work so far ...

[Void Main]

Void Main wrote:

I've been trying to preach this but it almost seems like nobody is hearing me.

What I do now is comment them out and only enable them when I want to install a particular package I can't find on Fedora US, this seems to work so far ...

That will work as long as the thing you are trying to install depends on another package that is contained in both repos but with different names. For small programs you shouldn't have a problem doing this.