Import 0.99
This commit is contained in:
Mario Fetka
482
static/menu.html
Normal file
482
static/menu.html
Normal file
@@ -0,0 +1,482 @@
|
||||
<HTML>
|
||||
<BODY BGCOLOR=#F0F0FF>
|
||||
|
||||
<TABLE BORDER=0 CELLSPACING=0 WIDTH=100%>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD>
|
||||
<IMG SRC="/static/smart_icon.jpg"><BR>
|
||||
</TD>
|
||||
<TD ALIGN=RIGHT>
|
||||
<B><FONT SIZE=+2>Main menu</FONT></B><BR>
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/general" TARGET="OPTS"><B><FONT SIZE=+2>General settings</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Servername</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Internal network number</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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>
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Tests at startup</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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>
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Server version</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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>
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Burst mode</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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>.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/dirs" TARGET="OPTS"><B><FONT SIZE=+2>Directories</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/configh" TARGET="OPTS"><B><FONT SIZE=+2>Precompiled settings</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/security" TARGET="OPTS"><B><FONT SIZE=+2>Security</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Modes</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Password handling of DOS-clients</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/susers" TARGET="OPTS"><B><FONT SIZE=+2>User configuration</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Guest user</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
Here you can set the UID a user will get before logging in.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>Supervisor user</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<B>User mapping</B>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/volumes" TARGET="OPTS"><B><FONT SIZE=+2>Volumes</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/devices" TARGET="OPTS"><B><FONT SIZE=+2>Devices</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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)</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)
|
||||
</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)
|
||||
</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>
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/logging" TARGET="OPTS"><B><FONT SIZE=+2>Logging</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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>.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#C0C0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/smart" TARGET="OPTS"><B><FONT SIZE=+2>SMArT settings</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
Some things have to be configured here before you can use SMArT.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/users" TARGET="OPTS"><B><FONT SIZE=+2>Users</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
You can edit the userlist from the bindery files here. This option will not
|
||||
change anything to the <TT>nwserv.conf</TT> configuration file.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/groups" TARGET="OPTS"><B><FONT SIZE=+2>Groups</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
|
||||
<TR>
|
||||
<TD HEIGHT=25>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#D0D0FF>
|
||||
<TD COLSPAN=2>
|
||||
<A HREF="/settings/queues" TARGET="OPTS"><B><FONT SIZE=+2>Print queues</FONT></B></A>
|
||||
</TD>
|
||||
</TR>
|
||||
<TR BGCOLOR=#E0E0FF>
|
||||
<TD COLSPAN=2>
|
||||
|
||||
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.
|
||||
</UL>
|
||||
|
||||
</TD>
|
||||
</TR>
|
||||
</TABLE>
|
||||
|
||||
</BODY>
|
||||
</HTML>
|
||||
Reference in New Issue
Block a user