Re: help - I installed rpm4.0.6 and now nothing works!



On Mon, 02 Jan 2006, in the Usenet newsgroup comp.os.linux.misc, in article
<op.s2qr51s4nxtvbs@xxxxxxxxxxxxxxxx>, Enrique Perez-Terron wrote:

>Hm, so the pain I remember must have been with RH 5? (How come I can't
>associate anyting with 6.0 or 6.1...) In any case, this refutes the
>hypothesis that the woes of the OP could be related to the libc5->
>glibc transition.

RH 5.0 (hurricane) was the first distribution with the glibc2 (and a
2.0.32 kernel) on 1 December 1997. My, how time flies!!!

RH 6.0 (hedwig) introduced the 2.2.5 kernel, and 6.1 (cartman) brought
that up to 2.2.12, both in 1999. Hazy memories, but I recall 6.0 was
rejected here because of the new kernel, and 6.1 wasn't that much of
an improvement. We stayed with 5.2 (apollo) until 6.2 came out in March
2000, and transitioned to that. But then, we had stayed with 4.2 until
5.2 came out in late 1998.

>I must admit that I am not in a sysadmin position with responsibility for
>mission critical servers. I would definitely handle such machines with a
>different level of caution than my desktop and development toys.

When we get interested in a new distribution, we take the CDs back into
the lab area, and several of us start installing it on test systems,
playing with it until we can agree on what the installation should look
like. As this is in addition to our regular jobs, it tends to take two
to three weeks. We then install it on more test boxes that mirror the
production systems, and follow that through a backup cycle (8 weeks).
If nothing has gone wrong, we'll come in over a weekend, and pour the
new version over everything. The following Monday tends to get exciting,
but we've only had to back out once, and that was a printing problem
back with an early release of Red Hat - I think 4.0, or 4.1.

>I install things quite often, and after fairly sloppy consideration of
>the possibility of incompatibilibies. Searching releasenotes and errata
>for possible problems would have amounted to tens of hours over the years.

We _use_ the systems, so experimentation is quite limited.

>But I try very hard to stick to things packages for the particular version
>and release of the distro. The idea of installing rpm4 on Redhat 6.2
>would have made me very nervous before starting to read anything at all.

Updates are always tested on test boxes before reaching the production
hardware. The update to rpm4 wasn't that big of a deal, as we had gone
through the update from rpm2 to rpm3 on RH 5.2 (came with rpm-2.5.5-5.2,
and was updated to rpm-3.0.2-5.x, rpm-3.0.5-9.5x and finally rpm-4.0.2-5x).

>Most likely I would have discarded the idea without any such reading,
>because I would have felt that even if I did the reading and found no
>objections, I would be very unlikely to find direct assurances that it's OK.
>If it's unlikely, hunting for it is lost time most of the time. This kind
>of things you are not supposed to do, don't always carry warnings
>explaining what happens if you do.

We'd been receiving warm-fuzzies from the various Red Hat mailing lists of
the time, so we were not that concerned.

>But I would have felt that rpm is very much at the heart of the security
>and stability of the system, since everything else is installed by it.

Packaging systems, whether rpm (remember rpp?) or Debian's apt, *BSD's
ports and so on go a long way to to easing maintenance. Depending on how
paranoid you are, they don't fully replace common sense or source audits.

>You also have rpm -V, which I have used several times and I consider very
>important. This is not a logical thought, it's just a kind of heuristic,
>or a thinking by association rather than logic. Gut feeling.

Only problem we have with 'rpm -V' is that it can't check files it's not
aware of - one example being many of the files in /etc/. We've been
using tripwire for that. One thing I do appreciate is being able to set
ownership and permissions back to a semi-sane way using rpm. This is not
a common problem for us (we don't hand out root permissions on our systems)
but when it's needed, it's a magic savior.

Old guy
.



Relevant Pages

  • Re: [opensuse] how to update alsa to 1.0.14rc2 on Suse 10.1 with checkinstall?
    ... > But I want to maintain the integrity of the rpm database by creating ... > rpms of those packages using checkinstall. ... > $#>rmmod snd_timer ... > Should I keep both the alsa-1.0.13-0.pm.0 rpm when installing the ...
    (SuSE)
  • Re: [SLE] Help to install Firefox and Flashplayer 7 [Solved]
    ... > |> Thanks for the RPM, I found too the one for Thunderbird, I installed ... Are you installing the tarballs as root? ... First I've to tell you that I use to manage RPMs and tarballs and that I ...
    (SuSE)
  • Re: Aptitude wants to remove OpenOffice.org
    ... Please also explain "Almost anything is better than installing .rpms ... declares that it depends (requires in rpm) other packages. ... The package manager does not check the filesystem when looking to see ... But rpm and dpkg use different databases. ...
    (Debian-User)
  • Re: An update is needed Fedora!
    ... a hard reason for PHP5 requirement. ... development SRPMs. ... > Could you send one more example for compiling, installing, configuring, etc? ... they should then be installed as an update using: rpm -Uvh ...
    (Fedora)
  • Re: SPS 2003 and .NET 2.0
    ... Installing 2.0 and using 2.0 are two diffrent things. ... I have had two test boxes being used extensively for development and ... usability studies with 2.0 installed with no issues. ... I just left the SPS portal sites on 1.1. ...
    (microsoft.public.sharepoint.portalserver)