From owner-freebsd-current@freebsd.org Fri Jan 8 02:06:36 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10769A678A3 for ; Fri, 8 Jan 2016 02:06:36 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD8201AA0; Fri, 8 Jan 2016 02:06:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id y66so326525996oig.0; Thu, 07 Jan 2016 18:06:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=KWpHtpjjr4GDPCqT1iL3tzZICuXC+DIpQhSDbVPbrwk=; b=MJ80pbaNBjtfF1mzcEWJZDkkzMRDbHMXRBd0xVIx2eTsx5DfBSUB3A47iwQPaCMZCB 0MF6yzu6W4ccXy5TMnDKYM8bqN4OEp/lYZrXBwPP88YEJtq2a6bxzbgLQj6xRCo38YeW nwwN/Jyz6whjHfZ5SoNsqAnd+PSxHd+ou0NA6y4GLyj8A7dC9B1fE8UT23SitsVW72uK R3rLn43Ivr0rDv5nwBFIQJ21u7vEzu9JNiiYfF6jvS640apFnPGIBM54eiZHVkESH/1a Q+8mGGs42Q/zlpumxRbETImaZrqvdJmblvFrY44w+eYO93yxNSimFxVnNaPaUWn1lJmb DImg== MIME-Version: 1.0 X-Received: by 10.202.56.3 with SMTP id f3mr74987713oia.65.1452218794957; Thu, 07 Jan 2016 18:06:34 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.202.98.131 with HTTP; Thu, 7 Jan 2016 18:06:34 -0800 (PST) In-Reply-To: <20160107114950.GA2808@c720-r285885-amd64> References: <20160107014958.GA1697@c720-r285885-amd64> <40C37099-59AA-4A6B-9E7E-7926AD16A104@freebsd.org> <20160107114950.GA2808@c720-r285885-amd64> Date: Thu, 7 Jan 2016 18:06:34 -0800 X-Google-Sender-Auth: akNPoKrROdbhvuiKDjvQk_WQq3c Message-ID: Subject: Re: after update to r292778 no interface ath0 and wlan0 From: Kevin Oberman To: Matthias Apitz , Michael Gmelin , FreeBSD Current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 02:06:36 -0000 On Thu, Jan 7, 2016 at 3:49 AM, Matthias Apitz wrote: > El d=C3=ADa Thursday, January 07, 2016 a las 03:04:24AM +0100, Michael Gm= elin > escribi=C3=B3: > > > > wlans_ath0=3D"wlan0" > > > ifconfig_wlan0=3D"WPA DHCP" > > > > > > (i.e. unchanged as they worked before); in dmesg the aht0 is shown as > > > usual with: > > > > > > > See > https://lists.freebsd.org/pipermail/freebsd-net/2015-August/042976.html > and don't forget to run mergemaster to update rc scripts. > > A side question or remark on this: Why I do understand that certain > files (like: /etc/group, /etc/motd, ...) must be overwritten or merged or > ignored > with the files from the new installworld, I do not understand why the > script files in /etc/rc.d or /etc are not just overwritten with the new > files; > > these files are not meant to be changed by the system admin, they are > just new software; > > matthias > I have no idea here you get this idea. The whole idea of /etc is to hold files that configure a system that might be managed and modified by the admin. You had better know what you are doing before editing these but I have had many files in various systems that I customized and that was the whole idea of the /etc directory at least back in BSD4.2 (NOT FreeBSD!). The reason we have /etc/defaults is to have a safe, reasonable set of defaults that should NOT be modified. If FreeBSD update or any other mechanism simply over-wrote the files that had been modified in /etc, I could no longer use them as I have NEVER had a system where at least a few files in /etc were modified. Yes, that includes scripts. /etc/rc.s are a bit less likely to be edited, but I used to have quite a number that I modified on my personal systems to modify shutdown actions. Still, I agree that this is a bit unusual and updating by default might be reasonable.