On Sat, 10 Aug 2024 09:02:13 -0700 (PDT) "Rodney W. Grimes" <freebsd-...@gndrsh.dnsmgr.net> wrote:
> > Shawn Webb writes: > > > > > While probably less efficient than just running the tools outright, I > > > usually just set up a tmpfs that I chroot into and install those kinds > > > of packages. > > > > Yeah, I do something similar, with the footnote that I more often than > > not have no internet connection, so I have to remember to bring the > > packages. > > Build yourself a full release on USB and just be done with it. > The project keeps deleting stuff from base I find very useful, > I have given up on releases as a tool, I build a stick install > and tweak all the things I need, image it "just in case" and > keep it around for emergencies, and daily special use. > > A new stick is created for each release. > > > -- > Rod Grimes rgri...@freebsd.org Currently, IIRC, DVD image contains at least some of pkgs, while other images contains none. What would be useful for ALL images would be: *ports-mgmt/pkg, *All (at least, network interface ones) kmod ports which are allowed by their license and built with exactly the same src tree as the release itself. In some cases, any of kmod ports are needed to get internet access working, especially relatively new notebooks. What's important is, as already noted above, the bundled kmod ports SHALL be built with the kernel to be installed, exactly. For *.0 releases, there should be no problem with official pkgs. But for *.1 and later, official pkgs are built against oldest supported release of the corresponding stable branch, thus cause failing to kldload. Basically, my opinion is to force kmod ports to be always built from ports and stop providing official pkgs for them, but the above is the only exception. Internet access is needed to obtain/sync ports tree and distfiles to build. So kmods for "bootstrapping" would be important. For example, I've recently found this thread on forums.freebsd.org. [1] [1] https://forums.freebsd.org/threads/new-system-hardware-supported.93574/ -- Tomoaki AOKI <junch...@dec.sakura.ne.jp>
