From owner-freebsd-arch@freebsd.org Fri Feb 15 17:41:31 2019 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A187F14E2203 for ; Fri, 15 Feb 2019 17:41:31 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AC34B73967 for ; Fri, 15 Feb 2019 17:41:29 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id uhUEgQC3wMRX3uhUFgRm3s; Fri, 15 Feb 2019 10:41:21 -0700 X-Authority-Analysis: v=2.3 cv=TL87tGta c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=IkcTkHD0fZMA:10 a=CFTnQlWoA9kA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=5MujDi1ExtQV1IlaB0QA:9 a=QEXdDO2ut3YA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [192.168.1.102] (S0106002401cb186f.gv.shawcable.net [70.67.125.17]) by spqr.komquats.com (Postfix) with ESMTPSA id 75EE91DFD; Fri, 15 Feb 2019 09:41:17 -0800 (PST) Date: Fri, 15 Feb 2019 09:41:16 -0800 User-Agent: K-9 Mail for Android In-Reply-To: <20190215155026.GA9317@troutmask.apl.washington.edu> References: <20190214180101.GB67712@troutmask.apl.washington.edu> <20190214182419.GA67872@troutmask.apl.washington.edu> <20190214190244.GA68143@troutmask.apl.washington.edu> <20190214191739.GA68371@troutmask.apl.washington.edu> <20190214225810.kmfxzeuvr7t7gget@smtp.freebsd.org> <20190214233000.GA2752@troutmask.apl.washington.edu> <3b0ba403-ff96-8c94-6d98-40165473d1f3@gmail.com> <20190215155026.GA9317@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: "DRM removal soon" is premature To: sgk@troutmask.apl.washington.edu, Steve Kargl , Johannes Lundberg CC: freebsd-arch@freebsd.org From: Cy Schubert Message-ID: <6531965D-0E8D-479F-8773-F166651C9334@cschubert.com> X-CMAE-Envelope: MS4wfEDNsjx2SL/zoiIBGoAug18K2/cQrktn42cgwO3pXW5Z5v1hqreT5jLYdZ4ORf89EMqYQtWE2MPx9owH+3Y/sQMmpC7gbRxl+SSrzcDIEPzl9uE5YiP2 UiNDfhQ2kgQubPhoP1D8hnPGwk0oKeJebzF9o6itmfo5LJnL6ZI8Zpz8Zdx+sMeC7oEyRMaJUiDThX4Z7EW/jEYs4DlTA7J7d0nBkc3Z39z/79fMi2LGDYOb 0l7v98blVXQ6p7nSCdwp5C0n+aIsPmpYwbMoTfCgXC8= X-Rspamd-Queue-Id: AC34B73967 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-5.00 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; IP_SCORE(-1.89)[ip: (-4.86), ipnet: 64.59.128.0/20(-2.54), asn: 6327(-1.98), country: CA(-0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[spqr.komquats.com]; NEURAL_HAM_SHORT(-0.89)[-0.891,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[9.134.59.64.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:6327, ipnet:64.59.128.0/20, country:CA]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[17.125.67.70.zen.spamhaus.org : 127.0.0.11] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 17:41:32 -0000 On February 15, 2019 7:50:26 AM PST, Steve Kargl wrote: >On Fri, Feb 15, 2019 at 09:07:08AM +0000, Johannes Lundberg wrote: >>=20 >> This happens all time for me with virtualbox-kmod as well in current=2E >> Changes to src breaks certain (kmod) ports and there's always a delay >> until they are fixed=2E This is life in -CURRENT=2E I accept this and >don't >> go bitching to virtualbox-kmod maintainers about it=2E Your usage is an >> edge case so naturally there will be a longer delay before breakage >is >> noticed, until we can get automated CI up and running (even so, there >> will be a delay)=2E >>=20 > >Was virtualbox-kmod every a part of the FreeBSD base sytem? > >drm2 was a part of the base system and it was functional >until it was unhooked from the build=2E The issue with the >merged PAE vs=2E non-PAE i386/pmap=2Eh would have been identified >prior to it being committed if either drm2 had not been=20 >unhooked or if an exp-run over ports was run=2E > >I also don't see how this is an edge case=2E A part of drm2 >removal was the creation of a port, so those who don't have >the luxury of updating hardware every year can continue to >use drm2=2E If this type of breakage of functionality formerly=20 >in base, and the name calling of someone pointing out the >breakage, is the new norm, then it is a harbinger of doom for >pkg-base=2E Just to add a data point, I use drm-current on a 13 year old i386 laptop r= unning -current, used as an i386 test platform=2E Keeping it in sync with m= y amd64 platforms=2E --=20 Pardon the typos and autocorrect, small keyboard in use=2E Cheers, Cy Schubert FreeBSD UNIX: Web: http://www=2EFreeBSD=2Eorg The need of the many outweighs the greed of the few=2E