Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: Automating Security Patches For Chrooted Environment

  1. #11
    Senior Member Maestr0's Avatar
    Join Date
    May 2003
    Posts
    604
    You will still need the output from ldd from rpm and up2date in the jail so rpm can run. If you can get rpm to run it should begin to take care of dependencies after that.

    -Maestr0
    \"If computers are to become smart enough to design their own successors, initiating a process that will lead to God-like omniscience after a number of ever swifter passages from one generation of computers to the next, someone is going to have to write the software that gets the process going, and humans have given absolutely no evidence of being able to write such software.\" -Jaron Lanier

  2. #12
    Junior Member
    Join Date
    Apr 2006
    Posts
    20
    Thank you Maestr0 and theHorse13 for your help. I was able to setup the automated chroot patching. Setting up RPM in the chroot was all I needed. I did not go as far as setting up up2date in the chroot.

    Up2date in the non-chrooted part of the OS has been configured to keepinstallfiles in the rpm repository. Then I run rpm -Uvh --root=/jail /tmp/*.rpm (cron job). /tmp is the rpm repository (again I configured up2date to use /jail/tmp as the repository).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •