Re: [OpenIndiana-discuss] pkg update removes installed services ?!?

2023-06-08 Thread Maurilio Longo via openindiana-discuss 
Yes, it doesn't do anything because 2022.0.0.15384 is the build that it is 
installed right now :)

This blog-post clarifies it:

https://alp-notes.blogspot.com/2015/10/userland-incorporation-in-openindiana.html

Anyway, as can be seen from the list of incorporations, there is a huge hole 
between build 15384 and the next one at 19514 spanning more than a year.

That said, back to plan B for my problem.

Cheers.

Maurilio.



> Il 09/06/2023 07:50 CEST Maurilio Longo via openindiana-discuss 
>  ha scritto:
> 
>  
> Hi Tim,
> 
> the oldest userland incorporation listed right now are 
> 
> consolidation/userland/userland-incorporation 0.5.11-2023.0.0.19516  
> ---
> consolidation/userland/userland-incorporation 0.5.11-2023.0.0.19514  
> ---
> consolidation/userland/userland-incorporation 0.5.11-2022.0.0.15384  
> i--
> 
> but a 
> 
>pkg update -nv userland-incorporation@0.5.11-2022.0.0.15384
> 
> does not update any packages, and gives a message which is, more or less 
> since it is in my national language, "there are no updates for this image".
> 
> Regards.
> 
> Maurilio.
> 
> > Il 07/06/2023 10:30 CEST Tim Mooney via openindiana-discuss 
> >  ha scritto:
> > 
> > 
> > pkg list -af userland-incorporation
> > 
> > to get every available version of that package.  'pkg update' supports
> > an @ specifier, but I don't know (actually, I doubt) if it's
> > as simple as something like
> > 
> > pkg update -v userland-incorporation@0.5.11-2023.0.0.17799
> >
> 
> ___
> 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] pkg update removes installed services ?!?

2023-06-08 Thread Maurilio Longo via openindiana-discuss 
Hi Tim,

the oldest userland incorporation listed right now are 

consolidation/userland/userland-incorporation 0.5.11-2023.0.0.19516  ---
consolidation/userland/userland-incorporation 0.5.11-2023.0.0.19514  ---
consolidation/userland/userland-incorporation 0.5.11-2022.0.0.15384  i--

but a 

   pkg update -nv userland-incorporation@0.5.11-2022.0.0.15384

does not update any packages, and gives a message which is, more or less since 
it is in my national language, "there are no updates for this image".

Regards.

Maurilio.

> Il 07/06/2023 10:30 CEST Tim Mooney via openindiana-discuss 
>  ha scritto:
> 
> 
>   pkg list -af userland-incorporation
> 
> to get every available version of that package.  'pkg update' supports
> an @ specifier, but I don't know (actually, I doubt) if it's
> as simple as something like
> 
>   pkg update -v userland-incorporation@0.5.11-2023.0.0.17799
>

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

Re: [OpenIndiana-discuss] pkg update removes installed services ?!?

2023-06-08 Thread Maurilio Longo via openindiana-discuss 
Hi Tim,

just FYI freezing postgres-10 packages prevents pkg update from doing any 
useful work, it does not update most of the system, just less than 20 packages 
get updated.

So, I'll do a pg_dumpall inside the old BE and a pg_restore once inside the new 
one and with an updated postgres.

Best regards.

Maurilio.

> Il 07/06/2023 08:47 CEST Tim Mooney via openindiana-discuss 
>  ha scritto:
> You can 'freeze' (see pkg(1)) a package at a specific version, if that
> specific version is critical to your install and you're worried an update
> might take it out.  Note that doing that may prevent updates without other
> steps being taken.
>

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

Re: [OpenIndiana-discuss] pkg update removes installed services ?!?

2023-06-07 Thread Maurilio Longo via openindiana-discuss 
Hi Tim,

I always create a new BE while updating and I'm back to my previous working 
configuration; I was just baffled by the removal of an active and working 
service.

And I know that postgres 10 is EOL, this is why I was updating the OS in 
preparation to the migration of my data to postgres 14.

BTW, I cannot even install it right now on a old Openindiana installation 
because latest postgres-10 depends on newer incorporations.

That said, I'll look up the freezing of the postgres package and see what 
happens when I try an update.

Thanks for pointing me to the freeze feature of pkg.

Best regards.

Maurilio Longo.

> Il 07/06/2023 08:47 CEST Tim Mooney via openindiana-discuss 
>  ha scritto:
> 
>  
> In regard to: [OpenIndiana-discuss] pkg update removes installed services...:
> 
> > How am I supposed to proceed to update the OS to the latest available,
> > while at the same time maintaining all the working services intact ?
> 
> Postgresql 10 was end-of-life November 10, 2022.
> 
> Newer versions of postgres have been part of OI for a while.  Upgrading
> your postgres-10 install to something like postgres-14 while both were
> provided by the OS would probably have been the easiest path.
> 
> You can see what an update is going to do without doing it using the '-nv'
> flag with update.  I usually look through that output before actually
> applying an update.
> 
> You can 'freeze' (see pkg(1)) a package at a specific version, if that
> specific version is critical to your install and you're worried an update
> might take it out.  Note that doing that may prevent updates without other
> steps being taken.
> 
> You may want to go back to your previous boot environment (see beadm(8))
> and plan an upgrade to a newer postgresql within that boot environment.
> Then, once you've converted to a newer postgresql series, you should be
> able to safely update.
> 
> Rolling releases and a very small contributor pool means that there's
> no good way to do long-term support for outdated/EOL software, especially
> when there are newer versions that are still receiving updates.
> 
> Tim
> -- 
> Tim Mooney tim.moo...@ndsu.edu
> Enterprise Computing & Infrastructure /
> Division of Information Technology/701-231-1076 (Voice)
> North Dakota State University, Fargo, ND 58105-5164
> 
> ___
> 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

[OpenIndiana-discuss] pkg update removes installed services ?!?

2023-06-06 Thread Maurilio Longo via openindiana-discuss 
Hi all,

I've just tried  a pkg update on an OpenIndiana Hipster 2021.10 installation 
which has a postgres 10 instance installed and working.

To my disbelief, upon reboot, I realized that postgres 10 had been removed, and 
as such the system was unable to perform its intended role!

How am I supposed to proceed to update the OS to the latest available, while at 
the same time maintaining all the working services intact ?

Regards.

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

Re: [OpenIndiana-discuss] INFO: pkg update manifest hash error in package readline

2023-06-01 Thread Maurilio Longo via openindiana-discuss 
Hi Stephan,

same error here on a 

 OpenIndiana Hipster 2021.10 (powered by illumos)
 OpenIndiana Project, part of The Illumos Foundation (C) 2010-2021
  Use is subject to license terms.
   Assembled 30 October 2021

but no problems on a more recent system (virtual machine on 2022.10) which I've 
just updated to 2023.05.

Regards.

Maurilio Longo.



> Il 01/06/2023 14:08 CEST Stephan Althaus  
> ha scritto:
> 
>  
> On 6/1/23 08:28, Stephan Althaus wrote:
> > On 6/1/23 08:14, Marcel Telka wrote:
> >> On Thu, Jun 01, 2023 at 06:55:50AM +0200, Stephan Althaus wrote:
> >>> # pkgrecv -s https://pkg.openindiana.org/hipster/ -a -d ./pkgtest
> >>> pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z
> >>>  
> >>>
> >>> Retrieving packages for publisher openindiana.org ...
> >>> Retrieving and evaluating 1 package(s)...
> >>> pkgrecv:
> >>> pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z
> >>>  
> >>>
> >>>    Invalid content: manifest hash failure: fmri:
> >>> pkg://openindiana.org/library/readline@6.3,5.11-2022.1.0.3:20221224T140642Z
> >>>  
> >>>
> >>> expected: e6571024d64e235a1ef19fd8557d028837118fec computed:
> >>> 658d78a4022ed30bef9c2f9b6b15edabeb81ef1f. (happened 4 times)
> >>>
> >>> I have tested the download on a different machine, same error.
> >>>
> >>> Maybe someone else can have a look at this?
> >> Confirmed.  Same error here.
> >>
> > Hello!
> >
> > Thanks!
> >
> > The package readline is used by many packages and stuck in versions 
> > 5.2 and 6.3 - very special..
> >
> > Should i create a PR with a new component revision to trigger a 
> > rebuild or what is "the right way" to achieve this?
> >
> > Regards,
> > Stephan
> >
> >
> >
> > ___
> > openindiana-discuss mailing list
> > openindiana-discuss@openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> Hello!
> 
> Maybe it is a problem with pkg itself:
> 
> pkg search -r libm.so.2
> 
> does not return any results on the old (nov 2022) system.. (?)
> 
> Regards,
> 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] services dependency cycle

2022-05-05 Thread Maurilio Longo via openindiana-discuss 
Hi Stephan,

I had a similar problem in the past due to the meta-init service not being 
completely removed by a previous update.

Maybe it is the same meta-something Espen remembers.

Regards.
Maurilio.

> Il 05/05/2022 15:07 Stephan Althaus  ha 
> scritto:
> 
>  
> On 5/5/22 14:51, Espen Martinsen wrote:
> > Hi,
> >    I had this on an old laptop for some weeks ago, and it was because 
> > of a "leftver?) metadb-service, I just removed the service completely, 
> > and then everything was fine.
> >    Noen of the binaries from old "disksuite" was left anyway, that's 
> > why it would not start.
> >
> > -espen
> >
> > On 5/5/22 14:40, Stephan Althaus wrote:
> >> Hello!
> >>
> >> After pkg update on one of my systems, i get a maintenance mode login 
> >> due to a dependency loop, many of the services are not starting.
> >>
> >> I bootet a previous BE and did a
> >>
> >> beadm mount openindiana-2022:05:05  /a
> >>
> >> In /var/svc/log there is an entry only in
> >>
> >> system-filesystem-usr:default.log:4706:[ May  5 13:40:12 Stopping for 
> >> maintenance due to dependency_cycle. ]
> >> system-filesystem-usr:default.log:4707:[ May  5 13:40:12 Stopping for 
> >> maintenance due to dependency_cycle. ]
> >> system-filesystem-usr:default.log:4708:[ May  5 14:11:35 Stopping for 
> >> maintenance due to dependency_cycle. ]
> >> system-filesystem-usr:default.log:4709:[ May  5 14:11:35 Stopping for 
> >> maintenance due to dependency_cycle. ]
> >>
> >> i don't find a log where the other dependant services are mentioned.
> >>
> >>
> >> Does anyone knows of changes in the service dependencies that may be 
> >> related?
> >>
> >>
> >> Any help is appreciated :-)
> >>
> >> Stephan
> >>
> >>
> >>
> >> ___
> >> openindiana-discuss mailing list
> >> openindiana-discuss@openindiana.org
> >> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >
> >
> @Espen: Thanks for your input.. I dont have the service metadb
> 
> svc:/system/filesystem/usr:default (read/write root file systems mounts)
>   State: maintenance since  5 May 2022 at 14:58:23 CEST
> Reason: Completes a dependency cycle.
>     See: http://illumos.org/msg/SMF-8000-HP
> Impact: 89 dependent services are not running:
>      svc:/network/ipsec/ipsecalgs:default
>      svc:/system/device/local:default
>      svc:/system/filesystem/minimal:default
>      svc:/system/manifest-import:default
>      svc:/application/print/service-selector:default
>      svc:/network/location:default
>      svc:/network/dns/client:default
>      svc:/network/ipfilter:default
>      svc:/network/rpc/bind:default
>      svc:/system/sysding:system
>      svc:/milestone/sysconfig:default
>      svc:/milestone/multi-user:default
>      svc:/system/intrd:default
>      svc:/milestone/multi-user-server:default
>      svc:/application/texinfo-update:default
>      svc:/system/zones:default
>      svc:/system/system-log:default
>      svc:/network/smtp:sendmail
>      svc:/network/sendmail-client:default
>      svc:/system/utmp:default
>      svc:/system/console-login:default
>      svc:/network/ssh:default
>      svc:/network/inetd:default
>      svc:/system/sac:default
>      svc:/system/idmap:default
>      svc:/network/smb/client:default
>      svc:/network/smb/server:default
>      svc:/network/shares/group:default
>      svc:/network/shares/group:smb
>      svc:/network/shares/group:zfs
>      svc:/system/filesystem/autofs:default
>      svc:/system/dumpadm:default
>      svc:/system/fmd:default
>      svc:/application/pkg/system-repository:default
>      svc:/application/pkg/zones-proxyd:default
>      svc:/system/identity:domain
>      svc:/system/name-service-cache:default
>      svc:/milestone/single-user:default
>      svc:/system/filesystem/local:default
>      svc:/application/desktop-cache/input-method-cache:default
>      svc:/application/desktop-cache/dconf-update:default
>      svc:/system/smartd:default
>      svc:/system/cron:default
>      svc:/application/desktop-cache/mime-types-cache:default
>      svc:/system/xvm/vnc-config:default
>      svc:/system/update-man-index:default
>      svc:/system/hotplug:default
> svc:/application/desktop-cache/docbook-catalog-update:default
>      svc:/application/desktop-cache/icon-cache:default
> svc:/application/desktop-cache/pixbuf-loaders-installer:default
>      svc:/application/virtualbox/zoneaccess:default
>      svc:/system/boot-archive-update:default
>      svc:/application/desktop-cache/gconf-cache:default
>      svc:/system/filesystem/rmvolmgr:default
>      svc:/application/x11/x11-init:default
>      svc:/application/desktop-cache/desktop-mime-cache:default
>      svc:/system/consolekit:default
>      svc:/application/virtualbox/run-once:default
>

Re: [OpenIndiana-discuss] Possible to update from 2021.0430 to 2021.1130 with pkg tool?

2022-05-04 Thread Maurilio Longo via openindiana-discuss 
Toomas,

I'm not aware of any method to update to an exact point in time, which would be 
a usefull thing when you have really old systems to update.

You update your system to the current packages which are newer than 2021.1130

Being that Hipster is a rolling relase type of OS, you can end up with 
different systems even if you pkg update them in the same day but in different 
moments, as far as I know.

Regards.

Maurilio

> Il 04/05/2022 00:01 Toomas Soome via openindiana-discuss 
>  ha scritto:
> 
>  
> > On 9. Jan 2022, at 06:29, hput via openindiana-discuss 
> >  wrote:
> > 
> > Can one update from one release to another with just the pkg tool.
> > 
> > When I run `pkg update' on oi/hipster installed from 2021.0430 does
> > that install the pkgs that are current in 2021.1130?
> > 
> 
> Yes, thats the purpose of pkg.
> 
> rgds,
> toomas
> ___
> 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] can't install a new zone

2022-04-11 Thread Maurilio Longo via openindiana-discuss 
Hi Andreas,

thanks a lot!
After a pkg refresh --full I was able to install my new zone without further 
issues.

Best regards.
Maurilio.


> Il 10/04/2022 14:29 Andreas Wacknitz  ha scritto:
> 
>  
> Am 10.04.22 um 11:46 schrieb Andreas Wacknitz:
> > Am 10.04.22 um 11:23 schrieb Stephan Althaus:
> >> On 4/10/22 11:12, Stephan Althaus wrote:
> >>> On 4/10/22 10:52, Andreas Wacknitz wrote:
> >>>> Am 10.04.22 um 10:47 schrieb Stephan Althaus:
> >>>>> On 4/10/22 09:56, Andreas Wacknitz wrote:
> >>>>>> Am 09.04.22 um 18:38 schrieb Maurilio Longo via openindiana-discuss:
> >>>>>>> No problem Andreas,
> >>>>>>>
> >>>>>>> it is at 15370
> >>>>>>>
> >>>>>>> $ pkg info userland-incorporation
> >>>>>>>   Name: consolidation/userland/userland-incorporation
> >>>>>>>    Summary: userland consolidation incorporation
> >>>>>>> (consolidation/userland/userland-incorporation)
> >>>>>>>    Description: This incorporation constrains packages from the
> >>>>>>> userland
> >>>>>>>     consolidation
> >>>>>>>   Category: Meta Packages/Incorporations
> >>>>>>>  State: Installed
> >>>>>>>  Publisher: openindiana.org
> >>>>>>>    Version: 0.5.11
> >>>>>>>     Branch: 2022.0.0.15370
> >>>>>>>     Packaging Date: Sat Apr  9 09:53:00 2022
> >>>>>>> Last Install Time: Sun Oct 31 19:39:21 2021
> >>>>>>>   Last Update Time: Sat Apr  9 12:01:18 2022
> >>>>>>>   Size: 0.00 B
> >>>>>>>   FMRI:
> >>>>>>> pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Regards.
> >>>>>>>
> >>>>>>> Maurilio
> >>>>>>>
> >>>>>> I have investigated further and found out that we have some actual
> >>>>>> problems with old packages that have been replaced in the past.
> >>>>>> The problems became imminent after illumos-gate has merged #14583
> >>>>>> developer/opensolaris/osnet requirements cleanup and after
> >>>>>> shrinking the
> >>>>>> repository.
> >>>>>> So far I have identified three:
> >>>>>>     file/slocate
> >>>>>>     runtime/java
> >>>>>>     service/network/ftp
> >>>>>> and replaced the fmri's with their replacements mlocate, openjdk8
> >>>>>> and
> >>>>>> proftpd.
> >>>>>> There might be more outdated fmri's left that need to be fixed,
> >>>>>> though.
> >>>>>>
> >>>>>>
> >>>>>> ___
> >>>>>> openindiana-discuss mailing list
> >>>>>> openindiana-discuss@openindiana.org
> >>>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>>>>
> >>>>> Hi!
> >>>>>
> >>>>>
> >>>>> There are some packages mentioned that are not in "2022":
> >>>> This should not be a problem. They just haven't been build this year
> >>>> yet. But you need to make sure that they are still in the repository,
> >>>> though.
> >>>> Eg. pkg info -r compress/bzip2@1.0.8-2020.0.1.0
> >>>> and are in the userland-incorporation meta package.
> >>>>
> >>>>
> >>>>>
> >>>>> # zoneadm -z bz-template install 2>&1 |grep 202|grep -v 2022
> >>>>>
> >>>>>  Reject:
> >>>>> pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433Z
> >>>>>
> >>>>>  Reject:
> >>>>> pkg://openindiana.org/compress/gzip@1.11-2020.0.1.0:20210903T182240Z
> >>>>>  Reject:
> >>>>> pkg://openindiana.org/compress/unzip@6.0-2020.0.1.5:20200330T1135

Re: [OpenIndiana-discuss] can't install a new zone

2022-04-09 Thread Maurilio Longo via openindiana-discuss 
No problem Andreas,

it is at 15370

$ pkg info userland-incorporation
 Name: consolidation/userland/userland-incorporation
  Summary: userland consolidation incorporation
   (consolidation/userland/userland-incorporation)
  Description: This incorporation constrains packages from the userland
   consolidation
 Category: Meta Packages/Incorporations
State: Installed
Publisher: openindiana.org
  Version: 0.5.11
   Branch: 2022.0.0.15370
   Packaging Date: Sat Apr  9 09:53:00 2022
Last Install Time: Sun Oct 31 19:39:21 2021
 Last Update Time: Sat Apr  9 12:01:18 2022
 Size: 0.00 B
 FMRI: 
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z

Regards.

Maurilio


> Il 09/04/2022 18:34 Andreas Wacknitz  ha scritto:
> 
>  
> Sorry, I made a mistake. Please use
> pkg info userland-incorporation
> (without "-r" which means remote) in order to get information about your
> local userland-incorporation.
>

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

Re: [OpenIndiana-discuss] can't install a new zone

2022-04-09 Thread Maurilio Longo via openindiana-discuss 
Hi Andreas,

mine is reported as newer than 15370.

$ pkg info -r userland-incorporation
  Name: consolidation/userland/userland-incorporation
   Summary: userland consolidation incorporation
(consolidation/userland/userland-incorporation)
   Description: This incorporation constrains packages from the userland
consolidation
  Category: Meta Packages/Incorporations
 State: Not installed
 Publisher: openindiana.org
   Version: 0.5.11
Branch: 2022.0.0.15372
Packaging Date: Sat Apr  9 13:24:12 2022
  Size: 0.00 B
  FMRI: 
pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15372:20220409T132412Z

Regards

Maurilio


> Il 09/04/2022 18:16 Andreas Wacknitz  ha scritto:
> 
>  
> Something prohibits to update to the latest bits. What does "pkg info
> userland-incorporation" output?
> Here it is
> ─➤  pkg info -r userland-incorporation
>    Name: consolidation/userland/userland-incorporation
>     Summary: userland consolidation incorporation
>      (consolidation/userland/userland-incorporation)
>     Description: This incorporation constrains packages from the userland
>      consolidation
>    Category: Meta Packages/Incorporations
>   State: Not installed
>   Publisher: openindiana.org
>     Version: 0.5.11
>      Branch: 2022.0.0.15370
> Packaging Date: Sat Apr  9 09:53:00 2022
>    Size: 0.00 B
>    FMRI:
> pkg://openindiana.org/consolidation/userland/userland-incorporation@0.5.11-2022.0.0.15370:20220409T095300Z
> 
> Make sure your userland-incorporation is at this version or newer. If it
> is older try to install it explicitly and see what prevents its update:
> pfexec pkg install userland-incorporation@0.5.11-2022.0.0.15370
>

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

[OpenIndiana-discuss] can't install a new zone

2022-04-09 Thread Maurilio Longo via openindiana-discuss 
Hi,

I've just updated an Openindiana 2021.10 system with a
   # pkg refresh --full
   # pkg update

$ uname -a
SunOS st-ar-01 5.11 illumos-041297c2d6 i86pc i386 i86pc illumos

because, after a few years from the last time I did install one, I could not 
install a new zone due to missing dependencies, but the problem stays the same.

$ pfexec zoneadm -z ztc install
A ZFS file system has been created for this zone.
Sanity Check: Looking for 'entire' incorporation.
Image: Preparing at /nas/zones/ztc/root.

Publisher: Using openindiana.org (http://pkg.openindiana.org/hipster/).
Cache: Using /var/pkg/publisher.
Installing: Packages (output follows)
Creating Plan (Running solver): -
pkg install: No matching version of compress/zip can be installed:
Reject: 
pkg://openindiana.org/compress/zip@3.0-2020.0.1.1:20200615T163122ZReason: No 
version matching 'require' dependency compress/bzip2@1.0.8-2020.0.1.0 can be 
installedReject: 
pkg://openindiana.org/compress/bzip2@1.0.8-2020.0.1.0:20200330T113433ZReason: 
No version matching 'require' dependency SUNWcs@0.5.11-2020.0.1.19548 can be 
installed
...

an so on and so forth for tens of different packages ?!?

The zone config is as bare I can get it

$ zonecfg -z ztc info
zonename: ztc
zonepath: /nas/zones/ztc
brand: ipkg
autoboot: false
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid:
fs-allowed:
net:
address not specified
allowed-address not specified
physical: vnztc0
defrouter not specified

Is it still possibile to run zones on current Openindiana or am I doing 
something wrong?

Regards.

Maurilio

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

Re: [OpenIndiana-discuss] how to remove loader and get back to grub

2016-12-05 Thread Maurilio Longo via openindiana-discuss 

Hi Aurélien,

I'm going to put it in production in a couple of days, then I'll try to 
recreate this problem with a virtual machine.


If I'm able to recreate it, I'll open a ticket.

Regards.

Maurilio.

Aurélien Larcher wrote:




How about opening a ticket?
 



--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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

Re: [OpenIndiana-discuss] how to remove loader and get back to grub

2016-12-02 Thread Maurilio Longo via openindiana-discuss 

It's pretty easy.

1) add to /rpool/boot/grub/menu.lst the missing BE(s)
2) # installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c?t?d?s0
3) repeat 2) for the other boot disk (I have a mirrored rpool)
4) add BE_HAS_GRUB=true inside /etc/default/be

Now I can boot from either of my boot disks if I remove one or the other.

This confirms, IMHO, that the bsd loader is not ready, since it can only boot 
from the disk your system was installed to (at least in a case like mine were 
I'm not using a whole disk for the rpool).


Regards.

Maurilio.


Maurilio Longo via openindiana-discuss wrote:

Hi,

are there instructions somewhere on how (given that I hope that it is 
possible) to remove bsd loader from Hipster 2016.10 after it already 
installed itself?




--
 __
|  |  | |__| Maurilio Longo
|_|_|_||


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

[OpenIndiana-discuss] how to remove loader and get back to grub

2016-12-01 Thread Maurilio Longo via openindiana-discuss 

Hi,

are there instructions somewhere on how (given that I hope that it is 
possible) to remove bsd loader from Hipster 2016.10 after it already installed 
itself?


I have a mirrored rpool where the update to 2016.10 has installed loader on 
the first disk even if this is not a whole disk (from release notes I was 
under the wrong impression it would not do this to me :)).


I've made several attempts to upgrade the second disk to loader following 
these instructions


https://www.openindiana.org/2016/09/28/loader-integration/

But I can't boot my system from the second disk, it traps with a

spa_import_rootpool: error 5

when the first disk is not visible anymore.

I'm pretty sure it was working with grub and so I'd like to revert this change 
if it is possible.


Thanks.

Maurilio.

--
 __
|  |  | |__| Maurilio Longo
|_|_|_||


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

Re: [OpenIndiana-discuss] Fwd: USB 3.0 (xHCI) Beta Testing and Review

2016-11-23 Thread Maurilio Longo via openindiana-discuss 

Hi Robert,

for the PCI ID.

I'm attaching here the full dmesg log, so you can have a look at it.

I've also tried a reboot after a touch /reconfigure, but it made no difference.

Regards.

Maurilio.

Robert Mustacchi wrote:


Did you check the /etc/driver_aliases for xhci or for just the PCI ID?
The xhci driver doesn't attach to a specific PCI ID, but the PCI class,
which is in the device's compatible list that you mentioned.

It's a bit surprising that there's no log information, if it is actually
trying to attach and failing.

Robert



--
 __
|  |  | |__| Maurilio Longo
|_|_|_||

Nov 24 08:28:03 st-ar-02 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.11 
Version illumos-edb901a 64-bit
Nov 24 08:28:03 st-ar-02 genunix: [ID 877030 kern.notice] Copyright (c) 1983, 
2010, Oracle and/or its affiliates. All rights reserved.
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: lgpg
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: tsc
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: msr
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: mtrr
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: pge
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: de
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: cmov
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: mmx
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: mca
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: pae
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: cv8
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: pat
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: sep
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: sse
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: sse2
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: htt
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: asysc
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: nx
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: sse3
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: cx16
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: cmp
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: tscp
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: mwait
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: cpuid
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: ssse3
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: sse4_1
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: sse4_2
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: 1gpg
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: clfsh
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: 64
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: aes
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: pclmulqdq
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: xsave
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: avx
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: vmx
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: f16c
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: rdrand
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: x2apic
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: avx2
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: bmi1
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: bmi2
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: fma
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: smep
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: smap
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: adx
Nov 24 08:28:03 st-ar-02 unix: [ID 223955 kern.info] x86_feature: rdseed
Nov 24 08:28:03 st-ar-02 unix: [ID 168242 kern.info] mem = 66935344K 
(0xff568c000)
Nov 24 08:28:03 st-ar-02 acpica: [ID 789330 kern.notice] ACPI: RSDP 0x   0  
 FE320 24 (v2 DELL  )
Nov 24 08:28:03 st-ar-02 acpica: [ID 771794 kern.notice] ACPI: XSDT 0x   
08EFFD188 EC (v1 DELL   PE_SC3     0113)
Nov 24 08:28:03 st-ar-02 acpica: [ID 577225 kern.notice] ACPI: FACP 0x   
08EFC6000 00010C (v5 DELL   PE_SC3    DELL 0001)
Nov 24 08:28:03 st-ar-02 acpica: [ID 173488 kern.notice] ACPI: DSDT 0x   
08EFB2000 00E9C8 (v2 DELL   SKL   INTL 20121114)
Nov 24 08:28:03 st-ar-02 acpica: [ID 468798 kern.notice] ACPI: FACS 0x   
08EF83000 40
Nov 24 08:28:03 st-ar-02 acpica: [ID 509689 kern.notice] ACPI: BOOT 0x   
08EFCC000 28 (v1 INTEL  TIANO0002 MSFT 0113)
Nov 24 08:28:03 st-ar-02 acpica: [ID 41090

Re: [OpenIndiana-discuss] Fwd: USB 3.0 (xHCI) Beta Testing and Review

2016-11-23 Thread Maurilio Longo via openindiana-discuss 

Robert,

I can't find anything inside dmesg related to this intel sunrise point 
grepping its name or pci-id or 'xhci'.


I've also found that driver_aliases does not contain any reference to it


$ cat /etc/driver_aliases | grep 6a7
bge "pci108e,16a7"
bge "pci14e4,16a7"

$ cat /etc/driver_aliases | grep a12f



A prtconf -v contains this

pci1028,6a7 (driver not attached)
Hardware properties:
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.XHC_'
name='assigned-addresses' type=int items=5
value=8300a010..92e0..0001
name='reg' type=int items=10

value=a000.....0300a010....0001
name='compatible' type=string items=7
value='pci8086,a12f.1028.6a7.31' + 
'pci8086,a12f.1028.6a7' + 'pci1028,6a7' + 'pci8086,a12f.31' + 'pci8086,a12f' + 
'pciclass,0c0330' + 'pciclass,0c03'

name='model' type=string items=1
value='Unknown class of pci/pnpbios device'
name='power-consumption' type=int items=2
value=0001.0001
name='fast-back-to-back' type=boolean
name='devsel-speed' type=int items=1
value=0001
name='interrupts' type=int items=1
value=0001
name='max-latency' type=int items=1
value=
name='min-grant' type=int items=1
value=
name='subsystem-vendor-id' type=int items=1
value=1028
name='subsystem-id' type=int items=1
value=06a7
name='unit-address' type=string items=1
value='14'
name='class-code' type=int items=1
value=000c0330
name='revision-id' type=int items=1
value=0031
name='vendor-id' type=int items=1
value=8086
name='device-id' type=int items=1
value=a12f
name='vendor-name' type=string items=1
value='Intel Corporation'
name='device-name' type=string items=1
value='Sunrise Point-H USB 3.0 xHCI Controller'
name='subsystem-name' type=string items=1
value='unknown subsystem'
pci1028,6a7 (driver not attached)
Hardware properties:
name='assigned-addresses' type=int items=5
value=8300a210..92e16000..1000
name='reg' type=int items=10

value=a200.....0300a210....1000
name='compatible' type=string items=7
value='pci8086,a131.1028.6a7.31' + 
'pci8086,a131.1028.6a7' + 'pci1028,6a7' + 'pci8086,a131.31' + 'pci8086,a131' + 
'pciclass,118000' + 'pciclass,1180'

name='model' type=string items=1
value='DSP/DAP controllers'
name='power-consumption' type=int items=2
value=0001.0001
name='devsel-speed' type=int items=1
value=
name='interrupts' type=int items=1
value=0003
name='max-latency' type=int items=1
value=
name='min-grant' type=int items=1
value=
name='subsystem-vendor-id' type=int items=1
value=1028
name='subsystem-id' type=int items=1
value=06a7
name='unit-address' type=string items=1
value='14,2'
name='class-code' type=int items=1
value=00118000
name='revision-id' type=int items=1
value=0031
name='vendor-id' type=int items=1
value=8086
name='device-id' type=int items=1
value=a131
name='vendor-name' type=string items=1
value='Intel Corporation'
name='device-name' type=string items=1
value='Sunrise Point-H Thermal subsystem'
name='subsystem-name' type=string items=1
value='unknown subsystem'
pci1028,6a7 (driver not attached)
Hardware properties:
name='acpi-namespace' type=string items=1
value='\_SB_.PCI0.HECI'
name='assigned-addresses' type=int items=5
value=8300b010..92e17000..1000
name='reg' type=int items=10

value=b000.

Re: [OpenIndiana-discuss] Fwd: USB 3.0 (xHCI) Beta Testing and Review

2016-11-22 Thread Maurilio Longo via openindiana-discuss 

Hi Adam and Robert,

I've just made a test with a Dell PowerEdge T330 where latest hipster image 
does not work; keyboard and mouse are dead when connected to the native ports 
on the unit, and I've got this result to the commands below.


$ uname -a
SunOS st-ar-02 5.11 illumos-edb901a i86pc i386 i86pc Solaris

pfexec mdb -ke '::prtusb'
INDEX   DRIVER  INST  NODEVID.PID PRODUCT
1   uhci0 pci1106,3038.   No Product String
2   uhci1 pci1106,3038.   No Product String


pfexec prtconf -dD | grep -i xhci
pci1028,6a7 (pciex8086,a12f) [Intel Corporation Sunrise Point-H USB 
3.0 xHCI Controller]



I hope this helps.

Regards.

Maurilio.

Adam Števko wrote:



Begin forwarded message:

From: Robert Mustacchi 
Subject: USB 3.0 (xHCI) Beta Testing and Review
Date: November 18, 2016 at 9:13:40 PM GMT+1
To: illumos Developer 
Cc: Toomas Soome , Dan McDonald , Adam Števko 


Hi,

Thanks to everyone who's helped test some alpha builds of xhci, I think
we have something that's getting pretty close to being a useful initial
integration of USB 3 and xhci support.

I'd like to thank Toomas Soome, Dan McDonald, and Adam Števko I have
images for SmartOS, OmniOS, OI hipster, and OI/Loader for ready testing.
While there are a few known issues with the current code, if you see
panics or hangs of any kind, please reach out to me with more
information and if at all possible, a crash dump. Please note, this is
all *beta* software. While I don't expect folks to encounter problems,
you certainly may.

So far, we've tried to test as many of the major classes of devices as
possible. Including audio, storage, serial, Ethernet, keyboard, mouse,
hubs, etc. We've also had a lot of luck so far on the following
chipsets: VMware Fusion controller, Fresco Logic FL1100EX, Intel 8
Series/C220 series chipset, Sunrise Point-H USB 3.0 xHCI Controller, and
Intel Celeron N2000 Series USB xHCI.

If you do test it, and things are working, it'd help me if you could
share the output of the following two commands for my notes:

mdb -ke '::prtusb'
prtconf -dD | grep -i xhci

With that, here are links to builds and images:

Toomas has put together his loader branch with the xhci changes. There
are OI ISO/USB images here:

https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/oi/OI_Loader_xhci_Text_X86.iso
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/oi/OI_Loader_xhci_Text_X86.usb

Dan McDonald has put together OmniOS bloody repo available at:
http://pkg.omniti.com/omnios/USB3/. For more information on how to use
it, please reach out to OmniOS

Adam Števko has put together an OI Hipster repository. It's available at
http://pkg.openindiana.org/hipster-xhci. For more information or
questions on the repo, please reach out to the OI Developer list.


SmartOS builds:

https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.tgz
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.iso
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos/platform-20161117T180610Z.usb.bz2


SmartOS debug builds:

https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.tgz
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.iso
https://us-east.manta.joyent.com/rmustacc/public/preview/xhci/20161110/smartos-dbg/platform-20161116T183444Z.usb.bz2


Finally, if you're interested in review, we've started the process of
our public review at Joyent. It's available at
https://cr.joyent.us/#/c/872/. We will likely land this in
illumos-joyent and get a little bit more soak time and then RTI it for
illumos.

Once again, I'd like to thank everyone who's helped test, given me
advice, or helped me through while debugging nasty bugs.

Thanks,
Robert


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


--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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

Re: [OpenIndiana-discuss] local zones and local users

2016-11-09 Thread Maurilio Longo via openindiana-discuss 

Hi Bob,

Bob Friesenhahn wrote:


Normally one tries really hard to avoid putting any actual data in the 
zone since this becomes dead weight (or baggage) whenever the zone is 
cloned and going back to an earlier snapshot reverts both the zone root 
and the data.  Instead you have the zone do a loopback mount of a 
directory in the global zone, and apparently one can also do a zfs mount 
of a filesystem if that is desired.  For security reasons, zones are not 
normally allowed to do their own mounts (requires a filesystem mount 
privilege).




thanks for the hint, this is what I was looking for.

Now it is clear why nearly all of the examples I've found so far were so 
"different" from my way of thinking  :)


Best regards.

Maurilio.


--
 __
|  |  | |__| Maurilio Longo
|_|_|_||


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

Re: [OpenIndiana-discuss] local zones and local users

2016-11-09 Thread Maurilio Longo via openindiana-discuss 

Hi Till,

in my case they don't seem to be holding any configuration file and dev is
empty, but the fact that zone1 is still under GZ's control makes sense.

root@st-ar-02:/root# ls -la /nas/zones/zone1/
total 10
drwx--  4 root root  4 Nov  9 12:30 .
drwxr-xr-x  3 root root  3 Nov  9 12:08 ..
drwxr-xr-x  2 root sys   2 Nov  9 12:30 dev
drwxr-xr-x 18 root root 19 Nov  9 12:42 root
root@st-ar-02:/root# ls -la /nas/zones/zone1/dev/
total 1
drwxr-xr-x 2 root sys  2 Nov  9 12:30 .
drwx-- 4 root root 4 Nov  9 12:30 ..

Best regards.

Maurilio.


Till Wegmüller wrote:

Hi Maurilio

So far what I have learned from zones is that the FS of the Zone Starts 
at nas/zones/zone1/ROOT and not nas/zones/zone1. So it would be logical 
that the zone has no permission to nas/zones/zone1 as that Directory is 
still under the ownership of the Global Zone.


If you have a look at nas/zones/zone1 you will find not only a directory 
called ROOT but also other files which have the Configuration of the 
Zone in it.



--
 __
|  |  | |__| Maurilio Longo
|_|_|_||





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

Re: [OpenIndiana-discuss] local zones and local users

2016-11-09 Thread Maurilio Longo via openindiana-discuss 

Hi again,

so, next round against zones :)

Inside my local zone (named zone1) I have:

root@zone1:/root# zfs list
NAME   USED  AVAIL  REFER  MOUNTPOINT
nas650G  13.4T96K  /nas
nas/zones  537M  13.4T88K  /nas/zones
nas/zones/zone1537M  13.4T88K  /nas/zones/zone1
nas/zones/zone1/ROOT   537M  13.4T88K  legacy
nas/zones/zone1/ROOT/zbe   537M  13.4T   537M  legacy


So I've created export and export/home as zfs filesystems inside my local zone

root@zone1:/root# zfs create -o mountpoint=/export nas/zones/zone1/ROOT/export
root@zone1:/root# zfs create nas/zones/zone1/ROOT/export/home

and now I have

# zfs list
NAME   USED  AVAIL  REFER  MOUNTPOINT
nas650G  13.4T96K  /nas
nas/zones  537M  13.4T88K  /nas/zones
nas/zones/zone1537M  13.4T88K  /nas/zones/zone1
nas/zones/zone1/ROOT   537M  13.4T88K  legacy
nas/zones/zone1/ROOT/export176K  13.4T88K  /export
nas/zones/zone1/ROOT/export/home88K  13.4T88K  /export/home
nas/zones/zone1/ROOT/zbe   537M  13.4T   537M  legacy


and at this point I can add a local user to the zone with

root@zone1:/root# useradd -b /export/home -m -z maurilio
80 blocks
root@zone1:/root# zfs list
NAMEUSED  AVAIL  REFER  MOUNTPOINT
nas 650G  13.4T96K  /nas
nas/zones   537M  13.4T88K  /nas/zones
nas/zones/zone1 537M  13.4T88K  /nas/zones/zone1
nas/zones/zone1/ROOT537M  13.4T88K  legacy
nas/zones/zone1/ROOT/export 292K  13.4T88K  /export
nas/zones/zone1/ROOT/export/home204K  13.4T88K  /export/home
nas/zones/zone1/ROOT/export/home/maurilio   116K  13.4T   116K 
/export/home/maurilio

nas/zones/zone1/ROOT/zbe537M  13.4T   537M  legacy


Which is similar to a global zone's hierarchy and gives me a local user which 
is not root.


I did try to create the export filesystem as child of nas/zones/zone1 but I 
can't, I get a permission denied error.


Now, just to be sure, am I the only one who tries/wants to proceed like this?

I've found several examples related to Solaris 11 where the global zone's 
/export/home is imported via zonecfg inside the local zone, but I'm still 
unable to find an example where export/home is created inside a local zone's 
root fs.


Any confirmation will be appreciated.

Regards

Maurilio.



Maurilio Longo via openindiana-discuss wrote:
2) my local zone has a /home directory and an /export directory but it 
hasn't
got the export/home zfs filesystem that I have on every rpool so when I 
try to

issue a:

useradd -m local-user

I get an error "unable to create the home directory. Operation non 
applicable".


What is the "correct" or preferred way to proceed?

Can I/should I create, inside my local zone, an export/home zfs filesystem,
mount it onto /export and then add the user?

Or is it better to mount the global zone's /export/home inside the local 
zone
(adding an fs with zonecfg) to have a place where I can create local 
user's homes?



--
 __
|  |  | |__| Maurilio Longo
|_|_|_||


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

Re: [OpenIndiana-discuss] local zones and local users

2016-11-07 Thread Maurilio Longo via openindiana-discuss 

Thanks Adam!

Maurilio


Adam Števko wrote:

Hi,

On Nov 7, 2016, at 2:29 PM, Jonathan Adams > wrote:


1) Is sysconfig or sysidtool (the tool that starts when the first 
zlogin -C

myzone is executed) for the local configuration of the zone still
available in
openindiana/hipster or do I need to manually configure the zone? 
(timezone,

root pw, hostname, keyboard, network etc).


we switched to sysding, which is easier than those previous tools. To 
have an idea, have a look at man sysding and example 
here https://github.com/OpenIndiana/sysding/blob/oi/sysding.conf

You will be able to configure most settings via it.

Cheers,
Adam


--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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

Re: [OpenIndiana-discuss] local zones and local users

2016-11-07 Thread Maurilio Longo via openindiana-discuss 

Hi Jonathan,

thanks.

I was aware of /home and /export/home what I find "strange" is that there 
isn't a zfs fs mounted on export/home like it happens inside the global zone.


Regards.

Maurilio.

Jonathan Adams wrote:

Hi Maurilio,
welcome to the group.

first off you'll probably find that /home is an "auto-mounted" directory 
on your system, there are a couple of ways around this:

1) edit /etc/auto_master and comment out the line with "/home" in it.
2) create the directory manually in /export/home/ and then change 
/etc/auto_home so that it has the line:

* localhost:/export/home/&

Jon

On 7 November 2016 at 13:23, Maurilio Longo via openindiana-discuss 
<mailto:openindiana-discuss@openindiana.org>> wrote:


Hi all,

I've just started my journey inside local zones on latest hipster
(2016.10)
and I have a few questions for which I can't find a conclusive solution
googling around.

1) Is sysconfig or sysidtool (the tool that starts when the first
zlogin -C
myzone is executed) for the local configuration of the zone still
available in
openindiana/hipster or do I need to manually configure the zone?
(timezone,
root pw, hostname, keyboard, network etc).

2) my local zone has a /home directory and an /export directory but
it hasn't
got the export/home zfs filesystem that I have on every rpool so
when I try to
issue a:

useradd -m local-user

I get an error "unable to create the home directory. Operation non
applicable".

What is the "correct" or preferred way to proceed?

Can I/should I create, inside my local zone, an export/home zfs
filesystem,
mount it onto /export and then add the user?

Or is it better to mount the global zone's /export/home inside the
local zone
(adding an fs with zonecfg) to have a place where I can create local
user's homes?

Thanks.

Maurilio.



-- 
 __

|  |  | |__| Maurilio Longo
|_|_|_||




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




--
 __
|  |  | |__| Maurilio Longo
|_|_|_||


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

[OpenIndiana-discuss] local zones and local users

2016-11-07 Thread Maurilio Longo via openindiana-discuss 

Hi all,

I've just started my journey inside local zones on latest hipster (2016.10)
and I have a few questions for which I can't find a conclusive solution
googling around.

1) Is sysconfig or sysidtool (the tool that starts when the first zlogin -C
myzone is executed) for the local configuration of the zone still available in
openindiana/hipster or do I need to manually configure the zone? (timezone,
root pw, hostname, keyboard, network etc).

2) my local zone has a /home directory and an /export directory but it hasn't
got the export/home zfs filesystem that I have on every rpool so when I try to
issue a:

useradd -m local-user

I get an error "unable to create the home directory. Operation non applicable".

What is the "correct" or preferred way to proceed?

Can I/should I create, inside my local zone, an export/home zfs filesystem,
mount it onto /export and then add the user?

Or is it better to mount the global zone's /export/home inside the local zone
(adding an fs with zonecfg) to have a place where I can create local user's 
homes?

Thanks.

Maurilio.



--
 __
|  |  | |__| Maurilio Longo
|_|_|_||




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

Re: [OpenIndiana-discuss] usb 2 pci-e card

2016-10-27 Thread Maurilio Longo via openindiana-discuss 

Ok,

got it, works perfectly :)

Maurilio.

Maurilio Longo via openindiana-discuss wrote:

Hi Predrag,

thank you, I'm buying one right now.

I'll report back how it works with my Dell.

Regards.

Maurilio.

Predrag Zečević - Technical Support Analyst wrote:

On 10/24/16 12:25 PM, Maurilio Longo via openindiana-discuss wrote:

Hi all,

I have a Dell PowerEdge t330 which is a usb-3 only unit, it works OK in
every
aspect but I can't use it in console (no mouse or keyboard) so if a
problem arises during boot before the ssh service is running I'm in
trouble.

Do any of you have an advice for a usb-2 pci-e card which works well 
with

openindiana/hipster?

Thanks.

Maurilio.



Hi Maurilo,
I am using PEXUSB4DP 4 port low profile PCI-e card from startech.com...
Have keyboard and mouse attached to it...

Its functionality might depend on BIOS (I guess).
Regards.





--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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

Re: [OpenIndiana-discuss] usb 2 pci-e card

2016-10-24 Thread Maurilio Longo via openindiana-discuss 

Hi Predrag,

thank you, I'm buying one right now.

I'll report back how it works with my Dell.

Regards.

Maurilio.

Predrag Zečević - Technical Support Analyst wrote:

On 10/24/16 12:25 PM, Maurilio Longo via openindiana-discuss wrote:

Hi all,

I have a Dell PowerEdge t330 which is a usb-3 only unit, it works OK in
every
aspect but I can't use it in console (no mouse or keyboard) so if a
problem arises during boot before the ssh service is running I'm in
trouble.

Do any of you have an advice for a usb-2 pci-e card which works well with
openindiana/hipster?

Thanks.

Maurilio.



Hi Maurilo,
I am using PEXUSB4DP 4 port low profile PCI-e card from startech.com...
Have keyboard and mouse attached to it...

Its functionality might depend on BIOS (I guess).
Regards.



--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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

[OpenIndiana-discuss] usb 2 pci-e card

2016-10-24 Thread Maurilio Longo via openindiana-discuss 

Hi all,

I have a Dell PowerEdge t330 which is a usb-3 only unit, it works OK in every
aspect but I can't use it in console (no mouse or keyboard) so if a problem 
arises during boot before the ssh service is running I'm in trouble.


Do any of you have an advice for a usb-2 pci-e card which works well with
openindiana/hipster?

Thanks.

Maurilio.

--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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

Re: [OpenIndiana-discuss] USB3 devices needed for driver testing

2016-10-04 Thread Maurilio Longo via openindiana-discuss 

Hi Adam,

I have a Dell PowerEdge T330 with usb3 ports and SS (usb 3.1?) ports.

None of them works.

Regards.

Maurilio.

Adam Števko wrote:

Hello folks,

there is an ongoing work on USB3 support in illumos and we should participate 
in testing. OI community can provide good testing background as I bet there is 
plenty of USB3 hardware.

I’d like to create a list of person (email), device and driver, so we have that 
ready when actual driver testing comes.  Any exotic USB3 device or peripheral 
will help.

So if anybody is interested in helping, please respond to this email. I’d also 
gladly ask others to not debate off-topic stuff in this thread. Thanks for 
understanding!

Cheers,
Adam




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


--
 __
|  |  | |__| Maurilio Longo
|_|_|_||



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