From nobody Sat Jun 29 14:37:33 2024 X-Original-To: freebsd-virtualization@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WBFKM0CqQz5NmtR for ; Sat, 29 Jun 2024 14:38:15 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WBFKK3Nylz4wLY for ; Sat, 29 Jun 2024 14:38:13 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1faad2f1967so20286625ad.0 for ; Sat, 29 Jun 2024 07:38:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719671891; x=1720276691; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=En4SbJ/d3o0lAM45P15XUyQsBsCcER+OTj0G2SJrA+Y=; b=bCsLuzmxSftYkRgny85LzNsl8OW0oyeCw6BcNI73QC0Sq8glpKyCd8AP4TFuZITKuT I2yS1hNlNfwfcRviU+cQQrQxZY70AKYLv6Rl8wucGsuKabqtLHFQeU433wyJptzByE0f UpjlUWVnUMFLt8VOLATgC8/d6yKxMFajU1yEQ6nw029N7ULGVqJEr9eL6d4Fj56mODF1 0NdvmHrVGaO6IIGftS8rL29HukF3W3A1rtGc8rmVnweMGjALmCPYJmdg9FmnGfAmOgPk +oAfJOGbPgHm8dGpgLrOSZiBQtoQ49uaZ+fLGxDgmTVSfNSCmdagYPK1n19hEJLJ1tKF CAFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719671891; x=1720276691; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=En4SbJ/d3o0lAM45P15XUyQsBsCcER+OTj0G2SJrA+Y=; b=GWBDyMbSQ86riYQocUeT9M12yNlubr1DH8KdKPDpphWxJXXTBJ5WHAw9rm2ndqnUa/ CEHv/14ajVAYaDg00DxONf3zsU77grU7+CewF1wkQswp1q603dpWYISUGxR1lv7zBFyW PL4Z78SVWu2Weh2iiHu6DTA/VUui2RIz3g15dW/juLI0p0h8UvxvY1JOOuX66Dfm04AB bgKKOBIgoP3k7QgwakjXQjJ4Re/lNTETSXjyoBfIcn4dHc0+8iBHVnNR48O0DcNAYwOG O9l19J2QJwi9Ww2FS1gmlEJpW8WjRfafVDvsttDEQMBC6zWh125rGNYQzvcbftkF4LDE /cEw== X-Forwarded-Encrypted: i=1; AJvYcCVA6VYuTum90H+HDlcrhYudhv4zYJJbWd0XI03fo0YWJGJuh3avrFNQZPUnV5bv7eK46E1mR7w4oU3dywEOs1LFSIKVwwiNK6JjKVhcTcRIb4mR X-Gm-Message-State: AOJu0YwgJt7S+5wq9/wA8CAKLO+S679wiuPHeJrGeTxmvbE1oFKE2jgQ v2TLRNtGjXDzeQabls3gZntkCNqSJlwHndOlR1bwfWGO4MkkF7doxwzUmZ1vjwQKaR5s1TGsm0X +Np/hAAtRU8T4SXPbQkRQIYwdlZY= X-Google-Smtp-Source: AGHT+IGq6lfvUovFKOz6Uns7Ib044+URxoxRUFa7/keIW69f8vkKUbDviwGEPDYN2OloNCwju4RIT44mbCGvRQVUYRY= X-Received: by 2002:a17:90b:d8b:b0:2c8:8e09:eecf with SMTP id 98e67ed59e1d1-2c927653000mr7011434a91.10.1719671890370; Sat, 29 Jun 2024 07:38:10 -0700 (PDT) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-virtualization@freebsd.org Sender: owner-freebsd-virtualization@FreeBSD.org MIME-Version: 1.0 References: <28dd6abb-5868-e42a-c385-37e72653ba2d@ny-central.org> In-Reply-To: From: Mario Marietto Date: Sat, 29 Jun 2024 16:37:33 +0200 Message-ID: Subject: Re: OS Images(Linux/etc) in ports tree To: Shawn Webb Cc: Chris Moerz , FreeBSD Virtualization Mailing List Content-Type: multipart/alternative; boundary="00000000000027eee7061c085080" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WBFKK3Nylz4wLY --00000000000027eee7061c085080 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I think that it may be possible to put only the VM config files on the ports,not necessarily heavy image files. On Sat, Jun 29, 2024 at 4:26=E2=80=AFPM Shawn Webb wrote: > On Sat, Jun 29, 2024 at 09:48:28AM +0200, Chris Moerz wrote: > > > > On Fri, 28 Jun 2024, Connor Cooper wrote: > > > > > Hello, I am presenting you all with an idea for the bhyve project tha= t > involves the ports tree. I've noticed that a lot of VPS providers have th= eir > > > own images available for various operating systems and it's relativel= y > easy to use compared to even standalone virtualization systems. Consideri= ng > the > > > existence of FreeBSD and bhyve I also just noticed that the ports tre= e > could be a good potential place for bhyve users to access those images. > What is > > > the input of the FreeBSD virtualization community regarding this idea= ? > Thanks. > > > Best regards, > > > Connor > > > > > > > > > > Hi Connor, > > > > The ports tree welcomes all sorts of software contributions. If you fee= l > > like setting utilities and scripts for providing OS images, you're > > certainly free to do so. > > > > As long as you host your code publicly, put an appropriate license on i= t > > and create a ports Makefile, you can submit that through Bugzilla for > > inclusion into the ports tree. It's also helpful to submit your ports > > Makefile as change diff to the ports tree via Phabricator > > (reviews.freebsd.org). > > > > Please keep in mind, that our ports maintainers are all volunteers, so > > creating and submitting a new port may take some time. > > > > One last thing, as my "2 cents", because this can quickly halt such > > endeavors: please remember to consider any licensing issues related wit= h > > the use of any third party OS images. Downloading them as a single pers= on > > may be straightforward but creating a means to download in "bulk" may > > cause discussions if the creators apply some terms of service or other > > legal constraints... > > Also please keep in mind the storage capacity of smaller downstreams > that maintain their own package repos. It would be rather troublesome > of our package repos suddenly grew by multiple GBs without adequate > advanced notice. > > Thanks, > > -- > Shawn Webb > Cofounder / Security Engineer > HardenedBSD > > Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 > > https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/0= 3A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc > --=20 Mario. --00000000000027eee7061c085080 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I think that it may be possible to put only the VM config = files on the ports,not nece= ssarily heavy image files.


On Sat, Jun 29, 2024 at 4:26= =E2=80=AFPM Shawn Webb <sh= awn.webb@hardenedbsd.org> wrote:
On Sat, Jun 29, 2024 at 09:48:28AM +0200, Chris Moe= rz wrote:
>
> On Fri, 28 Jun 2024, Connor Cooper wrote:
>
> > Hello, I am presenting you all with an idea for the bhyve project= that involves the ports tree. I've noticed that a lot of VPS providers= have their
> > own images available for various operating systems and it's r= elatively easy to use compared to even standalone virtualization systems. C= onsidering the
> > existence of FreeBSD and bhyve I also just noticed that the ports= tree could be a good potential place for bhyve users to access those image= s. What is
> > the input of the FreeBSD virtualization community regarding this = idea? Thanks.
> > Best regards,
> > Connor
> >
> >
>
> Hi Connor,
>
> The ports tree welcomes all sorts of software contributions. If you fe= el
> like setting utilities and scripts for providing OS images, you're=
> certainly free to do so.
>
> As long as you host your code publicly, put an appropriate license on = it
> and create a ports Makefile, you can submit that through Bugzilla for<= br> > inclusion into the ports tree. It's also helpful to submit your po= rts
> Makefile as change diff to the ports tree via Phabricator
> (reviews.freebsd.org).
>
> Please keep in mind, that our ports maintainers are all volunteers, so=
> creating and submitting a new port may take some time.
>
> One last thing, as my "2 cents", because this can quickly ha= lt such
> endeavors: please remember to consider any licensing issues related wi= th
> the use of any third party OS images. Downloading them as a single per= son
> may be straightforward but creating a means to download in "bulk&= quot; may
> cause discussions if the creators apply some terms of service or other=
> legal constraints...

Also please keep in mind the storage capacity of smaller downstreams
that maintain their own package repos. It would be rather troublesome
of our package repos suddenly grew by multiple GBs without adequate
advanced notice.

Thanks,

--
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/m= aster/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc


--
Mario.
--00000000000027eee7061c085080--