How come I don't have nmap command on SmartOS ?

What might be the reason the vmadm rollback-napshot does not work.. # vmadm rollback-snapshot d578fc74-612c-43fc-cc33-9847b17e5b2a predocker

Command failed: cannot rollback 'zones/d578fc74-612c-43fc-cc33-9847b17e5b2a/disk0': out of space

It is bhyve HVM with Debian 10 inside that I upgraded woth openmediavault and now woudl like to get the VM state back before it.

nikolam: pkgin install nmap

Parent dataset had to small quota for /disk0 image and it's snapshot to .. roll back the snapshot.. hm. dunnon if that makes sense but I doulbled parent's quota and rollback worked

jperkin, somehow pkgin install nmap doesn't work for me.. let me see.

Maybe that thing about removing old publishing site from joyent to mnx/smartos.org for pkgsrc, could be wider documented, mentioned at least. Maybe that's it. old SmartOS VM that can't fetch newer packages because of that.

it's up on the website, I posted to the netbsd mailing lists and smartos-discuss, and miniblogged it on mastodon, did I miss anything?

On Wiki/documentation?

I'm not really keen on having multiple places where documentation lives, it's fine to post notices to interactive sources, but having multiple sources of truth just causes problems

Isn't wiki.smartos.org main one , at least regarding SmartOS? It is now a wiki per se

for SmartOS things yes, for pkgsrc it's pkgsrc.smartos.org

Huh I would always look under OS doc's why my packages can't update. it is OS-level big shift. github.com/TritonDataCenter/pkgsrc/wiki/about:migrations proves to be not obvious to find at least for my brain.

Maybe just link on SmartOS docs to changes for pkgsrc things would be enough. As you said, that is the main place for it and upgrading repo is the important point in time

Trying to passthrough a NVIDIA Tesla P4 card. Having trouble with the first stop. There is this ppt_aliases file that I have put in /usbkey/boot/etc/ppt_aliases and added the ppt_aliases_ specific stuff in /usbkey/boot/loader.conf. I am using piadm to boot from my Zones pool. If I just reboot, pptadm list does not show this device as available. My question is do I have to do something else

with piadm to make it see what is in /usbkey/ and update itself?

I just started using piadm a few weeks ago. Previousy I was booting from a USBKEY. When I would update something in the past I would have to mount the usbdrive and make changes there and reboot. Is there something similar with piadm?

kahlemt: The file needs to be on your boot pool. /usbkey is on the zones pool, which only gets mounted after all of the boot related stuff is well over.

Ah, thanks bahamat. /zones/boot/boot?

The /usbkey directory name is an unfortunate accident of history and something that I wish could be changed, because it doesn't really have anything to do with the physical USB or even the boot process.

kahlemt: Whatever your boot pool is.

Ok. Rebooting now. Fingers crossed! :)

Nope. I am still doing something wrong:

under /zones/boot is where all my piadm directorys are with a simlink to the currently used one set to boot. So this is /zones/boot/boot/

Also note that if your file is /etc/ppt_aliases, it will show up as /system/boot/etc/ppt_aliases

And the kernel will search /system/boot before searching /