Mercurial > hg > Members > kono > nitros9-code

view docs/nitros9guide/dirm.refentry @ 2811:611715587834 lwtools-port

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Updated rules.mak and level1/coco1/bootfiles/makefile Updated the rules.mak file to remove the format entire image related to drivewire server disk images. Updated level1/coco1/bootfiles/makefile to create 3 new bootfile images. These images are stripped down to just the common files needed for vovdg games on os9 level 1. These bootfiles are for becker, dw, and arduino. Also corrected a duplicated dd descriptor when building some bootfiles that had both floppy_40d, floppy_80d, RBDW, RBBECKER, and RBARDUINO. Removed the dd descriptor from each of these sections and made it where the dd descriptor for the specific section was added in the main bootfile list.
author David Ladd <drencor-xeen@users.sf.net>
date Mon, 11 Feb 2013 20:16:24 -0600
parents b00cf13c9f61
children
line wrap: on
line source

<refentry id="dirm">
<refnamediv>
<refname>DIRM</refname>
<refpurpose>Display Module Directory for NitrOS-9 Level 2</refpurpose>
</refnamediv>

<refsynopsisdiv>
<cmdsynopsis>
<command>dirm</command>
</cmdsynopsis>
</refsynopsisdiv>

<refsect1><title>Description</title>
<para>
Displays the present module names in the system module directory,
i.e., all modules currently resident in memory. For example:
</para>
<screen>
OS9: dirm

 Module Directory at 14:44:35
D0      Pipe    OS9     OS9P2
Init    Boot    DDisk   D1
KBVDIO  TERM    IOMan   RBF
SCF     SysGo   Clock   Shell
PRINTER P       PipeMan Piper
Mdir
</screen>
<para>
If the &quot;e&quot; option is given, a full listing of the physical address,
size, type, revision level, reentant attribute, user count, and name
of each module is displayed. All numbers shown are in hexadecimal.
</para>
<para>
WARNING: Many of the modules listed by <command>dirm</command> are NitrOS-9 system modules
and <emphasis>not</emphasis> executable as programs: always check the module type code
before running a module if you are not familiar with it!
</para>
<para>
For more information see: <xref linkend="sec5.4.1"/>
</para>
</refsect1>
</refentry>