> For the complete documentation index, see [llms.txt](https://documentation.tjhsst.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.tjhsst.edu/obsolete/ekhi.md).

# Ekhi

{% hint style="warning" %}
This page contains information on systems that are in happy retirement from the Computer Systems Lab.
{% endhint %}

**Ekhi** was a Sun Microsystems server donated to the CSL in the spring of 2004. Ekhi was sent home with Myles Maxfield, an ex-sysadmin who graduated in 2007. It's main purpose was a training server for Sun admins.

Retired: 3 January 2008

## Technical Specifications

| Specification     | Description            |
| ----------------- | ---------------------- |
| **Server Type**   | Sun Enterprise 420R    |
| **CPU**           | UltraSPARC-II @ 450MHz |
| **RAM**           | 3 GB                   |
| **Hard Disks**    | 18 GB                  |
| **OS**            | Sun Solaris 10         |
| **Purchase Date** | Spring 2005            |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.tjhsst.edu/obsolete/ekhi.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.