Re: [OpenIndiana-discuss] Looking for experienced user input on specific Machine purchase

[Michael Kruger]

On 01/25/2016 05:04 AM, Richard L. Hamilton wrote:

Googling for solaris hardware compatibility will find some (partly/mostly 
crowdsourced, i.e. not authoritative) lists for commercial Solaris.
I'd expect that OpenSolaris derivatives would resemble Solaris 10, perhaps 
minus some closed-source drivers.
Others might be able to expand on differences between the commercial Solaris 
Hardware Compatibility Lists (HCLs) and e.g. OpenIndiana.



This is an interesting topic. OpenIndiana has the device driver utility 
which is capable of uploading the results of a compatibility scan. 
Unfortunately that tool is configured to send those results to a server 
side infrastructure which no longer exists.


If this could be reprogrammed to send those result to an OI server, 
perhaps something could be done with the information...e.g. an improved 
HCL could be assembled.


At this time there is some HCL information on the OI Wiki:

http://wiki.openindiana.org/oi/Components
http://wiki.openindiana.org/oi/Systems

There is also the illumos HCL:

https://www.illumos.org/hcl/


To answer the OP's question of compatibility, I'd say yes, most HP 
workstation class systems would likely work fine. I have an entry level 
Z210 and it works nearly perfectly with OpenIndiana Hipster. It does not 
suffer the crackling sound issues I have seen on my home NAS, which has 
an Intel brand desktop class motherboard.


IMHOa single Xeon Z210 system is probably a better choice over a 
dual Xeon system, which is probably overkill for a home NAS. That said, 
the limitation of the Z210 is the number of disk drives it can hold, 
which is 3. I suppose with removable 5.25 drive trays, this capacity 
could be expanded to 6 to match the number of available SATA ports.


Michael

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

Re: [OpenIndiana-discuss] Looking for experienced user input on specific Machine purchase

[Michael Kruger]

On 01/27/2016 05:16 AM, Aurélien Larcher wrote:

Hello,

This is an interesting topic. OpenIndiana has the device driver utility

which is capable of uploading the results of a compatibility scan.
Unfortunately that tool is configured to send those results to a server
side infrastructure which no longer exists.

If this could be reprogrammed to send those result to an OI server,
perhaps something could be done with the information...e.g. an improved HCL
could be assembled.



I suggested something similar a long time ago but it requires repackaging
and updating the ddu utility first as there is no repository for this tool
(disappeared with opensolaris.org) and the C source has been partially lost
(now moved back to Solaris ON and thus closed).
That's also why there is no component in oi-userland, it is waiting
patiently on the list though:

http://wiki.openindiana.org/oi/Migration+of+consolidations+to+oi-userland

I created a repository and started fixing the missing bits a while ago but
this is going very slowly as it lies at the bottom of my TODO list... If
there is an interest I can setup a public repository.



The OI project would definitely benefit from more developers. You guys 
can only do so much by yourselves. Keep up the good work!


Maybe as the our documentation efforts begin to bear fruit, we might 
begin to attract some Linux and or BSD devs, and hopefully some students 
as well.


Michael

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

[OpenIndiana-discuss] Updated OpenIndiana FAQ

[Michael Kruger]

Hello All,

I have taken the original OpenIndiana FAQ from the website and wiki, and 
created an updated draft ready for your review.


You'll find it here: http://hub.openindiana.ninja/?q=content/faq

Please take a few moments to review it and kindly provide your feedback 
so it can be further refined and improved.


Thanks!

Michael Kruger

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

Re: [OpenIndiana-discuss] [oi-dev] Updated OpenIndiana FAQ

[Michael Kruger]

On 01/30/2016 02:50 PM, Alexander Pyhalov wrote:


BTW, can we use echelog to log oi-documentation channel? It also should
be mentioned on the wiki.


Hi Alexander,

I've modified everything you've suggested, and improved a few other 
areas as well. Please have another look: 
http://hub.openindiana.ninja/?q=content/faq



I'd like to see logging enabled as well. From what I have read about 
echelog, they require the channel to be populated at all times by at 
least 5 users. So, we could use a few more folks willing to regularly 
hang out in the #oi-documentation channel.



Keep the comments coming,

Michael

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

Re: [OpenIndiana-discuss] [oi-dev] Updated OpenIndiana FAQ

[Michael Kruger]

On 01/31/2016 01:26 AM, Alexander Pyhalov wrote:

Hi.

Again I don't like "Linux in contrast, was created from scratch to
provide an open source alternative to proprietary Minix". This sounds
strange now, when Minix is open sourced. Perhaps, change it to something
like "to Minix, which license limited it to educational use only".


Hi Alexander,

How does this sound?

Both OpenIndiana and BSD are true unix operating systems, whose roots 
trace back to the original AT&T Unix. Linux in contrast, was created 
from scratch to provide a free and open source alternative to Minix, 
which at the time, was licensed for educational uses only.



Michael

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

Re: [OpenIndiana-discuss] [oi-dev] Updated OpenIndiana FAQ

[Michael Kruger]

On 01/31/2016 03:31 PM, Johan S wrote:

On Sun, 31 Jan 2016 19:33:24 +0100
Aurélien Larcher  wrote:


Hello,

I don t find the comparison useful ... i mean how useful is it ...?

Linux was written from scratch ... by Hp Ibm SGI and lot
of companies .
This is absolutely irrelevant and could only lead to flamewar...
Documentation is not a fair place for any kind of propaganda...
My 2 cts



I agree with Johan, I do not think this is meaningful for the handbook.
People running Linux do not care about reading about Linux in the FAQ and
people who do not know about Linux (if any) may just benefit from the
knowledge that illumos/*BSD/Linux follow the UNIX paradigm with slight
differences.
Discussions about origins, who funded what, ideology vs change of business
model etc.. are off-topic.

The difference worth mentioning may be that illumos is not just a kernel
unlike Linux (system approach like *BSDs vs Linux-type loose coupling ?).




Thanks , i had been using AT&T Unix, BSD*  and Linux for more than 20 years.
Nowadays people often get more confused calling Unix where they should call
it Linux and vice versa.. just have a look in employment offers :-)
Working with superdome involves HPUX knowledge not Redhat , working on Onyx
requires knowing IRIX which is BSD...
Keep things simple and avoid flamewars :-)
I would prefer reading somewhat like "Illumos has direct roots from Unix and
therefore is more than just an Unix like"
But then again is documentation the right place for philosophy ?
Eventually one can lead the reader to historical materials ... :-)



Agreedit's not a useful comparisonmarked for deprecation;-)

Writing this, I had no idea this one section would generate so many 
comments.


Happy to hear all the responses though:-)

Michael

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

Re: [OpenIndiana-discuss] [oi-dev] Updated OpenIndiana FAQ

[Michael Kruger]

On 02/03/2016 04:30 PM, cpforum wrote:

  Hi,



Both OpenIndiana and BSD are true unix operating systems, whose roots
trace back to the original AT&T Unix.


True


Shortly (I used all theses Unixes (even Edition 7 in the eigthies on a Perkin 
Elmer 3220) and all solaris release excepted SunOS 5.1

AT&T System V --> AT&T SystemV R4
^ V
AT&T Edition 7 --> BSD 4.2 --> SunOS 3 --- > Sun OS 4 ---> SunOS 5.X > SunOS 5.10 
---> OpenSolaris > OpenIndiana

AT&T Edition 7 --> BSD 4.2 --> BSD 4.3 ---> BSD 4.3 Reno ---> BSD 4.4 Lite -> 
 NetBSD OpenBSD FreeBSD(ZFS)
delete of AT&T

For a Full and reliable history of Unix like system look at :

http://www.levenez.com/unix (move the mouse above the white picture)

or

http://www.levenez.com/unix/unix_a4.pdf

OpenSolaris and OpenIndiana are here until 2012


Linux in contrast, was created
from scratch to provide a free and open source alternative to Minix,
which at the time, was licensed for educational uses only.


Really ? I have some doubt. command line are Gnu, Xfree86 was X11 from MIT, init.d 
and rc.d come from AT&T System V R2, first TCP/IP stack was probably BSD etc.
even first kernels are probably inspired from Minix and BSD.
My first Linux install was a slackware with 0.99 kernel around 1995 with 4 Mb 
RAM and 5 GB disk on an Intel 286 or 386.

So saying OpenIndiana is a POSIX/Unix like with a mix of Gnu, BSD and System V 
commands is also true (like many others)


Thank you for your comments.

As I get some time this weekend, I'll try to rework this section to be a 
bit more historically accurate and intellectually honest;-)


I also would like to toss together a little news story about FOSDEM 2016 
for the OI website. If anyone has anything they'd like to contribute to 
that, please let me know.


For another update, we're collecting content for the next issue of 
Hipster news. If anyone has anything they'd like mentioned, I'd be happy 
to hear it.


Michael

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

[OpenIndiana-discuss] Updated OpenIndiana FAQ (2nd draft)

[Michael Kruger]

Hi All,

Based on feedback, I've reworked the FAQ a bit more.
Several sections have been reworded and re-ordered.

http://hub.openindiana.ninja/?q=content/faq

Feel free to comment

Michael

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

Re: [OpenIndiana-discuss] Updated OpenIndiana FAQ (3rd draft)

[Michael Kruger]

Last night I went back and re-read the comments folks provided, and have 
further updated the FAQ to include these.


Sections I worked on were the package manager, SPARC support, and 
getting involved. A few more minor edits elsewhere as well.


Unless anyone finds glaring regressions, this is likely to be closer to 
something we may want to publish.


Michael

http://hub.openindiana.ninja/?q=content/faq

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

Re: [OpenIndiana-discuss] [oi-dev] Updated OpenIndiana FAQ (3rd draft)

[Michael Kruger]

On 02/10/2016 06:14 AM, Alexander Pyhalov wrote:

Hi. I have several notices.

"Some notable features of OpenSolaris were the introduction of the all
familiar GNOME desktop, GNU userland tools, and a new network based
package manager (IPS)"
It seems comma before "and" is not necessary, but I'm not a native speaker.




Oh noafter the Linux debacle in earlier drafts of the FAQ, I'm not 
sure I am quite ready yet for an Oxford comma flame war;-)





In Feature/Description table some descriptions could be a bit expanded.
For non-Solaris user descriptions "Service Management Facility" and
"Fault Management Architecture" say nothing. At least there should be
links to documentation, wiki or wikipedia.




Good ideaI'll expand on those.




I'd avoid speaking about 32-bit support. It seems we are going to nuke
it in future, and in immediate future more and more 64-bit-only
applications will appear. One old good example is qemu-kvm.




OK perhaps we can exchange bitness for GHZ, or just whack the collumn 
from the table completely.





Adam, can we host
http://www.linuxtopia.org/online_books/opensolaris_2008/index.html on OI
infrastructure? Referencing to linuxtopia site seems strange.




Wellwe do have the docs from the 2009.06 drop, which we could host 
ourselves. They're not quite as outdated as the 2008 docs. I for one 
think they would be a helpful resource even as they are, but I am unsure 
how many other folks on the list would agree with the idea.


Another option is to simply whack that line from the list.




"Utilities maintenance - pkg[5]". Link seems to be broken. I think this
item needs brief clarification.




I need to try inserting an escape character to fix that...the wiki 
creole interpreter somehow thinks it's a link.





"As illumos is not itself a distribution, OpenIndiana combines
illumos-gate with OpenIndiana derived oi-userland"
I think something is wrong with this sentence.




I was thinking the same thing, but never got around to fixing it. I'll 
think a bit how to reword that so it makes more sense.





"At this time, the following distributions are known to support the
SPARC platform:.."
I think it would be good to reorganize the list in alphabetic order.



OKthat's easy enough to do. I'll look into putting Oracle Solaris by 
itself as well.



Thank you for taking the time to read this whole thing once more.

Michael

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

Re: [OpenIndiana-discuss] [oi-dev] Updated OpenIndiana FAQ (3rd draft)

[Michael Kruger]

On 02/10/2016 06:14 AM, Alexander Pyhalov wrote:

Hi. I have several notices.

"Some notable features of OpenSolaris were the introduction of the all
familiar GNOME desktop, GNU userland tools, and a new network based
package manager (IPS)"
It seems comma before "and" is not necessary, but I'm not a native speaker.

In Feature/Description table some descriptions could be a bit expanded.
For non-Solaris user descriptions "Service Management Facility" and
"Fault Management Architecture" say nothing. At least there should be
links to documentation, wiki or wikipedia.

I'd avoid speaking about 32-bit support. It seems we are going to nuke
it in future, and in immediate future more and more 64-bit-only
applications will appear. One old good example is qemu-kvm.

Adam, can we host
http://www.linuxtopia.org/online_books/opensolaris_2008/index.html on OI
infrastructure? Referencing to linuxtopia site seems strange.

"Utilities maintenance - pkg[5]". Link seems to be broken. I think this
item needs brief clarification.

"As illumos is not itself a distribution, OpenIndiana combines
illumos-gate with OpenIndiana derived oi-userland"
I think something is wrong with this sentence.

"At this time, the following distributions are known to support the
SPARC platform:.."
I think it would be good to reorganize the list in alphabetic order.


Hi Alexander,

I've applied all the edits you suggested and tossed an updated copy out 
on Github Gist: https://gist.github.com/makruger/83209277d6382c01c534


The creole markup rendering is not quite perfect (a few extra ** here 
and there), but github has rendered it mostly correct.


As for hosting the 2009.06 docs, I suppose we could do it on 
openindiana.org, but will we (those working on the docs) be able to 
easily update them there?


e.g. will we be able to obtain FTP access to an upload directory so the 
content can be updated as the documentation project progresses along? If 
not, then perhaps hosting the docs on github pages might provide better 
access to the doc team.


Ideally what I'd really like to see happen is the conversion of the 
solbook xml to asciidoc and import all the OpenSolaris books into github 
in that particular text markup format. I'd like to do the same with the 
handbook, FAQ, and anything else I am working on as well.


Solbook and docbook aren't much fun to work with, whereas ascidoc is 
plainly readable. And using the ruby acscidoctor toolkit, it produces 
some very nice HTML5 output, as well as PDF and EPUBS too.


After playing around a bit with both python based Sphinx and ruby based 
Ascidoctor, I think the later is the way to go. Ascidoctor installs fine 
on Hipster as a ruby gem (yes even with our ancient ruby 1.9).


If the proposed github doc repo could be configured with a commit hook 
to convert the docs and push them to github pages, then we'd have a 
fully automated (and might I also say very modern) documentation 
toolchain. This would really lower the bar for those working on the docs 
and mean less fuss for everyone involved. One would just need to 
understand how to use GIT and how to write docs in ASCIIDOC using the 
text editor of their choice.


Michael

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

[OpenIndiana-discuss] Contributing to the development of OpenIndiana

[Michael Kruger]

Hello All,

In the latest iteration of the OpenIndiana FAQ:

https://github.com/makruger/openindiana-docs/blob/master/faq.asciidoc

It became apparent the list of contribution task entry points was a bit 
outdated. For example, it mentions the distribution constructor, which 
ALP kindly pointed out is no longer used by Hipster.


Upon this discovery I realized this list should be updated.

This post is a solicitation for comments to create a more relevant list.

Here is the actual text from the FAQ:

*

Here are just some of the many ways you may contribute:

Release engineering - Distribution Constructor

Development

Utilities maintenance - Image Packaging System - pkg[5]

Packaging - oi-userland, 3rd party packaging (SFE, etc.)

Documentation - Handbook, Tutorials, News articles, etc.

OpenIndiana Evangelism - blogging, conferences, etc.

Website Maintenance

Translation

Artwork

For additional details, including links to our github source 
repositories, please see: 
http://www.openindiana.org/community/getting-involved


*

Please provide suggestions for how this can be improved.

thanks,

Michael

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

Re: [OpenIndiana-discuss] VirtualBox 5.0.16 working on OpenIndiana

[Michael Kruger]

On 03/13/2016 07:56 AM, russell wrote:

Hi,

I upgraded to VirtualBox from 5.0.14 to 5.0.16 no problems found yet.

Regards

Russell


Hi Russell,

Is there a package for this, or did you roll your own?

If the later, do you have a procedure which could be added to the 
OpenIndiana Handbook?


Michael

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

Re: [OpenIndiana-discuss] VirtualBox 5.0.16 working on OpenIndiana

[Michael Kruger]

On 03/15/2016 03:44 PM, Nikola M wrote:


Either way they should, ideally, be recompiled for OI to test and
distribute.



+1

I too would really like to see Virtualbox as a maintained package for 
Hipster.


It seems to me it would be a real help for new users coming from a 
Windows environment as they could still run their Windows apps virtually 
on top of OpenIndiana.


While KVM would also work well for this task, I think Virtualbox is a 
bit more user friendly...especially in the absense of virt-manager.


While we're talking about virutalization, is virt-manager something that 
could be ported to Hipster for managing KVM? Or if there is an old 
obsolete package, can we add it to the ever growing wish list of "nice 
to have" applications?



Michael

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

Re: [OpenIndiana-discuss] Updated FAQ has been published

[Michael Kruger]

Resending due to recent bounce back issue.



On 04/09/2016 11:59 PM, Michael Kruger wrote:


Hello all,

The FAQ that I have been working on has now been published. Being a
living document, it will improve and grow along with the project.

You can find the updated FAQ here:

http://www.openindiana.org/documentation/faq/

Also, our Wordpress instance now has an interpreter for the Asciidoc
text markup. And this document is the first written in this new markup.

Comments are always welcome.

Michael


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

[OpenIndiana-discuss] Updated FAQ has been published

[Michael Kruger]

Hello all,

The FAQ that I have been working on has now been published. Being a 
living document, it will improve and grow along with the project.


You can find the updated FAQ here:

http://www.openindiana.org/documentation/faq/

Also, our Wordpress instance now has an interpreter for the Asciidoc 
text markup. And this document is the first written in this new markup.


Comments are always welcome.

Michael

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

[OpenIndiana-discuss] Vim.org alternate download mirror

[Michael Kruger]

Just wanted to mention there is an alternate download mirror available.

http://ftp.vim.org/os/openindiana.org/dlc/isos/hipster/


If I am not mistaken, aren't both the primary and alternate mirrors 
located in Europe? If so, perhaps soliciting a mirror in North America 
would help reduce some of the strain on the European mirrors.


Michael


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

Re: [OpenIndiana-discuss] Vim.org alternate download mirror

[Michael Kruger]

On 04/23/2016 05:07 AM, Nikola M wrote:


I am additionally  proposing adding official (not per-user made)
.torrent files and magnet links
for newly made ISOs, on the same place where sha256sum and file itself is.
Also publishing sha256sums in same documents when mentioning Disk images
it a good practice.


+1 - Torrents would really help.

Another thought I had was to create a "current" folder on the download 
folder. With such a folder, there would no longer be a need to update 
documents referencing specific files on the download server. Instead 
those documents would simply point to the current folder.


Michael

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

Re: [OpenIndiana-discuss] [zfs] zfs + iscsi = poor sequential reding performance

[Michael Kruger]

On 04/23/2016 08:26 AM, Сисадмин wrote:

  Hi everyone,

to make the long story short - i 've spent 6 weeks trting really hard, read 
tons of doc pages on the internet (get lots of knowledge to be honest)

so i can get very good results , however unfortunetely i cant get from 
iscsi+zfs good results about sequential reading.


Admittedly I have not done any testing of ZFS performance on OpenIndiana.

However, about 4 years ago I went through this very exercise and tested 
nearly every available solution (FreeNas, Open-E, Nexenta, etc.,) and in 
the end chose Openfiler as my SAN solution. Using 2 NICs, I was able to 
achieve read speeds of nearly 200MB/s. I don't recall what the write 
speeds were, but I am think they were in the same neighborhood.


Here is a thread post to vmware communities, where I posted my results: 
https://communities.vmware.com/message/1986953#1986953


Assuming the storage can keep up, using 4 NIC's in an MPIO round robin 
configuration should deliver nearly 400 MB/s.


My white box lab didn't use any kind of fault tolerance. I was only 
using 2 500G disks in a raid stripe attached to an LSI controller with 
write caching was enabled. The LSI controller managed the disks.


One thing I discovered in this process was the Realtek NIC's vastly 
outperformed the Intel NICS. Whether the issue was on the ESXI side or 
the Openfiler side, I am not sure. I swapped both sides out with 
Realtek. OpenFiler however didn't natively support the Realtek NICs so I 
had to install my own drivers.


I have read the freebsd project has done some tuning to get ZFS to 
perform better. There are also some tunable parameters in illumos which 
may possibly help. See here: 
http://www.linuxtopia.org/online_books/opensolaris_2008/SOLTUNEPARAMREF/html/soltuneparamref.html


Hope that helps,

Michael

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

Re: [OpenIndiana-discuss] Vim.org alternate download mirror

[Michael Kruger]

On 04/23/2016 05:07 AM, Nikola M wrote:


I am additionally  proposing adding official (not per-user made)
.torrent files and magnet links
for newly made ISOs, on the same place where sha256sum and file itself is.
Also publishing sha256sums in same documents when mentioning Disk images
it a good practice.


There is already an unofficial torrent in the wild. Found this via a 
link from Distrowatch. Currently 11 seeders, mine will become 12.


http://linuxtracker.org/?page=torrents&search=openindiana&category=0&active=0



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

Re: [OpenIndiana-discuss] OI Hipster 2016.04 snapshot

[Michael Kruger]

Hi Carl,

There is a torrent directory on DLC, but no torrents for the latest 
release. http://dlc.openindiana.org/torrents/


Perhaps Xenol or Alp can help with this.

There is however, an unofficial torrent for the GUI desktop ISO. In fact 
Distrowatch is 'giving  back' to the community by hosting torrents for 
select projects, OpenIndiana being one of them.


For more details see:

http://distrowatch.com/weekly.php?issue=20160425#torrent

Michael



On 04/30/2016 06:49 PM, Carl Brewer wrote:

On 22/04/2016 2:16 AM, Alexander Pyhalov wrote:

Hi.

OI Hipster 2016.04 snapshot is ready.

Images:

http://dlc.openindiana.org/isos/hipster/OI-hipster-gui-20160421.iso
http://dlc.openindiana.org/isos/hipster/OI-hipster-gui-20160421.usb

http://dlc.openindiana.org/isos/hipster/OI-hipster-text-20160421.iso
http://dlc.openindiana.org/isos/hipster/OI-hipster-text-20160421.usb

SHA 256 checksums are available at ${link}.sha256sum

Release notes: http://wiki.openindiana.org/oi/2016.04+Release+notes


Great!  Any chance of a torrent?

thank you

Carl







___
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

[OpenIndiana-discuss] demonstration docs website

[Michael Kruger]

Hello all,

Here is a little something I have been working to help showcase 
documentation for the OpenIndiana project.


Currently hosted are:

OpenIndiana FAQ (Complete, but still growing and improving)
OpenIndiana Handbook (little more than a template at this point)
OpenSolaris Books (41 titles from the 2009 redistributable docs release)

All of this resides on github, so further evolution of this website and 
it's content simply follows existing development practices.


Here is the URL: http://makruger.github.io/website/

Enjoy,

Michael





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

[OpenIndiana-discuss] OpenIndiana Docs (proof of concept) - What is it all about?

[Michael Kruger]

Now that the dust has settled a little bit after my initial 
presentation, perhaps I should elaborate a bit about my motivations and 
intentions in creating this little proof of concept.


In the responses and discussions that followed, some feathers were 
ruffled, and a number of points where raised, many of which could be 
distilled into at least 3 distinct themes.


I'll start by talking about the first theme as everything else hinges 
upon it.



* Community conduct
* Project visibility
* Proof of concepts

* Version control
* Hosting infrastructure
* Project marketing, SEO

* Existing docs (OSOL Docs)
* Viability/Usability of Wiki
* dlc.openindiana.org/docs
* Documentation Standards (media types, etc.)
* Licensing/Contributer agreements/copyrights, branding etc.


It's now been about 3 months since I volunteered to help the project 
with documentation. I have learned quite a bit and overall it's been 
very interesting. I chose this project because it was very small, needed 
people, and I thought I might be able to make a meaningful difference. I 
still believe that.


So, this is my creative outlet. This is a place where I can express 
myself, learn, try new things, and explore new ideas. It's a place where 
I can (hopefully) make a difference.


Having a creative outlet is very important to me, because in my day job 
I work for a government bureaucracy. There each department is it's own 
little kingdom where nobody shares information or works together. As a 
result, innovation is stifled and dysfunction is pervasive. Even worse, 
most people are unhappy, and everyone complains. But the money is good 
and my commute is very short, so I put up with it all.


Here however, we're all volunteering our time. So I think having an 
atmosphere of acceptance, civility, and respect is extremely important. 
If not, the project will eventually curl up and die.


However, before any of that happens, people may find themselves needing 
to work alone or in small groups specifically and intentionally 
excluding individuals with problematic behaviors. This will occur 
because it's simply not possible to get anything done in an atmosphere 
of hostility, jumping to premature conclusions, or where kvetching is 
the rule of the day.


This leads me to suggest there should be an OpenIndiana 'Code of 
Conduct' to help reign in people with troublesome behaviors. After all, 
such individuals effectively prevent others from achieving anything 
meaningful. The future of the project may very well depend on it.


Having said all of that, let me turn the discussion back to my little 
docs website proof of concept. For starters, it's not a submarine 
project, nor do I intend to apply any kind of licensing which may 
restrict it's reuse in any way. Frankly I could care less how it's 
licensed. I wrote it all for the pure joy of writing. And in the spirit 
of community, it's free and available to all.


As for how it evolved the way it did, there are a number of reasons.

As soon as I joined the project I began looking at the OSOL docs, the 
website, and the wiki, and took notes of my thoughts and observations 
along the way. Those notes are publicly available for anyone to see:


https://github.com/makruger/openindiana-docs

The README describes what's in each document. This is all public and has 
been for quite some time. Again, not a submarine project at all.


So, after looking at the current state of information management, 
several things became clear.


There needed to be a way to:

1) Place documentation under distributed version control.
2) Lower the bar of entry to the documentation process.
3) Make changes and quickly deploy those changes in some kind of 
automated fashion (e.g. continuous integration).

4) Present the documentation in an organized and aesthetically pleasing way.

It's been said that a project lives or dies by it's documentation. 
Whether that's really true or not, I don't know, but the general 
perception for OpenIndiana is it's largely an undocumented project.


The need is there, now it's just a matter of coming up with a workable 
method for addressing the need. Good docs are important. Just as 
important is way the documentation is organized and presented.


This leads me to state the obvious:

The current state of the wiki is quite poor. The content is poorly 
organized, largely outdated, and the navigation menus do not function at 
all on mobile devices (this included tablets). This is a real problem, 
especially if the project expects people to rely on the Wiki as the "go 
to" source of information about the OpenIndiana project.


I can only conclude by saying this is quite unacceptable and something 
better is required. Whether that something better is my little project, 
or something else entirely, that's for the community to decide.


My proposal is on the table and I can only expect it to be fairly judged 
on it's technical merits. It should not however be frontally assaulted 
because it differ

Re: [OpenIndiana-discuss] [oi-dev] demonstration docs website

[Michael Kruger]

On 05/04/2016 06:52 AM, Alexander Pyhalov wrote:

> Hi, Michael.
>
> Thank you for your work.
> To move further I think we should consider several questions...
>
> 1) Someone should look through the docs... So , reviewers are welcome.
> Have you changed "OpenSolaris Redistributable Books" in any way or just
> created the index and converted them to docbook? How do we mark parts of
> the books which are not currently actual? How are we going to update
> them (create new document or mark current document as reviewed)? How
> http://makruger.github.io/website/pages/docs/handbook.html and
> http://wiki.openindiana.org/oi/OpenIndiana+Handbook are related? What
> parts are missing?



The website is composed of 3 separate components:

1) The Awestruct web framework

And the contents of 2 GitHub repositories:

2) https://github.com/makruger/openindiana-docs
3) https://github.com/makruger/docs_20090715

The Awestruct framework works with an Asciidoctor plugin to compile 
Asciidoc text markup content pages into HTML5 and then deploys it to a 
gh-pages branch. This branch is published to GitHub pages.


The compiler parses through everything it finds and anything which is 
already compiled (or for which there is no parser) is simply copied over 
without any further processing. The main index as well as header/footer 
layouts, etc., are composed in HAML (but can also include snippets of HTML).


The 2 GitHub repositories are not configured as submodules, but going 
forward they probably should be, or alternately things could remain as 
they are and inclusive of it all.


The openindiana-docs repository consists of the FAQ I previously worked 
on as well as a skeleton for an updated handbook. It also includes 
several informal 'work products' containing notes and guidance for 
anyone working on the docs project. Some of these work products could be 
used in the creation of other documents, others are better reserved for 
reference use only.


As for the handbook, I never envisioned it becoming as comprehensive the 
OSOL books, but rather be used as a supplement to them. Call it a guide 
for new users wanting to quickly get up to speed with the operating system.


The docs_20090715 repository contains the redistributable books. Here I 
simply extracted the zipfile (which already contained compiled HTML 
along with the raw XML sources) and wrote several index pages which 
linked it all together.


These books are as originally released without any further editing. I do 
not yet have a formal process for updating the books. Up until this 
point my only concern has been to host them as they are and develop a 
process for updating them at a later date.




> 2) What is the process of contribution, how site is generated? What
> tools are used to work on the docs ( asciidoctor + git ?)?



At this time the site is manually generated. Though in the future it 
could be automated using Travis-CI.


For those interested in helping with the development of the website 
itself, Awestruct can be run locally in development mode. This requires 
a Ruby environment, although this can be simplified in the future by 
using Gradle.


For those who wish to contribute to new or existing content, all that is 
required is a text editor. I use VIM along with an asciidoc VIM plugin. 
There is also an Asciidoctor IDE by the name of AsciidocFX. The IDE uses 
an Atom like text editor along with a live preview of the parsed text.


For those who wish to use VIM, there is an Asciidoctor plugin available 
for firefox (and Chrome as well) which can be used to parse the document 
and provide a close approximation of it's final rendered form.


Content is written using Asciidoc text markup (or more specifically the 
enhanced Asciidoctor version of it).


In either use case (content creation or website development), 
contributors would fork the repository and submit a pull request to have 
their changes incorporated. Someone (most likely me or anyone else who 
wishes to help) would review and merge the changes.


As for linking new documents with site menus, this is a manual process, 
but could be simplified by using TOC pages and adding and simply adding 
a new line item for the additional document.




> 3) How do you propose to incorporate documentation site in current OI
> web site? How do you suggest to consider what articles should live on
> the wiki, which - on documentation site? How these two sites are going
> to be related?



These are very good questions. I think initially we can provide a menu 
option on word press to redirect users to the docs site. Other pages may 
contain references residing on the docs site much as we do today with 
the Wiki.


As for deciding what goes where, unfortunately I do not yet have an 
answer. My inspiration for this project has been the Jenkins project who 
as far as I know have retained their Wiki. We could probably look to 
them for an answer to this question.


Michael

__

Re: [OpenIndiana-discuss] MATE 1.14 Desktop for OpenIndiana

[Michael Kruger]

On 05/11/2016 02:34 AM, Predrag Zečević - Unix Systems Administrator wrote:


Hi Toasterson,

I did unpacked MATE to separate directory, and navigated there, then:
$ ls -la
total 22K
drwxr-xr-x 11 rootroot   11 May 11 08:23 .
drwxr-xr-x  3 predrag_zecevic admin   3 May 11 08:23 ..
drwxr-xr-x  2 rootroot   82 May  5 18:27 bin
drwxr-xr-x  3 rootroot3 Mar 29  2015 doc
drwxr-xr-x  7 rootroot7 May  5 18:27 etc
drwxr-xr-x 24 rootroot   24 May  5 18:27 include
drwxr-xr-x 20 rootroot  110 May  5 18:28 lib
drwxr-xr-x  5 rootroot   30 May  5 17:50 libexec
drwxr-xr-x  3 rootroot3 Mar 29  2015 man
drwxr-xr-x  2 rootroot3 May  3 14:57 sbin
drwxr-xr-x 58 rootroot   58 May  5 18:27 share

I see that that structure is not same as / one, and also some files will
be replaced on existing OS (latest /hipster in my case), for example:

$ ls -al etc/dbus-1/system.d/pulseaudio-system.conf
-rw-r--r-- 1 root root 1.1K May  5 18:27
etc/dbus-1/system.d/pulseaudio-system.conf

$ ls -al /etc/dbus-1/system.d/pulseaudio-system.conf
-r--r--r-- 1 root bin 1.4K Oct  3  2015
/etc/dbus-1/system.d/pulseaudio-system.conf

What I did NOT checked is how many other files will be replaced and how
many files will be installed on wrong place, for example 'lib' dir
should go to '/usr/lib'?

With best regards.
Predrag Zečević


I inquired about how to test this via IRC:

[08:22:11]  makruger: gdm looks for /usr/share/xsessions/*.desktop
[08:22:39]  just ensure that you have corresponding file for mate there


Hope that helps,

Michael

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

[OpenIndiana-discuss] OpenIndiana Docs - updated

[Michael Kruger]

Hello All,

Reporting my progress so nobody gets the idea this little technology 
demonstration project has been abandoned. Far from it, there has been 
continued development.


See it all here: http://makruger.github.io/website/


This weekend the contribution page was reworked with a slightly modified 
layout and several new buttons:


* Style Guide
* GitHub (link to my repo, so you can fork it)
* Site build
* Site Theming
* Site Publishing

Renamed the workflow page to 'process' and expanded it out.

And to top it all off, I shamelessly stole the favicon from the OI WIKI.

Still need to work on adding content to the site build pages, etc., but 
in the meantime, you can look at my blog which provides some details how 
to install and build an Awestruct based website from scratch:


http://the-docs-guy.blogspot.com/

Michael

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

Re: [OpenIndiana-discuss] [oi-dev] OpenIndiana Docs - updated

[Michael Kruger]

On 05/16/2016 08:41 AM, Alexander Pyhalov wrote:


Some notes:
http://makruger.github.io/website/pages/docs/faq.html:
1) Sun/Oracle’s proprietary OS/NET consolidation has been replaced with
illumos-gate. => Sun OS/NET consolidation, closed by Oracle, has been
replaced...  I mean, OS/NET was open until Oracle came;


OK, thanks for pointing this out. I'll fix it.



2) What are the recommended hardware specifications... I'm not sure
about 4GB... It can be true for desktop/decent server, but you shurely
can run OI with 2GB RAM or even less. I've just checked, my OI VM with
GUI has 2 GB RAM... Perhaps, we can distinguish minimal and recommended
requirements?


Yes, I too have run the Gnome desktop as a virtual machine with 2GB and 
never experienced any problems.


Then one day I tried to run the Gnome desktop on a physical machine with 
an Nvidia adapter and this did not run well on 2GB. In fact when I 
performed a pkg update, the system used up all 3GB of available memory 
(2GB of RAM and the 1GB paging file) resulting in pkg crashing. Nothing 
else was runningjust Gnome and a command shell window. So I 
attributed the crash to insufficient memory.


This prompted me to suggest a 2GB minimum with an additional note to be 
sure to enlarge the paging file above it's default of 50% of physical 
memory.


Later we modified this with even more specific information regarding the 
true minimums and maximums, etc. based on what the source code was 
actually doing.


Around the same time, others in the forums were suggesting a 4GB 
minimum, so I decided to simply do away with the minimum spec and all 
the confusing language and caveats that went with itand simply 
say4GB recommended.


To solve this issue, I can look through my git logs and examine the 
language used in previous versioins of this document to find some 
compromise everyone is happy with.


But as someone said in the forum"If you can't dedicate more memory 
to the system than what is common to a cell phone, then perhaps you 
should not be running OI as your desktop".


Sorry for the long story...but that's how we arrived at a 4GB recommended.




http://makruger.github.io/website/pages/docs/handbook.html
Besides synchronizing to Handbook on the wiki, other notes:
1) Booting physical hardware - seems irrelevant, better to provide links
to illumos HCL and OI community HCL.
2) 2.1.2. Booting Virtual Hardware
No special tricks are required for Virtualbox, just mention to select os
type Solaris 11 64-bit.
3) 2.2. The OpenIndiana Boot Menu
  You should eventually be presented with a desktop. - irrelevant to
Text Install images.
4) Perhaps, need to mention that UEFI boot is still not supported.
5) 4.2  When you boot from the text installer, it immediately begins the
installation process using the previously described Text based Guided
Install.
Not entirely true, it also can spawn shell and be used as recovery image.



Admittedly, my skeleton of a handbook has not received very much 
attention as there are lots of problems with it. I've mostly just been 
tossing notes into it for future reference. I'll add your suggestions 
and, as I have time, begin to mold this document into something more 
useful. Just so you know, it's been my intention all along to start 
pulling in reusable content from the Wiki, etc.




Other general note. If we have to use some documentation tools to write
OI documentation, they should be available in OI repository. Perhaps
it's not true for IDEs, but basic tools should be there.



In the case of this website, there really aren't any tools. That's the 
beauty of it all. The site is completely self contained and inclusive of 
all it's documents. Creating or editing documents only requires a plain 
text editor (VIM, Gedit, etc.).


A Ruby development environment is only required when running the site 
locally in development mode, or when deploying it to github pages. Most 
contributors would never need to do any of that.


Thank you for taking the time to provide your feedback,

Michael

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

[OpenIndiana-discuss] Public Documentation License (terms)

[Michael Kruger]

Hello All,

Given the topic of licensing has come up several times in recent 
discussions, I thought this might be a good time to talk a little more 
about the PDL license and the terms it imposes on authored works subject 
to this license.


Below I have cobbled together a few things I found on the Internet, and 
have drawn a few conclusions from it all. Please let me know whether I 
am incorrect in any of my conclusions.


First, the firebird SQL website 
(http://www.firebirdsql.org/manual/licenses-pdl.html), gives the 
following summary of the PDL:


-

To give you a quick idea of what the PDL is all about, here is a short 
overview of the rights granted and requirements imposed by the PDL:


Free use: everyone may use and distribute PDL-licensed works, for free 
or for money, as long as the license notice is kept intact.


Right to modify: everyone may modify and redistribute PDL-licensed 
works, as long as any modified versions are PDL-licensed too, the 
original license notice is kept intact, and the modifications are 
documented.


Larger works: everyone may incorporate PDL-licensed documentation in a 
larger work. The larger work as a whole need not be released under the 
PDL, but the license requirements must be fulfilled for the PDL-licensed 
parts.


Please be advised that this overview is for informational purposes only 
and has no legal status whatsoever. Only the license text itself - 
following hereafter - is legally binding.


---

The site then follows it up with the full text of the license:

http://www.firebirdsql.org/manual/licenses-pdl-text.html

---

For an example of a license notice, there is the dtrace guide from 
dtrace.org (http://dtrace.org/guide/license.html)


This page says:

Public Documentation License Notice

The contents of this Documentation are subject to the Public 
Documentation License Version 1.01 (the "License"); you may only use 
this Documentation if you comply with the terms of this License. A copy 
of the License is available at http://illumos.org/license/PDL


The Original Documentation is the Solaris Dynamic Tracing Guide. The 
Initial Writer of the Original Documentation is Sun Microsystems 
Copyright (C) 2003-2009. All Rights Reserved. (Initial Writer 
contact(s): http://sun.com).


Contributor(s): Joyent, Inc. Portions created by Joyent, Inc. are 
Copyright (C) 2012. All Rights Reserved. (Contributor contact(s): 
http://joyent.com).


This documentation was derived from the source at illumos docbooks. For 
full changes as required by the PDL, please see the above URL.


-

The above example is essentially the PDL appendix with the blank spaces 
completed.


This suggests every PDL licensed document modified by the OpenIndiana 
community (for example each book included in the PDL licensed 
redistributable docs) would need to included such a notice.


Interestingly, not all of the redistributable books appear to include a 
visible PDL notice.


For example: 
http://makruger.github.io/website/pages/books/content/getstart/html/docinfo.html


I don't see a PDL notice listed anywhere on that page.

However, the XML sources for this book all include a license declaration.

https://github.com/makruger/website/tree/master/pages/books/content/getstart

So, what's going on here. Well, to  answer that question, you need to 
look at the HTML source:


https://github.com/makruger/website/blob/master/pages/books/content/getstart/html/docinfo.html

There it isa statement saying the document is subject to the PDL.

Other books are a bit more explicit about the license. For example on 
this page 
(http://makruger.github.io/website/pages/books/content/SYSADV1/html/docinfo.html), 
the license declaration is clearly listed.


Presumably only documents modified since their original publication 
would require a completed PDL appendix.


So, what about the 'OpenSolaris' book hosted on the Oracle website?
Are they PDL licensed as well?

The answer to that question is apparently NO.

The 'OpenSolaris' documents hosted on the Oracle website do NOT contain 
any such PDL license declaration either visibly or contained in the HTML 
source. I think it's safe to conclude PDF copies of these documents are 
not PDL licensed either.



Taking the discussion in a slightly different direction, and looking 
once more at the PDL licensed Dtrace guide on Dtrace.org, the following 
question comes to mind:


How exactly does one go about identifying the original portions from the 
Joyent modified portions?


The answer to this question is found in the last sentence of the license 
notice which says "see the above URL". This URL references the 
Illumos-Doc

Re: [OpenIndiana-discuss] Public Documentation License (terms)

[Michael Kruger]

On 05/17/2016 09:33 PM, Michael Kruger wrote:


So, if the content found on openindiana.org or wiki.openindiana.org were
PDL licensed, then it would also follow that any document created from
such content would then need to include all the contributor names in
it's PDL notice.

And if a large document such as a new handbook was created from such
content, then the list of contributors would need to include all the
authors from each and every source document.

While both of the websites support change tracking, this concern might
be completely irrelevant because none of the documents found on
openindiana.org appear to contain visible PDL license declarations or
notices.



One last thought on all this.

If the content found on OpenIndiana.org (wiki, www) is not PDL licensed 
(as far as I can tell, this appears to be a true statement), then the 
argument to use the PDL for new documents (for the sake of re-usability 
on OpenIndiana.org) does not seem to be valid.


Having said that, there may be other valid reasons...such as drawing 
content from the OpenSolaris books. In this case, the PDL makes more 
sense, but even then isn't actually a requirement.


Such a larger work could for example use the MIT license (as long as the 
terms of the PDL were met for the content which came from a PDL source). 
But in such a case, the PDL would probably make things less confusing 
and easier to manage.


Michael


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

[OpenIndiana-discuss] OpenIndiana Docs - Demo 2.0

[Michael Kruger]

Hello All,

I am happy to announce further development of the OpenIndiana Docs 
static HTML website concept. This latest demonstration site uses the 
MkDocs content authoring and static website generation framework. MkDocs 
uses Markdown as the text markup used for content authoring.


The website theme remains the same (Bootswatch/Spacelab). Supported are 
in-line HTML elements, as well as Font Awesome HTML elements.


Please go have a look:

Website: http://makruger.github.io/website-2.0/

GitHub repository: https://github.com/makruger/website-2.0


Michael

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

Re: [OpenIndiana-discuss] OpenIndiana Docs - Demo 2.0

[Michael Kruger]

On 06/12/2016 12:27 PM, Jerry Kemp wrote:


Wow Michael,

That's awesome.  Thank you.

Jerry


Hi Jerry, it gets even better

This afternoon we automated everything with Travis-CI. Now upon commit 
the site automatically runs through a series of validation tests. If 
everything passes, the site is automatically built and deployed to 
GitHub pages.


If you or anyone else has any suggestions for improvement, we're happy 
to listen. Simply open an issue on Github:


https://github.com/makruger/website-2.0/issues

Michael

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

Re: [OpenIndiana-discuss] OpenIndiana Docs - Demo 2.0

[Michael Kruger]

On 06/12/2016 03:59 PM, Nikola M wrote:


So doesn't look nice , not solving any issue and not needing any
"Organizing" into "Roles" right now, thank you.


Nikolam,

All criticisms set aside, you have to admit this new site looks simply 
fabulous on an iPhone.


Try that sometime with the OI wiki.

Michael



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

[OpenIndiana-discuss] OpenIndiana Docs - Demo 2.0 (Now with HTTPS & Travis-CI)

[Michael Kruger]

Update on this.

We're fully automated with continuous integration (via Travis-ci) and 
have enabled HTTPS. And just today added a new script that checks for 
broken URL's.


The updated site URL is: https://makruger.github.io/website-2.0/

Currently we have 3 contributors, but we definitely will need additional 
help as the momentum continues to build.


For anyone wishing to give contributing a test run, here's a direct link 
to the "Getting Started" doc:


https://makruger.github.io/website-2.0/contrib/getting-started/

More to come


Michael

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

Re: [OpenIndiana-discuss] OpenIndiana Docs - Demo 2.0

[Michael Kruger]

On 06/15/2016 04:37 AM, Alexander Pyhalov wrote:


Hi, Michael.

Let's consider things which should be done to make documentation site
official:
- provide quick links to the latest OpenSolaris 2009.06 documentation
collection, hosted on github or our servers;
- move all actual and relevant content of current handbook to new version;
- review new handbook content to avoid actual errors;
- move repository to OI organization;
- make look and feel of http://www.openindiana.org/ and documentation
site similar;
- provide links to illumos documentation, open zfs documentation where
necessary.

I welcome other ideas and suggestions, except "let's don't touch OI
docs", as they just don't exist now...


Hi Alexander,

I copied what you wrote above and created a github issue:

https://github.com/makruger/website-2.0/issues/49

Within this issue I referenced several additional issues, created to 
address these points individually.


If you or anyone else has anything else to add, feel free to add a 
comment to the issue, or reply back here.


Thank you for your suggestions,

Michael

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

Re: [OpenIndiana-discuss] OpenIndiana Docs - Demo 2.0

[Michael Kruger]

On 06/15/2016 05:31 AM, Udo Grabowski (IMK) wrote:



Since the new version of the docs is coded now, it should be
possible to add some javascript that detects users device
parameters and render the sites accordingly. There are
a lot of examples and ready to use code how to do that in javascript.
I think that should also be the goal of the new version to facilitate
dynamical rendering serving best the presently connected device.

I really hate those projects where that is fixed based on the
"majority" with a "standard" viewing device (like it happened
in Gnome3, Unity, and the like). The world has moved on to
modern dynamic technics, and the new docs project should use
those goodies to render dynamically from a lightweight coded
docs repository which Michael is developing now.


Hello Udo,

The new site uses the Bootswatch 'Spacelab' theme which is derived from 
Bootstrap 3. Bootstrap is a mobile first framework. From the ground up 
it was designed to be responsive and dynamically alter it's appearance 
to best suite the device used to view the page.


It's doing exactly what you describe, which is exactly what we need.

http://getbootstrap.com/

https://bootswatch.com/spacelab/

Thank you for your comments,

Michael

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

Re: [OpenIndiana-discuss] The latest version of OpenSSL and gcc installation

[Michael Kruger]

On 08/09/2016 03:59 PM, Aurélien Larcher wrote:


After this, I checked with OpenSSL version, but it is 1.0.2g.  Now, we
should upgrade to 1.0.2h which is the latest one.
I can see the latest one when I typed the command like pkg info -r
openssl.  How can I update this anyway?
The command should be like pkg update openssl?  I tried to do this, but
the
message I got was like "there is no image" or something like this.



pkg update updates the whole system. There is AFAIK no way to just one
package.


If contraints are relaxed you can pkg update a single package.


Looking at the Oracle docs for pkg(1), I see you can do something 
similar to the following:


pkg install vim@7.3.254,5.11-0.174

Or

pkg install vim@latest


And the [pkg update] command looks to accept the very same arguments.

For example:

pkg update vim@7.3.254,5.11-0.174

Or

pkg update vim@latest

Although pkg update when issued without any arguments will update all 
installed packages to their latest available version.


See: https://docs.oracle.com/cd/E23824_01/html/E21802/gihhp.html

Hope that helps,

Michael

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

[OpenIndiana-discuss] Installing mate and enabling lightdm

[Michael Kruger]

For the sake of any folks new to OpenIndiana (such as myself), I wanted 
to loosely document the process of installing the mate desktop and 
enabling lightdm.


1) Install the MATE desktop meta package (sudo pkg install mate_install)
2) Close out running applications and boot into single user mode (sudo 
init s).

3) Authenticate as root user
4) Disable the Gnome Desktop Manager (svcadm disable gdm)
5) Enable the LightDM desktop manager (svcadm enable lightdm)
6) Exit single user mode (exit)

There might be more elegant ways of doing this, but the steps above 
worked for me.


Hope that helps,

Michael

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

Re: [OpenIndiana-discuss] Installing mate and enabling lightdm

[Michael Kruger]

On 08/21/16 04:06 AM, Andreas Wacknitz wrote:

Hi

Am 21.08.16 um 02:51 schrieb Michael Kruger:
For the sake of any folks new to OpenIndiana (such as myself), I 
wanted to loosely document the process of installing the mate desktop 
and enabling lightdm.


1) Install the MATE desktop meta package (sudo pkg install mate_install)
2) Close out running applications and boot into single user mode 
(sudo init s).

3) Authenticate as root user
4) Disable the Gnome Desktop Manager (svcadm disable gdm)
5) Enable the LightDM desktop manager (svcadm enable lightdm)
6) Exit single user mode (exit)

There might be more elegant ways of doing this, but the steps above 
worked for me.



I simply changed ~/.dmrc to use mate instead of gnome.


Ah yes, somehow I completely overlooked mentioning how to change into 
the MATE desktop.

I used the selector at the logon screen, but thanks for sharing your method.

Michael


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

Re: [OpenIndiana-discuss] Installing mate and enabling lightdm

[Michael Kruger]

On 08/21/16 04:18 AM, Andreas Wacknitz wrote:



Am 21.08.16 um 02:51 schrieb Michael Kruger:
For the sake of any folks new to OpenIndiana (such as myself), I 
wanted to loosely document the process of installing the mate desktop 
and enabling lightdm.


1) Install the MATE desktop meta package (sudo pkg install mate_install)
I needed to remove the packages "userland-incorporation" and "entire" 
before that.


Hi Andreas,

I'm unfamiliar with the packages you mentioned, so I did a 'pkg info' on 
them.


The 'entire' package is an incorporation to lock all system packages to 
same build.
And 'userland-incorporation' is a meta package which constrains packages 
from the userland consolidation.


Can you tell me why removing these was necessary?

Thanks,

Michael



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

[OpenIndiana-discuss] Viewing CIFS shares with smbutil

[Michael Kruger]

Hello,

I have a rather strange problem with viewing CIFS shares.
Both client and server machine are running OI Hipster.
On the server I have 3 zfs datasets shared out via CIFS, but the CIFS 
client can only see one of them.

From the OI Hipster server, everything looks OK to me.
And I am able to access all these shares from the client machine using 
the MATE GUI tool caja-connect-server. I can also access them via a 
Linux GUI client.


Not sure why I am seeing this inconsistency.

Michael

(From the server):

# sharemgr show -vp
default nfs=()
smb smb=()
* /var/smb/cvol  smb=() ""
  c$=/var/smb/cvol   smb=(abe="false" 
guestok="false")  "Default Share"

zfs smb=()
zfs/storage/freeagent_backup smb=()
  freeagent_backup=/storage/freeagent_backup
zfs/storage/laptop_backup smb=()
  laptop_backup=/storage/laptop_backup
zfs/storage/wd500_backup smb=()
  wd500_backup=/storage/wd500_backup

(From the client):

$ smbutil view //172.16.0.107
ShareType   Comment
---
c$   disk   Default Share
IPC$ IPCRemote IPC
vss$ disk   VSS
wd500_backup disk

4 shares listed from 4 available

I also tried viewing the list of shares from a Linux command line. While 
it sees all the shares, it looks to be unhappy about netbios.


smbclient -L 172.16.0.107
WARNING: The "syslog" option is deprecated
Enter mike's password:
Domain=[WORKGROUP] OS=[SunOS 5.11 illumos-4cde22c] Server=[Native SMB 
service]


Sharename   Type  Comment
-     ---
c$  Disk  Default Share
wd500_backupDisk
ipc$IPC   Remote IPC
freeagent_backup Disk
laptop_backup   Disk
Connection to 172.16.0.107 failed (Error NT_STATUS_CONNECTION_REFUSED)
NetBIOS over TCP disabled -- no workgroup available

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

[OpenIndiana-discuss] No desktop after pkg update

[Michael Kruger]

Just did a pkg update on an instance of the Mate experimental release 
installed into vmware and it no longer boots to the desktop.

SSH apparently isn't running so I cannot ssh or scp to obtain the logs.
I didn't see anything obvious in the Xorg.0.log or in dmesg.
Anything else I should be looking for?

Thanks,

Michael

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

Re: [OpenIndiana-discuss] No desktop after pkg update

[Michael Kruger]

On 09/12/2016 04:50 AM, Till Wegmueller wrote:

Hey Michael.

Can you check which version of illumos you have ?
There are reports on Irc that there is a smf bug where services are not started.

See https://www.illumos.org/issues/7369 for details.

Greetings
Till


Thanks Till,

That looks to be the culprit. Lots of services offline. Rebooted into 
previous BE.


Michael

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

Re: [OpenIndiana-discuss] No desktop after pkg update

[Michael Kruger]

On 09/13/2016 07:55 AM, Francis.D wrote:

Hi,
Actually I can boot on BE Openindiana-1
  but I don't have Mate desktop environnment. Only mode console. It's seen a
bug from Illumos

thank


Hi Francis,

Yes, there is a SMF related bug  causing the desktop to fail to load. 
Boot back into the previous boot environment to revert the changes and 
you will have your desktop back.


Boot environments (or backup boot environments) are created each time 
you run 'pkg update'. In the case of the regular boot environments 
(opendindiana-1, -2, etc.) the packages are installed into the new boot 
environment and you boot into it. This provides a failsafe. In case 
something goes wrong, you simply boot back into your original boot 
environment.


Backup boot environments are different. Sometimes when software is 
installed, it is not necessary to create a new boot environment, so only 
a backup is created. You do not boot into these, unless of course 
something goes wrong and you need to revert your changes.


Michael

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

Re: [OpenIndiana-discuss] Upgrading to OI Hipster - Issues with smbshares

[Michael Kruger]

On 09/17/2016 02:12 PM, IT@Mitutoyo wrote:

What's weird is from my home system over vpn, I'm able to see the testing 
share, but no others. I tried setting abe=false on one of them, and that didn’t 
help. I tried setting the permissions back to everyone full control, and that 
didn't help either.



Something you said just triggered my memory.
Now I recall running into something similar a little while back.
Mind you this was a workgroup setup, not domain.

https://openindiana.org/pipermail/openindiana-discuss/2016-August/019344.html

Using smbview from an OI client system, I could only see one of my shares.
However, I could access them all via the GUI client (caja-connect-server).

Using smbview from a Linux client I could see them all (but it was 
complaining about netbios over TCP/IP being disabled).

And using KDE Dolphin I could access the shares just fine.

From a Windows 10 machine I could see and access them without any problems.

Michael

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

Re: [OpenIndiana-discuss] Hipster 16.04

[Michael Kruger]

On 09/21/2016 03:17 PM, Alexander Pyhalov wrote:

In hipster 16.04, can you specify a full two-disk mirror for root
right at the start of installing from live DVD media??


No, but you can follow 
https://wiki.openindiana.org/oi/Advanced+-+Creating+an+rpool+manually




Hi Alp,

While the article you provided would certainly provide greater control 
over the pool creation process, this all looks pretty complicated. How 
would OI be installed to such a pool?


Wouldn't it be easier to simply mirror the rpool after the installation 
has completed?


Michael



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

Re: [OpenIndiana-discuss] ntfs-3g

[Michael Kruger]

On 09/25/2016 02:09 PM, Apostolos Syropoulos via openindiana-discuss wrote:


  Hello,

I kust wanted to check ntfs-3g and I downloaded and installed the packages from

http://jp-andre.pagesperso-orange.fr/openindiana-ntfs-3g.html



There is also a package in the hipster repo:

system/file-system/ntfsprogs@2016.2.22,5.11-2016.0.0.2:20160730T020527Z 



However, I didn't have much luck getting that one to work either.

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

Re: [OpenIndiana-discuss] ntfs-3g

[Michael Kruger]

On 09/25/2016 04:24 PM, Adam Števko wrote:

HI,

out of curiosity, how was the NTFS created? When I tested this last, I was able 
to mount ntfs properly. However, the partition was created by ntfs-3g tools.

Adam


I don't recall as it's been a while since I tried. It was either created 
under Windows 10, or using gparted under Linux. I never considered 
trying to do it on OI. Seems to me the value of ntfs-3g would be 
diminished if it can only work with partitions and filesystems created 
by the tool itself.


For that matter, I'm curious whether a Windows system would respect a 
partition and NTFS filesystem created by ntfs-3g. I sure would hope so 
as this utility is, after all, to help provide interoperability.


Michael

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

Re: [OpenIndiana-discuss] pkg update error

[Michael Kruger]

Hi Glenn,

Sounds like you ran into this: 
https://www.openindiana.org/2016/08/29/possible-ssh-update-issue/


Michael


On 10/01/2016 12:11 PM, Glenn Holmer wrote:

What does it mean? What should I do?


root@shoggoth:/root# pkg update --be-name 2016-10-01
 Packages to remove:   7
Packages to install:  14
 Packages to update: 535
Mediators to change:   1
Create boot environment: Yes
Create backup boot environment:  No

DOWNLOADPKGS FILESXFER (MB)
  SPEED
Completed556/556 6247/6247  330.4/330.4
1.7M/s

PHASE  ITEMS
Removing old actions   2923/2923
Installing new actions 3596/3596
Updating modified actions  2955/7387Action upgrade
failed for 'etc/ssh/sshd_config'
(pkg://openindiana.org/service/network/ssh):
  TypeError: 'NoneType' object is not callable

The running system has not been modified. Modifications were only made
to a clone of the running system.  This clone is mounted at
/tmp/tmp2sBW_d should you wish to inspect it.
Traceback (most recent call last):
   File "/usr/bin/pkg", line 5444, in handle_errors
 __ret = func(*args, **kwargs)
   File "/usr/bin/pkg", line 5430, in main_func
 pargs=pargs, **opts)
   File "/usr/bin/pkg", line 2116, in update
 display_plan_cb=display_plan_cb, logger=logger)
   File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py",
line 1600, in _update
 logger=logger)
   File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py",
line 1476, in __api_op
 ret = __api_execute_plan(_op, _api_inst)
   File "/usr/lib/python2.7/vendor-packages/pkg/client/client_api.py",
line 1028, in __api_execute_plan
 api_inst.execute_plan()
   File "/usr/lib/python2.7/vendor-packages/pkg/client/api.py", line
2825, in execute_plan
 self._img.imageplan.execute()
   File "/usr/lib/python2.7/vendor-packages/pkg/client/imageplan.py",
line 4613, in execute
 p.execute_update(src, dest)
   File "/usr/lib/python2.7/vendor-packages/pkg/client/pkgplan.py", line
582, in execute_update
 dest.install(self, src)
   File "/usr/lib/python2.7/vendor-packages/pkg/actions/file.py", line
189, in install
 stream = self.data()
TypeError: 'NoneType' object is not callable


pkg: This is an internal error in pkg(5) version 33d20ff.  Please log a
Service Request about this issue including the information above and this
message.
root@shoggoth:/root#





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

[OpenIndiana-discuss] Updated OpenIndiana-Welcome

[Michael Kruger]

This is a request for comments for an updated OpenIndiana-Welcome doc...

Did a quick update of the doc which ships with OI and is presented the 
first time Firefox is run.


Please review and if you have suggestions for what else should be added 
to this, or would like to see something changed, please let me know.


Feel free to turn on change tracking and send me back an edited copy.

but please no bike-shedding.as I would like to see this get shipped 
with the next release.


ODT file is attached.

thanks,

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

Re: [OpenIndiana-discuss] fresh hipster install important tool no workee

[Michael Kruger]

On 10/25/2016 02:15 PM, Aurélien Larcher wrote:
=


Yes I was able to get a working system from this ISO in three
VirtualBox instances last month.
Each of them has 3GB RAM and 24GB disk.


That's about what I would recommend for resources when running OI as a 
virtual guest with a GUI. Although in practice it's worked for me with 
as little as 2GB. Though on bare metal I have seen pkg burn through the 
RAM and swap file and then crash when given so little memory.


Also, I believe the command 'pkg image-update -v' has been deprecated in 
favor of 'pkg update -v'. That could be the problem as well.


Michael

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

Re: [OpenIndiana-discuss] Updated OpenIndiana-Welcome

[Michael Kruger]

Whoops...sent an old version. Here is the latest version with the fix.

Michael


On 10/23/2016 10:54 PM, Michael Kruger wrote:

This is a request for comments for an updated OpenIndiana-Welcome doc...

Did a quick update of the doc which ships with OI and is presented the
first time Firefox is run.

Please review and if you have suggestions for what else should be added
to this, or would like to see something changed, please let me know.

Feel free to turn on change tracking and send me back an edited copy.

but please no bike-shedding.as I would like to see this get shipped
with the next release.

ODT file is attached.

thanks,

Michael

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

[OpenIndiana-discuss] Looking for translators for the updated 'openindiana-welcome'

[Michael Kruger]

Hello All,

I've committed the updates to my fork of openindiana-welcome.

https://github.com/makruger/openindiana-welcome

So, at this time I would like to invite the community to submit 
translations.


Translations reside in the folder data/html. Each translation requires a 
subfolder (for example 'de for german).


I'll be happy to convert the translations to html, so the changes can be 
committed to the repository. Or, if you like, you can fork my fork and 
submit me a PR.


I've pasted the entire text below.

Michael
=


OpenIndiana Logo
Welcome to OpenIndiana Hipster!

OpenIndiana is an illumos based Unix-like distribution derived from 
OpenSolaris. Constructed as a general purpose operating system with 
enterprise class features, OpenIndiana Hipster is developed by the 
community, and for the community.


OpenIndiana obtains its name from Project Indiana, an open source effort 
by Sun Microsystems (now Oracle Corporation) to produce OpenSolaris, a 
community developed Unix-like distribution based on Sun Solaris. Project 
Indiana was led by Ian Murdock, founder of the Debian Linux Distribution.


Some of the differences between OpenIndiana and OpenSolaris can be 
characterized as follows:


Sun's OS/NET consolidation (closed by Oracle) has been replaced 
with illumos-gate.


Many of the original OpenSolaris software consolidations have been 
reorganized into a single oi-userland consolidation.


Oracle's Sun Studio has been replaced with the open source GNU GCC 
compiler.


XVM (XEN) has been replaced with the illumos-kvm port.

OpenIndiana Hipster Enterprise Class Features
Feature Description
ZFS File System and Volume Manager
Dtrace  Dynamic Tracing Framework (System Introspection)
CrossbowNetwork Virtualization and Resource Control
SMF Service Management Facility
FMA Fault Management Architecture
COMSTAR Common Multiprotocol SCSI Target (ISCSI Target Framework)
KVM Kernel-Based Virtual Machine (Operating System Virtualization)
Zones   OS Level Virtualized Application Containers
Time-Slider Automated ZFS Snapshots and Rollbacks
RBACRole-Based Access Control
IPMPIP Network Multipathing
DLMPData Link Multipathing

Release Notes
https://wiki.openindiana.org/oi/Release+Notes

About Us

The OpenIndiana Project is a community of volunteers and UNIX 
enthusiasts from around the world. Currently build servers, hosting and 
bandwidth is donated by EveryCity hosting in the UK.


Getting Involved

Our success as a distribution depends upon the success of our community, 
which is why we would like to invite all those interested in the future 
of OpenIndiana to participate and get involved!


We have many resources from which you can get started, including our 
Wiki, Mailing Lists and IRC Channel.


For developers we have Vagrant development images which can be 
easily deployed.


For end users we have publicly available IPS repositories for 
updating your installation with the latest software and security fixes.



Links

Website: https://openindiana.org

Wiki: https://wiki.openindiana.org

Mailing Lists: http://openindiana.org/mailman

IRC Channel: #openindiana on irc.freenode.net


License
OpenIndiana Licensing Information

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

Re: [OpenIndiana-discuss] Looking for translators for the updated 'openindiana-welcome'

[Michael Kruger]

Update:

We have the following translations now:

French
Greek
Russian

And Francis is currently working on the Portuguese (Brazil) translation.

Translation wish list (in no particular order):

Slovenian
Serbian
Italian
Chinese
Japanese
Spanish

I've attached the US English version as an attachment.

(Sorry, I know these attachments aren't making it to the discussion 
list, but if you respond back to me directly, I'll be happy to send you 
a copy)


Michael



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

Re: [OpenIndiana-discuss] Looking for translators for the updated 'openindiana-welcome'

[Michael Kruger]

Hello,

Thank you very much for your contribution. I am very happy to see so 
many contributions. I'll get this coded so it will be included in the 
next release.


Michael


On 10/31/2016 04:38 AM, Matjaž M wrote:

Hi,

I guess there are not many Slovenes here, so I did it …

———
OpenIndiana Logo
Dobrodošli v OpenIndiana Hipster!

OpenIndiana je Unixu podobna distribucija, ki temelji na Illumusu, ta pa je 
izveden iz OpenSolarisa. Zgrajena je kot splošno namenski operacijski sistem z 
lastnostmi, potrebnimi v podjetjih. OpenIndiana Hipster je razvila skupnost za 
skupnost.

OpenIndiana je ime dobila iz Projekta Indiana, odprtokodnega podviga Sun 
Microsystems (zdaj Oracle Corporation), katerega namen je bil izdelati 
OpenSolaris, skupnostno, Unixu podobno distribucijo, temelječo na sistemu Sun 
Solaris. Projekt Indiana je vodil Ian Murdock, ustanovitelj Distribucije Linux 
Debian.

Nekatere razlike med OpenIndiano in OpenSolarisom so opisane spodaj:

Sunovo konsolidacijo OS/NET (ki jo je Oracle zaprl) smo zamenjali z 
illumos-gate.

Številne originalne programske konsolidacije v OpenSolarisu smo 
reorganizirali v enotno konsolidacijo oi-userland.

Oraclov Sun Studio smo zamenjali z odprtokodnim prevajalnikom GNU GCC.

XVM (XEN) smo zamenjali z illumos-kvm.

Lastnosti sistema OpenIndiana, primerna za podjetja:
LastnostOpis
ZFS Datotečni sistem in volume manager
Drtace  Orodje za dinamično sledenje procesom
CrossbowNadzor nad virtualizacijo omrežja in sredstev
SMF Sefvice Management Facility, sistem za upravljanje s storitvami
FMA Fault Management Architecture, sistem za upravljanje z napakami
COMSTAR Common Multiprotocol SCSI Target (sistem podpore za ISCSI 
Target)
KVM Kernel-Based Virtual Machine (virtualizacija operacijskih sistemov)
Zones   Virtualizirani aplikacijski kontejnerji na nivoju operacijskega sistema
Time-Slider Orodje za avtomatsko izdelavo ZFS posnetkov in povrnitev v 
prejšnje stanje
RBACRole-Based Access Control, nadzor nad dostopom na podlagi vlog
IPMPIP Network Multipathing
DLMPData Link Multipathing

Obvestila ob izdaji
https://wiki.openindiana.org/oi/Release+Notes 
<https://wiki.openindiana.org/oi/Release+Notes>

O nas

Projekt OpenIndiana je skupnost prostovoljcev in UNIX entuziastov z vsega 
sveta. Trenutno strežnike za izgradnjo sistema, gostovanje in pasovno širino 
donira EveryCity hosting v Združenem kraljestvu.

Kako se nam lahko pridružite?

Uspeh naše distribucije je odvisen od uspeha naše skupnosti, zato bi radi 
povabili vse, ki jih zanima prihodnost OpenIndiane, da sodelujejo in se 
vključijo!

Imamo veliko virov, s pomočjo katerih lahko začnete, vključno z Wiki, poštnim 
seznamom in kanalom IRC.

   Za razvijalce imamo slike Vagrant, ki jih je enostavno uporabiti.

   Za končne uporabnike imamo javno dostopne repozitorije IPS, s katerimi lahko 
posodobite vašo namestitev z najnovejšimi programi in varnostnimi popravki.

Povezave

   Spletna stran: https://openindiana.org <https://openindiana.org/>

   Wiki: https://wiki.openindiana.org <https://wiki.openindiana.org/>

   Poštni seznami: http://openindiana.org/mailman 
<http://openindiana.org/mailman>

   Kanal IRC: #openindiana na irc.freenode.net <http://irc.freenode.net/>


Licenca
Podatki o licenciranju OpenIndiana


On 30. okt. 2016, at 01:35, Michael Kruger  wrote:

Update:

We have the following translations now:

French
Greek
Russian

And Francis is currently working on the Portuguese (Brazil) translation.

Translation wish list (in no particular order):

Slovenian
Serbian
Italian
Chinese
Japanese
Spanish

I've attached the US English version as an attachment.

(Sorry, I know these attachments aren't making it to the discussion list, but 
if you respond back to me directly, I'll be happy to send you a copy)

Michael



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


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



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

Re: [OpenIndiana-discuss] Looking for translators for the updated 'openindiana-welcome'

[Michael Kruger]

On 10/31/2016 05:03 AM, Predrag Zečević - Technical Support Analyst wrote:



Hi,

I am in the process of translating/adopting it to Serbian language.

With best regards.
Predrag Zečević

=



Great, looking forward to it.

Michael

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

[OpenIndiana-discuss] Hipster Handbook updates

[Michael Kruger]

Hello All,

Lots of activity to report on the new Hipster Handbook.

http://docs.openindiana.org

This past week I've updated the docs site to include details for:

* Using the new FreeBSD boot loader
* Using the new ZFS rpool options provided by the text installer
* Added a basic Git usage guide for documentation contributors


While the most basic of topics are now covered for installing and using 
our wonderful operating system, the new Hipster Handbook still needs 
much love.


The next stage in our documentation transformation is to begin migrating 
end user related Wiki content to the new handbook. We'll be pulling in 
content which is still valid and marking old outdated pages as deprecated.


In either case, whenever anyone works on a page to migrate or deprecate 
the content, I ask that they also kindly leave a note redirecting people 
to the new site (docs.openindiana.org).


As for the areas where the handbook needs content, here is a short 
(non-inclusive) list. If you have additional ideas, that's OK too.


While I would encourage people to fork the oi-docs repo and give the 
mkdocs framework a try (especially since I wrote a nice little guide to 
using Git), you're also welcome to contribute content in any way you 
like by emailing your contribution (in any format) to [DOCS AT 
Opendiana.org]



* The X-Window system
* Working with Device Drivers
* Basic Unix Commands
* Basic System Administration
* Desktop Applications
* Multimedia - Audio
* Multimedia - Video
* Printing
* Fault Management
* Service Management
* Systems logging and monitoring
* The illumos boot process
* Security
* Zones
* Storage - Mounting file systems
* Storage - NTFS support
* Storage - ISCSI
* Storage - Configuring Backup software
* Storage - ZFS Configuration and usage
* Virtualization
* Localization
* Dtrace
* Networking - Local Configuration
* Clustering
* Firewalls
* Advanced networking (Crossbow, etc.)
* NAS Storage Server (CIFS/Samba/NFS)
* NIS and LDAP
* DHCP
* WWW/FTP
* DNS
* NTP
* INETD



Thank you for supporting this effort,

Michael



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

Re: [OpenIndiana-discuss] OI hipster frequence freeze during update

[Michael Kruger]

On 12/30/2016 06:56 PM, Full Name wrote:

I've 2GB RAM on the system.   The system has 32-bit intel processor.

how do i check swap/raw partition?


Pulled this from my personal notes for future docs to write.
It shows how to check and enlarge the swap.
Hopefully you can make sense of it.

Michael



Check swap space and adding more

# swap -l
swapfile devswaplo   blocks free
/dev/zvol/dsk/rpool/swap 283,2 8  2060280  1295128

If blocks and free are the same, then the swap space isn't being used 
and it can be resized.
In this case, half of the space is being used (definitely an indication 
the system could use more memory)


So, we have to add another swap filesystem.

# zfs create -V 2G rpool/swap2

Now we have to activate it.

# swap -a /dev/zvol/dsk/rpool/swap2

And check the available space again

# swap -l
swapfile devswaplo   blocks free
/dev/zvol/dsk/rpool/swap 283,2 8  2060280  1299488
/dev/zvol/dsk/rpool/swap2 283,3 8  4194296  4194296

Here is an update listing of all the filesystems. Swap and Swap2 are 
listed last.


# zfs list
NAME   USED  AVAIL  REFER  MOUNTPOINT
rpool 9.38G   440G  30.5K  /rpool
rpool/ROOT5.24G   440G19K  legacy
rpool/ROOT/openindiana20.7M   440G  3.81G  /a
rpool/ROOT/openindiana-1  5.22G   440G  3.82G  /
rpool/ROOT/openindiana-1/var  1.39G   440G   943M  /var
rpool/ROOT/openindiana/var4.46M   440G   975M  /a/var
rpool/dump1006M   440G  1006M  -
rpool/export  44.1M   440G19K  /export
rpool/export/home 44.1M   440G19K  /export/home
rpool/export/home/mike44.0M   440G  44.0M  /export/home/mike
rpool/swap1.04G   441G   650M  -
rpool/swap2   2.06G   442G 8K  -

***NOTE*** adding swap space creates a persistant swap filesystem, but 
the activation does not persist after a reboot.

Probably need to add the 2nd swap space to /etc/vfstab

Also, after a reboot (and before logging into the GUI desktop), the swap 
may not any longer be in use.
This would be a good time to ssh into the system and increase the size 
of the original swap volume.

You could either leave the 2nd swap volume, or remove it.

To increase the space, first verify it's really still free.

swap -l
swapfile devswaplo   blocks free
/dev/zvol/dsk/rpool/swap 283,2 8  2060280  2060280
/dev/zvol/dsk/rpool/swap2 283,3 8  4194296  4194296

Now lets look at the how big the volume really is.

# zfs get volsize rpool/swap
NAMEPROPERTY  VALUESOURCE
rpool/swap  volsize   1006Mlocal

At 1GB, it's pretty small. Lets enlarge it to 4 GB instead.

# zfs set volsize=4g rpool/swap

Now lets have another look at it.

# zfs get volsize rpool/swap
NAMEPROPERTY  VALUESOURCE
rpool/swap  volsize   4G   local

That's much better. We're much less likely to run out of /tmp space now.

NOTE: swap -l will still show the old swap file size until the system 
reboots.
Not sure exactly what this means, but perhaps the new size does not take 
effect until after the reboot.


# zfs list
NAME   USED  AVAIL  REFER  MOUNTPOINT
rpool 14.2G   435G  30.5K  /rpool
rpool/ROOT6.88G   435G19K  legacy
rpool/ROOT/openindiana20.7M   435G  3.81G  /a
rpool/ROOT/openindiana-1  14.2M   435G  3.82G  /
rpool/ROOT/openindiana-1/var  8.37M   435G   993M  /var
rpool/ROOT/openindiana-2  6.85G   435G  4.07G  /
rpool/ROOT/openindiana-2/var  1.64G   435G   901M  /var
rpool/ROOT/openindiana/var4.46M   435G   975M  /a/var
rpool/dump1006M   435G  1006M  -
rpool/export  44.1M   435G19K  /export
rpool/export/home 44.0M   435G19K  /export/home
rpool/export/home/mike44.0M   435G  44.0M  /export/home/mike
rpool/swap4.25G   439G   699M  -
rpool/swap2   2.06G   437G  51.2M  -


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

Re: [OpenIndiana-discuss] OI hipster frequence freeze during update

[Michael Kruger]

On 12/31/2016 11:45 AM, Full Name wrote:

Indeed, my swap blocks and free sizes are the same, so no swap is being 
utilized.

so i followed each step in your note to create 'swap2' and enlarged the size to 
'4G'.

then i rerun:
# pkg set-publisher -G  http://pkg.openindiana.org/hipster-2015 -g  
https://pkg.openindiana.org/hipster  openindiana.org

it stuck at 'refreshing catalog 1/1 openindiana.org 69.38kB',  with mouse 
cursor blinking at the end.   i waited for 30 minutes and nothing changes.
at this stage, graphics icons on the desktop stopped responding to clicks, 
can't open 'firefox' 'terminal' etc.


-erdos



Virtual machines can generally run with 2GB without any issues, but in 
my experience physical hardware requires either more memory, or an 
enlarged swap file.


However, I just noticed your previous post mentioned you were using a 32 
bit processor and OI no longer supports 32 bit machines. So, perhaps 
you're running into some kind of issue related to this.


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

Re: [OpenIndiana-discuss] The end is near

[Michael Kruger]

Solaris on Sparc looks to be dead and (it appears) i386 as well, but 
against all odds, OpenIndiana somehow lives on. For i386 users that 
might actually be helpful to the project. Maybe it could mean more users 
and more developers.


As for Oracle though, it would seem their killing off OpenSolaris in 
2010 was a bit shortsighted.


Michael

On 01/23/2017 02:14 PM, Bob Friesenhahn wrote:

The end is apparently even nearer than presumed:

http://www.zdnet.com/article/oracle-lays-off-more-than-1000-employees/

Bob


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

Re: [OpenIndiana-discuss] The end is near

[Michael Kruger]

On 01/23/2017 08:31 PM, Tomasz Kłoczko wrote:


Can you show any facts/numbers supporting such thesis?
Do you know anything about abandoning any Oracle internal projects in which
some work on new Solaris features has been or will be abandoned?
Is it not kind of contradiction with your claim that Solaris on Sparc is
dead that on roadmap is release v2 software in silicone? and/or do you know
anything about any existing or upcoming releases of other CPU platforms
technologies bringing functionalities of Sparc v1 software in silicone?

kloczek
PS. please be serious and do not mention changes in versioning as
supporting fact.



No, my evidence is purely anecdotal and soley based on the prima facie 
value of the company sacking 40% percent of the sparc team.


Michael

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

Re: [OpenIndiana-discuss] Recent Wiki Changes unchanged for two months

[Michael Kruger]

On 03/24/2017 08:49 AM, Aurélien Larcher wrote:

On Fri, Mar 24, 2017 at 1:45 PM, Gary Mills  wrote:


It's now been two months since this page:

https://wiki.openindiana.org/oi/Recent+Wiki+Changes

last changed.  Is something wrong?

Same as usual I guess.




Sadly, in the case of the new Docs site, it really hasn't changed (much) 
in 2 months. It's kind of like owning a a shiny new car only to let it 
sit in the driveway for months on end.


Yep, I am encouraging folks to step up and help expand the base of 
knowledge which helps the OpenIndiana community.


I'd love to continue helping, but I simply haven't the time anymore.

Michael

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

[OpenIndiana-discuss] really nice stuff

[Michael Kruger]

Hello friend, 

I've been looking for some stuff on the web and suddenly came across that! You 
should  see that, I swear  you'll love it! More info here 
http://www.ppjsvihar.in/cry.php?e4e5

My best to you, Michael Kruger

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

Re: [OpenIndiana-discuss] Hardware to run OpenIndiana ...

[Michael Kruger]

On 12/27/2017 07:33 PM, Till Wegmüller wrote:


I have it running on a HP Proliant Microserver Gen10 and I know that
Gen8 works well too.


Really? I would think Gen 10 would be UEFI?
Does Hipster now support UEFI?

Michael

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