Re: static binaries, jails and compat x

From: Doug Ambrisko (ambrisko_at_ambrisko.com)
Date: 08/03/05

  • Next message: Doug Barton: "Re: ath + wep issue" 
    To: Julian Elischer <julian@elischer.org>
Date: Tue, 2 Aug 2005 16:29:56 -0700 (PDT)

    Julian Elischer writes:
    | Now that we have dynamic binaries everywhere I'm discovering all those
    | places
    | where this breaks..
    |
    | FreeBSD 5 or 6 machine. (needed because freeBSD 4 can't run on the new
    | hardware)
    | freeBSD 4 jail to run a legacy app.
    | ps top and netstat (and friends) don't work (not surprisingly)
    | ps I can get from /rescue
    | but top and netstat are only available in dynamic form.

    Hey, it gets harder when you run FreeBSD 4.X on a FreeBSD amd64 machine and
    have mixed i386/amd64 libs :-( I copy over the amd64 versions of ps etc.
    and had to copy over some libs that conflict in names. In-order to get
    around placement issues I binary edit them on the fly via sed:
            sed -e 's/libkvm/libhvm/g' -e 's/libexec/libhxec/g' -e 's/libsbuf/libhbuf/g'

    etc. One thing I just found out was:
            UNAME_s,r,v,m,p
    and hacked libc's getosreldate & uname to use that stuff. I LD_PRELOAD
    my lib of these then pkg_add -r, libtool etc. then just work and think
    the are really running on FreeBSD 4.X. I wish if LD_PRELOAD lib's
    didn't exist then it would just ignore it versus failing to run. I've made
    that change locally. That way I can chroot in chroot without needing
    the shims when not needed.

    It's a mess. Do you think the libc stuff should have the same type
    of over-rides as the uname binary. I think so.

    Doug A.
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Doug Barton: "Re: ath + wep issue"

    Relevant Pages

    • Re: static binaries, jails and compat x
      ... >| Now that we have dynamic binaries everywhere I'm discovering all those ... >the are really running on FreeBSD 4.X. ... That way I can chroot in chroot without needing ... Linux binaries at the moment. ...
      (freebsd-current)
    • Re: Init.c, making it chroot
      ... :> For this to work, i'd like to know at what point do i call chroot(), ... DVD-ROM with FreeBSD and DragonFly BSD on it. ... I decided to add the feature to DragonFly BSD's ... that a committer will pick it up. ...
      (freebsd-hackers)
    • Re: Init.c, making it chroot
      ... Oliver Fromme writes: ... DVD-ROM with FreeBSD and DragonFly BSD on it. ... I decided to add the feature to DragonFly BSD's ... The chroot() patch has been committed with r1.6. ...
      (freebsd-hackers)
    • Re: "nanobsd" prototype
      ... But if we use something like or picobsd like crunch ... > The point of nanobsd is simply to create a tool for putting FreeBSD ... Is there a list of progs which get installed with libs etc? ... And have a script which lists all libs needed. ...
      (freebsd-current)
    • pam_chroot
      ... Has anyone got the pam_chroot module to successfully work in FreeBSD? ... libraries into my chroot, I can chroot -u test -g test /home/test ... Nick Twaddell ...
      (FreeBSD-Security)