I have pkgbox.dragonflybsd.org set up to regularly build up-to-date binary
packages from the most recent 'stable' release of pkgsrc.

What I'd like to do is restrict access to mirrors only, with rsync.  This
would entail a username and password (separate from any existing accounts
on leaf or other dragonflybsd.org machines) for use for rsync only.

If you run one of the mirrors below, please let me know what you want your
username/password to be - and tell me if rsync won't work out.  (it looks
like the most efficient choice right now)

chlamydia.fs.ei.tum.de
TheShell.com
TWAREN FTP
dragonflybsd.kiev.ua

Also - if you want to set up a new mirror, please tell me.

Evil Plan Part 2:

I found pkg_add (and I think 'make bin-install') can be set to use a CGI
target that will accept redirects to mirror sites.  The Plan is to set a
redirect script up on pkgbox.dragonflybsd.org, and then modify the default
shell profiles/rc files on DragonFly to point at that URL.

The goal of the Plan is to make any new DragonFly system able to install
software 'out of the box'.  You then do not have an out-of-date pkgsrc src
tree, and you do have a relatively reliable network installation system
that works immediately and probably faster than building from source.

Does anyone have an objection to 'The Plan'?

reminds me of the discussions before 1.10 on the bsdinstaller and also
the nrelease build.. I was just investigating
this part of things trying to find out why a netboot would work on
my machine from the installer, but not from the local boot server I'm
trying to setup (anyone have ideas here - BTX error & reboot ?..)

In any case, some notes on the installer while trying to figure out
how it works / where the code is (also - this didn't seem to be 100%
resolved and will probably bite again)

http://bugs.dragonflybsd.org/issue730 : the installer update issue

threads on same:

http://leaf.dragonflybsd.org/mailarchive/bugs/2007-07/msg00109.html
http://leaf.dragonflybsd.org/mailarchive/kernel/2007-05/msg00090.html
http://leaf.dragonflybsd.org/mailarchive/users/2007-07/msg00103.html

from what I can tell / recall (those directly involved please correct! -
this message is just trying to gather the pieces together)

- bsdinstaller itself had progressed beyond what was being maintained
  for dragonfly (main problem is lua 5.0 -> 5.1 compatibility?)
- scripts + dfui lua extension needed updating to match the installer
- not enough testing was done / time was available to include the
  updates Simon / Gergo / et. al. made related to this for the release
- the 1.10 installer was as a result based on the previous version
  with script updates to handle the disklabel / slice reworking

Links to updated sources for the 'experimental' updated version are
available in the ticket ref. above.

There are also some packages Joerg is maintaining in pkgsrc relating to
the installer:

sysutils/dfuibe_installer & devel/libinstaller .. not sure where the
'real deal' installer is there .. will probably investigate in the next
few days.

Installer is created as follows (second hand - again please correct)

- build installer from scratch somehow ???
- configure appropriate package URL into nrelease makefile
- create an installer image via make installer_release
- enjoy

questions ...
[ message continues ]