[OpenIndiana-discuss] Workaround for Flash issue
Hi, I found an interesting fact about the flash player problem (151a8,a9): If you manage to right click the menu entry 'About Adobe flash player' while the video is loading, but before it plays (you have to be fast...), the video will first crash, but a second tab opens and shows the Adobe flash intro running. After that, close the Adobe tab, and reload the video page. The video will run, and all subsequent videos after will also be shown without crashes in this instance of firefox (latest solaris flash 11.2.202.223) ! This seems to hint to a threading issue with library load order, I previously experimented a lot and got flash running randomly, but not in a way to present a consistent workaround, but this time, it seems to circumvent the problem always. The debugger loads the plugin-container with the libraries below when it works, but loads these ones additionally when actually starting the video: Reading pango-basic-fc.so Reading libcanberra-gtk.so.0.1.7 Reading libcanberra.so.0.2.4 Reading libgconf-2.so.4.1.5 Reading libORBit-2.so.0.1.0 Reading libltdl.so.3.1.4 Reading libcanberra-oss.so Reading libvorbisfile.so.3.3.5 Reading libvorbis.so.0.4.6 Reading libogg.so.0.7.1 Reading libpixbufloader-xpm.so (video shown) So maybe there's something wrong in these compared to a7, where flash used to work. - Libraries loaded before: Reading plugin-container Reading ld.so.1 Reading libxul.so Reading libCrun.so.1 Reading libCstd.so.1 Reading libpthread.so.1 Reading libc.so.1 Reading libssl3.so Reading libnss3.so Reading libnssutil3.so Reading libplc4.so Reading libnspr4.so Reading libthread.so.1 Reading librt.so.1 Reading libplds4.so Reading libnsl.so.1 Reading libXrender.so.1 Reading libX11.so.4 Reading libXext.so.0 Reading libmozalloc.so Reading libgobject-2.0.so.0.2800.8 Reading libglib-2.0.so.0.2800.8 Reading libgtk-x11-2.0.so.0.2200.1 Reading libgdk-x11-2.0.so.0.2200.1 Reading libcairo.so.2.11000.2 Reading libgio-2.0.so.0.2800.8 Reading libresolv.so.2 Reading libsocket.so.1 Reading libm.so.2 Reading libXt.so.4 Reading libdemangle.so.1 Reading libdl.so.1 Reading libgthread-2.0.so.0.2800.8 Reading UTF-8%UTF-16LE.so Reading UTF-16LE%UTF-8.so Reading libgmodule-2.0.so.0.2800.8 Reading libsmime3.so Reading libmozsqlite3.so Reading libdbus-1.so.3.4.3 Reading libatk-1.0.so.0.3209.1 Reading libfreetype.so.6 Reading libgdk_pixbuf-2.0.so.0.2200.1 Reading libfontconfig.so.1 Reading libpango-1.0.so.0.2800.4 Reading libmp.so.2 Reading libmd.so.1 Reading libXau.so.6 Reading libXdmcp.so.6 Reading libsecdb.so.1 Reading libpangocairo-1.0.so.0.2800.4 Reading libXcomposite.so.1 Reading libXdamage.so.1 Reading libXfixes.so.1 Reading libpng14.so.14.12.0 Reading libpangoft2-1.0.so.0.2800.4 Reading libtsol.so.2 Reading libXinerama.so.1 Reading libXi.so.5 Reading libXrandr.so.2 Reading libXcursor.so.1 Reading libpixman-1.so.0 Reading libz.so.1 Reading libSM.so.6 Reading libICE.so.6 Reading libbsm.so.1 Reading libbz2.so.1 Reading libexpat.so.1.6.0 Reading libinetutil.so.1 Reading libscf.so.1 Reading libuutil.so.1 Reading libgen.so.1 Reading libnvpair.so.1 Reading libsmbios.so.1 Reading xlcUTF8Load.so.2 Reading libclearlooks.so Reading libcanberra-gtk-module.so Reading libflashplayer.so Reading libpangoxft-1.0.so.0.2800.4 Reading libpangox-1.0.so.0.2800.4 Reading libXft.so.2 Reading libsoftokn3.so Reading libnssdbm3.so Reading libfreebl3.so Reading libkstat.so.1 ... (here the libraries for the video will load) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
On 1/23/14, 10:09 PM, Volker A. Brandt wrote: >> On 1/23/14, 1:41 AM, Ben Taylor wrote: >>> I am looking at decom'ing some sparc hardware in Chicago, and have found >>> someone willing to host the hardware out there, on the agreement that >>> someone is going to actively use the hardware for the sparc port. Any >>> volunteers? >> >> We've had this discussion on the Illumos side about a year ago. The >> hardware wasn't the issue. It was the volunteers (save for a single >> brave soul, nobody wanted to deal with it). > > ...which is not quite how I remember it; several people including me > offered hardware, hosting, and porting help. There were long and > emotional discussions, yes; and ultimately nothing came of it. > But it was definitely more than one person, and there still is > some interest as can be seen by the continued use of Martin Bochnig's > OpenSXCE. Well, I should have expanded a bit more. I only got a single request for an account on the build farm I set up. It's possible there's more people out there who are willing to put in the hours (Martin being one example), but I didn't see them. Also, the infrastructure (hardware/hosting/whatever) wasn't the problem. As you said, several people offered that (including myself, and I actually built it, configured it and made it publicly available). But the fact is, nobody stepped forward to actually take responsibility for getting the work done. But by all means, do get your hands dirty and get a port up and running. I assure you Illumos will happily accept back patches which fix any breakage that might have happened, or new features for the port. I try my hardest not to break SPARC when I develop Illumos stuff, but it's not my area of focus or interest. Cheers, -- Saso ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
> On 1/23/14, 1:41 AM, Ben Taylor wrote: > > I am looking at decom'ing some sparc hardware in Chicago, and have found > > someone willing to host the hardware out there, on the agreement that > > someone is going to actively use the hardware for the sparc port. Any > > volunteers? > > We've had this discussion on the Illumos side about a year ago. The > hardware wasn't the issue. It was the volunteers (save for a single > brave soul, nobody wanted to deal with it). ...which is not quite how I remember it; several people including me offered hardware, hosting, and porting help. There were long and emotional discussions, yes; and ultimately nothing came of it. But it was definitely more than one person, and there still is some interest as can be seen by the continued use of Martin Bochnig's OpenSXCE. Regards -- Volker -- Volker A. Brandt Consulting and Support for Oracle Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim Email: v...@bb-c.de Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 46 Geschäftsführer: Rainer J. H. Brandt und Volker A. Brandt ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] SPARC-port: THIEF of my work, not this time again!
WOW: Mr. Ben Taylor aka @SunTzuTech silently joins me, tells me nothing and asks lots of odd questions. He didn't say a single good word about OpenSXCE. Instead I now see on the OI lists that he wants to steal/clone my work under his name 4 OI he did the same in 2006 with my sparc post of QEMU, he understood nothing of the code. But then took my patches and submitted them upstream UNDER HIS NAME!!! [OpenIndiana-discuss] sparc support Ben Taylor http://openindiana.org/pipermail/openindiana-discuss/2014-January/thread.html#14853 [OpenIndiana-discuss] sparc support Saso Kiselkov [OpenIndiana-discuss] sparc support Stefan Müller-Wilken [OpenIndiana-discuss] sparc support Saso Kiselkov [OpenIndiana-discuss] sparc support Stefan Müller-Wilken [OpenIndiana-discuss] sparc support Saso Kiselkov [OpenIndiana-discuss] sparc support Stefan Müller-Wilken [OpenIndiana-discuss] sparc support Saso Kiselkov [OpenIndiana-discuss] sparc support Stefan Müller-Wilken [OpenIndiana-discuss] sparc support Adam Glasgall [OpenIndiana-discuss] sparc support Stefan Müller-Wilken I would like to thank my friends, sponsors, mentors and supporters. Last but nor least for having informed me what's going on here. This permitted me to resubscribe for this message. Note: Forking, branching off all that is absolutely fine and ok. But not from behind! Mr. Ben Taylor subscribed on twitter.com/martinbochnig a few days ago, without saying a single word concerning his grand plans. The only thing I wondererd about: He asked all sorts of questions, even quite silly ones. While not having a single good word about OpenSXCE, nor any personal "hello" or apology for qemu, timetravel back to 2006/2007 ... I wish everyone Good Luck with this effort, but not this way. -- regards %martin bochnig http://svr4.opensxce.org/sparc/5.11/ http://opensxce.org/ http://wiki.openindiana.org/oi/MartUX_OpenIndiana+oi_151a+SPARC+LiveDVD http://www.youtube.com/user/MartUXopensolaris https://twitter.com/MartinBochnig ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OI a9 upgrade and SFE
Hi, if you are using SFE on top of OI and you have system/library/orc installed from SFE (e.g. you are using ffmpeg or mplayer), then either set sfe repo as non-sticky or uninstall system/library/orc from SFE before upgrade. system/library/orc is part of OI distribution now. After update to a9, ffmpeg and mplayer can consume system/library/orc from OI without issue. Best regards, Milan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] No login prompt when updating 151a8 -> 151a9
Just to make sure: deleting the cache in one boot environment may not hurt other environments, right? Wouldn't want to risk my running installation. I would be surprised if it were storage errors. At least I scrub regularly and without any errors... Cheers Stefan Von: Jason Matthews [ja...@broken.net] Gesendet: Donnerstag, 23. Januar 2014 17:32 An: Discussion list for OpenIndiana Cc: Discussion list for OpenIndiana [openindiana-discuss@openindiana.org] Betreff: Re: [OpenIndiana-discuss] No login prompt when updating 151a8 -> 151a9 could it be some byzantine disk failure keeping your zpools from importing? try deleting /etc/zfs/zfs.cache in single user and rebooting. if that boots u likely have a storage problem Sent from Jasons' hand held On Jan 22, 2014, at 11:57 PM, Stefan Müller-Wilken wrote: > Dear all, > > following the discussion we've had lately around upgrading installations, > I've done so for a few 151a8 servers. While most of them were absolutely > noiseless, one has failed. After doing 'pkg update', the machine rebooted as > expected but then repeatedly got stuck on startup. While the server seemed to > boot as always, I didn't receive a login prompt. The screen would accept key > presses, the network stack would respond to ICMP messages, but neiter did I > get a login prompt on the console nor via SSH. Going to single user mode on > boot would work but moving on towards multi user (using Ctrl-D) would get me > back into stuck state. Nothing in the logs, nothing unusual on screen, just > silence. > > Thanks to this being OpenIndiana, I simply reverted back to the previous boot > environment and everything was fine again. > > Any idea what might have happened or where to look? > > Cheers > Stefan > > > Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: > Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 > ___ > 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 Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
Woah, that's *way* more than what I would have expected. Pretty amazing initiative! Cheers Stefan Von: Adam Glasgall [glasg...@mit.edu] Gesendet: Donnerstag, 23. Januar 2014 17:44 An: bentaylor.sol...@gmail.com Cc: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] sparc support Hi, #oi-dev pointed me at this thread and I feel obligated to speak up now. I have a working build of most of 151a8 for SPARC that I've built on an old Fire V210 in our machine room, and if you can offer me access to better hardware, I'd be happy to use it to build a more complete version. I'm also happy to offer people the install ISO and repo I've built, but I'd rather it not be announced as official yet, since much remains to be done before it's up to the same standards as the x86 port. Please cc me or reply directly to me if you want to talk about making this happen; I'm not subbed to oi-discuss because my inbox is already perpetually overflowing. Thanks, Adam Glasgall MIT SIPB ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
Hi, #oi-dev pointed me at this thread and I feel obligated to speak up now. I have a working build of most of 151a8 for SPARC that I've built on an old Fire V210 in our machine room, and if you can offer me access to better hardware, I'd be happy to use it to build a more complete version. I'm also happy to offer people the install ISO and repo I've built, but I'd rather it not be announced as official yet, since much remains to be done before it's up to the same standards as the x86 port. Please cc me or reply directly to me if you want to talk about making this happen; I'm not subbed to oi-discuss because my inbox is already perpetually overflowing. Thanks, Adam Glasgall MIT SIPB ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] No login prompt when updating 151a8 -> 151a9
could it be some byzantine disk failure keeping your zpools from importing? try deleting /etc/zfs/zfs.cache in single user and rebooting. if that boots u likely have a storage problem Sent from Jasons' hand held On Jan 22, 2014, at 11:57 PM, Stefan Müller-Wilken wrote: > Dear all, > > following the discussion we've had lately around upgrading installations, > I've done so for a few 151a8 servers. While most of them were absolutely > noiseless, one has failed. After doing 'pkg update', the machine rebooted as > expected but then repeatedly got stuck on startup. While the server seemed to > boot as always, I didn't receive a login prompt. The screen would accept key > presses, the network stack would respond to ICMP messages, but neiter did I > get a login prompt on the console nor via SSH. Going to single user mode on > boot would work but moving on towards multi user (using Ctrl-D) would get me > back into stuck state. Nothing in the logs, nothing unusual on screen, just > silence. > > Thanks to this being OpenIndiana, I simply reverted back to the previous boot > environment and everything was fine again. > > Any idea what might have happened or where to look? > > Cheers > Stefan > > > Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: > Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 > ___ > 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] recommendations for updating to 151a9
On 01/23/14 01:54 AM, Jonathan Adams wrote: On 22 January 2014 20:05, Tim Mooney wrote: - it recommends using "image-update". That doesn't seem to be documented in the "pkg" man page. How does it differ from just "update"? Is it just deprecated syntax that's been replaced by "update"? I don't _know_ the answer, but they both appear to do the same thing, and I have used just "update" for the last year+ Yes, "image-update" is the old, now deprecated, name for what's now just "update". That change was made in IPS near the end of OpenSolaris development, after many people had formed habits around "image-update", so that persists in various writeups they've done. -- -Alan Coopersmith- alan.coopersm...@oracle.com Oracle Solaris Engineering - http://blogs.oracle.com/alanc ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] 151a9 does not boot
... I have with unsatisfying results described earlier today. Have you tried single user mode? That at least is working in my case... Von: Dmitry Kozhinov [d...@desktopfay.com] Gesendet: Donnerstag, 23. Januar 2014 13:30 An: openindiana-discuss@openindiana.org Betreff: [OpenIndiana-discuss] 151a9 does not boot 151a9 update went without problems, but the updated version goes into reboot loop immediately after "SunOS..." initial boot message. The machine is Athlon XP (32bit). In verbose mode a number of messages appear, something like "x86feature=something" and the last message shows amount of RAM available. The messages disappear very quickly, as a reboot followed. Hitting Pause/Break key does not help. Had to boot back into 151a8 BE. Has anyone tried 151a9 on a 32bit hardware? Dmitry. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] gvfs help
Hi, while working on beta2 of XStream Desktop, we've encountered mysterious problems with gvfs. We tried various versions, from OI 1.6.x up to 1.16.4, converting patches to support our newer glib2. We always have the same problems: - smb uris don't work, as if the URI is taken wrong - hal support cannot be enabled during build, or binaries will crash the desktop We're mainly investigating the first problem, you can find details on the bug we filed here: https://bugzilla.gnome.org/show_bug.cgi?id=722481 Anyone here is expert with gvfs? How can this happen? We mainly believe that the glib-gio warning about "two different plugins" registering smb uri object can be the reason. But we can't find a way to get out of this hell. Any help will be appreciated, Gabriele. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] 151a9 does not boot
151a9 update went without problems, but the updated version goes into reboot loop immediately after "SunOS..." initial boot message. The machine is Athlon XP (32bit). In verbose mode a number of messages appear, something like "x86feature=something" and the last message shows amount of RAM available. The messages disappear very quickly, as a reboot followed. Hitting Pause/Break key does not help. Had to boot back into 151a8 BE. Has anyone tried 151a9 on a 32bit hardware? Dmitry. ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
That's sad! :-( Von: Saso Kiselkov [skiselkov...@gmail.com] Gesendet: Donnerstag, 23. Januar 2014 12:56 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] sparc support On 1/23/14, 11:51 AM, Stefan Müller-Wilken wrote: >> Sure, why not. What do you propose needs to be done to facilitate a) and b)? > > Hmmm... I thought the original post was by Ben, being willing to offer a > stack of recommissioned Sparc hardware under the condition that it would be > actively used for the Sparc port. So, if you would offer Martin online access > to that hardware to get forward with OpenSXCE, it would at least help *one* > Sparc port. And as Martin's work is open source, it could be used as a > nucleus for OI/SPARC and thus get one step closer to b). No? I already did offer a bunch of SPARC hardware, wired up, installed and ready to go, at no charge, but no maintainers stepped up to the plate, so I'm kind of skeptical there's interest in this direction. I could be wrong and perhaps I just didn't reach the right people, but my effort was made public on the mailing lists and in my experience, the response was almost completely silence (one brave soul did ask for a root account on these machines and I sent it to him, but he never used it). -- Saso ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
On 1/23/14, 11:51 AM, Stefan Müller-Wilken wrote: >> Sure, why not. What do you propose needs to be done to facilitate a) and b)? > > Hmmm... I thought the original post was by Ben, being willing to offer a > stack of recommissioned Sparc hardware under the condition that it would be > actively used for the Sparc port. So, if you would offer Martin online access > to that hardware to get forward with OpenSXCE, it would at least help *one* > Sparc port. And as Martin's work is open source, it could be used as a > nucleus for OI/SPARC and thus get one step closer to b). No? I already did offer a bunch of SPARC hardware, wired up, installed and ready to go, at no charge, but no maintainers stepped up to the plate, so I'm kind of skeptical there's interest in this direction. I could be wrong and perhaps I just didn't reach the right people, but my effort was made public on the mailing lists and in my experience, the response was almost completely silence (one brave soul did ask for a root account on these machines and I sent it to him, but he never used it). -- Saso ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
>Sure, why not. What do you propose needs to be done to facilitate a) and b)? Hmmm... I thought the original post was by Ben, being willing to offer a stack of recommissioned Sparc hardware under the condition that it would be actively used for the Sparc port. So, if you would offer Martin online access to that hardware to get forward with OpenSXCE, it would at least help *one* Sparc port. And as Martin's work is open source, it could be used as a nucleus for OI/SPARC and thus get one step closer to b). No? Cheers Stefan Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
On 1/23/14, 11:40 AM, Stefan Müller-Wilken wrote: > That might be true, but if he is one of the (at least to my knowledge) very > few working on SPARC Solaris descendants, wouldn't he still a) deserve > support and b) indirectly help OI/Sparc in the long run? Sure, why not. What do you propose needs to be done to facilitate a) and b)? -- Saso ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
That might be true, but if he is one of the (at least to my knowledge) very few working on SPARC Solaris descendants, wouldn't he still a) deserve support and b) indirectly help OI/Sparc in the long run? Cheers Stefan Von: Saso Kiselkov [skiselkov...@gmail.com] Gesendet: Donnerstag, 23. Januar 2014 12:05 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] sparc support On 1/23/14, 5:29 AM, Stefan Müller-Wilken wrote: > What about Martin and his OpenSXCE efforts? could he maybe make use of it? Martin's decided, for ideological reasons as far as I can tell, to maintain his own OS/Net consolidation. -- Saso > Am 23.01.2014 um 02:45 schrieb "Saso Kiselkov" : > >> On 1/23/14, 1:41 AM, Ben Taylor wrote: >>> I am looking at decom'ing some sparc hardware in Chicago, and have found >>> someone willing to host the hardware out there, on the agreement that >>> someone is going to actively use the hardware for the sparc port. Any >>> volunteers? >> >> We've had this discussion on the Illumos side about a year ago. The >> hardware wasn't the issue. It was the volunteers (save for a single >> brave soul, nobody wanted to deal with it). >> >> Cheers, >> -- >> Saso >> >> ___ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > > Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: > Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 > > ___ > 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 Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] sparc support
On 1/23/14, 5:29 AM, Stefan Müller-Wilken wrote: > What about Martin and his OpenSXCE efforts? could he maybe make use of it? Martin's decided, for ideological reasons as far as I can tell, to maintain his own OS/Net consolidation. -- Saso > Am 23.01.2014 um 02:45 schrieb "Saso Kiselkov" : > >> On 1/23/14, 1:41 AM, Ben Taylor wrote: >>> I am looking at decom'ing some sparc hardware in Chicago, and have found >>> someone willing to host the hardware out there, on the agreement that >>> someone is going to actively use the hardware for the sparc port. Any >>> volunteers? >> >> We've had this discussion on the Illumos side about a year ago. The >> hardware wasn't the issue. It was the volunteers (save for a single >> brave soul, nobody wanted to deal with it). >> >> Cheers, >> -- >> Saso >> >> ___ >> OpenIndiana-discuss mailing list >> OpenIndiana-discuss@openindiana.org >> http://openindiana.org/mailman/listinfo/openindiana-discuss > > > Acando GmbH, Millerntorplatz 1, 20359 Hamburg, Germany | Geschäftsführer: > Guido Ahle | Amtsgericht Hamburg, HRB 76048 | Ust.Ident-Nr.:DE208833022 > > ___ > 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] recommendations for updating to 151a9
jadams@jadlaptop:~$ pkg publisher PUBLISHER TYPE STATUS P LOCATION openindiana.org origin online F http://pkg.openindiana.org/hipster/ jds.openindiana.org (non-sticky) origin online F http://opensolaris.cz:1/ sfe-encumbered origin online F http://pkg.openindiana.org/sfe-encumbered/ sfe(non-sticky) origin online F http://pkg.openindiana.org/sfe/ localhost (non-sticky, disabled) origin online F http://localhost:1/ jadams@jadlaptop:~$ On 22 January 2014 20:05, Tim Mooney wrote: > > - it recommends removing opensolaris.org as a publisher. I didn't add > that, so it must have come from the OI151a8 install I did. Should I > really remove it? > I did, unless you want legacy software, for old OpenSolaris/Indiana distributions you won't need it in the future. - it recommends using "image-update". That doesn't seem to be documented > in the "pkg" man page. How does it differ from just "update"? Is it > just deprecated syntax that's been replaced by "update"? > I don't _know_ the answer, but they both appear to do the same thing, and I have used just "update" for the last year+ > - this is a desktop workstation, so I've installed quite a few > media-related packages from sfe, and a couple from sfe-encumbered. > After I set sfe and sfe-encumbered as non-sticky, > the "pkg update -nv" had no conflicts, but I'm uncertain what that > means for the packages I've installed from sfe or sfe-encumbered. > > - should I just remove all of them before I do an update? > no, only bother to remove if there is a conflict. > - will the fact that sfe and sfe-encumbered are now non-sticky mean > that the updates that come from /dev will leave sfe packages on > the > system, but in a broken state? Or, will the update automatically > remove stuff from sfe/sfe-encumbered if their dependencies are no > longer met? > the usual conflicts are when there are permission changes on the files in the packages, or if there is an overlap of files. If a newer package appears in any repository, that has non-conflicting permissions then the update will just move to that package, even if it is in a different repository. setting stuff non-sticky just allows it to do that. Jon PS. All information contained in this email may be wrong, and probably is, but it worked for me :) ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Upgrade Conflicts with 151a9
Hi, On 23.01.2014 09:13, Predrag Zecevic [Unix Systems Administrator] wrote: I know that (you had said that to me few times). What I wanted to stress is: so why do you ask again and again? :-) a) lack of any instructions, docs and plan explanation, etc for both /dev and /hispter releases Lack of time, no document writers? b) I had a look into dictionary: hipster is "a person who follows the latest trends and fashions." - So I would expect that /hipster is moving faster than /dev. In some ways yes, probably. Not in all. c) I would expect that changes made in /hipster are implemented to /dev (or it could be that I have wrong impression? see a) Look at /hipster as Ubuntu and /dev as Debian. Sometimes Ubuntu move faster, sometimes Debian. They can take inspirations from each other. In reality, I am ready to claim, that the most part of JDS is the most up-to-date in OI. Even in comparison to Solaris. The rest will be fixed with a10, I hope :-) Again, I do not care about /hipster and I hope that /dev will not take JDS bits from it, because it is much much much easier to maintain JDS in specs than in userland. d) I am willing to help with testing, but with no idea what would be next step, it is really hard. I understand it is not easy to start. But to be fair, several people asked me how they can help. In case of /hipster I answer - go and look at userland and help there. I cannot do more for you. Sorry. Regards. Best regards, Milan Regards Predrag P.S. I am running /hipster and have zone running /dev. Now I have paradox: zone was updated to 1.9 while my global zone is still 1.8.1 It is only number, nothing more :-) Best regards, Milan ___ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
