"Fossies" - the Fresh Open Source Software Archive

Member "scponly-20110526/build_extras/README" (20 Nov 2003, 2333 Bytes) of package /linux/privat/old/scponly-20110526.tgz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. 
    1 THIS DIRECTORY CONTAINS ADDITIONAL SCRIPTS IN CASE THE MAIN
    2 setup_chroot.sh HAS FAILED YOU.
    3 
    4 
    5 for the time being, some hacked up setup_chroot.sh scripts are located
    6 here. ultimately, these hacked up scripts in this directory will be
    7 removed.  the rationale is simply that maintaining individual scripts for
    8 each OS will be a maintenance nightmare.
    9 
   10 however, setup_chroot.sh has been modified to support pre and post setup
   11 scripts, which are in the arch sudirectory. it is my hope to isolate OS 
   12 specific commands into small easily managed files.
   13 
   14 
   15 here are some notes regarding the new architecture:
   16 
   17 well, as many of you know, setup_chroot.sh and setup_chroot.sh.in has been
   18 one of the most problematic aspects of scponly installation.  a generic
   19 script to create chrooted jails just isnt as easy as one might hope.  
   20 i've done some initial overhauling, and as per Sven's suggestion, come up
   21 with a framework for a more extensible installation script.
   22 
   23 the first part of the setup_chroot script is intended just to figure
   24 things out, without making any changes. it looks like this:
   25 
   26  - probe the filesystem for the locations of binaries
   27  - probe the filesystem for the locations of libraries required by the
   28 	binaries
   29  - ask the user a couple of questions about their preferences
   30  - check for the existence of an OS specific presetup script in the
   31 	build_extras/arch directory
   32 
   33 the idea here is that the generic case (setup_chroot.sh) will take a best
   34 guess approach, but any customizations required for the various platforms
   35 can be located in a seperate file.
   36 
   37 the pathname of this file will be "build_extras/arch/`uname -sr`.pre.sh"
   38 
   39 the second part of the installation script actually makes the changes, as
   40 follows:
   41  - install directories
   42  - install binaries
   43  - install libraries
   44  - check for the existence of a postsetup script in the build_extras/arch
   45 	directory
   46 
   47 the pathname of this file will be "build_extras/arch/`uname -sr`.post.sh"
   48 
   49 so for example, additional things required for redhat, debian, irix,
   50 solaris, etc etc ad nauseum can be located in seperate files.
   51 
   52 it is my hope that people will contribute these presetup and postsetup
   53 scripts to me via email, so that i can add them to the arch directory.
   54 
   55 let me know if you see any problems with this idea.  incidentally, i think
   56 it initially came from Roland Lammel.