Quickstart

This gives some quickstart info about using freebsd-rustdate based on your existing knowledge and workflow with freebsd-update.

For details of freebsd-rustdate’s commands and arguments, see the commands reference.

See the missing pieces page for things that are known not to be supported (many not intended to be).

See the differences page for some discussion of general differences between freebsd-update and freebsd-rustdate.

Contents

Normal Day-To-Day Usage

As with freebsd-update, the basic usage of freebsd-rustdate mostly falls into the fetch (update current release to new patches) and upgrade (update current release to new release) paths. The commands for running those are pretty much the same as freebsd-update.

# freebsd-rustdate fetch
  [ lotsa output ]
# freebsd-rustdate install

# freebsd-rustdate upgrade -r 13.8-RELEASE
  [ even more lotsa output ]
  [ run `freebsd-rustdate resolve-merges` if you have conflicts]
# freebsd-rustdate install
  [ reboot new kernel ]
# freebsd-rustdate install
  [ rebuild packages with new world ]
# freebsd-rustdate install

When running upgrade, any merge conflicts needing resolved will be done via the resolve-merges command, not during the upgrade run itself.

There’s a fair amount of online --help available too, on the various commands. And the commands reference on this site has more.

Configuration

freebsd-rustdate reads the same /etc/freebsd-update.conf (or another location given on the command line) as freebsd-update, and uses (a subset of) the same config, so you shouldn’t need to change anything.

Help

freebsd-rustdate can tell you a lot about itself, just ask. Running the help command will show a summary of the overall args, and the individual commands. Running help <cmd> individually will tell you more about it. See the online reference for more.

Shared Storage

freebsd-rustdate uses similar local storage to freebsd-update, so a lot of that is shared. Particularly, the files/ dir, which both use to cache the downloaded data and stashed up info from the current system. So either of them will be able to use files the other downloaded, and not download them again. Assuming both are using the same WorkDir of course.

However, the metadata for updates is not shared. That means that you can’t do a fetch with one and then install with the other, or vice versa. Neither will know anything about any pending stuff the other has queued up.