374 lines
17 KiB
HTML
374 lines
17 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
<title>SMArT Main menu</title>
|
|
<link rel="icon" href="/static/favicon.ico" type="image/x-icon">
|
|
<link rel="icon" type="image/png" sizes="16x16" href="/static/favicon-16x16.png">
|
|
<link rel="icon" type="image/png" sizes="32x32" href="/static/favicon-32x32.png">
|
|
<link rel="apple-touch-icon" href="/static/apple-touch-icon.png">
|
|
<style>
|
|
:root{--bg:#f4f1ea;--panel:#faf8f4;--line:#dfd2bf;--soft:#efe6d7;--text:#3d342c;--muted:#6f6257;--accent:#ad1d1c;--accent2:#c96b3d;--gold:#b9813d;}
|
|
*{box-sizing:border-box} html,body{margin:0;padding:0;background:var(--bg);color:var(--text);font:15px/1.55 Arial,Helvetica,sans-serif}
|
|
body{padding:18px}
|
|
a{color:inherit} code,tt{font-family:"DejaVu Sans Mono",monospace}
|
|
.shell{max-width:1100px;margin:0 auto}
|
|
.hero{display:flex;align-items:center;justify-content:space-between;gap:18px;padding:22px 24px;border:1px solid var(--line);border-radius:18px;background:linear-gradient(135deg,#a80f18,#c44731 60%,#d79a54);color:#fff;box-shadow:0 12px 30px rgba(64,36,12,.08)}
|
|
.hero img{height:42px;width:auto;display:block;background:#fff;border-radius:10px;padding:5px;box-shadow:0 8px 20px rgba(0,0,0,.12)}
|
|
.hero h1{margin:0;font-size:28px;line-height:1.1}
|
|
.hero p{margin:6px 0 0;font-size:15px;opacity:.95}
|
|
.grid{margin-top:18px;display:grid;gap:16px}
|
|
.card{display:block;text-decoration:none;background:var(--panel);border:1px solid var(--line);border-radius:16px;overflow:hidden;box-shadow:0 6px 18px rgba(64,36,12,.04)}
|
|
.card-header{padding:16px 18px;background:linear-gradient(90deg,#efe7da,#e8dfcf);border-bottom:1px solid var(--line)}
|
|
.card-title{margin:0;font-size:18px;color:var(--accent)}
|
|
.card-sub{margin:6px 0 0;color:var(--gold);font-size:12px;text-transform:uppercase;letter-spacing:.12em}
|
|
.card-body{padding:0}
|
|
.info{padding:16px 18px;border-top:1px solid #eee5d7}
|
|
.info:first-child{border-top:0}
|
|
.info h3{margin:0 0 8px;font-size:15px;color:#8b4a1d}
|
|
.info p,.info ul,.info ol{margin:0 0 10px;color:var(--muted)}
|
|
.info p:last-child,.info ul:last-child,.info ol:last-child{margin-bottom:0}
|
|
.info ul,.info ol{padding-left:22px}
|
|
.note{color:#5f5349}
|
|
@media (max-width:700px){body{padding:12px}.hero{padding:18px;align-items:flex-start;flex-direction:column}.hero img{height:36px}.card-header{padding:14px 16px}.info{padding:14px 16px}}
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<div class="shell">
|
|
<div class="hero">
|
|
<div>
|
|
<h1>Main menu</h1>
|
|
<p>SMArT configuration navigation with the original explanations preserved.</p>
|
|
</div>
|
|
<img src="/static/smart_icon.jpg" alt="SMArT logo">
|
|
</div>
|
|
<div class="grid">
|
|
<a class="card" href="/settings/general" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">General settings</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<h3>Servername</h3>
|
|
<div class="note">The servername is the name under which this server will show up when using
|
|
tools like <tt>SLIST</tt> (server-list).<br/>
|
|
If you don't supply an entry for this section, the hostname of your
|
|
Linux-machine will be converted to all-uppercase and used as the servername.</div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>Internal network number</h3>
|
|
<div class="note">If have dealt with the TCP/IP-configuration of your Linux-Box, the term
|
|
<i>ip-address</i> may be familiar to you. It's a numer that uniquely
|
|
identifies your machine in the internet.<br/>
|
|
As you might already expect, even the IPX-people use a unique number to
|
|
identify each other. Addresses in the IPX-world always consist of a
|
|
4-byte network-number plus a 6-byte node-number (remember the
|
|
ip-addresses also use 4-bytes).<br/>
|
|
The numbering-rule for ipx-clients is easy: their address is the
|
|
external-network of the server they are connected to plus the
|
|
hardware-address of their own ethernet-card (6 byte). As a result of this
|
|
rule, the clients can determine their address automatically (by listening
|
|
to the server and looking at their own ethernet-hardware) and no
|
|
configuration-files on the clients-side have to be maintained. (It would
|
|
really be a nasty thing if you think of very many DOS-clients [remember:
|
|
DOS is an OS where ordinary users can screw up the configuration files].)<br/>
|
|
For internal routing purposes, a NetWare-server has an <i>internal network</i><br/>
|
|
As there is no organisation which regulates the use of network-numbers
|
|
in the IPX-world, you have to run <tt>SLIST</tt> (under DOS or Linux) to
|
|
determine a number that isn't already used by another server on your
|
|
net. You better double-check and ask the other network administrators
|
|
before using a random value because not all servers might be on-line when
|
|
you listen to the net.<br/>
|
|
A reasonable choice for the internal net-number of your MARS_NWE-server
|
|
could be the ip-address of your Linux-Box. It is reasonable because
|
|
ip-addresse are unique and if every nw-administrator uses only this uniqe
|
|
value, potential conflicts will be minimized. Of course this choice is
|
|
no guarantee and it only works if your Linux-Box IP is well configured.<br/>
|
|
Please note that you have to specify the address of your internal
|
|
IPX-network in hexadecimal format (the leading <tt>0x</tt> indicates it).<br/>
|
|
<b>Most people who use FreeBSD want to set the network number of their IPX
|
|
network here</b></div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>Tests at startup</h3>
|
|
<div class="note">If you want some sanity checks at startup, set this flag, so
|
|
MARS_NWE will try to create/change missing directories:<br/>
|
|
<tt>SYS:LOGIN, SYS:MAIL, SYS:MAIL/XXX, SYS:PUBLIC, SYS:SYSTEM ...</tt>
|
|
(with the right permissions, of course)<br/>
|
|
This should also be enabled when you use a new MARS_NWE version.<br/>
|
|
Disabling this test only spares little time when starting MARS_NWE.<br/></div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>Server version</h3>
|
|
<div class="note">Some clients work better if the server tells that it is a 3.11 Server,
|
|
although many calls (namespace services) of a real 3.11 Server are
|
|
missing yet.<br/>
|
|
If you want to use longfilenamesupport and/or namespace routines
|
|
you should set this section to '1' or '2'<br/>
|
|
And you should read doc/FAQS.<br/></div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>Burst mode</h3>
|
|
<div class="note">If you want to test Burst mode you can enable it here, and in config.h
|
|
you must set <tt>ENABLE_BURSTMODE</tt> to 1. Also, you have to set the
|
|
server version number to 3.12 .<br/>
|
|
<b>MAX_BURST_READ/WRITE_BUF:</b><br/>
|
|
Don't ask me what they mean, but they're hexadecimal, so don't forget to
|
|
prepend <tt>0x</tt>.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/dirs" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Directories</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">Some directories for MARS_NWE files.
|
|
The path cache directory is needed for Client-32 and the namespace calls,
|
|
the spool directory is used for internal print queue handling.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/configh" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Precompiled settings</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">When you just leave these fields empty, the values in your <tt>config.h</tt>
|
|
file will be used. If you want to change those settings without recompiling
|
|
<tt>MARS_NWE</tt>, you can change them here.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/security" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Security</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<h3>Modes</h3>
|
|
<div class="note">Here you can change the standard modes for new files and directories.
|
|
You can enter <tt>0</tt> here to use the default value, and you can enter
|
|
<tt>-1</tt> for the directory <tt>creat()</tt> mode to use the
|
|
<tt>st_mode</tt> of the parent directory.</div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>Password handling of DOS-clients</h3>
|
|
<div class="note">When changing your MARS_NWE-password from a DOS-client, this client
|
|
(think of "<tt>LOGIN.EXE</tt>", "<tt>SYSCON.EXE</tt>" or "<tt>SETPASS.EXE</tt>")
|
|
can encrypt your password before sending it to the MARS_NWE-server
|
|
(this improves security a little bit).<br/>
|
|
In this section you can enforce encryption of user-passwords or allow
|
|
not-encrypted sending of passwords over the net.<br/>
|
|
On the Linux-side, passwords will only be stored in encrypted format.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/susers" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">User configuration</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<h3>Guest user</h3>
|
|
<div class="note">Here you can set the UID a user will get before logging in.</div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>Supervisor user</h3>
|
|
<div class="note">The <tt>SUPERVISOR</tt> of a NetWare-server is much like <tt>root</tt> on the
|
|
Linux-side.<br/>
|
|
Specify a Linux-user that should be mapped to the supervisor of this
|
|
MARS_NWE-server.<br/>
|
|
To improve security, don't use <tt>root</tt> for this purpose but create a
|
|
seperate administrative account (under Linux) called <tt>nw-adm</tt> or similar.<br/>
|
|
The nw-user defined in this section will have the MARS_NWE internal UID
|
|
1 (remember even under Linux <tt>root</tt> must have the special UID 0), so
|
|
it is not possible to define a supervisor in section 13 (the users
|
|
defined there will get random UIDs).<br/>
|
|
You <i>can</i> define a user with name <tt>SUPERVISOR</tt> in section 13, but he
|
|
won't really be the "local god" on the MARS_NWE-server.<br/>
|
|
And of course you <i>can</i> define a supervisor with name <tt>GOD</tt> or <tt>ROOT</tt>
|
|
in <i>this</i> section, which would only break the traditional naming-scheme
|
|
of the NetWare-world.</div>
|
|
</div>
|
|
<div class="info">
|
|
<h3>User mapping</h3>
|
|
<div class="note">If you have a large number of accounts on your Linux-machine, you may
|
|
want to map all Linux-logins automatically to MARS_NWE-logins.<br/>
|
|
At this stage this section is only a quick hack to make life a bit
|
|
easier for the administrator.<br/>
|
|
<b>WARNING:</b> As there is no algorithm to convert the encrypted
|
|
Linux-passwords into the encrypted format used by the DOS-clients (and
|
|
therefore MARS_NWE), you have to supply a common password for all
|
|
automatically mapped users. This is a big security concern and you
|
|
should never make this common password public (and, of course you
|
|
should choose a sufficient "secure" (read: difficult) password).<br/>
|
|
Type the common password to grant access to the users login and the
|
|
command "setpass" instead of telling the password to the user.<br/>
|
|
Only those Linux-logins will handled automatically that don't have a
|
|
x or asterisk as their encrypted password.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/volumes" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Volumes</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">The OS/2 additional namespace can be used by Windows 9x too. The
|
|
'no fixed i-nodes' option is necessary when exporting DOS or CD-ROM
|
|
file systems. The 'single filesystem' option can be used when the
|
|
entire volume consists of only one mounted filesystem/device.
|
|
For more information about pipe filesystems you can take a look at
|
|
MARS_NWE's documentation directory.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/devices" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Devices</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">This section contains information for the ipx-router built into mars_nwe
|
|
and/or the external program <tt>nwrouted</tt>.<br/>
|
|
Both processes exchange the IPX-packets between your machine and the rest
|
|
of the world (in other words: their functionallity is essential). Of
|
|
course, to use one of both is already sufficient.<br/>
|
|
<b>Note for people with other IPX/NCP servers on the net:</b><br/>
|
|
<ul><li>choose the same frame-type as the other servers use
|
|
<li>make sure your network-number is not already in use by another server
|
|
(see the output of <tt>SLIST</tt> under Linux or DOS)</li></li></ul>
|
|
Under Linux, it is possible to let the kernel creat all ipx-devices
|
|
automatically for you. This is only possible (and only makes sense then)
|
|
if there are other IPX/NCP servers on the same net which are setup
|
|
correctly.<br/>
|
|
<ol>
|
|
<li><b>Network number</b><br/>
|
|
This number is determined by the router of the physical network you're
|
|
attached to. Use "0x0" to use the entry for all network number match.
|
|
<li><b>Device</b><br/>
|
|
The network-interface associated with the NET_NUMBER. (<tt>eth0</tt>,
|
|
<tt>arc0</tt>, <tt>ppp0</tt>, etc.) Use an asterisk to use this entry for
|
|
all devices match.
|
|
<li><b>Frame type</b><br/>
|
|
The frame-type of the data-packets on your local network.<br/>
|
|
Possible values are:
|
|
<ul><li><tt>ethernet_ii</tt> (Best for mixed(ipx, ip) environments)
|
|
<li><tt>802.2</tt> (Novell uses this as default since 3.12)
|
|
<li><tt>802.3</tt> (Older frame typ, some boot-PROMs use it)
|
|
<li><tt>snap</tt> (Normally not used)
|
|
<li><tt>token</tt> (For token ring cards)
|
|
<li><tt>auto</tt> (Automatic detection of the frame-type used in your IPX-environment)
|
|
</li></li></li></li></li></li></ul>
|
|
<li><b>Ticks</b><br/>
|
|
The time data-packets need to get delivered over a
|
|
certain interface. If your connection goes through several
|
|
routers, the shortest path can be determined by summing up
|
|
all ticks for every route and compare the results.<br/>
|
|
(1 tick = 1/18th second), default=1<br/>
|
|
<b>NOTE:</b> If ticks > 6 then the internal router handles
|
|
RIP/SAP specially. (RIP/SAP filtering)
|
|
</li></li></li></li></ol>
|
|
<b>NOTE:</b>
|
|
Automatic detection in this section means that ipx-interfaces which
|
|
are created by other instances than the server/router,
|
|
e.g. pppd, ipppd or ipx_interface, will be detected and inserted/removed
|
|
in internal device/routing table at runtime.<br/>
|
|
<b>You don't have to set this in FreeBSD!</b></div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/logging" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Logging</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">MARS_NWE can keep a log file with error messages, click here to set what
|
|
kind of messages must be logged and where.<br/>
|
|
You can set a logfile name to <tt>syslog</tt> if you want MARS_NWE to
|
|
use <tt>syslogd</tt> for logging.<br/>
|
|
According to <tt>nwserv.conf</tt>, the NWCLIENT tag must always be set
|
|
to <i>No debugging</i>.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/smart" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">SMArT settings</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">Some things have to be configured here before you can use SMArT.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/users" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Users</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">You can edit the userlist from the bindery files here. This option will not
|
|
change anything to the <tt>nwserv.conf</tt> configuration file.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/groups" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Groups</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">You can edit the group list from the bindery files here. This option will not
|
|
change anything to the <tt>nwserv.conf</tt> configuration file.</div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
<a class="card" href="/settings/queues" target="OPTS">
|
|
<div class="card-header">
|
|
<h2 class="card-title">Print queues</h2>
|
|
<div class="card-sub">Open settings</div>
|
|
</div>
|
|
<div class="card-body">
|
|
<div class="info">
|
|
<div class="note">Here you can edit the list of print queues. The things you have to fill in are:
|
|
<ol>
|
|
<li><b>Print queue name</b><br/>
|
|
The name with which the print queue will show up in the printer lists, and
|
|
the name you need when you want to print something from the client.
|
|
<li><b>Unix printing command</b><br/>
|
|
The command used to send a file to the printer, the text/etc. will come from
|
|
the standard input.<br/>
|
|
There's a nasty bug in MARS_NWE that removes this property, well, I think
|
|
it's a bug. It also happens when the startup tests are not set to maximum.
|
|
<li><b>Spool directory</b><br/>
|
|
The directory used to keep the print spool for this print queue. Use the
|
|
<tt>VOLUME:/directory</tt> form, you can leave this one empty to use a
|
|
default directory.
|
|
|
|
</li></li></li></ol></div>
|
|
</div>
|
|
</div>
|
|
</a>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|