subject:"\[OpenIndiana\-discuss\] OMNIOS"

Re: [OpenIndiana-discuss]  OmniOS Emergency Security Update r36m, r34am, r30cm - Baron Samedit

2021-01-27 Thread Volker A. Brandt

James via openindiana-discuss writes:
> On 27/01/2021 14:46, OmniOS Community Edition Newsletter wrote:
>
> > this will take care of the update. If you would like to see what is
> > going to happen before actually doing it, try
> >
> > # pkg update -nv sudo omnios-userland entire
>
> Just puzzled... why does this downgrade rsync, then on update it on next
> update:

To eliminate all side effects, just try "pkg update -nv sudo".  This
will avoid anything that is specified by version in "entire".

Regards -- 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]  OmniOS Emergency Security Update r36m, r34am, r30cm - Baron Samedit

2021-01-27 Thread James via openindiana-discuss


On 27/01/2021 15:19, James via openindiana-discuss wrote:

On 27/01/2021 14:46, OmniOS Community Edition Newsletter wrote:


Wrong list, so sorry, probable the mostly the people anyway!


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

Re: [OpenIndiana-discuss]  OmniOS Emergency Security Update r36m, r34am, r30cm - Baron Samedit

2021-01-27 Thread James via openindiana-discuss


On 27/01/2021 14:46, OmniOS Community Edition Newsletter wrote:


this will take care of the update. If you would like to see what is
going to happen before actually doing it, try

# pkg update -nv sudo omnios-userland entire


Just puzzled... why does this downgrade rsync, then on update it on next 
update:


# pkg update -v omnios-userland
Packages to update: 1
 Estimated space available: 442.39 GB
Estimated space to be consumed:  10.31 MB
   Create boot environment:No
Create backup boot environment:   Yes
  Rebuild boot archive:No

Changed packages:
omnios
  network/rsync
3.2.2-151030.0 -> 3.1.3-151030.0

DOWNLOADPKGS FILESXFER (MB) 
 SPEED
Completed1/1   3/3  0.3/0.3 
819k/s


pkg update -PHASE  ITEMS
Removing old actions 4/4
Installing new actions   1/1
Updating modified actions6/6
Updating package state database Done
Updating package cache   1/1
Updating image stateDone
Creating fast lookup database   Done
Reading search indexDone
Building new search index423/423
Updating package cache   2/2


# pkg update -nv
Packages to update: 1
 Estimated space available: 442.37 GB
Estimated space to be consumed:  10.38 MB
   Create boot environment:No
Create backup boot environment:   Yes
  Rebuild boot archive:No

Changed packages:
omnios
  network/rsync
3.1.3-151030.0 -> 3.2.2-151030.0



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

Re: [OpenIndiana-discuss] OmniOS CE LX Zones and bhyve

2018-05-18 Thread Aurélien Larcher

On Fri, May 18, 2018 at 11:56 PM, Rasaki Temidire  wrote:

> Hello,
>
>
>
> Are there any plans to pull in any of the recent additions from omniOS CE
> illumos work that introduced LX zones and bhyve?  If it is already in the
> openIndiana repository, how can I update my current hipster 2018.04
> installation to take in those additions?  If not, are there any plans to
> pull those additions in or is openIndiana going to stay on vanilla
> illumos-gate like Tribblix (although he has an omniOS variant of late with
> the changes).
>

The project needs help to pull this type of thing and maintain it in the
long run.
Unless one or two persons volunteer and commit to rebase the branch once in
a while OpenIndiana will stay vanilla.
There is already quite a lot of work ongoing for modernizing the toolchain
and maintain the current set of packages.
LX itself is scattered across 900+ commits and merging it cleanly would
take a considerable amount of dedication :)

Kind regards,

Aurélien

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

-- 
---
Praise the Caffeine embeddings
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

[OpenIndiana-discuss] OmniOS CE LX Zones and bhyve

2018-05-18 Thread Rasaki Temidire


Hello,



Are there any plans to pull in any of the recent additions from omniOS CE 
illumos work that introduced LX zones and bhyve?  If it is already in the 
openIndiana repository, how can I update my current hipster 2018.04 
installation to take in those additions?  If not, are there any plans to pull 
those additions in or is openIndiana going to stay on vanilla illumos-gate like 
Tribblix (although he has an omniOS variant of late with the changes).



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

Re: [OpenIndiana-discuss] [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

2016-11-30 Thread Fred Liu

This is encouraging!

Thanks.

Fred

> -Original Message-
> From: wo...@4amlunch.net [mailto:wo...@4amlunch.net]
> Sent: 星期三, 十一月 30, 2016 20:04
> To: Fred Liu
> Cc: omnios-disc...@lists.omniti.com; smartos-disc...@lists.smartos.org;
> Discussion list for OpenIndiana; develo...@lists.illumos.org
> Subject: Re: [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?
> 
> I'm using ConnectX-2 cards in my OmniOS fileserver. Everything works 
> perfectly.
> Including SRP (SCSI RDMA). I use it with ESXi hosts.
> 
> -brian
> 
> > On Nov 30, 2016, at 06:47, Fred Liu  wrote:
> >
> > Hi,
> >
> > Please post if you know.
> >
> >
> > Thanks.
> >
> > Fred
> > ___
> > OmniOS-discuss mailing list
> > omnios-disc...@lists.omniti.com
> > http://lists.omniti.com/mailman/listinfo/omnios-discuss
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

2016-11-30 Thread wonko

I'm using ConnectX-2 cards in my OmniOS fileserver. Everything works perfectly. 
Including SRP (SCSI RDMA). I use it with ESXi hosts.

-brian

> On Nov 30, 2016, at 06:47, Fred Liu  wrote:
> 
> Hi,
> 
> Please post if you know.
> 
> 
> Thanks.
> 
> Fred
> ___
> OmniOS-discuss mailing list
> omnios-disc...@lists.omniti.com
> http://lists.omniti.com/mailman/listinfo/omnios-discuss

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] User/group accounts for packaged daemons

2016-03-19 Thread Bob Friesenhahn


On Fri, 18 Mar 2016, Jim Klimov wrote:


A solution of this sort involves running a number of services, such as a stack 
of milters, an antivirus engine, a sniffer (p0f), etc. - some with special 
privileges and constraints, and thus preferably different accounts, so possible 
security issues with one project do not let break into others. While some 
services might be generalized as 'mail' or 'antivir' accounts, it is not always 
good and safe to do so.

The illumos default UIDs and GIDs generally reserve numbers under 
100 and above somewhere around 6. While there are Wiki pages for 
illumos and OI to list the well-known and occupied "system" account 
numbers and names, I'm not sure there is a procedure to claim and 
reserve the number so as to avoid conflicts.


I already encountered a conflict when OmniOS introduced OpenSSH and 
used the user id used by another add-on package for it.  Due to this, 
I investigated the user id used by the SFE version of the package and 
used that.  The SFE versions should at least not conflict with user 
ids used by Oracle Solaris 11 packages.



On a side note, how do we uninstall or update IPS packages where software can 
create files, and we have no 'preremove' script goodness? :-)


From what I have read, while there is no script goodness associated 
with IPS packages, there is the ability to run a script when a service 
manifest is installed or removed.  As long as each package provides 
its own service manifest, then it should be possible to remove the 
junk when the associated service manifest is removed.


It would indeed be useful if there was a UID/GID registery for add-on 
software and managed by the Illumos project (even if just in a Git 
repository).  These should try not to conflict with what Oracle 
Solaris 10/11 and stable OpenIndiana are already using for similar 
packages.  Guidance should be taken from SFE, which has already needed 
to deal with conflicts.


Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] User/group accounts for packaged daemons

2016-03-19 Thread Tim Mooney


In regard to: Re: [OpenIndiana-discuss] [OmniOS-discuss] User/group...:


It would indeed be useful if there was a UID/GID registery for add-on
software and managed by the Illumos project (even if just in a Git
repository).  These should try not to conflict with what Oracle Solaris
10/11 and stable OpenIndiana are already using for similar packages.
Guidance should be taken from SFE, which has already needed to deal with
conflicts.


+1 to this.

I would also suggest that when there isn't already prior Solaris-derived
uid/guid names & numbers, we should default to choosing the same uid/guid
that's used for the package on Linux.  Of course, the Linux distros don't
always agree, but often they will.

Tim
--
Tim Mooney tim.moo...@ndsu.edu
Enterprise Computing & Infrastructure  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-07-09 Thread Predrag Zečević - Unix Systems Administrator


Hi Jim,

VB 5.0.0 is just released, and I have tried to patch vboxcontrol.sh - 
but got error during installation.


So, changed manually lines

 273 errorprint Failed to parse the Solaris 
kernel major version.

 274 exit 1

to

 273 return 0

and fixed pkginfo checksum. After that, installation went fine:


$ yes '' | pfexec pkgadd -d . -a ./autoresponse

The following packages are available:
  1  SUNWvbox Oracle VM VirtualBox
  (i386) 5.0.0,REV=2015.07.09.12.00.101573

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Processing package instance SUNWvbox from 
/export/NoBackup/Virtualization/VirtualBox/Install


Oracle VM VirtualBox(i386) 5.0.0,REV=2015.07.09.12.00.101573
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
Done.
Waiting for services from previous installation to be removed.
Warning!!! Some service(s) still appears to be present
## Processing package information.
## Processing system information.
   2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.

Installing Oracle VM VirtualBox as SUNWvbox
...
...
...
## Executing postinstall script.
Checking for older bits...
Installing new ones...
Detected Solaris 2015.0 Version
Loading VirtualBox kernel modules...
   - Loaded: Host module
   - Loaded: NetAdapter module
   - Detected: Force-load file //etc/vboxinst_vboxflt.
   - Loaded: NetFilter (STREAMS) module
   - Detected: Force-load file //etc/vboxinst_vboxusb.
   - Loaded: USBMonitor module
   - Loaded: USB module
Configuring services...
   - Enabled: Zone access service
Installing MIME types and icons...
Installing Python bindings...
   - Installed: Bindings for Python 2.6
Updating the boot archive...

Installation of SUNWvbox was successful.


FYI!
With best regards.
Predrag Zečević

On 06/24/15 04:43 PM, Jim Klimov wrote:


  Hello Predrag,

  Thanks for bringing that bit to my attention - now the same patch is 
reorganized (on GitHub) to suffice for both 4.3.28 and 5.0rc1 versions of 
vboxconfig.sh.

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



--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-07-09 Thread Predrag Zečević - Unix Systems Administrator


Of course, meant vboxconfig.sh (not vboxcontrol.sh) :-)

On 07/ 9/15 03:00 PM, Predrag Zečević - Unix Systems Administrator wrote:

Hi Jim,

VB 5.0.0 is just released, and I have tried to patch vboxcontrol.sh -
but got error during installation.

So, changed manually lines

  273 errorprint Failed to parse the Solaris
kernel major version.
  274 exit 1

to

  273 return 0

and fixed pkginfo checksum. After that, installation went fine:


$ yes '' | pfexec pkgadd -d . -a ./autoresponse

The following packages are available:
   1  SUNWvbox Oracle VM VirtualBox
   (i386) 5.0.0,REV=2015.07.09.12.00.101573

Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]:
Processing package instance SUNWvbox from
/export/NoBackup/Virtualization/VirtualBox/Install

Oracle VM VirtualBox(i386) 5.0.0,REV=2015.07.09.12.00.101573
Oracle Corporation
## Executing checkinstall script.
Checking package dependencies...
Done.
Waiting for services from previous installation to be removed.
Warning!!! Some service(s) still appears to be present
## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.

Installing Oracle VM VirtualBox as SUNWvbox
...
...
...
## Executing postinstall script.
Checking for older bits...
Installing new ones...
Detected Solaris 2015.0 Version
Loading VirtualBox kernel modules...
- Loaded: Host module
- Loaded: NetAdapter module
- Detected: Force-load file //etc/vboxinst_vboxflt.
- Loaded: NetFilter (STREAMS) module
- Detected: Force-load file //etc/vboxinst_vboxusb.
- Loaded: USBMonitor module
- Loaded: USB module
Configuring services...
- Enabled: Zone access service
Installing MIME types and icons...
Installing Python bindings...
- Installed: Bindings for Python 2.6
Updating the boot archive...

Installation of SUNWvbox was successful.


FYI!
With best regards.
Predrag Zečević

On 06/24/15 04:43 PM, Jim Klimov wrote:


  Hello Predrag,

  Thanks for bringing that bit to my attention - now the same patch is
reorganized (on GitHub) to suffice for both 4.3.28 and 5.0rc1 versions
of vboxconfig.sh.

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





--
Predrag Zečević
Technical Support Analyst
2e Systems GmbH

Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile:+49  174 3109 288, Skype: predrag.zecevic
E-mail:predrag.zece...@2e-systems.com

Headquarter:  2e Systems GmbH, Königsteiner Str. 87,
  65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director:Phil Douglas

http://www.2e-systems.com/ - Making your business fly!

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] pkg(5) in alternate roots

2015-07-02 Thread Jim Klimov

От: Dan McDonald dan...@omniti.com
Дата: Wednesday, July 1, 2015 19:43
 
  On Jul 1, 2015, at 9:20 AM, Jim Klimov j...@cos.ru wrote:
  
  The corresponding part of the script (and exact command-lines 
 involved) are here:
  
  
  ...
  
  { echo = 
 Updating PKG software itself
    
 ### This clause should fail if no 'pkg' updates were available, 
 or if a
    
 ### chrooted upgrade attempt with the new 'pkg' failed - both 
 ways fall
    
 ### through to altroot upgrade attempt
    if 
 /usr/bin/pkg -R $BENEW_MNT update --no-refresh --accept --deny-
 new-be --no-backup-be pkg; then \
  echo = Updating the image with new PKG software via chroot
  chroot $BENEW_MNT /usr/bin/pkg -R / image-update --no-refresh 
 --accept --deny-new-be --no-backup-be
    
 else false; fi; } || \
  { echo = 
 Updating the image with old PKG software via altroot
    
 /usr/bin/pkg -R $BENEW_MNT image-update --no-refresh --accept -
 -deny-new-be --no-backup-be; } || \
  { echo = 
 Updating the image with old PKG software via altroot and allowed 
 refresh   /usr/bin/pkg -R $BENEW_MNT image-update --accept 
 --deny-new-be --no-backup-be; }
 
 Can you run these, one at a time, by hand, so we all can see the 
 exact output per command that's run?  It'll help at least 
 me get a better bead on what's wrong.
 
 Thanks,
 Dan


Most of the output was in the screenshot just above that, and I guess I found a 
workaround 
that should suffice (will test more today), but for the sake of completeness, 
here goes:


The old BE was OmniOS bloody updated a month ago (20150602Z070407), new one 
with an updated pkg program was made yesterday, starting as the old one's clone 
(export BENEW=omnios-20150701Z065339-test) and the relevant tree was mounted 
into /a with my splitroot scripts from github:



###


:; ./beadm-mount.sh
omnios-20150701Z065339-test does not exist or appear to be a valid BE.
Please check that the name of the BE provided is correct.
=== Will clone omnios-20150602Z070407 into omnios-20150701Z065339-test, ok? 
Using these settings:
BENEW=omnios-20150701Z065339-test
BENEW_DS=rpool/ROOT/omnios-20150701Z065339-test
BENEW_MNT=/a
BENEW_MPT=/a
BEOLD=omnios-20150602Z070407
BEOLD_DS=rpool/ROOT/omnios-20150602Z070407
BEOLD_MNT=/
BEOLD_MPT=/
EXCLUDE_ATTRS='org.opensolaris.libbe:uuid|canmount|mountpoint'
RPOOL=rpool
RPOOLALT=
RPOOL_ROOT=rpool/ROOT
RPOOL_SHARED=rpool/SHARED
    (Press ENTER or CTRL+C)


Created successfully
=== Created omnios-20150701Z065339-test based on omnios-20150602Z070407
=== Trying to replicate ZFS attributes from original to new BE...
= ''
org.opensolaris.libbe:policy=static
org.openindiana.caiman:install=ready
= '/opt'
compression=gzip-9
= '/opt/local'
compression=gzip-9
= '/usr'
compression=gzip-9
= '/usr/local'
compression=gzip-9
= '/var'
compression=gzip-9
= '/var/db'
= '/var/db/pkgin'
= '/var/pkg'
compression=gzip-9
= '/var/pkg/publisher'
=== Replicated custom ZFS attributes
Mounted successfully on: '/a'
=== Mounted omnios-20150701Z065339-test at /a
rpool/ROOT/omnios-20150701Z065339-test   153387008      721348   124154515     
1%    /a
rpool/ROOT/omnios-20150701Z065339-test/usr   153387008      758981   124154515  
   1%    /a/usr
rpool/ROOT/omnios-20150701Z065339-test/usr/local   153387008          28   
124154515     1%    /a/usr/local
rpool/ROOT/omnios-20150701Z065339-test/opt   153387008     1207927   124154515  
   1%    /a/opt
rpool/ROOT/omnios-20150701Z065339-test/opt/local   153387008      811058   
124154515     1%    /a/opt/local
rpool/ROOT/omnios-20150701Z065339-test/var   153387008       18600   124154515  
   1%    /a/var
rpool/ROOT/omnios-20150701Z065339-test/var/db   153387008          33   
124154515     1%    /a/var/db
rpool/ROOT/omnios-20150701Z065339-test/var/db/pkgin   153387008      665190   
124154515     1%    /a/var/db/pkgin
rpool/ROOT/omnios-20150701Z065339-test/var/pkg   153387008       38370   
124154515     1%    /a/var/pkg
rpool/ROOT/omnios-20150701Z065339-test/var/pkg/publisher   153387008        
9364   124154515     1%    /a/var/pkg/publisher
=== BE clone completed!


=== To upgrade from upstream do:
pkg -R /a image-update --deny-new-be --no-backup-be  touch /a/reconfigure 
 bootadm update-archive -R /a  beadm umount omnios-20150701Z065339-test


TS=`date -u +%Y%m%dZ%H%M%S`
zfs snapshot -r rpool/SHARED@postupgrade-$TS
zfs snapshot -r rpool/ROOT/omnios-20150701Z065339-test@postupgrade-$TS


beadm activate omnios-20150701Z065339-test
===


INFO: Unmounting any previous traces (if any - may fail), just in case
=== Unmounting BE omnios-20150701Z065339-test under '/a'...
= beadm-unmounting omnios-20150701Z065339-test (/a)...
Unmounted successfully
Mounted successfully on: '/a'
BE                          Active Mountpoint Space Policy Created
omnios-20150701Z065339-test -      /a         15.0K

Re: [OpenIndiana-discuss] [OmniOS-discuss] pkg(5) in alternate roots

2015-07-01 Thread Jim Klimov

1 июля 2015 г. 15:20:56 CEST, Jim Klimov j...@cos.ru пишет:
Hello all,


Due to my split-root configurations, I often do OI/OmniOS upgrades in a
pre-created cloned BE (automated by
https://github.com/jimklimov/illumos-splitroot-scripts since the
generic beadm/zfs clone do a poor job with customized zfs attributes on
child datasets). As part of an upgrade, I do a chroot into the mounted
new BE to use the pkg(5) in place (and with altroot of /) and if
this fails - I fall back to alternate root (-R) with the unchanged
pkg(5) version installed in the original BE. In either case, I pass the
--deny-new-be parameter to pkg(5). (relevant code snippet is
presented below in this message)


However there are some packages whose upgrades seem to require a
non-Live BE installation. And even though I install to an alternate
BE, they fail. Is there some way around this, beside fixing pkg(5)
itself?


For example, recently I got the state below: the pkg program got
updated in the new BE, but it could not be used via chroot due to live
image concerns, and the old pkg(5) in original BE did not suffice for
the upgrades. A reboot into the new BE and another upgrade request
fixes this, but that's kind of unwieldy. And installing new pkg into
old BE goes somewhat against the purpose of BEs (unchanged old state I
can roll back into - thus including escape from broken pkg(5) as any
other bit of system software).


Screenshot from the script:



= Updating PKG software itself
Packages to update: 1


DOWNLOAD                                PKGS         FILES    XFER (MB)
  SPEED
Completed                                1/1         16/16      0.3/0.3
 303k/s


PHASE                                          ITEMS
Removing old actions                             1/1
Updating modified actions                      18/18
Updating package state database                 Done
Updating package cache                           1/1
Updating image state                            Done
Creating fast lookup database                   Done
Reading search index                            Done
Updating search index                            1/1



= Updating the image with new PKG software via chroot
pkg update: The proposed operation cannot be performed on a live image.
= Updating the image with old PKG software via altroot
WARNING: pkg(5) appears to be out of date, and should be updated before
running update.  Please update pkg(5) by executing 'pkg install
pkg:/package/pkg' as a privileged user and then retry the update.
= Updating the image with old PKG software via altroot and allowed
refresh
WARNING: pkg(5) appears to be out of date, and should be updated before
running update.  Please update pkg(5) by executing 'pkg install
pkg:/package/pkg' as a privileged user and then retry the update.




The corresponding part of the script (and exact command-lines involved)
are here:


...

        { echo = Updating PKG software itself
          ### This clause should fail if no 'pkg' updates were
available, or if a
          ### chrooted upgrade attempt with the new 'pkg' failed - both
ways fall
          ### through to altroot upgrade attempt
          if /usr/bin/pkg -R $BENEW_MNT update --no-refresh --accept
--deny-new-be --no-backup-be pkg; then \
            echo = Updating the image with new PKG software via
chroot
            chroot $BENEW_MNT /usr/bin/pkg -R / image-update
--no-refresh --accept --deny-new-be --no-backup-be
          else false; fi; } || \
        { echo = Updating the image with old PKG software via
altroot
          /usr/bin/pkg -R $BENEW_MNT image-update --no-refresh
--accept --deny-new-be --no-backup-be; } || \
        { echo = Updating the image with old PKG software via
altroot and allowed refresh
          /usr/bin/pkg -R $BENEW_MNT image-update --accept
--deny-new-be --no-backup-be; }
...




Essentially, what I want is for pkg(5) to correctly guess, or be told
by the caller, that it in fact does not modify a live image and so
can do anything dangerous it would please to do.


Thanks in advance,
Jim Klimov








___
OmniOS-discuss mailing list
omnios-disc...@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

I guess i found the workaround - the pkg(5) script honors some PKG_LIVE_ROOT 
variable, for unittesting from what i gather, that along with -R allows to not 
create BEs for packages that otherwise need them.

I guess this is not a committed api, but will have to do ;)

Jim
--
Typos courtesy of K-9 Mail on my Samsung Android

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-06-24 Thread Jim Klimov


Hello all,

Earlier in March I posted a patch that fixes installation of VirtualBox on 
non-Oracle Solaris hosts (e.g. OpenIndiana and OmniOS). Lest it be lost in the 
list archives, I moved the patch (now licensed as GPLv2 to match VirtualBox 
licensing) and an accompanying README to GitHub: 
https://github.com/jimklimov/vboxconfig_sh

Feel free to add the changes into the distributions (if you maintain 
packages/repositories), so such hackery won't be needed ;)

Thanks, 
 Jim Klimov




- Исходное сообщение -
От: Jim Klimov j...@cos.ru
Дата: Monday, March 16, 2015 9:30
Тема: [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS
Кому (To): openindiana-discuss@openindiana.org, omnios-discuss 
omnios-disc...@lists.omniti.com
Копия (Cc): tho...@espix.net


 Hello all,

 Earlier this month I posted to the VirtualBox lists my patch for 
 vboxconfig.sh to better support 
 installation on non-Sun/Oracle Solaris-like hosts, tested on OI (Hipster) and 
 OmniOS (bloody). 
 It may support SXCE as well (has the code, but was not practically tested 
 lately) since there are 
 aspects where SXCE was like Solaris 10 (SVR4 packaging) and yet more advanced 
 than that 
 (CrossBow, etc.).

 Unfortunately, so far the post fell through the cracks... so for possible 
 integration into packages
 provided by the illumos distributions (e.g. to help the work done by Thomas 
 Gouverneur to turn
 SVR releases into IPS, or to support proper GPL-source builds of VirtualBox), 
 I'd like to repost 
 these fixes here too. Feel free to build on them, to make VB updates 
 hiccup-less ;)

 In my practice, it sufficed to pkgtrans the Oracle VB package into a 
 directory, patch the script
 vboxconfig.sh provided in the installation image, update the pkgmap with 
 new values for 
 size and checksum of the changed file, (run pkgrm to remove an obsoleted 
 installation) and 
 pkgadd to install the package from the directory.
 


 ---

 The reposted part:

 http://article.gmane.org/gmane.comp.emulators.virtualbox.devel/7390
 Date: 2015-03-09 15:09:25 GMT

 Hello all,

 I submit a patch which should simplify installation of modern VirtualBox on 
 some
 non-Oracle derivate distributions of Solaris which are known to host 
 VirtualBox 
 just fine. Most of the patch deals with proper detection of major and minor 
 OS
 version numbers on those distributions. Also there is now a touchable filename
 to enforce installation of USB filters and corresponding UNIX group accounts,
 as a workaround for further distros not detected as supported by even new 
 code.

 I submit this patch under the terms of MIT license.

 This was last tested with VirtualBox 4.3.24 and OpenIndiana Hipster and OmniOS
 Bloody, all updated today to the most current states available.

 Note this was not yet tested in practice with SXCE although snippets were 
 developed
 that should work there. I don't expect there are many of those installations 
 left beside my 
 closet, but those are all pleased with old VBox versions for now... ain't 
 broke, you know ;)


 Hope this helps,
 // Jim Klimov

 

  ___
  OmniOS-discuss mailing list
  omnios-disc...@lists.omniti.com
  http://lists.omniti.com/mailman/listinfo/omnios-discuss

 -- 

 ++
 ||
 | Климов Евгений, Jim Klimov |
 | технический директор   CTO |
 | ЗАО ЦОС и ВТ  JSC COSHT |
 ||
 | +7-903-7705859 (cellular)  mailto:jimkli...@cos.ru |
 |CC:ad...@cos.ru,jimkli...@gmail.com |
 ++
 | ()  ascii ribbon campaign - against html mail  |
 | /\- against microsoft attachments  |
 ++ 
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-06-24 Thread Predrag Zecevic [Unix Systems Administrator]


Hi Jim,

I was curious, so tried to test on *installed* tree (5.0.0_RC1):

$ pfexec bash
$ cd /opt/VirtualBox
$ ls -la vboxconfig.sh
-rwxr-xr-x  1 0 2  45K Jun  1 20:15 vboxconfig.sh*

$ gpatch -p1  vboxconfig.sh.patch
can't find file to patch at input line 10
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|This patch adds the ability for VirtualBox packaged installer script
|to configure USB filters on OpenSolaris and non-Oracle descendant
|distributions. For those distros not immediately covered by the patch,
|there is an ability to force the logic by 'touch /etc/vboxinst_vboxusb'
|
|Copyright (C) 2013-2015 by Jim Klimov under the terms of MIT License.
|
|--- vboxconfig.sh.orig 2015-03-02 16:17:43.0 +0100
|+++ vboxconfig.sh  2015-03-09 15:30:35.673996000 +0100
--
File to patch: vboxconfig.sh  
asked me here to enter file to patch
patching file vboxconfig.sh
Hunk #1 succeeded at 1 with fuzz 2.
Hunk #2 succeeded at 286 (offset 6 lines).
Hunk #3 succeeded at 315 (offset 6 lines).
Hunk #4 succeeded at 352 (offset 6 lines).
Hunk #5 succeeded at 703 (offset 6 lines).
Hunk #6 succeeded at 751 (offset 6 lines).
patch unexpectedly ends in middle of line
patch unexpectedly ends in middle of line
$ ls -al vboxc*
-rwxr-xr-x 1 root bin   47K Jun 24 14:40 vboxconfig.sh
-rwxr-xr-x 1 root bin   45K Jun  1 20:15 vboxconfig.sh.orig
-rw-r--r-- 1 root root 8.6K Jun 24 14:40 vboxconfig.sh.patch
$

I am not sure if that is supposed to be so, just FYI.

Thank you and very best regards.

On 06/24/15 02:04 PM, Jim Klimov wrote:


Hello all,

Earlier in March I posted a patch that fixes installation of VirtualBox on 
non-Oracle Solaris hosts (e.g. OpenIndiana and OmniOS). Lest it be lost in the 
list archives, I moved the patch (now licensed as GPLv2 to match VirtualBox 
licensing) and an accompanying README to GitHub: 
https://github.com/jimklimov/vboxconfig_sh

Feel free to add the changes into the distributions (if you maintain 
packages/repositories), so such hackery won't be needed ;)

Thanks,
  Jim Klimov




-  � -
��: Jim Klimov j...@cos.ru
: Monday, March 16, 2015 9:30
: [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS
 (To): openindiana-discuss@openindiana.org, omnios-discuss 
omnios-disc...@lists.omniti.com
� (Cc): tho...@espix.net



Hello all,



Earlier this month I posted to the VirtualBox lists my patch for vboxconfig.sh 
to better support
installation on non-Sun/Oracle Solaris-like hosts, tested on OI (Hipster) and 
OmniOS (bloody).
It may support SXCE as well (has the code, but was not practically tested 
lately) since there are
aspects where SXCE was like Solaris 10 (SVR4 packaging) and yet more advanced 
than that
(CrossBow, etc.).



Unfortunately, so far the post fell through the cracks... so for possible 
integration into packages
provided by the illumos distributions (e.g. to help the work done by Thomas 
Gouverneur to turn
SVR releases into IPS, or to support proper GPL-source builds of VirtualBox), 
I'd like to repost
these fixes here too. Feel free to build on them, to make VB updates 
hiccup-less ;)



In my practice, it sufficed to pkgtrans the Oracle VB package into a 
directory, patch the script
vboxconfig.sh provided in the installation image, update the pkgmap with 
new values for
size and checksum of the changed file, (run pkgrm to remove an obsoleted 
installation) and
pkgadd to install the package from the directory.





---



The reposted part:



http://article.gmane.org/gmane.comp.emulators.virtualbox.devel/7390
Date: 2015-03-09 15:09:25 GMT



Hello all,



I submit a patch which should simplify installation of modern VirtualBox on some
non-Oracle derivate distributions of Solaris which are known to host VirtualBox
just fine. Most of the patch deals with proper detection of major and minor OS
version numbers on those distributions. Also there is now a touchable filename
to enforce installation of USB filters and corresponding UNIX group accounts,
as a workaround for further distros not detected as supported by even new code.



I submit this patch under the terms of MIT license.



This was last tested with VirtualBox 4.3.24 and OpenIndiana Hipster and OmniOS
Bloody, all updated today to the most current states available.



Note this was not yet tested in practice with SXCE although snippets were 
developed
that should work there. I don't expect there are many of those installations 
left beside my
closet, but those are all pleased with old VBox versions for now... ain't 
broke, you know ;)




Hope this helps,
// Jim Klimov






   ___
   OmniOS-discuss mailing list
   omnios-disc...@lists.omniti.com
   http://lists.omniti.com/mailman/listinfo/omnios-discuss

  --

  ++
  |

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-06-24 Thread Jim Klimov


 Hello Predrag,




 Thanks for the feedback, I'll look into it with 5.0rc1 - I only tested across 
a few latest 4.3.* releases during the patch's evolution.

 OTOH, you used an older version (published in March) which may fail on recent 
OI Hipster which changed the PKG FMRI numbering scheme - this is what my more 
recent fixes amend.

 As for patch unexpectedly ends in middle of line - I didn't see that one 
yet, did you download it from Github (as raw text 
https://raw.githubusercontent.com/jimklimov/vboxconfig_sh/master/vboxconfig.sh.patch),
 or from that e-mail post? Perhaps the mailing-list archival and/or download 
process was faulty?

 Finally, regarding matching of the filename - in the recent version of the 
patch, it now references subdirname/vboxconfig.sh in both original and new 
versions so as to not confuse the patch programs.

 I also added the copy-pasteable package-patching procedure to README in the 
GitHub project to facilitate installations.




 Thanks,
 Jim

- Исходное сообщение -
От: Predrag Zecevic [Unix Systems Administrator] 
predrag.zece...@2e-systems.com
Дата: Wednesday, June 24, 2015 14:52
Тема: Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer 
under OI/OmniOS
Кому (To): openindiana-discuss@openindiana.org

  Hi Jim,
  
  I was curious, so tried to test on *installed* tree (5.0.0_RC1):
  
  $ pfexec bash
  $ cd /opt/VirtualBox
  $ ls -la vboxconfig.sh
  -rwxr-xr-x  1 0 2  45K Jun  1 20:15 vboxconfig.sh*
  
  $ gpatch -p1  vboxconfig.sh.patch
  can't find file to patch at input line 10
  Perhaps you used the wrong -p or --strip option?
  The text leading up to this was:
  --
  |This patch adds the ability for VirtualBox packaged installer script
  |to configure USB filters on OpenSolaris and non-Oracle descendant
  |distributions. For those distros not immediately covered by the 
  patch,|there is an ability to force the logic by 'touch 
  /etc/vboxinst_vboxusb'|
  |Copyright (C) 2013-2015 by Jim Klimov under the terms of MIT License.
  |
  |--- vboxconfig.sh.orig 2015-03-02 16:17:43.0 +0100
  |+++ vboxconfig.sh  2015-03-09 
  15:30:35.673996000 +0100
  --
  File to patch: 
  vboxconfig.sh  asked me 
  here to enter file to patch
  patching file vboxconfig.sh
  Hunk #1 succeeded at 1 with fuzz 2.
  Hunk #2 succeeded at 286 (offset 6 lines).
  Hunk #3 succeeded at 315 (offset 6 lines).
  Hunk #4 succeeded at 352 (offset 6 lines).
  Hunk #5 succeeded at 703 (offset 6 lines).
  Hunk #6 succeeded at 751 (offset 6 lines).
  patch unexpectedly ends in middle of line
  patch unexpectedly ends in middle of line
  $ ls -al vboxc*
  -rwxr-xr-x 1 root bin   47K Jun 24 14:40 vboxconfig.sh
  -rwxr-xr-x 1 root bin   45K Jun  1 20:15 
  vboxconfig.sh.orig-rw-r--r-- 1 root root 8.6K Jun 24 14:40 
  vboxconfig.sh.patch$
  
  I am not sure if that is supposed to be so, just FYI.
  
  Thank you and very best regards.
  
  On 06/24/15 02:04 PM, Jim Klimov wrote:
  
   Hello all,
  
   Earlier in March I posted a patch that fixes installation of 
  VirtualBox on non-Oracle Solaris hosts (e.g. OpenIndiana and 
  OmniOS). Lest it be lost in the list archives, I moved the patch 
  (now licensed as GPLv2 to match VirtualBox licensing) and an 
  accompanying README to GitHub: 
  https://github.com/jimklimov/vboxconfig_sh
   Feel free to add the changes into the distributions (if you 
  maintain packages/repositories), so such hackery won't be needed ;)
  
   Thanks,
 Jim Klimov
  
  
  
  
   -  � -
  ��: Jim Klimov j...@cos.ru
   : Monday, March 16, 2015 9:30
   : [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS
    (To): openindiana-discuss@openindiana.org, omnios-discuss 
  omnios-disc...@lists.omniti.com
   � (Cc): tho...@espix.net
  
  
   Hello all,
  
   Earlier this month I posted to the VirtualBox lists my patch 
  for vboxconfig.sh to better support
   installation on non-Sun/Oracle Solaris-like hosts, tested on 
  OI (Hipster) and OmniOS (bloody).
   It may support SXCE as well (has the code, but was not 
  practically tested lately) since there are
   aspects where SXCE was like Solaris 10 (SVR4 packaging) and 
  yet more advanced than that
   (CrossBow, etc.).
  
   Unfortunately, so far the post fell through the cracks... so 
  for possible integration into packages
   provided by the illumos distributions (e.g. to help the work 
  done by Thomas Gouverneur to turn
   SVR releases into IPS, or to support proper GPL-source builds 
  of VirtualBox), I'd like to repost
   these fixes here too. Feel free to build on them, to make VB 
  updates hiccup-less ;)
  
   In my practice, it sufficed to pkgtrans the Oracle VB 
  package into a directory, patch the script
   vboxconfig.sh provided in the installation image, update 
  the pkgmap with new values for
   size and checksum of the changed file, (run

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-06-24 Thread Predrag Zecevic [Unix Systems Administrator]


Hi Jim,

This was download action (from bash history):

 2526  [2015-06-24 14:38:11] wget -c 
https://raw.githubusercontent.com/jimklimov/vboxconfig_sh/master/vboxconfig.sh.patch

I took link from github site (https://github.com/jimklimov/vboxconfig_sh)
Regards.


On 06/24/15 04:25 PM, Jim Klimov wrote:


  Hello Predrag,




  Thanks for the feedback, I'll look into it with 5.0rc1 - I only tested across 
a few latest 4.3.* releases during the patch's evolution.

  OTOH, you used an older version (published in March) which may fail on recent 
OI Hipster which changed the PKG FMRI numbering scheme - this is what my more 
recent fixes amend.

  As for patch unexpectedly ends in middle of line - I didn't see that one yet, did you 
download it from Github (as raw text 
https://raw.githubusercontent.com/jimklimov/vboxconfig_sh/master/vboxconfig.sh.patch), or from that 
e-mail post? Perhaps the mailing-list archival and/or download process was faulty?

  Finally, regarding matching of the filename - in the recent version of the patch, it 
now references subdirname/vboxconfig.sh in both original and new versions so 
as to not confuse the patch programs.

  I also added the copy-pasteable package-patching procedure to README in the 
GitHub project to facilitate installations.




  Thanks,
  Jim

- Исходное сообщение -
От: Predrag Zecevic [Unix Systems Administrator] 
predrag.zece...@2e-systems.com
Дата: Wednesday, June 24, 2015 14:52
Тема: Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer 
under OI/OmniOS
Кому (To): openindiana-discuss@openindiana.org

   Hi Jim,
  
   I was curious, so tried to test on *installed* tree (5.0.0_RC1):
  
   $ pfexec bash
   $ cd /opt/VirtualBox
   $ ls -la vboxconfig.sh
   -rwxr-xr-x  1 0 2  45K Jun  1 20:15 vboxconfig.sh*
  
   $ gpatch -p1  vboxconfig.sh.patch
   can't find file to patch at input line 10
   Perhaps you used the wrong -p or --strip option?
   The text leading up to this was:
   --
   |This patch adds the ability for VirtualBox packaged installer script
   |to configure USB filters on OpenSolaris and non-Oracle descendant
   |distributions. For those distros not immediately covered by the
   patch,|there is an ability to force the logic by 'touch
   /etc/vboxinst_vboxusb'|
   |Copyright (C) 2013-2015 by Jim Klimov under the terms of MIT License.
   |
   |--- vboxconfig.sh.orig 2015-03-02 16:17:43.0 +0100
   |+++ vboxconfig.sh  2015-03-09
   15:30:35.673996000 +0100
   --
   File to patch:
   vboxconfig.sh  asked me 
here to enter file to patch
   patching file vboxconfig.sh
   Hunk #1 succeeded at 1 with fuzz 2.
   Hunk #2 succeeded at 286 (offset 6 lines).
   Hunk #3 succeeded at 315 (offset 6 lines).
   Hunk #4 succeeded at 352 (offset 6 lines).
   Hunk #5 succeeded at 703 (offset 6 lines).
   Hunk #6 succeeded at 751 (offset 6 lines).
   patch unexpectedly ends in middle of line
   patch unexpectedly ends in middle of line
   $ ls -al vboxc*
   -rwxr-xr-x 1 root bin   47K Jun 24 14:40 vboxconfig.sh
   -rwxr-xr-x 1 root bin   45K Jun  1 20:15
   vboxconfig.sh.orig-rw-r--r-- 1 root root 8.6K Jun 24 14:40
   vboxconfig.sh.patch$
  
   I am not sure if that is supposed to be so, just FYI.
  
   Thank you and very best regards.
  
   On 06/24/15 02:04 PM, Jim Klimov wrote:
   
Hello all,
   
Earlier in March I posted a patch that fixes installation of
   VirtualBox on non-Oracle Solaris hosts (e.g. OpenIndiana and
   OmniOS). Lest it be lost in the list archives, I moved the patch
   (now licensed as GPLv2 to match VirtualBox licensing) and an
   accompanying README to GitHub:
   https://github.com/jimklimov/vboxconfig_sh
Feel free to add the changes into the distributions (if you
   maintain packages/repositories), so such hackery won't be needed ;)
   
Thanks,
  Jim Klimov
   
   
   
   
-  � -

��: Jim Klimov j...@cos.ru

: Monday, March 16, 2015 9:30
: [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS
 (To): openindiana-discuss@openindiana.org, omnios-discuss
   omnios-disc...@lists.omniti.com
� (Cc): tho...@espix.net
   
   
Hello all,
   
Earlier this month I posted to the VirtualBox lists my patch
   for vboxconfig.sh to better support
installation on non-Sun/Oracle Solaris-like hosts, tested on
   OI (Hipster) and OmniOS (bloody).
It may support SXCE as well (has the code, but was not
   practically tested lately) since there are
aspects where SXCE was like Solaris 10 (SVR4 packaging) and
   yet more advanced than that
(CrossBow, etc.).
   
Unfortunately, so far the post fell through the cracks... so
   for possible integration into packages
provided by the illumos distributions (e.g. to help the work
   done by Thomas Gouverneur to turn
SVR releases into IPS, or to support proper GPL-source

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

2015-06-24 Thread Jim Klimov


 Hello Predrag,

 Thanks for bringing that bit to my attention - now the same patch is 
reorganized (on GitHub) to suffice for both 4.3.28 and 5.0rc1 versions of 
vboxconfig.sh.

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

2014-06-04 Thread Jonathan Adams

On 3 June 2014 17:18, ken mays via openindiana-discuss 
openindiana-discuss@openindiana.org wrote:
snip

 Point is there are a few options and custom servers or the cheap ones on
 eBay for $500 (i.e. Dell R710 or similar)...


minor nit.  the Dell R710's have Broadcom network cards that didn't play
nice in Solaris 10, needing a reboot to fix them when they decided to
suddenly stop.

they seem more stable in OI, but I feel it's worth mentioning.

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

2014-06-04 Thread Ian Collins


Jonathan Adams wrote:

On 3 June 2014 17:18, ken mays via openindiana-discuss 
openindiana-discuss@openindiana.org wrote:
snip


Point is there are a few options and custom servers or the cheap ones on
eBay for $500 (i.e. Dell R710 or similar)...


minor nit.  the Dell R710's have Broadcom network cards that didn't play
nice in Solaris 10, needing a reboot to fix them when they decided to
suddenly stop.

they seem more stable in OI, but I feel it's worth mentioning.


My experience was the opposite, they worked OK in Solaris 11, but were 
unreliable with Illumos...


Well worth avoiding, Dell will swap them for Intel, at least they do on 
720s.


--
Ian.


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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

2014-06-03 Thread ken mays via openindiana-discuss

I like what Ian said. although, 4U is a bit daunting.

You can opt for 1U-2U, 1-2 processors.

You can have a chassis with 8 drive bays. Fit for = 18TB of storage.

From there you can get solid state HDs and regular drives of your choice. 
Simple controller that can handle them - and has a driver for it.
Your HD vendor/OEM usually know that info on controller/HD compatibility.

You can also go for a separate NAS storage unit. 

Point is there are a few options and custom servers or the cheap ones on eBay 
for $500 (i.e. Dell R710 or similar)...

The HP N54L are well supported by the community.

~ Ken Mays
 




On Monday, June 2, 2014 1:56 AM, Ian Collins i...@ianshome.com wrote:
 


Jim Klimov wrote:
 Thus the box we'd build should be good with storage (including responsive 
 read-write NFS) and VM hosting. I am not sure whether OI, OmniOS or ESX(i?) 
 with HBA passthrough onto an illumos-based storage/infrastructure services VM 
 would be a better fit. Also, I was away from shopping for new server gear for 
 a while and its compatibility with illumos in particular, so I'd kindly ask 
 for suggestions for a server like that ;)

SmartOS would be a good fit if you are combining storage with KVM. USB 
booting also saves a couple of drive slots!

 The company's preference is to deal with HP, so while it is not an 
 impenetrable barrier, buying whatever is available under that brand is much 
 simpler for the department. Cost seems a much lesser constraint ;)

HP's bundled RAID controllers can be a problem, make sure you can get 
something with IT firmware, or at least JBOD support.

 I am less certain about HBAs (IT mode, without HW-RAID crap), and the 
 practically recommended redundancy (raidzN? raid10? how many extra disks in 
 modern size ranges are recommended - 3?)

That all depends on the number of drives and the workload.

 Also i am not sure about modern considerations of multiple PCI buses - 
 especially with regard to separation of ssd's onto a separate HBA (or 
 several?) to avoid bottlenecks in performance and/or failures.

SSDs can be SATA and the hard drives SAS.

 Finally, are departmental all-in-one combines following the Thumper ideology 
 of data quickly accessible to applications living on the same host without 
 uncertainties and delays of remote networking still at all 'fashionable'? ;)

They are with Joyent!

 Buying a single purchase initially may be easier to justify than multiple 
 boxes with separate roles, but there are other considerations too. In 
 particular, their corporate network is crappy and slow, so splitting into 
 storage+server nodes would need either direct cabling for data, or new 
 switching gear which i don't know yet if it would be a problem; localhost 
 data transfers are likely to be a lot faster. I am also not convinced about 
 higher reliability of split-head solutions, though for high loads i am eager 
 to believe that separating the tasks can lead to higher performance. I am 
 uncertain if this setup and its tasks would qualify for that; but it might be 
 expanded later on, including role-separation, if a practical need is found 
 after all.

You can easily get all you are after in a 4U all in one.  Keep the 
system simple if you can.

 PS: how do you go about backing up such a thing? Would some N54L's suffice to 
 receive zfs-send's of select datasets? :)

Another, low spec Illumos box with plenty of storage.  Performance won't 
be an issue, so you can use wider raidzN vdevs to boots capacity.

-- 
Ian.



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

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

2014-06-02 Thread Ian Collins


Jim Klimov wrote:

Thus the box we'd build should be good with storage (including responsive 
read-write NFS) and VM hosting. I am not sure whether OI, OmniOS or ESX(i?) 
with HBA passthrough onto an illumos-based storage/infrastructure services VM 
would be a better fit. Also, I was away from shopping for new server gear for a 
while and its compatibility with illumos in particular, so I'd kindly ask for 
suggestions for a server like that ;)


SmartOS would be a good fit if you are combining storage with KVM. USB 
booting also saves a couple of drive slots!



The company's preference is to deal with HP, so while it is not an impenetrable 
barrier, buying whatever is available under that brand is much simpler for the 
department. Cost seems a much lesser constraint ;)


HP's bundled RAID controllers can be a problem, make sure you can get 
something with IT firmware, or at least JBOD support.



I am less certain about HBAs (IT mode, without HW-RAID crap), and the 
practically recommended redundancy (raidzN? raid10? how many extra disks in 
modern size ranges are recommended - 3?)


That all depends on the number of drives and the workload.


Also i am not sure about modern considerations of multiple PCI buses - 
especially with regard to separation of ssd's onto a separate HBA (or several?) 
to avoid bottlenecks in performance and/or failures.


SSDs can be SATA and the hard drives SAS.


Finally, are departmental all-in-one combines following the Thumper ideology of 
data quickly accessible to applications living on the same host without 
uncertainties and delays of remote networking still at all 'fashionable'? ;)


They are with Joyent!


Buying a single purchase initially may be easier to justify than multiple boxes 
with separate roles, but there are other considerations too. In particular, 
their corporate network is crappy and slow, so splitting into storage+server 
nodes would need either direct cabling for data, or new switching gear which i 
don't know yet if it would be a problem; localhost data transfers are likely to 
be a lot faster. I am also not convinced about higher reliability of split-head 
solutions, though for high loads i am eager to believe that separating the 
tasks can lead to higher performance. I am uncertain if this setup and its 
tasks would qualify for that; but it might be expanded later on, including 
role-separation, if a practical need is found after all.


You can easily get all you are after in a 4U all in one.  Keep the 
system simple if you can.



PS: how do you go about backing up such a thing? Would some N54L's suffice to 
receive zfs-send's of select datasets? :)


Another, low spec Illumos box with plenty of storage.  Performance won't 
be an issue, so you can use wider raidzN vdevs to boots capacity.


--
Ian.


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

Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

2013-01-04 Thread Fabio Rodrigues

Hi Alain/All,

 Well, I have about 4.2TB to copy (might have some redundant data that I'll 
find out soon), and I know I can copy over rsync, NFS or ssh and I'm not very 
concerned with the time it takes to be honest. 

 The reason I've decided to send the e-mail is, first of all, to find out is 
there was a solution to natively support NTFS that I wasn't aware of and 
second, in case there was nothing there, to make an statement about the issue 
and that might be solved in the future (hopefully soon, rater than later). I 
don't believe I would be the only one to benefit from a proper solution, and 
that (IMHO) would be also great for OmniOS/illumos based distros ;-)

 Now, I've been trying a couple of things in the meantime as well. The package 
ntfsprogs (which is available in the main OmniOS repo) provides some utils 
and I was able to list the files on my USB device, but the mount option wasn't 
ported to OmniOS. Here is more info about the pkg:

 #

 root@gearloose:~# pkg info -r ntfsprogs
 Name: system/file-system/ntfsprogs
 Summary: ntfsprogs - Utilities that provide access to NTFS
 Description: ntfsprogs are utilities that provide access to and manipulation
 of NTFS
 Category: System/Administration and Configuration
 State: Not installed
 Publisher: omnios
 Version: 2.0.0
 Build Release: 5.11
 Branch: 0.151004
 Packaging Date: Thu Oct 11 22:43:21 2012
 Size: 831.75 kB
 FMRI: 
pkg://omnios/system/file-system/ntfsprogs@2.0.0,5.11-0.151004:20121011T224321Z

 #

 I've also got parted from the main repo to help with reading the partition 
table, etc.

 After some Googling, I've found the following link:

 https://blogs.oracle.com/mandalika/entry/mounting_windows_ntfs_on_open

 The solution points to two Benelix packages: FSWpart and FSWfsmisc, but the 
links are dead. It creates a NFS share from the NTFS partition and mount it on 
localhost (ok, ok, I think I still prefer the ntfs-3g ;-) 

 Continuing my research, I've found somebody that kept the files:

 http://aminsblog.wordpress.com/2012/05/22/mount-ntfs-in-solaris-11/

 The packages were a bit old, but taking the risk I've downloaded the packages 
and gave it a go. Using the pkgadd, FSWpart installed with no problem but 
FSWfsmisc conflicted with some ntfsprogs binaries (as pointed in both blogs), 
so I didn't accept the binaries replacement and found it better to remove 
parted and ntfsprogs (interdependent somehow).
 Tried to install again FSWfsmisc, it completed the install but in the end 
gave me libgcc_s_so.1 lib error.
 Just thought it worth to mention both packages here, since they're part of 
this project: http://mount-ntfs.sourceforge.net/ . It looks abandoned at the 
moment, so maybe somebody will find it interesting and useful. Also, more info 
here: http://belenix.sarovar.org/binfiles/README.FSWfsmisc.txt 
 Here are both installed:

 #

 fabior@gearloose:~$ pkginfo -l FSWfsmisc
 PKGINST: FSWfsmisc
 NAME: Miscellaneous filesystem support for OpenSolaris
 CATEGORY: system
 ARCH: i386
 VERSION: 0.1
 BASEDIR: /
 VENDOR: 
 DESC: NFS server based read-only support for NTFS and EXT2FS on OpenSolaris
 PSTAMP: parnassus20060823173017
 INSTDATE: Jan 03 2013 22:04
 STATUS: completely installed
 FILES: 183 installed pathnames
 43 directories
 41 executables
 21970 blocks used (approx)

 fabior@gearloose:~$ pkginfo -l FSWpart 
 PKGINST: FSWpart
 NAME: x86 Partition Table Dumper
 CATEGORY: system
 ARCH: i386
 VERSION: 0.1
 BASEDIR: /
 VENDOR: 
 DESC: Utility to display information about the x86 partition table
 PSTAMP: parnassus20060816210351
 INSTDATE: Jan 03 2013 22:01
 STATUS: completely installed
 FILES: 3 installed pathnames
 2 executables
 198 blocks used (approx)

 #

 The lib error was affecting (obviously) other programs as well, like grep, 
wget and so on. So after some troubleshooting (ldd -s /usr/gnu/bin/grep, dump 
-Lv /usr/gnu/bin/grep, etc), found out that the FSWfsmisc install chopped my 
libgcc_s.so.1 and replaced with the following symlink:

 lrwxrwxrwx 1 root root 24 Jan 3 22:04 libgcc_s.so - ../sfw/lib/libgcc_s.so.1
 lrwxrwxrwx 1 root root 24 Jan 3 22:04 libgcc_s.so.1 - ../sfw/lib/libgcc_s.so.1

 There were no libs files under ../sfw/lib/, and I couldn't find the 
libgcc_s.so.1 anywhere!!! Panic station for a few secs, then I powered up an 
OmniOS VM I have on my Fedora laptop and scp the lib from there to my server 
and reacreate the libgcc_s.so symlink point to it. Everything working again 
;-)

 Now, after all installed, I've manage to mount the ntfs partition (mount -F 
ntfs -o ro /dev/dsk/c0t0d0p0 /mnt/usb), so voila!!! I could access the 
filesfor a few mins! When I've tried to rsync the files to a local 
directory, the NFS server kept timing out, so it's impossible to use... oh 
well, that was the closest I could get from it ;-)

 Sorry for the long e-mail... The next thing I will try is to remove those 2 
packages,

Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

2013-01-04 Thread Jean-Pierre


Hi Fabio,

Fabio Rodrigues wrote:

Hi Alain/All,



  The reason I've decided to send the e-mail is, first of all,

 to find out is there was a solution to natively support NTFS
 that I wasn't aware of and second, in case there was nothing
 there, to make an statement about the issue and that might be
 solved in the future (hopefully soon, rater than later).
 I don't believe I would be the only one to benefit from a
 proper solution, and that (IMHO) would be also great for
 OmniOS/illumos based distros ;-)


AFAIK, (apart from Microsoft) only Tuxera has an in-kernel
implementation of an NTFS driver. It is a closed-source one,
which has not been adapted to Solaris and friends.
(see http://www.tuxera.com)



  Now, I've been trying a couple of things in the meantime as well.

 The package ntfsprogs (which is available in the main OmniOS repo)
 provides some utils and I was able to list the files on my USB
 device, but the mount option wasn't ported to OmniOS. Here is more
 info about the pkg:


  #

  root@gearloose:~# pkg info -r ntfsprogs
  Name: system/file-system/ntfsprogs
  Summary: ntfsprogs - Utilities that provide access to NTFS
  Description: ntfsprogs are utilities that provide access to and manipulation
  of NTFS
  Category: System/Administration and Configuration
  State: Not installed
  Publisher: omnios
  Version: 2.0.0
  Build Release: 5.11
  Branch: 0.151004
  Packaging Date: Thu Oct 11 22:43:21 2012
  Size: 831.75 kB
  FMRI: 
pkg://omnios/system/file-system/ntfsprogs@2.0.0,5.11-0.151004:20121011T224321Z


This is a very old package from a dead project. Be prepared
to get into problems with 4k sector devices.

It has been taken over by ntfs-3g and it is now part of
the ntfs-3g releases and it has been ported to OpenIndiana.

The source code and executables for OpenIndiana are available on
http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html
(the same source code on Tuxera at
http://www.tuxera.com/community/ntfs-3g-advanced/#download)

Regards

Jean-Pierre

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

Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

2013-01-04 Thread Fabio Rodrigues

Hi Jean-Pierre,

 Hmmm, that's makes sense about the NTFS being a closed-source implementation, 
so that's why it's not present yet.

 Since the two packages haven't worked properly and, as you have pointed out, 
they're old, it's enough good reason for me to remove them. Giving a try with 
ntfs-3g soon ;-)

 I'll let you know.

 Cheers,
 Fabio
- Ursprüngliche Nachricht -
Von: Jean-Pierre
Gesendet: 04.01.13 18:20 Uhr
An: openindiana-discuss@openindiana.org
Betreff: Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount 
NTFS USB under OmniOS

 Hi Fabio, Fabio Rodrigues wrote:  Hi Alain/All,  The reason I've decided to 
send the e-mail is, first of all,  to find out is there was a solution to 
natively support NTFS  that I wasn't aware of and second, in case there was 
nothing  there, to make an statement about the issue and that might be  
solved in the future (hopefully soon, rater than later).  I don't believe I 
would be the only one to benefit from a  proper solution, and that (IMHO) 
would be also great for  OmniOS/illumos based distros ;-) AFAIK, (apart from 
Microsoft) only Tuxera has an in-kernel implementation of an NTFS driver. It is 
a closed-source one, which has not been adapted to Solaris and friends. (see 
http://www.tuxera.com)   Now, I've been trying a couple of things in the 
meantime as well.  The package ntfsprogs (which is available in the main 
OmniOS repo)  provides some utils and I was able to list the files on my USB  
device, but the mount option wasn't ported to OmniOS. Here is more  info about 
the pkg:   #   root@gearloose:~# pkg info -r 
ntfsprogs  Name: system/file-system/ntfsprogs  Summary: ntfsprogs - Utilities 
that provide access to NTFS  Description: ntfsprogs are utilities that provide 
access to and manipulation  of NTFS  Category: System/Administration and 
Configuration  State: Not installed  Publisher: omnios  Version: 2.0.0  
Build Release: 5.11  Branch: 0.151004  Packaging Date: Thu Oct 11 22:43:21 
2012  Size: 831.75 kB  FMRI: 
pkg://omnios/system/file-system/ntfsprogs@2.0.0,5.11-0.151004:20121011T224321Z 
This is a very old package from a dead project. Be prepared to get into 
problems with 4k sector devices. It has been taken over by ntfs-3g and it is 
now part of the ntfs-3g releases and it has been ported to OpenIndiana. The 
source code and executables for OpenIndiana are available on 
http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html (the same source 
code on Tuxera at http://www.tuxera.com/community/ntfs-3g-advanced/#download) 
Regards Jean-Pierre ___ 
OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org 
http://openindiana.org/mailman/listinfo/openindiana-discuss



---
 Fabio Rodrigues
 fab...@gmx.net
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [OmniOS-discuss] Mount NTFS USB under OmniOS

2013-01-01 Thread Fabio Rodrigues

Hi All,

 Thanks for all the answers. We got some very valid suggestions as the one 
below from you Jay, but I must say I'm not very comfortable (not technically) 
with it. I believe, as per Jim Klimov and Ken Mays replies, we should have a 
proper solution on OmniOS.

 Please, don't understand me wrong and I know very well that is easier to say 
than do, but maybe if there's somebody in the community willing to port fuse 
and ntfs-3g to OmniOS (if that would be the best solution, I don't know...) and 
add to the official repo, I'm sure it would be a great addition and can be 
added to the list of supported features. 

 I think that OmniOS is an outstanding OS and rock solid, as all the others 
illumos/OpenSolaris based ones!!! I really hope that the repos will be more 
rich in time, even though I like the minimalistic approach for now/

 I might try to copy all the data I have from a laptop running Linux and upload 
to my server via NFS, but I don't consider this thread closed and I would like 
to hear more about in case somebody else want to collaborate with this issue.

 Thanks a mill and Happy 2013!!!

 Cheers,
 Fabio
- Ursprüngliche Nachricht -
Von: Jay Fenton
Gesendet: 30.12.12 14:27 Uhr
An: smartos-disc...@lists.smartos.org
Betreff: Re: [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

 Hi Fabio, I'd suggest the easiest (and I use the term loosely) way to do this 
would be to bring up a Linux VM and, assuming it's supported, pass the raw USB 
device through to it. You can then mount your zpool via NFS from the global 
zone. I'm using SmartOS, and vmadm(1m) seems to imply that the -usb and 
-usbdevice are supported through qemu_opts. I'm not sure what value you would 
use for -usbdevice as it's normally host:VendorID:ProductID, and normally you 
can find these from /sbin/lsusb on Linux - not sure of the equivalent in 
Solaris land. Hope that helps. Best Regards, Jay Fenton On 30 Dec 2012, at 
20:46, Fabio Rodrigues fab...@gmx.net wrote:  Hi All,   Sorry for the 
SPAM to the other lists, but I'm just trying to find a solution for this. I 
didn't want to compile a ntfs-3g module on my machine, because maybe there's 
already something ready for it.   I believe this would be useful not only for 
NTFS USBs, but for any kind.   Any help will be appreciated ;-)   Cheers,  
Fabio- Ursprüngliche Nachricht -  Von: Fabio Rodrigues  
Gesendet: 25.12.12 01:32 Uhr  An: omnios-disc...@lists.omniti.com  Betreff: 
Mount NTFS USB under OmniOS  Hi All,   First of all, I've been using 
OmniOS stable Home for the last few weeks on a HP Microserver NL36 (8GB RAM). 
It's performing very well, but I'm still getting used with the OS. I've been 
using Solaris for a good few years so I'm not that rusty...   Now, I was 
trying to find out how to mount the USB (Iomega eGo 500GB, NTFS), but there's 
no guidelines on how to make my life easier. The intention is to mount some of 
my USB devices and copy the data to my zpool.   If any of you could help me 
with some guides and also if there's any option to add it as an automount (kind 
of like Linux does), let me know please.   Thank you very much in advance 
and Happy Xmas ;-)   Cheers,   ---  Fabio Rodrigues  fab...@gmx.net 
---  Fabio Rodrigues  fab...@gmx.net  smartos-discuss | Archives | 
Modify Your Subscription ___ 
OmniOS-discuss mailing list omnios-disc...@lists.omniti.com 
http://lists.omniti.com/mailman/listinfo/omnios-discuss



---
 Fabio Rodrigues
 fab...@gmx.net
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] [OmniOS-discuss] hardware specs for illumos storage/virtualization server

2012-11-17 Thread Paul B. Henson

On Sat, Nov 17, 2012 at 11:56:48PM +1100, Denis Cheong wrote:
 That's a lot of issues and questions to raise in the one post!

Sorry :), it was either that or post a dozen different threads ;).

 Let me start off by saying that your intentions are very similar to mine.
 My OmniOS box is the storage backend for my household, and this includes
 MythTV as well as stackloads of photos, videos, music, etc.

Cool.

 Intel S2600CO Motherboard (16 x DIMM slots, dual LGA2011)

Interesting, although I don't like that feature key. It sounds like it
has on-board SAS, but unless you type a magic key into the BIOS it
doesn't work? I hate that model. I'll have to take a look at the prices
though, the supermicro board was like $500.

 8 x 16GB Hynix DDR ECC DIMMs (total 128GB)

Ouch, 16GB sticks? They were pretty pricy compared to the 8GB.

 2 x LSI 9201-16i 6G SAS cards

Did you flash these with the IT firmware, or do they support JBOD out of
the box?

 Norco RPC-4224 case, 24 x hotswap 6G SAS bays

I looked at a couple Norco cases. They were OK, but the Supermicro one
just seemed better built, and

 OCZ ZX Series 850W power supply (note importantly this PSU has a 30A 5V
 rail)

came with dual redundant 960w power supplies. With the Norco cases, by
the time I added in the separately purchased power supplies, the cost
differential wasn't that much.

 13 x 3TB WD Red drives
[...]
 With respect to the NAS drives - it's too early for me to give much
 feedback on them, but they are definitely the ones to get, for the reasons
 you gave.

My only concern is performance, given they're only 5400 RPM. I just
don't know how to qualify my I/O needs enough to tell if that'll be a
problem. How do you have them set up? The newegg reviews also have a lot
of people complaining about DOA or early death, so reliability is a
concern too. With a 3 year warranty, it's not too big a deal if a couple
go belly up, as long as it's not 3 in a row before the hot spare
resilvers 8-/. Have you run bonnie++ on your setup?

 1. It's not going to work natively, nobody that I have been able to find
 has actually got a backend build working on Solaris and kept it up to date

Heh, I had no intention of trying to build Myth natively under illumos
:). That would just be painful.

 2. It would have been a good option, but BrandZ has gone by the wayside
 long ago

You mean the linux compatible zone? That would have been interesting, at
least performance wise. I wonder how hard it would be to bring that back
to illumos.

 3. KVM as I have so far tested has some major limitations that would make
 it impractical, i.e. both network bandwith and disk throughput is terrible
 to the point that it will cause problems with MythTV.

Really? I've got a quad-core sandy bridge i5 desktop set up at work
right now testing out omnios and kvm. It's only on a 100Mb port right
now, but a quick iperf from omnios native outbound:

[  4]  0.0-10.0 sec   106 MBytes  88.7 Mbits/sec
[  4]  0.0-10.0 sec  87.4 MBytes  73.3 Mbits/sec

Compared to one from a fedora vm under kvm:

[  3]  0.0-10.0 sec  91.8 MBytes  76.9 Mbits/sec
[  3]  0.0-10.0 sec  86.4 MBytes  72.4 Mbits/sec

Not a ridiculous difference. What kind of throughput are you seeing? Are
you using the e1000 nic or the virtio one? I'm using e1000 right now, I
haven't had a chance to play with the virtio. I won't be in the office
next week, but the week after I'll plug this box into a gig port and do
a bit more testing. Given joyent runs this stuff commercially, I can't
imagine it has endemic performance issues.

I'm actually planning to have my mythtv storage native on zfs, and share
via nfs from the host to the guest, so the vm disk won't really be an
issue for that.

 Please keep us up to date with how you go if you do deploy a MythTV backend
 into a KVM instance though, I'm interested to see your observations on
 network throughput, since mine was so crippled..

I probably won't get this box built or running before 2013 :), but I'll
definitely do some network testing on my omnios eval the week after next
and see what it does on a gig port.

Oh, forgot to try an iperf guest-host:

[  3]  0.0-10.0 sec   920 MBytes   772 Mbits/sec

Hmm, looks like my guest to host nfs should be pretty snappy :). I'd
expect higher though, I'll have to look at that.

Thanks for the feedback...

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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-27 Thread Paolo Marcheschi


HI

I tried it on a virtualbox machine, and it seems nothing special. :-\
It has its own repository :

http://pkg.omniti.com/omnios/release/en/catalog.shtml

uname -a

SunOS Omnios 5.11 omnios-79686dc i86pc i386 i386pc Solaris


Paolo

On 04/23/12 06:07 PM, James Carlson wrote:

Richard Elling wrote:

On Apr 23, 2012, at 6:27 AM, paolo marcheschi wrote:

Is that related with Openindiana ?, Are there any advantages with it ?

It is designed for the server market, not the desktop market.

A small amount of searching locates a manifesto:

http://lethargy.org/~jesus/writes/the-desktop-and-server-oil-and-water


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

[OpenIndiana-discuss] OMNIOS

2012-04-23 Thread paolo marcheschi


HI

I see that there is a variant of opensolaris known as Omnios:

http://omnios.omniti.com/

Is that related with Openindiana ?, Are there any advantages with it ?

Thank you

Paolo

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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-23 Thread Gary Gendel

Sounds like a minimal system, closer to SmartOS than OpenIndiana, but 
since most of their links were broken so it's hard to compare.


On 4/23/12 9:27 AM, paolo marcheschi wrote:

HI

I see that there is a variant of opensolaris known as Omnios:

http://omnios.omniti.com/

Is that related with Openindiana ?, Are there any advantages with it ?

Thank you

Paolo

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



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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-23 Thread Jonathan Adams

their web servers run on Linux and Windows ...
http://uptime.netcraft.com/up/hosted?netname=SCNET-NET-66-225-209-0-1,66.225.209.0,66.225.209.255

Eweek announced the OS on 4th April 2012 ...

http://www.eweek.com/c/a/Linux-and-Open-Source/OmniTI-Delivers-OmniOS-to-Replace-OpenSolaris-378324/

theoretically it might be worth keeping an eye on, but from first
glance (avoiding their broken links) I am unsure if they are
interested in joining our community, or pushing stuff back to us, or
of supporting Illumos/OpenIndiana itself as a commercial entity.

Jon

On 23 April 2012 14:27, paolo marcheschi paolo.marches...@ftgm.it wrote:
 HI

 I see that there is a variant of opensolaris known as Omnios:

 http://omnios.omniti.com/

 Is that related with Openindiana ?, Are there any advantages with it ?

 Thank you

 Paolo

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

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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-23 Thread Jonathan Adams

On 23 April 2012 14:38, Jonathan Adams t12nsloo...@gmail.com wrote:
 their web servers run on Linux and Windows ...
 http://uptime.netcraft.com/up/hosted?netname=SCNET-NET-66-225-209-0-1,66.225.209.0,66.225.209.255


actually looking at it they are probably not running windows, except
maybe as an accelerator (sounds like a stupid idea to me though).

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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-23 Thread Richard Elling

On Apr 23, 2012, at 6:27 AM, paolo marcheschi wrote:

 HI
 
 I see that there is a variant of opensolaris known as Omnios:

No, it is an illumos distribution.

 
 http://omnios.omniti.com/
 
 Is that related with Openindiana ?, Are there any advantages with it ?

It is designed for the server market, not the desktop market.
 -- richard

--
ZFS Performance and Training
richard.ell...@richardelling.com
+1-760-896-4422



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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-23 Thread James Carlson

Richard Elling wrote:
 On Apr 23, 2012, at 6:27 AM, paolo marcheschi wrote:
 Is that related with Openindiana ?, Are there any advantages with it ?
 
 It is designed for the server market, not the desktop market.

A small amount of searching locates a manifesto:

http://lethargy.org/~jesus/writes/the-desktop-and-server-oil-and-water

-- 
James Carlson 42.703N 71.076W carls...@workingcode.com

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

Re: [OpenIndiana-discuss] OMNIOS

2012-04-23 Thread Dan Swartzendruber

Looks interesting.  I dl'ed it and set it up in an ESXi VM and am playing
with it.  Definitely seems snappy.

-Original Message-
From: Richard Elling [mailto:richard.ell...@richardelling.com] 
Sent: Monday, April 23, 2012 11:23 AM
To: Discussion list for OpenIndiana
Subject: Re: [OpenIndiana-discuss] OMNIOS

On Apr 23, 2012, at 6:27 AM, paolo marcheschi wrote:

 HI
 
 I see that there is a variant of opensolaris known as Omnios:

No, it is an illumos distribution.

 
 http://omnios.omniti.com/
 
 Is that related with Openindiana ?, Are there any advantages with it ?

It is designed for the server market, not the desktop market.
 -- richard

--
ZFS Performance and Training
richard.ell...@richardelling.com
+1-760-896-4422



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


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

Re: [OpenIndiana-discuss]  OmniOS Emergency Security Update r36m, r34am, r30cm - Baron Samedit

Re: [OpenIndiana-discuss]  OmniOS Emergency Security Update r36m, r34am, r30cm - Baron Samedit

Re: [OpenIndiana-discuss]  OmniOS Emergency Security Update r36m, r34am, r30cm - Baron Samedit

Re: [OpenIndiana-discuss] OmniOS CE LX Zones and bhyve

[OpenIndiana-discuss] OmniOS CE LX Zones and bhyve

Re: [OpenIndiana-discuss] [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

Re: [OpenIndiana-discuss] [OmniOS-discuss] any supoorted in Mellanox HBA in illumos?

Re: [OpenIndiana-discuss] [OmniOS-discuss] User/group accounts for packaged daemons

Re: [OpenIndiana-discuss] [OmniOS-discuss] User/group accounts for packaged daemons

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] pkg(5) in alternate roots

Re: [OpenIndiana-discuss] [OmniOS-discuss] pkg(5) in alternate roots

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Fix to VirtualBox installer under OI/OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

Re: [OpenIndiana-discuss] [OmniOS-discuss] Shopping for an all-in-one server

Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] [smartos-discuss] Re: Mount NTFS USB under OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] Mount NTFS USB under OmniOS

Re: [OpenIndiana-discuss] [OmniOS-discuss] hardware specs for illumos storage/virtualization server

Re: [OpenIndiana-discuss] OMNIOS

[OpenIndiana-discuss] OMNIOS

Re: [OpenIndiana-discuss] OMNIOS

Re: [OpenIndiana-discuss] OMNIOS

Re: [OpenIndiana-discuss] OMNIOS

Re: [OpenIndiana-discuss] OMNIOS

Re: [OpenIndiana-discuss] OMNIOS

Re: [OpenIndiana-discuss] OMNIOS

35 matches

Site Navigation

Mail list logo

Footer information