summaryrefslogtreecommitdiff
path: root/release/picobsd/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'release/picobsd/doc/src')
-rw-r--r--release/picobsd/doc/src/Makefile11
-rw-r--r--release/picobsd/doc/src/TODO.html154
-rw-r--r--release/picobsd/doc/src/UCI.html960
-rw-r--r--release/picobsd/doc/src/bugs.html22
-rw-r--r--release/picobsd/doc/src/faq.html8
-rw-r--r--release/picobsd/doc/src/hardware.html7
-rw-r--r--release/picobsd/doc/src/how2build.html8
-rw-r--r--release/picobsd/doc/src/intrinsics.html4
-rw-r--r--release/picobsd/doc/src/intro.html30
9 files changed, 31 insertions, 1173 deletions
diff --git a/release/picobsd/doc/src/Makefile b/release/picobsd/doc/src/Makefile
index cbd065c8c21e5..6478cbfdc518b 100644
--- a/release/picobsd/doc/src/Makefile
+++ b/release/picobsd/doc/src/Makefile
@@ -1,17 +1,14 @@
#
-# $Id: Makefile,v 1.1 1998/09/26 17:23:01 abial Exp $
+# $Id$
#
.include "../../Version"
-DATE!="date"
-
DOCS= bugs.html faq.html hardware.html how2build.html \
- intrinsics.html intro.html TODO.html
+ intrinsics.html intro.html
all: ../../Version
- for i in ${DOCS}; \
+ for i in `ls *.html`; \
do \
- cat $${i}|sed -e 's/@VER@/${VER}/g' \
- -e 's/@DATE@/${DATE}/g' >../$${i}; \
+ cat $${i}|sed -e 's/@VER@/${VER}/g' >../$${i}; \
done
diff --git a/release/picobsd/doc/src/TODO.html b/release/picobsd/doc/src/TODO.html
deleted file mode 100644
index 8192f02a0cb23..0000000000000
--- a/release/picobsd/doc/src/TODO.html
+++ /dev/null
@@ -1,154 +0,0 @@
-<html>
-<! $Id: TODO.html,v 1.2 1998/12/22 21:40:56 abial Exp $ >
-<body>
-<h1><center> Small FreeBSD ToDo List.
-</center></h1>
-
-<p>This list represents various tasks which are being collected from
-discussions on freebsd-small, and which represent the general
-direction and needs of using FreeBSD for small installations.</p>
-
-<p>The tasks are arranged by how important they are to the overall
-idea and goals of the project. If you are interested in doing some
-part of the work, please contact the coordinator of PicoBSD project
-(<A HREF="mailto:abial@freebsd.org">Andrzej Bialecki</a>).</p>
-
-<hr>
-
-<h2>Short term tasks:</h2>
-
-<ul>
-<li>
-Eliminate need for patching FreeBSD source tree - either by
-keeping our own version of Makefiles, or by adding (many) knobs to
-the standard ones. (NOTE: this will be resolved in v. 0.44).
-</li>
-<li>
-Provide options for building separate kernel and FS images of
-various sizes.
-</li>
-<li>
-Add some "wizards" to help people new to Unix configure "dialup"
-and "net" for most common tasks.
-</li>
-<li>
-Replace most of currently used scripts with Makefiles.
-(NOTE: this will be resolved in v. 0.44).
-</li>
-<li>
-Add simple authentication module to oinit.
-</li>
-<li>
-Fix kzip to be able to produce kzip'ped ELF kernels.
-(NOTE: currently we work around it by using kzipped /boot/loader).
-</li>
-<li>
-Write better documentation. This is very important - the most
-common configurations should be described in detail, step by step.
-</li>
-<li>
-Collect our experiences with using FreeBSD with SBCs, flash disks
-etc, and write a short practical guide to embedding FreeBSD.
-</li>
-</ul>
-<hr>
-
-<h2>Medium term tasks:</h2>
-
-<ul>
-<li>
-Change the building process so that it allows to easily choose
-(with finer granularity) needed components of the target system.
-</li>
-<li>
-Make use of recently added KLD to allow for easy adding and
-removing drivers when running stripped kernels.
-</li>
-<li>
-Investigate pros and cons of using the new boot/loader together
-with ELF kernels.
-(NOTE for v.0.43: it was simply mandatory to use it :-)
-</li>
-<li>
-Change currently used crunched binaries to something more flexible
-- as it is now, even small change in set of programs requires
-rebuilding of the whole image.
-</li>
-<li>
-Provide options for building systems which operate from
-(basically) read-only media, such as CD-ROM or flash disk. Such
-system doesn't need to keep all root FS in memory, but only small
-fraction of it for /tmp and /var.
-</li>
-<li>
-Integrate DHCP into "dialup" version.
-</li>
-<li>
-Rework oinit to be more modular, and write additional modules
-(remote access, SNMP (?), authentication, shell(), configuration
-editor).
-</li>
-<li>
-Provide a remote access (telnetd/login/shell) module for the
-"router" version. Make the shell() module more predictable and
-compatible with common sense :-)
-</li>
-<li>
-At last prepare usable version of ISP floppy, and test it (some
-basic tests with server PPP). This involves among others a version
-of PPP which supports Radius.
-</li>
-</ul>
-
-<hr>
-
-<h2>Long term tasks:</h2>
-
-<ul>
-<li>
-Either port ROMfs from Linux, or write our own replacement for it.
-</li>
-<li>
-Describe the configuration tasks and parameters of PicoBSD systems
-in terms of hierarchy of categories - this is needed to start
-working on the next two points.
-</li>
-<li>
-Design a flexible and efficient scheme (not necessarily compatible
-with currently used set of shell scripts) for storing and editing
-system configuration in some form of hierarchical DB.
-</li>
-<li>
-Design a user interface for configuration of system parameters
-and services, meeting the following requirements: hierachical,
-logical, helpful (hinting), providing ability to automate certain
-tasks.
-</li>
-<li>
-Reduce memory footprint.
-</li>
-<li>
-Add other language versions.
-</li>
-<li>
-Throw some more effort in porting the newer version of W (graphical
-UI), so that it uses VESA color modes. IMHO it's worth it.
-</li>
-</ul>
-
-<hr>
-
-<h2>Other half-baked ideas...</h2>
-
-<p>(fill this in :-)</p>
-
-<hr>
-Last modified:
-@DATE@
-
-
-<p><i>Send your comments, ideas, and most importantly the code itself, to
-<A HREF="mailto:abial@freebsd.org">abial@freebsd.org</a>.</i></p>
-
-</body>
-</html>
diff --git a/release/picobsd/doc/src/UCI.html b/release/picobsd/doc/src/UCI.html
deleted file mode 100644
index ae74b8489f827..0000000000000
--- a/release/picobsd/doc/src/UCI.html
+++ /dev/null
@@ -1,960 +0,0 @@
-<html>
-<! $Id: UCI.html,v 1.2 1998/11/25 11:08:54 abial Exp $ >
-<body>
-<h1><center> Unified Configuration Interface Project
-</center></h1>
-
-<p>The idea behind this project is to completely replace currently
-used configuration approach, which is based on several shell scripts, and to
-provide ability to change system behaviour basing on set of well-defined
-parameters' hierarchy. One of the goals is also to provide an object
-oriented model of the OS management and structure, instead of currently
-used (inconsistent) procedural model of system/service startup/shutdown.</p>
-
-<p>This project involves such issues as:
-<ul>
-<li>
-providing consistent view of the system and its functional subsystems as
-a set of interrelated objects equipped with certain properties.
-</li>
-<li>
-providing global approach to user interface, either command-line or with GUI
-front-ends.
-</li>
-<li>
-managing system resources and subsystems. This includes managing
-static and dynamic interdependencies between subsystems, ability to
-upgrade/downgrade specific subsystems on-the-fly.
-</li>
-</ul>
-</p>
-
-<p><i><b>This is work in progress</b> - I'm aware that many pieces
-are either completely missing or misplaced. Please send any comments and
-changes you seem appropriate either directly to me, or better to
-freebsd-small@freebsd.org. I'll gladly welcome anyone who can help with
-design and/or implementation.</i></p>
-
-
-<hr>
-
-<h1><center> Unified Configuration Interface
-</center></h1>
-
-<ul>
-<li>
-<p>Let's first introduce the following terms:
-<ul>
-<li>
-<b>management base</b> - the actual structure holding configuration and
-information data according to defined structure. This structure will most
-probably have a form of tree (possibly with cross-branch links or some other
-mechanism representing mutual dependencies) - the way it's stored is
-something which needs to be discussed.
-</li>
-<li>
-<b>user interface</b> - a method (and agent) for presenting data stored in
-management base in such a way that it can be viewed and modified by
-legitimate users.
-</li>
-<li>
-<b>system monitor</b> - an entity performing actual configuration and monitoring
-tasks, from one side dealing with management base, and from the other
-dealing with the system resources and subsystems, and from yet another dealing
-either directly with the user (thus acting as a user interface),
-or passing requests to other entity which acts as user interface.
-</li>
-<li>
-<b>subsystem</b> - a package containing programs, configuration data, as well
-as installing/deinstalling/start/stop stubs, which form together one logical
-entity performing specific services on behalf of the system. Each subsystem
-is viewed as an object with specific properties, dependencies, which is able
-to generate events, service general requests common to all such subsystems,
-and provide specific services to other subsystems.
-</li>
-</ul>
-</li>
-<li>
-<p>One possible approach to storing the management data is to use already
-existing framework known as MIB, as defined in applicable RFCs.</p>
-
-<p>This approach has several advantages: it represents well thought-out work
-of many experienced individuals and teams, it has already proven to be
-useful, it's widely used and accepted, it's easily extensible, it's able to
-represent quite complicated objects, etc.</p>
-
-<p>It has some drawbacks, as well: e.g. there is no standard mechanism for
-representing events and indirectly related objects, it tends to create
-deep and narrow trees which require to descent several levels to change some
-commonly used parameters, it doesn't say anything about the mutual
-dependencies between objects and parameters (except parent-child-sibling),
-and about required sequence to properly set their parameters, etc.</p>
-
-<p>These issues are not directly addressed in standards, and real
-implementations (known to me) have to implement these additional mechanisms
-"behind the scenes", so that their workings are not obvious nor easily
-accessible (let alone changeable).</p>
-
-<p>So, if we decide to use it, we need to address these issues somehow.
-The next point presents one possible approach to this dilemma.</p>
-</li>
-<li>
-<p>The term "object" used in the following discussion represents a functional
-subsystem, such as system service, usually performed by some specific
-process (or, a set of global system parameters, in which case the system
-monitor agent is the service itself). </p>
-
-<p>Each object represented in management base can be characterized by
-following properties:
-<ul>
-<li>
-its internal state, possibly consisting of several parameters and currently
-performed functions, but represented to the rest of the system as a symbolic
-state, one of set of states common to all objects.
-</li>
-<li>
-a temporary space for new sets of parameters, which are being supplied by
-other subsystems, prior to their actual application,
-</li>
-<li>
-FSM definition, describing state transitions in reaction to received events,
-</li>
-<li>
-list of events it can generate and accept,
-</li>
-<li>
-list of dependencies on other objects' states and services,
-</li>
-<li>
-list of requests it can handle,
-</li>
-<li>
-list of parameters it can accept and/or provide, with their valid ranges.
-</li>
-</ul>
-</p>
-
-<p>A few words on system startup: the system startup routines should ensure
-that dependencies can be unwound into linear, ordered list. If it's not
-possible, they should detect possible deadlocks at runtime, and act as an
-arbiter between conflicting parties (or signal an error). In case of
-unsatisfied dependency on some missing subsystem, the system monitor will
-act appropriately as described below (in paragraph on request handling).</p>
-
-<p>The <b>set of symbolic states</b> may consist of the following states,
-depicting object's current internal state (as described by its FSM):
-
-<center><table border>
-<tr><th>Name</th><th>Meaning</th></tr>
-<tr>
-<td>INIT</td><td>the subsystem is initializing itself, possibly loading
-necessary data and binaries from permanent storage.</td>
-</tr>
-<tr>
-<td>CHECK</td><td>performing consistency check on newly supplied parameter values</td>
-</tr>
-<tr>
-<td>READY</td><td>ready to start performing its primary function, but not started</td>
-</tr>
-<tr>
-<td>START</td><td>start-up tasks (related to its primary function, as opposed
-to INIT which is related to its own initialization)</td>
-</tr>
-<tr>
-<td>STOP</td><td>stop (shutdown) tasks (when the object intends to stop
-performing its function). This can involve unloading data and binaries from
-main memory.</td>
-</tr>
-<tr>
-<td>RUN</td><td>primary (work) phase</td>
-</tr>
-<tr>
-<td>IDLE</td><td>waiting for some external event to happen</td>
-</tr>
-<tr>
-<td>BUSY</td><td>the subsystem is busy (either with performing some
-high-priority task, or just simply hung), and cannot be interrupted without
-complete restart,</td>
-</tr>
-<tr>
-<td>ERROR</td><td>this object is either improperly configured, or
-malfunctioning</td>
-</tr>
-<tr>
-<td>(other...)</td><td>(other...)</td>
-</tr>
-</table></center>
-</p>
-
-<p>The <b>set of possible actions</b> may include the following actions:</p>
-
-<center><table border>
-<tr><th>Name</th><th>Meaning</th></tr>
-<tr>
-<td>LIST_EV_REQ</td><td>get list of events the subsystem can generate</td>
-</tr>
-<tr>
-<td>LIST_ACT_REQ</td><td>get list of actions the subsystem can respond to</td>
-</tr>
-<tr>
-<td>GET_DEF_REQ</td><td>get definition of given parameter (the arguments, and
-valid ranges)</td>
-</tr>
-<tr>
-<td>SET_REQ</td><td>set given parameter to given value (this value will
-be used only after COMMIT_REQ)</td>
-</tr>
-<tr>
-<td>GET_REQ</td><td>get currently used value of given parameter</td>
-</tr>
-<tr>
-<td>COMMIT_REQ</td><td>commit changes supplied in last transaction to currently
-used set of parameters</td>
-</tr>
-<tr>
-<td>ROLLBACK_REQ</td><td>revert last commit</td>
-</tr>
-<tr>
-<td>INIT_REQ</td><td>perform initialization tasks</td>
-</tr>
-<tr>
-<td>START_REQ</td><td>start performing primary function</td>
-</tr>
-<tr>
-<td>STOP_REQ</td><td>stop performing primary function</td>
-</tr>
-<tr>
-<td>RESTART_REQ</td><td>restart operation, possibly forcefully</td>
-</tr>
-<tr>
-<td>NOTIFY_REQ</td><td>notify me of any changes in your state</td>
-</tr>
-<tr>
-<td>CHECK_REQ</td><td>perform self-consistency check</td>
-</tr>
-<tr>
-<td>UPGRADE_REQ</td><td>upgrade the subsystem - this possibly involves
-downloading necessary pieces via network to permanent storage area. The
-upgrade process should be transactional, and should save the older version
-of the subsystem in case the DOWNGRADE_REQ should be issued.</td>
-</tr>
-<tr>
-<td>DOWNGRADE_REQ</td><td>downgrade the subsystem - restore the previous
-version of the subsystem from the copy on permanent storage.</td>
-</tr>
-<tr>
-<td>UNINSTALL_REQ</td><td>uninstall the subsystem completely - possibly
-freeing the space on permanent storage.</td>
-</tr>
-<tr>
-<td>(other...)</td><td>(other...)</td>
-</tr>
-</table></center>
-<p><i>(Each request includes source service identifier and credentials of
-the sender)</i></p>
-
-<p>The <b>set of events</b> which can be generated by subsystems may include
-the following:</p>
-
-<center><table border>
-<tr><th>Name</th><th>Meaning</th></tr>
-<tr>
-<td>EV_ACK</td><td>positive acknowledge of the last operation</td>
-</tr>
-<tr>
-<td>EV_NACK</td><td>negative acknowledge of the last operation</td>
-</tr>
-<tr>
-<td>EV_CHANGE</td><td>change notification (includes the name of changed
-parameter, and/or FSM state change)</td>
-</tr>
-<tr>
-<td>EV_DEP</td><td>signal the dependency on another subsystem - ask for
-existence of the service. Probably there should be two types of the dependency:
-a soft one (where the subsystem can still function even if the dependency is
-unresolved) and a hard one (when the existence and proper functioning of the
-other subsystem is mandatory for its function).</td>
-</tr>
-<tr>
-<td>(other...)</td><td>(other...)</td>
-</tr>
-</table></center>
-
-<p>One of event attributes can be a flag which says that this particular event
-is a directed, or broadcast message. In case of directed message, it should
-be forwarded only to interested parties. Broadcast message is sent to all
-subsystems.</p>
-
-<p>System monitor agent will process these events and route them to
-appropriate subsystems which are registered with it. Generally, if some
-subsystem is dependent on some other, it will want to also receive all events
-generated by the other subsystem.</p>
-
-<p>In case the subsystem
-is missing, and the system monitor received events signalling that some other
-subsystem is depending on it, the system monitor should arrange either for
-installing necessary pieces from some media (be it permanent storage, or the
-network), or to send an EV_NACK to the requesting subsystem. It's the
-responsibility of the requesting subsystem to deal with such case
-appropriately to the type of dependency (i.e. either "hard" or "soft").
-
-<p>Ideally, the system monitor agent will be equipped with routines to
-serialize the management data into human-readable form, so that it's easily
-stored, backed up, and repaired in case of inconsistencies.</p>
-</li>
-<li>
-<p>Actual user interface is still quite another story: I've seen UIs which
-merely followed the standard MIBs, and menus were composed of actual OID
-numbers plus DESCRIPTION field. In my experience, they are (barely)
-acceptable, though due to the usual width and depth of MIB trees you had to
-traverse several levels down and up in order to change some (protocol-wise)
-related parameters.</p>
-
-<p>More acceptable UI would collect interrelated items under common menu
-entries, irrespectibly of their actual position in the MIB tree.</p>
-
-<p>A worthwhile goal to pursue is to create such an UI which could guide
-you through the most common configuration tasks, while at the same time
-allowing for unrestricted and quick use by power users. This can be done
-either as a set of configuration "wizards" or extensive hinting, command
-completion, etc.</p>
-</li>
-<li>
-<p>The management database should be easily exportable via standard
-protocols, such as SNMP or LDAP.</p>
-
-<p>Most known to me (if not all) implementations of agents for these
-protocols are (contrary to their name) quite heavy-weight - so their use
-should be either optional, or replaced with some other light-weight
-protocol and a proxy agent running on other machine. One example of
-such proxy agent is existing UCD-SNMP implementation which in
-significant part follows the sysctl(3) tree, merely exporting it as
-a part of the MIB trees.</p>
-
-<p>It's worthwhile to consider also use of other protocols such as
-DHCP (and BOOTP), Service Location Protocol (SLP - RFC2165) for easy
-integration with LAN resources, easy initial configuration, and peer
-discovery.</p>
-</li>
-<li>
-<p>All operations performed by system monitor agent should be transactional,
-i.e. it should be possible to commit a set of changes as one logical entity,
-and be sure that either it's applied in whole, or not at all. This includes
-also ability to abort processing in the middle.</p>
-
-<p>This probably means that each object (subsystem) should be able to store
-not only its current configuration data, but also the newly supplied config
-data that are to be applied after the transaction ends successfuly.</p>
-
-<p>Operations should be verified against allowed values, as well as against
-allowed credentials, and basing on this either committed or aborted.</p>
-</li>
-<li>
-<p>A few notes on possible implementation of system monitor:</p>
-<ul>
-<li>
-let's assume that all configuration information is read on startup
-by some specialized daemon (this can be part of init(8) as well),
-which then performs role of communication agent through which passes
-all configuration information, be it request for change, request
-for info, request for start / shutdown, or notification about the change.
-</li>
-<li>
-configuration information itself is stored either in binary database, or as
-a filesystem hierachy mimicking configuration items hierarchy.
-</li>
-<li>
-each user-level program performing some task (such as routing daemon, inetd
-etc) is either equipped with the ability to communicate with config agent, or
-is relinked with special stub which fakes to the program necessary config
-files and events (such as signals to reread configuration).
-<p>This probably means also that some libc routines would have to be replaced,
-because they assume reading configuration from certain disk files.</p>
-
-<p>Since each such subsystem needs to implement some common actions such as
-installing, deinstalling, start/stop etc, we could use already present
-system of packages (with some minor modifications) to easily achieve
-part of the goals (i.e. install/deinstall/upgrade/downgrade/stop/start).</p>
-</li>
-<li>
-each subsystem performing some task requests its initial config data
-from system monitor, at the same time registering with it to receive
-configuration events, such as request to re-read data, to provide currently
-used config data, return status, react for signals, restarts, etc...
-</li>
-<li>
-system monitor acts as a meeting point for all producers and consumers
-of events and config data. It needs to maintain a table of registered
-subsystems, set of events they provide, set of events they want to receive,
-etc.. Basing on this table, it routes appropriate information to
-appropriate parties.
-</li>
-<li>
-user interface is then just one of clients of system monitor, albeit possessing
-special privileges.
-</li>
-<li>
-one of important tasks of system monitor, in case given
-object (subsystem) registers with it to be notified about certain events, is
-to ensure that such type of event can be possibly generated. This is to
-prevent subsystems from waiting for events coming from other non-existent
-subsystems. See the discussion above on satisfying dependencies.
-</li>
-</ul>
-<i><p>NOTE: this is one possible approach - a centralized one. It's worth to
-consider other approach, distributed, in which case each object (subsystem)
-sends and listens to the data at a meeting point specific to each other
-object. This eliminates (or drastically minimizes) the role of system
-monitor which is a single point of failure in centralized case.</p></i>
-</li>
-</ul>
-
-<hr>
-
-<p>Here is my initial proposal for the User Interface hierarchy:</p>
-
-<ul>
-<li>
-System configuration.
- <ol>
- <li>
- Boot device and file <br>
- <small>Name of the boot device (possibly networked) and boot
- image.</small>
- <ol>
- <li>
- (Enumeration of available devices)
- <ol>
- <li>
- (Enumeration of available files)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Config file <br>
- <small>Configuration file management - loading and saving, either
- local or remote (if applicable). </small>
- <ol>
- <li>
- Load / Save
- <ol>
- <li>
- Source / Destination <br>
- (Enumeration of available storage places, possibly
- networked)
- </li>
- </ol>
- </li>
- <li>
- Edit directly (geek mode)
- </li>
- </ol>
- </li>
- <li>
- Subsystems <br>
- <ol>
- <li>
- Module management <br>
- <small>Optional hardware drivers and protocol modules
- management.</small>
- <ol>
- <li>
- (Enumeration of available loadable modules)
- <ol>
- <li>
- Load / unload / status
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Package management<br>
- <small>Management of basic and optional system services.</small>
- <ol>
- <li>
- (Enumeration of locally available packages)
- <ol>
- <li>
- Start / Stop / Status / Configure
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Default source of service packages<br>
- <small>Where to automatically get the missing packages from.
- </small>
- <ol>
- <li>
- (Enumeration of available media) <br>
- (local and remote disks, ftp, http)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Resource management
- <ol>
- <li>
- Memory consumption <br>
- <small>This is entry point to a subtree, which allows to set
- up various resource limits for subsystems, services and
- processes.</small>
- </li>
- <li>
- Space consumption<br>
- <small>(Things like minimal free space on permanent storage..)
- </small>
- </li>
- <li>
- Task priorities
- <small>This includes not only currently running tasks, but all
- which can possibly be started.</small>
- <ol>
- <li>
- List / Modify
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- System console
- </li>
- <li>
- Virtual consoles (if applicable)
- </li>
- <li>
- System Date / Time Zone
- </li>
- <li>
- Banner
- </li>
- <li>
- Logging
- <ol>
- <li>
- Local logging
- </li>
- <li>
- Remote logging
- </li>
- </ol>
- </li>
- </ol>
-</li>
-<li>
-Network configuration.
- <ol>
- <li>
- Hostname and Domain
- </li>
- <li>
- Interfaces
- <ol>
- <li>
- (Enumeration of physical interfaces) <br>
- (Enumeration of virtual interfaces, if applicable) <br>
- (Options for creating virtual interfaces, if applicable)
- <ol>
- <li>
- Interface options (speed, media, encapsulation,
- description, etc.)
- </li>
- <li>
- ARP
- </li>
- <li>
- Bridging
- </li>
- <li>
- IP
- <ol>
- <li>
- Adress / netmask / alias
- </li>
- </ol>
- </li>
- <li>
- IPX
- </li>
- <li>
- AppleTalk
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Protocol Options
- <ol>
- <li>
- IP, UDP, TCP, ARP, IPX, ATM ... <br>
- (Enumeration of available protocols)
- <ol>
- <li>
- (Enumeration of protocol specific options, such as
- buffer sizes, algorithms, ARP tables etc)
- <ol>
- <li>
- List / Add / Delete / Modify / Set (where
- applicable)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Routes
- <ol>
- <li>
- List
- </li>
- <li>
- Static
- <ol>
- <li>
- Add / Delete / List
- <ol>
- <li>
- (route expression)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Dynamic
- <ol>
- <li>
- (Enumeration of available routing protocols)
- <ol>
- <li>
- Add / Delete / List
- <ol>
- <li>
- (route expression)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Network services
- <ol>
- <li>
- DNS
- <ol>
- <li>
- Hosts
- <ol>
- <li>
- Add / Delete / List
- <ol>
- <li>
- (hosts definitions)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Resolvers
- <ol>
- <li>
- Add / Delete / List
- <ol>
- <li>
- (hosts addresses)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- Local DNS server config
- </li>
- </ol>
- </li>
- <li>
- PPP
- <ol>
- <li>
- Server
- </li>
- <li>
- Client
- </li>
- </ol>
- </li>
- <li>
- NFS
- <ol>
- <li>
- Server
- </li>
- <li>
- Client
- </li>
- </ol>
- </li>
- <li>
- NIS
- </li>
- <li>
- DHCP
- <ol>
- <li>
- Add / Delete / Reserve / List
- <ol>
- <li>
- (IP address expressions)
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- SNMP
- <ol>
- <li>
- Protocol version
- </li>
- <li>
- Send traps to...
- </li>
- <li>
- Access Control Lists <br>
- <small>(This is either full-blown ACL system in case
- of SNMPv2, or a community string for SNMPv1.)</small>
- </li>
- </ol>
- </li>
- <li>
- Printing
- <ol>
- <li>
- Local / Remote
- <ol>
- <li>
- Printers
- <ol>
- <li>
- Add / Modify / Delete / List
- </li>
- </ol>
- </li>
- <li>
- Queues
- <ol>
- <li>
- Priority / Delete / List
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- SMB services
- </li>
- <li>
- Network Address Translation
- </li>
- <li>
- Packet filters
- </li>
- <li>
- Bandwidth Manager
- </li>
- <li>
- NTP
- </li>
- <li>
- Remote Access
- </li>
- </ol>
- </li>
- </ol>
-<li>
-User management.
- <ol>
- <li>
- User accounts
- <ol>
- <li>
- Add / Delete / Modify / List
- <ol>
- <li>
- Name / Password / ACL
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- User profiles
- <ol>
- <li>
- Access Control Lists.
- <ol>
- <li>
- Add / Delete / Modify / List
- <ol>
- <li>
- Name / Template / Definition
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- ACL Templates
- <ol>
- <li>
- Add / Delete / Modify / List
- <ol>
- <li>
- Name
- <ol>
- <li>
- Command restrictions list
- </li>
- <li>
- Location restrictions list
- </li>
- <li>
- Resources restrictions list
- </li>
- <li>
- Time restrictions list
- </li>
- <li>
- Authentication methods
- <ol>
- <li>
- Unix passwd
- </li>
- <li>
- S/Key
- </li>
- <li>
- Kerberos
- </li>
- <li>
- Radius
- </li>
- <li>
- TACACS
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
- </li>
- </ol>
-</li>
-<li>
-Other services
- <ol>
- <li>
- Cron tasks
- </li>
- </ol>
-</li>
-<li>
-Filesystems.
- <ol>
- <li>
- Local / Remote
- <ol>
- <li>
- (Enumeration of available FS-s)
- <ol>
- <li>
- FS / Mounting point / Options
- </li>
- </ol>
- </li>
- <li>
- Swap Partition / Swap File
- <ol>
- <li>
- Create / Turn on
- </li>
- </ol>
- </ol>
- </li>
- </ol>
-</li>
-<li>
-Environment
- <ol>
- <li>
- Set / Unset / List
- </li>
- </ol>
-</li>
-<li>
-System status
- <ol>
- <li>
- (Enumeration of available status items)
- </li>
- </ol>
-</li>
-<li>
-Diagnostics
- <ol>
- <li>
- Debug
- <ol>
- <li>
- (Enumeration of subsystems hierarchy, those of which can
- provide debugging data)
- <ol>
- <li>
- Set / Clear / Level
- </li>
- </ol>
- </li>
- </ol>
- </li>
- <li>
- System messages
- </li>
- <li>
- Ping / traceroute / rtquery
- </li>
- </ol>
-</li>
-</ul>
-
-<hr>
-<i>
-<p>Please send your comments to <A HREF="mailto:abial@freebsd.org">
-Andrzej Bialecki</a></p>
-<p>Last modified:
-@DATE@
-</p>
-</i>
-
-</body>
-</html>
diff --git a/release/picobsd/doc/src/bugs.html b/release/picobsd/doc/src/bugs.html
index 2eb29cee525d2..c878d00968316 100644
--- a/release/picobsd/doc/src/bugs.html
+++ b/release/picobsd/doc/src/bugs.html
@@ -1,5 +1,5 @@
<HTML>
-<! $Id: bugs.html,v 1.6 1998/11/01 20:01:40 abial Exp $ >
+<! $Id: bugs.html,v 1.3 1998/10/12 07:52:34 abial Exp $ >
<HEAD>
<TITLE>History and Bug fixes</TITLE>
</HEAD>
@@ -14,25 +14,9 @@ the list before reporting a new one.</p>
<p>We tried to make this software bug-free, but life is life... Sorry for the
inconvenience.</p>
-<h3>PicoBSD 0.43</h3>
-<ul>
-<li>
- 1999.01.19: A lot of fixes related to architectural changes in
- 3.0-current code. Most importantly, we run now ELF kernel and we use
- the new bootloader. This is most probably the last release of PicoBSD in
- its present shape - the next version will (hopefully) become a part of
- normal release building process.
-</li>
-</ul>
-
<h3>PicoBSD 0.42</h3>
<ul>
<li>
- 1999.01.15: Well, it seems that this version was for developers
- only... ;-) It was abandoned when recent massive changes in -current
- demanded more serious measures...
-</li>
-<li>
1998.10.15: Small fixes and updates to match the 3.0-RELEASE
source tree. The binary snapshot built from 3.0-R sources will
soon follow...
@@ -134,12 +118,12 @@ the list before reporting a new one.</p>
</ul>
<h5>Last modified:
-@DATE@
+Mon Oct 12 00:51:45 PDT 1998
</h5>
<HR align="center" width="100%">
<CENTER><h5>Any comments? Send them to
-<A HREF="mailto:abial@freebsd.org">the author</A> </h5></CENTER>
+<A HREF="mailto:abial@nask.pl">the author</A> </h5></CENTER>
</BODY>
</HTML>
diff --git a/release/picobsd/doc/src/faq.html b/release/picobsd/doc/src/faq.html
index 1a86d587f67c8..c45b56e784779 100644
--- a/release/picobsd/doc/src/faq.html
+++ b/release/picobsd/doc/src/faq.html
@@ -1,5 +1,5 @@
<HTML>
-<! $Id: faq.html,v 1.3 1998/10/28 16:16:31 abial Exp $ >
+<! $Id: faq.html,v 1.1 1998/09/26 17:23:01 abial Exp $ >
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Author" CONTENT="Dinesh Nair">
@@ -39,7 +39,7 @@ fully grown daemons, and PicoBSD as a system infested with
<P>PicoBSD has versions based on FreeBSD 3.0-RELEASE, 3.0-current and
FreeBSD 2.2.5-RELEASE.
-<A HREF="mailto:abial@freebsd.org">Andrzej Bialecki</A> maintains the <A HREF="http://www.freebsd.org/~picobsd/picobsd.html">FreeBSD
+<A HREF="mailto:abial@nask.pl">Andrzej Bialecki</A> maintains the <A HREF="http://www.freebsd.org/~picobsd/picobsd.html">FreeBSD
3.0-RELEASE and -current versions</A> and
<A HREF="mailto:dinesh@alphaque.com">Dinesh Nair</A>
maintains the <A HREF="http://info.net-gw.com/picoBSD/">FreeBSD
@@ -101,7 +101,7 @@ maintained by Dinesh Nair</LI>
Additional mirror sites will be brought online as demand increases. If
you're interested in mirroring the PicoBSD distribution, please get in
touch with <A HREF="mailto:dinesh@alphaque.com">Dinesh Nair</A> or
-<A HREF="mailto:abial@freebsd.org">Andrzej Bialecki</A>.
+<A HREF="mailto:abial@nask.pl">Andrzej Bialecki</A>.
<P><B>How do I copy it to the floppy?</B></p>
@@ -241,7 +241,7 @@ Handbook</A> or the <A HREF="http://www.freebsd.org/">FreeBSD Home</A>.
PicoBSD user community comes in. And big thanks to all of you who already
sent us some suggestions!</FONT></CENTER>
<P><B><FONT SIZE=-1>Last Modified:
-@DATE@
+Thu Oct 15 23:31:28 CEST 1998
</FONT></B></P>
</BODY>
</HTML>
diff --git a/release/picobsd/doc/src/hardware.html b/release/picobsd/doc/src/hardware.html
index 2954695f6481a..207508123e116 100644
--- a/release/picobsd/doc/src/hardware.html
+++ b/release/picobsd/doc/src/hardware.html
@@ -1,5 +1,5 @@
<html>
-<! $Id: hardware.html,v 1.1 1998/09/26 17:23:01 abial Exp $ >
+<! $Id: hardware.html,v 1.1.1.1 1998/08/27 17:38:42 abial Exp $ >
<body>
<h1><center>Lists of supported hardware configurations.</center></h1>
@@ -103,10 +103,5 @@ you'll find it as a cheap yet reliable alternative to commercial communication
servers :-)) This work is still in progress, and
<A HREF="beta.html">I need some people to test</a> the early
dial-in server version.</p>
-
-<hr>
-<i>Last modified:
-@DATE@
-</i>
</body>
</html>
diff --git a/release/picobsd/doc/src/how2build.html b/release/picobsd/doc/src/how2build.html
index 7225603a5039a..9a29f28bfcd14 100644
--- a/release/picobsd/doc/src/how2build.html
+++ b/release/picobsd/doc/src/how2build.html
@@ -1,5 +1,5 @@
<html>
-<! $Id: how2build.html,v 1.3 1998/10/28 16:16:31 abial Exp $ >
+<! $Id: how2build.html,v 1.1 1998/09/26 17:23:01 abial Exp $ >
<head>
<title><center>PicoBSD Development Kit</center></title>
</head>
@@ -184,10 +184,6 @@
<p>If, for some reason, the scripts don't work for you at all, also let me
know.</p>
-<hr>
-<i>Last modified:
-@DATE@
-
-<p><A HREF="mailto:abial@freebsd.org">&lt;abial@freebsd.org&gt;</a></i></p>
+<A HREF="mailto:abial@nask.pl">&lt;abial@nask.pl&gt;</a>
</body>
</html>
diff --git a/release/picobsd/doc/src/intrinsics.html b/release/picobsd/doc/src/intrinsics.html
index dc4ca55aba3cc..cac4703cbcbe2 100644
--- a/release/picobsd/doc/src/intrinsics.html
+++ b/release/picobsd/doc/src/intrinsics.html
@@ -1,5 +1,5 @@
<html>
-<! $Id: intrinsics.html,v 1.1 1998/09/26 17:23:01 abial Exp $ >
+<! $Id: intrinsics.html,v 1.1.1.1 1998/08/27 17:38:42 abial Exp $ >
<head>
<title><center>Details of building process</center></title>
</head>
@@ -122,5 +122,5 @@ the build process:</p>
<h6>
Last modified:
-@DATE@
+Wed Aug 19 18:49:08 CEST 1998
</h6>
diff --git a/release/picobsd/doc/src/intro.html b/release/picobsd/doc/src/intro.html
index 0b69b6b7b6633..c69622be2d9a7 100644
--- a/release/picobsd/doc/src/intro.html
+++ b/release/picobsd/doc/src/intro.html
@@ -1,5 +1,5 @@
<HTML>
-<! $Id: intro.html,v 1.5 1998/11/01 19:52:47 abial Exp $ >
+<! $Id: intro.html,v 1.2 1998/09/26 17:39:21 abial Exp $ >
<HEAD>
<TITLE>PicoBSD</TITLE>
</HEAD>
@@ -9,6 +9,7 @@
<HR shade align="center" size="8" width="25%"></CENTER>
+<IMG SRC="../../icons/daemon.gif" ALIGN="right">
<p><b>Contents:</b></p>
<ul>
<li>
@@ -156,7 +157,7 @@ version 0.4 it's a part of official FreeBSD CVS and lives in
<code>src/release/picobsd</code>. I also create the snapshots of this source
tree - keep in mind that they are not so up-to-date as the tree
in FreeBSD CVS. You can get the snapshot I made on
-Sun Nov 1 11:48:32 PST 1998
+Mon Oct 12 00:53:02 PDT 1998
<A HREF="http://www.freebsd.org/~picobsd/picobsd/picobsd.tgz">here</a>.</p>
<p> Now, if you don't like the setup of PicoBSD, or you miss
@@ -215,15 +216,14 @@ imagination and coding skills:</p>
<ul>
<li>
To write a command line tool patterned after Cisco IOS, which could configure
-various aspects of router-like version of PicoBSD.
-<p>Well, currently you can read very preliminary draft of proposed
-architecture, called the <A HREF="UCI.html">Unified Configuration Interface.</a></p>
+various aspects of router-like version of PicoBSD. I'm nowhere near with this
+goal - I even don't have any good idea how to do it cleanly (I do have some
+ideas, but I classify them as dirty hacks).
</li>
<li>
To put an XWindow-like GUI on the 'dialup' floppy. (Update: you can look at
<A HREF="http://www.freebsd.org/~picobsd/preview/preview2.tgz">preview
-version</a> and send me your comments. <b>I need some help in porting newer
-version of W</b>).
+version</a> and send me your comments).
</li>
<li>
To gain some experience with solid state disks, and prepare standard images
@@ -247,23 +247,23 @@ to be able to run truely effortlessly on 4MB machines... This would
probably include rewriting oinit(8) to run multithreaded.
</li>
<li>
-And many others... You can find a complete list
-<A HREF="TODO.html">here</a>.
+And many others, too vague to put them here. <b>You</b> can also suggest me
+some others applications/solutions you're dreaming of...
</li>
</ul>
<A NAME="credits"><h3>Credits</h3>
<p>The following people are either responsible for the very existence of this
-project, or significantly eased my pains in gaining necessary knowledge:</p>
+project, or significantly eased my pains of gaining necessary knowledge:</p>
<ul>
<li>
the whole FreeBSD team for this magnificent OS, and their hard work of
continuous development,
</li>
<li>
-Dinesh Nair, for co-development and preparing of the version which compiled
-on 2.2.5-RELEASE,
+Dinesh Nair, for co-development and preparing of the version which compiles
+on -RELEASE,
</li>
<li>
Joe Greco, for his encouraging example of XKERNEL (some parts of the scripts
@@ -292,15 +292,15 @@ guys!
which allows you to use it in various ways, including commercial
applications. So grab it and enjoy! And if you feel that you want to help
with this project, either by donating some time to write code, or by
-some other donation, just <A HREF="mailto:abial@freebsd.org">contact me</a>.</p>
+some other donation, just <A HREF="mailto:abial@nask.pl">contact me</a>.</p>
<h5>Last modified:
-@DATE@
+Fri Sep 4 01:17:44 PDT 1998
</h5>
<HR shade align="left" size="2" width="100%">
<CENTER><h5>Any comments? Send them to
-<A HREF="mailto:abial@freebsd.org">the author</A> </h5></CENTER>
+<A HREF="mailto:abial@nask.pl">the author</A> </h5></CENTER>
</BODY>
</HTML>
generated by cgit v1.2.3 (git 2.25.1) at 2025-11-09 20:58:17 +0000