From owner-freebsd-stable Fri Jan 1 11:12:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12052 for freebsd-stable-outgoing; Fri, 1 Jan 1999 11:12:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from www.inx.de (www.inx.de [195.21.255.251]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12047 for ; Fri, 1 Jan 1999 11:12:29 -0800 (PST) (envelope-from jnickelsen@acm.org) Received: by www.inx.de (Smail3.2.0.96inx) from [194.42.65.35] (194.42.65.35) with esmtp id ; Fri, 1 Jan 1999 20:12:04 +0100 (MET) X-Sender: jn@berlin.snafu.de Message-Id: In-Reply-To: <14812.915093240@zippy.cdrom.com> References: Your message of "Thu, 31 Dec 1998 14:54:07 +0800." <199812310654.OAA89915@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 1 Jan 1999 14:55:00 +0100 To: "Jordan K. Hubbard" From: Juergen Nickelsen Subject: Re: Final upgrades of tools in 2.2-STABLE (Re: Sendmail 8.9.1a ) Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >[...] I'd prefer to avoid bind or anything else which >requires intervention. Upgrading sendmail would be fine. :) But that *does* require intervention, since because of the the new anti-relay-rules you have to list your domain in the file of domains you do relay for. This is, of course, a good thing and the reason I installed 8.9.1 after someone complained about one of the ~ 29700 messages relayed through our machine. :-( But a simple upgrade without intervention does break things. Wouldn't it be enough to include 8.9.1 as a port (if it isn't already)? Greetings, Juergen. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.5.3i for non-commercial use iQA/AwUBNozTkfxneYZkCUPbEQIYqACgt5LgiIOLn8DfYWKjS7VCUbZaBVkAn1TI sNZ4hCp821jI5TFBo8klDvBv =2+PU -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jan 1 22:26:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15267 for freebsd-stable-outgoing; Fri, 1 Jan 1999 22:26:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from animal.blarg.net (animal.blarg.net [206.124.128.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15259 for ; Fri, 1 Jan 1999 22:26:03 -0800 (PST) (envelope-from kosmos@animal.blarg.net) Received: from localhost (kosmos@localhost) by animal.blarg.net (8.9.1/8.9.1) with SMTP id WAA11495 for ; Fri, 1 Jan 1999 22:25:39 -0800 Date: Fri, 1 Jan 1999 22:25:39 -0800 (PST) From: Allan Bowhill To: stable@FreeBSD.ORG Subject: managing configuration changes with SGML/XML Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have thoughts about using SGML/XML to address problems that arise from changes made to configuration files? If package authors or maintainers each supplied a default configuration file as an SGML document instance, and a structural specification for that file as an SGML DTD, wouldn't it make changes to the content or structure of configurations easier to manage? For instance, after a CVS update, if a system operator could validate configurations against the most current DTD for each package, it would be more convenient than using diff to manually merge *etc changes. Diff triggers a lot of false-positives on unimportant information. Structural validation gets closer to the point than diff, because as long as the document instance conforms to the author's specification, it doesn't matter how the system operator's particular version of a configuration file measures up to the system default, (or sample configuration.) The files really shouldn't be compared directly, becuase they don't necesssarily share a direct relationship to each other. In the case that the author changed the package's behavior radically enough so it resulted in an important change in the configuration specification (e.g an option was deleted, modified or added; or the file's structure was changed) the package's DTD would have to be changed, too. So after a CVS update, a change in a DTD would have to trigger some kind of structured comparison to inform the system operator of changes in the configuration specification, and how it affects his current configuration files. If that could be done, changes to configuration files could possibly be made in-place, without a lot of intermediary steps after a build. Comments on this are welcome... --Allan kosmos@blarg.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jan 2 07:06:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24142 for freebsd-stable-outgoing; Sat, 2 Jan 1999 07:06:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA24115 for ; Sat, 2 Jan 1999 07:06:41 -0800 (PST) (envelope-from berend@pobox.com) Received: from auke.nederware.nl (nederware.nl [194.109.55.62]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id QAA19476; Sat, 2 Jan 1999 16:06:15 +0100 (CET) Received: from bmach (bmach.nederware.nl [192.168.33.3]) by auke.nederware.nl (8.8.8/8.8.8) with SMTP id PAA17309; Sat, 2 Jan 1999 15:57:25 +0100 (CET) (envelope-from berend@pobox.com) From: "Berend de Boer" To: "'Chris Silva'" , "Freebsd-Stable" Subject: RE: Upgrade from 2.2.8 --> 3.0 Date: Sat, 2 Jan 1999 15:57:19 +0100 Message-ID: <000401be3660$32782ed0$0321a8c0@bmach.nederware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 In-Reply-To: <000101be34e9$09141d10$ddb5a8b6@mis2> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's the proper way, and or the easiest way to upgrade from > my 2.2.8 to the release of 3.0 in Jan? Upgrading from 2.2.x to 3.0 is a hell of a job because of the switch to .elf. But if you don't have X I suggest you to try out the upgrade option in the menu presented to you by the install program on the cdrom. However your /etc directory isn't completely upgraded so bring in every change in /etc/upgrade as well, especially the stuff in rc and rc.conf. Groetjes, Berend. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message