RedHat introduced using modules in DNF on RHEL version 8 (and above). This opens very interesting new options, however, sometimes – a quick-n-dirty repo is needed. An example – for offline systems, a repo of already installed packages (on exactly similar system) is created for later use. This used to work well on RHEL version…
SSH is a wonderful tool. One of its best features is the ability to pierce a firewall and let you go through it. If you’re using the dynamic port (-D as argument in command line openSSH), you actually get a SOCKS5 proxy over which you can transport all your desired data. This allows you the…
This is relevant for Redhat EL 3 and 4, and any other compatible system not using “yum”. RHEL5 uses “yum”, and its RPM system does not include the “–aid” flag, which we require so much. 1. Place all the available RPMS (I assume these are the installation medias, combined) in a single directory – for…
YUM is a nice (and useful, when used correctly) tool to manage packages, using RPM as its engine. APT, the Debian alternative, has this ability, and so does YUM. YUM does not pin a specific version of a package, but rather avoids upgrading it as soon as it was marked. It remains installed, but never…
This is the error message I have seen in my Linux+Postfix+Amavisd-new system. Not only that, but Amavis has kept a copy of each message in its tmp directory, which reduced my /var size to nothing quite rapidly. amavis[21189]: (21189-01) (!)PRESERVING EVIDENCE in /var/amavis/tmp/amavis-200 80103T051116-21189 Doesn’t sound too good. Partial search in google has produced the…
On most cases, when preparing a recovery server, you can just ‘tar’ the entire server’s contents and just move it, along with a short recipe on how to rebuild the original partition layout (software Raid? LVM? flat partition tables?), how to mount volumes in-place, how to extract the tar files into the right locations, and…
