Quote:
Originally Posted by acampbell
...I don't understand what you mean by not using a "live" public ftp mirror.
|
What
J65nko describes is staging a new installation on an intermediate machine first. If, after installation, he is satisfied with
all parts of installation, he then installs the kernels, filesets, &
saved packages
(saved through use of the PKG_CACHE variable...).
The installation on the second computer is all done locally.
- Installation of the base installation filesets is done from a mounted disk. I also live on -current, & the filesets I keep are either on a USB drive or burned to CD.
- Packages can be installed locally too. Packages in their original *.tgz form can also be saved to a USB drive or burned CD or DVD too. When I install packages I have saved, I don't bother with setting PKG_PATH on the second machine. It is not needed. I install packages from a mounted drive.
Why save the packages'
*.tgz files downloaded from a mirror? Because bulk builds are done often enough that anything I install last week may be overwritten by newer packages which were built with newer incompatible libraries found in newer snapshots. The landscape of
-current is always changing.
Quote:
So what do you use - perhaps have the same bsd.rd on both machines? Could you enlarge on this please?
|
Your assumption here is that the configuration of what mirror is used is saved in the kernel. This is incorrect.
PKG_PATH is simply an environment variable. Many have it set to a fixed value in their
~/.profile such that it is constantly set to the same value during every session. The purpose of
PKG_PATH is to simplify what parameters need to be manually supplied to
pkg_add such that it will retrieve the desired files from a remote server. When installing locally, this convenience is not required.