From owner-freebsd-cloud@freebsd.org Thu Jan 3 22:38:04 2019 Return-Path: Delivered-To: freebsd-cloud@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 0A80B1439E0B for ; Thu, 3 Jan 2019 22:38:04 +0000 (UTC) (envelope-from jay@sentenai.com) Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 759E86CAF8 for ; Thu, 3 Jan 2019 22:38:02 +0000 (UTC) (envelope-from jay@sentenai.com) Received: by mail-qk1-x736.google.com with SMTP id o8so4188970qkk.11 for ; Thu, 03 Jan 2019 14:38:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sentenai-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zhksf6/x5L2KGMp1XdR+VNijaHfESDe7pR/sAJlqj9c=; b=0BzEi0A2qeJWf75vLW/sIHyfC+7YQh/N1s4k/PrVnyIqZ+Jw7Ja2owvsYg1TBGoZkB 8NJthBot+Zu+B8cF81XLkRLj/nUxXjSVpB/eV/G2wBvpeeeDWfoKVeyQUdmaQGVEATOn WGiKgUVLGFdl/YmXBARbb/sekK9iD2+hlQ+Hlk8GoAdUz6dDAXW346pes600oqBmbppC Ic4OC4wowdO50NOb6RwEJrjkGkZmV8ouA9nLKxbPjh0KpO9y8iKFeWW9cr9PXu/i0Gdl fM4ZvP5Kh59fzeKzCiEdoSDms7JoxzF5aCNFMfZ9Scz0fO/dpAl3gV9oEP9eu4sLPe7I R9PA== 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=Zhksf6/x5L2KGMp1XdR+VNijaHfESDe7pR/sAJlqj9c=; b=Q9Mk9VDSkVXQzZ2H2PYvo085DU6bTw8Y7tC4L2Ps3g3MDcsZew11zQTv772ONaKcap wWTX+Fps8stcIbbN6h0FH5ftacY2ZguWUpxh+6q1RMGXCzt0J7JBex86xT1A2YIhzWHC J7xYH94msqFAQXFwsycxfWvhzJ073lUG+OtQ8lSZopv0UvvtRLs1/iANIzGibV6izMPD 3lC73scY7WamvDr+LH7vbeqy9P2Ze/IebsvTqjrD8nTPLtf0feQAOFSZ9KlTGM3oW+9k w9ZcilRKnMoD89QCqbG1VIJ3mHQOwK/xj7eJ33win8Ol66i/152UFWCVa4LYPG+9wA6K lR4A== X-Gm-Message-State: AJcUuke+R5XgAhJDeEAKsLaVbWtxDewN6NW86I0eBOWPKyHUVHMQg7jN uCFkVHlugF9bVCvf2cyhTXv6nh7eLBa0hxQERxBO X-Google-Smtp-Source: ALg8bN4rvJiJsNMIomsj9Xw5YhWLQwf17fiYY3d4nvxKoRRWkcgQG21pO4J6o8K+7ASy680Iz+3Z6nslKDF3deHGSGw= X-Received: by 2002:a37:ac5:: with SMTP id 188mr45561822qkk.135.1546555081657; Thu, 03 Jan 2019 14:38:01 -0800 (PST) MIME-Version: 1.0 References: <01000167dd7b16cd-58ee733f-c662-42d5-9c75-2301fbc8377a-000000@email.amazonses.com> <01000167f27b4bf1-86cf2251-ed4f-4f6f-88d7-9f2969338a57-000000@email.amazonses.com> In-Reply-To: <01000167f27b4bf1-86cf2251-ed4f-4f6f-88d7-9f2969338a57-000000@email.amazonses.com> From: Jay Edwards Date: Thu, 3 Jan 2019 17:37:50 -0500 Message-ID: Subject: Re: Any plans for EC2 AMIs with RootOnZFS? To: Colin Percival Cc: Ben Woods , freebsd-cloud@freebsd.org, "freebsd-fs@freebsd.org" X-Rspamd-Queue-Id: 759E86CAF8 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=sentenai-com.20150623.gappssmtp.com header.s=20150623 header.b=0BzEi0A2; spf=pass (mx1.freebsd.org: domain of jay@sentenai.com designates 2607:f8b0:4864:20::736 as permitted sender) smtp.mailfrom=jay@sentenai.com X-Spamd-Result: default: False [-4.08 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; URI_COUNT_ODD(1.00)[5]; DKIM_TRACE(0.00)[sentenai-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,alt4.aspmx.l.google.com,alt3.aspmx.l.google.com,alt2.aspmx.l.google.com,aspmx.l.google.com]; NEURAL_HAM_SHORT(-0.94)[-0.939,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.995,0]; R_DKIM_ALLOW(-0.20)[sentenai-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-cloud@freebsd.org]; DMARC_NA(0.00)[sentenai.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[6.3.7.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.63)[ip: (-9.30), ipnet: 2607:f8b0::/32(-2.15), asn: 15169(-1.64), country: US(-0.08)]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jan 2019 22:38:04 -0000 I've got a fairly robust collection of utilities for Google Cloud that: 1) Starts up an official FreeBSD image 2) Mounts a separate drive (the ZFS target) 3) Installs the release; installs all of the various GCP packages 4) Configures a bunch of custom stuff applicable to me 5) Creates an image that is then used as a base for any further custom images. It shouldn't be that difficult to add AWS support. Jay Edwards On Thu, Dec 27, 2018 at 8:48 PM Colin Percival wrote: > [Adding freebsd-fs in the hope of finding more ZFS people.] > > On 12/23/18 3:51 PM, Colin Percival wrote: > > On 12/23/18 7:12 AM, Ben Woods wrote: > >> Is there any plans to provide official FreeBSD AMIs in the AWS > Marketplace > >> which use RootOnZFS out of the box? > > > > Nothing concrete yet, but it's on my radar. Now that FreeBSD AMIs are > being > > published by a separate (release engineering) account, I'm more > comfortable > > with working on more "experimental" AMIs. (And if this turns out to be > widely > > useful I'll talk to the release engineering team about adding it to the > set > > they publish.) > > I've created an experimental FreeBSD 12.0 ZFS AMI in the us-east-1 region: > ami-0786f5b55d5aa573f > > Since I'm basically a ZFS newbie (I run it on my laptop, but only with the > default setup from the installer, and I've never used any of the fancy ZFS > features) I don't know if I've set everything up properly. So far I have > one piece of feedback, which is that I should have marked canmount=off for > zroot. > > Can people please try out this AMI and let me know if there's anything else > (ZFS-related) which I should fix? Some time next week I'll fix whatever > people notice and build AMIs for all the regions. > > -- > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid > _______________________________________________ > freebsd-cloud@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-cloud > To unsubscribe, send any mail to "freebsd-cloud-unsubscribe@freebsd.org" > From owner-freebsd-cloud@freebsd.org Sat Jan 5 00:05:05 2019 Return-Path: Delivered-To: freebsd-cloud@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 B88F2143F4CF for ; Sat, 5 Jan 2019 00:05:05 +0000 (UTC) (envelope-from bilbo@hobbiton.org) Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B4F98AE45 for ; Sat, 5 Jan 2019 00:05:03 +0000 (UTC) (envelope-from bilbo@hobbiton.org) Received: by mail-qt1-x836.google.com with SMTP id v11so42198460qtc.2 for ; Fri, 04 Jan 2019 16:05:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ofwilsoncreek-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OM0abPyZXm3oXQCUtkwH8nF6gsg/MkIw6cnEk0eDh6g=; b=PSAgNn8bBvS13NjeOJNRKEpn+xsLswd8tmAZ8YWgPmB3PCSfrDSDxri4+suCwTkSCx TOdaHX+05KEcTHlkk7fl7QsmP/qMyrQS7c96BJSWSE4rBAbhgG+sgS/eHeByW9Uiiyec fYhAMYVFN+P0lmgGXBW71CwvWnQky0r4YMlVw1y7g+NwIS0Iqpgw1Z4u6YUZaIiwa67h 22mE/LFUK/H3svULjUeBRW2B4CdgGTTvrg3ZzAKkjtGA7c5ky+nKlK8CyzkbkLvoObzo nHExhEs9zmi0Tm9ndae8pY4b5updY8kW3bQOwxF0+K2QpFzkIex7i5UhZ20PWAG0b2vO hHCg== 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=OM0abPyZXm3oXQCUtkwH8nF6gsg/MkIw6cnEk0eDh6g=; b=uG36XoyeRAW2aAdYxmd3Pz2SG7Wa8vrS8r+uHNTH3UBExiPre1gRwTOORUDYXdTBPi T9jpbFpzqh8VOSDDgZdq6TWS5iikXE9M9By1mj7hnnf/GbN285yGUqrFD//orwnTSexG DZ/CNmbuGl2y3z8WoiZefZkpGWwdxMIXAQNeFkAI3c7rYRgwr8jPGHqSNnElybPnm065 XHm2mNQaWc51XPUz1gVRRuJH3M/8f35JzBNB8eV6Q3CY/TeY6kHLbQ4aMeWmV3/WrJDe yNVQRkZJc3Sz1jJ+xlgoqZfCmy8ZufA4pDeUaQiUnUH7HqD2J6apzOEognPhh/kLqKb/ 22LQ== X-Gm-Message-State: AA+aEWYP+THOnkE3iplsAzQx5JlUgzXyH5TKNoz0qn6BvAr3ElvdAt8I p1q2O5JSsSiTbZAg5sv2Ew3eL5fp8C0xao6vklDNRQ== X-Google-Smtp-Source: ALg8bN7obtbxcb2z/MpYhZSIefMHCjmK1Qq84mGo3KKhWn7JP4GjjRT4pOI84BDiOrbKNXHnmkkADzgh9fh8+AZQ8yo= X-Received: by 2002:ac8:1941:: with SMTP id g1mr50088190qtk.193.1546646703098; Fri, 04 Jan 2019 16:05:03 -0800 (PST) MIME-Version: 1.0 References: <01000167dd7b16cd-58ee733f-c662-42d5-9c75-2301fbc8377a-000000@email.amazonses.com> <01000167f27b4bf1-86cf2251-ed4f-4f6f-88d7-9f2969338a57-000000@email.amazonses.com> In-Reply-To: From: Leif Pedersen Date: Fri, 4 Jan 2019 18:04:27 -0600 Message-ID: Subject: Re: Any plans for EC2 AMIs with RootOnZFS? To: Jay Edwards Cc: Colin Percival , "freebsd-fs@freebsd.org" , Ben Woods , freebsd-cloud@freebsd.org X-Rspamd-Queue-Id: 3B4F98AE45 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ofwilsoncreek-com.20150623.gappssmtp.com header.s=20150623 header.b=PSAgNn8b; spf=pass (mx1.freebsd.org: domain of bilbo@hobbiton.org designates 2607:f8b0:4864:20::836 as permitted sender) smtp.mailfrom=bilbo@hobbiton.org X-Spamd-Result: default: False [-3.84 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; URI_COUNT_ODD(1.00)[9]; RCPT_COUNT_FIVE(0.00)[5]; DKIM_TRACE(0.00)[ofwilsoncreek-com.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,aspmx2.googlemail.com,alt2.aspmx.l.google.com,aspmx3.googlemail.com]; NEURAL_HAM_SHORT(-0.98)[-0.984,0]; FORGED_SENDER(0.30)[leif@ofwilsoncreek.com,bilbo@hobbiton.org]; RCVD_TLS_LAST(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+]; FROM_NEQ_ENVFROM(0.00)[leif@ofwilsoncreek.com,bilbo@hobbiton.org]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; R_DKIM_ALLOW(-0.20)[ofwilsoncreek-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-cloud@freebsd.org]; DMARC_NA(0.00)[ofwilsoncreek.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[6.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.65)[ip: (-9.30), ipnet: 2607:f8b0::/32(-2.19), asn: 15169(-1.66), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2019 00:05:06 -0000 I worked out a procedure to convert a UFS filesystem to ZFS, and I've used it successfully many times on AWS and Azure instances. If the disk's data will fit in RAM, it works with a memory disk. Otherwise you can attach a second disk and substitute its device node for $extradisk. It is merely intended as a quick hack to convert after a new installation before putting important data on the machine, so it's not explained or robust. In other words, be sure you understand it before you use it, and very much use it at your own risk. But perhaps one could use the general idea to make a better process. http://devpit.org/wiki/Convert_UFS_to_ZFS Because of `reboot -r`, it works without disturbing the uptime (although it restarts all the services). That's a fun brag if you're into raising eyebrows. ("I changed the boot filesystem without rebooting...can you do that with _your_ favorite OS?") However, I'd suggest rebooting after to test the boot procedure and be sure you don't leave your future self an unpleasant 3 AM surprise. -Leif On Thu, Jan 3, 2019 at 4:38 PM Jay Edwards wrote: > I've got a fairly robust collection of utilities for Google Cloud that: > > 1) Starts up an official FreeBSD image > 2) Mounts a separate drive (the ZFS target) > 3) Installs the release; installs all of the various GCP packages > 4) Configures a bunch of custom stuff applicable to me > 5) Creates an image that is then used as a base for any further custom > images. > > It shouldn't be that difficult to add AWS support. > > Jay Edwards > > > On Thu, Dec 27, 2018 at 8:48 PM Colin Percival > wrote: > > > [Adding freebsd-fs in the hope of finding more ZFS people.] > > > > On 12/23/18 3:51 PM, Colin Percival wrote: > > > On 12/23/18 7:12 AM, Ben Woods wrote: > > >> Is there any plans to provide official FreeBSD AMIs in the AWS > > Marketplace > > >> which use RootOnZFS out of the box? > > > > > > Nothing concrete yet, but it's on my radar. Now that FreeBSD AMIs are > > being > > > published by a separate (release engineering) account, I'm more > > comfortable > > > with working on more "experimental" AMIs. (And if this turns out to be > > widely > > > useful I'll talk to the release engineering team about adding it to the > > set > > > they publish.) > > > > I've created an experimental FreeBSD 12.0 ZFS AMI in the us-east-1 > region: > > ami-0786f5b55d5aa573f > > > > Since I'm basically a ZFS newbie (I run it on my laptop, but only with > the > > default setup from the installer, and I've never used any of the fancy > ZFS > > features) I don't know if I've set everything up properly. So far I have > > one piece of feedback, which is that I should have marked canmount=off > for > > zroot. > > > > Can people please try out this AMI and let me know if there's anything > else > > (ZFS-related) which I should fix? Some time next week I'll fix whatever > > people notice and build AMIs for all the regions. > > > > -- > > Colin Percival > > Security Officer Emeritus, FreeBSD | The power to serve > > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly > paranoid > > _______________________________________________ > > freebsd-cloud@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-cloud > > To unsubscribe, send any mail to "freebsd-cloud-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-cloud@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-cloud > To unsubscribe, send any mail to "freebsd-cloud-unsubscribe@freebsd.org" > From owner-freebsd-cloud@freebsd.org Sat Jan 5 12:40:02 2019 Return-Path: Delivered-To: freebsd-cloud@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 62898149A143; Sat, 5 Jan 2019 12:40:02 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 757EB80D55; Sat, 5 Jan 2019 12:40:01 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-vs1-xe2a.google.com with SMTP id n13so24233477vsk.4; Sat, 05 Jan 2019 04:40:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=AQ1EbwmDWQV0b+XFN98hU/MksRovIw46xxVuqASzUZY=; b=rMMmbpjGytK0MXcj+ZrGf6W8XGLZB2gj7v/fYENnoJ1H3pqHLdf0xAmpfSzes69kS1 ZRmyTywEm0I2JlBd4r3U724F7i9usCCEku+p6EBAbhP1+cIxUnDmBNDfSA6CNQMSr8Cr 80JmBvNcv+LJrAxJibATk+m35fyuJe5M+lduA0xrcq723Nzs1LO4J/SDWmGGTQ6CqzpA Zeebcvy+gEq5FoBytvkR/8MA6Nz6nSe1KmhM7eNBORBW4vOgLY4v9T5g9PLqPJ5+V9EG o7o5zg18KY9GM1UhKDvCmPFjngihNTXViQ/TCQHMlKuV6B7OCFMz2YtPNhyDopoMJdbV Vs+Q== 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=AQ1EbwmDWQV0b+XFN98hU/MksRovIw46xxVuqASzUZY=; b=gO2RkeHXByJ729NH0uItYUNck93JjwcSQanHN5OGyTjOQawy0Hefgpzk8jZBvWNU4r I/Fe9vq/Gk1ygQpqZRnEFaVuucll/O+ECItg40mngu+Ay16nUSOhunua4oO19dV5VO4g kIciBxAqnM6+cj3nLD8/mCp/2/R5olsOGIBGooj0ib05kaS/Y7/kQ4ZZ2sN87NUL94tt c91osT9PfWiD1O3cfbAyrfu/V4fjwhj0vbPWWRMtujRJzyo+QWs+vMbLlmsGdQ+1l/6J UviDF5umHhn+jVtwh/CPhzzG8+bCUehb/6s2Msbl1LO1C3/NyiDtzLfEXSm+labAbTvT aXBA== X-Gm-Message-State: AA+aEWbcOIPN0Ys43uUe2J+LTMaR6C9NfUIiXOmDJkSKu+EN03jqxKP6 u6vHGIQ4c+uBZXaFv2jy1zdgy4871x1w1EAmrio= X-Google-Smtp-Source: AFSGD/U0XWrsWxiFsQVEHUvaS/NjXqPns5rTcbjQFEROy+HqxkVNfZOIJoBwuOVyh7FWu/VtFe3arLUB3aaNsHwfpNY= X-Received: by 2002:a67:1505:: with SMTP id 5mr19585653vsv.20.1546692000537; Sat, 05 Jan 2019 04:40:00 -0800 (PST) MIME-Version: 1.0 References: <01000167dd7b16cd-58ee733f-c662-42d5-9c75-2301fbc8377a-000000@email.amazonses.com> <01000167f27b4c13-41c15731-ae4c-4658-820d-80c4d4fbb01c-000000@email.amazonses.com> In-Reply-To: <01000167f27b4c13-41c15731-ae4c-4658-820d-80c4d4fbb01c-000000@email.amazonses.com> From: Ben Woods Date: Sat, 5 Jan 2019 23:39:57 +1100 Message-ID: Subject: Re: Any plans for EC2 AMIs with RootOnZFS? To: Colin Percival Cc: freebsd-cloud@freebsd.org, "freebsd-fs@freebsd.org" X-Rspamd-Queue-Id: 757EB80D55 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=rMMmbpjG; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of woodsb02@gmail.com designates 2607:f8b0:4864:20::e2a as permitted sender) smtp.mailfrom=woodsb02@gmail.com X-Spamd-Result: default: False [-4.17 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[5]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.43)[-0.431,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.73)[ip: (-9.71), ipnet: 2607:f8b0::/32(-2.19), asn: 15169(-1.67), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2019 12:40:02 -0000 On Fri, 28 Dec 2018 at 12:43, Colin Percival wrote: > I've created an experimental FreeBSD 12.0 ZFS AMI in the us-east-1 region: > ami-0786f5b55d5aa573f > > Since I'm basically a ZFS newbie (I run it on my laptop, but only with the > default setup from the installer, and I've never used any of the fancy ZFS > features) I don't know if I've set everything up properly. So far I have > one piece of feedback, which is that I should have marked canmount=off for > zroot. > Hi Colin, Thanks a lot for doing this - much appreciated. I have just given it a try, and have the following feedback for you: 1. ZFS DATASETS AND PROPERTIES SHOULD MATCH INSTALLER DEFAULT To avoid any confusion or unexpected behaviour, I believe the list of ZFS datasets and their properties should exactly match the bsdinstall defaults (especially for releases). zpool create: https://svnweb.freebsd.org/base/head/usr.sbin/bsdinstall/scripts/zfsboot?revision=342283&view=markup#l1308 zfs datasets and properties: https://svnweb.freebsd.org/base/head/usr.sbin/bsdinstall/scripts/zfsboot?revision=342283&view=markup#l141 Looking at how you created the zpool and zfs datasets (using the "zpool history zroot" command), the following changes would achieve this outcome: --- zfs-commands.old +++ zfs-commands.new @@ -1,19 +1,15 @@ -zpool create -o altroot=/mnt zroot ada0p2 -zfs set compress=on zroot +zpool create -o altroot=/mnt -O compress=lz4 -O atime=off -m none -f zroot ada0p2 zfs create -o mountpoint=none zroot/ROOT zfs create -o mountpoint=/ -o canmount=noauto zroot/ROOT/default zfs create -o mountpoint=/tmp -o exec=on -o setuid=off zroot/tmp -zfs create -o canmount=off -o mountpoint=/usr zroot/usr +zfs create -o mountpoint=/usr -o canmount=off zroot/usr zfs create zroot/usr/home -zfs create -o exec=off -o setuid=off zroot/usr/src -zfs create zroot/usr/obj -zfs create -o mountpoint=/usr/ports -o setuid=off zroot/usr/ports -zfs create -o exec=off -o setuid=off zroot/usr/ports/distfiles -zfs create -o exec=off -o setuid=off zroot/usr/ports/packages -zfs create -o canmount=off -o mountpoint=/var zroot/var +zfs create -o setuid=off zroot/usr/ports +zfs create zroot/usr/src +zfs create -o mountpoint=/var -o canmount=off zroot/var zfs create -o exec=off -o setuid=off zroot/var/audit zfs create -o exec=off -o setuid=off zroot/var/crash zfs create -o exec=off -o setuid=off zroot/var/log -zfs create -o atime=on -o exec=off -o setuid=off zroot/var/mail -zfs create -o exec=on -o setuid=off zroot/var/tmp +zfs create -o atime=on zroot/var/mail +zfs create -o setuid=off zroot/var/tmp zpool set bootfs=zroot/ROOT/default zroot 2. LOADER.CONF SETTINGS The following settings should be included in /boot/loader.conf: kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" 3. SYSCTL.CONF SETTINGS The following settings should be included in /etc/sysctl.conf: vfs.zfs.min_auto_ashift=12 4. THE GPT TABLE IS INITIALLY CORRUPT I suspect this is because I used a 50Gb disk, and it hasn't been expanded correctly. The following error was in DMESG and I suspect is related: GEOM: ada0: the secondary GPT header is not in the last LBA. I was able to fix this with the following commands on firstboot: # gpart recover ada0 # gpart resize -i 2 ada0 # zpool online -e zroot ada0p2 The full background of my investigation and resolution is shown below: # gpart show => 40 20971440 ada0 GPT (50G) [CORRUPT] 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 20967424 2 freebsd-zfs (10G) 20969472 2008 - free - (1.0M) # gpart recover ada0 ada0 recovered # gpart show => 40 104857520 ada0 GPT (50G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 20967424 2 freebsd-zfs (10G) 20969472 83888088 - free - (40G) # gpart resize -i 2 ada0 ada0p2 resized # gpart show => 40 104857520 ada0 GPT (50G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 104855512 2 freebsd-zfs (50G) # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zroot 9.50G 1.25G 8.25G - - 0% 13% 1.00x ONLINE - # zpool online -e zroot ada0p2 # zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zroot 49.5G 1.25G 48.3G - - 0% 2% 1.00x ONLINE - Thanks again for your efforts. Regards, Ben -- From: Benjamin Woods woodsb02@gmail.com From owner-freebsd-cloud@freebsd.org Sat Jan 5 22:14:28 2019 Return-Path: Delivered-To: freebsd-cloud@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 4248D1424E71; Sat, 5 Jan 2019 22:14:28 +0000 (UTC) (envelope-from SRS0=/O5A=PN=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A54F06F84A; Sat, 5 Jan 2019 22:14:27 +0000 (UTC) (envelope-from SRS0=/O5A=PN=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 2553528417; Sat, 5 Jan 2019 23:14:16 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 4BDAD28416; Sat, 5 Jan 2019 23:14:14 +0100 (CET) Subject: Re: Any plans for EC2 AMIs with RootOnZFS? To: Ben Woods , Colin Percival Cc: "freebsd-fs@freebsd.org" , freebsd-cloud@freebsd.org References: <01000167dd7b16cd-58ee733f-c662-42d5-9c75-2301fbc8377a-000000@email.amazonses.com> <01000167f27b4c13-41c15731-ae4c-4658-820d-80c4d4fbb01c-000000@email.amazonses.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Sat, 5 Jan 2019 23:14:13 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: A54F06F84A X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [5.56 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MX_GOOD(-0.01)[cached: elsa.codelab.cz]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=/O5A=PN=quip.cz=000.fbsd@elsa.codelab.cz]; FREEMAIL_TO(0.00)[gmail.com]; RECEIVED_SPAMHAUS_PBL(0.00)[209.16.49.86.zen.spamhaus.org : 127.0.0.11]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; SUBJECT_ENDS_QUESTION(1.00)[]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz,SRS0=/O5A=PN=quip.cz=000.fbsd@elsa.codelab.cz]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(0.95)[0.947,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.97)[0.974,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.997,0]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; IP_SCORE(0.45)[ip: (1.18), ipnet: 94.124.104.0/21(0.59), asn: 42000(0.47), country: CZ(0.04)]; R_SPF_NA(0.00)[] X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2019 22:14:28 -0000 Ben Woods wrote on 2019/01/05 13:39: > On Fri, 28 Dec 2018 at 12:43, Colin Percival wrote: > >> I've created an experimental FreeBSD 12.0 ZFS AMI in the us-east-1 region: >> ami-0786f5b55d5aa573f >> >> Since I'm basically a ZFS newbie (I run it on my laptop, but only with the >> default setup from the installer, and I've never used any of the fancy ZFS >> features) I don't know if I've set everything up properly. So far I have >> one piece of feedback, which is that I should have marked canmount=off for >> zroot. >> > Hi Colin, > > Thanks a lot for doing this - much appreciated. > > I have just given it a try, and have the following feedback for you: > > 1. ZFS DATASETS AND PROPERTIES SHOULD MATCH INSTALLER DEFAULT > To avoid any confusion or unexpected behaviour, I believe the list of ZFS > datasets and their properties should exactly match the bsdinstall defaults > (especially for releases). > zpool create: > https://svnweb.freebsd.org/base/head/usr.sbin/bsdinstall/scripts/zfsboot?revision=342283&view=markup#l1308 > zfs datasets and properties: > https://svnweb.freebsd.org/base/head/usr.sbin/bsdinstall/scripts/zfsboot?revision=342283&view=markup#l141 > > Looking at how you created the zpool and zfs datasets (using the "zpool > history zroot" command), the following changes would achieve this outcome: > --- zfs-commands.old > +++ zfs-commands.new > @@ -1,19 +1,15 @@ > -zpool create -o altroot=/mnt zroot ada0p2 > -zfs set compress=on zroot > +zpool create -o altroot=/mnt -O compress=lz4 -O atime=off -m none -f zroot > ada0p2 > zfs create -o mountpoint=none zroot/ROOT > zfs create -o mountpoint=/ -o canmount=noauto zroot/ROOT/default > zfs create -o mountpoint=/tmp -o exec=on -o setuid=off zroot/tmp > -zfs create -o canmount=off -o mountpoint=/usr zroot/usr > +zfs create -o mountpoint=/usr -o canmount=off zroot/usr > zfs create zroot/usr/home > -zfs create -o exec=off -o setuid=off zroot/usr/src > -zfs create zroot/usr/obj > -zfs create -o mountpoint=/usr/ports -o setuid=off zroot/usr/ports > -zfs create -o exec=off -o setuid=off zroot/usr/ports/distfiles > -zfs create -o exec=off -o setuid=off zroot/usr/ports/packages > -zfs create -o canmount=off -o mountpoint=/var zroot/var > +zfs create -o setuid=off zroot/usr/ports > +zfs create zroot/usr/src > +zfs create -o mountpoint=/var -o canmount=off zroot/var > zfs create -o exec=off -o setuid=off zroot/var/audit > zfs create -o exec=off -o setuid=off zroot/var/crash > zfs create -o exec=off -o setuid=off zroot/var/log > -zfs create -o atime=on -o exec=off -o setuid=off zroot/var/mail > -zfs create -o exec=on -o setuid=off zroot/var/tmp > +zfs create -o atime=on zroot/var/mail > +zfs create -o setuid=off zroot/var/tmp > zpool set bootfs=zroot/ROOT/default zroot I think the opposite - bsdinstall shoul be fixed to use exec=off and setuid=off. Just my $0.02 Miroslav Lachman From owner-freebsd-cloud@freebsd.org Sat Jan 5 22:31:36 2019 Return-Path: Delivered-To: freebsd-cloud@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 122EB1425602; Sat, 5 Jan 2019 22:31:36 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D2E5700D0; Sat, 5 Jan 2019 22:31:35 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-vs1-xe36.google.com with SMTP id z23so21465579vsj.11; Sat, 05 Jan 2019 14:31:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WOzm8TduS/naFb1n99u6o6s28Jilqgg8TF0DvE35hdY=; b=Bx6lsCrFMyDIEYS244UyzaQdc+EMTo04gFUTwJFXZVTJo9Q6NbnE7U1jPZsAw9Su9i nDANNB24Fu3ZJQUyTj641Gh6yyBj+gfS7eLOW5IdZgSEbQz++nWpN8VYJPpCq/O9ZjDp +pr6mJGxaVaikFheGBpPYiq+n1YWYaF6Hku4c3Md/SFqnyop1WYhZwEotcRqxR1LzuUi kk7rU9hfOZEZ7xQZkurCd0BbGX1AcVrOUii0vADn1DRgGeHglKZSZY+rlAgbk37fr0m4 4fQqxOn+dA1l3VHArIWK51R5dV0suvNOvOLx3NQZM+pmyuvDOCgTa346KL0UGrvnC2w8 HDoQ== 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=WOzm8TduS/naFb1n99u6o6s28Jilqgg8TF0DvE35hdY=; b=YQndWkggwa4IX3a9L2e+8Nff5Z7n9SMKjd7KE/Ct+CSiQJhiazXUt0esm9e9RNV5cw oX9m3FoBXNARSKQgvcXrOLXkzQdJFCTA+wQ6NRreSb/jcp57JMcPrCA6OOExTpb2fVRQ SlrPuj1UUe9gp+MeZfm3BlastRo5/heYL/wk4rHDxgjNnukfSypyh/UXuHQdIH8p7k2b bPfIEMdFbgQjlyAWQkjo4MS+Zj2vOAg3XCgc3Nq4dxwB+isXHGowoopfZiRgyusNcmxW 4y5a6AjXrsLaD7QtyMQTDz+QGwn8MT01ilnMOgpvTdpH9ZAC4Y5hW294OOkTfQPsI3s1 G4eQ== X-Gm-Message-State: AA+aEWbLGmeE+hsLA+25FpFTRBNMOAFV48+HIf8v8+nanfINDfUVGaTN UkhqXeS+ZYBiAD8pcf5mQNUvajL0QBaNsc+r7TDwXQ== X-Google-Smtp-Source: AFSGD/UKGqlQigAJQms3t2Q3IRdul/3Dj059cG88r+M9Zm6frLzbw1OFW2VqGGg6nRDS1uW2LIadgv8Hu0UdRjwLzss= X-Received: by 2002:a67:1505:: with SMTP id 5mr20097365vsv.20.1546727494514; Sat, 05 Jan 2019 14:31:34 -0800 (PST) MIME-Version: 1.0 References: <01000167dd7b16cd-58ee733f-c662-42d5-9c75-2301fbc8377a-000000@email.amazonses.com> <01000167f27b4c13-41c15731-ae4c-4658-820d-80c4d4fbb01c-000000@email.amazonses.com> In-Reply-To: From: Ben Woods Date: Sun, 6 Jan 2019 09:31:23 +1100 Message-ID: Subject: Re: Any plans for EC2 AMIs with RootOnZFS? To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Colin Percival , freebsd-cloud@freebsd.org, "freebsd-fs@freebsd.org" X-Rspamd-Queue-Id: 3D2E5700D0 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Bx6lsCrF; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of woodsb02@gmail.com designates 2607:f8b0:4864:20::e36 as permitted sender) smtp.mailfrom=woodsb02@gmail.com X-Spamd-Result: default: False [-5.73 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.97)[-0.974,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; SUBJECT_ENDS_QUESTION(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[6.3.e.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(-2.75)[ip: (-9.80), ipnet: 2607:f8b0::/32(-2.20), asn: 15169(-1.67), country: US(-0.08)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2019 22:31:36 -0000 On Sun, 6 Jan 2019 at 9:14 am, Miroslav Lachman <000.fbsd@quip.cz> wrote: > I think the opposite - bsdinstall shoul be fixed to use exec=3Doff and > setuid=3Doff. > > Just my $0.02 > > Miroslav Lachman > Hi Miroslav, I agree with you there. I just think that until that happens, the FreeBSD AWS EC2 images shouldn=E2= =80=99t take it upon themself to change the defaults - the place to change it is in bsdinstall for the next release. Regards, Ben --=20 -- From: Benjamin Woods woodsb02@gmail.com