Date: Wed, 16 Jan 2002 07:39:22 -0500 From: Beth Reid <breid@cyberguard.com> To: "'questions@freebsd.org'" <questions@freebsd.org> Subject: FreeBSD patch/packaging questions Message-ID: <F767BDFE817ED411A32100D0B7694A9FAD1BBA@mail.cybg.com>
next in thread | raw e-mail | index | archive | help
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C19E8A.D2DF0F16 Content-Type: text/plain; charset="iso-8859-1" Hi I have a few questions regarding non-kernel FreeBSD patch distribution. Any information is really appreciated. If all of this is documented somewhere, I would be happy to do the research if someone could point me to the document. 1 ) If I produced a product based on FreeBSD 4.3, how would my customers get the patches? I can see there was a binary distribution of the patches using pkg_add. This seems to work very nicely in distributing patches to customers. However, this process seemed to change with the openssh patch 01:63. The binary distribution was for FreeBSD 4.4 only. How does one ship a binary installation of that patch to their customers who are running 4.3? (Same goes for patches 02:01 and 02:02.) The customer's system does not have source. :-/ 2) Do you provide a mechanism where I can create my own binary installations using pkg_add? It seems I can use pkg_create. That seems to work fine, but can I get more information on the packinglist file? Is creating a very simple packinglist such as this for the pw patch seem okay? (There seemed to be a lot of more complex options. I am not too sure about the mtree and unexec lines.) @cwd /usr/sbin @srcdir source_directory @owner root @group wheel @mode 555 pw 3) What about patches that patch libraries which impact several executables? If there is a patch that patches a library (similar to the old 01:40) patch, how do you know which commands that it would impact and which to include in the binary package? Would it be documented in the README? Thanx! Beth Reid CyberGuard Corporation phone: 954-958-3900 x3230 email: breid@cyberguard.com fax: 954-958-3901 See the LX, a new, low-cost EAL4 certified firewall/VPN compact appliance! http://www.cyberguard.com/SOLUTIONS/Solutions_lx1.html ------_=_NextPart_001_01C19E8A.D2DF0F16 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 5.5.2650.12"> <TITLE>FreeBSD patch/packaging questions</TITLE> </HEAD> <BODY> <P><FONT SIZE=3D2 FACE=3D"Arial">Hi</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">I have a few questions regarding = non-kernel FreeBSD patch distribution. Any information is really = appreciated. If all of this is documented somewhere, I would be = happy to do the research if someone could point me to the document. = </FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">1 ) If I produced a product based on = FreeBSD 4.3, how would my customers get the patches?</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">I can see there was a binary = distribution of the patches using pkg_add. This seems to work = very nicely in distributing patches to customers. However, this = process seemed to change with the openssh patch 01:63. The binary = distribution was for FreeBSD 4.4 only. How does one ship a binary = installation of that patch to their customers who are running = 4.3? (Same goes for patches 02:01 and 02:02.) The = customer's system does not have source. :-/</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">2) Do you provide a mechanism = where I can create my own binary installations using pkg_add?</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">It seems I can use pkg_create. = That seems to work fine, but can I get more information on the = packinglist file? Is creating a very simple packinglist such as = this for the pw patch seem okay? (There seemed to be a lot of = more complex options. I am not too sure about the mtree and = unexec lines.)</FONT></P> <UL><UL> <P><FONT SIZE=3D2 FACE=3D"Arial">@cwd /usr/sbin</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">@srcdir source_directory</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">@owner root</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">@group wheel</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">@mode 555</FONT> <BR><FONT SIZE=3D2 FACE=3D"Arial">pw</FONT> </P> </UL></UL> <P><FONT SIZE=3D2 FACE=3D"Arial">3) What about patches that patch = libraries which impact several executables? </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial">If there is a patch that patches a = library (similar to the old 01:40) patch, how do you know which = commands that it would impact and which to include in the binary = package? Would it be documented in the README?</FONT></P> <P><FONT SIZE=3D2 FACE=3D"Arial">Thanx!</FONT> </P> <P><FONT COLOR=3D"#000000" SIZE=3D1 FACE=3D"Tahoma">Beth Reid</FONT> <BR><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Tahoma">CyberGuard = Corporation</FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Tahoma">phone: 954-958-3900 x3230</FONT> <BR><FONT SIZE=3D2 FACE=3D"Tahoma">email: breid@cyberguard.com</FONT> <BR><FONT SIZE=3D2 FACE=3D"Tahoma">fax: 954-958-3901</FONT> </P> <BR> <P><B><I><FONT COLOR=3D"#FF0000" SIZE=3D2 FACE=3D"Arial">See the LX, a = new, low-cost EAL4 certified firewall/VPN compact = appliance!</FONT></I></B><I></I> <BR><U><B><FONT COLOR=3D"#0000FF" SIZE=3D1 FACE=3D"Arial"><A = HREF=3D"http://www.cyberguard.com/SOLUTIONS/Solutions_lx1.html" = TARGET=3D"_blank">http://www.cyberguard.com/SOLUTIONS/Solutions_lx1.html= </A></FONT></B></U><B></B> </P> </BODY> </HTML> ------_=_NextPart_001_01C19E8A.D2DF0F16-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F767BDFE817ED411A32100D0B7694A9FAD1BBA>