clustering talk

{|-

stuff

-|}

<john>testing</john>

~~TAGCLOUD~~

${a}

1. cd /tmp
2. umask 22
3. wget package
4. extract package into /tmp
5. run stem:
   

   stem -add packageName-Version Dest -skiprcs -objs solaris9

   
   

   example: stem -add atk-1.18.0 X -skiprcs -objs solaris9

6. go to the /src/DEST/packageName-Version directory
7. copy the README.AcIS from the previous version's directory, and change applicable package version info
8. follow the README.AcIS instructions to finish configuring
9. after configure, diff -u ../oldVersion/config.h config.h | less to see if there are any major changes
10. if no major changes, run make
11. make the destination dir, /opt/packageName-Version
12. chown jf659 /opt/packageName-Version
13. chmod 2755 /opt/packageName-Version
14. make sure umask 22
15. make install
16. cd /opt/packageName-Version
17. strip binaries:
    

    find -type f | xargs file | grep "stripped" |cut -f 1 -d : | xargs strip

18. chown -R root:staff /opt/packageName-Version
19. tar the package (tar czf /tmp/packageName-Version.tgz /opt/packageName-Version

1. connect to dill
2. https://www1.columbia.edu/sec/acis/sy/systems-manual/Linux/hp_linux_console.html
3. connect to shrimp, and run
   

   sc -i unix check whelk

   where “whelk” is the host you are checking

cat cubmail-4.diff |nenscript -2Gr -P watson7a

UMich does this

• http://www.openldap.org/lists/openldap-software/200411/msg00359.html
• http://www.umich.edu/~dirsvcs/ldap/doc/guides/slapd/

• cfengine
• http://puppet.reductivelabs.com/

• http://www.zenoss.com
• http://rsug.itd.umich.edu/software/nefu/

1. come up with short, unique, and descriptive namespace names for all the initial and potential groups using this wiki
2. decide on how locked down the wiki is (can anyone with a cunix id log in, or only people with the CUIT affiliation?)
3. setup the inital acl rules and test to ensure everything works as expected (can we create a wiki-test type user?)
   1. document the acl setup, and how to add new groups/permissions
4. review currently installed plugins and see if we need to add any
5. create standard usage recommendations
   1. namespace templates
   2. tagging
   3. general namespace organization
   4. user management
6. group contacts
   1. create a mailing list of each group's primary wiki contact to notify of wiki maintenance etc. and to discuss plugins, wiki usage, feature requests, etc.)
   2. decide if we need group administrators (probably the same people who are the group contacts) with limited admin access (but would allow group admins to add users to their “owned” namespace)
7. make it easy to access wiki syntax/usage information and examples
   1. create a user-editable (and generally user-answerable) wiki area for users to ask for help (basically like bulletin board)
8. create a feature request page for general users (different from a group admin requesting a feature via the wiki mailing list)
9. finalize pamacea authentication plugin (allow one to add users via the web-interface)
10. theme the wiki to match either Columbia's or CUIT's webpage style

thoughtbit

here is a bunch

a thoughtbit is a cool thing

of white space to fill up

all this space here to make the page scroll down

and down

and down

down

…

down

down

Ctrl+Alt+Del

Ctrl

Friggity Frack is cool

thoughtbit

The name of my really cool website.

subdef

test 2

   ? Definition Title
     Multiple lines are possible
   ! Definition Description
   ? Definition Title1
   ? Definition Title2
   ! Definition Description1
   ! Definition Description2
   ! Definition Description3
     ? Subdefinition
     ! Description
   ! Back
     ? Again deeper

this is header test 1 text

header test 2 text

header test 3 text

now if I want this text under header test 2, I have to do

this

and back to header 1

header test 2b text

now imagine that I want this text under the “header test 1” header. it's not there. until…

here

• Do a new computer installation (insert link to Windows XP Domain setup instructions)
• Remedy

• networking tools for full-time employees:
• whither
• switchmgr
• domain password reset