DragonFly BSD
DragonFly bugs List (threaded) for 2005-02
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: make upgrade overwrites /etc/mail/mailer.conf

From: Jonas Trollvik <jontro@xxxxxxxxx>
Date: Tue, 8 Feb 2005 01:11:13 +0100

How about just appending the service to /etc/services if it doesnt
exist and re sort it?
Or do it in some other similar fashion as a new user is added to
/etc/passwd in a system upgrade?

On Mon, 7 Feb 2005 15:49:43 -0800 (PST), Matthew Dillon
<dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
> :On Mon, Feb 07, 2005 at 03:12:43PM -0800, Matthew Dillon wrote:
> :>     getservbyname() and getservbyport() could use a simple 'check
> :>     /etc/services first then check /etc/defaults/services' scheme.
> :>     In getservent()'s case it would have to merge the two files
> :>     together (maybe on the fly if we were to require that the entries
> :>     be sorted by port) to produce a single coherent result.
> :
> :I'd still like to comment out users in /etc/passwd or services
> :in /etc/services, which would not be possible if they are virtually
> :merged.
> :
> :Joerg
>    I was thinking 'on the fly', but it's a good question... how does
>    one 'comment out' a service in /etc/services that exists in
>    /etc/defaults/services.  Detecting '#...' in /etc/services and
>    making that also remove the line from /etc/defaults/services would lead
>    to mass confusion.
>    I don't think it's necessary that we support service removal
>    immediately, but if we were to do it I would suggest something like
>    '-<servicename> ...' in /etc/services to remove a service entirely.
>    Still not perfect, but workable if the number of services being removed
>    is fairly small.  A major ripout would pretty much require overwriting
>    the file in /etc/defaults and I don't think it would make sense to
>    try to hack up the build system to support that kind of thing.
>                                        -Matt
>                                        Matthew Dillon
>                                        <dillon@xxxxxxxxxxxxx>

[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]