| 1 |
On Saturday 10 September 2005 14:45, Edward Catmur wrote: |
| 2 |
> On Sat, 2005-09-10 at 14:29 -0500, John Jolet wrote: |
| 3 |
> > We're in the process of transitioning from 32-bit Redhat (7 I think) |
| 4 |
> > web/app servers to 64-bit gentoo web/app servers. One concern I've got |
| 5 |
> > is from a security standpoint, normally you don't deploy webservers with |
| 6 |
> > development tools on them. How do you guys handle this question with |
| 7 |
> > internet-facing production servers? |
| 8 |
> > |
| 9 |
> > One thought I had was to set up a build server, build the binaries on |
| 10 |
> > this server, and do an emerge of the binaries FROM this server to the |
| 11 |
> > production servers, with gcc and such removed from them. Will this work? |
| 12 |
> |
| 13 |
> Yes. |
| 14 |
> |
| 15 |
> >From emerge(1): |
| 16 |
> |
| 17 |
> --buildpkg (-b) |
| 18 |
> Tells emerge to build binary packages for all ebuilds processed |
| 19 |
> in addition to actually merging the packages. Useful for main- |
| 20 |
> tainers or if you administrate multiple Gentoo Linux systems |
| 21 |
> (build once, emerge tbz2s everywhere). The package will be cre- |
| 22 |
> ated in the ${PKGDIR}/All directory. An alternative for |
| 23 |
> already-merged packages is to use quickpkg which creates a tbz2 |
| 24 |
> from the live filesystem. |
| 25 |
> |
| 26 |
> I would recommend building packages on a build server with --buildpkg, |
| 27 |
> installing them on a testing server, and once tested re-packaging them |
| 28 |
> with quickpkg on the testing server to install on the production |
| 29 |
> servers. (The advantage of quickpkg is it picks up changes to |
| 30 |
> configuration files.) Of course, you could combine the build and testing |
| 31 |
> servers onto one machine. |
| 32 |
> |
| 33 |
> HTH. |
| 34 |
Thanks. |
| 35 |
-- |
| 36 |
John Jolet |
| 37 |
Your On-Demand IT Department |
| 38 |
512-762-0729 |
| 39 |
www.jolet.net |
| 40 |
john@×××××.net |
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives