wifibox port/src install via DVD without internet possible? (Noob read handbook)

[rotaecho]

Howdy, I read the handbook section: https://docs.freebsd.org/en/books/handbook/ports/

As the source section, but I must be missing something. I haven't touched FreeBSD in decades, but I remember installing ports/src via the DVD installer and not requiring an internet connection.

On the DVD install, I stated src and ports to be installed. But every time I try to use pkg or run a Make it's trying to go get something off the internet.

I'm trying to test FreeBSD on a laptop, but I need to get wifibox installed. I was hoping I could install wifibox via the DVD copied source/ports and manually build with what was provided by the DVD iso.

Is that possible, or is an internet required for any source / port install?

My search in the forum/google didn't bring much results of installing/source compile against the DVD provided material.

Thanks for any insight!

-Will

 

[richardtoohey2]

So which exact image did you use to make your DVD?

What platform is this? amd64?

What exact pkg command are your trying, as an example?

The DVD cannot hold everything on it so chances are at some point it will have to go to the internet.

It’s not something I’ve tried in a long time!

You are also talking about ports and packages on the DVD so think you might be mixing things up.

ports are likely to just be meta data - instructions on where to get the required files for building from the internet.

But I think some packages are still on the DVD so there might be a way to install one of those.

 

[Deleted member 81054]

The DVD cannot hold everything on it so chances are at some point it will have to go to the internet.

You can point the pkg system at a local repository, as well.

E.g., I have a /Source "partition" (which may be on a different spindle) which contains things like ./src (symlinked to from /usr/src), ./xsrc, ./pkgsrc, ./distfiles plus any of my own sources. This, separate from /Repository (for obvious reasons).

This lets me keep other bits of the hierarchy (partitions) small as, typically, if something goes south, you don't need access to the "sources" as much as you do to other BINARIES. So, those want to be available all the time.

 

[rotaecho]

Upon research it's not like Slackware or what I vaguely remember with freeBSD of past where it was able to keep a good majority of the software source local and one just needed to compile from that.

I guess the software tree has gotten too big for that.

This was on amd64, but the pkg and ports (make install) commands failed as each tried to reach the internet.

I was able to get a wired connection working to download software. Of which I was able to install packages as ports (for driver install)

Thanks

 

[Deleted member 81054]

I guess the software tree has gotten too big for that.

Yes. In an effort to "port everything", there are just too many "packages" (and their corresponding sources)

I was able to get a wired connection working to download software.

I've been maintaining an off-line "distfiles" directory that I routinely update from various mirrors. So, I can point the build mechanism at *it* (e.g., a local URL) and let if "fetch" the sources that it needs.

Periodically, I incrementally update that repository in an effort to stay ahead of the problem as I never know what I might want to build, next week, or a year from now on an "old" RELEASE. (It's REALLY annoying to have to update the OS just because some older package is no longer available)

 

[rotaecho]

I did that for my Solaris & Linux machines in the past; host the local software repo. I may do the same for FreeBSD too.

Yes. In an effort to "port everything", there are just too many "packages" (and their corresponding sources)


I've been maintaining an off-line "distfiles" directory that I routinely update from various mirrors. So, I can point the build mechanism at *it* (e.g., a local URL) and let if "fetch" the sources that it needs.

Periodically, I incrementally update that repository in an effort to stay ahead of the problem as I never know what I might want to build, next week, or a year from now on an "old" RELEASE. (It's REALLY annoying to have to update the OS just because some older package is no longer available)