Date: Sat, 29 Jun 2024 16:37:33 +0200 From: Mario Marietto <marietto2008@gmail.com> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: Chris Moerz <freebsd@ny-central.org>, FreeBSD Virtualization Mailing List <freebsd-virtualization@freebsd.org> Subject: Re: OS Images(Linux/etc) in ports tree Message-ID: <CA%2B1FSii3a_%2BH43-8VkxDT%2BpW_tM9b93cW8zYx6bLTmWGmz8heQ@mail.gmail.com> In-Reply-To: <bur66nu6ytk7n5nnriwjy2oddrczsk3wse3zjvv2g6giaiohbl@xpbsmba6kp47> References: <CAD6yh%2BM_Z_HNcPavt4_TvGn9QhWPX8Q2qU12em3bUkfNXS1WSA@mail.gmail.com> <28dd6abb-5868-e42a-c385-37e72653ba2d@ny-central.org> <bur66nu6ytk7n5nnriwjy2oddrczsk3wse3zjvv2g6giaiohbl@xpbsmba6kp47>
next in thread | previous in thread | raw e-mail | index | archive | help
--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 <shawn.webb@hardenedbsd.= org> 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 <div dir=3D"ltr">I think that it may be possible to put only the VM config = files on the ports,<span class=3D"gmail-HwtZe" lang=3D"en"><span class=3D"g= mail-jCAhz gmail-JxVs2d gmail-ChMk0b"><span class=3D"gmail-ryNqvb">not nece= ssarily heavy image files.</span></span></span><span class=3D"gmail-ZSCsVd"= ></span><div class=3D"gmail-OvtS8d"><br></div></div><br><div class=3D"gmail= _quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Jun 29, 2024 at 4:26= =E2=80=AFPM Shawn Webb <<a href=3D"mailto:shawn.webb@hardenedbsd.org">sh= awn.webb@hardenedbsd.org</a>> wrote:<br></div><blockquote class=3D"gmail= _quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204= ,204);padding-left:1ex">On Sat, Jun 29, 2024 at 09:48:28AM +0200, Chris Moe= rz wrote:<br> > <br> > On Fri, 28 Jun 2024, Connor Cooper wrote:<br> > <br> > > 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<br> > > own images available for various operating systems and it's r= elatively easy to use compared to even standalone virtualization systems. C= onsidering the<br> > > 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<br> > > the input of the FreeBSD virtualization community regarding this = idea? Thanks.<br> > > Best regards,<br> > > Connor<br> > ><br> > ><br> > <br> > Hi Connor,<br> > <br> > The ports tree welcomes all sorts of software contributions. If you fe= el<br> > like setting utilities and scripts for providing OS images, you're= <br> > certainly free to do so.<br> > <br> > As long as you host your code publicly, put an appropriate license on = it<br> > 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<br> > Makefile as change diff to the ports tree via Phabricator<br> > (<a href=3D"http://reviews.freebsd.org" rel=3D"noreferrer" target=3D"_= blank">reviews.freebsd.org</a>).<br> > <br> > Please keep in mind, that our ports maintainers are all volunteers, so= <br> > creating and submitting a new port may take some time.<br> > <br> > One last thing, as my "2 cents", because this can quickly ha= lt such<br> > endeavors: please remember to consider any licensing issues related wi= th<br> > the use of any third party OS images. Downloading them as a single per= son<br> > may be straightforward but creating a means to download in "bulk&= quot; may<br> > cause discussions if the creators apply some terms of service or other= <br> > legal constraints...<br> <br> Also please keep in mind the storage capacity of smaller downstreams<br> that maintain their own package repos. It would be rather troublesome<br> of our package repos suddenly grew by multiple GBs without adequate<br> advanced notice.<br> <br> Thanks,<br> <br> -- <br> Shawn Webb<br> Cofounder / Security Engineer<br> HardenedBSD<br> <br> Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50<br> <a href=3D"https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Sha= wn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc" rel=3D"noreferrer= " target=3D"_blank">https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/m= aster/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc</a><br> </blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre= fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Mario.<br></d= iv> --00000000000027eee7061c085080--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B1FSii3a_%2BH43-8VkxDT%2BpW_tM9b93cW8zYx6bLTmWGmz8heQ>