> On Jul 9, 2018, at 6:33 AM, Lawrence Giam wrote:
>
> Hi All,
>
> Can I check if Seagate 1200.2 (ST200FM0133) is supported by OmniOS R151014?
Even if OmniTI were still supporting OmniOS, r151014 would've been EOSLed by
now. See this old page:
> On Jun 14, 2018, at 3:04 AM, Oliver Weinmann wrote:
> I would be more than happy to use a zone instead of a full blown VM but since
> there is no ISCSI and NFS server support in a Zone I have to stick with the
> VM as we need NFS since the VM is also a datastore for a few VMs.
You rambled
On Mon, May 07, 2018 at 10:14:40AM -0400, Dan McDonald wrote:
> I'd guess I need a new root CA cert for OmniTI-MS. Where may I find this?
And the answer is: Use the old one:
https://github.com/omniosorg/omnios-build/tree/r151022/build/ca-bundle/files
Thanks Andy F. for reminding
You may have software installed dependent on a specific version of entire. I
can't tell you which one off the top of my head, but there are some well-known
offenders in the old ms.omniti.com repo.
Dan
___
OmniOS-discuss mailing list
Use the -lv flags for pkg list.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Feb 19, 2018, at 3:02 PM, Software Information
> wrote:
>
> Hi All
> I have been trying to understand the reason for an error I have been getting
> when I try to install a
Check the output of "pkg publisher" in both global and each lipkg zone. Maybe
you have one "omnios" publisher pointing to a different URL?
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
Curious... has anyone here in OmniOS-land run bloody or current-stable on
very recent Intel Skylake server hardware? For example:
https://www.supermicro.com/products/motherboard/Xeon/C620/X11DPi-NT.cfm
We're seeing some weirdness with SmartOS, and wanted to know if similar
weirdness was
On Mon, Jan 22, 2018 at 09:13:00PM -0500, Software Information wrote:
> Hi All
> I was just wondering. I recently updated my host machine from r151020 to
> r151022.
> The welcome message on the host machine is fine but when I log on to the
> non-global zone, I still see the welcome message for
I use NFS.
I either use automounter on MacOS (i.e. /net/server//...) or now that I
have Carbon Copy Cloner, I also use NFS URLs (nfs://server/), though I
set up distinct ZFS datasets for CCC.
I see problems occasionally, but less so as time has gone on. Seeing the
._filename files (where
I upgraded my HDC to OmniOSce r151024, and did some nightly builds. After
re-rewhacking PERL_VERS, I managed to get a MOSTLY clean build save for:
> Begin forwarded message:
>
> From: Dan McDonald <dan...@nowhere.kebe.com>
> Subject: Nightly i386 Build of illumos-gate Failed
> On Nov 4, 2017, at 4:04 PM, Bob Friesenhahn
> wrote:
>
> I have X11 (without twm installed) from pkgsrc which is enough to run and
> compile X11 programs. It is not clear to me if you want the server-side of
> X11, or want to use XDM, or if X11-client only
I apologize in advance for asking the community this in lieu of figuring it out
myself.
I wish to run "Just enough X" on OmniOS to run twm and xterm. Basically, I'd
like console windows for all of my zones readily available. I used to do this
when I ran OI on my home server, and occasionally
t; pkg: 0/1 catalogs successfully updated:
>
> http protocol error: code: 404 reason: Not Found
> URL:
> 'http://pkg.omniti.com/omnios/r151014/omnios/catalog/1/update.20170301T19Z.
>
>
> C' (happened 4 times)
>
> From:
> On Oct 28, 2017, at 3:18 PM, Machine Man wrote:
>
> Is this still online? I am not able to update my last two machines by change
> over to OpenSSH before upgrading to OmniOS CE r22.
I see:
http://pkg.omniti.com/omnios/r151014/
is giving me an appropriate
On Tue, Oct 10, 2017 at 09:39:59PM +, Jeff Stockett wrote:
> Tyan is making a new EPYC based server chassis that looks pretty slick (24
> hotswap U.2 nvme drives directly connected to the CPU - no PLX expanders
> required):
>
> http://tyan.com/Barebones_TN70AB8026_B8026T70AE24HR
Von: Peter Kelm
Betreff: Reminder & update: Oct 12 SmartOS/OmniOS/OI/illumos user meeting at
Erlangen, Germany
Datum: 3. Oktober 2017 um 11:43:25 MESZ
An: openindiana-discuss-ow...@openindiana.org,
smartos-disc...@lists.smartos.org, omnios-discuss@lists.omniti.com
Some of us still use omniti-ms for things. I know it's not a supported
publisher, but I'm curious about this Apache bug:
https://blog.fuzzing-project.org/60-Optionsbleed-HTTP-OPTIONS-method-can-leak-Apaches-server-memory.html
And whether or not the apache24 package will get a bump to fix this?
Peter asked me to forward this to the list.
Dan
=
Von: Peter Kelm >
Betreff: Invitation to the SmartOS/OmniOS/OI/illumos user meeting at Erlangen,
Germany on October 12
Datum: 15. September 2017 um 11:15:28 MESZ
An:
On Mon, Sep 11, 2017 at 06:27:12PM +0200, Sylvain Leroux wrote:
> I was asked about the supported architecture for OmniOSce.
>
> As far as I can tell, this was not mentioned on the
> http://www.omniosce.org website. So, I assume x86_64.
>
> But, I *think* OmniOS did support x86_32 too. Is this
On Fri, Sep 08, 2017 at 03:40:44PM +0100, David Ledger wrote:
>
> Knowing that certainly helps, thanks. Can I also ignore those online
> documents that say it’s all done by configurations within the svcs setup and
> that I need to disable one version of ipfilter and enable another?
I use stock
On Fri, Sep 08, 2017 at 03:21:30PM +0100, David Ledger wrote:
>
> We now need to set up a couple of zones that have their own subnet, but talk
> to the outside world through the global zone. These will need to be network
> isolated from the existing zones and with access controlled,
On Thu, Aug 31, 2017 at 02:43:46PM -0400, Linda Kateley wrote:
> All,
>
> Has anyone ever run into a case where ipadm details are persistent across
> reboot? I am seeing this intermittently in zones.
ipadm(1M) is SUPPOSED TO be persisten across reboots. Unless you specify
with -t.
Or are you
> On Aug 24, 2017, at 8:41 AM, Schweiss, Chip wrote:
>
> I just move one of my production systems to OmniOS CE 151022m from 151014 and
> my NFS performance has tanked.
>
> Here's a snapshot of nfssvrtop:
>
> 2017 Aug 24 07:34:39, load: 1.54, read: 5427 KB, swrite:
"beadm create newBEname"
Read the beadm(1M) man page for more details.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Aug 20, 2017, at 7:02 PM, Fábio Rabelo wrote:
>
> Hi to all
>
> There are a way to force the creation of a new boot environment ?
>
>
1.) Which OmniOS release? Make sure it's a recent one before drawing
conclusions.
2.) Have you queried the larger illumos mailing list? I know there are several
open NFSv4 issues still there, and if you have a reproducible test case, it may
be helpful.
Dan
MANY of the OmniTI-Ms packages have hard coded version dependencies (e.g. ONLY
r151014, not at least r151014). I tried to fix this, but many packages there
remained unbuilt to the new, looser, dependencies.
I'd remove ALL OmniTI-Ms packages before upgrading, and then put them back.
Dan
Sent
1022/ to
>>>> pkg.omniosce.org/r151022/core/ which is the mandatory step prior of the
>>>> final pkg update -rv command execution).
>>>>
>>>> Worth to mention that additional step on the
>>>> https://github.com/omniosorg/omnios-build/blo
You're sure you're on the very latest 014? Could be lack of updated
certificates...
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Jul 27, 2017, at 4:14 PM, Krzysztof Grzempa wrote:
>
> Guys,
> I will grab this thread as it is somehow similiar. I want to
Oops, should've read more carefully.
YES, bloody isn't signed. I often create an alternat BE First, mount it, then
use "pkg -R" to keep the original stable BE safe.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Jul 21, 2017, at 7:11 PM, Ryan Zezeski wrote:
>
In the past, bloody was never signed. Has CE changed that policy?
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Jul 21, 2017, at 7:11 PM, Ryan Zezeski wrote:
>
> Hey everyone,
>
> I've been trying to reproduce this but can't seem to get my omniosce
> onto
I have an OmniOS r151022 box. (You may have heard me talk about it from time
to time. :) ) Some of its zones use other publishers for some things. In
particular, the omniti-ms and niksula.hut.fi publishers.
Has anyone who's already made the jump done so and successfully continued to
use software
Thank you all for your efforts.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
I will later today forward a list from my notes (once I get settled in and can
punchin to home) of packages that I effectively froze because for some reason
or another, they couldn't be upgraded. There's a rash of version-bump upgrades
happening on the OmniOSce omnios-build repo, and some of
> On Jul 7, 2017, at 11:42 AM, Guenther Alka wrote:
>
> hello Dan
>
> Thanks for jumping in.
> You are the person with the very best insights in OmniOSand Illumos
> and propably OI. Can you please comment about the options to cooperate with
> OI.
>
> Is this doable and
> 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
Sending from kebe.com, as that's how I interact with OmniOS.
And again, SORRY for missing this upon r151022's release.
Dan
- Forwarded message from Dan McDonald <dan...@joyent.com> -
Date: Mon, 3 Jul 2017 09:33:20 -0400
From: Dan McDonald <dan...@joyent.com>
To: illum
> On Jul 1, 2017, at 4:59 AM, Oliver Weinmann
> wrote:
>
> Hi,
>
> We have a nexenta system and this has a few additional parameters for zfs
> send an receive. These do not exist on omnios or open Indiana. I found a very
> old feature request for this:
>
>
> On Jun 22, 2017, at 3:13 AM, Oliver Weinmann
> wrote:
>
> Hi,
>
> Don’t think so:
>
> svcs -vx rcapd
>
> shows nothing.
You're not looking for the right thing.
neuromancer(~)[0]% pgrep rcapd
340
neuromancer(~)[0]% svcs -a | grep cap
online
> On Jun 19, 2017, at 4:51 AM, Lawrence Giam wrote:
>
> Hi All,
>
> I am planning to get this SuperMicro server SSG-2028R-E1CR24L and I am
> wondering if there is any problem associated with Intel C612 chipset and
> Intel X540 Dual Port 10GBase-T?
>
> Planning to
It's like you're missing packages. Did you populate it with both
illumos-omnios AND omnios-build packages?
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
(1)# pkg update -rnv
pkg: 1/2 catalogs successfully updated:
1: http protocol error: Unknown error code: 404 reason: Not Found
URL:
'http://pkg.omniti.com/omniti-ms/ms.omniti.com/catalog/1/update.20170515T21Z.C'
2: http protocol error: Unknown error code: 404 reason: Not Found
URL:
> On Jun 6, 2017, at 9:47 PM, Paul B. Henson wrote:
>
> echo ::sd_state | mdb -k | egrep '(^un|_blocksize)'
Shit, you're right:
(2)# echo ::sd_state | mdb -k | egrep '(^un|_blocksize)'
un 0: ff0d0c58d9c0
un_sys_blocksize = 0x200
un_tgt_blocksize = 0x200
> On Jun 4, 2017, at 11:00 PM, Paul B. Henson wrote:
>
>>
>> And what does the "native" mean: is that "4kB physical AND 4kB logical
>> block size" as opposed to "4kB physical with 512B logical block size"?
>
> At this point I'm thinking the loader is only broken for disks
On Thu, Jun 01, 2017 at 01:01:49PM -0700, Paul B. Henson wrote:
> > From: Geoff Nordli
> > Sent: Tuesday, May 30, 2017 7:57 PM
> >
> > Right, it will not boot after upgrading to the new loader; even if the
> > 4K disks are not part of the rpool.
>
> Yikes 8-/, I'm glad I hadn't got around to
r151022 is out now. Please upgrade to that and see if the problem manifests.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
This is only a test.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
> On May 16, 2017, at 5:22 PM, Dan McDonald <dan...@omniti.com> wrote:
>
> The tests are collidy-enough where I'm running an illumos-omnios build before
> I push them. For now, let's assume it works and I push these upstream to the
> illumos-omnios repo.
The illumo
Found my first error
> On May 16, 2017, at 5:22 PM, Dan McDonald <dan...@omniti.com> wrote:
>
> YOUR HOMEWORK PART 0: Figure this out.
Correction: "Figure out whether or not illumos 7590 is worth a backport all by
itself."
Dan
_
> On May 16, 2017, at 10:53 AM, Alexander Lesle
> wrote:
>
> No NSA or U.S. laws pressure to code a backdoor for them.
As someone who worked in the shadow of such a threat for many years (Building
IPsec both at NRL, and pre-OpenSolaris Sun), the open-source nature
> On May 15, 2017, at 4:46 PM, Michael Rasmussen wrote:
>
> On Mon, 15 May 2017 07:37:35 +0200
> Michael Rasmussen wrote:
>
>> To follow example I will commit myself to maintain the wiki and any
>> other web based infrastructure the project may need and choose
hree years as
rewarding as I'd hoped they'd be when I joined OmniTI. And as for OmniTI, if
you need web or database consulting, please keep them in mind. Still a fan,
even though I'm no longer with them.
Dan McDonald -- OmniOS Engineering
___
Omni
> On May 11, 2017, at 5:11 AM, Ludovic Orban wrote:
>
> If my understanding of the LX code is correct, sysconf(_SC_CHILD_MAX) ends up
> being translated to lx_getrlimit() which would return the value of
> zone.max-lwps. Looks like an odd default to me, but I can't say for
> On May 9, 2017, at 4:40 PM, Schweiss, Chip wrote:
>
> Here's the screen shot:
Interesting.
So notice that the IP address in question is 10.28.17.29 (uggh, the leading-0
is a Mentat-ism we need to fix in -gate already). And notice that the other
node's MAC is
> On May 9, 2017, at 3:32 PM, Schweiss, Chip wrote:
>
> This was a first for me and extremely painful to locate.
>
> In the middle of the night between last Friday and Saturday, I started
> getting down alerts from most of my network. It took 4 engineers including
>
> On May 9, 2017, at 10:30 AM, Dan McDonald <dan...@omniti.com> wrote:
>
> When I get home I'll provide more details, but you should try bloody or still
> in beta r151022.
>
Well shoot. It appears I have pretty much the same problem in OmniOS bloody
(and therefore r151
When I get home I'll provide more details, but you should try bloody or still
in beta r151022.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On May 9, 2017, at 10:02 AM, Nahum Shalman wrote:
>
> As a data point, I tested this on a very recent SmartOS and was
I've updated bloody, and install media, today.
illumos-omnios is at d2ed2f2489, omnios-build is at b902717c6dc, both master
branches.
A few merges from upstream illumos, a few small LX fixes from Joyent, and a
bump of Mozilla-NSS to 3.30.2.
This master branch has been merged into r151022
For anyone using Debian in an LX zone...
Dan
> Begin forwarded message:
>
> From: "Christopher Horrell"
> Subject: Re: [smartos-discuss] Problem updating Debian 8.7 (jessie) zone
> Date: May 8, 2017 at 10:11:02 AM EDT
> To: SmartOs Discuss
First off, thanks to Andy Fiddaman, who discovered a problem with the DEBUG
packages in bloody.
I've pushed out new illumos-omnios packages for bloody on the repo server.
Most people won't strictly need to upgrade, because these only affected the
debug.illumos=true variant of these packages.
This update is almost entirely illumos-omnios driven.
uname -v says omnios-master-f88fa452c2, and illumos-omnios from master, commit
f88fa452c2, built this release.
Some bugfixes include:
- Install media were missing the "xhci" USB3 driver.
- Two older LX commits that I'd overlooked,
> On Apr 26, 2017, at 12:44 PM, Richard Skelton wrote:
>
> Hi,
> I am have a problem copying the stable repo:-(
>
> root@ml110:~# pkgrepo create /rpool/omnios/r151020
> root@ml110:~# pkgrecv -s http://pkg.omniti.com/omnios/r151020 -d
> /rpool/omnios/r151020 -m latest
> On Apr 26, 2017, at 11:34 AM, Jens Bauernfeind
> wrote:
>
> Do you used a real DVD or an ISO?
> For the future you could use the iso mount feature of HP ILOs so you save
> time to burn the iso and save blank cd/dvd.
> I see no reason to use a remote console
Sorry, I didn't read deeply enough. flowadm(1M) doesn't use establishment as a
flow limiter. I do wonder, though, if you couldn't use ipfilter to label
inbound SYN packets with a distinct diffserv number which flowadm CAN use for
limiting?
Dan
Sent from my iPhone (typos, autocorrect, and
Read up on flowadm(1M) - this is a better tool for rate limiting.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Apr 25, 2017, at 1:29 PM, Software Information
> wrote:
>
> Hi All
> I have been trying to find some ipfilter documentation that will show
> On Apr 24, 2017, at 10:09 AM, Dan McDonald <dan...@omniti.com> wrote:
>
> Is e1000g0 manually configured, or configured with DHCP?
I'd also suggest running and capturing the output of:
route -n monitor
on the zone you have e
> On Apr 24, 2017, at 4:34 AM, Michael Mounteney wrote:
>
> What seems to happen is that e1000g0 goes down entirely so that, as
> previously mentioned, not even "ping 89.16.167.134" works, but if you
> Esc on the web page so that it doesn't keep trying to send traffic,
>
Hello!
I've updated all of the omnios-build packages for bloody, in anticipation of
getting r151022 ready for a release sometime in May. There's still some
debugging to do for r151022 (and some PRs to accept), and a couple of more
illumos merges, but with this update we have several new
> On Apr 20, 2017, at 12:24 PM, Volker A. Brandt wrote:
>
> So the abomination will live on. Sigh...
You can engage them via t...@iana.org, y'know. :)
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
> On Apr 20, 2017, at 11:52 AM, Jens Bauernfeind
> wrote:
>
> Hello all,
>
> I thought that adding a menu for the timezone selection might be an idea.
> As I wrote to Dan, it uses tzselect(1M) instead of entering the $TZ
> manually.
>
> It's only a little
ENOCAFFEINE -- it's not because of entire or OmniOS-userland.
I'll investigate this more when I get back from the Dr.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Apr 20, 2017, at 8:24 AM, Dan McDonald <dan...@omniti.com> wrote:
>
> I have to push out entire and
No EPOLL in r151014:
commit a5eb7107f06a6e23e8e77e8d3a84c1ff90a73ac6
Author: Bryan Cantrill
Date: Sat Feb 14 16:55:35 2015 -0800
5640 want epoll support
Reviewed by: Jerry Jelinek
Reviewed by: Robert Mustacchi
I'd recommend snoop -o on your NAT box/zone.
I tried your steps, and did not see this problem. My NAT is more
sophisticated, servicing both my home and a work-from-home segment for OmniTI,
which was where I tried your reproduction. NO idea what might've happened.
Are you yourself in
> On Apr 16, 2017, at 7:37 PM, Jens Bauernfeind
> wrote:
>
> Hello,
>
> is this normal behaviour?
> r151021-20170405.iso
> Platform: VMware Workstation Player 12.5.5-5234757 on latest CentOS7
> OS: Solaris 11 64bit
> 4GB RAM
> 2 CPU
> 30GB vDisk
I have seen
That woz was the result of zpool split is news to me (or I missed it, in which
case I apologize).
I wonder if a toy test with files ala the zfs test suite can reproduce this?
- create 3-way mirror
- zdb
- split one disk
- zdb original and split-created pool
Adding illumos zfs list.
Dan
Sent
> On Apr 14, 2017, at 6:20 AM, Guenther Alka wrote:
>
> I found a strange behaviour with the newest 151021 when I tried to setup on
> ESXi 6.5
>
> I created a new VM (Solaris 11-64) with a DVD device connected to the OS
> .iso.
> On first boot of the VM, the ESXi web
We've changed the code-signing regimen for OmniOS r151022. To that end, if you
want to be able to upgrade to r151022, you will need to update your "ca-bundle"
package to include the new root CA certificates.
Normally we don't update obsoleted release, but in the spirit of allowing any
It appears there's an additional requirement -- Active Directory. :(. The
/dev/random check happens in the join_domain() function of kclient.
Thanks and sorry,
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Apr 12, 2017, at 11:43 AM, Dan McDonald <dan...@omniti.com&
Does anyone have:
* Working kerberos infrastructure
* A non-global zone in which they can test kclient(1M)?
If so, please contact me off-list.
Thanks,
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
> On Apr 7, 2017, at 8:26 PM, John Barfield wrote:
>
> Greetings,
>
> I just want to report that after a clean istall of r151020 I found a bug
> whereby importing an older zpool from r151012 and running zpool upgrade
> causes an SSD cache device size to be reported
> On Apr 6, 2017, at 2:16 PM, Software Information
> wrote:
>
> Hi All
> Just trying to understand how some services work under OmniOS. Please help me
> to understand this. I have build omnios-r151020-4151d05 and I am running a
> Git Server in a zone. I used
> On Apr 5, 2017, at 1:52 PM, Michael Rasmussen wrote:
>
> I prefer using stdout for a broader usage scenario leaving
> decision where to output to the invoker.
>
> What do you think?
I think that's what I had in mind. :)
Thanks!
Dan
> On Apr 3, 2017, at 4:56 PM, Michael Rasmussen wrote:
>
> Btw. What do you exactly mean by 'modified to scribble commands
> into /mnt/.initialboot' ?
Sorry for not getting back to this sooner.
You have an interactive setup. It then invokes certain commands like "ipadm
Now that linked-image zones don't necessarily update from global without the
"-r" flag, we DO need to tag certain packages as "MUST ALWAYS UPGRADE" because
they have dependencies on the kernel or other global-zone goodies.
Rich Lowe brought this to my attention a long while back, and now it's
OmniTI would like to hear from OmniOS users. We have a survey that we'd
appreciate you taking.
There's no extra automatic emails that will result from taking this survey.
Here's the link:
https://www.surveymonkey.com/r/omnios
Please take the survey before May 5th.
Thanks,
Dan
A new bloody update is out. All media has been updated, as has the upstream
repo server.
REMINDER: OmniOS repo servers can & should be accessed via https URLs from now
on. Just as an extra level of protection. This will also be true for r151022
when it ships.
"uname -v" shows
I would like you to go into your zones, and patch THEIR version of
/usr/sbin/shutdown thusly:
--- /usr/sbin/shutdown Fri Apr 22 16:36:43 2016
+++ /zones/lipkg0/root/usr/sbin/shutdownMon Apr 3 17:54:24 2017
@@ -228,7 +228,9 @@
if [ "$pid1" ] || [ "$pid2" ]
then
- /usr/bin/kill
> On Apr 3, 2017, at 4:11 PM, Frank Boeye wrote:
>
> Do I need to specify an old repository or publisher first again then?
Yes. Sorry for not being clear about that. You need to go back to the 006
publisher and get it all-the-way updated.
Dan
> On Apr 3, 2017, at 3:38 PM, Bob Friesenhahn
> wrote:
>
> It does not seem that you obtained the same initial error message ("failed to
> open console master: Device busy") that I always do.
When it fails, I *DO* see this.
Apr 3 15:22:16 bloody
> On Apr 3, 2017, at 3:18 PM, Dan McDonald <dan...@omniti.com> wrote:
>
> AND THINGS GET WEIRDER.
>
> After the failure I documented earlier, I went off to do something else.
> When I came back, the zsched process was gone, and the zone appeared to be
> properly
> On Apr 3, 2017, at 2:59 PM, Dan McDonald <dan...@omniti.com> wrote:
>
> Okay. I will be diving into this now to see WTF happened. I'm sorry for not
> paying closer attention to this sooner.
AND THINGS GET WEIRDER.
After the failure I documented earlier, I went off to
> On Apr 3, 2017, at 2:11 PM, Bob Friesenhahn
> wrote:
>
> The problem is definintely with zone 'shutdown'. I have never seen it happen
> with 'reboot' or 'halt'.
Which does go through the inittab things.
I've found something. I can reproduce this on bloody
I see the problem...
> On Apr 3, 2017, at 1:47 PM, Frank Boeye wrote:
>
> pkg contents -m runtime/perl/manual
>
> set name=pkg.fmri
> value=pkg://omnios/runtime/perl/manual@5.16.1,5.11-0.151006:20130507T191120Z
> set name=pkg.summary value="Perl 5.16.1 Programming Language
> On Apr 3, 2017, at 1:40 PM, Bob Friesenhahn
> wrote:
>
> The common theme is always the first message "failed to open console master:
> Device busy". The failure to unmount filesystems is new to me.
That could be something from the LX code, but I'm not seeing
> On Apr 3, 2017, at 12:01 PM, Michael Rasmussen wrote:
>
> I will make a new version later today which supports command line. Do
> you need the file attached here or can you live with that you have to
> fetch it from git?
Git is fine assuming the URL you mentioned earlier is
Dumb question: Do you have any non-OmniOS publishers like ms.omniti.com on
this installation? If so, let's see if one of those is incorporate-blocking
you.
If not, you could try, thought this will produce more output:
pkg update -v --be-name=omnios-r151014 entire@11,5.11-0.151014
> On Apr 2, 2017, at 7:07 PM, Bob Friesenhahn
> wrote:
>
> Previously I reported a problem (in the 040 timeframe) in that zones are
> hanging when being shut down. Problems continue on that system. Today I am
> seeing the same issue with a different OmniOS
I'll need to take a look at this in depth.
Our preferred license is CDDL. Take a look at the prototypes directory for
sample headers for each:
https://github.com/omniti-labs/illumos-omnios/tree/master/usr/src/prototypes/
One thing about this, and I need to try it of course, is
> 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
___
> On Mar 30, 2017, at 5:11 PM, Brian Hechinger wrote:
>
> I'd like to see a way that network configuration can be disabled from within
> the zone so that it's set by the host admin and not the zone admin (assuming
> they are different people).
I thought more people would
> On Mar 30, 2017, at 5:02 PM, Bob Friesenhahn <bfrie...@simple.dallas.tx.us>
> wrote:
>
> On Thu, 30 Mar 2017, Dan McDonald wrote:
>
>>
>>> On Mar 30, 2017, at 4:26 PM, Bob Friesenhahn <bfrie...@simple.dallas.tx.us>
>>> wrote:
>
1 - 100 of 1141 matches
Mail list logo