Re: [OmniOS-discuss] Bug ?

> With pain in my heart, i fear OmniOs has started it's slow descent to >> death >>> :-( >>> >>> >>> >>> -Oorspronkelijk bericht- >>> Van: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] >> Namens >>>

Re: [OmniOS-discuss] Bug ?

> On Jul 3, 2017, at 10:41 AM, Jim Klimov wrote: > > > Among technological differences between OI and OO, a notable benefit is LX > zones. It was often stated that OI community has not enough resources to > deviate from upstream illumos-gate, since maintaining a fork beyond

Re: [OmniOS-discuss] Bug ?

;> >> Hi All, >> >> With pain in my heart, i fear OmniOs has started it's slow descent to >death >> :-( >> >> >> >> -Oorspronkelijk bericht----- >> Van: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] >Namens >

Re: [OmniOS-discuss] Bug ?

On Sun, 2 Jul 2017, Tobias Oetiker wrote: ; not to join forces seem to be a pitty ... how about hosting that fork on ; https://github.com/omniosorg and starting to accept PRs there At the moment the fork is very much driven by our requirements and not considering a wider community. We're

Re: [OmniOS-discuss] Bug ?

- On Jul 2, 2017, at 12:09 PM, Andy Fiddaman omn...@citrus-it.net wrote: > On Thu, 29 Jun 2017, Guenther Alka wrote: > > ; Unless there are news regarding OmniOS my stance is > ; > ; - OmniOS 151022 is a freeze of current Illumos + LX. At the moment it is the > ; most stable and feature rich

Re: [OmniOS-discuss] Bug ?

On Thu, 29 Jun 2017, Guenther Alka wrote: ; Unless there are news regarding OmniOS my stance is ; ; - OmniOS 151022 is a freeze of current Illumos + LX. At the moment it is the ; most stable and feature rich free Illumos general use server distribution with ; the addition LX zones. As there is

Re: [OmniOS-discuss] Bug ?

s.omniti.com <mailto:omnios-discuss@lists.omniti.com>> *Subject:* Re: [OmniOS-discuss] Bug ? Unfortunately OmniTI no longer offers support contracts for OmniOS. We actually have a contract that's still good through I think November, but given their main support engin

Re: [OmniOS-discuss] Bug ?

nden: donderdag 29 juni 2017 22:13 > Aan: 'Guenther Alka' <a...@hfg-gmuend.de>; omnios-discuss@lists.omniti.com > Onderwerp: Re: [OmniOS-discuss] Bug ? > > > From: Guenther Alka > > Sent: Thursday, June 29, 2017 12:33 AM > > > > There are no signs from OmniTi to add

Re: [OmniOS-discuss] Bug ?

descent to death :-( -Oorspronkelijk bericht- Van: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] Namens Paul B. Henson Verzonden: donderdag 29 juni 2017 22:13 Aan: 'Guenther Alka' <a...@hfg-gmuend.de>; omnios-discuss@lists.omniti.com Onderwerp: Re: [OmniOS-discuss] Bug ? > F

Re: [OmniOS-discuss] Bug ?

.de>; omnios-discuss@lists.omniti.com Onderwerp: Re: [OmniOS-discuss] Bug ? > From: Guenther Alka > Sent: Thursday, June 29, 2017 12:33 AM > > There are no signs from OmniTi to add any fixes. An OmniTI person posted an intention to back port security fixes to r151022 for one

Re: [OmniOS-discuss] Bug ?

> From: Guenther Alka > Sent: Thursday, June 29, 2017 12:33 AM > > There are no signs from OmniTi to add any fixes. An OmniTI person posted an intention to back port security fixes to r151022 for one year, although I'm not sure whether that was under the auspices of OmniTI employment or just on

Re: [OmniOS-discuss] Bug ?

> From: Oliver Weinmann > Sent: Thursday, June 29, 2017 12:14 AM > > Ohh that is bad news. Yes, it was quite disappointing :(, I really liked OmniOS. > I have a productions system that somehow fails to join AD and I don’t know > what is causing this. We had a similar issue on our nexenta

Re: [OmniOS-discuss] Bug ?

Unless there are news regarding OmniOS my stance is - OmniOS 151022 is a freeze of current Illumos + LX. At the moment it is the most stable and feature rich free Illumos general use server distribution with the addition LX zones. As there is no repo and development outside OmniTi it is

Re: [OmniOS-discuss] Bug ?

mstadt, HRB 89231; Managing Director/Geschäftsführer: Sigmar Keller From: Paul B. Henson [mailto:hen...@acm.org] Sent: Donnerstag, 29. Juni 2017 08:51 To: Oliver Weinmann <oliver.weinm...@telespazio-vega.de> Cc: omnios-discuss <omnios-discuss@lists.omniti.com> Subject: Re: [O

Re: [OmniOS-discuss] Bug ?

Unfortunately OmniTI no longer offers support contracts for OmniOS. We actually have a contract that's still good through I think November, but given their main support engineer is no longer with the company and the OS appears to be in limbo at the moment I'm not sure what good that does us ;).

Re: [OmniOS-discuss] Bug 6569 r151020

> On Apr 1, 2017, at 12:07 PM, John Barfield wrote: > > Thanks for that! Add "-a" to that git branch: git branch -a --contains That way you don't have to check out every branch in your local repo. Dan ___

Re: [OmniOS-discuss] Bug 6569 r151020

Thanks for that! John Barfield Engineering and Stuff M: +1 (214) 425-0783 O: +1 (214) 506-8354 john.barfi...@bissinc.com 4925 Greenville Ave, Ste 900 Dallas, TX 75206 For Support Requests: http://support.bissinc.com or supp...@bissinc.com Follow us on

Re: [OmniOS-discuss] Bug 6569 r151020

This isn't make it in to 020. It will be in the 022, the next LTS. We plan to make an announcement on that soon regarding its availability. BTW, if you're curious if a specific commit is present in a particular branch in git, you can clone the repo and make sure the branches you're interested

Re: [OmniOS-discuss] [Bug] Installer crashes on disk selection

This is a known issue with the current installer. We're fixing this by replacing the installer for the next OmniOS release. Please track bloody for the upcoming installer change. If you can, boot off dhcp and use the Kayak PXE installer, which will form the basis of the new ISO one. Dan

Re: [OmniOS-discuss] Bug #6842 - is it in Omni stable yet?

> On Aug 16, 2016, at 8:41 AM, Lawrence Giam wrote: > > Hi All, > > I have been experiencing this bug quite a lot. Looking up and found that this > bug have been push up to illumos-gate and I would like to know if OmniOS have > got this implement in stable? > >

Re: [OmniOS-discuss] Bug #6842 - is it in Omni stable yet?

Hi! It looks like it's there on OmniOS 151014 (current LTS): https://github.com/omniti-labs/illumos-omnios/blob/r151014/usr/src/uts/common/fs/zfs/zap.c since the April, 21st update Release. See Release Notes here: https://omnios.omniti.com/wiki.php/ReleaseNotes/r151014 ...about "ZFS fixes for

Re: [OmniOS-discuss] bug in powertop

On Wed, Jun 10, 2015 at 7:12 PM, Michael Rasmussen m...@miras.org wrote: On Wed, 10 Jun 2015 17:04:20 +0100 Peter Tribble peter.trib...@gmail.com wrote: Delete that line in powertop.c and all should be well. FYI, I've looged illumos bug #6003 https://www.illumos.org/issues/6003 Do

Re: [OmniOS-discuss] bug in powertop

On Tue, 9 Jun 2015, Zach Malone wrote: This sounds like a libc or kernel change, but I can't imagine why it would show up on both 012 and 014. Maybe someone with a working build environment can dig further? I have read that powertop uses DTrace probes under Illumos. Does it link against a

Re: [OmniOS-discuss] bug in powertop

On Wed, 10 Jun 2015 09:34:03 -0500 (CDT) Bob Friesenhahn bfrie...@simple.dallas.tx.us wrote: I have read that powertop uses DTrace probes under Illumos. Does it link against a dtrace library? Has the interface changed? If it is linked dynamically to DTrace then you shouldn't see a

Re: [OmniOS-discuss] bug in powertop

On Tue, Jun 9, 2015 at 4:45 PM, Michael Rasmussen m...@miras.org wrote: Hi all, Anybody able to start powertop using some of the available options? root@nas:/root# powertop -d 1 Segmentation Fault (core dumped) Oh, that's bad. Look at:

Re: [OmniOS-discuss] bug in powertop

On Wed, 10 Jun 2015 17:04:20 +0100 Peter Tribble peter.trib...@gmail.com wrote: Delete that line in powertop.c and all should be well. Do I need to build the entire illumos-gate to recompile powertop? (I get the following as well: powertop: failed to compile P-states (frequencies) program

Re: [OmniOS-discuss] bug in powertop

I gave this a go on 151012 (014 isn't available as an AMI yet, and I can't get the 006 AMI to accept a ssh key pair on instance creation), and saw the same thing. powertop appears to segfault in string_to_decimal / libc.so.1. I then tried rebuilding powertop from the OmniTI illumos-gate build

Re: [OmniOS-discuss] Bug in pkg/server on OmniOS when the publisher name contains a dash

The OmniOS version of pkg(5) is a downstream of OpenIndiana's, which is in turn a downstream of Oracle's, but last synched in 2013 (because Oracle uses hg, and git from hg is annoying). Interesting, wasn't aware of that. So is it really just a matter of mercurial-git conversion, or

Re: [OmniOS-discuss] Bug in pkg/server on OmniOS when the publisher name contains a dash

On Apr 20, 2015, at 4:38 PM, Volker A. Brandt v...@bb-c.de wrote: Hi Dan! Dug through my mail, and I didn't see this note. I may have lost it, but gmail is usually good about not letting you get rid of mails. :( Well, I sent it to @omniti.com. My guess is you don't see any of my

Re: [OmniOS-discuss] Bug in pkg/server on OmniOS when the publisher name contains a dash

On Mon, Apr 20, 2015 at 4:38 PM, Volker A. Brandt v...@bb-c.de wrote: wonder if this bug was around a while, and that's why it's ms.omniti.com instead of omniti-ms, for example? Sounds likely. I wouldn't know. :-) I would know, as I was the one that chose it when I was at OmniTI. :) The

Re: [OmniOS-discuss] Bug in pkg/server on OmniOS when the publisher name contains a dash

As I understand it (someone please correct me if I'm wrong), we cannot use Oracle's pkg-gate unmodified, as it has dependencies on closed bits in Solaris for certain features. Those need to be stripped/modified for non-Solaris use, which is what OI has been maintaining in their fork, thanks

Re: [OmniOS-discuss] Bug in pkg/server on OmniOS when the publisher name contains a dash

Hi Dan! This is paraphrased from a mail that I had sent to Dan privately on March 31st. Unfortunately, the problem still persists in 151014. Dug through my mail, and I didn't see this note. I may have lost it, but gmail is usually good about not letting you get rid of mails. :(

Re: [OmniOS-discuss] Bug in pkg/server on OmniOS when the publisher name contains a dash

On Apr 20, 2015, at 1:11 PM, Volker A. Brandt v...@bb-c.de wrote: Hello all! This is paraphrased from a mail that I had sent to Dan privately on March 31st. Unfortunately, the problem still persists in 151014. Dug through my mail, and I didn't see this note. I may have lost it, but

Re: [OmniOS-discuss] Bug in omnios packaging

On Mon, Dec 8, 2014 at 8:29 AM, Jim Klimov j...@cos.ru wrote: Hi all, Found a small issue in some of the omnios (ms.omniti.com) packages: they include symlinks that point to the build-host's absolute paths, i.e.: # find /opt/omni -ls | grep tmp 122950 lrwxrwxrwx 1 root root

Re: [OmniOS-discuss] Bug in omnios packaging

On Mon, Dec 8, 2014 at 10:24 AM, Eric Sproul eric.spr...@circonus.com wrote: Haha... busted! Thanks for the bug report. For whatever reason, these compression tools all have very non-standard build procedures, and make all sorts of silly assumptions. We'll get it fixed. The fix was to make

Re: [OmniOS-discuss] Bug: OmniOS r151008j terminates iSCSI initiator too early in shutdown

| On 2014-03-07 21:49, Chris Siebenmann wrote: |In at least OmniOS r151008j, the iSCSI initiator and thus any iSCSI | disks it has established are shut down relatively early during a shutdown | or reboot. In specific they are terminated before halt et al runs | '/sbin/bootadm -ea

Re: [OmniOS-discuss] Bug: OmniOS r151008j terminates iSCSI initiator too early in shutdown

I wrote: | As far as I can tell from simply looking at things right now, even | an orderly shutdown on an OmniOS system will not avoid this. I should clarify that: 'on a normal, stock setup OmniOS system'. You can of course add SMF jobs to import and export ZFS pools and then shim them into the

Re: [OmniOS-discuss] Bug in 'zfs userspace -t ....'

https://www.illumos.org/issues/4208 Looks like it made it into 151008, and the fix hasn't yet. On Tue, Jan 28, 2014 at 3:34 PM, Chris Siebenmann c...@cs.toronto.edu wrote: zfs userspace -t type is documented as taking 'posixuser' as a type, and this is traditional Solaris 10 behavior. In