From owner-freebsd-arch@freebsd.org Sun Jun 10 19:40:53 2018 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 BE708101ABC0 for ; Sun, 10 Jun 2018 19:40:53 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 538677413A for ; Sun, 10 Jun 2018 19:40:53 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mailman.ysv.freebsd.org (Postfix) id 1747B101ABB9; Sun, 10 Jun 2018 19:40:53 +0000 (UTC) Delivered-To: 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 0351F101ABB8 for ; Sun, 10 Jun 2018 19:40:53 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 8F3AB74136 for ; Sun, 10 Jun 2018 19:40:52 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x22c.google.com with SMTP id x128-v6so5788197ybg.3 for ; Sun, 10 Jun 2018 12:40:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to; bh=dU/wcpBRUBf5YfH+qPVEgLmwakFFo9nFU4AXqe+74ns=; b=pei4uV9ssTnsPAdnFFreReyS/SDMBfdxmhzPOHrToNvx9WsuwvJ5XLm4MyIXJxMmNx uN2q21FM1zm60cFH1Lt/T5Nf4imwncPXHsYK1fX2rWVTbKAok/DgYooFrZAo3PHrTzZY HdpAngPPaupUWspHAH+E0ikmeSWjf9VwDL/lY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dU/wcpBRUBf5YfH+qPVEgLmwakFFo9nFU4AXqe+74ns=; b=thYG51UFMWKrZHX8SgEDiQUoN38r1VrhHcPeryXsFg0f1Qi+m4XCvqEcUHkZMx8Xyq JJDzO1xqSqqDY3ncyyflmG7IMMZ5yhtZRWrrhhxulvLhXZjA+byrD6QzcXxi5knxa/wy bJZj0Biu4n+dnXlZLR3q8wKSLxDDvOXQfztVc/5A15rvrRfO/hjZHy/58tVGIg9VIWQt T6YDOwOVhIcfR5r/BrpgkCPL5EbdVNxvv+uydAhGMltZEf1xOckHGvrWMLk6LEAOML+j tky764sq1fMV0pR0gUShUM5UStnvXn+Jd/Vk5QSp9uvcYq7ujeH99niwnVbfQTNdGz0k B6/g== X-Gm-Message-State: APt69E3uN7pxU/A8fjpPHw+nag96rt6BJcj94wU2a+hwrS4A2IQgtP9s gflxh/H5xdIiDve/TxIupyil6N2Q0+CEYh4w6nSlLaNM X-Google-Smtp-Source: ADUXVKIr2LEWZww+5s2ENGeiVAMyKKeQD6H5HEKXz1K4u8WwmXIubfcyTCEIRIuWR5p+iPu2c9rPV4oFS/WP3WMs5/s= X-Received: by 2002:a25:2605:: with SMTP id m5-v6mr8805411ybm.89.1528659651613; Sun, 10 Jun 2018 12:40:51 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sun, 10 Jun 2018 12:40:21 -0700 (PDT) From: Eitan Adler Date: Sun, 10 Jun 2018 12:40:21 -0700 Message-ID: Subject: upstream for contrib/tzcode/stdtme? To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2018 19:40:53 -0000 What's the upstream for contrib/tzcode/stdtme? There are a couple of PRs for it and I'd like to either update, fix upstream, or move to non-contrib & fix. -- Eitan Adler From owner-freebsd-arch@freebsd.org Mon Jun 11 02:04:38 2018 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 373CE100F021 for ; Mon, 11 Jun 2018 02:04:38 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C539285081 for ; Mon, 11 Jun 2018 02:04:37 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 862FD100F01E; Mon, 11 Jun 2018 02:04:37 +0000 (UTC) Delivered-To: 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 72461100F01D for ; Mon, 11 Jun 2018 02:04:37 +0000 (UTC) (envelope-from pfg@FreeBSD.org) Received: from sonic304-23.consmr.mail.gq1.yahoo.com (sonic304-23.consmr.mail.gq1.yahoo.com [98.137.68.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC6A98507E for ; Mon, 11 Jun 2018 02:04:36 +0000 (UTC) (envelope-from pfg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1528682669; bh=iRSFJFAaqZV3OWi3Fe+uEDU4gw+pIY0wU3aMRWRyHEA=; h=From:Subject:To:Cc:Date:From:Subject; b=fU/tQOoKm5ZtQ0/cgAuoB/+V0TrnGzF008wJweXPu7V61mEuQoyUkwHS5hVOAmC1xOYAHuvZrpIhbXoMURMLYN6udI3tEQ+rqlkG/oIfOUQCozIrOEf9TqwVzMoiIRG8QaY+cpF6Bkqdg0VVbm2tkAoauLo8gEPvDbUxnFSlVvmK/l+UoEMCrLTaLKyva3fp9oMrOhJirrUTBq8ui65Inwz374MZZDskYmbRfCogeWcZJnWsqYiQgRFMmucrJ5N1Xl5aD4sZNlG2/U7VKSzIAzKx77qlmr/LIa/zWtPpKbEvaepoaDQbN1cGHz9AjbjdTyrTr8NZzYJygm2uRbQnVw== X-YMail-OSG: L0rFxfQVM1locU97LDsRoDsW2hveqCFt7sboVI570ki4nDTT9PMlovhAwPOCM_3 ax1Z6lUmPiFegufM.LqPoaALwtE1LEJHxzapn2UAd_L6r3_3csOuhA5qpNsurt8puVD4iN_8IFKR kjsMVWZt.WKwsUaOCznYepVDuEf5zyIa6DQrVlwwDm_YSaDq3_iEMtIzNxlV7Z4gJZitqc97Hm8X SKBovZwDFJcWSfrdO2rT478hzNcMpPfeWGm_y8jIGrLThEA2wg51NhZuODSW6JuLdnWx4VJyN5cE iJib.xyJGRrjxAvk0etAp3iW1lkLmPIztwZpl5MiPuXAddg9xEGfqsEnJo6uO3qOccMfkuuwvAF6 _MrwfxljMKCiLPqLvdRcSbOvFlvFHwSqAKwELiz9RwgeHZ6vY7xQt7PGnJ4cK5ER4HlZCfNciEur YhhtjESoflFs9pDDsOAZs_cPy.mY0kPWO_Lz6VJCNSHJK6jEkFoju..gGZHSSqRG9frD6j1mLmAV b4AYwzbNIFnfnC2GWSYJDeSaFaWHIVS4ftPCIRFHPyagVYtlmGPM6CDty70yIejF0_e_G2MkiX_q xlllfou4bu8U4Ve3a_lSaLeWXqSrmxk1wL8a3H5UI8DJ3Ivw23vaI2NA0T_cML1uTJB7_vF8SQa8 W85T38O2_JjSGmw9xWYlQLSMcC8Cc4kPdY_t.7Nm8LsnayPbFITUvRSciEi9UImL27yn59DhOTsQ 3W0krhZMC3tzfvrWZc8hQMHGmNM4HK36.d878eQmSwxLsYREUbA1kfM6ajMiYYfP4nfUDTpyujgB C6wJWCR3zbKV1pi7TEoys1TFW.WzEEHz1AE8e4tgaLfMf5el7of3MVIGtXO4Hcdh0ziDBNk9vEvo nQzXyUxL.TXqr_hplsovnnnwb.ZPcP4vJFt42FX9YFlBsJnJWscSgqK22FUQY_Y0cm3Zer7wlcw- - Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Mon, 11 Jun 2018 02:04:29 +0000 Received: from 181.52.72.201 (EHLO [192.168.0.6]) ([181.52.72.201]) by smtp421.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID fc346b4f83ebeb657320c7951fac437a; Mon, 11 Jun 2018 02:04:27 +0000 (UTC) From: Pedro Giffuni Subject: Re: upstream for contrib/tzcode/stdtme? To: Eitan Adler Cc: "freebsd-arch@freebsd.org" Message-ID: <97d539d8-a38c-8389-ba91-90d23356bd36@FreeBSD.org> Date: Sun, 10 Jun 2018 21:04:28 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2018 02:04:38 -0000 > What's the upstream for contrib/tzcode/stdtme? > > There are a couple of PRs for it and I'd like to either update, fix > upstream, or move to non-contrib & fix. > > -- > Eitan Adler Hi, I think it's here https://www.iana.org/time-zones or here (depending on how much bleeding edge you want to go): https://github.com/eggert/tz I recall we have old versions of the same files in libc too, plus some modifications we got from Apple and Illumos. NetBSD also has some updates of their own. Pedro.. From owner-freebsd-arch@freebsd.org Mon Jun 11 02:52:34 2018 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 55F921015754 for ; Mon, 11 Jun 2018 02:52:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DF1BE87960 for ; Mon, 11 Jun 2018 02:52:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id A313E1015750; Mon, 11 Jun 2018 02:52:33 +0000 (UTC) Delivered-To: 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 7F1901015748 for ; Mon, 11 Jun 2018 02:52:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 127588795B for ; Mon, 11 Jun 2018 02:52:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id a3-v6so9202150itd.0 for ; Sun, 10 Jun 2018 19:52:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7WTnrU/f1iI+6csFQm/NFfDQw8R+Ui9mCOBKkz6xaFA=; b=d3ja3aUvpiEodByjE56R1D0A1W/yjVR3LE0VI+kTXt6b5eha3QC/NEl7QciNcktfM5 Pwp1jlLZ6Jd9buTTp/AFCkHOigcOCMFX/yD0OtYeq7EzxfWfPtz9X+wOWtFfqng7+DAG 15VfxgS3gQr7izIQeMH2Je3g1T/N7CDccsrdh62eZtImyuFjbor7cerIFPHibJwbTXHG MKQocg0nJyl2f1L7fwpphby2wbIGVXkANF8PkrmznFV6gvSbdUEJPql4eH9tlX8uZpFm EVT9cy5CcMcg/smk/gSedTyKcNSEFmwKNUgCohcu0XGjTke/ZXEQ2pdwpCQKPFi2ZUM8 qB7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7WTnrU/f1iI+6csFQm/NFfDQw8R+Ui9mCOBKkz6xaFA=; b=s9kAZFoWdxpOsmiLP3DH8Btk4gwvTx2TWZAeunh0+8Tsn5G/mJ0UVGmaHNRdXNBDa9 2avPejO+4MNWjZWuBlDvnsbeaWKXtcgxqn4+prB1rml1icu9LYcK4UxpDrob81ahERPi KJSEdzojQHObX33GoJ0oNpjLtsjOPdvoDwthabAnwvbZhf25WRRigkH+LnV0tZjivUtL DhZ1Ft+8EfnFqeT4g8OmPMi3ZJm3TEFuD2kpICTFlJ38Ir3iLAiJQEnY793RFjsL4NJe RqlOHQ1W5JfrckYi3dERC1mdN3pmXznEPPZ545XbKLw1jmPglQyieqCahXcHsUsuRLEe cyBw== X-Gm-Message-State: APt69E1BdVYKLraAMNbOLwAoQcMCJ49J3czlBvHLFWFQj7BETK/i9MeJ mzttXwdBHYiF+ulOUrBEEJTgP1f1MT6yNUfsmqCR+Q== X-Google-Smtp-Source: ADUXVKK2Cwy4vSpQkiTcEO7SmSltnZOeheOUuBwN4mEr7pcBlndo8EVCroRhZeWCYeXpSae50si6Bt08ePVoE8TmLEQ= X-Received: by 2002:a24:8201:: with SMTP id t1-v6mr9312773itd.51.1528685552359; Sun, 10 Jun 2018 19:52:32 -0700 (PDT) MIME-Version: 1.0 References: <97d539d8-a38c-8389-ba91-90d23356bd36@FreeBSD.org> In-Reply-To: <97d539d8-a38c-8389-ba91-90d23356bd36@FreeBSD.org> From: Warner Losh Date: Sun, 10 Jun 2018 20:52:21 -0600 Message-ID: Subject: Re: upstream for contrib/tzcode/stdtme? To: Pedro Giffuni Cc: Eitan Adler , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2018 02:52:34 -0000 On Sun, Jun 10, 2018, 8:05 PM Pedro Giffuni wrote: > > What's the upstream for contrib/tzcode/stdtme? > > > > There are a couple of PRs for it and I'd like to either update, fix > > upstream, or move to non-contrib & fix. > > > > -- > > Eitan Adler > Hi, > > I think it's here > > https://www.iana.org/time-zones > > or here (depending on how much bleeding edge you want to go): > > https://github.com/eggert/tz > > I recall we have old versions of the same files in libc too, plus some > modifications we got from Apple and Illumos. > > NetBSD also has some updates of their own. > Plus some fixes of our own... Warner Pedro.. > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-arch@freebsd.org Mon Jun 11 08:04:26 2018 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 8139A101C7EA for ; Mon, 11 Jun 2018 08:04:26 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 070CB74AFC for ; Mon, 11 Jun 2018 08:04:26 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BBCA9101C7E5; Mon, 11 Jun 2018 08:04:25 +0000 (UTC) Delivered-To: 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 97CC8101C7E2 for ; Mon, 11 Jun 2018 08:04:25 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::22e]) (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 2A64174AF8; Mon, 11 Jun 2018 08:04:25 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-ot0-x22e.google.com with SMTP id n3-v6so22724562ota.5; Mon, 11 Jun 2018 01:04:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P6yWQlcmH0h89bdn80e5bdDileQ1hPQvZR22X2RGYyg=; b=oBNLhXMD0/96PonMuXN7tLquHwwf6GypmNffu5nemLIvt1J/FAGj5biIFzMs0EbT+/ VNm1kgI43vPWEQOHlE3wr+ZYGeCj40qCccdkdFMGVnb2Z5udkLWDDG+cw7kDJE5//yTD xNY7Qy71foIyN5PA3Ug5J5D6/6sUMPVkXUexIKveW51gP0xFmwb430RzI1JMynzqktKw M8jpDQvrGdJp4JGgCBCss0a9LjsXX6CCodKCsU67juyRcfYGZK9QXDJNu8K1L+ChzHig ywyenFg2Y+yzUiNesWy60un3r0kgazwTkbTEmzmVDYGwdqnEvN2fA18Avahwh85eVit7 Yi9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=P6yWQlcmH0h89bdn80e5bdDileQ1hPQvZR22X2RGYyg=; b=hhpQWacG8erjD4YGbttxSZg/PmgADF3EUalctdPwP48zLQLUrpQRupnNWOQEEwOaXH Yrt/87fzKBbzfWJYZ66oJQdUyExvcPBubo9mIyFjdyaErS5idhyU5n6dphkwhJR7nmtH yOQh3MTxl7lYeecHB22N/nk0c94ViTphJSMlwQ7kw+0RfT2zCXiWJsOQYhjG6F3EkU8k DFySw15pBRdBdSC/YpN6NpDL1MVsd8SrOIsaD0bQOndEVTUgKUTuwXWkiQci7BjBa0/g DNo9vxXK67sQbvnPXLXB6brVLtEiTit6C890DmxwmJHSK6xWzHmEJyt2lv1gVPehEkEf h3kA== X-Gm-Message-State: APt69E3n2zqGIK/V6d0dBRyRIsNwTaS9YB5JElpJop40fP/HebV2QohS Dw5nKciU+S8D1WfgeX8qBSNvV/qK03j3FWysLlaVLg== X-Google-Smtp-Source: ADUXVKKn2Wosr9z+kq0fa/KXDuZuDH46bh+aP7IYhE4LQ6kJVC9bNaFZ4Nyu18lX+1vzWDKhmLSW7/RYZFq4hUy1ll4= X-Received: by 2002:a9d:350a:: with SMTP id o10-v6mr8723127otc.247.1528704264343; Mon, 11 Jun 2018 01:04:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:396:0:0:0:0:0 with HTTP; Mon, 11 Jun 2018 01:03:43 -0700 (PDT) In-Reply-To: <97d539d8-a38c-8389-ba91-90d23356bd36@FreeBSD.org> References: <97d539d8-a38c-8389-ba91-90d23356bd36@FreeBSD.org> From: Mehmet Erol Sanliturk Date: Mon, 11 Jun 2018 11:03:43 +0300 Message-ID: Subject: Re: upstream for contrib/tzcode/stdtme? To: Pedro Giffuni Cc: Eitan Adler , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2018 08:04:26 -0000 On Mon, Jun 11, 2018 at 5:04 AM, Pedro Giffuni wrote: > What's the upstream for contrib/tzcode/stdtme? >> >> There are a couple of PRs for it and I'd like to either update, fix >> upstream, or move to non-contrib & fix. >> >> -- >> Eitan Adler >> > Hi, > > I think it's here > > https://www.iana.org/time-zones > > or here (depending on how much bleeding edge you want to go): > > https://github.com/eggert/tz > > I recall we have old versions of the same files in libc too, plus some > modifications we got from Apple and Illumos. > > NetBSD also has some updates of their own. > > Pedro.. > > _______________________________________________ > > In page https://data.iana.org/time-zones/tz-link.html ( Sources for time zone and daylight saving time data ) the following is written : " Changes to the tz database The tz code and data are by no means authoritative. If you find errors, please send changes to tz@iana.org, the time zone mailing list. You can also subscribe to it and browse the archive of old messages. " Mehmet Erol Sanliturk From owner-freebsd-arch@freebsd.org Wed Jun 13 16:55:03 2018 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 10152101D0CB for ; Wed, 13 Jun 2018 16:55:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 98F0A6D794 for ; Wed, 13 Jun 2018 16:55:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 54463101D0C7; Wed, 13 Jun 2018 16:55:02 +0000 (UTC) Delivered-To: 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 30039101D0C6 for ; Wed, 13 Jun 2018 16:55:02 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (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 B50076D791 for ; Wed, 13 Jun 2018 16:55:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x230.google.com with SMTP id s26-v6so4162182ioj.4 for ; Wed, 13 Jun 2018 09:55:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=2aKFOs8JpfpEWlQ4BkYEukDvz6TSfUjBH58hlnbY8pY=; b=NgfZPTcTlsyj8A09GewCUdYN7hSVfT/r1p6fwjAh1mlAxMjVDHmecIePNl7MDUPOst CxGX2jIW9SBonKn18WGL1iW7Er9VVfw0pb5VKk07Cjb2uMrrfm+gbSwkCCa+oPL2WJu8 yEJbxwNz8GhUhqq0UQ/NieSWCDQsCF2ycVRHmy+eQHO9abYZDkgXsa6G0wSB+0dmddBQ 3NEHv8FeJDUTQBWFG7NtN1GvzhAV9CxuwrYCqfDjlQL2yD1zaog7Tsh2Qa6jizPQ1wyr afdm2efMJ1VhQEnwZ2QlWVJehtQm5z72+RutK6U8LYc5FJtM+HvVOHR5i7hruA7mrUTQ tFQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=2aKFOs8JpfpEWlQ4BkYEukDvz6TSfUjBH58hlnbY8pY=; b=bG4rF9/IiQRgnETIEk0cTHxeC6Oq29lgffw2qhEei4N5sh+4gd3/5+r7DgTflKn15o JLwUGUFUx0kMy8MA+5YlfccI8T+tOFUazF65oUiQOraup3JrNaTJtN6GJQWWA4+F6opg MS1RjGwBO0BYPur+om9ZYYPuGgftusqmzaV7AobS/afzHWbTlU3xRSJo/GDzuLJbIhof /+F7AY+pDLafV4Ig766+0cv9nsumdGhSO16byx7LzDZ7vd16dGJiQpJZIB85j7AY/IeY S57BrspGGsXkqR7Uvac9QsAMF0sN1A08ZFe5oCE9FyfrH9vWHEioJtj/f/spavOvqbsw dhJg== X-Gm-Message-State: APt69E0VarL+/pbmZqa6/r96I+UsWLuPES3XsID8D2IxcSk+RqsqJWDn ddrb23hxo4BHeFH/jW4ii2QmgDwCMRjFh2zNqKQVlA== X-Google-Smtp-Source: ADUXVKIB8X4khFyZtvKy77a4MqFjSksaDyPRK7dTL6AYjmKW7J93VDI4kkG4nI8GQBhs4ohThOzFJC6K2ANT4aLRGQA= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr5465092ioo.168.1528908901061; Wed, 13 Jun 2018 09:55:01 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 09:55:00 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] From: Warner Losh Date: Wed, 13 Jun 2018 10:55:00 -0600 X-Google-Sender-Auth: h9Bm_aNWs8qMbqDzpb90_V9u4-Y Message-ID: Subject: Armeb removal before 12 To: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 16:55:03 -0000 I'd like to remove armeb before 12.0. It's poorly supported today. Nobody has tested the concurrency kit changes on it. And ck is now mandatory. We don't even know if it works or not. Last time we asked, it took quite a while to find users. It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to run in. The hardware was last made almost a decade ago. It uses non-standard non-mainstream boot loaders (boot technology has moved on from redboot). The cost of doing API sweeps, make universe runs, etc exceeds the benefit to the project. So, given all these factors, it sounds like a good candidate for retirement. Therefore, I'd like to remove it on July 15th. Comments? (please keep them on topic to this specific thing: there's other things that may also be past their freshness date, we'll discuss those in a separate thread). Warner From owner-freebsd-arch@freebsd.org Wed Jun 13 17:39:12 2018 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 26DE71021272 for ; Wed, 13 Jun 2018 17:39:12 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BA1626FB2A for ; Wed, 13 Jun 2018 17:39:11 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: by mailman.ysv.freebsd.org (Postfix) id 7D40A102126F; Wed, 13 Jun 2018 17:39:11 +0000 (UTC) Delivered-To: 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 6A088102126E; Wed, 13 Jun 2018 17:39:11 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E0CFE6FB29; Wed, 13 Jun 2018 17:39:10 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w5DHd6Ms040723; Wed, 13 Jun 2018 10:39:06 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w5DHd6sl040722; Wed, 13 Jun 2018 10:39:06 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> Subject: Re: Armeb removal before 12 In-Reply-To: To: Warner Losh Date: Wed, 13 Jun 2018 10:39:06 -0700 (PDT) CC: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 17:39:12 -0000 > I'd like to remove armeb before 12.0. > > It's poorly supported today. > > Nobody has tested the concurrency kit changes on it. And ck is now > mandatory. We don't even know if it works or not. > > Last time we asked, it took quite a while to find users. > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > run in. 64MB is usable for 32 bit archs, I have many VM's running in that configuration, so this item should not be in this list. > > The hardware was last made almost a decade ago. > > It uses non-standard non-mainstream boot loaders (boot technology has moved > on from redboot). > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > to the project. > > So, given all these factors, it sounds like a good candidate for retirement. > > Therefore, I'd like to remove it on July 15th. > > Comments? (please keep them on topic to this specific thing: there's other > things that may also be past their freshness date, we'll discuss those in a > separate thread). Given all the other valid reasons, I have no objection to removal of armeb. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-arch@freebsd.org Wed Jun 13 18:09:11 2018 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 6BF831001F99 for ; Wed, 13 Jun 2018 18:09:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E5A5D71367 for ; Wed, 13 Jun 2018 18:09:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id A903E1001F94; Wed, 13 Jun 2018 18:09:10 +0000 (UTC) Delivered-To: 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 6CAC81001F93 for ; Wed, 13 Jun 2018 18:09:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 0132671365 for ; Wed, 13 Jun 2018 18:09:10 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id j135-v6so5158582itj.1 for ; Wed, 13 Jun 2018 11:09:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=muxbzQ1ZTPT+EFm/vHUfyGom5Iz8xaAllgxQTKG9ndM=; b=n4p4/c5s7uH2WJHdQOks0NR2h79pMAY7ZwwiRDVqwAhtOigpDv6B/5mudgMwUUsEDL oblBjo8u7jFqpePoEO9YIz89sElsGuO5fJZF7I2651X78+mSZPU+EZVuSL+b7AapAuXe aMXXUdkYz+iu/enLXOUizy5tD+n3OTWa1J7+UEmU3pL5Xb56UgjrHismy37ZtcXfwWXF a/LSO6ibt7e0ds3gAODgUogHSq5mhMWatVcw709moAGqzhoXWCvNLnBRFLxAlbIrJDpi JQ8OzVKX7SqnjgCQXin0co79aPjLnY4huPbBJUNHGrIfssVgdk9S9alDF+K42qy9W2Np zTmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=muxbzQ1ZTPT+EFm/vHUfyGom5Iz8xaAllgxQTKG9ndM=; b=Y4DjVDlnFcY7A/5wKjE6uG93kuUOaPX0+CwwgIoNLx8MtER6sqF0VGk7NG7soFuVuy N4WH8QXMoEFF+/XDS2d7VCHN8rwm7smlBchWMdkwU5yn13UFFJc7FEE0oag92zksDWlj Y+BHZuEL+4rOVsgfIPGqKgFm5oIRSoHQyn43odtZsk5OOw5mTcWHGDYUlbDPodF+FMF2 vP2vPZreYPpj9D6c1W+XtXGaTgYdWfrG5P7NIpDQHWlSxD9o+zr0K4CMEzddSt1ZFUNk nlvdTgp02oPowvbYhC6qrwrqBV5JCeZGCCsHsxI/Prs6k9xrKkvlVV6QKOqjt7X9M0pW bDlA== X-Gm-Message-State: APt69E1lWmKj0LNLmpQtak7/ewyBqPbQIm8oRxfzfD3P05AggDyfH23l jiq7pgHAE55RbEvySDCksiKE2SMpb8+qGgfWpnY1ig== X-Google-Smtp-Source: ADUXVKLe2k3hwZePxE5LHTLGm/Zovta769QqVl6RW0I6/Oeo1XzFWwm28oRwFMeRryvbW11BrmY703nObJShJJkkZPs= X-Received: by 2002:a02:6348:: with SMTP id j69-v6mr838749jac.45.1528913349277; Wed, 13 Jun 2018 11:09:09 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 11:09:08 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Wed, 13 Jun 2018 12:09:08 -0600 X-Google-Sender-Auth: a-642fCUulx0DUc4ohG_ifEMUoU Message-ID: Subject: Re: Armeb removal before 12 To: "Rodney W. Grimes" Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:09:11 -0000 On Wed, Jun 13, 2018 at 11:39 AM, Rodney W. Grimes < freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > > I'd like to remove armeb before 12.0. > > > > It's poorly supported today. > > > > Nobody has tested the concurrency kit changes on it. And ck is now > > mandatory. We don't even know if it works or not. > > > > Last time we asked, it took quite a while to find users. > > > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > > run in. > > 64MB is usable for 32 bit archs, I have many VM's running in > that configuration, so this item should not be in this list. Yes and no. A VM is a different beast to a real box. arm requires more memory in general, and a little more on real machines. You can run it in 128MB and do useful things, but not very many things. One cannot, for example, run a wifi access point on arm in 128MB, at least on this hardware. Adrian's ultra-stripped down stuff might be possible, but nobody has ported it to this hardware despite it being ported to many weird things. Likewise with the ZRouter project. You could run a simple sshd / dns server on it, but there's lots of other alternatives for that which are dirt cheap. One can, with a lot of effort, do 64MB too, but it's more effort than for i386. Even at 64MB on i386, though, the number of things you can do is quite limited. You can't build anything on that machine. DNS + SSH is possible here as well, as long as the zones are too big. So I'll concede the point it's possible, and I'm not looking to make it not be possible. However, we do need to draw the line somewhere, and this is but one factor of many. Were it the only factor here, we wouldn't be contemplating removal. Most people want to do more ambitious things that can be done in 256MB is all I was trying to say. > The hardware was last made almost a decade ago. > > > > It uses non-standard non-mainstream boot loaders (boot technology has > moved > > on from redboot). > > > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > > to the project. > > > > So, given all these factors, it sounds like a good candidate for > retirement. > > > > Therefore, I'd like to remove it on July 15th. > > > > Comments? (please keep them on topic to this specific thing: there's > other > > things that may also be past their freshness date, we'll discuss those > in a > > separate thread). > > Given all the other valid reasons, I have no objection to removal of armeb. Excellent. Warner From owner-freebsd-arch@freebsd.org Wed Jun 13 18:23:25 2018 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 D4BAA10037ED for ; Wed, 13 Jun 2018 18:23:25 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 750C97210C for ; Wed, 13 Jun 2018 18:23:25 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 340B210037DF; Wed, 13 Jun 2018 18:23:25 +0000 (UTC) Delivered-To: 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 2172910037DE; Wed, 13 Jun 2018 18:23:25 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id B0F4A72109; Wed, 13 Jun 2018 18:23:24 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 015AC14885; Wed, 13 Jun 2018 18:23:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w5DINLOv045576 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 18:23:21 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w5DINKhS045575; Wed, 13 Jun 2018 18:23:20 GMT (envelope-from phk) To: Warner Losh cc: "Rodney W. Grimes" , "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" Subject: Re: Armeb removal before 12 In-reply-to: From: "Poul-Henning Kamp" References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <45573.1528914200.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Jun 2018 18:23:20 +0000 Message-ID: <45574.1528914200@critter.freebsd.dk> X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:23:26 -0000 -------- In message , Warner Losh writes: >One can, with a lot of effort, do 64MB too, but it's more effort than for >i386. Even at 64MB on i386, though, the number of things you can do is >quite limited. You can't build anything on that machine. = Well, we *do* have code for something called "swap-devices", and belive it or not, I actually ran make world in 64MB recently - just to see if it would work. Took most of a week. PS: No opinion on the proposed removal. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-arch@freebsd.org Wed Jun 13 18:23:34 2018 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 848C4100385B for ; Wed, 13 Jun 2018 18:23:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD9C7212B for ; Wed, 13 Jun 2018 18:23:34 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id C54B21003856; Wed, 13 Jun 2018 18:23:33 +0000 (UTC) Delivered-To: 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 A0B3F1003854 for ; Wed, 13 Jun 2018 18:23:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 3006772126 for ; Wed, 13 Jun 2018 18:23:33 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id r24-v6so4443766ioh.9 for ; Wed, 13 Jun 2018 11:23:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=J3zITzvsvjTdAw/8ifyG8amwcSL2ZhA+8cXwOdVrjcM=; b=Glp6DnNZ7no40uvrmpt6EAzon5nO5NSNHQKnC3ZKqq/4GvE0/4MEEMj/7WsXXAUbZ6 1+6y5+2XO5pt6wRK9lU4pHeiIFgzAe2pEbrGHVRBRTsmtWSXcgvwA0nLkfN/EgVIMJri L76nY4svtH/MBH4Lzz2zJJDbkIOB+IWkd3xowqv4O8rotg0K9UEjS+N8dZUFnUhEHS5z C6X4ai/hRA6MpFvKGNZAChQKeY2b9yBirQFybDBOv7x6vnqZWzQsLP8hz1D81RXNi2uP XFgRjZSteW6vokya4b0g5uefO7xzoRPjUykrtb6KMIBkjPahW/+8aOkokcoUTTrD3O4x c/MQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=J3zITzvsvjTdAw/8ifyG8amwcSL2ZhA+8cXwOdVrjcM=; b=Znsx5YhIScJiH06Utv6AWWY+x/7GZHNQefefUcTQrRgmitxITH03YSRaihDu/EhoQ7 nXS9UdatflY89ALAqc8OrLgXFxRfkHfHb8lQgl0Tc+59rcFrtAK90iQwWeyxKNhkzX4e jgK02fv7K806F9q5q8aRTM5Wr7APnp7hiKuXrQEUvRIjXtJ4UsQvZIJ6fZhd00Jkfqsa lNnqpCAV5BfjjLGXZWqGZIRKoFYiD7SWrT4uD7ZR84+c3+J4+hnduDgOKW/g1sdRuZvA 8b6QwklQ3zGpSTLbwwBwVETAA4hjHzCWFYjxJhMyp3WJ0FZ8RQv3mkzwTru4/4rpcUlS j7cg== X-Gm-Message-State: APt69E1FXSb3ygI6YjDicGIj30Zo0pnu+ClA+EdN00PSzpfGxoWF7ox8 pEiE2SrfQ71sN9fYYEfykYRpaTjbiZEMwzBRCpUfPQ== X-Google-Smtp-Source: ADUXVKI5maW7pHL08UCUyjxShuQPLOhPd9rqkHxITOOK3m8Jag+jPznBCJCBGBbEX8ZWXDajDktOdrTAu5W0Vxc8W48= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr5749459ioo.168.1528914212496; Wed, 13 Jun 2018 11:23:32 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 11:23:31 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> From: Warner Losh Date: Wed, 13 Jun 2018 12:23:31 -0600 X-Google-Sender-Auth: vdCgBYSjz-W0iLJh8Yz1Qz218uA Message-ID: Subject: Re: Armeb removal before 12 To: "Rodney W. Grimes" Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:23:34 -0000 On Wed, Jun 13, 2018 at 12:09 PM, Warner Losh wrote: > > > On Wed, Jun 13, 2018 at 11:39 AM, Rodney W. Grimes < > freebsd-rwg@pdx.rh.cn85.dnsmgr.net> wrote: > >> > I'd like to remove armeb before 12.0. >> > >> > It's poorly supported today. >> > >> > Nobody has tested the concurrency kit changes on it. And ck is now >> > mandatory. We don't even know if it works or not. >> > >> > Last time we asked, it took quite a while to find users. >> > >> > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to >> > run in. >> >> 64MB is usable for 32 bit archs, I have many VM's running in >> that configuration, so this item should not be in this list. > > > Yes and no. A VM is a different beast to a real box. arm requires more > memory in general, and a little more on real machines. > > You can run it in 128MB and do useful things, but not very many things. > One cannot, for example, run a wifi access point on arm in 128MB, at least > on this hardware. Adrian's ultra-stripped down stuff might be possible, but > nobody has ported it to this hardware despite it being ported to many weird > things. Likewise with the ZRouter project. You could run a simple sshd / > dns server on it, but there's lots of other alternatives for that which are > dirt cheap. > > One can, with a lot of effort, do 64MB too, but it's more effort than for > i386. Even at 64MB on i386, though, the number of things you can do is > quite limited. You can't build anything on that machine. DNS + SSH is > possible here as well, as long as the zones are too big. > > So I'll concede the point it's possible, and I'm not looking to make it > not be possible. However, we do need to draw the line somewhere, and this > is but one factor of many. Were it the only factor here, we wouldn't be > contemplating removal. Most people want to do more ambitious things that > can be done in 256MB is all I was trying to say. > Just to followup... On my 11.0 internal DHCP / DNS server (dnsmasq), I have a Allwinner A20 board with 1GB ram that runs between 100-120MB avm 120-1320MB wired with ~750MB free. That's what I've been basing my 256MB to run comfortably statements on. It's possible to do it with less, but it takes a lot of tuning, custom kernels, and legwork to make it happen. This box has only 14 processes, apart from kernel threads and is pretty minimal. Warner From owner-freebsd-arch@freebsd.org Wed Jun 13 18:45:05 2018 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 DF2A910058C2 for ; Wed, 13 Jun 2018 18:45:05 +0000 (UTC) (envelope-from 4250.10.arch=freebsd.org@email-od.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 783D773441 for ; Wed, 13 Jun 2018 18:45:05 +0000 (UTC) (envelope-from 4250.10.arch=freebsd.org@email-od.com) Received: by mailman.ysv.freebsd.org (Postfix) id 31A9010058B5; Wed, 13 Jun 2018 18:45:05 +0000 (UTC) Delivered-To: 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 1F65410058B4 for ; Wed, 13 Jun 2018 18:45:05 +0000 (UTC) (envelope-from 4250.10.arch=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BBC9F7343E for ; Wed, 13 Jun 2018 18:45:04 +0000 (UTC) (envelope-from 4250.10.arch=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1528915505; x=1531507505; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=bTKTdB+lvuQsecWWEU2/0kpGUXHMUgMWUmkCKeT8w3I=; b=cibHc7cc04hS6HDxcJ6tm3L/74KeHF5A3xoJ+qKtiTTKseOrXWUMZMq55rNKqVkX3QtErTjy9ejMEYEm5xZl3kj8K1XR9lbhQWVWUg5ss4kjxtP8Gu0/kHLJTjHS0G3up2cnj1mHn/+ueVU0wnDZ9Fkzys4H1r9NO/CxbbAYyEk= X-Thread-Info: NDI1MC4xMi4xOGYwMDAwMDAwOTRkMDMuYXJjaD1mcmVlYnNkLm9yZw== Received: from r5.us-west-2a.aws.in.socketlabs.com (r5.us-west-2a.aws.in.socketlabs.com [52.39.5.146]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Wed, 13 Jun 2018 14:44:59 -0400 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r5.us-west-2a.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Wed, 13 Jun 2018 14:44:57 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fTAlK-000Ded-Ar; Wed, 13 Jun 2018 18:44:54 +0000 Date: Wed, 13 Jun 2018 19:44:54 +0100 From: Steve O'Hara-Smith To: "Poul-Henning Kamp" Cc: Warner Losh , "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Subject: Re: Armeb removal before 12 Message-Id: <20180613194454.534e9157129d3988c1683972@sohara.org> In-Reply-To: <45574.1528914200@critter.freebsd.dk> References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> <45574.1528914200@critter.freebsd.dk> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) X-Clacks-Overhead: "GNU Terry Pratchett" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 18:45:06 -0000 On Wed, 13 Jun 2018 18:23:20 +0000 "Poul-Henning Kamp" wrote: > Well, we *do* have code for something called "swap-devices", and > belive it or not, I actually ran make world in 64MB recently - just > to see if it would work. Took most of a week. If memory serves correctly buildworld took a day or two back when 64MB was a fairly generous allocation of memory and there was a lot less world. -- Steve O'Hara-Smith From owner-freebsd-arch@freebsd.org Wed Jun 13 19:13:09 2018 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 558E81008AFA for ; Wed, 13 Jun 2018 19:13:09 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D9F7A752A8 for ; Wed, 13 Jun 2018 19:13:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 987791008AF2; Wed, 13 Jun 2018 19:13:08 +0000 (UTC) Delivered-To: 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 5C16C1008AF0 for ; Wed, 13 Jun 2018 19:13:08 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 E2FDA752A7 for ; Wed, 13 Jun 2018 19:13:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id a195-v6so5171728itd.3 for ; Wed, 13 Jun 2018 12:13:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=frAJ/6cptoxcZM8cDzaNIoq2vg9dt1bEuUe62c6bcBM=; b=RTul18l2CaaNgyciBzunQFfOF4/Ycy+Ls7sV0kKAO23VbJz6gaEGUWFVNhyaIFjlmI xvUlTFmEX05tZz2bdHnpIZko/lgqy3aDFkbW5KUU8Yh/UX6WBIrCP3MzLQgDPJomOjL2 L/gN+4X05y0igyOPKLhcOhvPgVjn+3Ql5SZgg5r2iQj/X430zGcoB+plHeL4XtjZwzqh TWZdFxlzEQJhgDM8L+Y8kj4O94UTQd3tqFKLTPbFNU/yKMQdLOoNT58TLdR4/FAfG135 /x+g/upkHqhNc1gGGFzAMUJXKda+HoYjYlH7tFEO3Yn2t+DIacafvt3y49ipKEFJlPxA kQAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=frAJ/6cptoxcZM8cDzaNIoq2vg9dt1bEuUe62c6bcBM=; b=CxuiKi6CftadN7ZU7SUI4GVRnY023l6eddcFokvu/tVl/bqpAlyZOqoRBbsE5krIGk JnhEjyhFVfjf+Z1kzWlA+YORUOiDkB9JktQjieiIBCDW224y8VIbpeRnz8q7kWIt7Abl ZRAq6rrTO36DcjYP0pX33QuHOnHui6iSCMh8NYnxwOKm3hYN/yzvQtJtpFLQHt4V22jh vKjHOQzGhc7zt/TljYZPSrXWrELf9ZOTCp5mqbAd8rmxc4eyvviFe4nG3ViIaw3hHXmO lTJqzRiDWq4vGEudB8/CybwOuLbUJx1dF/OvNfOFYjSOkRvD4kzePkNcyHrSgsBOmv/6 I3Vw== X-Gm-Message-State: APt69E1NjlQoPuWP0yx8HJmC4koE63OdaKQHyWiHlL6KHPqyomoy0SqE HJ5GHxjiCuOsdcOB9aYSTtEp/mFoxF8pKh/bnHsG0Q== X-Google-Smtp-Source: ADUXVKKTb665ZRjyxiSMqWtk6l3m5dheWaIY/it35QAmMiXg+YasZl8e+HmjFaRAECGi8i3gTcAZ1Q/ny9d31BbBhZs= X-Received: by 2002:a24:7c8d:: with SMTP id a135-v6mr5811319itd.73.1528917187113; Wed, 13 Jun 2018 12:13:07 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 12:13:06 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20180613194454.534e9157129d3988c1683972@sohara.org> References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> <45574.1528914200@critter.freebsd.dk> <20180613194454.534e9157129d3988c1683972@sohara.org> From: Warner Losh Date: Wed, 13 Jun 2018 13:13:06 -0600 X-Google-Sender-Auth: CiRENNPEJPCRPURN_i_a8mPFmeY Message-ID: Subject: Re: Armeb removal before 12 To: "Steve O'Hara-Smith" Cc: Poul-Henning Kamp , "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 19:13:09 -0000 On Wed, Jun 13, 2018 at 12:44 PM, Steve O'Hara-Smith wrote: > On Wed, 13 Jun 2018 18:23:20 +0000 > "Poul-Henning Kamp" wrote: > > > Well, we *do* have code for something called "swap-devices", and > > belive it or not, I actually ran make world in 64MB recently - just > > to see if it would work. Took most of a week. > > If memory serves correctly buildworld took a day or two back when > 64MB was a fairly generous allocation of memory and there was a lot less > world. > In the FreeBSD 1.x time frame, my 486DX2-66 with 32MB of RAM built world over night (well, late afternoon start the build, it was done by breakfast the next day so < 15 hours). Warner From owner-freebsd-arch@freebsd.org Wed Jun 13 19:39:11 2018 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 D3193100B2B1 for ; Wed, 13 Jun 2018 19:39:11 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 68FEC765DD for ; Wed, 13 Jun 2018 19:39:11 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 22794100B2A7; Wed, 13 Jun 2018 19:39:11 +0000 (UTC) Delivered-To: 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 0F75E100B2A6; Wed, 13 Jun 2018 19:39:11 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 93AB9765DA; Wed, 13 Jun 2018 19:39:10 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A3F611487A; Wed, 13 Jun 2018 19:39:09 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id w5DJd8mP045780 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 13 Jun 2018 19:39:08 GMT (envelope-from phk@critter.freebsd.dk) Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id w5DJd8K4045779; Wed, 13 Jun 2018 19:39:08 GMT (envelope-from phk) To: "Steve O'Hara-Smith" cc: "freebsd-arch@freebsd.org" , "freebsd-arm@freebsd.org" , "Rodney W. Grimes" Subject: Re: Armeb removal before 12 In-reply-to: <20180613194454.534e9157129d3988c1683972@sohara.org> From: "Poul-Henning Kamp" References: <201806131739.w5DHd6sl040722@pdx.rh.CN85.dnsmgr.net> <45574.1528914200@critter.freebsd.dk> <20180613194454.534e9157129d3988c1683972@sohara.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <45777.1528918748.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Jun 2018 19:39:08 +0000 Message-ID: <45778.1528918748@critter.freebsd.dk> X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 19:39:12 -0000 -------- In message <20180613194454.534e9157129d3988c1683972@sohara.org>, Steve O'H= ara-Smith writes: >On Wed, 13 Jun 2018 18:23:20 +0000 >"Poul-Henning Kamp" wrote: > >> Well, we *do* have code for something called "swap-devices", and >> belive it or not, I actually ran make world in 64MB recently - just >> to see if it would work. Took most of a week. > > If memory serves correctly buildworld took a day or two back when >64MB was a fairly generous allocation of memory and there was a lot less >world. Most of the cpu-time in buildworld is taken up compiling LLVM. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-arch@freebsd.org Wed Jun 13 22:28:58 2018 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 7E14F101E763 for ; Wed, 13 Jun 2018 22:28:58 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 13EA47FC96 for ; Wed, 13 Jun 2018 22:28:58 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: by mailman.ysv.freebsd.org (Postfix) id CC32B101E75E; Wed, 13 Jun 2018 22:28:57 +0000 (UTC) Delivered-To: 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 A9EC3101E75D for ; Wed, 13 Jun 2018 22:28:57 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh602-vm1.bullet.mail.ssk.yahoo.co.jp (nh602-vm1.bullet.mail.ssk.yahoo.co.jp [182.22.90.26]) by mx1.freebsd.org (Postfix) with SMTP id B70A57FC95 for ; Wed, 13 Jun 2018 22:28:56 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [182.22.66.105] by nh602.bullet.mail.ssk.yahoo.co.jp with NNFMP; 13 Jun 2018 22:25:44 -0000 Received: from [182.22.91.133] by t603.bullet.mail.ssk.yahoo.co.jp with NNFMP; 13 Jun 2018 22:25:44 -0000 Received: from [127.0.0.1] by omp606.mail.ssk.yahoo.co.jp with NNFMP; 13 Jun 2018 22:25:44 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 684077.32694.bm@omp606.mail.ssk.yahoo.co.jp Received: (qmail 52050 invoked by uid 60001); 13 Jun 2018 22:25:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1528928744; bh=B/HLa3bOQXNS53diXkEV6qovaEnZdSWAYQi3feQFsjY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bg4y455C+Gc8LwuvBO5lPfNrHf9IkeDlB4i80a73a5QKxB7D7Z1hCAzrZ+s/qU7fUruKx+WFR1EjVRSWtdkZOQSMJLgHfAerAMllc4o8dsORDYb+M+T2KlP4T5Dvzk/CaojQxzMPfSSIoETNUUiVnzyQD6w1Ng7ceh/LDdyJt2U= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JKJIrJb0unvtUCLYRjA6nGG7/H0AMiY4j4wdoGnjBa/PmnZTyDJZzbJrajDJgCKL8bLuEqn7jJ9njgv33Bg3NvQws+czaKNCggzH/Lpj6ooIaUXCHNyEGN40rLTKUh4UFMZTRzV9XAxHvKSyZtTS/YCd8d8N27GwxwcqphC9nBE=; Message-ID: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> X-YMail-OSG: 3K28KpsVM1l03toHXstNalsxsnupG4PqLvDzE5CxithSyW4F5pQdsSdroBstCjO6LRUBmka.RaAEbnElen1fjKMWQB3Hh0Zo4OlkL5JJ8jfpQfPnIiJkfoQoToh5Mw6u_gH7NsoEsg2VZxaJ91xahaNvjV1qd2hI4hvt0hcjEILKB21duaoPi0vMhYGBAkln4.AEHRD6vhHrWtHZcnp8huE0TzjklegM1Jt3GqsPScRtUiPXLJTJYRJnMoihp.Ra5Fl6BMoOHUlvtq_xmhKLi3pDK_L1jLehAoGdIIn3zmEF8ddrQaWiuSDJ.NnMpAGdZwWOZmNK50ju6elSB2Fva42Wc5erj9rHo6FfDirp_27R1H8mEXE7hcnQ2EYxLcDgnDtIYrXGb_dddKaWgQTUxNUmX2sOVwGzVICuNDwabKOXkDsCo1vC2tuaL225QzG3rsxfNO2VQbxQa4j_poyetwZA2c5V1EYB8EdRJ21Lzif0uRh7TCP.RXgLzerwygtzNrXFMBpotnUrWdebri2qiQIJVVc0xcuwIEtpwelaGnpNn7v9QHmIusHncnwaJrKiadNM1J5XBnQxORdkOtM5zQngQ_wbvRp0knV_VrJtvLYmshUpbfPyJBDPuxx.dKRK Received: from [203.165.91.75] by web101701.mail.ssk.yahoo.co.jp via HTTP; Thu, 14 Jun 2018 07:25:43 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: Pq.l_6YVM1k1eiLk1cFy3OP3RmXiLFDgjBgo3t0jMUlVa0ZCOa9zOIBzvxDbF9WepNJfLucits4H3Qj3MFOk9gYhHJXz.nuklYnl18yBXCdtJTWhgPJMBeg6lb1D3LkutBBl References: Date: Thu, 14 Jun 2018 07:25:43 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: Re: Armeb removal before 12 To: Warner Losh , "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 22:28:58 -0000 Hi.=0A=0A=0A----- Original Message -----=0A> From: Warner Losh =0A> To: "freebsd-arm@freebsd.org" ; "freebsd-= arch@freebsd.org" =0A> Cc: =0A> Date: 2018/6/14, Thu 01:5= 5=0A> Subject: Armeb removal before 12=0A> =0A> I'd like to remove armeb be= fore 12.0.=0A> =0A> It's poorly supported today.=0A> =0A> Nobody has tested= the concurrency kit changes on it. And ck is now=0A> mandatory. We don't e= ven know if it works or not.=0A> =0A> Last time we asked, it took quite a w= hile to find users.=0A> =0A> It maxes out at 256MB of RAM. This is barely l= arge enough for FreeBSD to=0A> run in.=0A=0Asys/arm/ralink target is only 1= 6M of RAM. I use bridge on this target=0Awork fine.=0A=0AI have FWIXP422BB = target(Planex BRC-14VG) with 32M of RAM. I never build=0AFreeBSD for this= =A0target.=0A=0AI want build for=A0FWIXP422BB but clang cross build is very= slow. It take=0A7 hour on my machine.=0A=0A> =0A> The hardware was last ma= de almost a decade ago.=0A> =0A> It uses non-standard non-mainstream boot l= oaders (boot technology has moved=0A> on from redboot).=0A> =0A> The cost o= f doing API sweeps, make universe runs, etc exceeds the benefit=0A> to the = project.=0A> =0A> So, given all these factors, it sounds like a good candid= ate for retirement.=0A> =0A> Therefore, I'd like to remove it on July 15th.= =0A> =0A> Comments? (please keep=A0 them on topic to this specific thing: t= here's other=0A> things that may also be past their freshness date, we'll d= iscuss those in a=0A> separate thread).=0A> =0A> Warner=0A> _______________= ________________________________=0A> freebsd-arm@freebsd.org mailing list= =0A> https://lists.freebsd.org/mailman/listinfo/freebsd-arm=0A> To unsubscr= ibe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"=0A> From owner-freebsd-arch@freebsd.org Wed Jun 13 22:57:04 2018 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 C24151020E1C for ; Wed, 13 Jun 2018 22:57:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 535E480C78 for ; Wed, 13 Jun 2018 22:57:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0A2291020E15; Wed, 13 Jun 2018 22:57:04 +0000 (UTC) Delivered-To: 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 DA5B61020E14 for ; Wed, 13 Jun 2018 22:57:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 6D82880C77 for ; Wed, 13 Jun 2018 22:57:03 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x235.google.com with SMTP id d185-v6so5228817ioe.0 for ; Wed, 13 Jun 2018 15:57:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ZAg9QIw4NwwqcOk7QTThnQrCXaQaZWqs/xTOjF2sOUI=; b=lhK7QvGc5KFURML9LqyXEBNYbyKygHOjrKj7ph0uAB/PH2HNHN/CAxS4rCqQELYEUq 7kiQYoczavBGZ5GjAJOyMrzmmLmGWRDTpqTGDsxp2dpDzGDhd58fg8Hk8aAcfIFTdx8M jkHSJmoHVfRLcLWlYCckWQSBm2SsLch8789Wztz4VwLpgrQn3xT+TdL4fTU1hur0Jcpe sgp49A2v8aUrR4WO+Zbd5yI7ZPZSuNwZ8FDGve3XG1+zP7aIK3YsKK5C6judxTvOM/hL 3wTZ65nDcRvRAKkSi8uVyeIsq5q7genOMnJZ4s0cetWC9rpMyoYQ/JmiJbE/ziBKu8E/ LETw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ZAg9QIw4NwwqcOk7QTThnQrCXaQaZWqs/xTOjF2sOUI=; b=PR2Sls45tN1DXo5X3HMxFKBIkqDmj6Eqg0VoMjM6A+Q3cZuPZwIps0VtvqteN3k9m/ g0ijxLFjYEj9eUzsoCvJeq1NLl76yedEdb0JFk7MK5OPsxkx3dPQIPpxG8+yTOloTJbL FPyPc+aaq/Bufi0MKcjvEzJqr8mhEHi3RpcOjGyjXigb8BfyHs8Lw1jDEKbJH8owq6Dn 9OFBsa1Z58Ero5SlQSw3eSSst0nSD/DJw4zA5Rk7/+mCjENnTq3eBAWB+WOTSNIHwRhZ 1l35myxEt54vxZY9k+qQeeb7Akf+WbMi538oZVTQu3zU1vrFR7ATZawFLOoMN2HjiHaH QiHA== X-Gm-Message-State: APt69E3rbm9e9deYdANj1L5mxSTLVsEwuGWvM3ctgrqhS1X6aBtLQgUO w+qsDsnEim0WaAOpAIvjyz8GSaFjrPntfLokqLxBZw== X-Google-Smtp-Source: ADUXVKIkWRNWg+5K/DYIhiDL2FwS94AUaniTImnF3zC7u/lqZ8C4D7eJ56pWcTH0wiuxjHX1Dda/nUsKPOq5VmJpCU8= X-Received: by 2002:a6b:d40c:: with SMTP id l12-v6mr124789iog.37.1528930622665; Wed, 13 Jun 2018 15:57:02 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 15:57:02 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> From: Warner Losh Date: Wed, 13 Jun 2018 16:57:02 -0600 X-Google-Sender-Auth: 5HUYRbmaDjcSxXO0TItfn25B4fs Message-ID: Subject: Re: Armeb removal before 12 To: Mori Hiroki Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 22:57:05 -0000 On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki wrote: > Hi. > > > ----- Original Message ----- > > From: Warner Losh > > To: "freebsd-arm@freebsd.org" ; " > freebsd-arch@freebsd.org" > > Cc: > > Date: 2018/6/14, Thu 01:55 > > Subject: Armeb removal before 12 > > > > I'd like to remove armeb before 12.0. > > > > It's poorly supported today. > > > > Nobody has tested the concurrency kit changes on it. And ck is now > > mandatory. We don't even know if it works or not. > > > > Last time we asked, it took quite a while to find users. > > > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > > run in. > > sys/arm/ralink target is only 16M of RAM. I use bridge on this target > work fine. > Even with current? It seems to have grown a lot. Even FreeBSD 11 on my atmel boards, the 32MB ones can't really do much of anything (though a custom /etc/rc.d might be usable). The 64MB ones I have troubles logging into without disabling a ton of stuff. And FreeBSD-current is even larger. Are you using a custom rc.d in this setup? > I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never build > FreeBSD for this target. > > I want build for FWIXP422BB but clang cross build is very slow. It take > 7 hour on my machine. I'm sorry to hear that. Even on my fast machines, it takes long time. Warner > > > > > The hardware was last made almost a decade ago. > > > > It uses non-standard non-mainstream boot loaders (boot technology has > moved > > on from redboot). > > > > The cost of doing API sweeps, make universe runs, etc exceeds the benefit > > to the project. > > > > So, given all these factors, it sounds like a good candidate for > retirement. > > > > Therefore, I'd like to remove it on July 15th. > > > > Comments? (please keep them on topic to this specific thing: there's > other > > things that may also be past their freshness date, we'll discuss those > in a > > separate thread). > > > > Warner > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > From owner-freebsd-arch@freebsd.org Wed Jun 13 23:12:18 2018 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 5666F10222BA for ; Wed, 13 Jun 2018 23:12:18 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CF0A1816B7 for ; Wed, 13 Jun 2018 23:12:17 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: by mailman.ysv.freebsd.org (Postfix) id 8E27310222B4; Wed, 13 Jun 2018 23:12:17 +0000 (UTC) Delivered-To: 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 6BD0F10222B3 for ; Wed, 13 Jun 2018 23:12:17 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from nh501-vm7.bullet.mail.kks.yahoo.co.jp (nh501-vm7.bullet.mail.kks.yahoo.co.jp [183.79.56.137]) by mx1.freebsd.org (Postfix) with SMTP id 79DA4816AF for ; Wed, 13 Jun 2018 23:12:16 +0000 (UTC) (envelope-from yamori813@yahoo.co.jp) Received: from [183.79.100.141] by nh501.bullet.mail.kks.yahoo.co.jp with NNFMP; 13 Jun 2018 23:10:14 -0000 Received: from [183.79.100.136] by t504.bullet.mail.kks.yahoo.co.jp with NNFMP; 13 Jun 2018 23:10:14 -0000 Received: from [127.0.0.1] by omp505.mail.kks.yahoo.co.jp with NNFMP; 13 Jun 2018 23:10:14 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 210555.61927.bm@omp505.mail.kks.yahoo.co.jp Received: (qmail 57827 invoked by uid 60001); 13 Jun 2018 23:10:13 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.jp; s=yj20110701; t=1528931413; bh=h1nmF6+dSMhXdTAUALJnMxxrecPJ3Be4OZQPtiaXxnA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FL+U1vYmVGgUtLRLum+LOnStn9QxeDdCv0ykPcd4cBm+EiBMYBdnhgTLU2o2gIPDNZdcycMcz+qHMQFtW5RBYMADeOWUMn3ONHS9WOFkwvBqw+3VF2ow71Cpi+hXufXYd6DbPuugBHdJpUMMf72ZYjgmj0cwqnG0eEg1lfJlB6M= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=yj20110701; d=yahoo.co.jp; h=Message-ID:X-YMail-OSG:Received:X-Mailer:X-YMail-JAS:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LJgvbbK1g/LnSAKlrZ/Cx4gu9hmz0S0+IOywH6ov0iWZHzhomjQYQtGTFypKQZFoydrExxNPMWufC1esTmIH0ASB8UigFYf81KL1BAZ9Wipm1h6j2g5wcqANF27kBJxqWd+4mrQp96wmR/Mp8ehg+Bc3k5XPoYubuAiIgcvyM8k=; Message-ID: <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp> X-YMail-OSG: 8Swe6woVM1lkyhri6SEJGpR0pOXoYO88EpoJExZ2vqiQuy48sc_9ZU4Ywf329Uzib26WLBzyl.hnm5uLnFRV2vHj0cc3qT0Ry99s2R_5okEkQytftDtiCLt2_wevelYtiCOEb1kj1Syu.eWAA0LfxMCenyisAMlQOPnOZvjQKLodpLQdQx7dy0dgWUO1663PImIcNU22LUizeuQPCk4UMmvYGxBp9Nfc.iXqTQuSYepLptTJUvhhd4s6fA0_Fc4B2yOVneXW.Ij0i8Vs_t8e_gPyxMQ8ER7lxi0ZvSJQMO2a3zAkx5ponsOXh9eRI.ph2kAQRUgFWuP6BRX3zjbNl3xdpF0ogjIJVTNcQZkdmm.1zVTqW9XToqObKKbtdRAWg.XwsmOTBGUhRUvq3eIN.5reYHgX0m4tAwC7Z9R2tT_sBkEYSfmD.OZYYqGgzydQqcKa.WNwytnL5qgzOi71ojOgHZ5kcpOqIl2NnULg9t.iEbtnlI4vFN_QHfKCrdkzvbKep4pP.Wbk3WPDT2ysG1wNQjH0UZbgChI7cb39VkWuz7qWgzfx0IcB8.Vt65Ru94KVF5zn9ZDIIhkNR.8tHkkDvwoYdTn48l6da5XU2HNkMloupzs1z.co9o1VOZ3C Received: from [203.165.91.75] by web101713.mail.ssk.yahoo.co.jp via HTTP; Thu, 14 Jun 2018 08:10:12 JST X-Mailer: YahooMailWebService/0.8.111_74 X-YMail-JAS: lCRctvMVM1lAWZKcdIKBOVMlzUV4IypNvOI1o41ca_b3K8LpSBF_yNyKkD0T4bAHyOzgVXmNfrTreaJXV3vE6sNJujYjqjIT8CnpsJcg8je3bhdHZl2HJTEcvfcL8v5iDh8M References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> Date: Thu, 14 Jun 2018 08:10:12 +0900 (JST) From: Mori Hiroki Reply-To: Mori Hiroki Subject: Re: Armeb removal before 12 To: Warner Losh Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 23:12:18 -0000 Hi=0A=0A----- Original Message -----=0A>From: Warner Losh = =0A>To: Mori Hiroki =0A>Cc: "freebsd-arm@freebsd.or= g" ; "freebsd-arch@freebsd.org" = =0A>Date: 2018/6/14, Thu 07:57=0A>Subject: Re: Armeb removal before 12=0A> = =0A>=0A>=0A>=0A>=0A>=0A>On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki wrote:=0A>=0A>Hi.=0A>>=0A>>=0A>>----- Original Message --= ---=0A>>> From: Warner Losh =0A>>> To: "freebsd-arm@freebsd= .org" ; "freebsd-arch@freebsd.org" =0A>>> Cc: =0A>>> Date: 2018/6/14, Thu 01:55=0A>>> Subject: Armeb remova= l before 12=0A>>> =0A>>> I'd like to remove armeb before 12.0.=0A>>> =0A>>>= It's poorly supported today.=0A>>> =0A>>> Nobody has tested the concurrenc= y kit changes on it. And ck is now=0A>>> mandatory. We don't even know if i= t works or not.=0A>>> =0A>>> Last time we asked, it took quite a while to f= ind users.=0A>>> =0A>>> It maxes out at 256MB of RAM. This is barely large = enough for FreeBSD to=0A>>> run in.=0A>>=0A>>sys/arm/ralink target is only = 16M of RAM. I use bridge on this target=0A>>work fine.=0A>>=0A>=0A>=0A>Even= with current? It seems to have grown a lot. Even FreeBSD 11 on my atmel bo= ards, the 32MB ones can't really do much of anything (though a custom /etc/= rc.d might be usable). The 64MB ones I have troubles logging into without d= isabling a ton of stuff. And FreeBSD-current is even larger.=0A>=0A>=0A>Are= you using a custom rc.d in this setup?=0A=0A=0AOf course CURRENT.=0A=0Ahtt= ps://gist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5=0A=0A=0AI u= se custom rc.d by ZRouter build system.=0A=0AThanks=0A=0AHiroki Mori=0A=0A>= =A0=0A>I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never b= uild=0A>>FreeBSD for this=A0target.=0A>>=0A>>I want build for=A0FWIXP422BB = but clang cross build is very slow. It take=0A>>7 hour on my machine.=0A>= =0A>=0A>I'm sorry to hear that. Even on my fast machines, it takes long tim= e.=0A>=0A>=0A>Warner=0A>=0A>=0A>=A0=0A>=0A>>> =0A>>> The hardware was last = made almost a decade ago.=0A>>> =0A>>> It uses non-standard non-mainstream = boot loaders (boot technology has moved=0A>>> on from redboot).=0A>>> =0A>>= > The cost of doing API sweeps, make universe runs, etc exceeds the benefit= =0A>>> to the project.=0A>>> =0A>>> So, given all these factors, it sounds = like a good candidate for retirement.=0A>>> =0A>>> Therefore, I'd like to r= emove it on July 15th.=0A>>> =0A>>> Comments? (please keep=A0 them on topic= to this specific thing: there's other=0A>>> things that may also be past t= heir freshness date, we'll discuss those in a=0A>>> separate thread).=0A>>>= =0A>>> Warner=0A>>=0A>>> ______________________________ _________________= =0A>>> freebsd-arm@freebsd.org mailing list=0A>>> https://lists.freebsd.org= / mailman/listinfo/freebsd-arm=0A>>> To unsubscribe, send any mail to "free= bsd-arm-unsubscribe@ freebsd.org"=0A>>> =0A>>=0A>=0A>=0A> From owner-freebsd-arch@freebsd.org Wed Jun 13 23:24:16 2018 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 270F51000265 for ; Wed, 13 Jun 2018 23:24:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9E6BB81F1E for ; Wed, 13 Jun 2018 23:24:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5A5B21000258; Wed, 13 Jun 2018 23:24:15 +0000 (UTC) Delivered-To: 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 37F351000257 for ; Wed, 13 Jun 2018 23:24:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (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 B943A81F1C for ; Wed, 13 Jun 2018 23:24:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x232.google.com with SMTP id l6-v6so6265703iti.2 for ; Wed, 13 Jun 2018 16:24:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=zeheL/enFjhTSq+XXwjaIU75eBMw/ePyR23ecLbXufU=; b=J366PIzvOTDKsWBS6IBXpL+bDRPlSGUG9qeHAsX7ww6Af2DePMCqiOA7186mgYlvAJ 8SfKaq/FHCfIkZc4HM8JiUe6A6tHrbatH1AJUdVF2BncHaUMvd9HXahmxMr/W+5MZzUd RBO3R3fwJV4nduaS2pB2I12wRZ8isiJq6BeWO8KkqVoOLrY4Wj6EilTQ/eT8D5u5Zb8J Snur0uYzdHYuGi6OPDQebqdgBe0DblNrl7+KruBQoYNPOnx7ANne8oCgylXhfxjWaG6K 71mo9FmvpkMkZw/dFLr4tAlMDCgsw5HjomQZMUIbrdIDf3Dt5UDpU7ZUpHG4LgfpGu6w 6wEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=zeheL/enFjhTSq+XXwjaIU75eBMw/ePyR23ecLbXufU=; b=YKRhs8r9OmMnJu+bfvr3zSQagXacOaualiQefC2+33LjjlCVgDjeC1xCVdiHUEKlAC L2TbZ6Hm2bv08A6mYyIKMabTx0NHC8fcgLBXiRIcz5awpVAE3fd6Bfc37fEOJ0DYXZkn 8fJIA2nfg8NWJbb5WLpjxA6ohWCViQyM6dnXVCYEoP4hzCT2cgGBhgnSlO6FcNyq8vOx 8JF4grfky92hSPIO7lIce/t+6iHp+LWIYUw4wR3Bz39mCu3cpapv764a3ZlEsa7vmmnw BZIBwaw811yA8TTL43lWOkyQEyVJNpfrBeON21Gfhli07RaoScOjijGvCZKg53AXAu2D v/+A== X-Gm-Message-State: APt69E1lXbBaGCb7nzYiU+3fLZ53P+32NzOaMAx3FLuDTH5FM95J4KQO 3UzmXPV19wos5zqRKhTmKVq/DyvCO9Fp4cMYwqC59A== X-Google-Smtp-Source: ADUXVKIeqjuHuhtkXQkkXA+k0ne/oMXK2H7wddXK5gDfixRSUQIu39Gr+lPl4qpQzT2CfM+CA+LoVWHfNaA8cI0VLu4= X-Received: by 2002:a24:64ce:: with SMTP id t197-v6mr153106itc.36.1528932254073; Wed, 13 Jun 2018 16:24:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 13 Jun 2018 16:24:13 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp> References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> <861063.32056.qm@web101713.mail.ssk.yahoo.co.jp> From: Warner Losh Date: Wed, 13 Jun 2018 17:24:13 -0600 X-Google-Sender-Auth: ZjLw9CiLa-Jyxq2FQWakPGJtlHQ Message-ID: Subject: Re: Armeb removal before 12 To: Mori Hiroki Cc: "freebsd-arm@freebsd.org" , "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2018 23:24:16 -0000 On Wed, Jun 13, 2018 at 5:10 PM, Mori Hiroki wrote: > Hi > > ----- Original Message ----- > >From: Warner Losh > >To: Mori Hiroki > >Cc: "freebsd-arm@freebsd.org" ; " > freebsd-arch@freebsd.org" > >Date: 2018/6/14, Thu 07:57 > >Subject: Re: Armeb removal before 12 > > > > > > > > > > > > > >On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki > wrote: > > > >Hi. > >> > >> > >>----- Original Message ----- > >>> From: Warner Losh > >>> To: "freebsd-arm@freebsd.org" ; " > freebsd-arch@freebsd.org" > >>> Cc: > >>> Date: 2018/6/14, Thu 01:55 > >>> Subject: Armeb removal before 12 > >>> > >>> I'd like to remove armeb before 12.0. > >>> > >>> It's poorly supported today. > >>> > >>> Nobody has tested the concurrency kit changes on it. And ck is now > >>> mandatory. We don't even know if it works or not. > >>> > >>> Last time we asked, it took quite a while to find users. > >>> > >>> It maxes out at 256MB of RAM. This is barely large enough for FreeBSD > to > >>> run in. > >> > >>sys/arm/ralink target is only 16M of RAM. I use bridge on this target > >>work fine. > >> > > > > > >Even with current? It seems to have grown a lot. Even FreeBSD 11 on my > atmel boards, the 32MB ones can't really do much of anything (though a > custom /etc/rc.d might be usable). The 64MB ones I have troubles logging > into without disabling a ton of stuff. And FreeBSD-current is even larger. > > > > > >Are you using a custom rc.d in this setup? > > > Of course CURRENT. > > https://gist.github.com/yamori813/88224f1c96c9c592fb611b12a15e4ab5 > > > I use custom rc.d by ZRouter build system. > Cool! You have 10MB available. what all runs in that little space? I didn't see too much starting up Warner > Thanks > > Hiroki Mori > > > > >I have FWIXP422BB target(Planex BRC-14VG) with 32M of RAM. I never build > >>FreeBSD for this target. > >> > >>I want build for FWIXP422BB but clang cross build is very slow. It take > >>7 hour on my machine. > > > > > >I'm sorry to hear that. Even on my fast machines, it takes long time. > > > > > >Warner > > > > > > > > > >>> > >>> The hardware was last made almost a decade ago. > >>> > >>> It uses non-standard non-mainstream boot loaders (boot technology has > moved > >>> on from redboot). > >>> > >>> The cost of doing API sweeps, make universe runs, etc exceeds the > benefit > >>> to the project. > >>> > >>> So, given all these factors, it sounds like a good candidate for > retirement. > >>> > >>> Therefore, I'd like to remove it on July 15th. > >>> > >>> Comments? (please keep them on topic to this specific thing: there's > other > >>> things that may also be past their freshness date, we'll discuss those > in a > >>> separate thread). > >>> > >>> Warner > >> > >>> ______________________________ _________________ > >>> freebsd-arm@freebsd.org mailing list > >>> https://lists.freebsd.org/ mailman/listinfo/freebsd-arm > >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@ freebsd.org > " > >>> > >> > > > > > > > From owner-freebsd-arch@freebsd.org Thu Jun 14 11:41:05 2018 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 CB000101FFA4 for ; Thu, 14 Jun 2018 11:41:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 49AD785AAC for ; Thu, 14 Jun 2018 11:41:05 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0384D101FF9E; Thu, 14 Jun 2018 11:41:05 +0000 (UTC) Delivered-To: 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 D4E0D101FF9C for ; Thu, 14 Jun 2018 11:41:04 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 6FE2985A9E for ; Thu, 14 Jun 2018 11:41:04 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id p126-v6so10017660wmb.2 for ; Thu, 14 Jun 2018 04:41:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=oTck3iL2pGE+wm60oC8XtGV3+1cGgJoP1x5kVWeMqCM=; b=WTpDAjpeKDuKL3G3eyp4Te5EeNfWHwWxaCMlACULZU1dP455M8LRW534fgWrWEHFMM RZdDnFkkYZ7i3iJa4yufPf7dSiUvCSB9+UurWpGWARP2JU+6LOqu0NEKU5ZDMhZAD1fE NxrE0l8qld3xYNzGWa/kQWfXIL3UqBbZyVJZzsBqNsgBValhIHywEIRchi8EQTUEjk55 X39/93e/463JV+8eFyUE0YLvlU/y5Et8kykHVKgHd65eVkX9OYTxkvRXBX8LVNqXWHOb gQqPNGUtE5iP8rGXJIgazydyDHWcHj5uTaj+7zkflzg9uRIkty8sb50aj3DovdQqxJWX Bd9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=oTck3iL2pGE+wm60oC8XtGV3+1cGgJoP1x5kVWeMqCM=; b=a04+SbB4hZGvAl1LjjQ89eIsoz8u5amj6SBgoeoDBGCXkw3CROZXo/uv+ndHKMXi5J nr2LG0TocSZ70NG3QIkkRPfRLpW15mAwopSslkWwVLqdu79pi6Kg7UJc6RXnDvKeeNRF RPGl0oWeKIl2slUuLkknBiAdYYQwgOsWpj/Mxv5Ef/IGCxD1+a3wXKzzW/Uf8/BO45uL mn8ZueolXfLrTTC+Ffg4a0/uOly/2TwmqGOhJCShjo1tIW54i7aqmVwWHTUcPHSEvfHM nyZ/OuGJVfQCtgD/K5BAL0RLlEE4gtuG1AzS3F2ar3LafcwrKBSkJSwjGOwM/kOmuqJY S2fg== X-Gm-Message-State: APt69E0TohMfEXdvpdCqadK9XOBjP1v/QeYjamEXH1Src3ctf7TRqsra fTHSho0/h+XVQOAbF2gOzVYnsg== X-Google-Smtp-Source: ADUXVKK4dNLGcTQwK7uBoW1JSnCtWd4I6axhD5jhlTlx1ZGbQYS8mOHewJGN8stTAkW+DgG/LX6aLQ== X-Received: by 2002:a1c:8410:: with SMTP id g16-v6mr1599642wmd.26.1528976463293; Thu, 14 Jun 2018 04:41:03 -0700 (PDT) Received: from ernst.home (p5B02381D.dip0.t-ipconnect.de. [91.2.56.29]) by smtp.gmail.com with ESMTPSA id b186-v6sm4024684wmh.4.2018.06.14.04.41.02 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 14 Jun 2018 04:41:02 -0700 (PDT) Date: Thu, 14 Jun 2018 13:41:01 +0200 From: Gary Jennejohn To: "freebsd-arch@freebsd.org" Subject: Re: Armeb removal before 12 Message-ID: <20180614134101.6c041990@ernst.home> In-Reply-To: References: <540973.43848.qm@web101701.mail.ssk.yahoo.co.jp> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Jun 2018 11:41:06 -0000 On Wed, 13 Jun 2018 16:57:02 -0600 Warner Losh wrote: > On Wed, Jun 13, 2018 at 4:25 PM, Mori Hiroki wrote: > > > Hi. > > > > > > ----- Original Message ----- > > > From: Warner Losh > > > To: "freebsd-arm@freebsd.org" ; " > > freebsd-arch@freebsd.org" > > > Cc: > > > Date: 2018/6/14, Thu 01:55 > > > Subject: Armeb removal before 12 > > > > > > I'd like to remove armeb before 12.0. > > > > > > It's poorly supported today. > > > > > > Nobody has tested the concurrency kit changes on it. And ck is now > > > mandatory. We don't even know if it works or not. > > > > > > Last time we asked, it took quite a while to find users. > > > > > > It maxes out at 256MB of RAM. This is barely large enough for FreeBSD to > > > run in. > > > > sys/arm/ralink target is only 16M of RAM. I use bridge on this target > > work fine. > > > > Even with current? It seems to have grown a lot. Even FreeBSD 11 on my > atmel boards, the 32MB ones can't really do much of anything (though a > custom /etc/rc.d might be usable). The 64MB ones I have troubles logging > into without disabling a ton of stuff. And FreeBSD-current is even larger. > As someone wrote in an earlier mail to one of the lists, it's amazing how bloated UNIX has become in the last few decades. In 1986 I was developing on a 68010-based SYS V machine for Morrow Designs which had a whopping 1MB of RAM. This was considered to be a very well endowed machine! It was packed with all kinds of controller boards and I was doing custom drivers for Morrow Designs. It even had one of the very first Syquest removable-disk drives in it, I think it was the 5MB model with MFM encoding. Unfortunately, 1986 was also the year in which Morrow Designs went tits up. I then owned the only UNIX-based machine which Morrow Designs had ever produced. Eventually I donated it to the VCF. -- Gary Jennejohn From owner-freebsd-arch@freebsd.org Fri Jun 15 14:28:54 2018 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 91363100AE6D for ; Fri, 15 Jun 2018 14:28:54 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A25A70C97 for ; Fri, 15 Jun 2018 14:28:54 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from weatherwax.trouble.is (weatherwax.trouble.is [IPv6:2a00:dd80:3c::62e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 04B1A18732 for ; Fri, 15 Jun 2018 14:28:54 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.trouble.is (rincewind.trouble.is [88.198.44.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "rincewind.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 416jXh1sFWz3C1F for ; Fri, 15 Jun 2018 14:28:52 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, authenticated sender philip) id 416jXg5rTfz2r3; Fri, 15 Jun 2018 14:28:51 +0000 (UTC) From: "Philip Paeps" To: freebsd-arch@freebsd.org Subject: Re: upstream for contrib/tzcode/stdtme? Date: Fri, 15 Jun 2018 16:28:50 +0200 X-Clacks-Overhead: GNU Terry Pratchett X-Mailer: MailMate (1.11.2r5496) Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 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 Jun 2018 14:28:54 -0000 On 2018-06-10 21:40:21 (+0200), Eitan Adler wrote: > What's the upstream for contrib/tzcode/stdtme? https://www.iana.org/time-zones (and https://github.com/eggert/tz). > There are a couple of PRs for it and I'd like to either update, fix > upstream, or move to non-contrib & fix. I've started updating it several times but the rather awkward layout of the vendor tree makes doing just about anything else more attractive. :) More than happy to review an update if you actually manage to complete one! I wonder if we should just make the "moving around files" in the vendor tree go away... Many thanks! Philip -- Philip Paeps Senior Reality Engineer Ministry of Information From owner-freebsd-arch@freebsd.org Fri Jun 15 16:03:28 2018 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 9EC591010DA5 for ; Fri, 15 Jun 2018 16:03:28 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 555E2750F7 for ; Fri, 15 Jun 2018 16:03:28 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 7797510AFCD for ; Fri, 15 Jun 2018 12:03:27 -0400 (EDT) Subject: Re: upstream for contrib/tzcode/stdtme? To: freebsd-arch@freebsd.org References: From: John Baldwin Message-ID: Date: Fri, 15 Jun 2018 09:03:26 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 15 Jun 2018 12:03:27 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 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 Jun 2018 16:03:28 -0000 On 6/15/18 7:28 AM, Philip Paeps wrote: > On 2018-06-10 21:40:21 (+0200), Eitan Adler wrote: >> What's the upstream for contrib/tzcode/stdtme? > > https://www.iana.org/time-zones (and https://github.com/eggert/tz). > >> There are a couple of PRs for it and I'd like to either update, fix >> upstream, or move to non-contrib & fix. > > I've started updating it several times but the rather awkward layout of > the vendor tree makes doing just about anything else more attractive. :) > > More than happy to review an update if you actually manage to complete > one! > > I wonder if we should just make the "moving around files" in the vendor > tree go away... I do think we should perhaps import the vendor tree to contrib/stdtime or some such and then apply our local patches from libc to there. Alternatively, we could move the the files from libc into suitable locations in contrib/stdtime and then do an 'svn merge --record-only' to bootstrap the vendor mergeinfo for the current version and use that as a basis for updating? -- John Baldwin From owner-freebsd-arch@freebsd.org Fri Jun 15 17:46:34 2018 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 390A610162B4 for ; Fri, 15 Jun 2018 17:46:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 D065B7AF95 for ; Fri, 15 Jun 2018 17:46:33 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22e.google.com with SMTP id s201-v6so3612342ywg.8 for ; Fri, 15 Jun 2018 10:46:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UPtxJ6008aXQ7gIA/bV7MkVz2DFCJjQzrIZ5hMne2iU=; b=TJ5baZlKa1PaqmU/F4bYS4Jk+DrtOtxFkBLFiET+6bd1PzxoWlxHjjkV7h+Brp6tuI YoQNH0k7W8gPoUHMof2oxJL3Me0tRQxo6Rtoj/+R6HzDH6LYaLQFZ2JWe7IposaV6QOx LNLN6XSez9zrc9Y6km/IV/pxS1bkdRaXWLZcg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UPtxJ6008aXQ7gIA/bV7MkVz2DFCJjQzrIZ5hMne2iU=; b=B5KcuWHZt41/HSgBNQknfCqKMzrplAITtyNSi3A8VIUMvDiNkoB1nwnfXlXRk6jC1z gJWWuVmk7TVKs5MU6jJWwEbFRiCu/JPpM6Ktkz7W49oFR79Pk5vzABiZdBO3k9ez0IgE yaeqt0gCtB5kw7ebPvbG6CrrObhP+WVCsCZnNBu/Lf78khB7QolGD2VrQ/VfmaGBWkXe MBWysI/Jw9Njh8DuYxVU1Om/ro0QEhHVbKzwiPFZLUkWlihLoFbCF4yb0UPM8TEln5R0 CaB1tLhBH7dG0uB2SzSraQpZ6UGQiTqjANK4SgTs3dy03ikN2zbliD6VXMoxLDrx3X/H /Alw== X-Gm-Message-State: APt69E0h5dT6o5CrDusvQzPOh0cwa9WE5iUQ1fSXN41LCsxAVXGcy8oB W9bagrmvKHdINGiiZBJxrn8kIhEwhv5oD2YSK7mwqQ== X-Google-Smtp-Source: ADUXVKLmHx+1v/1WPb8i64Ypte7wERREAKssVI0rm8QQRE2xZzVeM4oQPwpqn/ROVH1vOIs/eM5qVDj2KHx2V6DuXik= X-Received: by 2002:a81:af1d:: with SMTP id n29-v6mr1381254ywh.113.1529084792887; Fri, 15 Jun 2018 10:46:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 10:46:02 -0700 (PDT) In-Reply-To: References: From: Eitan Adler Date: Fri, 15 Jun 2018 10:46:02 -0700 Message-ID: Subject: Re: upstream for contrib/tzcode/stdtme? To: John Baldwin Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 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 Jun 2018 17:46:34 -0000 On 15 June 2018 at 09:03, John Baldwin wrote: > On 6/15/18 7:28 AM, Philip Paeps wrote: >> On 2018-06-10 21:40:21 (+0200), Eitan Adler wrote: >>> What's the upstream for contrib/tzcode/stdtme? >> >> https://www.iana.org/time-zones (and https://github.com/eggert/tz). >> >>> There are a couple of PRs for it and I'd like to either update, fix >>> upstream, or move to non-contrib & fix. >> >> I've started updating it several times but the rather awkward layout of >> the vendor tree makes doing just about anything else more attractive. :) >> >> More than happy to review an update if you actually manage to complete >> one! I'll attempt one this weekend. :) >> I wonder if we should just make the "moving around files" in the vendor >> tree go away... +1 > I do think we should perhaps import the vendor tree to contrib/stdtime or > some such and then apply our local patches from libc to there. I'd like to do the following: - identify what local patches we have and divide them into two parts: (a) issues already fixed upstream (b) issues not already fixed [or local changes] - import the latest stdtime into vendor - copy from vendor into our contrib/stdtime without flattening the structure - reapply all (b) patches manually This will make the mergeinfo correct and also make it clear what patches are local and what are upstream > Alternatively, > we could move the the files from libc into suitable locations in contrib/stdtime > and then do an 'svn merge --record-only' to bootstrap the vendor mergeinfo > for the current version and use that as a basis for updating? Exactly. -- Eitan Adler From owner-freebsd-arch@freebsd.org Fri Jun 15 18:31:48 2018 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 4353B101751C for ; Fri, 15 Jun 2018 18:31:48 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3D9C7CBA3 for ; Fri, 15 Jun 2018 18:31:47 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id E890D10AFAD; Fri, 15 Jun 2018 14:31:46 -0400 (EDT) Subject: Re: upstream for contrib/tzcode/stdtme? To: Eitan Adler References: Cc: "freebsd-arch@freebsd.org" From: John Baldwin Message-ID: <20a85a8f-29a7-0d8f-64d1-9ba005ffe79c@FreeBSD.org> Date: Fri, 15 Jun 2018 11:31:46 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 15 Jun 2018 14:31:47 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 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 Jun 2018 18:31:48 -0000 On 6/15/18 10:46 AM, Eitan Adler wrote: > On 15 June 2018 at 09:03, John Baldwin wrote: >> On 6/15/18 7:28 AM, Philip Paeps wrote: >>> On 2018-06-10 21:40:21 (+0200), Eitan Adler wrote: >>>> What's the upstream for contrib/tzcode/stdtme? >>> >>> https://www.iana.org/time-zones (and https://github.com/eggert/tz). >>> >>>> There are a couple of PRs for it and I'd like to either update, fix >>>> upstream, or move to non-contrib & fix. >>> >>> I've started updating it several times but the rather awkward layout of >>> the vendor tree makes doing just about anything else more attractive. :) >>> >>> More than happy to review an update if you actually manage to complete >>> one! > > I'll attempt one this weekend. :) > >>> I wonder if we should just make the "moving around files" in the vendor >>> tree go away... > > +1 > >> I do think we should perhaps import the vendor tree to contrib/stdtime or >> some such and then apply our local patches from libc to there. > > I'd like to do the following: > > - identify what local patches we have and divide them into two parts: > (a) issues already fixed upstream (b) issues not already fixed [or > local changes] > - import the latest stdtime into vendor > - copy from vendor into our contrib/stdtime without flattening the structure > - reapply all (b) patches manually > > This will make the mergeinfo correct and also make it clear what > patches are local and what are upstream > >> Alternatively, >> we could move the the files from libc into suitable locations in contrib/stdtime >> and then do an 'svn merge --record-only' to bootstrap the vendor mergeinfo >> for the current version and use that as a basis for updating? > > Exactly. I think this second approach is actually a better plan and is not quite what you were suggesting. That is, import the vendor bits corresponding to our existing code first into the vendor area, then svn cp our existing files from libc, zic, etc. into the contrib/stdtime tree in the correct layout and do a single 'svn merge --record-only' merge to initialize the vendor mergeinfo. At that point you should be able to svn diff contrib/stdtime against the vendor/stdtime/dist to determine what local changes we have and start to think about them. It also means that svn merge will consider them during your merge to the newer vendor sources without you have to manually apply patches in (b) while also preserving the commit history of those patches. -- John Baldwin From owner-freebsd-arch@freebsd.org Fri Jun 15 23:09:48 2018 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 7B4F5101FF0B for ; Fri, 15 Jun 2018 23:09:48 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::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 1606987A21 for ; Fri, 15 Jun 2018 23:09:48 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22d.google.com with SMTP id u124-v6so3893337ywg.0 for ; Fri, 15 Jun 2018 16:09:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HcasK9lk3rRbJDdt6+TzV98s/01PFVDM0G21Gsu/JDk=; b=iHShr2IpSYxh4Mg5odZp6BD/yd91GeovRaNIvXwlo7Q+Y0bKru3+cXoMcYPKmU+SLS 3L1JD0qFJZJ4ce+3If1QDW1ALV30nYRa8rbHQQ5BO/dbo8Xgn8tx4+5DlH5xxrbzK4/A wxZrrNVS8/Q72WbZef5Kimr+1OwVQd09juBMk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HcasK9lk3rRbJDdt6+TzV98s/01PFVDM0G21Gsu/JDk=; b=EVk2VZAPHNQ7L+dc3z69oanMkHRCSVYWZJkAh6KDjn6ICyps/EhaxWRDS1hpeSsU17 3n2gD8scyGphX6IaGjCn/DL0vULed/5FTwwLJSW6/jYB2yLoYqEVQy+K6SNnWphX1ul3 DUDWdwXTdQskc2PuVEk94M7eKdgQHANd1P2/kUDo31NCVNxvuPc7D4/n3iSjAIHbmrn/ rN+Zp73hyTk4v3mE8KmluOajMzctd1pWWDsvH6ML4g32afYranQFwWG30Vupm8cc4682 4AQf94+TSb+mZT5Tr0Fr8mrs4S7Idmj3Q4HxubJyqk/ObgmL9XuaLJCHsaTlSa9Dgo6A OkbA== X-Gm-Message-State: APt69E2u3ISjkPd0ym1vNuttRP5dYYLRLb/QUieofR9NtQYx4cfsZmuI MUX/90+Ggfq9LTZK4ioI035NrlI2R6X7onPYcDPDAg== X-Google-Smtp-Source: ADUXVKIdkl+fu+82ioEBcDvxFcQXpEeVRsqwlMXgCuyI0q3VtL4NJaXDoXwxpT+wtvOcoOWDixGcQ+0ZxVqyO88P8/I= X-Received: by 2002:a81:af1d:: with SMTP id n29-v6mr1930385ywh.113.1529104187501; Fri, 15 Jun 2018 16:09:47 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Fri, 15 Jun 2018 16:09:16 -0700 (PDT) In-Reply-To: <20a85a8f-29a7-0d8f-64d1-9ba005ffe79c@FreeBSD.org> References: <20a85a8f-29a7-0d8f-64d1-9ba005ffe79c@FreeBSD.org> From: Eitan Adler Date: Fri, 15 Jun 2018 16:09:16 -0700 Message-ID: Subject: Re: upstream for contrib/tzcode/stdtme? To: John Baldwin Cc: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.26 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 Jun 2018 23:09:48 -0000 On 15 June 2018 at 11:31, John Baldwin wrote: > I think this second approach is actually a better plan and is not quite what you > were suggesting. > > That is, import the vendor bits corresponding to our existing code first into > the vendor area, > then svn cp our existing files from libc, zic, etc. into the > contrib/stdtime tree in the correct layout and do a single 'svn merge --record-only' > merge to initialize the vendor mergeinfo. > At that point you should be able to > svn diff contrib/stdtime against the vendor/stdtime/dist to determine what local > changes we have and start to think about them. At this point both vendor and contrib have the same files, same layout, but possibly different content? How do we do the update itself then? "svn merge" from the vendor area into contrib? -- Eitan Adler