Re: [OpenIndiana-discuss] samba for nonglobal zone
I set from the beginning with image OI-hipster-text-20151003.iso --- Исходное сообщение --- От кого: "Alexander Pyhalov" Дата: 4 декабря 2015, 09:22:05 > On 12/04/2015 10:15, Alexandr Akol'zin wrote: > > Set hipster-2015. Created a zone. Publiher: > > http://pkg.openindiana.org/hipster-2015/ Publisher: Using openindiana.org > > (http://pkg.openindiana.org/hipster-2015/ ) > > I try to set a zone and an error appears: A ZFS file system has been > > created for this zone. Image: Preparing at /export/zones/root. Caching > > catalogs ... Done Refreshing catalog 'openindiana.org' ... Done Caching > > catalogs ... Done Cache: Using /var/pkg/publisher. Sanity Check: Looking > > for 'entire' incorporation. Installing: Packages (output follows) Planning: > > Solver setup ... pkg install: No matching version of compress/unzip can be > > installed: Reject: > > pkg://openindiana.org/compress/unzip@6.0-2015.0.0.2:20151027T055654Z > > pkg://openindiana.org/compress/unzip@6.0-2015.0.2.3:20151029T205121Z > > Reason: Excluded by proposed incorporation 'entire' No matching version of > > service/management/sysidtool can be installed: Reject: > > pkg://openindiana.org/service/management/sysidtool@0.5.11-2015.0.1.0:20151027T073029Z > > Reason: Excluded by proposed incorporation 'entire' No matching version of > > compress/zip can be installed: Reject: pkg://openindiana.org/compress > / > zip@3.0-2014.0.1.0:20151027T055656Z Reason: Excluded by proposed > incorporation 'entire' No matching version of editor/vim can be installed: > Reject: pkg://openindiana.org/editor/vim@7.4-2015.0.0.0:20151027T063819Z > Reason: Excluded by proposed incorporation 'entire' No matching version of > system/management/sysidtool can be installed: Reject: > pkg://openindiana.org/system/management/sysidtool@0.5.11-2013.0.0.0:20151027T080304Z > Reason: Excluded by proposed incorporation 'entire' No matching version of > compress/bzip2 can be installed: Reject: > pkg://openindiana.org/compress/bzip2@1.0.6-2014.0.1.2:20151027T055646Z > Reason: Excluded by proposed incorporation 'entire' No matching version of > compress/gzip can be installed: Reject: > pkg://openindiana.org/compress/gzip@1.5-2014.0.1.1:20151027T055647Z Reason: > Excluded by proposed incorporation 'entire' ERROR: failed to install package > How to correct it? > > Have you updated the base system? > You can't run new zone on the old system (when libc versions differ). > And I suppose for IPKG brand zone creation scripts ensure that NGZ's and > GZ's entire versions match. > -- > Best regards, > Alexander Pyhalov, > system administrator of Southern Federal University IT department С уважением Александр А. Акользин. With kind regards Alexandr Akol'zin ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] OI roadmap (for production)
Alexander Pyhalov, Thu Dec 3 12:39:35 UTC 2015: > As for /dev, I think it's not a big secret that it's efficiently dead. Nikola M, Thu Dec 3 18:46:38 UTC 2015: > It is not big secret that hipster is never planned for any kind of production What is the plan then? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/04/2015 17:16, Dmitry Kozhinov wrote: Alexander Pyhalov, Thu Dec 3 12:39:35 UTC 2015: > As for /dev, I think it's not a big secret that it's efficiently dead. Nikola M, Thu Dec 3 18:46:38 UTC 2015: > It is not big secret that hipster is never planned for any kind of production What is the plan then? Hi. What do you want to know? Currently we try to ride the car and tune it simultaneously (like illumos-gate does). I mean, there are changes which will affect urgent needs (e.g, security fixes) and some development (for example, major version updates). As for the current plan, there are several links http://wiki.openindiana.org/oi/Packaging+projects http://wiki.openindiana.org/oi/TODO+list As for my personal plans, I'd like to look at porting Mate now. As for other tasks, I think we have to remove python2.6 from OI, but to make this real, we have either: 1) officially state that /dev is dead and try to merge python2.7 changes to illumos-gate, 2) invent some decision which would work on OI /dev and old python, 3) add python 2.7 and updated IPS to OI /dev and merge python2.7 changes to illumos-gate. From these options only first one seems rather easy. When I looked at (2) I didn't find elegant way to achieve this. As for third option, it would be the best if there was some developer interested in this and having some free time. Also note that transition from legacy build systems to oi-userland is far from being complete, and this boring task also needs some heads and hands. SFW and JDS are mostly done, however there are still several components, which were not moved from these consolidations. There's a lot of work in XNV, and I even don't speak about g11n/inputmethod. There's also a set of binary blobs in OI which should be replaced or removed whenever possible. -- Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Thank you for the detailed response. I understand that there is a lot of work to do. But the work should have a goal. "we try to ride the car and tune it simultaneously" - doesn't that mean that OI will never be ready for production use? As for what do I want to know... A simpler question: What branch of OI (dev or hipster) you would recommend for production use? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/04/2015 18:18, Dmitry Kozhinov wrote: Thank you for the detailed response. I understand that there is a lot of work to do. But the work should have a goal. "we try to ride the car and tune it simultaneously" - doesn't that mean that OI will never be ready for production use? As for what do I want to know... A simpler question: What branch of OI (dev or hipster) you would recommend for production use? As always, everything depends on your "production use". I see Hipster suitable to run my "production" workstation or storage server. Your needs or ideas about production can be different. I wouldn't use OI /dev as it's currently not supported. -- Best regards, Alexander Pyhalov, system administrator of Southern Federal University IT department ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/ 4/15 04:18 PM, Dmitry Kozhinov wrote: Thank you for the detailed response. I understand that there is a lot of work to do. But the work should have a goal. "we try to ride the car and tune it simultaneously" - doesn't that mean that OI will never be ready for production use? As for what do I want to know... A simpler question: What branch of OI (dev or hipster) you would recommend for production use? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss Hi all, IMHO OpenIndiana /hipster is OK for desktop use (not ideal, but if you like it...). For serious use (if Oracle Solaris is out of question) I would use one of SERVER distributions, mentioned here: http://wiki.illumos.org/display/illumos/Distributions (SmartOS is maybe best choice. Of course I do not know what needs you really have) Personally I use /hipster from OI for every day job (is that production use?) and despite some problems and missing bits, I found it very stable and fairly good to use (consider latest Firefox, OpenSSH/OpenSSL/OpenLDAP, OpenOffice, LibreOffice /SFE/, TimeSlider, VirtualBox, etc). Best regards. -- Predrag Zečević Technical Support Analyst 2e Systems GmbH Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 Mobile:+49 174 3109 288, Skype: predrag.zecevic E-mail:predrag.zece...@2e-systems.com Headquarter: 2e Systems GmbH, Königsteiner Str. 87, 65812 Bad Soden am Taunus, Germany Company registration: Amtsgericht Königstein (Germany), HRB 7303 Managing director:Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Hi Predrag, what speaks against using OI in server use? I did that for the last few years without problems. What do you think is missing? Cheers Stefan Von: Predrag Zečević - Unix Systems Administrator [predrag.zece...@2e-systems.com] Gesendet: Freitag, 4. Dezember 2015 16:33 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production) On 12/ 4/15 04:18 PM, Dmitry Kozhinov wrote: > Thank you for the detailed response. I understand that there is a lot of > work to do. But the work should have a goal. "we try to ride the car and > tune it simultaneously" - doesn't that mean that OI will never be ready > for production use? > > As for what do I want to know... A simpler question: What branch of OI > (dev or hipster) you would recommend for production use? > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > Hi all, IMHO OpenIndiana /hipster is OK for desktop use (not ideal, but if you like it...). For serious use (if Oracle Solaris is out of question) I would use one of SERVER distributions, mentioned here: http://wiki.illumos.org/display/illumos/Distributions (SmartOS is maybe best choice. Of course I do not know what needs you really have) Personally I use /hipster from OI for every day job (is that production use?) and despite some problems and missing bits, I found it very stable and fairly good to use (consider latest Firefox, OpenSSH/OpenSSL/OpenLDAP, OpenOffice, LibreOffice /SFE/, TimeSlider, VirtualBox, etc). Best regards. -- Predrag Zečević Technical Support Analyst 2e Systems GmbH Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 Mobile:+49 174 3109 288, Skype: predrag.zecevic E-mail:predrag.zece...@2e-systems.com Headquarter: 2e Systems GmbH, Königsteiner Str. 87, 65812 Bad Soden am Taunus, Germany Company registration: Amtsgericht Königstein (Germany), HRB 7303 Managing director:Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ 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-IdNr.: DE208833022 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/ 4/15 04:53 PM, Stefan Müller-Wilken wrote: Hi Predrag, what speaks against using OI in server use? I did that for the last few years without problems. What do you think is missing? Cheers Stefan Von: Predrag Zečević - Unix Systems Administrator [predrag.zece...@2e-systems.com] Gesendet: Freitag, 4. Dezember 2015 16:33 An: openindiana-discuss@openindiana.org Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production) On 12/ 4/15 04:18 PM, Dmitry Kozhinov wrote: Thank you for the detailed response. I understand that there is a lot of work to do. But the work should have a goal. "we try to ride the car and tune it simultaneously" - doesn't that mean that OI will never be ready for production use? As for what do I want to know... A simpler question: What branch of OI (dev or hipster) you would recommend for production use? Hi all, IMHO OpenIndiana /hipster is OK for desktop use (not ideal, but if you like it...). For serious use (if Oracle Solaris is out of question) I would use one of SERVER distributions, mentioned here: http://wiki.illumos.org/display/illumos/Distributions (SmartOS is maybe best choice. Of course I do not know what needs you really have) Personally I use /hipster from OI for every day job (is that production use?) and despite some problems and missing bits, I found it very stable and fairly good to use (consider latest Firefox, OpenSSH/OpenSSL/OpenLDAP, OpenOffice, LibreOffice /SFE/, TimeSlider, VirtualBox, etc). Best regards. -- Hi Stefan, depends on "server" definition! If that is SAMP - no problems (Apache/PHP are latest ones, and instead of MySQL use either Percona or MariaDb - which is great). CIFS/Samba also works fine, Has all sort of servers: sFTP, FTP, DNS, etc VirtualBox runs everything So, can be used in most cases (once more: depends what is server definition) *but* it is NOT decalred as ready for production use, so one can use it if that is acceptable... Also, number of people involved in OS maintenance made me suggest SmartOS or OmniIT... Best regards. P.S I am writing this from OI /hipster which I still find attractive and useful. -- Predrag Zečević Technical Support Analyst 2e Systems GmbH Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894 Mobile:+49 174 3109 288, Skype: predrag.zecevic E-mail:predrag.zece...@2e-systems.com Headquarter: 2e Systems GmbH, Königsteiner Str. 87, 65812 Bad Soden am Taunus, Germany Company registration: Amtsgericht Königstein (Germany), HRB 7303 Managing director:Phil Douglas http://www.2e-systems.com/ - Making your business fly! ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Alexander, and Predrag, Thank you for the information. Currently I am using OI 151a9 for a web/ftp/mail server exposed to Internet. I am satisfied with the stability but concerned that this branch is not supported. I will consider hipster next time when I need to setup a server (it may be an intranet database server or something like a backend for an online service). I think that hipster is stable enough and hope that some future update will not beak everything :) Best regards, Dmitry. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Hipster permission files
Hey Community Me again with problems on OpenIndiana I have something very strange, I have a directory shared with smb, an app need to get into to see and format the files to show an screen, and also i can see that images on http, the http is not problem i can see the images there, but i give the permisions to the folder, and i tell who is the owner and here is the strange thing, if i have my network interface over dhcp i can see the image on the app, but i need to have a static ip, i make the change and it doesnt work anymore! Im a little crazy because is my boss here pushing me and i need to fix it soon i appreciated any help thank you! Luisa ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production) - typo correction
"break everything" ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
On 12/04/2015 11:06 AM, Dmitry Kozhinov wrote: Alexander, and Predrag, Thank you for the information. Currently I am using OI 151a9 for a web/ftp/mail server exposed to Internet. I am satisfied with the stability but concerned that this branch is not supported. I will consider hipster next time when I need to setup a server (it may be an intranet database server or something like a backend for an online service). I think that hipster is stable enough and hope that some future update will not beak everything :) Best regards, Dmitry. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss I moved to OmniOS because I was unable to upgrade hipster at one point as it broke the bge driver (in a very frustrating way as it looked like all packets were being filtered). I tried several times as new releases were available without success. Eventually decided to go to OmniOS as it met my needs and had stable and LTS versions. I still think that OpenIndiana via hipster is really good and would use it for a desktop or laptop when applicable, but having an X-server wasn't a necessity for my server setup. OmniOS has a minimal footprint and can use pkgsrc (supported by Joyent) to bring in lots of supported and latest packages you may need. Gary ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] firefox-43.0b8
Noticed firefox-43.0b7 made it into hipster (thanks Alexander!) and decided to try building firefox-43.0b8 with Martin and Alexander's patches. Hit the below GNU ld error with libxul.so. Anyone made it past it on OI? John groenv...@acm.org gmake[3]: Entering directory '/home/oi.1/john/ff43/toolkit/library' libxul.so rm -f libxul.so /home/oi.1/john/ff43/_virtualenv/bin/python /home/oi.1/john/firefox-43.0b8/config/expandlibs_exec.py --uselist -- /usr/bin/env LD_ALTEXEC=/usr/gnu/bin/ld PATH=/usr/gcc/4.9/bin:/usr/gcc/4.5/bin:/usr/gcc/4.7/bin:/usr/gcc/4.8/bin:ATH g++ -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -O -fomit-frame-pointer -fno-exceptions -fno-strict-aliasing -fno-rtti -fno-exceptions -fno-math-errno -std=gnu++0x -pthread -pipe -DNDEBUG -DTRIMMED -O -fomit-frame-pointer -fPIC -shared -Wl,-h,libxul.so -o libxul.so StaticXULComponentsStart.o -lpthread -Wl,-z,text -Wl,-z,ignore -Wl,-R,'$ORIGIN:$ORIGIN/..' -Wl,-z,lazyload -Wl,-z,combreloc -Wl,-z,muldefs ../../memory/volatile/libmemory_volatile.a ../../media/kiss_fft/libmedia_kiss_fft.a ../../media/libstagefright/libmedia_libstagefright.a ../../security/certverifier/libsecurity_certverifier.a ../../security/pkix/libmozillapkix.a ../../security/apps/libsecurity_apps.a ../../xpcom/typelib/xpt/libxpt.a ../../xpcom/string/libxpcom_string.a ../../xpcom/base/libxpcom_base.a ../../xpcom/ds/libxpcom_ds.a ../../xpcom/io/libxpcom_io.a ../../xpcom/components/libxpcom_components.a ../../xpcom/threads/libxpcom_threads.a ../../xpcom/reflect/xptinfo/libxpcom_reflect_xptinfo.a ../../xpcom/reflect/xptcall/libxpcom_reflect_xptcall.a ../../xpcom/reflect/xptcall/md/unix/libxpcom_reflect_xptcall_md_unix.a ../../chrome/libchrome.a ../../xpcom/build/libxpcom_build.a ../../modules/libpref/libmodules_libpref.a ../../intl/hyphenation/hyphen/libintl_hyphenation_hyphen.a ../../intl/hyphenation/glue/libintl_hyphenation_glue.a ../../intl/locale/libintl_locale.a ../../intl/locale/unix/libintl_locale_unix.a ../../intl/lwbrk/libintl_lwbrk.a ../../intl/strres/libintl_strres.a ../../intl/unicharutil/libintl_unicharutil.a ../../intl/unicharutil/util/internal/libintl_unicharutil_util_internal.a ../../intl/uconv/libintl_uconv.a ../../intl/build/libintl_build.a ../../netwerk/base/libnetwerk_base.a ../../netwerk/cookie/libnetwerk_cookie.a ../../netwerk/dns/libnetwerk_dns.a ../../netwerk/dns/mdns/libmdns/libnetwerk_dns_mdns_libmdns.a ../../netwerk/socket/libnetwerk_socket.a ../../netwerk/mime/libnetwerk_mime.a ../../netwerk/streamconv/libnetwerk_streamconv.a ../../netwerk/streamconv/converters/libnetwerk_streamconv_converters.a ../../netwerk/cache/libnetwerk_cache.a ../../netwerk/cache2/libnetwerk_cache2.a ../../netwerk/protocol/about/libnetwerk_protocol_about.a ../../netwerk/protocol/app/libnetwerk_protocol_app.a ../../netwerk/protocol/data/libnetwerk_protocol_data.a ../../netwerk/protocol/device/libnetwerk_protocol_device.a ../../netwerk/protocol/file/libnetwerk_protocol_file.a ../../netwerk/protocol/ftp/libnetwerk_protocol_ftp.a ../../netwerk/protocol/http/libnetwerk_protocol_http.a ../../netwerk/protocol/res/libnetwerk_protocol_res.a ../../netwerk/protocol/viewsource/libnetwerk_protocol_viewsource.a ../../netwerk/protocol/websocket/libnetwerk_protocol_websocket.a ../../netwerk/protocol/wyciwyg/libnetwerk_protocol_wyciwyg.a ../../netwerk/ipc/libnetwerk_ipc.a ../../netwerk/wifi/libnetwerk_wifi.a ../../netwerk/build/libnetwerk_build.a ../../extensions/auth/libextensions_auth.a ../../ipc/chromium/libipc_chromium.a ../../ipc/glue/libipc_glue.a ../../ipc/ipdl/libipc_ipdl.a ../../ipc/testshell/libipc_testshell.a ../../js/ipc/libjs_ipc.a ../../hal/libhal.a ../../js/xpconnect/wrappers/libjs_xpconnect_wrappers.a ../../js/xpconnect/loader/libjs_xpconnect_loader.a ../../js/xpconnect/src/libjs_xpconnect_src.a ../../intl/chardet/libintl_chardet.a ../../media/libyuv/libyuv_libyuv/libyuv.a ../../modules/libjar/libmodules_libjar.a ../../modules/libjar/zipwriter/libmodules_libjar_zipwriter.a ../../storage/libstorage.a ../../storage/build/libstorage_build.a ../../extensions/cookie/libextensions_cookie.a ../../extensions/permissions/libextensions_permissions.a ../../rdf/base/librdf_base.a ../../rdf/util/internal/librdf_util_internal.a ../../rdf/datasource/librdf_datasource.a ../../rdf/build/librdf_build.a ../../uriloader/base/liburiloader_base.a ../../uriloader/exthandler/liburiloader_exthandler.a ../../uriloader/prefetch/liburiloader_prefetch.a ../../caps/libcaps.a ../../parser/xml/libparser_xml.a ../../parser/htmlparser/libparser_htmlparser.a ../../parser/html/libparser_html.a ../../gfx/2d/libgfx_2d.a ../../gfx/ycbcr/libgfx_ycbcr.a ../../gfx/src/libgfx_src.a ../../gfx/qcms/libgfx_qcms.a ../../gfx/gl/libgfx_gl.a ../../gfx/layers/libgfx_layers.a ../../gfx/thebes/libgfx_thebes.a ../../gfx/ipc/libgfx_ipc.a ../../gfx/vr/libgfx_vr.a ../../ima
Re: [OpenIndiana-discuss] OI roadmap (for production)
In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...: what speaks against using OI in server use? Security updates. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] firefox-43.0b8
Hi. John D Groenveld писал 04.12.2015 19:47: Noticed firefox-43.0b7 made it into hipster (thanks Alexander!) and decided to try building firefox-43.0b8 with Martin and Alexander's patches. Hit the below GNU ld error with libxul.so. Anyone made it past it on OI? /usr/gnu/bin/ld:/usr/gcc/4.9/lib/gcc/i386-pc-solaris2.11/4.9.3/../../../libgcc-unwind.map:1: syntax error collect2: error: ld returned 1 exit status /home/oi.1/john/firefox-43.0b8/config/rules.mk:826: recipe for target 'libxul.so' failed gmake[3]: *** [libxul.so] Error 1 gmake[3]: Leaving directory '/home/oi.1/john/ff43/toolkit/library' /home/oi.1/john/firefox-43.0b8/config/recurse.mk:71: recipe for target 'toolkit/library/target' failed gmake[2]: *** [toolkit/library/target] Error 2 It seems you've missed a ld wrapper hack: https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/firefox/patches/04-gnu-ld-wrapper.patch https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/firefox/Makefile#L62 https://github.com/OpenIndiana/oi-userland/blob/oi/hipster/components/firefox/Makefile#L62 --- System Administrator of Southern Federal University Computer Center ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Hi, Gary. Gary Gendel писал 04.12.2015 19:16: I moved to OmniOS because I was unable to upgrade hipster at one point as it broke the bge driver (in a very frustrating way as it looked like all packets were being filtered). I tried several times as new releases were available without success. Eventually decided to go to OmniOS as it met my needs and had stable and LTS versions. I still think that OpenIndiana via hipster is really good and would use it for a desktop or laptop when applicable, but having an X-server wasn't a necessity for my server setup. OmniOS has a minimal footprint and can use pkgsrc (supported by Joyent) to bring in lots of supported and latest packages you may need. Could you check if bge works with latest Hipster ISO -http://dlc.openindiana.org/isos/hipster/OI-hipster-text-20151003.iso ? I'm just interested if it currently works... --- System Administrator of Southern Federal University Computer Center ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Good point, indeed. Just curious: But isn't that something all Illumos distributions have in common? Von: Tim Mooney [tim.moo...@ndsu.edu] Gesendet: Freitag, 4. Dezember 2015 17:56 An: Discussion list for OpenIndiana Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production) In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...: > what speaks against using OI in server use? Security updates. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ 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-IdNr.: DE208833022 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] OI roadmap (for production)
Security updates are a part of the weekly package review and requests. Not always public announced, but someone like me usually pings Alex (alp) about certain update needs if they are high or it is discussed in the oi-dev channel. As for driver updates, same thing. We usually support what we have on hand. If you need specific support, just request it. Ken On Friday, December 4, 2015 1:44 PM, Stefan Müller-Wilken wrote: Good point, indeed. Just curious: But isn't that something all Illumos distributions have in common? Von: Tim Mooney [tim.moo...@ndsu.edu] Gesendet: Freitag, 4. Dezember 2015 17:56 An: Discussion list for OpenIndiana Betreff: Re: [OpenIndiana-discuss] OI roadmap (for production) In regard to: Re: [OpenIndiana-discuss] OI roadmap (for production), Stefan...: > what speaks against using OI in server use? Security updates. Tim -- Tim Mooney tim.moo...@ndsu.edu Enterprise Computing & Infrastructure 701-231-1076 (Voice) Room 242-J6, Quentin Burdick Building 701-231-8541 (Fax) North Dakota State University, Fargo, ND 58105-5164 ___ 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-IdNr.: 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
