On 1/13/06, Marc Espie <[EMAIL PROTECTED]> wrote: > > On Fri, Jan 13, 2006 at 12:47:51AM +0059, Han Boetes wrote: > > Clint M. Sand wrote: > > > On Thu, Jan 12, 2006 at 09:38:07PM +0100, Han Boetes wrote: > > > > I doubt you need perl at all on a box like that. You can also > > > > consider to simply remove all the perl on that system. > > > > > > The pkg_* tools are perl. Even though its a firewall he may need > > > to install/remove/maintain pkg's of some sort. > > > > Ever seen the contents of a package? You don't need perl for > > maintaining that. Just a simple script can do the removing and > > adding of packages. > > > > Oh sure, and 200K of perl code say otherwise. > > I don't think you have a real idea what these tools do these days. > There have been lots of small additions and changes. > > The devil is in the details as they say. > > Good luck writing correct tools without perl. > > As mentioned above, you can use binpatch:
http://openbsdbinpatch.sourceforge.net/ I've had a wrap for a few months and this is the first time I've needed to patch it, so I used binpatch on my main server to create a patch and installed it very easily on the wrap. I also did the same with the 002_fd patch. Cheers z0mbix
