Re: OS Images(Linux/etc) in ports tree
- Reply: Chris Moerz : "Re: OS Images(Linux/etc) in ports tree"
- In reply to: Shawn Webb : "Re: OS Images(Linux/etc) in ports tree"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 29 Jun 2024 14:37:33 UTC
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 PM 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 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 relatively > easy to use compared to even standalone virtualization systems. Considering > 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 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 feel > > 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 > > 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 with > > the use of any third party OS images. Downloading them as a single person > > 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/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc > -- Mario.