michelle olson wrote: > This is alpha review of the OpenSolaris User FAQ. It is intended to > answer questions asked by new users, refer them to all the other FAQ > resources available, and is a work-in-progress. > > http://www.genunix.org/wiki/index.php/FAQ_Prototype
General nits: - Is there any way to make the master of this file a DocBook/XML file that we convert it to single/multipage HTML, PDF etc. ? IMO Wikis are nice for online usage but have only limited use for printed media and other uses (e.g. convertion to manpage format etc.) - ZFS is there but both QFS and UFS are missing - Question: "Where can I download Solaris/Solaris Express ISO images" ? Answer: See http://www.opensolaris.org/os/downloads/ (and please find someone who can describe the difference between "Solaris Express Community Edition" and "Solaris Express Developer Edition" - I always forget which of these I have to avoid and usually I have to click around until I get the stuff with the newest Nevada release...) > The are a couple of unanswered questions about boot up and partitions, > if anyone can help there. There is a section for ZFS that doesn't yet > include links to the best practices doc on solaris internals. > > Plus Q/As for the new user about general OSOL information, installation, > log in, networking, DTrace, What about making an item "diagnostics tools" and make "Dtrace" a sub-item ? IMO there are other usefull tools (like "coreadm" which is able to track core dump generation and log it into the system log). Two items for this section: 1. coreadm: -- snip -- Question: "How can I see if an application, service or any other process crashed ?" Answer: "Enable coreadm like this: $ mkdir -p /var/core ; coreadm -g /var/core/core.uid%u.gid%g.pid%p.%f -e global -e process -e log -e global-setid # - this will send a notification of any generated core dumps to the system log (/var/adm/messages) and put a copy of the core dump into /var/core/" -- snip -- 2. pstack: -- snip -- Question: How can I get a stack trace from a core dump when I don't have a debugger installed ? Answer: Use $ /usr/bin/pstack <name-of-coredump> # to get the stack trace -- snip -- > NFS, ZFS, What about making an item "Filesystems" and make "UFS", "ZFS" and "QFS" sub-items ? > Zones, Upgrading, Shells, Minor update for shells (quoted lines are the old text): -- snip -- > Q: Why isn't bash the default shell? > > A: Ksh93 is a better shell. It is more standards compliant, has all of the > features you love about bash, and more. It also happens to be the best > scripting shell available. Erm, neither "bash" or "ksh93" are the "default shell". IMO the term "default shell" itself is a problem because there is no "default shell", the nearest terms may be "default system shell" (=/bin/sh) and "default user shell" (e.g. the shell used by default when a new user is created (which is unfortunately /bin/sh)). Most of the ravings&&rants are AFAIK about /bin/sh which is the "Bourne shell" (not "bash" (="Bourne Again Shell")) and not a POSIX shell (like "bash" in POSIX mode) as many applications and users seem to expect. Problem is now how to phrase it (I'm notoriously bad at that stuff...) ... > Q: Where can I find more info on ksh93? > > A: Check http://www.kornshell.com/doc/ (In particular, the book "The New > KornShell" is an excellent resource.) > Q: What shells are available for use with end-user accounts? Could you please add http://www.opensolaris.org/os/project/ksh93-integration/ to that list (at least until we have the new ksh93s+ manual page online) ? > A: bash, csh, jsh, ksh, ksh93, sh, tcsh, zsh Erm, it may be better to list the full paths, e.g. /usr/bin/bash, /usr/bin/jsh, /usr/bin/ksh, /usr/bin/ksh93, /usr/bin/sh, /usr/bin/tcsh, /usr/bin/zsh -- snip -- ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
