Hi, new to OmniOS CE, have tried the old OmniOS/Napp-IT for a spell just to see how it works a year or two ago, but now am using it regularly in a VM for all my ZFS storage and NFS and SMB shares - I love that '# zfs set sharexxx=on pool/dataset' actually works!
It's been difficult to get adjusted to a Solarish system though. Two things really irk me.
1) Where's the scroll back buffer for the console? I mean, I can use | more - but FreeBSD (which I also use regularly) has scroll-lock to enable the scroll back buffer, and Linux has shift-pgup. Google has not helped me figure out how to do it in OmniOS - what gives?
2) I am having an issue with dladm/ipadm and vmxnet3. I followed this guide GeneralAdministration to set up my NICs and IPs -- I notice that the syntax for OmniOS and Solaris for dladm are different, which makes troubleshooting difficult as there are very few resources for OmniOS compared to Solaris.
I've installed vmwaretools 10.3.20 for the vmxnet3 driver and I have an internal-only vNIC that communicates using vmxnet3 just fine, and has been stable, but the one I used for a vNIC with a physical NIC took a crap on me, and now when I run
I get:
Any ideas?
Running OmniOS CE with Napp-It installed manually in an ESXi 6.7 VM. Current uname -a:
It's been difficult to get adjusted to a Solarish system though. Two things really irk me.
1) Where's the scroll back buffer for the console? I mean, I can use | more - but FreeBSD (which I also use regularly) has scroll-lock to enable the scroll back buffer, and Linux has shift-pgup. Google has not helped me figure out how to do it in OmniOS - what gives?
2) I am having an issue with dladm/ipadm and vmxnet3. I followed this guide GeneralAdministration to set up my NICs and IPs -- I notice that the syntax for OmniOS and Solaris for dladm are different, which makes troubleshooting difficult as there are very few resources for OmniOS compared to Solaris.
I've installed vmwaretools 10.3.20 for the vmxnet3 driver and I have an internal-only vNIC that communicates using vmxnet3 just fine, and has been stable, but the one I used for a vNIC with a physical NIC took a crap on me, and now when I run
Code:
# ipadm enable-addr vmxnet3s0/v4
Code:
ipadm: persistent operation not supported for enable-addr
Running OmniOS CE with Napp-It installed manually in an ESXi 6.7 VM. Current uname -a:
Code:
SunOS napp-it01 5.11 omnios-r151026-d9b45886bd i86pc i386 i86pc illumos