I did a stage1 install last night. Due to my own stupidity, I forgot to copy /etc/resolv.conf into the chroot. /usr/portage was mounted from my file server via NFS. This is what I did: emerge metadata cd /usr/portage scripts/bootstrap.sh -v The last command failed while trying to download some code into /usr/portage/distfiles that wasn't on my file server yet. Since /etc/resolv.conf was missing, it couldn't resolve host names for downloading. I fixed this and started bootstrap again. It recognized that it failed last time and continued from where it stopped. I got this error message (typing out of my memory) --resume cannot be used with -v So, next try: starting bootstrap.sh without -v Message: bootstrap was completed, if you really want to run it, it will start from the beginning. So I had to boostrap from scratch. So, bootstrap (and portage?) do not act as expected when using "-v". The use of -v is not marked als discouraged as far as I know. Expected behaviour would be that bootstrap can continue even if "-v" is used at the command line. Perhaps it should filter it out, giving a warning about -v and --resume?
There's no message like that "--resume cannot be used with -v" in bootstrap.sh anywhere. This must be something in portage.
The "--resume cannot be used with -v" limitation is only in portage 2.0.x (fixed a few weeks ago in the 2.1 branch).
Fixed in rc portage, no time to really backport it to 2.0
