about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorahriman <ahriman@falte.red>2019-04-24 23:59:58 +0000
committerahriman <ahriman@falte.red>2019-04-24 23:59:58 +0000
commit02a0b396b499f0d645c1905b02b0686d939167b7 (patch)
tree72e8872356e1976e27a2f4b08bf2a225beb95bdd
parent3caf4cbae7f16e25bf33f7afb98274458c6b60e7 (diff)
downloadsite-02a0b396b499f0d645c1905b02b0686d939167b7.tar.gz
removed old wiki
-rw-r--r--wiki.php52
-rw-r--r--wikipages/README.md23
-rw-r--r--wikipages/bchs.wiki21
-rw-r--r--wikipages/dcss.wiki46
-rw-r--r--wikipages/finger.wiki42
-rw-r--r--wikipages/gettingstartedcommands.wiki40
-rw-r--r--wikipages/gopher.wiki74
-rw-r--r--wikipages/gpg-for-ssh-auth.wiki28
-rw-r--r--wikipages/irc.wiki14
-rw-r--r--wikipages/password-store.wiki88
-rw-r--r--wikipages/template.wiki19
-rw-r--r--wikipages/unixprotips.wiki29
12 files changed, 0 insertions, 476 deletions
diff --git a/wiki.php b/wiki.php
deleted file mode 100644
index 39d4a0e..0000000
--- a/wiki.php
+++ /dev/null
@@ -1,52 +0,0 @@
-<!DOCTYPE PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/1/DTD/1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/" lang="en" xml:lang="en">
-<head>
-        <meta http-equiv="Content-Type" content="text; charset=utf-8" />
-        <meta name="viewport" content="width=device-width, initial-scale=1" />
-        <title>tilde.institute :: Wiki</title>
-        <link rel="stylesheet" href="tilde.css" type="text/css"/>
-        <link rel="icon" type="image/png" href="icon.png"/>
-</head>
-<body>
-<div id="container">
-	<div id="logo">
-        <img src="logo.png" alt="" /><br />
-		<div id="logobyline">
-			of OpenBSD Education
-		</div>
-	</div>
-	<div id="navigation">
-		<a href="http://tilde.institute">News</a> :: <a href="/signup">Sign Up</a> :: <a href="/coc">Code of Conduct</a> :: <a href="https://tilde.zone/@tildeinstitute">Mastodon</a> :: <a href="https://wiki.tilde.institute">Wiki</a> :: <a href="https://tildegit.org/institute">Git</a> :: <a href="/stats">Stats</a>
-	</div>
-	<div id="content">
-    <?php
-        if (!isset($_GET["page"]) || !file_exists("wikipages/{$_GET['page']}.wiki")) {
-    ?>
-
-        <h2>~institute wiki</h2>
-        <p>Welcome to the tilde.institute wiki</p>
-
-	<p>If you are new here, you likely want to check out the <a href="wiki.php?page=gettingstartedcommands">"getting started" page</a>"</p>
-
-        <p>If you know your way around and want to contribute to the wiki, check out the
-        <a href="https://tildegit.org/institute/site/src/branch/master/wikipages">repository</a> and open a PR!
-        </p>
-
-        <h3>Pages:</h3>
-        &nbsp;&nbsp;<a href="wiki.php?page=bchs">BCHS Intro Guide</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=dcss">Dungeon Crawl Stone Soup</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=finger">Finger</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=gopher">Getting Started With Gopher</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=gpg-for-ssh-auth">GnuPG for SSH Authentication</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=irc">IRC</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=password-store">password-store Usage Guide</a><br />
-        &nbsp;&nbsp;<a href="wiki.php?page=unixprotips">UNIX ProTips</a><br />
-        <?php
-
-        } else {
-            include("wikipages/{$_GET['page']}.wiki");
-        } ?>
-	</div>
-</div>
-</body>
-</html>
diff --git a/wikipages/README.md b/wikipages/README.md
deleted file mode 100644
index da9cf0b..0000000
--- a/wikipages/README.md
+++ /dev/null
@@ -1,23 +0,0 @@
-To contribute to the wiki, create a page using the same pattern as the previously existing pages and submit a pull request.
-
-Step-By-Step:
-
-Fork this repo
-
-git clone https://tildegit.org/your_username/site.git
-
-cd site
-
-git checkout -b my-wiki-page-etc
-
-cd wikipages
-
-Add your page following the same format as the existing pages
-
-git add .
-
-git commit -m "added page whatchamacalit to wiki"
-
-git push
-
-Then from the tildegit.org web interface, open a pull request to this repository from your fork/branch
diff --git a/wikipages/bchs.wiki b/wikipages/bchs.wiki
deleted file mode 100644
index de41703..0000000
--- a/wikipages/bchs.wiki
+++ /dev/null
@@ -1,21 +0,0 @@
-<!--
-    author: ahriman
-    title: BCHS Guide
-    description: a quick intro to what the BCHS stack is
--->
-<h2>BCHS Guide</h2>
-<p>This will be a quick-and-dirty guide to getting started with the BCHS stack. More information can be found at:</p>
-    <ul>
-        <li><a href="https://learnbchs.org">Learn BCHS</a></li>
-        <li><a href="http://man.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man2/pledge.2">pledge(2)</a></li>
-        <li><a href="http://man.openbsd.org/unveil.2">unveil(2)</a></li>
-        <li><a href="https://kristaps.bsd.lv/kcgi/">kcgi</a></li>
-        <li><a href="https://kristaps.bsd.lv/ksql/">ksql</a></li>
-        <li><a href="https://kristaps.bsd.lv/kwebapp">kwebapp</a></li>
-    </ul>
-<p>tilde.institute is set up to process all files with the .cgi extension via slowcgi(8). This allows for a multitude of possibilities - any compiled language can be used to develop web applications on an OpenBSD server. It's advised to use C because of the pledge(2) and unveil(2) system calls available, which allow for restricting privileges and restricted filesystem access, respectively.</p>
-<p>Keep in mind that if you don't use the previously listed kcgi/ksql/kwebapp libraries, you will need to work with HTTP's eccentricities manually. For an example, here's <a href="helloworld.c.txt">the Hello World code</a> from the LearnBCHS site. And <a href="helloworld.cgi">here it is running</a> as compiled CGI here at the Tilde Institute.</p>
-<p>Once you've written your software to be served via CGI, be sure to statically link the executables. Sure, there's a larger file size, but the benefits outweigh that in this case - there's no relying on what I may or may not have installed on the Tilde Institute's server. For example:</p>
-<p><code>$ cc -static -g -W -Wall -o app.cgi app.c</code></p>
-<p>When you've completed compilation, make sure to set permissions properly (755) and move it to the public folder in your home directory. httpd(8) is set to use index as the index file, however this can be changed to index.cgi or what-have-you by contacting ahriman via IRC.</p>
-<p>~institute user <code>xvetrd</code> has written a more detailed example on kcgi than is provided on the library's site. It includes an example makefile as well. The KCGI Starter archive <a href="kcgi-start.tar.gz">is available here</a>. Simply <code>curl -O https://tilde.institute/kcgi-start.tar.gz</code> it to your home directory here on ~institute, untar, make, and make install to test the compilation. It installs to ~/public_html with the proper ownership and permissions. View the index.c source and the makefile to see what goes on under the hood! Feel free to adapt it your own projects!</p>
diff --git a/wikipages/dcss.wiki b/wikipages/dcss.wiki
deleted file mode 100644
index 43c04a4..0000000
--- a/wikipages/dcss.wiki
+++ /dev/null
@@ -1,46 +0,0 @@
-<!--
-    author: ahriman / Ben Morrison
-    title: Dungeon Crawl Stone Soup
-    description: playing DCSS on the tildeverse server
--->
-
-<h2>Dungeon Crawl Stone Soup</h2>
-
-<p>DCSS is a fun roguelike game that is now available on a
- tildeverse server for your enjoyment. There are two ways to
- play: via WebTiles for simple 2d graphics and via SSH for
- a more traditional ascii interface.</p>
-
- <p>CTVO: <a href="https://crawl.tildeverse.org">https://crawl.tildeverse.org</a></p>
-
-<p>If you already have an account on tilde.institute, you can
- play via the ascii interface by issuing the command <code>dcss</code>.
- This will automatically connect to the server and present the
- login/registration menu.</p>
-
-<p>Some users prefer graphics. For webtiles, it will be necessary
- to go to <a href="https://crawl.tildeverse.org">https://crawl.tildeverse.org</a>.
- Click "PLAY" to open the WebTiles interface.</p>
-
-<h3>Recorded Games</h3>
-
-<p>All games on CTVO (the tildeverse crawl server) are recorded for
- later playback. In order to review a previously recorded game,
- navigate to <a href="https://crawl.tildeverse.org/ttyrec">the ttyrec directory</a>,
- select a username, and download the ttyrec file. You'll need to
- have the ttyrec package installed in order to review them. Issue:
- <code>ttyplay file.ttyrec</code> and watch as your terminal
- automagically transforms into a recorded DCSS game.</p>
-
-<p>ttyplay is installed on tilde.institute, so feel free to download
- a game to your home directory and watch it from there.</p>
-
-<h3>Morgue Files</h3>
-
-<p>Want to see the run-down of a game? Check out the morgue file
- for it. They're sorted into username directories at:
- <a href="https://crawl.tildeverse.org/morgue">https://crawl.tildeverse.org/morgue</a>.
- Each morgue file contains information such as how you died, your stats,
- an account of monsters vanquished, among other stuff.</p>
-
-<a href="/wiki">Back to Wiki</a>
diff --git a/wikipages/finger.wiki b/wikipages/finger.wiki
deleted file mode 100644
index f74b1e3..0000000
--- a/wikipages/finger.wiki
+++ /dev/null
@@ -1,42 +0,0 @@
-<!--
-    author: ahriman
-    title: Finger
-    description: a brief introduction to the finger service
--->
-
-<h2>finger</h2>
-
-<p>the finger protocol was created way back in 1977. its purpose was to display information about the queried user of a system, or all the users of a system.</p>
-
-<p>it fell out of use in the 1990s due to various security concerns. the old finger daemons were buggy and easily exploited, while the information garnered from a query could be used for social engineering attacks. nowadays, the finger daemons have been refined and are no longer so vulnerable.</p>
-
-<p>in the post-facebook world, new types of social networks are popping up. the latest in this movement is a resurgence of the finger protocol. what follows is a rough guide for getting yourself up to speed with finger on tilde.institute.</p>
-
-<h3>querying</h3>
-
-<p>the standard query for finger is simply</p>
-
-<p><code>finger user@host</code></p>
-
-<p>which displays login name, home directory, shell, real name, current login time, idle time, whether or not the user has mail, and the contents of the user's ~/.plan file. Here is an example of the output:</p>
-
-<div class="code"><pre>Login: username                          Name: Bob Bobson XXII
-Directory: /home/username                Shell: /bin/bash
-On since Wed Jan  2 04:04 (EST) on pts/94 from 168.297.83.21 via mosh [6420]
-    8 minutes 26 seconds idle
-Last login Wed Jan  2 04:33 (EST) on pts/91 from 168.297.83.21
-No mail.
-Plan:
-hey hey hey everybody!</pre></div>
-
-<h3>.plan</h3>
-
-<p>The ~/.plan file displayed at the end of the finger query response allows for some customization. You can put literally any text you want there. Status updates, summaries, etc. This little file allows us to use finger as a rudimentary social network.</p>
-
-<p>For example, say you want to use it as a personal summary, like having a blurb about what you're working on. Place the statement into ~/.plan and you're ready to go!</p>
-
-<p>For a more traditional social network style format, put dated and timed status updates as if you're tooting on a mastodon instance. The sky's the limit! Well, actually, text is the limit. But you get the idea. Right?</p>
-
-<p>hope to see you on finger soon!</p>
-
-<a href="/wiki">Back to Wiki</a>
diff --git a/wikipages/gettingstartedcommands.wiki b/wikipages/gettingstartedcommands.wiki
deleted file mode 100644
index 10c79bb..0000000
--- a/wikipages/gettingstartedcommands.wiki
+++ /dev/null
@@ -1,40 +0,0 @@
-<!--
-    author: kneezle
-    title: Getting Started with ~.institute
-    description: Getting started page
--->
-
-<h2>Getting Started with ~.institute</h2>
-
-<p>Hello and welcome to tilde.institute! We hope you enjoy your new ~/home</p>
-
-<p>Useful commands:</p>
-
-<p>The basic unix commands are fairly well documented, and you can learn more about them here: <a href="http://mally.stanford.edu/~sr/computing/basic-unix.html">http://mally.stanford.edu/~sr/computing/basic-unix.html</a></p>
-<p>For institute specific commands, check out below:</p>
-
-<ul>
-<li>To change your shell: <code>chsh</code></li>
-<li>To see if you have unread mail: <code>newmail</code></li>
-<li>To see the intro message again: <code>motd</code></li>
-<li>To chat with us on IRC: <code>chat</code></li>
-<li>To use the <a href="https://www.linode.com/docs/networking/ssh/persistent-terminal-sessions-with-tmux/">Terminal multiplexer</a>: <code>tmux</code></li>
-<li>To check your ~institute email account: <code>mutt</code></li>
-</ul>
-
-<p>Same fun games we have:</p>
-<ul>
-<li>Collaborative world-building: <code>holodeck</code></li>
-<li>Plant a little garden: <code>botany</code></li>
-<li>Play with other ~institute members: <code>tron</code></li>
-<li>The classic roguelike: <code>nethack</code></li>
-<li>Roguelike set in Middle-Earth: <code>angband</code></li>
-<li>The classic adventure game: <code>zork</code></li>
-<li>Dungeon Crawl Stone Soup: <code>dcss</code></li>
-<li>Multi-user persistent social-farming game: <code>asciifarm</code></li>
-</ul>
-
-
-<p>Happy Unixing!</p>
-
-<a href="/wiki">Back to Wiki</a>
diff --git a/wikipages/gopher.wiki b/wikipages/gopher.wiki
deleted file mode 100644
index b265400..0000000
--- a/wikipages/gopher.wiki
+++ /dev/null
@@ -1,74 +0,0 @@
-<!--
-    author: tomasino
-    title: Getting Started With Gopher Using burrow
-    description: gopherhole management tutorial using the burrow tool
--->
-
-<h2>Getting Started With Gopher Using burrow</h2>
-
-<p>To create a gopher hole on tilde.institute, a user can easily get started
-by doing the following:</p>
-
-<p>1) Create the gopher directory</p>
-
-<div class="code">$ mkdir public_gopher</div>
-
-<p>2) Create a root gophermap</p>
-
-<div class="code">$ burrow gophermap</div>
-
-<p>Gophernicus will interpret any text you add here as information
-lines unless they begin with one of gophernicus' special characters
-or contains a tab. As a general rule, don't use tabs unless you're
-intentionally linking something.</p>
-
-<p>Add a cool header to the file (check out <code>figlet</code>!), then somewhere near the top, paste:</p>
-
-<div class="code" style="text-align:center">==== Last Updated: February 19th, 2019 ====</div>
-
-<p>The date doesn't matter, really. Whenever you "phlog" with burrow it will
-update the date for you. How sweet is that?</p>
-
-<p>Now lets add a link to your phlog that you're totally going to have:</p>
-
-<div class="code">1phlog[tab]phlog</div>
-
-<p>That [tab] should be a literal tab, though. Make sure your editor doesn't
-convert it to spaces. Now, save and quit the editor.</p>
-
-<p>3) Create a phlog directory</p>
-
-<div class="code">$ mkdir ~/public_gopher/phlog</div>
-
-<p>4) Now create a new phlog with burrow</p>
-
-<div class="code">$ burrow phlog</div>
-
-<p>You'll be prompted for a title. If you hit enter and give no title then
-burrow will abort.</p>
-
-<p>Once you hit enter after giving your title a temporary file will open in
-your default $EDITOR. Don't like that editor? Be sure to change your
-environment var!</p>
-
-<p>If you quit your phlog file without saving the post is aborted. If you
-save and quit, it will create a new phlog entry, add it to your phlog
-gophermap that now exists, and update the date on your root gophermap.
-That's it!</p>
-
-<p>You have an RSS file sitting in the root of your gopher hole at rss.xml.
-It will automatically generate when you phlog, like a winner. You can edit
-your root gophermap at any time by using burrow's gophermap action. If you
-create other folders and gophermaps in the future you can use burrow's
-gophermap function to target them. For instance, to open the phlog
-listings you would:</p>
-
-<div class="code">$ burrow gophermap /phlog</div>
-
-<p>Editing gophermaps with burrow will ensure they're always saved and
-formatted properly! Any other files are just text, so open them directly with your editor of
-choice.</p>
-
-<p>That's it! Happy gophering.</p>
-
-<p>~tomasino</p>
diff --git a/wikipages/gpg-for-ssh-auth.wiki b/wikipages/gpg-for-ssh-auth.wiki
deleted file mode 100644
index b891ec9..0000000
--- a/wikipages/gpg-for-ssh-auth.wiki
+++ /dev/null
@@ -1,28 +0,0 @@
-<!--
-    author: ahriman
-    title: Using GPG For SSH Authentication
-    description: setting gpg-agent to handle ssh authentication on linux
--->
-
-<h2>Using GPG for SSH Authentication</h2>
-
-<p>It's a fairly simply process to have <code>gpg-agent</code> handle your SSH authentication. To start off, you'll need to have a private GnuPG key generated with an appropriate subkey for authentication. Once that's taken care of, open up <code>~/.gnupg/gpg-agent.conf</code></p>
-
-<div class="code">$ cat ~/.gnupg/gpg-agent.conf<br />
-enable-ssh-support<br />
-default-cache-ttl 60<br />
-max-cache-ttl 120</div>
-
-<p>Now you'll need to append the following to ~/.bashrc, or the appropriate rc file for your shell</p>
-
-<div class="code">$ cat ~/.bashrc<br />
-export GPG_TTY="$(tty)"<br />
-export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket)<br />
-gpg-connect-agent updatestartuptty /bye</div>
-
-<p>Once that's done, you'll need to let gpg-agent know which GnuPG subkey to use for SSH authentication. Run <code>gpg --with-keygrip -k &lt;email&gt;</code> and copy the keygrip associated with the subkey you've generated specifically for authentication only. Now, open <code>~/.gnupg/sshcontrol</code> and paste the keygrip into that file. Verify that the correct keygrip has been selected by running <code>ssh-add -L</code> and comparing it against the output of <code>gpg
---export-ssh-key &lt;keyid&gt;</code>. If it's correct, kill off gpg-agent with <code>killall gpg-agent</code>, then open up a new terminal and attempt to connect to a server!</p>
-
-<br />
-
-<a href="/wiki">Back to Wiki</a>
diff --git a/wikipages/irc.wiki b/wikipages/irc.wiki
deleted file mode 100644
index 70ddbc3..0000000
--- a/wikipages/irc.wiki
+++ /dev/null
@@ -1,14 +0,0 @@
-<!--
-    author: ahriman
-    title: IRC
-    description: information on connecting to IRC
--->
-
-<h2>IRC</h2>
-<p>To connect to the <a href="https://tilde.chat">tildeverse IRC network</a> and begin chatting while logged on to tilde.institute, simply use the command <code>chat</code>! If you prefer to use a different IRC client than the default, such as irssi, the following server information will apply:</p>
-        <ul>
-            <li>localhost, port 6667</li>
-        </ul>
-        <p>Don't forget to /join #institute and /join #meta</p>
-        <p>Join us on the tildeverse IRC network and socialize with other tilde users!</p>
-        <p>tilde.institute is now peering with the larger <a href="https://tilde.chat">tildeverse IRC network</a>! Our specific node can be connected remotely via institute.tilde.chat, port 6697, with SSL enabled.</p>
diff --git a/wikipages/password-store.wiki b/wikipages/password-store.wiki
deleted file mode 100644
index c9de846..0000000
--- a/wikipages/password-store.wiki
+++ /dev/null
@@ -1,88 +0,0 @@
-<!--
-    author: erxeto
-    title: password store
-    description: command line, GnuPG base, password manager.
--->
-
-<h2>pass, cli password manager</h2>
-
-<p><code>pass</code> is a command line utility to manage your passwords.</p>
-<p>
-It creates a simple file/folder structure under your $PASSWORD_STORE_DIR (by default <code>~/.password-store</code>) where every file is encrypted with your gpg key.
-</p>
-
-<p>
-You can organize that hierarchy as you see fit. For instance something like <code>sites/tilde.news/myusername</code> is a common way of doing it.
-</p>
-
-<p>
-Those files are not limited to contain simply a password, they can contain anything. But is recommended that the password goes alone in the first line, so you can benefit from the <code>-c</code> option which copies that to the clipboard directly.
-</p>
-
-<p>
-There is bash, zsh and fish command line completion available and all can be tracked using git. So it's really convenient.
-</p>
-
-<h2>setup</h2>
-<p>This is simple, just one command (assuming you have your GnuPG key ready). GPG-ID is the hex id of your key.</p>
-<div class="code">
-$ pass init GPG-ID<br />
-mkdir: created directory ‘/home/user/.password-store’<br />
-Password store initialized for GPG-ID<br />
-</div>
-
-
-<h2>basic usage</h2>
-
-<p>
-list all passwords "tree" style
-</p>
-<div class="code"><pre>
-$ pass
-Password Store
-├── sites
-│   ├── tilde.zone
-│   │   ├── myUserName
-│   │   ├── secondAccount
-...</pre>
-</div>
-<p>find a password</p>
-<div class="code"><pre>
-$ pass find tilde.zone
-Search Terms: tilde.zone
-└── sites
-    └── tilde.zone
-        └── myUserName@tilde.zone
-</pre></div>
-<p>See the content of a file</p>
-<div class="code">
-    $ pass email/tilde.institute/myAccount<br />
-    supersecret<br />
-</div>
-<p>Copy the first line to the clipboard. Clear time can be configured with <code>$PASSWORD_STORE_CLIP_TIME</code></p>
-<div class="code">
-    $ pass -c email/tilde.institute/myAccount<br />
-    Copied email/tilde.institute/myAccount to clipboard. Will clear in 45 seconds.<br />
-</div>
-<p>Insert a new password. It can be multiline with <code>-m</code>. Remember to put the password on the first line if you want to use the clipboard function</p>
-<div class="code">
-    $ pass insert sites/foo.com/blah<br />
-    Enter password for sites/foo.com/blah:<br />
-</div>
-<p>Generate a 32 chars random password and store it. You can define the default length with <code>$PASSWORD_STORE_GENERATED_LENGTH</code>. With <code>-n</code> the password will not include symbols, but alphanumeric characters only. With <code>-c</code> it gets copied to the clipboard as usual.</p>
-<div class="code">
-    $ pass generate sites/foo.com/abcd 32<br />
-    The generated password to sites/foo.com/abcd is:<br />
-    $(-QF&Q=IN2nFBx)<br />
-</div>
-
-<p>take a look at the <code>--help</code> option or the complete documentation on their website.</p>
-
-<p>
-references:
-<ul>
-    <li><a href="https://www.passwordstore.org/" target="_blank">pass home page</a></li>
-</ul>
-</p>
-
-<a href="/wiki">Back to Wiki</a>
diff --git a/wikipages/template.wiki b/wikipages/template.wiki
deleted file mode 100644
index 1f8a0d3..0000000
--- a/wikipages/template.wiki
+++ /dev/null
@@ -1,19 +0,0 @@
-<!--
-    author:
-    title:
-    description:
--->
-
-<h2>Page Title</h2>
-
-<p>paragraph content</p>
-
-<code>inline filesystem paths, commands, etc</code>
-
-<div class="code">code blockquote</div>
-
-<ul>
-    <li>bulleted list item</li>
-</ul>
-
-<a href="/wiki">Back to Wiki</a>
diff --git a/wikipages/unixprotips.wiki b/wikipages/unixprotips.wiki
deleted file mode 100644
index 6d9e9a0..0000000
--- a/wikipages/unixprotips.wiki
+++ /dev/null
@@ -1,29 +0,0 @@
-<!--
-    author: xvetrd
-    title: Unix ProTips
-    description:
--->
-
-<h2>UNIX ProTips</h2>
-<p>I realized today I wasn't getting mail notifications, and I hadn't
-set them up on this shell. So here are some things I do on my
-local machine that work here:</p>
-<p>To get the shell to tell you when you have new mail, after command
-executions, add this to your <code>.profile</code></p>
-
-<p><code>export MAILCHECK=0</code></p>
-
-<p>And, if you want, you can have a persistent notification when you
-have un-incorporated mail, or more specifically, when your
-<code>/var/mail/&lt;username&gt;</code> isn't empty.</p>
-
-<p><code>PS1="\$([-s /var/mail/`whoami` ] && echo '* ')$PS1"</code></p>
-
-<p>This works in /bin/ksh, I can't speak for other shells.</p>
-
-<p>If anybody else has some quick tips they would like to share, I
-encorage them to edit this page.</p>
-
-<p>Happy Unixing!</p>
-
-<a href="/wiki">Back to Wiki</a>