Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Richard Lowe]

The challenge of answering that is you often don't know the answer
until you see it

The ::stacks command will give you asummarized view of every kernel
thread's stack
the ::cpuinfo -v command will show you what the CPUs are doing now (or
were doing, before you got into kmdb).

Both or either might have a smoking gun of some kind, but it's hard to
predict what it might look like.

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

Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices

[Richard Lowe]

A good thing to do is to get into mdb when it's hung, and see where we
are with the ::stacks command.
https://illumos.org/books/dev/debugging.html has other tips.

I would add if you set the 1 bit of `moddebug` when you're in kmdb (I
think moddebug/W 8001 is verbose and stop on _init, but I tend to
forget), we will stop whenever a module `_init` is called, which can
be a good trick to try to narrow down where things might have gone
wrong if we don't respond to any means to get into kmdb.

More manually, an illumos version which works and one which doesn't
work will narrow down which illumos changes might have caused
problems.

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

Re: [OpenIndiana-discuss] Why are DOS executables being installed?

[Richard Lowe]

I don't know about python.  eventlog.dll is weird smb compatibility.
Gordon (cc'd) can probably fill you in on that.

-- Rich

On Tue, Jun 22, 2021, 16:32 Reginald Beardsley via openindiana-discuss <
openindiana-discuss@openindiana.org> wrote:

> I'm working on system image audit tools and found these in 2021.04.30:
>
> /usr/lib/python3.5/distutils/command/wininst-9.0-amd64.exe: DOS
> executable (EXE)
> /usr/lib/python3.5/distutils/command/wininst-9.0.exe:   DOS executable
> (EXE)
> /usr/lib/python3.5/distutils/command/wininst-8.0.exe:   DOS executable
> (EXE)
> /usr/lib/python3.5/distutils/command/wininst-14.0.exe:  DOS executable
> (EXE)
> /usr/lib/python3.5/distutils/command/wininst-6.0.exe:   DOS executable
> (EXE)
> /usr/lib/python3.5/distutils/command/wininst-10.0-amd64.exe:DOS
> executable (EXE)
> /usr/lib/python3.5/distutils/command/wininst-10.0.exe:  DOS executable
> (EXE)
> /usr/lib/python3.5/distutils/command/wininst-14.0-amd64.exe:DOS
> executable (EXE)
> /usr/lib/python3.5/vendor-packages/pip/_vendor/distlib/t32.exe: DOS
> executable (EXE)
> /usr/lib/python3.5/vendor-packages/pip/_vendor/distlib/t64.exe: DOS
> executable (EXE)
> /usr/lib/python3.5/vendor-packages/pip/_vendor/distlib/w64.exe: DOS
> executable (EXE)
> /usr/lib/python3.5/vendor-packages/pip/_vendor/distlib/w32.exe: DOS
> executable (EXE)
> /usr/lib/python3.5/vendor-packages/setuptools/gui.exe:  DOS executable
> (EXE)
> /usr/lib/python3.5/vendor-packages/setuptools/gui-32.exe:   DOS
> executable (EXE)
> /usr/lib/python3.5/vendor-packages/setuptools/gui-64.exe:   DOS
> executable (EXE)
> /usr/lib/python2.7/vendor-packages/setuptools/gui.exe:  DOS executable
> (EXE)
> /usr/lib/python2.7/vendor-packages/setuptools/gui-64.exe:   DOS
> executable (EXE)
> /usr/lib/python2.7/vendor-packages/setuptools/gui-32.exe:   DOS
> executable (EXE)
> /usr/lib/python2.7/vendor-packages/pip/_vendor/distlib/t32.exe: DOS
> executable (EXE)
> /usr/lib/python2.7/vendor-packages/pip/_vendor/distlib/t64.exe: DOS
> executable (EXE)
> /usr/lib/python2.7/vendor-packages/pip/_vendor/distlib/w64.exe: DOS
> executable (EXE)
> /usr/lib/python2.7/vendor-packages/pip/_vendor/distlib/w32.exe: DOS
> executable (EXE)
> /usr/lib/python2.7/distutils/command/wininst-6.0.exe:   DOS executable
> (EXE)
> /usr/lib/python2.7/distutils/command/wininst-8.0.exe:   DOS executable
> (EXE)
> /usr/lib/python2.7/distutils/command/wininst-9.0-amd64.exe: DOS
> executable (EXE)
> /usr/lib/python2.7/distutils/command/wininst-7.1.exe:   DOS executable
> (EXE)
> /usr/lib/python2.7/distutils/command/wininst-9.0.exe:   DOS executable
> (EXE)
> /usr/lib/python3.9/vendor-packages/pip/_vendor/distlib/t64.exe: DOS
> executable (EXE)
> /usr/lib/python3.9/vendor-packages/pip/_vendor/distlib/t32.exe: DOS
> executable (EXE)
> /usr/lib/python3.9/vendor-packages/pip/_vendor/distlib/w32.exe: DOS
> executable (EXE)
> /usr/lib/python3.9/vendor-packages/pip/_vendor/distlib/w64.exe: DOS
> executable (EXE)
> /usr/lib/python3.9/vendor-packages/setuptools/gui.exe:  DOS executable
> (EXE)
> /usr/lib/python3.9/vendor-packages/setuptools/gui-32.exe:   DOS
> executable (EXE)
> /usr/lib/python3.9/vendor-packages/setuptools/gui-64.exe:   DOS
> executable (EXE)
> /var/smb/cvol/windows/system32/eventlog.dll:DOS executable (EXE)
>
> Why are they there?
>
> Reg
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Some internals questions

[Richard Lowe]

On Thu, Apr 22, 2021, 08:40 Reginald Beardsley via openindiana-discuss <
openindiana-discuss@openindiana.org> wrote:

> Do kernel modules load in a consistent order?
>

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

Re: [OpenIndiana-discuss] safely cleanup pkg cache?

[Richard Lowe]

History is recorded for the user only.  If you don't use it you could purge
it.

Flushing the cache on success is fine too, anything it needs again will
just get redownloaded.
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] When this misery end?

[Richard Lowe]

The linker generates output of the same form as its input (32 or
64bit, x86 or sparc).  Anything happening other than that is happening
through the compiler front end.

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

Re: [OpenIndiana-discuss] Closed-Source Binary Blobs?

[Richard Lowe]

I filed 11466 remove old closed iconv tables
(https://www.illumos.org/issues/11466)
if someone wanted to take a crack at this.

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

Re: [OpenIndiana-discuss] Closed-Source Binary Blobs?

[Richard Lowe]

I think that might have been the case with the old closed iconv(1),
but we don't use that any longer.

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

Re: [OpenIndiana-discuss] Closed-Source Binary Blobs?

[Richard Lowe]

Ar Gwen, 5 Gorff 2019 am 03:27 Till Wegmüller 
ysgrifennodd:
> What I am wondering is what those iconv .t files are.

Sorry, I missed this.  I _think_ these are translation tables for a
keyboard driver.  Possibly a very very very ancient keyboard driver.
I do not know why they're still packaged.

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

Re: [OpenIndiana-discuss] Closed-Source Binary Blobs?

[Richard Lowe]

The relevant result of an illumos 'make closedbins' is:

closed-bits/kernel/drv/lsimega.conf
closed-bits/kernel/drv/usbser_edge.conf
closed-bits/kernel/drv/amd64/lsimega
closed-bits/kernel/drv/amd64/mpt
closed-bits/kernel/drv/amd64/adpu320
closed-bits/kernel/drv/amd64/atiatom
closed-bits/kernel/drv/amd64/marvell88sx
closed-bits/kernel/drv/amd64/bcm_sata
closed-bits/kernel/drv/amd64/sdpib
closed-bits/kernel/drv/amd64/acpi_toshiba
closed-bits/kernel/drv/amd64/intel_nhmex
closed-bits/kernel/drv/amd64/glm
closed-bits/kernel/drv/amd64/usbser_edge
closed-bits/kernel/drv/amd64/ixgb
closed-bits/kernel/drv/sdpib.conf
closed-bits/kernel/drv/intel_nhmex.conf
closed-bits/kernel/drv/adpu320.conf
closed-bits/kernel/drv/glm.conf
closed-bits/kernel/drv/mpt.conf
closed-bits/kernel/misc/scsi_vhci/amd64/scsi_vhci_f_asym_lsi
closed-bits/kernel/misc/scsi_vhci/amd64/scsi_vhci_f_asym_emc
closed-bits/kernel/misc/scsi_vhci/amd64/scsi_vhci_f_sym_emc
closed-bits/kernel/kmdb/amd64/mpt
closed-bits/kernel/kmdb/amd64/nfs
closed-bits/kernel/strmod/amd64/sdpib
closed-bits/lib/svc/manifest/network/ipsec/ike.xml
closed-bits/etc/security/tsol/label_encodings.example
closed-bits/etc/security/tsol/label_encodings.gfi.single
closed-bits/etc/security/tsol/label_encodings
closed-bits/etc/security/tsol/label_encodings.gfi.multi
closed-bits/etc/security/tsol/label_encodings.single
closed-bits/etc/security/tsol/label_encodings.multi
closed-bits/platform/i86pc/kernel/cpu/amd64/cpu_ms.GenuineIntel.6.46
closed-bits/platform/i86pc/kernel/cpu/amd64/cpu_ms.GenuineIntel.6.47
closed-bits/usr/sbin/chk_encodings
closed-bits/usr/xpg4/bin/more
closed-bits/usr/lib/amd64/libike.so.1
closed-bits/usr/lib/amd64/llib-like.ln
closed-bits/usr/lib/raidcfg/amd64/mpt.so.1
closed-bits/usr/lib/raidcfg/mpt.so.1
closed-bits/usr/lib/llib-like.ln
closed-bits/usr/lib/labeld
closed-bits/usr/lib/fwflash/verify/ses-SUN.so
closed-bits/usr/lib/libike.so.1
closed-bits/usr/lib/llib-like
closed-bits/usr/lib/inet/certdb
closed-bits/usr/lib/inet/amd64/in.iked
closed-bits/usr/lib/inet/certlocal
closed-bits/usr/lib/inet/certrldb
closed-bits/usr/lib/mdb/kvm/amd64/nfs.so
closed-bits/usr/lib/mdb/kvm/amd64/mpt.so
closed-bits/usr/lib/iconv/646en.8859.t
closed-bits/usr/lib/iconv/646de.8859.t
closed-bits/usr/lib/iconv/iconv_data
closed-bits/usr/lib/iconv/646it.8859.t
closed-bits/usr/lib/iconv/8859.646en.t
closed-bits/usr/lib/iconv/8859.646de.t
closed-bits/usr/lib/iconv/646da.8859.t
closed-bits/usr/lib/iconv/8859.646it.t
closed-bits/usr/lib/iconv/8859.646es.t
closed-bits/usr/lib/iconv/8859.646fr.t
closed-bits/usr/lib/iconv/8859.646sv.t
closed-bits/usr/lib/iconv/646es.8859.t
closed-bits/usr/lib/iconv/8859.646.t
closed-bits/usr/lib/iconv/8859.646da.t
closed-bits/usr/lib/iconv/646fr.8859.t
closed-bits/usr/lib/iconv/646sv.8859.t
closed-bits/usr/include/sys/lc_core.h
closed-bits/usr/include/sys/localedef.h
closed-bits/usr/bin/pax

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

Re: [OpenIndiana-discuss] PATH=/usr/xpg4/bin /bin/ksh -c "rm -f"

[Richard Lowe]

This ksh93 having over-many broken builtins thing has bitten people
before, especially this one which can cause problems in autoconf.

Do we have a bug filed to remove them?  We should.

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

Re: [OpenIndiana-discuss] /hipster: xargs coredumps

[Richard Lowe]

This version of illumos has the bad version of the fix for 8362 in it,
which we backed out yesterday.

Boot an old BE, update illumos again (presuming OI has rebuilt), and you'll
probably be ok.
-- 

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

Re: [OpenIndiana-discuss] Can't find /boot/zfsloader

[Richard Lowe]

Were there other messages prior to that one?  This might be the bug that I
encountered and Toomas (Cc'd) gave me a fix for.

On Thu, Feb 9, 2017 at 9:07 AM Dirk Willems  wrote:

> Hello OI,
>
> Today I want to switch over from my ubuntu desktop to OpenIndiana.
> But I experience some issue, I create a OI-gui usb and boot from the usb
> device and get following
>
> Can't find /boot/zfsloader
>
> illumos/x86 boot
> Default: disk0s1a:/boot/zfsloader
> boot:
>
> I already tried to change in the bios the boot prio to usb and manually
> set the first boot disk also on usb, but i keep having the same error.
>
> I also tried with the OI-text usb exactly the same error, then I created
> a OmniOS usb that one is booting like designed.
>
> Followed this site
>
> http://docs.openindiana.org/handbook/getting-started/#creating-a-hipster-usb-drive
>
> Any suggestions ?
>
> Thanks in advance.
>
> Kind Regards,
>
> Dirk
>
>
> --
>
> 
>
>
>
>
> **Dirk Willems* *
> System Engineer
>
>
>
> *+32 (0)3 443 12 38 <+32%203%20443%2012%2038>* 
>
>
>
> *dirk.will...@exitas.be* 
>
>
>
> *Veldkant 31 - 2550 Kontich* 
>
>
>
> *www.exitas.be* 
>
> *Disclaimer* 
>
> ___
> openindiana-discuss mailing list
> openindiana-discuss@openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
-- 

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

Re: [OpenIndiana-discuss] missing Description field in many IPS packages

[Richard Lowe]

Description fields are omitted when they would otherwise just duplicate the
summary.
-- 

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

Re: [OpenIndiana-discuss] What is this comment on Bug #372 supposed to mean???

[Richard Lowe]

I didn't think Milan was done updating JDS.  I'd assume someone is
very confused.  Especially since "Update to this other piece of
software" hardly resolves the bug in what _is_ shipping.

-- Rich

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

Re: [OpenIndiana-discuss] Unexplained system shutdown

[Richard Lowe]

Did the system reboot, or turn itself off?

If it rebooted:
  When it came back, did it say it panicked?
  Anything in 'fmadm faulty'?
  Does running 'savecore' produce a dump?

If it powered off:
  I have for a while had a suspicion that we may sometimes shut
ourselves down based on thermal info, and not actually say that we've
done it.  (I have seen a system actually take itself to the "press a
key to reboot" prompt, and not say why, for eg)

-- Rich

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

Re: [OpenIndiana-discuss] "strange" linking error

[Richard Lowe]

This looks a lot like: https://www.illumos.org/issues/3436  I have no
idea whether that fix is in OpenIndiana.  One workaround is to stop
using ld -r.

I have no idea what your build process is doing though, because it
appears to believe it's building an archive library, but is using ld
-r, so is actually building a relocatable object with a name ending
'.a'.  Someone, somewhere, is very confused...

-- Rich


2013/3/7 Apostolos Syropoulos :
> Hello,
>
> I have downloaded the latest version of live555 (http://www.live555.com/) and
> I tried to compile it using the config-solaris-64bit configuration. The 
> compilation
> process tries to create 4 static libraries which are created with a command of
> the form:
>
> ld -olibliveMedia.a -L. -64 -r -dn \
> Media.o MediaSource.o FramedSource.o 
>
> Three our of four libraries are created with no problem but for one linking 
> fails
> and gives
>
> ld: fatal: relocation error: R_AMD64_64: file AVIFileSink.o: section 
> [40].rela.eh_frame: symbol .text._ZN16SubsessionBufferD2Ev (section): symbol 
> has been discarded with discarded section: [16].text._ZN16SubsessionBufferD2Ev
> ld: fatal: relocation error: R_AMD64_64: file AVIFileSink.o: section 
> [40].rela.eh_frame: symbol .text._ZN16SubsessionBufferD0Ev (section): symbol 
> has been discarded with discarded section: [18].text._ZN16SubsessionBufferD0Ev
> make[1]: *** [libliveMedia.a] Error 1
>
>
> Before posting I used Google to see whether someone has experienced a similar
> problem, but I could not find anything. So, I am wondering whether anyone
> could provide some help and/or assistance.
>
> BTW, creating an archive with ar cru and ranlib works but the resulting
> library is useless.
>
>
> Regards,
>
> Apostolos
>
>
> --
> Apostolos Syropoulos
> Xanthi, Greece
> ___
> 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] "bad mutex" crash?

[Richard Lowe]

Ruled out what I was wondering.  I'd file an illumos bug describing
the configuration, etc, and make the crashdump available somehow.

-- Rich

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

Re: [OpenIndiana-discuss] "bad mutex" crash?

[Richard Lowe]

Sorry, you have to run savecore twice.

Once:

# savecore
should write out the vmdump.0

The second
# savecore -vf vmdump.0

Will extract it.

-- Rich

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

Re: [OpenIndiana-discuss] "bad mutex" crash?

[Richard Lowe]

If you save the dump (savecore), extract it (savecore -vf vmdump.0 -d
.), and run mdb (mdb unix.0 vmcore.0)
What does:

   f7f9a9c5::whatis

say?  The stack looks reasonable enough that I'm wondering if you have
a module loaded someone's stripped that's actually at fault, rather
than it being our fault and a damage stack.  If it says it's a 3rd
party module, I'd suggest reporting a bug to wherever it came from.
Otherwise, please file an illumos bug and make the crash dump
available (over http ideally)?

-- Rich

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

Re: [OpenIndiana-discuss] beadm broken - multiple active environments

[Richard Lowe]

Is there any possibility that you've cloned a zone onto that data pool?

zfs list -o 
name,org.opensolaris.libbe:parentbe,org.opensolaris.libbe:active,org.opensolaris.libbe:uuid

Would probably be useful output to see.  It's telling you what it
claims to be, that you have a single zone with multiple active root
datasets.  I would ignore the 'active' property at first, and look for
zones which have two datasets with the same parentbe, and then see
whether both are active.

It's probably not being particularly smarted about whether the dataset
is mounted, etc, etc, but it's hard to guess from the code precisely
what's up.

-- Rich

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

Re: [OpenIndiana-discuss] [oi-dev] adding aok=1 and set zfs_recover=1 to live CD's /etc/system as well?

[Richard Lowe]

Assertions are a necessary aid to debugging, do not disable them in a
default environment, be in the live CD or post-install environment.

-- Rich

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

Re: [OpenIndiana-discuss] installing boot driver

[Richard Lowe]

When you've installed the system, you should be able to install the
driver into the root we created (mounted at /a, I believe),
You then should be able to run add_drv -R /a ...
I think the bootarchive will be automatically recreated when you
reboot, but you could run bootadm update-archive -vR /a to be sure

-- Rich

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

Re: [OpenIndiana-discuss] error execv: Permission denied

[Richard Lowe]

The version of gcc 4.4.4 in a5 was packaged incorrectly, and as
botched file permissions.  Don't use it, use gcc-3.

Jon, any chance of getting this fixed before it bites more people?
(Also: is the package really 'gcc'? that's unfortunate, I thought it
was being kept to the side for the 151 builds?)

-- Rich

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

Re: [OpenIndiana-discuss] zpool upgrade in OI151a5?

[Richard Lowe]

On Wed, Jul 4, 2012 at 9:49 PM, Dan Swartzendruber  wrote:
> I downloaded a PDF on the new zfs feature flag stuff.  I'm not sure what
> 5000 means, but I'm not worried now.  I don't think I'll upgrade the data
> pool yet though.

5000 is an arbitrarily high number, to provide separation between the
two versioning schemes.

-- Rich

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

Re: [OpenIndiana-discuss] Options for a root filesystem

[Richard Lowe]

On Mon, Jun 25, 2012 at 10:37 PM, Gordon Ross  wrote:
> UFS root should still work, also NFS root (convenient for ZFS debug work:)
>

As concepts within illumos, yes.

With the full OI distribution, doubtful.

-- Rich

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

Re: [OpenIndiana-discuss] pkg: No image found.

[Richard Lowe]

That sounds like the pkg in the zone didn't get updated, and doesn't
speak the new image format (which the pkg in the GZ updated it to).

-- Rich

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

Re: [OpenIndiana-discuss] pkg: No image found

[Richard Lowe]

One possibility:
   One of the recent pre-stable updates came with an image format
update, which older pkg won't be able to read

Another possibility:
   The same update is umask-sensitive, so if you have a restrictive
umask, /var/pkg will become unreadable (making it 0755 again should
wake things up).

-- Rich

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

Re: [OpenIndiana-discuss] problem with no randomness provider // on even new laptops ( Dell )

[Richard Lowe]

Its almost certainly not even unsafe, it just means that due to the race we
needed random data in boot before we could have any.

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

Re: [OpenIndiana-discuss] strange reboot behavior: deadman timeout

[Richard Lowe]

If you get a crash dump, can you provide it?  Is this a machine with
an x2apic?  If it is, have you disabled it?
(there's at least one known issue with complete, solid, system hangs
on machines with x2apics).

That said, if you were triggering the deadman regardless something is
clearly wrong that _is not_ the x2apic issue, possibly in addition.
The crash dump would help, if you can't provide a crash dump for
whatever reason, it'd be nice to see the output of:

sudo savecore
sudo savecore -vf vmdump.0 # or .1, or .3 or whatever number the most
recent dump is
sudo mdb 0 # The same number as above

::stacks
::cycinfo -v
::cpuinfo -v

Though it's very likely this would not be useful without also having the dump.

-- Rich

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

Re: [OpenIndiana-discuss] System disk corruption

[Richard Lowe]

Vague recollection that the pool level is errors that weren't
recovered, so possibly two of them on the device were ditto'd
metadata?  (I'm very unsure on both counts).

Otherwise, as Chris said, iostat is particularly difficult to trust.
No matter what the error (even if, indeed, the drive or transport)
there's no guarantee (or in my bitter experience even likelyhood) of
formal errors occurring to go with the data being bad.

-- Rich

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

Re: [OpenIndiana-discuss] Please stop retrofitting packages to require live images

[Richard Lowe]

This happens, pretty much always, because something on which the
package depends would also be upgraded and _really does_ require a new
BE.

Do an install -nv, look at what would be changed.

I highly doubt anyone is adding reboot-needed to random packages.

-- Rich

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

Re: [OpenIndiana-discuss] onu broken today for oi_151a

[Richard Lowe]

the traditional reason to back publish or republish package/pkg has been to
fix bugs affecting upgrade, so this is intentional, though perhaps outdated.

Its not a bug anywhere, though it'd be nice if onu checked ahead of time
somehow to save trouble.

Workarounds.

- update pkg in the current BE.
- disable the openindiana publisher temporarily in the current be
(set-publisher -d)
- pkg -R /tmp/onu.* image-update -fto do the update by hand and the
activate the new BE.

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

Re: [OpenIndiana-discuss] distro_const package caching

[Richard Lowe]

The most foolproof way is to pkrecv the packages into a local repository
first

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

Re: [OpenIndiana-discuss] Matrox

[Richard Lowe]

constype will _always_ display vgatext for that board regardless of a
correctly configured X.  It's displaying the kernel driver attached to
the framebuffer which is driving the console, not the X driver.

The other response regarding explicit configuration, etc, is probably
the best way to figure out what is wrong with X.

-- Rich

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

Re: [OpenIndiana-discuss] SFE g++ and _RESTRICT_KYWD

[Richard Lowe]

That's a bug in spawn.h, already filed with illumos.

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

Re: [OpenIndiana-discuss] GCC Performance hit?

[Richard Lowe]

On Fri, Dec 9, 2011 at 07:32, Robar Philip  wrote:
>
> I’m not a chat room user so I’m wondering, has anyone looked into how much of 
> a performance hit (if any) illumos and OpenIndiana are going to take by 
> switching from Sun’s compilers to GCC?

Yes.

-- Rich

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

Re: [OpenIndiana-discuss] What advantages of KVM over Vbox

[Richard Lowe]

You need to have EPT, certainly.

Joshua and I did some work to make shadow paging work again on the
AMD, and got to the point where it did for he and I, but seemingly not
for anyone else :\  It'd be a good place to start for anyone wanting
to remove the EPT requirement though.

-- Rich

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

Re: [OpenIndiana-discuss] IO Throttling

[Richard Lowe]

On Fri, Nov 18, 2011 at 11:43, Geoff Flarity  wrote:
> Hi,
>
> Has the IO Throtting work that Joyent has done made it's way into
> Illumos/Open Indiana yet?

No.

> Is this on the horizon?

I'd like it, but there were a couple of performance concerns they were
trying to work out with the other ZFS folks.

-- Rich

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

Re: [OpenIndiana-discuss] OpenOffice on oi151a

[Richard Lowe]

Sun C 5.10 is Studio 12u1.  It seems to explicitly want something prior to that.
I don't have answers to any other part, but installing 12u1 shouldn't
help you at all, based on the above.

-- Rich

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

Re: [OpenIndiana-discuss] Unusual pkg error creating a zone

[Richard Lowe]

> Alas the patch didn't do the trick.  It looks like the problem is with
> packages from the OI repro:
>
> Creating Plan |pkg: No matching version of SUNWadmap can be installed:
> pkg://openindiana.org/SUNWadmap@0.5.11,5.11-0.151:20110912T025048Z: This
> version is excluded by installed incorporation
> pkg://openindiana.org/consolidation/install/install-incorporation@0.5.11,5.11-0.148:20101128T215402Z
>

So yes.  It looks like SUNWadmap is only in the OI repo at @0.151 (not
even 0.151.1)
I think what you're seeing is the fact that pkgcreatezone (In OI148)
uses the old package names, and in this case is tripping on its own
feet because of confusion in the package repository).

I think the workaround is going to be to replace the old SUNW names
with the new names, (you can use pkg info -r  to find them),
in this case it's system/management/sysidtool.

I honestly have no idea how SUNWadmap can be in the state it appears to be in.

-- Rich

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

Re: [OpenIndiana-discuss] Unusual pkg error creating a zone

[Richard Lowe]

On Sun, Sep 25, 2011 at 03:36, Ian Collins  wrote:
>  On 09/25/11 07:06 PM, Richard Lowe wrote:
>>
>> This might be #944 (https://www.illumos.org/issues/944), which has
>> symptoms that are remarkably annoying to track to their cause.
>>
> It could be, but I wonder why is happened today and not a couple of weeks
> ago when I created the other zones?
>
> Did you find a fix?
>

Fix is in the defect.opensolaris.org bug linked from that one.
I'm not sure it's the same issue, either, but the error (messages) it
causes are utterly nonsensical.  So it seemed worth ruling out.

-- Rich

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

Re: [OpenIndiana-discuss] Unusual pkg error creating a zone

[Richard Lowe]

This might be #944 (https://www.illumos.org/issues/944), which has
symptoms that are remarkably annoying to track to their cause.

-- Rich

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

Re: [OpenIndiana-discuss] OI 151a - where are man pages ?

[Richard Lowe]

On Wed, Sep 14, 2011 at 16:05, Cyril Plisko  wrote:
> cis:~$ pkg search zfs.1m
> INDEX      ACTION VALUE                      PACKAGE
> basename   file   usr/share/man/man1m/zfs.1m pkg:/system/manual@0.5.11-0.148
> cis:~$ pkg info system/manual
> pkg: info: no packages matching the following patterns you specified are
> installed on the system.  Try specifying -r to query remotely:
>
>        system/manual
> cis:~$ ls -l /usr/share/man/man1m/zfs.1m
> -r--r--r-- 1 root bin 101224 2011-09-12 14:48 /usr/share/man/man1m/zfs.1m
> cis:~$
>
> So, what package zfs.1m comes from ?

system/file-system/zfs.

I have no idea why pkg search is saying otherwise.

-- Rich

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

Re: [OpenIndiana-discuss] iprb and ncrs on 151a?

[Richard Lowe]

On Wed, Sep 14, 2011 at 10:36, Peter Tribble  wrote:
> So I thought I would try 151a on a test system I've had sitting around
> (it's a white-box pentium4 machine).
>
> Two issues I would like to sanity check before I submit bugs:
>
> 1. The network appears to be driven by iprb, and doesn't work. It plumbs, but
> I can't get any traffic, and DHCP can't get an address. (It works up to a 
> point,
> in that if I run a snoop I can see *some* packets, just not very many.)

That sounds like an iprb bug.

> 2. I've got a symbios 53c875 card (actually, several) in the box, and
> these don't
> get picked up at all. That was ncrs, right? Has that gone?

ncrs is gone, yes, (prior to the split, even).  Isn't that the driver
that lived on somewhat as glm? or am I confused?

-- Rich

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

Re: [OpenIndiana-discuss] OI 151a - where are man pages ?

[Richard Lowe]

Illumos folded our ones into the same packages as the software.

I thought OI followed, but a small number could have been misplaced.

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

Re: [OpenIndiana-discuss] ZFS normalization problem

[Richard Lowe]

The best thing to do is likely to file an illumos bug
(http://illumos.org/issues/illumos-gate) and possibly post to
develop...@lists.illumos.org.  I'm not sure what the overlap of this
list, zfs-code, and developers@ is.

-- Rich

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

Re: [OpenIndiana-discuss] Showing dependencies with "pkg info"

[Richard Lowe]

pkg contents -Ho fmri -t depend 

If the package isn't installed, you'll need to add '-r'
You can filter the type of dependency with '-a'

-- Rich

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

Re: [OpenIndiana-discuss] how does one disable zil in OI?

[Richard Lowe]

I think this got swallowed up by milek's work on making it an actual
interface, try:

  zfs set sync=disabled  (other values are "standard", and "always")

I suspect it may not have made it into the manual pages we currently have.

-- Rich

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

Re: [OpenIndiana-discuss] Stack not written error on install attempt

[Richard Lowe]

That's part of the messages you get if the systems panics prior to the dump
device being configured.

Boot with -kv added to the kernel$ line in the grub configuration (hit 'e'
to edit.) And it should stop in the debugger and give you time to read the
message.  The '$http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] Boot crash

[Richard Lowe]

If you're crashing, you want to add '-k' to the boot arguments as well
as -v, etc.  to load the debugger, which should give you time to read
panic messages etc.

If with -k it stops at the debugger, the most useful thing is probably
to include the panic-related output from the debugger's $ /mnt

Update the boot archive on it

   bootadm update-archive -vR /mnt

-- Rich

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

Re: [OpenIndiana-discuss] FD_SETSIZE

[Richard Lowe]

The rationale included the words "SPARC V9 ABI", if I recall
correctly.  It's not changing.

-- Rich

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

Re: [OpenIndiana-discuss] [illumos-Developer] Unable to boot OpenIndiana on my dell studio 1450

[Richard Lowe]

::cpuinfo and ::stacks would be good to see.

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

Re: [OpenIndiana-discuss] Tabs no longer expanded when cutting and pasting

[Richard Lowe]

If this is the change reflected in the termio TAB* setting, this also
breaks emacs TRAMP unless a
workaround is applied.
It's very annoying.

If it _is_, 'stty tab0' restores the behaviour you're wanting (per terminal)

-- Rich

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

Re: [OpenIndiana-discuss] why is OI- illumos based 148a 805mb

[Richard Lowe]

> We should probably slim the LiveCD down a bit. Presumably if we built 151a 
> consolidations,
> and used distro-const from 151a, we'd end up with a CD rather than a DVD.

I suspect the locale changes necessary for use with illumos may push
this around some.
I had wondered if the over-size was partly an artifact of having both
sets of locale packages
(I would expect other, negative, consequences of this).

Keeping a useful live media on a CD is a never-ending challenge.
A common cause of swelling is autoconf-using software finding new dependencies
and dragging them in (medialib was a common one).  A good way to track
this would be
to first compare the package lists of this media with reference media,
and if that doesn't
show up obvious problems, I think you're stuck comparing on-disk package sizes
(not fun to calculate).

-- Rich

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

Re: [OpenIndiana-discuss] equivalents for SUNWcryr/SUNWcry?

[Richard Lowe]

On Mon, Jan 31, 2011 at 12:51, Brett Dikeman  wrote:
> On Fri, Jan 28, 2011 at 4:43 PM, Richard Lowe  wrote:
>> You shouldn't need to do anything, the functionality formally provided by
>> SUNWcry* (the encryption kit) was
>> folded in the base OS a couple of years ago.
>>
>> Forcing an install would (I think) be a really bad idea.
>
> I meant force installing of Legato networker, not the SUNWcry*
> packages...is this what you meant as well?

Ah, no.  I thought you meant forcing an install of the old SUNWcry.  I
don't know about Networker.
If that's its only complaint, I think it should be ok, but it's just a guess.

-- Rich

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

Re: [OpenIndiana-discuss] equivalents for SUNWcryr/SUNWcry?

[Richard Lowe]

You shouldn't need to do anything, the functionality formally provided by
SUNWcry* (the encryption kit) was
folded in the base OS a couple of years ago.

Forcing an install would (I think) be a really bad idea.

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

Re: [OpenIndiana-discuss] oi_147 repo image?

[Richard Lowe]

> There does not appear to be a way to tell pkg
> "use exactly this version:timestamp".

I think the "pkg update" changes of Shawn's allow that, but I don't recall
when they landed.

Really I thought giving the full FMRI to"install" worked, though.

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

Re: [OpenIndiana-discuss] opensolaris b134b (/release) to openindiana b148

[Richard Lowe]

On Dec 24, 2010 11:07 AM, "Anil"  wrote:
>
> Cool, thanks. One more question for everyone?
>
> Is it safe to upgrade global zone from 2009.06 -> 134 -> 148, but
> upgrade the non-global zones from 2009.06 -> 148? (I am wondering if I
> can skip the intermediate upgrade to 134 for zones)

The global and non-global zones should always run matching software
versions.  I'm amazed this mismatch works.

> What exactly is the reason for the two step upgrade, what breaks?
>

The reason is a combination of paranoia, uncertainty with intervening
package renames and what's been tested.  Probably the upgrade would fail,
rather than it working but leaving stuff broken (it _may_ do that though,
it's just less likely)

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

Re: [OpenIndiana-discuss] about devlopment tools

[Richard Lowe]

On Sat, Dec 4, 2010 at 10:26 PM, Harry Putnam  wrote:
> But is there not a pkg with a collection of the basic dev tools?

developer/gnu should be there, I think

-- Rich

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