[OpenIndiana-discuss] OI updates
I've just pushed a collection of illumos-gate CVE fixes for a9. This covers: - 5378 CVE-2014-3158 ppp: integer overflow in option parsing - 5480 CVE-2012-3165 mailx(1) buffer overflow vulnerability - 5481 CVE-2012-1750 mailx(1) tilde expansion vulnerability - 5853 pfexec_call() error handling could be improved 5854 pfexecd should initialize pfexec response buffers (Not sure what CVE this actually was assigned.) I've also pushed the NVIDIA driver update to 304.125 and the missing pieces of the Delphix vmxnet3s driver patchset. The new packages are: SUNWcs@0.5.11,5.11-0.151.1.9:20150504T114725Z system/network/ppp@0.5.11,5.11-0.151.1.9:20150504T120317Z consolidation/nvidia/nvidia-incorporation@0.5.11,5.11-0.151.1.9:20150504T113748Z driver/graphics/nvidia@0.304.125,5.11-0.151.1.9:20150504T113958Z driver/network/vmxnet3s@0.5.11,5.11-0.151.1.9:20150504T114139Z For those interested in an up to date OI branded illumos-gate, I've finished getting the OI patches done so anyone wishing to work with that can grab it here: https://github.com/OpenIndiana/illumos-gate That should build fine with GCC on hipster. If you build it with Studio on a9 you'll get a warning about clog (https://www.illumos.org/issues/5353) and warnings about pointers that can be fixed with https://paste.ec/paste/sDXMLQXR#DnPbnxkm9tFNmX0WxH1rWdV6CjIpGRmcKwfP2HOCgFE I've deliberately left out any broadcom patches that we had as there seems to be a mishmash of patches around from various sources and it's better for everyone if people look and work against upstream illumos-gate. Regards, Jon ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Fwd: [discuss] IPv6 bogus Router Advertisements and Illumos 5729
Forwarded Message
Subject: [discuss] IPv6 bogus Router Advertisements and Illumos 5729
Date: Fri, 27 Mar 2015 14:51:26 -0400
From: Dan McDonald dan...@omniti.com
Reply-To: disc...@lists.illumos.org
To: Dan McDonald dan...@omniti.com
Hello folks!
This is being sent to the illumos developers' list, the illumos
discussion list, and the OmniOS discussion list. I'd appreciate if
folks from other distros please forward this to your appropriate distro
mailing list(s). This mail assumes a mild working knowledge of IPv6 and
of the illumos kernel's internal structures. If you have questions,
feel free to contact me. The bottom line is we have nothing to worry
about! The rest of this note explains why.
Recently, I pushed this seemingly innocuous fix into illumos-gate:
commit a36f6bde69ea4d4ea2b0a475ce962b9c1c4ef323
Author: Dan McDonald dan...@omniti.com
Date: Thu Mar 19 19:04:20 2015 -0400
5729 in.ndpd should log broken RAs
Reviewed by: Robert Mustacchi r...@joyent.com
Approved by: Gordon Ross gordon.w.r...@gmail.com
I did so in response to a no-longer-embargoed request from CERT. The
problem behavior manifests with a malicious on-link IPv6 attacker who
can theoretically cause nodes to lower their default IPv6 hop limit
(like IPv4's TTL) to a small enough amount where IPv6 packets get
dropped before they reach their destinations.
This attack does not affect illumos, nor has it ever since its 2010
inception. This is due to our unusual STORAGE of IPv6 Router
Advertisement hop limits, vs. where we actually set these defaults.
Our in.ndpd code sends a SIOCLIFLNKINFO ioctl to the kernel in response
to a changed hop limit via a Router Advertisement. Fortunately, our
kernel stores this information in an ill_t's ill_max_hops. To see
these, per-interface, utter this as root on your system's global zone:
echo ::walk ill | ::print ill_t ill_name ill_isv6 ill_max_hops | mdb -k
The default value is 0, meaning use a system default. The good news
is, the value is NEVER USED BY THE REST OF THE IPv6 STACK. IPv6 instead
always sets the hopcount for locally-originated, non-reflective, packets
to whatever these ndd(1M) variables are set, per netstack:
ndd -get /dev/{tcp,udp,icmp} {tcp,udp,icmp}_ipv6_hoplimit
You can use the above mdb(1) walker to see if one of your subnets has
been subject to lower IPv6 hoplimits via Router Advertisements. An RA
message with that field set to 0 means don't change, and that's what
usually is sent. If it's set to any other of 1-255, the ill_max_hops
field will reflect the most recent receipt of this. If you have
multiple nics on multiple subnets (zoned or non-zoned) you may see
varying values.
Apparently some other platforms act on RA hop limits more aggressively
than illumos does. They are fixing this problem. Starting with the fix
for 5729, we are more vocal about seeing such RA hop limits, and have
mdb -p `pgrep in.ndpd` tunable globals to help sysadmins detect such
oddness.
I will now quote from CERT:
--
Essentially, RFC 3756 https://www.ietf.org/rfc/rfc3756.txt Section 4.4
lists some possible attacks that can be done regarding router discovery
operations in IPv6. The reporter's attack appears to be a variant of
these already well-known attacks. This fake RA attack in IPv6 has been
compared to ARP poisoning in IPv4. In other words, this is a known
problem due to rogue nodes on an internal network, and likely not a
severe software vulnerability as originally thought. CERT/CC thanks
vendors that helped provide this analysis.
Furthermore, this information was also submitted by the reporter to
several public mailing lists before contacting us. For example, see
discussion is available at http://patchwork.ozlabs.org/patch/453995/
and http://www.spinics.net/lists/netdev/msg322327.html. Therefore,
information on this patch is already fairly public at this point.
Given the circumstances, we will therefore remove our embargo, and allow
vendors to address this issue more publicly if desired.
--
So if you see a CERT notice about IPv6 Router Advertisements and hop
limits appear in the near future, you know that I've already performed
our due diligence on this account.
For the record, I'm now officially a CERT point of contact, so I see
things like this occasionally. I hope to do right by illumos with this
responsibility. In the future, if I have a problem that I need help
with, I know I can count on the community to help. (Some of you already
have helped, and without throwing you under the bus, THANK YOU!)
Happy IPv6-ing!
Dan McDonald -- OmniOS Engineering
---
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed:
https://www.listbox.com/member/archive/rss/182180/21175678-99894f87
Modify Your Subscription:
https://www.listbox.com/member/?member_id=21175678id_secret=21175678-1feae7e9
Re: [OpenIndiana-discuss] Reject: pkg://openindiana.org/consolidation .... How to upgrade from oi_151a8 to oi_151a9
Hi Stephan, The error says you have set SFE as sticky. You need to pkg set-publisher --non-sticky sfe Jon From: Stefan Everhartz x11...@unitybox.de To: Discussion list for OpenIndiana openindiana-discuss@openindiana.org Sent: Friday, 14 February 2014, 11:13 Subject: [OpenIndiana-discuss] Reject: pkg://openindiana.org/consolidation How to upgrade from oi_151a8 to oi_151a9 Is there a way to upgrade oi to the latest version if some newer packages are already installed from publisher 'sfe' ? # pfexec pkg refresh --full pfexec pkg image-update -vn Creating Plan / pkg update: No solution was found to satisfy constraints Plan Creation: Package solver has not found a solution to update to latest available versions. This may indicate an overly constrained set of packages are installed. latest incorporations: pkg://openindiana.org/consolidation/sunpro/sunpro-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/ips/ips-incorporation@0.5.11,5.11-0.151.1.9:20140117T204511Z pkg://openindiana.org/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151.1.9:20140117T204515Z pkg://openindiana.org/entire@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/cacao/cacao-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/hcts/hcts-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/sfw/sfw-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/solaris_re/solaris_re-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/sic_team/sic_team-incorporation@0.5.11,5.11-0.151.1.9:20140117T204518Z pkg://openindiana.org/consolidation/xvm/xvm-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/man/man-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/gnome_l10n/gnome_l10n-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/install/install-incorporation@0.5.11,5.11-0.151.1.9:20140117T204510Z pkg://openindiana.org/consolidation/cns/cns-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/jdmk/jdmk-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/cde/cde-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/nvidia/nvidia-incorporation@0.5.11,5.11-0.151.1.9:20140117T204514Z pkg://openindiana.org/consolidation/admin/admin-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/l10n/l10n-incorporation@0.5.11,5.11-0.151.1.9:20140117T204512Z pkg://openindiana.org/consolidation/X/X-incorporation@0.5.11,5.11-0.151.1.9:20140117T204519Z pkg://openindiana.org/consolidation/gfx/gfx-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/nspg/nspg-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z pkg://openindiana.org/consolidation/SunVTS/SunVTS-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z The following indicates why the system cannot update to the latest version: No suitable version of required package pkg://openindiana.org/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z found: Reject: pkg://openindiana.org/consolidation/gnome/gnome-incorporation@0.5.11,5.11-0.151.1.9:20140117T203708Z Reason: All versions matching 'incorporate' dependency pkg:/gnome/gnome-panel@0.5.11,5.11-0.151.1.9 are rejected Reject: pkg://openindiana.org/gnome/gnome-panel@0.5.11,5.11-0.151.1.9:20140117T202331Z Reason: All versions matching 'require' dependency pkg:/library/audio/gstreamer@0.5.11,5.11-0.151.1.9 are rejected Reject: pkg://openindiana.org/library/audio/gstreamer@0.5.11,5.11-0.151.1.9:20140117T202446Z Reason: All versions matching 'require' dependency pkg:/system/library/orc@0.5.11,5.11-0.151.1.9 are rejected Reject: pkg://openindiana.org/system/library/orc@0.5.11,5.11-0.151.1.9:20140117T203342Z Reason: Currently installed package 'system/library/orc' is from sticky publisher 'sfe'. No suitable version of required package pkg://openindiana.org/gnome/file-manager/nautilus@0.5.11,5.11-0.151.1.9:20140117T202321Z found: Reject: pkg://openindiana.org/gnome/file-manager/nautilus@0.5.11,5.11-0.151.1.9:20140117T202321Z Reason: All versions matching 'require' dependency pkg:/gnome/gnome-panel@0.5.11,5.11-0.151.1.9 are rejected Reject: pkg://openindiana.org/gnome/gnome-panel@0.5.11,5.11-0.151.1.9:20140117T202331Z Reason: All versions matching 'require' dependency
Re: [OpenIndiana-discuss] Upgrade to oi_151a8 fails on one machine
For debugging updates use the process here: http://wiki.openindiana.org/oi/Troubleshooting+image-update+failures - Original Message - From: Carl Brewer c...@bl.echidna.id.au To: openindiana-discuss@openindiana.org Cc: Sent: Wednesday, 14 August 2013, 1:01 Subject: Re: [OpenIndiana-discuss] Upgrade to oi_151a8 fails on one machine On 14/08/2013 8:36 AM, Gary Mills wrote: The first machine upgraded from oi_151a7 to oi_151a8 with no problems. The command I used was: pkg image-update --be-name oi_151a8 . It updated 879 packages into a new BE. It looked good when I rebooted into that BE. The second gave me trouble. I used the same command, but it only updated 37 packages. When I rebooted into the new BE, the kernel version was still oi_151a7 . I rebooted back to the old BE and destroyed the new one. In October, I had upgraded this second machine from oi_151a5 to oi_151a7, with no problems. It updated 947 packages that time. I did notice that the package `entire' was missing on the second machine, although it was present on the first one. I had been upgrading this second machine periodically, starting with opensolaris-126 . I suppose I must have removed `entire' somewhere along the way. Perhaps that was the cause of the problem, but why did the upgrade to oi_151a7 succeed? I tried adding the correct version of `entire' for oi_151a7, in a new BE, but `pkg image-update -n' still told me it would update only 37 packages. What could be preventing this upgrade from working? What should I do next? I don't know, but I have seen the same problem. I have two OI boxes, one is old (dates back to OS 90 or something ... 5 years or so and has been updated many, many times through pkg image-updates) and the other was built with OI 151a7 a few months ago. The old one displayed the same problem you describe, the new one was fine. I had made the new one a hipster version in the mean time though, and then pulled it back to 151a8 dev release three days ago. ___ 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] Workaround for Flash Plugin using older one
I found a version that works with FF19 and FF22 (22 had other issues like non-collapsing right-click menus) but it's at work so will post tomorrow. Did work for youtube and last.fm though. The version that works for me currently is 10.1.85.3 from fp_10.1.85.3_and_9.0.283_archive.zip available from Adobe's archive. Firefox reports it as Shockwave Flash 10.1 r85 md5sum... 7672ff843863fb00d8618d7245879472 libflashplayer.so JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Workaround for Flash Plugin using older one
On 14/07/2013 19:20, Udo Grabowski (IMK) wrote: On 09/07/2013 16:51, Udo Grabowski (IMK) wrote: On 09/07/2013 16:12, Paolo Marcheschi wrote: Hi I found a workaround for flash plugin in order to see youtube and other flash sites, I used the archived flashplayer10_1r53_64_solaris_x86.tar.bz2 from http://fpdownload.macromedia.com/get/flashplayer/installers/archive/fp10.1_archive.zip remove the newest plugin, and copy the old one in .mozilla/plugins folder. use the r53 instead of the r82, because the r82 does not work on other sites (i.e. grooveshark) to avoid activate the plugin every time follow this guide: http://mzl.la/R7DD9y I Hope this helps. It does, thanks for the research. Actually, the 10.1r53 was the most stable working horse of crashplayer before we switched to 11.1. Of course, that version is also vulnerable, as far as this has any practical relevance on non-Windows systems... ... No it does not, the r53 is actually a r82 (they don't archive severely vulnerable versions, but overwrite them silently). Instead of youtube, most videos on Dailymotion are now broken, and in general this version is very unstable. Did a check on later versions, but none of them work with hipster. So this problem is not fixed with that workaround, just shifted around. I found a version that works with FF19 and FF22 (22 had other issues like non-collapsing right-click menus) but it's at work so will post tomorrow. Did work for youtube and last.fm though. JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] gnome-terminal fails
On 12/07/2013 21:39, Udo Grabowski (IMK) wrote: On 12/07/2013 20:10, Milan Jurik wrote: Hi, I can reproduce it on my JDS build on top of OI. I hope to find some time to look at its code for fix. Log the bug, please. Done, see https://www.illumos.org/issues/3883 Is anyone seeing issues with Ctrl+left mouse click no longer working with URLs in gnome-terminal in hipster? JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Problems with dbus / Orbit
Do you have dbus-x11 installed? JT On 07/07/2013 15:36, Udo Grabowski (IMK) wrote: On 07/07/2013 12:37, Udo Grabowski (IMK) wrote: Openindiana 157a8 hipster, fresh update from a7: I'm totally lost, after a premature Ctrl-C on a pfexec packagemanager, I cannot start it anymore in pfexec mode (local machine, no NFS): ~: pfexec packagemanager GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: @@@ Failed to get connection to session: Unable to autolaunch when setuid) @@@ ... Segmentation fault I'm very near the point now where I'll go back to a7 and reinstall hipster Reinstalled hipster, and still it does not work, switched to another user with role admin, and again this fails. So there's not much room left where a lock file or other remnant artefakt can hide... I'm now not sure at all if it ever worked on a8 hipster (it does on a7), it more seems that this is a general problem introduced by a security fix in libdbus recently: https://bugs.freedesktop.org/show_bug.cgi?id=60667 If it really does not work (can anybody confirm this ?), this at least means that the gnome menu startup script for the packagemanager must be changed. ___ 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] Problems with dbus / Orbit
On 07/07/2013 15:44, Udo Grabowski (IMK) wrote: On 07/07/2013 16:41, Jon Tibble wrote: Do you have dbus-x11 installed? Yes. Found the same error message now with pfexec wireshark so this seems to be a general problem. And liboil and libxklavier? Not sure if they've got to the hipster repo - Andrzej may need to refresh the JDS pull. JT On 07/07/2013 15:36, Udo Grabowski (IMK) wrote: On 07/07/2013 12:37, Udo Grabowski (IMK) wrote: Openindiana 157a8 hipster, fresh update from a7: I'm totally lost, after a premature Ctrl-C on a pfexec packagemanager, I cannot start it anymore in pfexec mode (local machine, no NFS): ~: pfexec packagemanager GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: @@@ Failed to get connection to session: Unable to autolaunch when setuid) @@@ ... Segmentation fault I'm very near the point now where I'll go back to a7 and reinstall hipster Reinstalled hipster, and still it does not work, switched to another user with role admin, and again this fails. So there's not much room left where a lock file or other remnant artefakt can hide... I'm now not sure at all if it ever worked on a8 hipster (it does on a7), it more seems that this is a general problem introduced by a security fix in libdbus recently: https://bugs.freedesktop.org/show_bug.cgi?id=60667 If it really does not work (can anybody confirm this ?), this at least means that the gnome menu startup script for the packagemanager must be changed. ___ 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] sox library mismatch in OI 151a6
Hi Chad, On 05/09/2012 18:14, Chad Cantwell wrote: After upgrading from 151a5 to 151a6, sox stopped working with this error: $ sox ld.so.1: sox: fatal: libsox.so.2: open failed: No such file or directory Killed This should be fixed in today's SoX update. JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sox library mismatch in OI 151a6
On 05/09/2012 18:14, Chad Cantwell wrote: After upgrading from 151a5 to 151a6, sox stopped working with this error: $ sox ld.so.1: sox: fatal: libsox.so.2: open failed: No such file or directory Killed I couldn't find libsox.so.2 anywhere, but symlinking libsox.so.1 fixed the issue for now. Chad Hi Chad, Thanks, a fix is just building now and should be available tomorrow. JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Installing one package triggered upgrade
On 17/07/2012 19:54, Ryan Johnson wrote: On 17/07/2012 2:49 PM, Timothy Coalson wrote: It may be that the installed root pool version was 5000 rather than 28 and the boot environment from 151a3 does not handle that (a5 would be needed). Is this something the user can fix? Or is the packaging broken? I don't think that you should be able to have the rpool at version 5000 without installing from oi_151a5 media, or issuing a zpool upgrade rpool or zpool upgrade -a manually after booting into oi_151a5. If these are not the case, then your rpool should still be at version 28, and if so, previous boot environments should still work (you can can activate the one you are currently booted into via the package manager or beadm, and then a reboot should work, by not having any changed packages). It is not possible to downgrade a pool (so be careful with zpool upgrade). I installed the 151a1 media, I've never tried to do anything with ZFS, and the previous boot environments still work. Problem is, any attempt to install a package triggers an update and the new package goes into the (broken) BE the upgrade sets up. So the question is, how come the version of zfs pulled in by the new BE is the wrong version for that BE? I'm not trying to avoid an upgrade, as long as the machine still boots afterward. Ryan Firstly, an upgrade will not bump the zpool version - that would obviously be insane. Secondly you installed an oi_151a system (there was no media for oi_151a1 BTW) with package versions 0.151.1 and all the prestables have 0.151.1.x. Unfortunately this has raised an ugly issue we didn't know about until it was too late that pkg incorrectly thinks they are the same and can satisfy dependencies with them. This has the effect that you've seen that it therefore tries to upgrade you even when you install the simplest single package. It is slightly strange that it only tries to install a few packages though which probably causes your issue. The best thing to do would be to actually do a full upgrade. I'm not sure if it will let you pick a version or not but to find out you need to use a command similar to the debugging command found here: http://wiki.openindiana.org/oi/Troubleshooting+image-update+failures This will allow you to find something that works for you. A normal version upgrade is in the order of 900 packages so you should be able to see from the output if it looks like it is trying to do something sensible. If you upgrade to a3 or later make sure you have a normal umask set to avoid https://www.illumos.org/issues/2651. JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] oi_151a3 live installation failed
Hi Alex, On 13/04/2012 13:57, Alex Lam S.L. wrote: I see that the latest prestable comes with ISO, so I decided to give it a spin. First time I did the install, it got stuck at 99% (Completing transfer process) for an hour. I tried powering the PC off and then start without Live DVD to see if the installation went okay, and unfortunately it didn't. There does seem to be an unusually long delay around the 99% mark but I never saw anything as long as you describe. Second time, it produced the Installation Failed screen after going through the installation. Attached OpenIndiana installation log as given by that screen. You seem to have missed attaching the attachment. Would be good to see the log if you have it - looks like it can be found in /var/sadm/system/logs/install_log Thanks, JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Dependency problem on pkg:/service/network/dns/bind
On 30/03/2012 16:08, Jan Owoc wrote: On Fri, Mar 30, 2012 at 8:55 AM, Chris Riddchrisr...@mac.com wrote: Am I reading this wrong? Is there a workaround? I'm not sure if the repository got overwritten, or simply newer packages got added without removing the old ones. If the latter, there may be a way to force the installation of the older version of bind, the one corresponding to the rest of the system. (Or if there still exists a mirror of the original repository somewhere...) Updating to 0.151.1.2 from /dev and rebooting is an option. Or should I be changing my publisher to something more reliable? There is (currently) no stable release of OI. Your choices are to stay with whatever system you happened to install (it works!), or update to the most recent pre-stable release. I'm unable to find anything newer/more stable than this: http://wiki.openindiana.org/oi/oi_151a_prestable1+Release+Notes After refreshing the repositories with pkg refresh --full, you may or may not need to first update pkg (pkg install -v pkg:/package/pkg) before doing the full system upgrade (I did when going from 151a to 151a-pre0). Jan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss There was no history rewriting (whatever that is supposed to mean), later versions are added to the repo with nothing being taken away. The /dev repo is the most reliable for OI currently. If you don't want to update then use: pkg install blah@0.5.11-0.151.1.1 JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] webmin upgraded with OI upgrade to 151.1.2, why???
Hi Hans, On 25/02/2012 14:41, Hans J. Albertsson wrote: It certainly seemed like webmin had been upgraded for this new 151 version, but I notice: No it doesn't, OI branch versions get bumped with each release meaning you normally get updated metadata for every package installed when you update - slightly annoying and may change with the new system and a more rolling upgrade approach. Anyway searching for all versions of webmin at pkg.openindiana.org/dev gives: system/management/webmin@1.510,5.11-0.147:20100914T030204Z system/management/webmin@1.510,5.11-0.148:20101125T011516Z system/management/webmin@1.510,5.11-0.151.1.1:20120114T201949Z system/management/webmin@1.510,5.11-0.151.1.2:20120209T203632Z system/management/webmin@1.510,5.11-0.151.1:20110912T025048Z so you can see nothing has changed in regards to the webmin version. A: It's still v 1.510 ( Official webmin is at 1.570. ) Sounds about right. Plenty of packages are behind upstream. B: The known bug, incorrect directory for the smf manifest file, had not been fixed. I don't suppose the upgrade was intentional, or just for image packaging or something?? Stilll C: an irritating minor problem remains. It offers to upgrade to a newer webmin if you do that, webmin breaks in insiduous ways. One should remove that offer, or rewrite it to only offer an IPS pkg(5) upgrade if such an upgrade exists. Are there bugs filed for these two issues? bugs.openindiana.org doesn't seem to think so so could you do that please? Regards, JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Quadro 600 No Joy - Solved
On 01/03/11 00:54, Lou Picciano wrote: Now this is quite interesting, though (in my case) it has nothing to do with the bge driver. Several of us have had problems with the RealTek interfaces - or is it something to do with the rge driver? What's interesting is that, in all cases, the problems seemed to appear after 134a. I have posted something of a bug report at Illumos, but I don't really have enough concrete diagnostic data of much use, I'm afraid. Yes, I know, the obvious answer is 'buy an Intel interface', but now I'm curious... ! Lou Picciano - Original Message - From: Ken Gundersonkgund...@teamcool.net To: Discussion list for OpenIndianaopenindiana-discuss@openindiana.org Sent: Monday, February 28, 2011 7:36:50 PM Subject: Re: [OpenIndiana-discuss] Quadro 600 No Joy - Solved On Mon, 2011-02-28 at 10:59 -0500, Gary Gendel wrote: Jon, This particular v20z refuses to update to the latest firmware, but bge works properly for OpenSolaris up to and including 134b so it looks to be a change to the bge driver found in Oi 147 or 148. There is another issue where apcupsd wouldn't run because of some change in libusb as well. Recompling from source wouldn't fix that problem either. Unfortunately, this is my home router, file, web, mail, et. al. server so I can't do extended experimentation and debugging. That a second person saw a CPU issue with the bge driver makes me (want) to believe something changed in the driver source to cause this. Just to add to the data point, this exact same system (sans the Qudaro) worked for many months with bge as primary NIC under various iterations of Nevada and OpenSolaris. So I would concur with Gary that the fault is something introduced post 134b, but remedied in Illumos based 148a. The 2865 also has onboard nge, and that works fine, wh/I makes ruling out something else in the stack a pretty safe bet. I've been up to my ears with other things, but am curious if anyone has checked Illumos bug tracker? Best regards-- Ken It is known that the bge driver in 148 is broken, please see this bug for more information including how to install a working driver. http://www.illumos.org/issues/544 Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Image-updates
I've been mentioning this on IRC a lot and filed a bug for it (https://www.illumos.org/issues/547). Please be aware that the opensolaris.org publisher should be set non-sticky to successfully upgrade - if it is not you will not have fully updated to oi_148. To confirm if you have or have not fully updated you can run pkg list | grep incorporation and check all the builds are at 148. Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OI_148 available
Project OpenIndiana is pleased to announce the next development release, oi_148, is available. Existing users can image-update from their current repositories. Images of various formats (dd-usb to follow shortly) are available here: http://openindiana.org/download/ The release notes are available here: http://openindiana.org/support/documentation/release-notes/ We welcome feedback and volunteers on the mailing lists: http://openindiana.org/getting-involved/mailing-list/ the bug tracker: http://bugs.openindiana.org/ and in the IRC channel #openindiana on Freenode. Enjoy. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI_148 available
On 12/18/10 12:44 AM, Russ Price wrote: On 12/17/2010 05:36 PM, Jon Tibble wrote: Project OpenIndiana is pleased to announce the next development release, oi_148, is available. Existing users can image-update from their current repositories. Image-update isn't working for me. From my oi_147 BE: r...@castle:~# pkg image-update --be-name oi_148 No updates available for this image. r...@castle:~# pkg publisher PUBLISHER TYPE STATUS URI openindiana.org (preferred) origin online http://pkg.openindiana.org/dev/ opensolaris.org (non-sticky) origin online http://pkg.opensolaris.org/dev/ extra origin online https://pkg.sun.com/opensolaris/extra/ The main repo isn't in sync yet - it's an oversight we're working on. Sorry for the inconvenience. Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI_148 available
On 12/18/10 12:47 AM, Jon Tibble wrote: On 12/18/10 12:44 AM, Russ Price wrote: On 12/17/2010 05:36 PM, Jon Tibble wrote: Project OpenIndiana is pleased to announce the next development release, oi_148, is available. Existing users can image-update from their current repositories. Image-update isn't working for me. From my oi_147 BE: r...@castle:~# pkg image-update --be-name oi_148 No updates available for this image. r...@castle:~# pkg publisher PUBLISHER TYPE STATUS URI openindiana.org (preferred) origin online http://pkg.openindiana.org/dev/ opensolaris.org (non-sticky) origin online http://pkg.opensolaris.org/dev/ extra origin online https://pkg.sun.com/opensolaris/extra/ The main repo isn't in sync yet - it's an oversight we're working on. This should be fixed now. JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [oi-dev] OI_148 available
On 18/12/10 00:36, Jon Tibble wrote: Project OpenIndiana is pleased to announce the next development release, oi_148, is available. Existing users can image-update from their current repositories. Images of various formats (dd-usb to follow shortly) are available here: http://openindiana.org/download/ Please, publish the torrent files!. Also MD5 hashes are a bit weak, would be nice to publish SHA1 hashes, replacing MD5 or in addition to MD5. - -- Jesus Cea Avion torrents are in the works with the dd usable usb stuff. I've just added SHA1s to the download page so you can use those. Some people are having an issue with old cached md5 files from the beta testing. If you have this issue use the SHA1s as they weren't around to be cached during testing. Thanks, JT ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] [b 147] Consensus on how to set up static IP
On 11/10/10 04:05 PM, Harry Putnam wrote: Christopher Chanchristopher.c...@bradbury.edu.hk writes: On Tuesday, November 09, 2010 07:16 AM, Harry Putnam wrote: Can anyone point me to, or supply a brief step thru describing a known to work method for setting up a static IP address. One with complete steps that are current, as it appears from googling around that there are several ways described and not all work on newer opensolaris like b 134. ??? Is it really too hard to ask a question? A series of question marks is pretty meaningless. [...] Do we have a standard way to do this now? I don't know about standard but for static ips, I use the 'old way' and not nwam. Which is stuff ip-address into /etc/hostname.interface0, svcadm disable network:nwam; svcadm enable network:physical and edit /etc/resolv.conf and check for dns in /etc/nsswitch.conf for hosts. Exactly what I hoped to avoid. ---- ---=--- - DerSaidindersai...@gmail.com writes: Hello, See: http://blogs.sun.com/PlasticPixel/entry/nwam_static_ip_address_for The other files you'll want to check (I'm unsure if these are essential) when setting up a NIC are: /etc/nsswitch.conf /etc/defaultrouter I've seen various comments about that /etc/nsswitch.conf In my case it shows `files' first at every entry including `host'. Apparently some where added by dhcp when that was used: From /etc/nsswitch.conf on opensolaris b 134 [...] #hosts: files # Commented out by DHCP hosts: files dns # Added by DHCP #ipnodes:files # Commented out by DHCP ipnodes: files dns # Added by DHCP [...] About /etc/defaultrouter I do not have that file. I could of course create it, but it seems to work without it. find /etc/ -iname '*router*'nada But the route is still set and shows up in `netstat -nr' So that one (/etc/defaultrouter) may not be necessary (this is on opensolaris b 134) --- - ---=--- - Thanks for the URL... yes, I found other input very similar and did that on an opensolaris install successfully so hopefully it will also do the job on openindiana b 147 Haven't got to it yet. However I will say that opensolaris b 134 does not have the same setup at the network icon on upper left of desktop. oi b 147 has a different and better dialog far as I saw. And it may have actually done the job... it turned out that my virtual networking was confused by having both vmware and vbox installed apparently when I installed vbox (after vmware by a week or two) it took over the vmware vmnet adaptors somewhat confusing... but ok now. NWAM does static IP nicely, just not all settings are entirely accessible by GUI (imo config files are simpler/nicer anyway). Yes, give me files too but which are you referring to that are not accessible? Do you mean /etc/defaultrouter and /etc/nsswitch.conf? I haven't done it since b134 but there using the GUI to NWAM from the status bar next to the clock worked. Should be fairly straight forward. Think I may have needed one or two relogins to get the status bar to show both correct info and green instead of errors but it worked. Regards, Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] snv148 out in 2, 3 weeks?
Hi, Is it possible that oi148 will be ready in 2, 3 weeks? Does anybody know how long it will take? I won't install snv147. Hi Daniel, I believe what's been posted to the list was that it's expected to be available in 1Q 2011 (meaning 1st quarter of 2011). Since that won't be until after the beginning of the new year I would suspect the answer to your question is 'no'. But I have no inside knowledge. Cia W snip The 2011.Q1 is for the first stable release as opposed to the more regular dev releases. oi_147 and oi_148 are dev releases. 148 will be out ASAP - obviously not before it is all built though. Check http://wiki.openindiana.org/display/oi/oi_148 for the current status. You'll see at the moment the hold up is getting g11n built. Once that is done progress should be more easy to spot. Regards, Jon ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
