Re: [OpenIndiana-discuss] Why networking not work?

2021-04-27 Thread John D Groenveld
In message , "Nelson H. F. Bee
be" writes:
>The network setup on VirtualBox on vboxhost.example.com is unusual: its
>initial network is not bidirectional!  It only connects outbound.

When I use illumos as the host, I find it easier to dladm create an
etherstub and vnics for the host and the VBox guest.
Then I configure the VBox bridge adapter to pass the guest vnic.

This type of configuration is almost certainly possible with FreeBSD
and linux as the host.
John
groenv...@acm.org

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


[OpenIndiana-discuss] X startup/shutdown questions

2021-04-27 Thread Reginald Beardsley via openindiana-discuss
What service starts the MATE environment?  I've been unable to locate what 
starts that.  And generally unable to determine how exactly what any service 
does is specified.

I'd expected "init 2" in single user mode to take me to multi-user console 
mode, but it did not.  However, I was able to disable lightdm, come up to a 
multiuser console, login and start X and twm using startx(1) and the .xinitrc 
file on the command line.  However, when I exited twm it did not return to the 
login console.  What controls that?  Do I need something in .xinitrc?  I never 
did it that way but I remember it could be done.

I haven't messed with this in 15+ years.  I'm happy to say it appears that 
significant progress has been made.  The implementation of CDE was rather 
painful as was Motif.  So much so that I've been disinclined to even look at it 
for a long time.  Kudos to those who fixed it.

Firefox under twm did generate a GDK resource unavailable error in a short 
test, but that's mild compared to what I recall seeing if I started Netscape 
outside of the dtwm environment.  It almost certainly had to be dumping core 
for me to labor through starting separate window managers on each screen.

Reg

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] Why networking not work?

2021-04-27 Thread Volker A. Brandt
Nelson H. F. Beebe writes:
> The network setup on VirtualBox on vboxhost.example.com is unusual: its
> initial network is not bidirectional!  It only connects outbound.
> 
> In order to get inbound connections for ssh, it is necessary to add a
> second network adapter, which can only be down in powered-off state:
> 
>   VirtualBox control panel ->
>   Settings -> Network -> Adapter2 -> Attached-to -> Host-only 
> adapter
>   Name: vboxnet0
> 
> plus
>   Advanced ->
>   Adapter Type -> Intel PRO/1000 MT +
>   Promiscuous Mode: Deny +
>   Cable Connected
> 
> For the original Adapter1, we have
> 
>   VirtualBox control panel ->
>   Settings -> Network -> Adapter1 -> Attached-to -> NAT
> plus

If you select "Bridged Network" here, you don't need a second adapter.
See chapter 6.3 ("Bridged Networking") in the VirtualBox user manual:

  https://download.virtualbox.org/virtualbox/6.1.20/UserManual.pdf

If you only need to ssh into the VM from the VirtualBox host, a port
forwarding rule is also a good solution, as it is more secure.  You
just assign a port and run "ssh -p  localhost".


Cheers -- Volker
-- 

Volker A. BrandtConsulting and Support for Solaris-based Systems
Brandt & Brandt Computer GmbH   WWW: http://www.bb-c.de/
Am Wiesenpfad 6, 53340 Meckenheim, GERMANYEmail: v...@bb-c.de
Handelsregister: Amtsgericht Bonn, HRB 10513  Schuhgröße: 46
Geschäftsführer: Rainer J.H. Brandt und Volker A. Brandt

"When logic and proportion have fallen sloppy dead"

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] Why networking not work?

2021-04-27 Thread Nelson H. F. Beebe
"L. F. Elia"  asks about networking on VirtualBox.

We too found its behavior different from other virtualization systems, 
and I tend to write copious notes about machine issues.  Here is a
fragment of those notes, with generalized hostnames:

The network setup on VirtualBox on vboxhost.example.com is unusual: its
initial network is not bidirectional!  It only connects outbound.

In order to get inbound connections for ssh, it is necessary to add a
second network adapter, which can only be down in powered-off state:

VirtualBox control panel ->
Settings -> Network -> Adapter2 -> Attached-to -> Host-only 
adapter
Name: vboxnet0

plus
Advanced ->
Adapter Type -> Intel PRO/1000 MT +
Promiscuous Mode: Deny +
Cable Connected

For the original Adapter1, we have

VirtualBox control panel ->
Settings -> Network -> Adapter1 -> Attached-to -> NAT
plus
Advanced ->
Adapter Type -> Intel PRO/1000 MT +
Promiscuous Mode: Deny +
Cable Connected +
Port Forwarding

On a reboot, the VM will have two networks, like this example for
guest.example.com:

% ifconfig -a
em0: flags=8843 metric 0 mtu 
1500

options=85059b
ether 08:00:27:f2:0b:cc
inet 10.0.2.15 netmask 0xff00 broadcast 10.0.2.255
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active
em1: flags=8843 metric 0 mtu 
1500

options=85059b
ether 08:00:27:36:0b:70
inet 192.168.56.101 netmask 0xff00 broadcast 192.168.56.255
nd6 options=29
media: Ethernet autoselect (1000baseT )
status: active
...

sshd normally listens on all network interfaces, so from the
VirtualBox host, vboxhost.example.com, I can now do

ssh USER@192.168.56.101

and with suitable $HOME/.ssh/config settings, such as this on
anotherhost.example.com,

Host = guest.example.com guest
User = jones
HostName = 192.168.56.101
ProxyJump vboxhost.example.com

I can now ssh from anotherhost to the VM on VirtualBox on vboxhost.

---
- Nelson H. F. BeebeTel: +1 801 581 5254  -
- University of UtahFAX: +1 801 581 4148  -
- Department of Mathematics, 110 LCBInternet e-mail: be...@math.utah.edu  -
- 155 S 1400 E RM 233   be...@acm.org  be...@computer.org -
- Salt Lake City, UT 84112-0090, USAURL: http://www.math.utah.edu/~beebe/ -
---

___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] VirtualBox 6.1.18 nested vms

2021-04-27 Thread Chris

On 2021-04-27 08:32, L. F. Elia via openindiana-discuss wrote:
From what I recall, nested virtualization might require BIOS changes (at 
least on DELL). Good luck!


lfe...@yahoo.com, Portsmouth VA, 23701
Solaris/LINUX/Windows administration CISSP/Security consulting

On Thursday, April 1, 2021, 07:16:20 AM EDT, russell
 wrote:

 Hi

For what I have read VirtualBox 6.1 introduced the capability to have
nested VMs.

I have created a VM to run VMware 6.7.0u3, however when I attempt to
start any VM inside ESX 6.7.0u3 I get the following message

Failed to power on virtual machine Lethe. This host does not support
"AMD RVI" hardware assisted MMU virtualization. Click here for more
details.

While I haven't examined the specs for your specific version of the AMD CPU.
You won't get the information you desire from the VM. What you're really 
after
is what the VM HOST provides. I think your best bet is to have a look at 
dmesg

specifically dmesg.boot. It's the messages generated during boot. In FreeBSD
parlance; dmesg -a would give it to you, as would; less /var/run/dmesg.boot 
--

Sorry, I don't have my OI box handy to give you the exact incantation for OI.
Another thing to have a peek at is within your BOIS. You will need to be sure
you have VM option(s) enabled in order to expose them to the host OS.

HTH

--Chris


-

Looking at the log for the VBox VM

00:00:00.812397 Ext Name:    AuthenticAMD
00:00:00.812398 Ext Supports: 0x8000-0x801e
00:00:00.812398 Family:  15      Extended: 10
     Effective: 25
00:00:00.812398 Model:   1      Extended: 2    
Effective: 33
00:00:00.812399 Stepping:    0
00:00:00.812399 Brand ID:    0x000
00:00:00.812399 Ext Features
00:00:00.812399   Mnemonic -
Description  = guest (host)
00:00:00.812400   FPU - x87 FPU on
Chip   = 1 (1)
00:00:00.812400   VME - *Virtual 8086 Mode Enhancements* = 1 (1)
00:00:00.812401   DE - Debugging
extensions   = 1 (1)
00:00:00.812401   PSE - Page Size
Extension   = 1 (1)
00:00:00.812402   TSC - Time Stamp
Counter    = 1 (1)
00:00:00.812403   MSR - K86 Model Specific
Registers  = 1 (1)
00:00:00.812403   PAE - Physical Address
Extension    = 1 (1)
00:00:00.812404   MCE - Machine Check
Exception   = 0 (1)
00:00:00.812404   CX8 - CMPXCHG8B
instruction = 1 (1)
00:00:00.812405   APIC - APIC
On-Chip = 1 (1)
00:00:00.812405   SEP -
SYSCALL/SYSRET    = 1 (1)
00:00:00.812406   MTRR - Memory Type Range
Registers  = 1 (1)
00:00:00.812406   PGE - PTE Global
Bit    = 1 (1)
00:00:00.812407   MCA - Machine Check
Architecture    = 1 (1)
00:00:00.812407   CMOV - Conditional Move
instructions    = 1 (1)
00:00:00.812408   PAT - Page Attribute
Table  = 1 (1)
00:00:00.812408   PSE-36 - 36-bit Page Size
Extension = 1 (1)
00:00:00.812409   NX -
No-Execute/Execute-Disable = 1 (1)
00:00:00.812409   AXMMX - AMD Extensions to MMX
instructions  = 1 (1)
00:00:00.812410   MMX - Intel MMX
Technology  = 1 (1)
00:00:00.812410   FXSR - FXSAVE and FXRSTOR
Instructions  = 1 (1)
00:00:00.812411   FFXSR - AMD fast FXSAVE and FXRSTOR
instructions    = 1 (1)
00:00:00.812411   Page1GB - 1 GB large
page   = 0 (1)
00:00:00.812412   RDTSCP - RDTSCP
instruction = 1 (1)
00:00:00.812413   LM - AMD64 Long
Mode    = 1 (1)
00:00:00.812413   3DNOWEXT - AMD Extensions to
3DNow  = 0 (0)
00:00:00.812414   3DNOW - AMD
3DNow   = 0 (0)
00:00:00.812415   LahfSahf - LAHF/SAHF support in 64-bit
mode = 1 (1)
00:00:00.812415   CmpLegacy - Core multi-processing legacy
mode   = 1 (1)
00:00:00.812416 *SVM - AMD Secure Virtual Machine extensions* = 1 (1)
00:00:00.812416   EXTAPIC - AMD Extended APIC
registers   = 0 (1)
00:00:00.812417   CR8L - AMD LOCK MOV CR0 means MOV
CR8   = 1 (1)
00:00:00.812417   ABM - AMD Advanced Bit
Manipulation = 1 (1)
00:00:00.812418   SSE4A - SSE4A
instructions  = 1 (1)
00:00:00.812418   MISALIGNSSE - AMD Misaligned SSE
mode   = 1 (1)
00:00:00.812419   3DNOWPRF - AMD PREFETCH and PREFETCHW
instructions  = 1 (1)
00:00:00.812419   OSVW - AMD OS Visible
Workaround    = 0 (1)
0

Re: [OpenIndiana-discuss] Why networking not work?

2021-04-27 Thread L. F. Elia via openindiana-discuss
When I run a VBox NAT VM I want to ssh into -- the only reliable config I have 
found is to avoid 127.0.0.1 and instead use the actual IP of the box (such as 
10.1.100.221 port  or such). Not sure why this is, but that is what I have 
found to work.


lfe...@yahoo.com, Portsmouth VA, 23701
Solaris/LINUX/Windows administration CISSP/Security consulting 

On Thursday, April 8, 2021, 06:57:48 AM EDT, Jason Long via 
openindiana-discuss  wrote:  
 
 Hello,
I installed OpenIndiana as a VM in the VirtualBox and use "NAT" and "Port 
Forwarding" in the network setting. When I tried to connect to the VM then it 
showed me "Connection reset by peer":


  
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] VirtualBox 6.1.18 nested vms

2021-04-27 Thread L. F. Elia via openindiana-discuss
From what I recall, nested virtualization might require BIOS changes (at least 
on DELL). Good luck!

lfe...@yahoo.com, Portsmouth VA, 23701
Solaris/LINUX/Windows administration CISSP/Security consulting 

On Thursday, April 1, 2021, 07:16:20 AM EDT, russell 
 wrote:  
 
 Hi

For what I have read VirtualBox 6.1 introduced the capability to have 
nested VMs.

I have created a VM to run VMware 6.7.0u3, however when I attempt to 
start any VM inside ESX 6.7.0u3 I get the following message

Failed to power on virtual machine Lethe. This host does not support 
"AMD RVI" hardware assisted MMU virtualization. Click here for more 
details. 

 
-

Looking at the log for the VBox VM

00:00:00.812397 Ext Name:    AuthenticAMD
00:00:00.812398 Ext Supports: 0x8000-0x801e
00:00:00.812398 Family:  15      Extended: 10 
     Effective: 25
00:00:00.812398 Model:   1      Extended: 2     
Effective: 33
00:00:00.812399 Stepping:    0
00:00:00.812399 Brand ID:    0x000
00:00:00.812399 Ext Features
00:00:00.812399   Mnemonic - 
Description  = guest (host)
00:00:00.812400   FPU - x87 FPU on 
Chip   = 1 (1)
00:00:00.812400   VME - *Virtual 8086 Mode Enhancements* = 1 (1)
00:00:00.812401   DE - Debugging 
extensions   = 1 (1)
00:00:00.812401   PSE - Page Size 
Extension   = 1 (1)
00:00:00.812402   TSC - Time Stamp 
Counter    = 1 (1)
00:00:00.812403   MSR - K86 Model Specific 
Registers  = 1 (1)
00:00:00.812403   PAE - Physical Address 
Extension    = 1 (1)
00:00:00.812404   MCE - Machine Check 
Exception   = 0 (1)
00:00:00.812404   CX8 - CMPXCHG8B 
instruction = 1 (1)
00:00:00.812405   APIC - APIC 
On-Chip = 1 (1)
00:00:00.812405   SEP - 
SYSCALL/SYSRET    = 1 (1)
00:00:00.812406   MTRR - Memory Type Range 
Registers  = 1 (1)
00:00:00.812406   PGE - PTE Global 
Bit    = 1 (1)
00:00:00.812407   MCA - Machine Check 
Architecture    = 1 (1)
00:00:00.812407   CMOV - Conditional Move 
instructions    = 1 (1)
00:00:00.812408   PAT - Page Attribute 
Table  = 1 (1)
00:00:00.812408   PSE-36 - 36-bit Page Size 
Extension = 1 (1)
00:00:00.812409   NX - 
No-Execute/Execute-Disable = 1 (1)
00:00:00.812409   AXMMX - AMD Extensions to MMX 
instructions  = 1 (1)
00:00:00.812410   MMX - Intel MMX 
Technology  = 1 (1)
00:00:00.812410   FXSR - FXSAVE and FXRSTOR 
Instructions  = 1 (1)
00:00:00.812411   FFXSR - AMD fast FXSAVE and FXRSTOR 
instructions    = 1 (1)
00:00:00.812411   Page1GB - 1 GB large 
page   = 0 (1)
00:00:00.812412   RDTSCP - RDTSCP 
instruction = 1 (1)
00:00:00.812413   LM - AMD64 Long 
Mode    = 1 (1)
00:00:00.812413   3DNOWEXT - AMD Extensions to 
3DNow  = 0 (0)
00:00:00.812414   3DNOW - AMD 
3DNow   = 0 (0)
00:00:00.812415   LahfSahf - LAHF/SAHF support in 64-bit 
mode = 1 (1)
00:00:00.812415   CmpLegacy - Core multi-processing legacy 
mode   = 1 (1)
00:00:00.812416 *SVM - AMD Secure Virtual Machine extensions* = 1 (1)
00:00:00.812416   EXTAPIC - AMD Extended APIC 
registers   = 0 (1)
00:00:00.812417   CR8L - AMD LOCK MOV CR0 means MOV 
CR8   = 1 (1)
00:00:00.812417   ABM - AMD Advanced Bit 
Manipulation = 1 (1)
00:00:00.812418   SSE4A - SSE4A 
instructions  = 1 (1)
00:00:00.812418   MISALIGNSSE - AMD Misaligned SSE 
mode   = 1 (1)
00:00:00.812419   3DNOWPRF - AMD PREFETCH and PREFETCHW 
instructions  = 1 (1)
00:00:00.812419   OSVW - AMD OS Visible 
Workaround    = 0 (1)
00:00:00.812420   IBS - Instruct Based 
Sampling   = 0 (1)
00:00:00.812420   XOP - Extended Operation 
support    = 0 (0)
00:00:00.812421   SKINIT - SKINIT, STGI, and DEV 
support  = 0 (1)
00:00:00.812421   WDT - AMD Watchdog Timer 
support    = 0 (1)
00:00:00.812422   LWP - Lightweight Profiling 
support = 0 (0)
00:00:00.812422   FMA4 - Four operand FMA instruction 
support = 0 (0)
00:00:00.812423   17 - 
Reserved   = 0 (1)
00:00:00.812423   NodeId - NodeId in MSR 
C001_100C  

Re: [OpenIndiana-discuss] VBox on top of Hipster and twm?

2021-04-27 Thread Reginald Beardsley via openindiana-discuss
 

Thank you! That's great news. The reason I ran dtwm and twm side by side was 
Netscape wouldn't run properly on twm. Too many hooks into Motif.

I'd like to shift all my Internet access to a VM with the base system running 
OI on RAIDZ2.

Reg On Tuesday, April 27, 2021, 12:50:16 AM CDT, Stephan Althaus 
 wrote:  
 
 On 04/27/21 12:19 AM, Reginald Beardsley via openindiana-discuss wrote:
> I'd like to run Hipster in a VBox VM for web access with twm as the window 
> manager for the host.
>
> Is this likely to be possible, i.e. how much window manager stuff does VBox 
> require?  If not I can revert to using 2 window managers,  but I'd rather not 
> if I can avoid the added complexity and limitations.  You can't move windows 
> between screens if you are running 2 window managers.
>
> Reg
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss

Hi!

The window manager should have no effect on the X-application itself. i 
just tested VBox with twm by switching the window manager whilst working 
in the Mate-Desktop-Environment

pkill marco && twm

It works.

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
  
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] Graphics card CLI enquiry

2021-04-27 Thread Michelle
It's just text only. 

The N54L only has a VGA connector and I need a DVI for connection to my
KVM. 

The KVM won't take analogue over DVI so I need a half height card to do
the job.

Michelle


On Tue, 2021-04-27 at 08:20 +0200, Stephan Althaus wrote:
> On 04/26/21 03:21 PM, Michelle wrote:
> > Many thanks...
> > 
> > prtdiag -v told me
> > 
> >  Upgradeable Slots 
> > 
> > ID  StatusType Description
> > --- -  
> > 1   in usePCI Express  PCIE1-J5, Advanced Micro Devices,
> > Inc.
> > [AMD/ATI] RV370 [Radeon X600/X600 SE] (vgatext)
> > 2   available PCI Express  PCIE2-J6
> > 
> > 
> > On Mon, 2021-04-26 at 14:39 +0200, Stephan Althaus wrote:
> > > On 04/26/21 02:28 PM, Michelle wrote:
> > > > As QNAP are enforcing their malware removal tool out, which is
> > > > then
> > > > deleting files but has no log of which files it's deleted (and
> > > > you
> > > > can't turn the malware removal tool off... it just re-installs
> > > > itself
> > > > and keeps running)
> > > > 
> > > > ...I'm having to press my backup N54L into use and install OI
> > > > on
> > > > it.
> > > > 
> > > > The problem is, I need to query my currently running N54L with
> > > > OI
> > > > to
> > > > find out what graphics card is in it, so I can order a second
> > > > one.
> > > > 
> > > > The usual linux command isn't there so I was wondering what CLI
> > > > command
> > > > I run to find out what's in there please, as it isn't exactly a
> > > > command
> > > > I use every day :-)
> > > > 
> > > > 
> > > > ___
> > > > openindiana-discuss mailing list
> > > > openindiana-discuss@openindiana.org
> > > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > > Hello!
> > > 
> > > prtconf -d -D
> > > 
> > > is your friend. if you need a lot of detail, try
> > > 
> > > prtconf -v
> > > 
> > > 
> > > hth
> > > 
> > > Stephan
> > > 
> > > 
> > > ___
> > > openindiana-discuss mailing list
> > > openindiana-discuss@openindiana.org
> > > https://openindiana.org/mailman/listinfo/openindiana-discuss
> > 
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hi!
> 
> OI works best with NVidia quadro cards, support for amd is very
> limited 
> from what i know.
> 
> Stephan
> 
> 
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss


___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss


Re: [OpenIndiana-discuss] USB Access issues

2021-04-27 Thread russell

Good Morning John

The output of format -e for the USB Flash drive

   9. c7t0d0 
/pci@0,0/pci1022,1483@1,2/pci1b21,1142@0/hub@6/storage@3/disk@0,0

Running parted  /dev/dsk/c7t0d0p0

GNU Parted 1.8.8
Using /dev/dsk/c7t0d0p0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
Model: Generic Ide (ide)
Disk /dev/dsk/c7t0d0p0: 2005MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End Size    Type File system  Flags
 1  1049kB  2005MB  2004MB  primary  fat32    lba

# iostat -En reports

c7t0d0   Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: USB  Product: Flash Disk   Revision: 1100 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0

So the drive is seen but it is not mounted automatically.
I make a temporary directory and then manually mount it then it does 
become accessible


# mkdir /tmp/russ
# mount -f pcfs /dev/dsk/c7t0d0p1 /tmp/russ

Below is a list of all the active services, rvolmgr is running.

root@tesla:/home/russell# svcs -a | grep online
online  8:41:25 svc:/system/svc/restarter:default
online  8:41:25 svc:/system/early-manifest-import:default
online  8:41:25 svc:/network/datalink-management:default
online  8:41:25 svc:/network/netcfg:default
online  8:41:25 svc:/network/ip-interface-management:default
online  8:41:26 svc:/system/filesystem/root:default
online  8:41:26 svc:/system/cryptosvc:default
online  8:41:26 svc:/system/scheduler:default
online  8:41:26 svc:/system/auditset:default
online  8:41:26 svc:/network/loopback:default
online  8:41:26 svc:/system/boot-archive:default
online  8:41:26 svc:/system/filesystem/usr:default
online  8:41:26 svc:/system/pfexec:default
online  8:41:26 svc:/system/device/local:default
online  8:41:26 svc:/network/ipsec/ipsecalgs:default
online  8:41:26 svc:/system/keymap:default
online  8:41:26 svc:/system/filesystem/minimal:default
online  8:41:26 
svc:/application/desktop-cache/gio-module-cache:default

online  8:41:26 svc:/system/ca-certificates:default
online  8:41:26 svc:/system/zones-monitoring:default
online  8:41:26 svc:/system/hostid:default
online  8:41:26 svc:/system/dbus:default
online  8:41:26 svc:/system/rbac:default
online  8:41:26 svc:/system/logadm-upgrade:default
online  8:41:26 svc:/system/resource-mgmt:default
online  8:41:26 svc:/system/sysevent:default
online  8:41:26 svc:/system/rmtmpfiles:default
online  8:41:26 svc:/network/ipsec/policy:default
online  8:41:26 svc:/system/pkgserv:default
online  8:41:27 svc:/application/font/fc-cache:default
online  8:41:27 svc:/application/opengl/ogl-select:default
online  8:41:27 svc:/system/upower:default
online  8:41:27 svc:/network/npiv_config:default
online  8:41:27 svc:/system/name-service-cache:default
online  8:41:27 svc:/system/device/fc-fabric:default
online  8:41:27 svc:/milestone/devices:default
online  8:41:27 svc:/system/manifest-import:default
online  8:41:27 svc:/system/coreadm:default
online  8:41:27 svc:/application/print/service-selector:default
online  8:41:27 svc:/system/power:default
online  8:41:27 svc:/system/device/audio:default
online  8:41:28 svc:/network/physical:default
online  8:41:28 svc:/milestone/network:default
online  8:41:28 svc:/system/identity:domain
online  8:41:28 svc:/network/iptun:default
online  8:41:28 svc:/system/fcoe_initiator:default
online  8:41:28 svc:/network/initial:default
online  8:41:28 svc:/network/service:default
online  8:41:28 svc:/network/netmask:default
online  8:41:28 svc:/network/dns/client:default
online  8:41:28 svc:/milestone/name-services:default
online  8:41:28 svc:/network/iscsi/initiator:default
online  8:41:28 svc:/application/cups/scheduler:default
online  8:41:29 svc:/network/ntp:default
online  8:41:29 svc:/network/routing-setup:default
online  8:41:29 svc:/system/identity:node
online  8:41:29 svc:/network/rpc/bind:default
online  8:41:29 svc:/milestone/single-user:default
online  8:41:29 svc:/system/picl:default
online  8:41:29 svc:/network/routing/route:default
online  8:41:34 svc:/system/hal:default
online  8:41:35 svc:/system/filesystem/local:default
online  8:41:35 svc:/application/desktop-cache/dconf-update:default
online  8:41:35 svc:/system/sysding:system
online  8:41:35 svc:/application/x11/x11-init:default
online  8:41:35 svc:/system/cron:default
online  8:41:35 svc:/system/filesystem/autofs:default
online  8:41:35 svc:/system/xvm/vnc-

[OpenIndiana-discuss] wiki is down 503

2021-04-27 Thread Stephan Althaus

Hello admins!

The OI wiki site https://wiki.openindiana.org/ is down.
503 Service unavailable

Stephan



___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss