From owner-freebsd-arch Mon Mar 26 23: 9:43 2001 Delivered-To: freebsd-arch@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id ED11937B719 for ; Mon, 26 Mar 2001 23:09:38 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id XAA08662; Mon, 26 Mar 2001 23:08:52 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda08657; Mon Mar 26 23:08:35 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f2R786o63811; Mon, 26 Mar 2001 23:08:06 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdB63807; Mon Mar 26 23:07:45 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.3/8.9.1) id f2R77SR08693; Mon, 26 Mar 2001 23:07:28 -0800 (PST) Message-Id: <200103270707.f2R77SR08693@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdjd8679; Mon Mar 26 23:07:06 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: Jack Rusher Cc: Cy Schubert - ITSD Open Systems Group , Andrew Reilly , Jordan Hubbard , jonathan@graehl.org, freebsd-arch@FreeBSD.ORG Subject: Re: configuration files, XML? In-reply-to: Your message of "Mon, 26 Mar 2001 19:24:47 PST." <3AC007FF.1D9F60A3@integratus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Mar 2001 23:07:06 -0800 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This thread so far has discussed some general ideas and generally beat around the bush. What specifically are you proposing? What would specifically be changed, in which way will it specifically be changed, and what will be done to mitigate the effect of the proposed changes to heterogeneous environments like mine that need to leverage the time of staff across various platform types? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC In message <3AC007FF.1D9F60A3@integratus.com>, Jack Rusher writes: > Cy Schubert - ITSD Open Systems Group wrote: > > > > solutions to reduce my workload. There are enough issues of platform > > incompatibility between the various UNIX platforms out there without > > going out of our way to create new incompatibilities. > > This is the primary reason for the offense. :-) "I don't want to > learn another way of doing things, I want this OS to behave like my > other POSIX OSes, etc." These are all good reasons not to want to do > this sort of thing. On the other hand, these are exactly the reasons > that Rob Pike is mostly right when he says that OS work is stagnant (ok, > he says it's dead). > > If you're going to innovate, you're going to break compatibility. > That's the nature of the beast. Unfortunately, it means that only a > non-UNIX like Plan9 or (dare I say it?) Linux will be able to make > fundamental change without pissing people off. I guess in the Linux > case, it's just that they don't mind pissing people off. ;-) > > The caveat to the above is that people are accepting of good ideas > that don't change the Old Way(tm). I would cite kqueue() as a nice idea > that doesn't port to anyone else's playground. It doesn't scare anybody > because it doesn't displace any of the old ways of doing things. > Unfortunately, some things can't be done that way. > > > In regards to FreeBSD-only config files like login.conf or > > login.access, I don't care what format they are in as long as it's > > intelligent. > > Which makes them a great place to start. I was also thinking of > writing up a little PAM module that does authentication against an XML > version of the passwd/shadow files. We are lucky enough to have > loadable module support for that subsystem, so it's a nice place to > implement a demo. > > > Rather than stand in the way of progress, having the new config file > > format adopted by most of the major vendors would go a long way to > > mitigate many fears people have about a new super-config file format. > > We would obviously want everybody to join us in using the new > configuration format/tools. I do think somebody needs to belly up to > the bar and order the first drink, though. > > > Another way we can mitigate these concerns is to support two formats > > until the other popular UNIX systems (Solaris, AIX, Tru64-UNIX, HP/UX, > > This strikes me as hard for the subsystems that don't have an API in > place that governs how they access files. What are some of your ideas > of how you would do this? > > > Don't read into this that I am offended that the config file format may > > I don't take it that way at all. This is really good feedback from > someone who is thinking carefully about the problem. > > > Thanks, > > -- > Jack Rusher, Senior Engineer | mailto:jar@integratus.com > Integratus, Inc. | http://www.integratus.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message