From d50984ba5fd40ca43c643abe4702a199a4b80f48 Mon Sep 17 00:00:00 2001
From: Luigi Rizzo
Date: Wed, 24 Mar 2004 08:01:15 +0000
Subject: [PATCH] remove stale documentation
---
release/picobsd/README.html | 19 -
release/picobsd/doc/src/Makefile | 17 -
release/picobsd/doc/src/TODO.html | 154 ----
release/picobsd/doc/src/UCI.html | 960 ----------------------
release/picobsd/doc/src/bugs.html | 152 ----
release/picobsd/doc/src/faq.html | 243 ------
release/picobsd/doc/src/hardware.html | 112 ---
release/picobsd/doc/src/how2build.html | 197 -----
release/picobsd/doc/src/installflp.html | 99 ---
release/picobsd/doc/src/intrinsics.html | 122 ---
release/picobsd/doc/src/intro.html | 303 -------
release/picobsd/help/README | 8 -
release/picobsd/help/cat.hlp.en | 5 -
release/picobsd/help/cat.hlp.pl | 5 -
release/picobsd/help/chmod.hlp.en | 5 -
release/picobsd/help/chmod.hlp.pl | 5 -
release/picobsd/help/chown.hlp.en | 8 -
release/picobsd/help/chown.hlp.pl | 8 -
release/picobsd/help/cp.hlp.en | 6 -
release/picobsd/help/cp.hlp.pl | 6 -
release/picobsd/help/df.hlp.en | 5 -
release/picobsd/help/df.hlp.pl | 5 -
release/picobsd/help/dialup.hlp.en | 4 -
release/picobsd/help/dialup.hlp.pl | 5 -
release/picobsd/help/dmesg.hlp.en | 5 -
release/picobsd/help/dmesg.hlp.pl | 5 -
release/picobsd/help/echo.hlp.en | 8 -
release/picobsd/help/echo.hlp.pl | 8 -
release/picobsd/help/ee.hlp.en | 4 -
release/picobsd/help/ee.hlp.pl | 4 -
release/picobsd/help/fsck.hlp.en | 15 -
release/picobsd/help/fsck.hlp.pl | 15 -
release/picobsd/help/ftp.hlp.en | 8 -
release/picobsd/help/ftp.hlp.pl | 8 -
release/picobsd/help/gzip.hlp.en | 26 -
release/picobsd/help/gzip.hlp.pl | 12 -
release/picobsd/help/help.hlp.en | 7 -
release/picobsd/help/help.hlp.pl | 7 -
release/picobsd/help/hostname.hlp.en | 5 -
release/picobsd/help/hostname.hlp.pl | 5 -
release/picobsd/help/ifconfig.hlp.en | 18 -
release/picobsd/help/ifconfig.hlp.pl | 18 -
release/picobsd/help/kbdcontrol.hlp.en | 7 -
release/picobsd/help/kbdcontrol.hlp.pl | 7 -
release/picobsd/help/kget.hlp.en | 21 -
release/picobsd/help/kget.hlp.pl | 23 -
release/picobsd/help/kill.hlp.en | 8 -
release/picobsd/help/kill.hlp.pl | 8 -
release/picobsd/help/ln.hlp.en | 9 -
release/picobsd/help/ln.hlp.pl | 9 -
release/picobsd/help/ls.hlp.en | 10 -
release/picobsd/help/ls.hlp.pl | 11 -
release/picobsd/help/mkdir.hlp.en | 5 -
release/picobsd/help/mkdir.hlp.pl | 5 -
release/picobsd/help/more.hlp.en | 7 -
release/picobsd/help/more.hlp.pl | 8 -
release/picobsd/help/mount.hlp.en | 21 -
release/picobsd/help/mount.hlp.pl | 19 -
release/picobsd/help/mount_cd9660.hlp.en | 9 -
release/picobsd/help/mount_cd9660.hlp.pl | 9 -
release/picobsd/help/mount_ext2fs.hlp.en | 11 -
release/picobsd/help/mount_ext2fs.hlp.pl | 11 -
release/picobsd/help/mount_msdosfs.hlp.en | 13 -
release/picobsd/help/mount_msdosfs.hlp.pl | 13 -
release/picobsd/help/moused.hlp.en | 44 -
release/picobsd/help/moused.hlp.pl | 29 -
release/picobsd/help/mv.hlp.en | 9 -
release/picobsd/help/mv.hlp.pl | 9 -
release/picobsd/help/ping.hlp.en | 10 -
release/picobsd/help/ping.hlp.pl | 10 -
release/picobsd/help/ppp.hlp.en | 16 -
release/picobsd/help/ppp.hlp.pl | 14 -
release/picobsd/help/ps.hlp.en | 9 -
release/picobsd/help/ps.hlp.pl | 7 -
release/picobsd/help/pwd.hlp.en | 1 -
release/picobsd/help/pwd.hlp.pl | 1 -
release/picobsd/help/reboot.hlp.en | 3 -
release/picobsd/help/reboot.hlp.pl | 3 -
release/picobsd/help/rm.hlp.en | 13 -
release/picobsd/help/rm.hlp.pl | 12 -
release/picobsd/help/route.hlp.en | 13 -
release/picobsd/help/route.hlp.pl | 13 -
release/picobsd/help/sh.hlp.en | 3 -
release/picobsd/help/sh.hlp.pl | 3 -
release/picobsd/help/shutdown.hlp.en | 3 -
release/picobsd/help/shutdown.hlp.pl | 3 -
release/picobsd/help/ssh.hlp.en | 29 -
release/picobsd/help/ssh.hlp.pl | 29 -
release/picobsd/help/sysctl.hlp.en | 15 -
release/picobsd/help/sysctl.hlp.pl | 15 -
release/picobsd/help/telnet.hlp.en | 14 -
release/picobsd/help/telnet.hlp.pl | 14 -
release/picobsd/help/test.hlp.en | 1 -
release/picobsd/help/test.hlp.pl | 1 -
release/picobsd/help/traceroute.hlp.en | 14 -
release/picobsd/help/traceroute.hlp.pl | 14 -
release/picobsd/help/umount.hlp.en | 12 -
release/picobsd/help/umount.hlp.pl | 12 -
release/picobsd/help/vidcontrol.hlp.en | 7 -
release/picobsd/help/vidcontrol.hlp.pl | 7 -
release/picobsd/help/vm.hlp.en | 12 -
release/picobsd/help/vm.hlp.pl | 14 -
102 files changed, 3313 deletions(-)
delete mode 100644 release/picobsd/README.html
delete mode 100644 release/picobsd/doc/src/Makefile
delete mode 100644 release/picobsd/doc/src/TODO.html
delete mode 100644 release/picobsd/doc/src/UCI.html
delete mode 100644 release/picobsd/doc/src/bugs.html
delete mode 100644 release/picobsd/doc/src/faq.html
delete mode 100644 release/picobsd/doc/src/hardware.html
delete mode 100644 release/picobsd/doc/src/how2build.html
delete mode 100644 release/picobsd/doc/src/installflp.html
delete mode 100644 release/picobsd/doc/src/intrinsics.html
delete mode 100644 release/picobsd/doc/src/intro.html
delete mode 100644 release/picobsd/help/README
delete mode 100644 release/picobsd/help/cat.hlp.en
delete mode 100644 release/picobsd/help/cat.hlp.pl
delete mode 100644 release/picobsd/help/chmod.hlp.en
delete mode 100644 release/picobsd/help/chmod.hlp.pl
delete mode 100644 release/picobsd/help/chown.hlp.en
delete mode 100644 release/picobsd/help/chown.hlp.pl
delete mode 100644 release/picobsd/help/cp.hlp.en
delete mode 100644 release/picobsd/help/cp.hlp.pl
delete mode 100644 release/picobsd/help/df.hlp.en
delete mode 100644 release/picobsd/help/df.hlp.pl
delete mode 100644 release/picobsd/help/dialup.hlp.en
delete mode 100644 release/picobsd/help/dialup.hlp.pl
delete mode 100644 release/picobsd/help/dmesg.hlp.en
delete mode 100644 release/picobsd/help/dmesg.hlp.pl
delete mode 100644 release/picobsd/help/echo.hlp.en
delete mode 100644 release/picobsd/help/echo.hlp.pl
delete mode 100644 release/picobsd/help/ee.hlp.en
delete mode 100644 release/picobsd/help/ee.hlp.pl
delete mode 100644 release/picobsd/help/fsck.hlp.en
delete mode 100644 release/picobsd/help/fsck.hlp.pl
delete mode 100644 release/picobsd/help/ftp.hlp.en
delete mode 100644 release/picobsd/help/ftp.hlp.pl
delete mode 100644 release/picobsd/help/gzip.hlp.en
delete mode 100644 release/picobsd/help/gzip.hlp.pl
delete mode 100644 release/picobsd/help/help.hlp.en
delete mode 100644 release/picobsd/help/help.hlp.pl
delete mode 100644 release/picobsd/help/hostname.hlp.en
delete mode 100644 release/picobsd/help/hostname.hlp.pl
delete mode 100644 release/picobsd/help/ifconfig.hlp.en
delete mode 100644 release/picobsd/help/ifconfig.hlp.pl
delete mode 100644 release/picobsd/help/kbdcontrol.hlp.en
delete mode 100644 release/picobsd/help/kbdcontrol.hlp.pl
delete mode 100644 release/picobsd/help/kget.hlp.en
delete mode 100644 release/picobsd/help/kget.hlp.pl
delete mode 100644 release/picobsd/help/kill.hlp.en
delete mode 100644 release/picobsd/help/kill.hlp.pl
delete mode 100644 release/picobsd/help/ln.hlp.en
delete mode 100644 release/picobsd/help/ln.hlp.pl
delete mode 100644 release/picobsd/help/ls.hlp.en
delete mode 100644 release/picobsd/help/ls.hlp.pl
delete mode 100644 release/picobsd/help/mkdir.hlp.en
delete mode 100644 release/picobsd/help/mkdir.hlp.pl
delete mode 100644 release/picobsd/help/more.hlp.en
delete mode 100644 release/picobsd/help/more.hlp.pl
delete mode 100644 release/picobsd/help/mount.hlp.en
delete mode 100644 release/picobsd/help/mount.hlp.pl
delete mode 100644 release/picobsd/help/mount_cd9660.hlp.en
delete mode 100644 release/picobsd/help/mount_cd9660.hlp.pl
delete mode 100644 release/picobsd/help/mount_ext2fs.hlp.en
delete mode 100644 release/picobsd/help/mount_ext2fs.hlp.pl
delete mode 100644 release/picobsd/help/mount_msdosfs.hlp.en
delete mode 100644 release/picobsd/help/mount_msdosfs.hlp.pl
delete mode 100644 release/picobsd/help/moused.hlp.en
delete mode 100644 release/picobsd/help/moused.hlp.pl
delete mode 100644 release/picobsd/help/mv.hlp.en
delete mode 100644 release/picobsd/help/mv.hlp.pl
delete mode 100644 release/picobsd/help/ping.hlp.en
delete mode 100644 release/picobsd/help/ping.hlp.pl
delete mode 100644 release/picobsd/help/ppp.hlp.en
delete mode 100644 release/picobsd/help/ppp.hlp.pl
delete mode 100644 release/picobsd/help/ps.hlp.en
delete mode 100644 release/picobsd/help/ps.hlp.pl
delete mode 100644 release/picobsd/help/pwd.hlp.en
delete mode 100644 release/picobsd/help/pwd.hlp.pl
delete mode 100644 release/picobsd/help/reboot.hlp.en
delete mode 100644 release/picobsd/help/reboot.hlp.pl
delete mode 100644 release/picobsd/help/rm.hlp.en
delete mode 100644 release/picobsd/help/rm.hlp.pl
delete mode 100644 release/picobsd/help/route.hlp.en
delete mode 100644 release/picobsd/help/route.hlp.pl
delete mode 100644 release/picobsd/help/sh.hlp.en
delete mode 100644 release/picobsd/help/sh.hlp.pl
delete mode 100644 release/picobsd/help/shutdown.hlp.en
delete mode 100644 release/picobsd/help/shutdown.hlp.pl
delete mode 100644 release/picobsd/help/ssh.hlp.en
delete mode 100644 release/picobsd/help/ssh.hlp.pl
delete mode 100644 release/picobsd/help/sysctl.hlp.en
delete mode 100644 release/picobsd/help/sysctl.hlp.pl
delete mode 100644 release/picobsd/help/telnet.hlp.en
delete mode 100644 release/picobsd/help/telnet.hlp.pl
delete mode 100644 release/picobsd/help/test.hlp.en
delete mode 100644 release/picobsd/help/test.hlp.pl
delete mode 100644 release/picobsd/help/traceroute.hlp.en
delete mode 100644 release/picobsd/help/traceroute.hlp.pl
delete mode 100644 release/picobsd/help/umount.hlp.en
delete mode 100644 release/picobsd/help/umount.hlp.pl
delete mode 100644 release/picobsd/help/vidcontrol.hlp.en
delete mode 100644 release/picobsd/help/vidcontrol.hlp.pl
delete mode 100644 release/picobsd/help/vm.hlp.en
delete mode 100644 release/picobsd/help/vm.hlp.pl
diff --git a/release/picobsd/README.html b/release/picobsd/README.html
deleted file mode 100644
index aca246fe0d7..00000000000
--- a/release/picobsd/README.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
- PicoBSD Development Kit
-
-All documentation, instructions, list of supported hardware and FAQ are
-in doc/ directory. If they are missing, go to the doc/src/ subdirectory and
-do a 'make'. The docs are marked with HTML tags, but we try to keep
-them readable even without a browser.
-
-
Please start from here for general
-description of the project and its features, or just go directly
-here for detailed instructions on how to
-build your version of PicoBSD.
-
-
Enjoy!
-
-
-
-
diff --git a/release/picobsd/doc/src/Makefile b/release/picobsd/doc/src/Makefile
deleted file mode 100644
index c5f4aeb0836..00000000000
--- a/release/picobsd/doc/src/Makefile
+++ /dev/null
@@ -1,17 +0,0 @@
-#
-# $FreeBSD$
-#
-
-.include "../../Version"
-
-DATE!="date"
-
-DOCS= bugs.html faq.html hardware.html how2build.html \
- intrinsics.html intro.html TODO.html installflp.html
-
-all: ../../Version
- for i in ${DOCS}; \
- do \
- cat $${i}|sed -e 's/@VER@/${VER}/g' \
- -e 's/@DATE@/${DATE}/g' >../$${i}; \
- done
diff --git a/release/picobsd/doc/src/TODO.html b/release/picobsd/doc/src/TODO.html
deleted file mode 100644
index c2bbf07e34a..00000000000
--- a/release/picobsd/doc/src/TODO.html
+++ /dev/null
@@ -1,154 +0,0 @@
-
-
-
- Small FreeBSD ToDo List.
-
-
-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.
-
-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
-(Andrzej Bialecki).
-
-
-
-Short term tasks:
-
-
--
-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.45).
-
--
-Provide options for building separate kernel and FS images of
-various sizes.
-
--
-Add some "wizards" to help people new to Unix configure "dialup"
-and "net" for most common tasks.
-
--
-Replace most of currently used scripts with Makefiles.
-(NOTE: this will be resolved in v. 0.45).
-
--
-Add simple authentication module to oinit.
-
--
-Fix kzip to be able to produce kzip'ped ELF kernels.
-(NOTE: currently we work around it by using kzipped /boot/loader).
-
--
-Write better documentation. This is very important - the most
-common configurations should be described in detail, step by step.
-
--
-Collect our experiences with using FreeBSD with SBCs, flash disks
-etc, and write a short practical guide to embedding FreeBSD.
-
-
-
-
-Medium term tasks:
-
-
--
-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.
-
--
-Change the building process so that it allows to easily choose
-(with finer granularity) needed components of the target system.
-
--
-Make use of recently added KLD to allow for easy adding and
-removing drivers when running stripped kernels.
-
--
-Investigate pros and cons of using the new boot/loader together
-with ELF kernels.
-(NOTE for v.0.43: it was simply mandatory to start to use it :-)
-
--
-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.
-
--
-Integrate DHCP into "dialup" version.
-
--
-Rework oinit to be more modular, and write additional modules
-(remote access, SNMP (?), authentication, shell(), configuration
-editor).
-
--
-Provide a remote access (telnetd/login/shell) module for the
-"router" version. Make the shell() module more predictable and
-compatible with common sense :-)
-
--
-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.
-
-
-
-
-
-Long term tasks:
-
-
--
-Either port ROMfs from Linux, or write our own replacement for it.
-
--
-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.
-
--
-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.
-
--
-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.
-
--
-Reduce memory footprint.
-
--
-Add other language versions.
-
--
-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.
-
-
-
-
-
-Other half-baked ideas...
-
-(fill this in :-)
-
-
-Last modified:
-@DATE@
-
-
-Send your comments, ideas, and most importantly the code itself, to
-abial@freebsd.org.
-
-
-
diff --git a/release/picobsd/doc/src/UCI.html b/release/picobsd/doc/src/UCI.html
deleted file mode 100644
index 5c0caaab505..00000000000
--- a/release/picobsd/doc/src/UCI.html
+++ /dev/null
@@ -1,960 +0,0 @@
-
-
-
- Unified Configuration Interface Project
-
-
-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.
-
-This project involves such issues as:
-
--
-providing consistent view of the system and its functional subsystems as
-a set of interrelated objects equipped with certain properties.
-
--
-providing global approach to user interface, either command-line or with GUI
-front-ends.
-
--
-managing system resources and subsystems. This includes managing
-static and dynamic interdependencies between subsystems, ability to
-upgrade/downgrade specific subsystems on-the-fly.
-
-
-
-
-This is work in progress - 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.
-
-
-
-
- Unified Configuration Interface
-
-
-
--
-
Let's first introduce the following terms:
-
--
-management base - 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.
-
--
-user interface - 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.
-
--
-system monitor - 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.
-
--
-subsystem - 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.
-
-
-
--
-
One possible approach to storing the management data is to use already
-existing framework known as MIB, as defined in applicable RFCs.
-
-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.
-
-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.
-
-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).
-
-So, if we decide to use it, we need to address these issues somehow.
-The next point presents one possible approach to this dilemma.
-
--
-
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).
-
-Each object represented in management base can be characterized by
-following properties:
-
--
-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.
-
--
-a temporary space for new sets of parameters, which are being supplied by
-other subsystems, prior to their actual application,
-
--
-FSM definition, describing state transitions in reaction to received events,
-
--
-list of events it can generate and accept,
-
--
-list of dependencies on other objects' states and services,
-
--
-list of requests it can handle,
-
--
-list of parameters it can accept and/or provide, with their valid ranges.
-
-
-
-
-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).
-
-The set of symbolic states may consist of the following states,
-depicting object's current internal state (as described by its FSM):
-
-
-| Name | Meaning |
-
-| INIT | the subsystem is initializing itself, possibly loading
-necessary data and binaries from permanent storage. |
-
-
-| CHECK | performing consistency check on newly supplied parameter values |
-
-
-| READY | ready to start performing its primary function, but not started |
-
-
-| START | start-up tasks (related to its primary function, as opposed
-to INIT which is related to its own initialization) |
-
-
-| STOP | stop (shutdown) tasks (when the object intends to stop
-performing its function). This can involve unloading data and binaries from
-main memory. |
-
-
-| RUN | primary (work) phase |
-
-
-| IDLE | waiting for some external event to happen |
-
-
-| BUSY | the subsystem is busy (either with performing some
-high-priority task, or just simply hung), and cannot be interrupted without
-complete restart, |
-
-
-| ERROR | this object is either improperly configured, or
-malfunctioning |
-
-
-| (other...) | (other...) |
-
-
-
-
-The set of possible actions may include the following actions:
-
-
-| Name | Meaning |
-
-| LIST_EV_REQ | get list of events the subsystem can generate |
-
-
-| LIST_ACT_REQ | get list of actions the subsystem can respond to |
-
-
-| GET_DEF_REQ | get definition of given parameter (the arguments, and
-valid ranges) |
-
-
-| SET_REQ | set given parameter to given value (this value will
-be used only after COMMIT_REQ) |
-
-
-| GET_REQ | get currently used value of given parameter |
-
-
-| COMMIT_REQ | commit changes supplied in last transaction to currently
-used set of parameters |
-
-
-| ROLLBACK_REQ | revert last commit |
-
-
-| INIT_REQ | perform initialization tasks |
-
-
-| START_REQ | start performing primary function |
-
-
-| STOP_REQ | stop performing primary function |
-
-
-| RESTART_REQ | restart operation, possibly forcefully |
-
-
-| NOTIFY_REQ | notify me of any changes in your state |
-
-
-| CHECK_REQ | perform self-consistency check |
-
-
-| UPGRADE_REQ | 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. |
-
-
-| DOWNGRADE_REQ | downgrade the subsystem - restore the previous
-version of the subsystem from the copy on permanent storage. |
-
-
-| UNINSTALL_REQ | uninstall the subsystem completely - possibly
-freeing the space on permanent storage. |
-
-
-| (other...) | (other...) |
-
-
-(Each request includes source service identifier and credentials of
-the sender)
-
-The set of events which can be generated by subsystems may include
-the following:
-
-
-| Name | Meaning |
-
-| EV_ACK | positive acknowledge of the last operation |
-
-
-| EV_NACK | negative acknowledge of the last operation |
-
-
-| EV_CHANGE | change notification (includes the name of changed
-parameter, and/or FSM state change) |
-
-
-| EV_DEP | 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). |
-
-
-| (other...) | (other...) |
-
-
-
-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.
-
-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.
-
-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").
-
-
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.
-
--
-
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.
-
-More acceptable UI would collect interrelated items under common menu
-entries, irrespectibly of their actual position in the MIB tree.
-
-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.
-
--
-
The management database should be easily exportable via standard
-protocols, such as SNMP or LDAP.
-
-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.
-
-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.
-
--
-
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.
-
-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.
-
-Operations should be verified against allowed values, as well as against
-allowed credentials, and basing on this either committed or aborted.
-
--
-
A few notes on possible implementation of system monitor:
-
--
-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.
-
--
-configuration information itself is stored either in binary database, or as
-a filesystem hierachy mimicking configuration items hierarchy.
-
--
-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).
-
This probably means also that some libc routines would have to be replaced,
-because they assume reading configuration from certain disk files.
-
-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).
-
--
-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...
-
--
-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.
-
--
-user interface is then just one of clients of system monitor, albeit possessing
-special privileges.
-
--
-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.
-
-
-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.
-
-
-
-
-
-Here is my initial proposal for the User Interface hierarchy:
-
-
--
-System configuration.
-
- -
- Boot device and file
- Name of the boot device (possibly networked) and boot
- image.
-
- -
- (Enumeration of available devices)
-
- -
- (Enumeration of available files)
-
-
-
-
-
- -
- Config file
- Configuration file management - loading and saving, either
- local or remote (if applicable).
-
- -
- Load / Save
-
- -
- Source / Destination
- (Enumeration of available storage places, possibly
- networked)
-
-
-
- -
- Edit directly (geek mode)
-
-
-
- -
- Subsystems
-
- -
- Module management
- Optional hardware drivers and protocol modules
- management.
-
- -
- (Enumeration of available loadable modules)
-
- -
- Load / unload / status
-
-
-
-
-
- -
- Package management
- Management of basic and optional system services.
-
- -
- (Enumeration of locally available packages)
-
- -
- Start / Stop / Status / Configure
-
-
-
-
-
- -
- Default source of service packages
- Where to automatically get the missing packages from.
-
-
- -
- (Enumeration of available media)
- (local and remote disks, ftp, http)
-
-
-
-
-
- -
- Resource management
-
- -
- Memory consumption
- This is entry point to a subtree, which allows to set
- up various resource limits for subsystems, services and
- processes.
-
- -
- Space consumption
- (Things like minimal free space on permanent storage..)
-
-
- -
- Task priorities
- This includes not only currently running tasks, but all
- which can possibly be started.
-
- -
- List / Modify
-
-
-
-
-
- -
- System console
-
- -
- Virtual consoles (if applicable)
-
- -
- System Date / Time Zone
-
- -
- Banner
-
- -
- Logging
-
- -
- Local logging
-
- -
- Remote logging
-
-
-
-
-
--
-Network configuration.
-
- -
- Hostname and Domain
-
- -
- Interfaces
-
- -
- (Enumeration of physical interfaces)
- (Enumeration of virtual interfaces, if applicable)
- (Options for creating virtual interfaces, if applicable)
-
- -
- Interface options (speed, media, encapsulation,
- description, etc.)
-
- -
- ARP
-
- -
- Bridging
-
- -
- IP
-
- -
- Adress / netmask / alias
-
-
-
- -
- IPX
-
- -
- AppleTalk
-
-
-
-
-
- -
- Protocol Options
-
- -
- IP, UDP, TCP, ARP, IPX, ATM ...
- (Enumeration of available protocols)
-
- -
- (Enumeration of protocol specific options, such as
- buffer sizes, algorithms, ARP tables etc)
-
- -
- List / Add / Delete / Modify / Set (where
- applicable)
-
-
-
-
-
-
-
- -
- Routes
-
- -
- List
-
- -
- Static
-
- -
- Add / Delete / List
-
- -
- (route expression)
-
-
-
-
-
- -
- Dynamic
-
- -
- (Enumeration of available routing protocols)
-
- -
- Add / Delete / List
-
- -
- (route expression)
-
-
-
-
-
-
-
-
-
- -
- Network services
-
- -
- DNS
-
- -
- Hosts
-
- -
- Add / Delete / List
-
- -
- (hosts definitions)
-
-
-
-
-
- -
- Resolvers
-
- -
- Add / Delete / List
-
- -
- (hosts addresses)
-
-
-
-
-
- -
- Local DNS server config
-
-
-
- -
- PPP
-
- -
- Server
-
- -
- Client
-
-
-
- -
- NFS
-
- -
- Server
-
- -
- Client
-
-
-
- -
- NIS
-
- -
- DHCP
-
- -
- Add / Delete / Reserve / List
-
- -
- (IP address expressions)
-
-
-
-
-
- -
- SNMP
-
- -
- Protocol version
-
- -
- Send traps to...
-
- -
- Access Control Lists
- (This is either full-blown ACL system in case
- of SNMPv2, or a community string for SNMPv1.)
-
-
-
- -
- Printing
-
- -
- Local / Remote
-
- -
- Printers
-
- -
- Add / Modify / Delete / List
-
-
-
- -
- Queues
-
- -
- Priority / Delete / List
-
-
-
-
-
-
-
- -
- SMB services
-
- -
- Network Address Translation
-
- -
- Packet filters
-
- -
- Bandwidth Manager
-
- -
- NTP
-
- -
- Remote Access
-
-
-
-
- -
-User management.
-
- -
- User accounts
-
- -
- Add / Delete / Modify / List
-
- -
- Name / Password / ACL
-
-
-
-
-
- -
- User profiles
-
- -
- Access Control Lists.
-
- -
- Add / Delete / Modify / List
-
- -
- Name / Template / Definition
-
-
-
-
-
- -
- ACL Templates
-
- -
- Add / Delete / Modify / List
-
- -
- Name
-
- -
- Command restrictions list
-
- -
- Location restrictions list
-
- -
- Resources restrictions list
-
- -
- Time restrictions list
-
- -
- Authentication methods
-
- -
- Unix passwd
-
- -
- S/Key
-
- -
- Kerberos
-
- -
- Radius
-
- -
- TACACS
-
-
-
-
-
-
-
-
-
-
-
-
-
--
-Other services
-
- -
- Cron tasks
-
-
-
--
-Filesystems.
-
- -
- Local / Remote
-
- -
- (Enumeration of available FS-s)
-
- -
- FS / Mounting point / Options
-
-
-
- -
- Swap Partition / Swap File
-
- -
- Create / Turn on
-
-
-
-
-
-
--
-Environment
-
- -
- Set / Unset / List
-
-
-
--
-System status
-
- -
- (Enumeration of available status items)
-
-
-
--
-Diagnostics
-
- -
- Debug
-
- -
- (Enumeration of subsystems hierarchy, those of which can
- provide debugging data)
-
- -
- Set / Clear / Level
-
-
-
-
-
- -
- System messages
-
- -
- Ping / traceroute / rtquery
-
-
-
-
-
-
-
-Please send your comments to
-Andrzej Bialecki
-Last modified:
-@DATE@
-
-
-
-
-
diff --git a/release/picobsd/doc/src/bugs.html b/release/picobsd/doc/src/bugs.html
deleted file mode 100644
index f7c91c99b3f..00000000000
--- a/release/picobsd/doc/src/bugs.html
+++ /dev/null
@@ -1,152 +0,0 @@
-
-
-
- History and Bug fixes
-
-
-
-History and List of Bugfixes
-
-This is the short release history of PicoBSD, as well as the list of bugs
-which were found. Some of them were already corrected, so that you should read
-the list before reporting a new one.
-
-We tried to make this software bug-free, but life is life... Sorry for the
- inconvenience.
-
-PicoBSD 0.44
-
--
- 1999.05.10: Slightly refreshed version to match 3.2-RELEASE.
- No significant changes (yet)... :-(
-
-
-PicoBSD 0.43
-
--
- 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.
-
-
-
-PicoBSD 0.42
-
--
- 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...
-
--
- 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...
-
-
-
-PicoBSD 0.41
-
--
- 1998.10.12: Two small buglets has been discovered, and fixed in CVS
- copy of the sources. 'kget' utility was dumping core due to unexpected
- change in behaviour of dumpnlist. 'ns' utility poorly handled other
- netmasks than class C network.
-
I prepared new tar archive containing these corrected sources.
-
--
- 1998.09.26: Yes, this took more than just "a few days"... :-(. This is
- mainly a bugfix release of 0.4 - almost no new features were added,
- except the 'dmesg' to examine kernel messages buffer. Also, all
- programs are compiled in ELF format. SNMP services are provided now
- by UCD-SNMP v.3.5.
-
-
Unfortunately, I had to remove DEVFS for now - there are too many
- problems with it for now. This also means that we're back to creating
- device nodes manually, and chances are that the one you need is
- missing...
-
-
-
-PicoBSD 0.4
-
--
- 1998.08.28: Serious bug was discovered in MFS code (thanks to Eric
- P. Scott for detailed bug report!). Though the bug itself is in
- FreeBSD-current kernel code and not in the PicoBSD-specific sources,
- it makes PicoBSD very fragile and easy to crash.
-
Some people are already working on it, so expect the fixed version
- in a few days. Its availability will be noted here, on this page,
- so keep an eye on it.
-
--
- 1998.08.27: PicoBSD source tree is now a part of official FreeBSD
- source tree (you can find it in src/release/picobsd). From now on,
- all the fixes and changes will go directly to this tree, and from
- time to time I'll be preparing a stand-alone snapshot of the sources.
-
--
- 1998.08.19: PicoBSD 0.4 released.
-
New features include: NATd,
- netstat, DEVFS/SLICE instead of standard /dev, additional network
- drivers, and several minor fixes. Distribution contains also
- a collection of small versions of system programs (TinyWare), among
- them custom init(8).
- I added also the fourth type of setup - 'router' - which is a
- specialized version of PicoBSD that focuses on providing as small
- as possible router solution.
-
-
-PicoBSD 0.31
-
--
- 1998.03.28: Some people reported that the binary files (*.flp) were
- being corrupted during download because their browsers assumed that
- these are text files. I changed the names to *.bin - their contents
- is the same.
-
--
- 1998.03.20: PicoBSD 0.31 released. New features include: SNMP daemon,
- better creation of /kernel.config, some other minor fixes. Massive
- changes in the building scripts. I also removed vn(4) driver from
- "net" and "isp" floppies.
-
-
-PicoBSD 0.3
-The following bugs were found in this release of PicoBSD:
-
-- 1998.02.27: A bug in kget(8) utility caused it to dump core in certain
- situations. As a consequence, it wasn't possible to save the changes
- made in UserConfig (-c). This will be corrected in the next release (or
- bugfix issue).
-
-- 1998.02.24: Wrongly sized MFS caused the passwd(1) on "net" type
- floppy to fail because of lack of space for temporary files. This bug
- affected only "net" floppies, and of course the scripts ("2000" looks
- quite similar to "2200" :-(( ). Also, the 'update' script didn't work
- as expected...
-
This was fixed the same day, and the corrected files are: pb03en1.zip,
- pb03pn1.zip, and pbsd-s031.tgz respectively. They are now under standard
- links on the main page of PicoBSD project, so if you downloaded after
- this date, you shouldn't worry.
- Please check that you have the fixed versions - the archive name should
- contain the tiny number, such as "pb03en1.zip", or
- pbsd-s031.tgz".
- -
- 1998.02.15: PicoBSD 0.3 released. This is the first version that I can
- truly recommend - previous one was too buggy... :-)
-
-
-
-
-Last modified:
-@DATE@
-
-
-
-Any comments? Send them to
-the author
-
-
-
diff --git a/release/picobsd/doc/src/faq.html b/release/picobsd/doc/src/faq.html
deleted file mode 100644
index 4a0d34e98cc..00000000000
--- a/release/picobsd/doc/src/faq.html
+++ /dev/null
@@ -1,243 +0,0 @@
-
-
-
-
-
-
-
-
- PicoBSD FAQ
-
-
-
-
-
-The PicoBSD FAQ
-
-
-
-
-What is PicoBSD ?
-
-PicoBSD is a floppy sized version of popular operating system FreeBSD.
-It fits within a single bootable 1.44MB floppy and runs on a minimum i386
-with 8MB RAM. PicoBSD currently comes in four flavours: dialup, net, router and
-isp. For a description of how each of the flavours differ, take a look
-at the PicoBSD
-home page.
-
-
What is this "pico" in the name?
-
-It's an SI measure unit, which is equivalent of 10e-12.
-This is a good approximation of more colloquial "extremely small".
-
-You can also think of normal FreeBSD as a system infested with
-fully grown daemons, and PicoBSD as a system infested with
-"the little people" :-).
-
-What version of FreeBSD is PicoBSD based on ?
-
-PicoBSD has versions based on FreeBSD 3.2-RELEASE, 4.0-current and
-FreeBSD 2.2.5-RELEASE.
-Andrzej Bialecki maintains the FreeBSD
-3.x-RELEASE and -current versions and
-Dinesh Nair
-maintains the FreeBSD
-2.2.5-RELEASE version. Both the versions are different:
-
--
-the 3.x-RELEASE version is the one actively maintained, and provides support
-for many new devices
-
--
-the 2.2.5-RELEASE version is not maintained anymore - the only difference is
-that it has lynx on board.
-
-
-What is current version of PicoBSD?
-
-Current version of PicoBSD is @VER@.
-
-What can PicoBSD do?
-
-With the TCP/IP capabilities of FreeBSD included in and based on the
-strong 4.4BSD TCP/IP stack, PicoBSD can be used as a low cost Network Computer.
-With a text based HTML 3.2 compliant browser (2.2.5-RELEASE version only)
-and Internet access tools such as telnet and ftp, it can serve as a low
-cost Internet dialup client. With support for mounting MSDOS and Unix harddisks,
-it also can be used as a portable OS which you can carry around in a floppy.
-The net and isp flavours would allow you to make use of those redundant
-i386es as a low cost router or dialin PPP server. With SNMP and firewall
-support built-in, PicoBSD provides the functionality of dedicated routers
-and dialin terminal servers.
-
-
What are PicoBSD's minimum requirements?
-
-PicoBSD runs on a minimum i386 with 8MB RAM for the dialup flavour and
-10MB RAM for the net and isp flavours. Diskspace requirements are a single
-1.44MB floppy. For on-demand PPP access, a modem would be required, either
-external or internal.
-For LAN access, an Ethernet NIC (support for 3Com, NE2000 etc available)
-would also be required.
-
In case of "router" flavor, its requirements are even smaller: it can
-run in as low as 4MB of RAM, on a 386SX CPU.
-
-Where do I get PicoBSD?
- PicoBSD is available at the following
-locations:
-
-Additional mirror sites will be brought online as demand increases. If
-you're interested in mirroring the PicoBSD distribution, please get in
-touch with Dinesh Nair or
-Andrzej Bialecki.
-
-How do I copy it to the floppy?
-
-The binary images provided as part of the PicoBSD distribution are 1.44MB
-sized floppy images. They cannot be copied to a floppy using the MSDOS
-COPY or Unix cp commands. Instead, an image copy must be done
-using tools such as rawrite.exe
-or fdimage.exe
-under MSDOS and dd under Unix.
-
-
Under DOS you would do something like this:
-
C:\> fdimage.exe picobsd.flp a:
-
-while under Unix you would use something like:
-dd if=picobsd.flp of=/dev/rfd0
-
-How do I configure dialup PPP access on the Dialup flavour?
-
-There is an auto-configuration script to configure PPP dialup access.
-Run /stand/dialup after booting up from the floppy and make the
-relevant menu selections. Once you've tested it to work, you should make
-your changes permanent by committing them to the floppy using /stand/update.
-
-
How do I set my DNS server ?
-
-Use the provided /stand/ee editor and edit /etc/resolv.conf.
-Replace the domain with your domain and change the nameserver
-IP address to your nameserver or your ISP's nameserver. You may have as
-many nameserver lines as you want. Don't forget to run /stand/update
-to commit your changes to the floppy.
-
NOTE: starting with version 0.4, the dialup script asks you to
-set your nameserver as well as default domain name.
-
-I can't execute the /stand/update on the "router" floppy.
-The "router" floppy doesn't contain any real shell, so some commands work
-differently (and some don't work at all). In order to use this script you
-have to 'source it in', i.e.:
-
- (48)/# pwd
- /
- (48)/# . /stand/update
-
-
-How do I set my hostname ?
-
-Edit /etc/rc.conf and change the value of the hostname
-variable.
-
-
PicoBSD has "mkdir" but not "rmdir". How can I delete
-subsdirectories?
-"rm -d" will delete directories.
-
-Can I use a modem configured on COM3/COM4 instead of COM1, COM2?
-
-Yes, but these ports are initially disabled - most machines have only
-two serial ports anyway. You have to enable them in UserConfig.
-Here are the preferred settings:
-
-- sio0=COM1: port 0x3f8, irq 4, used by default for mouse (/dev/cuaa0)
-
-- sio1=COM2: port 0x2f8, irq 3, used by default for modem (/dev/cuaa1)
-
-- sio2=COM3: port 0x3e8, irq 5, disabled by default
-
-- sio3=COM4: port 0x2e8, irq 10, disabled by default
-
-
-
-I see a configuration conflict the first time I boot PicoBSD. What
-should I do?
-
-Disable those devices which are not present in your machine. If there is
-still some conflict, change the settings (I/O port, IRQ etc.).
-
-Exception: if you're using a PS/2 mouse, the visual configuration
-tool will display CONF for sc0 and psm0. The default settings are correct,
-and you should simply ignore the warning.
-
-What kind of SCSI support is there?
-
-None. Either build your own version of PicoBSD, or just install normal
-FreeBSD distribution.
-
-Using version 0.4 I get many strange messages on my console...
-This is related in large part to DEVFS subsystem - it is still somewhat
-experimental, and its author left some diagnostics turned on.. They are
-harmless. Versions 0.4x, x>0 don't use DEVFS at all, as it was too
-experimental to work reliably...
-
-How do I connect using PPP ?
-
-Just run the PPP process, /stand/ppp. at the ppp on pico>
-prompt, type dial and sit back and wait for the modem to sing it's
-mating tunes. When the ppp on pico> prompt is capitalized to PPP
-on pico>, you've managed to succesfully achieve a link-level PPP and
-TCP/IP connection with your ISP. Additionally, the PPP program will enter
-Packet Mode. Remember, don't quit or close the PPP
-connection if you want to continue to access the Internet. Type help
-at the ppp on pico> prompt for a list of PPP commands.
-
-
The PPP process is running on my screen. How do I use the browser
-or telnet to a host ?
-
-PicoBSD has many virtual terminals, 10 on the dialup flavour. You have
-run PPP on the first virtual terminal. You can switch to the others and
-run the browser and telnet clients there. Switching thru the VTs is done
-by ALT-F1 for VT0, ALT-F2 for VT1, ALT-F3 for VT2 etc. From these terminals,
-you could use telnet or the lynx browser cum newsreader.
-
-
I can't establish a PPP connection. The mouse pointer randomly appears
-and disappears. and moving the mouse has no effect.
-
-You have the mouse driver configured to use the modem's serial port.
-Issue a 'ps -ax', remember the pid (process ID) of 'moused', then issue a
-'kill -9 '. Edit /etc/rc.conf to specify the correct mouse port. Issue
-an 'update' commmand to save new configuration to the floppy, and reboot.
-
-I saved my lynx configuration but it was not there when I rebooted.
-Why ?
-
-
The lynx configuration is saved in /etc/lynx.cfg. You should
-run /stand/update to commit this to the floppy when you change the
-configuration. In effect, anything you change in /etc can be committed
-by running /stand/update.
-
-
How come there are no manual pages ?
-
-Well, this is a floppy-sized OS, so there's not enough space for full
-manpages. Instead, short help descriptions are given with the /stand/help
-program. If you need more detailed descriptions, take a look at the FreeBSD
-Handbook or the FreeBSD Home.
-
-
-
-More FAQ points will be added as feedback from the
-PicoBSD user community comes in. And big thanks to all of you who already
-sent us some suggestions!
-Last Modified:
-@DATE@
-
-
-
diff --git a/release/picobsd/doc/src/hardware.html b/release/picobsd/doc/src/hardware.html
deleted file mode 100644
index 0afede238cf..00000000000
--- a/release/picobsd/doc/src/hardware.html
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
-
-Lists of supported hardware configurations.
-
-Below you will find supported configurations for each of the flavors of
-PicoBSD as of version @VER@, as well as the lists of programs included.
-
-Dialup version:
-
-- minimum 386SX CPU (either Intel, AMD, Cyrix etc - doesn't matter),
-
-- minimum 8MB of RAM (some people reported success
-stories with 4MB only, but I certainly don't recommend it)
-
-- a modem (for Internet connection using PPP protocol), either internal or
-external, connected to COM1-COM4. NOTE: COM3 and COM4 are disabled by default
-- you have to explicitly enable them in UserConfig.
-
-- an Ethernet card for LAN connection:
-
-- ed - default settings: port 0x280, irq 10, iomem 0xd8000
-
NE2000 compatible ISA and PCI cards, most SMC and 3C503
-
-- ep - default settings: port 0x300, irq 10,
-
3C509 ISA card
-
-- ie - default settings: port 0x300, irq 10, iomem 0xd0000
-
Intel EtherExpress ISA, StarLan, 3C507
-
-- le - default settings: port 0x300, irq 5, iomem 0xd0000
-
DEC EtherWorks 2 and 3
-
-- lnc - default settings: port 0x280, irq 10, iomem 0xd0000
-
Lance/PCNet
-
-- de - DEC21040-based PCI cards,
-
-- fxp - Intel EtherExpress Pro/100B PCI card
-
-
-
-- 10 virtual consoles plus console utilities (vidcontrol, kbdcontrol)
-
-- basic networking tools: ifconfig, route, ping, ns (mini-netstat),
-traceroute
-
-- basic remote access tools: telnet, ftp and SSH
-
-- basic OS tools: shell, mount (FreeBSD, DOS, Linux), umount, ps, kill, vm
-(mini-vmstat), fsck, df, etc..
-
-- editable configuration (/etc directory and kernel configuration)
-
-- simple editor ee
-
-- simple help system for people new to FreeBSD
-
-
-Router-like version:
-
-- minimum 386SX CPU,
-
-- minimum 10 MB of RAM (8MB for basic setup)
-
-- support for PPP protocol on dialup/leased lines (using ijppp)
-
-- support for several types of Ethernet cards (two of each kind) - see above
-for descriptions: ed, ie, ep, de, fxp, lnc
-
-- network daemons: routing daemon (routed), inetd, telnetd.
-
-- IP Firewall and NAT daemon (natd).
-
-- more OS utilities, including: syslogd, mount_nfs, network logins via
-telnet
-
-- this version doesn't include: ssh, ftp
-
-
-Router version:
-
-- minimum 386SX CPU,
-
-- minimum 4 MB of RAM (6MB for running some additional daemons)
-
-- support for PPP protocol on dialup/leased lines (using kernel ppp)
-
-- support for several types of Ethernet cards - see above
-for descriptions: ed, ie, ep, de, fxp, lnc
-
-- custom init(8), which includes also a simple command-line interface,
-and its own way to configure the system on startup.
-
-- IP Firewall and NAT daemon (natd - it requires additional portion of RAM).
-
-- very few OS tools, except those absolutely necessary,
-
-
-
-There's also the fourth version, which can serve as a dialin server - I hope
-you'll find it as a cheap yet reliable alternative to commercial communication
-servers :-)) This work is still in progress, and
-I need some people to test the early
-dial-in server version.
-
-
-Last modified:
-@DATE@
-
-
-
diff --git a/release/picobsd/doc/src/how2build.html b/release/picobsd/doc/src/how2build.html
deleted file mode 100644
index 12303be1882..00000000000
--- a/release/picobsd/doc/src/how2build.html
+++ /dev/null
@@ -1,197 +0,0 @@
-
-
-
-PicoBSD Development Kit
-
-
- How to build your own version
- of PicoBSD?
-
-
-
--
-
Beginning with version 0.4, PicoBSD sources are maintained as
- part of official FreeBSD CVS repository, so
- you can find them in src/release/picobsd.
-
--
- Become root. You'll need to mount and unmount various volumes.
-
--
- Make sure you are running kernel with support for md(4) devices.
- If you run plain GENERIC (just as it was installed on your system),
- you'll need to recompile you kernel and reinstall it. See the
- appropriate entries in The Handbook (/usr/share/doc/handbook).
-
-- Change working directory (
cd build) and run the
- ./picobsd script. Select target language, size of MFS and
- one of pre-canned setups (personal dialup, dialin server or
- router-like). Details of each setup are contained in dial/,
- router/, isp/ and net/ directories respectively. You should at least
- check ${TYPE}/config/PICOBSD file to make sure it contains
- the drivers you want.
-
- You can also choose a special type called 'custom'. You'll need to
- supply the full path to your own custom config tree constructed
- exactly like one of the standard config directories. Also, you'll
- probably want to adjust the number of inodes on MFS - see the
- stage1 script and look for INODES=.
-
- I also recommend to adjust the ISA devices parameters to
- match the ones of your hardware - though PicoBSD can save the
- changes from UserConfig, this way it will produce smaller
- /kernel.config file.
-
-- I assume you will use 1.44MB floppy. If not, please edit the file
-
build/stage3.
-
-- There are several directories which contain some sources and config
- files:
-
- build/ main build directory; you MUST cd here!
- dial/ config files for dialup setup
- conf/ kernel config file
- crunch1/ crunch of system programs
- mfs.tree/ contains the MFS configuration
- lang/ contains language-dependent files
- floppy.tree/ contains the startup floppy hierarchy
-
- isp/ config files for dialin server setup
- ... (as above)
- net/ config files for router-like setup
- ... (as above)
- tinyware/ collection of small system utilities
- tools/ additional tools them needed during build
-
- There are no /etc/passwd nor /etc/pwd.db
- files on the "dial" floppy - in case of other types, they are
- reconstructed from /etc/master.passwd on each startup
- (and then put on MFS with the rest of /etc).
- In case of "dial" type floppy, you don't need them at all.
-
- NOTE: thanks to the above, the floppy is needed only during startup,
- and then only if you want to synchronize (possibly changed) MFS /etc
- with the one on the floppy. It means that you can pull off the floppy
- from the drive as soon as login: prompt appears.
- In other words, it is almost equal to read-only floppy.
-
-- Edit the set of installed programs.
-
-- Go to
${TYPE}/crunch1 directory, and edit it
- to suit your needs. Keep in mind that floppies aren't made
- of rubber... :-)
-
-- There are some patches included in these directories, which
- are applied during build process to some of the Makefiles in
- your
/usr/src. These patches attempt to decrease
- the size of some programs by cutting off rarely/unlikely used
- parts. The patches are reversed when you do a
- make clean (or build/clean
- for that matter).
- NOTE: patches may fail to apply, if your sources are too
- different from the ones I used. Don't worry: they are so
- straightforward that you can apply them by hand.
-
-- In order to have a functioning system you MUST include at
- least
/stand/init, or /stand/oinit,
- or /stand/sysinstall in
- your crunch.conf. Of course these can be your
- own programs... But if you install the stock
- /sbin/init, you
- also have to install some others, like sh, getty, login etc...
- This release of PicoBSD contains a small replacement for
- init(8), called 'oinit'. You can find it in TinyWare
- collection. The main building script allows you to use it
- instead of normal init(8). Be sure to read the oinit's docs
- before you decide to use it!
-
-
-
-- Make sure that the system you're running has /dev/md0* entries in
- /dev directory (if not, and you dont have DEVFS running, you can
- make them with 'MAKEDEV md0'), AND
- that your running kernel has built-in memory file device (there
- should be a line in your kernel config file stating 'device md').
-
-- You'll need at least 9MB of free disk space, and free /mnt directory.
-
-- Do a
cd build/ and fire off the ./picobsd
- script. Select the build parameters or 'n' for 'no change'. If all
- is well, after some time (like 10-30m) you end up with a
- 'picobsd.bin' file in this directory.
-
- WARNING: make sure you don't have stale .depend files
- around!!! You may encounter many strange errors during build process
- in that case.
-
- If there were any errors, please execute each script by hand and try
- to find what causes this error. Most often this will be one of the
- following reasons:
-
--
crunchgen can't find the source directory for a
- program 'proggy':
-
-- make sure that the source directory for 'proggy' is called
- 'proggy', otherwise the crunchgen won't find it
-
-- make sure that the Makefile allows crunchgen to deduce the
- set of objects to build. You can manually add an OBJS= ...
- to the program's Makefile.
-
-
-
-- crunch fails to build.
-
-- check your system source tree for stale .depend files and/or
- objects (*.o)
-
-- see if the individual programs can be built using original
- Makefiles. If not, cvsup the correct sources.
-
-
-
-- /: write failed - file system is full
-
-- this one is obvious - you wanted to put too many programs on
- the MFS and/or the target floppy. Or, you really don't have
- any space left on the root partition.. :-)
-
-- also, you can check if the
- MFS size is correctly reported while it's still mounted (right
- after
stage1 script ends).
-
-
- - the build process displays "Preparing MFS" and then
- silently stops. In this case check if you're running it as
- root, and that you run kernel with support for md(4)
- devices. Also, you can add 'set -x' at hte beginning
- of the scripts to see exactly where they stop.
-
-
-
- You can also remove 2>&1 redirections from Makefiles
- to see the stderr.
-
-- Transfer this file to the floppy:
-
- dd if=picobsd.bin of=/dev/rfd0
-
-
- (The 'build' script asks you if you want to do this.)
-
-
-
-That's all. You're welcome to change and improve these scripts. If you
- stumble upon something which looks like a good idea to have it here, let me
- know.
-
-If, for some reason, the scripts don't work for you at all, also let me
- know.
-
-
-Last modified:
-@DATE@
-
-<abial@freebsd.org>
-
-
diff --git a/release/picobsd/doc/src/installflp.html b/release/picobsd/doc/src/installflp.html
deleted file mode 100644
index b0ead20390b..00000000000
--- a/release/picobsd/doc/src/installflp.html
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-
-
- Configuring the PicoBSD install floppy
-
-
-
- Configuring the PicoBSD install floppy
-
- The PicoBSD Install Floppy is engineered to be flexible since every
- site has their own needs for an automated install solution. The
- base package contains tools and frameworks for further
- customization.
-
- Generating an Install Image
-
- Central to the design of the install floppy is a tarball image of
- the operating system. The install floppy downloads and extracts
- the image from a master server.
-
- To generate the install image:
-
-
- - Install and configure a machine as it should be
- installed.
-
- - Make the template machine as close to the target
- machines as possible. System-specific files such as
- /etc/fstab can cause problems if they are
- specific to a particular disk setup, such as multiple SCSI
- disks in the template vs. single IDE disks in the target.
-
- Try to keep the template as small as practical.
- The more packages you install on the template, the larger
- the image becomes.
-
- - Use tar to create the image. This shell script is useful
- for automating the process.
-
-#!/bin/sh
-TARBALL="/fbsdimage.tgz"
-GZIP="-9"
-
-tar -cpvzf ${TARBALL} --totals --exclude '/proc/*' --exclude '/var/tmp/*' \
- --exclude '/var/log/*' --exclude '/tmp/*' --exclude '/fbsdimage.tgz' /
-
-
- - Use the '--exclude' argument to remove files from the
- image.
-
- Don't forget to exclude the image itself or your tarball
- will be much larger than it should.
-
- The GZIP environment variable sets arguments to the
- gzip command called by tar's z option.
-
- - Copy the image file to your load server into a public FTP
- directory.
-
-
- Configuring the Install Floppy
-
- Once the install floppy has been built using the PicoBSD build
- script, mount the floppy and modify the install
- script, /floppy/etc/doinstall. doinstall is
- called from rc on startup to install the disk image and perform
- whatever other setup tasks are necessary. The script can set
- network parameters, configure applications, select kernels, or
- whatever else a shell script can do. A handful of useful
- utilities is included on the disk to ease automated installation.
-
- At minumum, set the URL to the FTP server holding the disk
- image. If you wish, uncomment and modify to taste any of the
- code blocks provided.
-
- By default, the install floppy:
-
- - Creates one large FreeBSD slice on the first IDE disk (wd0).
-
- Creates a 256MB swap partition and the rest for a large
- root partition.
-
- Formats the large partition using newfs with
- default parameters. '
-
- Downloads the image via FTP and feeds it directly into
- cpio for extraction.
-
-
- To modify the disk formatting parameters, modify the
- /floppy/etc/prepdisk script. prepdisk is a
- simple awk script that feeds directly into disklabel.
- Simply edit the generated partition table to taste.
-
-
-
-
- Doug White
-
-
-Last modified: Thu Oct 7 22:18:22 PDT 1999
-
-
-
diff --git a/release/picobsd/doc/src/intrinsics.html b/release/picobsd/doc/src/intrinsics.html
deleted file mode 100644
index f8ff478f981..00000000000
--- a/release/picobsd/doc/src/intrinsics.html
+++ /dev/null
@@ -1,122 +0,0 @@
-
-
-
-Details of building process
-
-
- Details of building process.
-
-For those of you who really want to know what's going on behind the scene,
-and can't quite deduce it from scripts themselves, here's short description of
-the build process:
-
-
-- The './build' script sets the basic parameters of the floppy, such as:
-
-- LANGUAGE: language of the various system messages, and C locale.
- Available choices are: "en" (English) and "pl" (Polish).
-
--
- SIZE: size of the memory filesystem (MFS), which will contain all the
- binaries (except the kernel). Make it big enough for all the pieces to
- fit, but keep it as small as possible (remember that running system
- needs some space in /var and /tmp!). Presently, "dial" type of floppy
- requires at least SIZE=1700, and others require ca. 2800 (numbers
- are in kB).
-
--
- TYPE: determines which set of programs and which trees will be
- installed on the floppies. This simply acts as a selector to dive into
- respective subdirectories in ../. Presently, the TYPE can be one of:
- "dial" (dialup floppy), "net" (networking floppy), "router" (router
- floppy) or "isp" (work in progress - not really usable yet).
-
-
- -
- Then the './build' scripts checks if there is a kernel built on basis
- of previously set parameters. The check is error prone, but is simple:
- the target config file is called PICOBSD-${TYPE}.${SIZE}, and if there
- exists a file called /sys/compile/PICOBSD-${TYPE}.${SIZE}/kernel, then
- it is assumed it's the right one.
-
-
If there is no such file, the script starts compilation of the kernel,
- using template in ../${YTPE}/conf/PICOBSD, and adding parameters which
- determine the built-in MFS size.
- -
- Then the './build' script starts the consecutive stages of the build
- process, which are performed by scripts (in the following order):
- stage1, populate, stage2, stage3.
-
--
- 'stage1' prepares the file called fs.PICOBSD with given size - it's a
- placeholder for the future MFS. Next, it turns it into device,
- and then performs some tricks which allow for doing 'disklabel'.
- I use the 'auto' option to disklabel(8).
-
-
One notable exception here is with the "router" floppy - I use one
- of extended floppy formats (820kB).
-
- After the file is labelled, the newfs(8) is run. Here you can adjust
- the parameter -i, which can gain you some space on the MFS (sacrificing
- available number of inodes, so be careful).
-
- Such prepared blank filesystem is mounted on /mnt. Here the stage1
- ends.
-
--
- 'populate', as its name suggests, transfers all the pieces which will
- reside in MFS, to the filesystem mounted on /mnt. This includes:
-
-- copying language dependent files from ../${TYPE}/lang/
-- making the MFS hierarchy according to informations in
- ../${TYPE}/mfs.tree/ subdir.
-
The MFS tree includes the /etc, which will contain the startup file
- /etc/rc.
- This file in turn doesn't do anything useful except copying the
- real /etc hierarchy from the floppy filesystem. (There's one possible
- improvement which comes to my mind - to have the whole /etc on the
- floppy in tar.gz - this would require only one inode to store the whole
- /etc, and we could gain some kB on the floppy)
-
-- making and installing the set of crunched programs, basing on the
- description in ../${TYPE}/crunch1/crunch.conf. This involves
- making the 'crunch', copying it to /mnt and making hard links to
- the names of all the programs contained therein.
-- preparing a short list of kernel symbols, which will be used by
- various utilities at runtime. In case of "net" and "isp" floppy, it also
- prepares the kvm_kernel.db database, which will be used by such
- programs as ps, netstat and others
-- preparing the list of "virgin" configuration of devices in kernel -
- this list will be used by kget(8) program to save the changes to
- /kernel.config file.
-
-
--
- 'stage2' prepares the target kernel. It takes the filesystem contained
- in fs.PICOBSD (which has all the above pieces inside), and writes it
- into the target kernel. Then it kzip(8)'s such construed kernel. This
- process also strips the symbols from the kernel (that's why we prepared
- the symbol list earlier).
-
--
- 'stage3' does almost the same as 'stage1', but this time it prepares
- the filesystem of the target floppy. Default size for the floppy is
- set at 1440kB.
-
After preparing the filesystem (which again involves doing disklabel(8)
- and newfs(8) - here you can notice that the resulting FS has very small
- number of inodes in order to save space), the script transfers the
- floppy hierarchy (which is
- taken from ../${TYPE}/floppy.tree). Notice that it also contains
- the /etc directory - its contents is copied right after bootup to the
- real /etc in MFS. This allows for changing the system behaviour
- (because you can't change the MFS contents without recompiling).
- The script finally copies previously prepared kernel to the floppy
- filesystem. The filesystem is unmounted, and here the build process
- ends.
-
-
-
-
-Last modified:
-@DATE@
-
diff --git a/release/picobsd/doc/src/intro.html b/release/picobsd/doc/src/intro.html
deleted file mode 100644
index f1156976ef8..00000000000
--- a/release/picobsd/doc/src/intro.html
+++ /dev/null
@@ -1,303 +0,0 @@
-
-
-
- PicoBSD
-
-
-
-PicoBSD
-
-
-
-Contents:
-
-
-
-
-
-What is it?
-If you ever dreamed about having really small, tiny, minimal system that
-would offer you benefits of Unix, while still fitting in reasonable space -
-here it is!
-
-PicoBSD is a one floppy version of
-FreeBSD, which in its
-different variations allows you to have secure dialup access, small diskless
-router or even a dial-in server. And all this on only one standard 1.44MB
-floppy - no need to sacrifice over 100MB of your precious HDD space.
-
-PicoBSD is... well, pico-sized :-) , and the minimal hardware that
-is required to run it is 386SX CPU with 8MB of RAM (no HDD!).
-
-
-
-Here you can find detailed list of supported
-hardware and features.
-
-
Current version of PicoBSD is @VER@, and this means that I consider it
-still immature, while on the other hand being somewhat tested and improved
-over previous versions. Does it tell you something? Well, at least you can
-try it - I cannot guarantee that it doesn't burn your house or blow up your
-machine, though the former is unlikely... :-)
-
-
-Where can I get it?
-
-There are two language editions of PicoBSD - English and Polish one. You'll
-be probably more interested in the former :-) The only difference is in
-the set of fonts included, C locale, and the language of messages.
-You can download them from www.freebsd.org or one of its mirrors:
-
-
-(See the feature list for more
-details)
-
-The above floppies were built from FreeBSD sources.
-You can find floppies built from 2.2.5 sources
-here or
-here.
-
-
-How can I use it?
-Previous versions were packed with a PKZIP(tm) compatible program - now they
-are simply the raw binary floppy images, so you just need to grab the
-appropriate version of the file.
-
-I assume you will use 1.44MB floppy to boot the system - other sizes
-(bigger) are not tested.
-
-The file 'pb_xx-X.bin' must be written onto a blank floppy. It does NOT
-mean that it can be copied using e.g. DOS 'copy' command. You must use a
-program like
-rawrite.exe
-or
-fdimage.exe
- to write this file directly on the raw floppy.
-
-Under DOS you would do something like this:
-
- C:\> fdimage.exe pb_xx-X.bin a:
-
-
-while under Unix you would use something like:
-
- dd if=pb_xx-X.bin of=/dev/rfd0
-
-
-Then boot off this floppy and enjoy!
-
-If you feel lost, try the 'help' command (it's available only on "dialup"
-floppies)
-
-
-
-Create your own, custom version of PicoBSD!
-
-I made available also the set of tools
-(a.k.a the PicoBSD Development Kit) I used to create the floppies (see also the
- detailed instructions)
-
-You can also access the full CVS repository of PicoBSD - beginning with
-version 0.4 it's a part of official FreeBSD CVS and lives in
-src/release/picobsd. 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
-here.
-
- Now, if you don't like the setup of PicoBSD, or you miss
-some program, or (better yet) you want to improve PicoBSD - you can grab the
-copy of exactly the same tools I used and build your own, customized
- version!
-
-Think of it: if your're an ISP, you can build the dialup version for
- your customers, including some scripts to automatically connect them to
-your site. You can also create a demo disk for your friend (or your boss! :-)).
-You can also build a firewall/router for your office, etc, etc...
- possibilities are really endless and limited only by your imagination.
-
-You will need at least 10MB of free disk space for building, and of course
-the full system sources installed. I also assume that the sources are
-quite -current. There is also a back-ported version of the scripts prepared by
-Dinesh Nair which builds ok on
-2.2.6-R systems.
-
-Version 0.31 was packed with pax(1) - newer versions are packed again
-with tar and gzip to avoid confusion... :-)
-
-I'm very interested in hearing from you about your experiences - if you
-come up with a setup you think is interesting, please let me know!
-
-
-Where can I get more info?
-
-Almost all of the programs included on the floppies are exactly the
-same versions as in normal FreeBSD installation, so that the normal
-manual pages apply. However, I didn't include the manpages themselves -
-they would take over 200kB!
-
- For the total newbies, which would use (I assume)
-the 'dialup' version, there is a short README on the floppy which gives
-step by step instructions on how to get a dialup connection. There is also
-a script called 'dialup' which attempts to configure PPP to allow for automatic
-log in to your provider, and for background operation.
-There is also a small help system ('help' command)
-
- There are some system utilities which are unique to PicoBSD, and at this
- moment they are documented in detail only in source and READMEs :-(.
-
-
-As for the new releases which will (hopefully) be prepared in the future:
-just keep an eye on this page. I'll also send announcements to FreeBSD mailing
-lists.
-
-
-Plans for the future
-
-Well, I hope that thanks to your comments I'll be able to continuously
-improve the setup and contents of PicoBSD. I also have specific dreams (if
-dreams can be specific..) - here they are, as an incentive to your
-imagination and coding skills:
-
-
-Credits
-
-The following people are either responsible for the very existence of this
-project, or significantly eased my pains in gaining necessary knowledge:
-
--
-the whole FreeBSD team for this magnificent OS, and their hard work of
-continuous development,
-
--
-Dinesh Nair, for co-development and preparing of the version which compiled
-on 2.2.5-RELEASE,
-
--
-Joe Greco, for his encouraging example of XKERNEL (some parts of the scripts
-still bear his fingerprints :-) (you can get it
- here).
-
-- Goran Hasse of Raditex AB, Sweden, for
-sending me M-Systems' and SanDisk flash disks to experiment with.
-
--
-Mike Smith for various tips and encouragement.
-
--
-freebsd-* mailing lists participants, which helped me with some other
-pieces.
-
--
-and many other people who keep encouraging me to continue this work. Thanks,
-guys!
-
-
-
-Licensing issues
-
-PicoBSD is distributed under BSD copyright,
-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 contact me.
-
-Last modified:
-@DATE@
-
-
-
-Any comments? Send them to
-the author
-
-
-
diff --git a/release/picobsd/help/README b/release/picobsd/help/README
deleted file mode 100644
index 69babc4612f..00000000000
--- a/release/picobsd/help/README
+++ /dev/null
@@ -1,8 +0,0 @@
-1998.02.20
-
-This is work in progress. Eventually I'll prepare the help system for newbies,
-and these files are just the beginning of it...
-
-
-
-$FreeBSD$
diff --git a/release/picobsd/help/cat.hlp.en b/release/picobsd/help/cat.hlp.en
deleted file mode 100644
index ed14871118f..00000000000
--- a/release/picobsd/help/cat.hlp.en
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mcat[m concatenate and print files
-
- Usage:
-
- cat [-benstuv] [-] [file ...]
diff --git a/release/picobsd/help/cat.hlp.pl b/release/picobsd/help/cat.hlp.pl
deleted file mode 100644
index cb49b995193..00000000000
--- a/release/picobsd/help/cat.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mcat[m polacz lub wyswietl pliki
-
- Sposob uzycia:
-
- cat [-benstuv] [-] [plik ...]
diff --git a/release/picobsd/help/chmod.hlp.en b/release/picobsd/help/chmod.hlp.en
deleted file mode 100644
index 6e516c5eb13..00000000000
--- a/release/picobsd/help/chmod.hlp.en
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mchmod[m change file modes
-
- Usage:
-
- chmod [-R [-H | -L | -P]] mode file ...
diff --git a/release/picobsd/help/chmod.hlp.pl b/release/picobsd/help/chmod.hlp.pl
deleted file mode 100644
index be690196a8a..00000000000
--- a/release/picobsd/help/chmod.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mchmod[m zmiana praw dostepu do pliku
-
- Sposob uzycia:
-
- chmod [-R [-H | -L | -P]] prawa plik ...
diff --git a/release/picobsd/help/chown.hlp.en b/release/picobsd/help/chown.hlp.en
deleted file mode 100644
index e32e855c33c..00000000000
--- a/release/picobsd/help/chown.hlp.en
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mchgrp[m change group
-[1mchown[m change owner
-
- Usage:
-
- chown [-R [-H | -L | -P]] [-f] [-h] owner[:group] file ...
- chown [-R [-H | -L | -P]] [-f] [-h] :group file ...
- chgrp [-R [-H | -L | -P]] [-f] [-h] group file ...
diff --git a/release/picobsd/help/chown.hlp.pl b/release/picobsd/help/chown.hlp.pl
deleted file mode 100644
index 0cdda8b8692..00000000000
--- a/release/picobsd/help/chown.hlp.pl
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mchgrp[m zmien grupe
-[1mchown[m zmien wlasciciela
-
- Sposob uzycia:
-
- chown [-R [-H | -L | -P]] [-f] [-h] wlasc[:grupa] plik ...
- chown [-R [-H | -L | -P]] [-f] [-h] :grupa plik ...
- chgrp [-R [-H | -L | -P]] [-f] [-h] grupa plik ...
diff --git a/release/picobsd/help/cp.hlp.en b/release/picobsd/help/cp.hlp.en
deleted file mode 100644
index 81171591a57..00000000000
--- a/release/picobsd/help/cp.hlp.en
+++ /dev/null
@@ -1,6 +0,0 @@
-[1mcp[m copy files
-
- Usage:
-
- cp [-R [-H | -L | -P]] [-f | -i] [-p] src target
- cp [-R [-H | -L | -P]] [-f | -i] [-p] src1 ... srcN directory
diff --git a/release/picobsd/help/cp.hlp.pl b/release/picobsd/help/cp.hlp.pl
deleted file mode 100644
index 30dea47a95f..00000000000
--- a/release/picobsd/help/cp.hlp.pl
+++ /dev/null
@@ -1,6 +0,0 @@
-[1mcp[m kopiuj pliki
-
- Sposob uzycia:
-
- cp [-R [-H | -L | -P]] [-f | -i] [-p] plik1 plik2
- cp [-R [-H | -L | -P]] [-f | -i] [-p] plik1 ... plikN katalog
diff --git a/release/picobsd/help/df.hlp.en b/release/picobsd/help/df.hlp.en
deleted file mode 100644
index 987849b52ae..00000000000
--- a/release/picobsd/help/df.hlp.en
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mdf[m display free disk space
-
- Usage:
-
- df [-ikn] [-t type] [file | filesystem ...]
diff --git a/release/picobsd/help/df.hlp.pl b/release/picobsd/help/df.hlp.pl
deleted file mode 100644
index 39fda444a3d..00000000000
--- a/release/picobsd/help/df.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mdf[m pokaz ilosc wolnego miejsca na dysku
-
- Sposob uzycia:
-
- df [-ikn] [-t typ] [plik | filesystem ...]
diff --git a/release/picobsd/help/dialup.hlp.en b/release/picobsd/help/dialup.hlp.en
deleted file mode 100644
index c729023a6e8..00000000000
--- a/release/picobsd/help/dialup.hlp.en
+++ /dev/null
@@ -1,4 +0,0 @@
-[1mdialup[m a simple PPP configuration script
-
- This script attempts to create the /etc/ppp/ppp.conf file suitable for
- automatic dialing and background operation of 'ppp' program.
diff --git a/release/picobsd/help/dialup.hlp.pl b/release/picobsd/help/dialup.hlp.pl
deleted file mode 100644
index a19c8d911c8..00000000000
--- a/release/picobsd/help/dialup.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mdialup[m prosty skrypt konfiguracyjny do PPP
-
- Skrypt ten tworzy plik /etc/ppp/ppp.conf w oparciu o wartosci
- podane przez uzytkownika, umozliwiajac automatyczne wybieranie
- numeru oraz dzialanie w tle.
diff --git a/release/picobsd/help/dmesg.hlp.en b/release/picobsd/help/dmesg.hlp.en
deleted file mode 100644
index b55e690b2b5..00000000000
--- a/release/picobsd/help/dmesg.hlp.en
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mdmesg[m display kernel message buffer contents
-
- Usage:
-
- dmesg | more
diff --git a/release/picobsd/help/dmesg.hlp.pl b/release/picobsd/help/dmesg.hlp.pl
deleted file mode 100644
index 544c6ca49da..00000000000
--- a/release/picobsd/help/dmesg.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mdmesg[m wyświetl zawartość bufora komunikatów
-
- Sposób użycia:
-
- dmesg | more
diff --git a/release/picobsd/help/echo.hlp.en b/release/picobsd/help/echo.hlp.en
deleted file mode 100644
index b54bdc3a736..00000000000
--- a/release/picobsd/help/echo.hlp.en
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mecho[m write arguments to the standard output
-
- Usage:
-
- echo [-n] [string...]
-
- Optional parameter -n tells echo not to end the output with new
- line character.
diff --git a/release/picobsd/help/echo.hlp.pl b/release/picobsd/help/echo.hlp.pl
deleted file mode 100644
index e268038a555..00000000000
--- a/release/picobsd/help/echo.hlp.pl
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mecho[m wypisz argumenty na standardowym wyjsciu (stdout)
-
- Sposob uzycia:
-
- echo [-n] [argumenty...]
-
- Opcjonalny parametr -n powoduje, ze nie zostanie dodany znak
- konca wiersza.
diff --git a/release/picobsd/help/ee.hlp.en b/release/picobsd/help/ee.hlp.en
deleted file mode 100644
index dfb66c09fa1..00000000000
--- a/release/picobsd/help/ee.hlp.en
+++ /dev/null
@@ -1,4 +0,0 @@
-[1mee[m Easy Editor
-
- This simple editor comes with its own help, visible in the upper part
- of the screen. Follow that instructions.
diff --git a/release/picobsd/help/ee.hlp.pl b/release/picobsd/help/ee.hlp.pl
deleted file mode 100644
index e0582195af0..00000000000
--- a/release/picobsd/help/ee.hlp.pl
+++ /dev/null
@@ -1,4 +0,0 @@
-[1mee[m Easy Editor
-
- Ten prosty edytor wyposazony jest w swoj wlasny system pomocy,
- umieszczony w gornej czesci ekranu.
diff --git a/release/picobsd/help/fsck.hlp.en b/release/picobsd/help/fsck.hlp.en
deleted file mode 100644
index e4c13e35a57..00000000000
--- a/release/picobsd/help/fsck.hlp.en
+++ /dev/null
@@ -1,15 +0,0 @@
-[1mfsck[m filesystem consistency check and interactive repair
-
- Usage:
-
- fsck -p [-f] [-m mode]
- fsck [-b block#] [-c level] [-l maxparallel] [-y] [-n] [-m mode]
- [filesystem] ...
-
- but in its simplest and most common version:
-
- fsck -y
-
- where is a name of the raw device, on which the filesystem
- lies, e.g. /dev/rfd0 for floppy A:, or /dev/rwd0s1 for partition #1 on
- first IDE drive.
diff --git a/release/picobsd/help/fsck.hlp.pl b/release/picobsd/help/fsck.hlp.pl
deleted file mode 100644
index 5f4b74889bb..00000000000
--- a/release/picobsd/help/fsck.hlp.pl
+++ /dev/null
@@ -1,15 +0,0 @@
-[1mfsck[m narzedzie do sprawdzania poprawnosci i spojnosci filesystemu.
-
- Sposob uzycia:
-
- fsck -p [-f] [-m mode]
- fsck [-b block#] [-c level] [-l maxparallel] [-y] [-n] [-m mode]
- [filesystem] ...
-
- ...ale w najprostszej i najczesciej spotykanej formie:
-
- fsck -y
-
- gdzie jest nazwa "surowego" urzadzenia, na ktorym
- znajduje sie system plikow, np. /dev/rfd0 dla dyskietki A:, lub
- /dev/rwd0s1 dla pierwszej partycji pierwszego dysku IDE.
diff --git a/release/picobsd/help/ftp.hlp.en b/release/picobsd/help/ftp.hlp.en
deleted file mode 100644
index 3b61e90378b..00000000000
--- a/release/picobsd/help/ftp.hlp.en
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mftp[m ARPANET file transfer program
-
- Usage:
-
- ftp [-adeginptvV] [host [port]]
- ftp host:path[/]
- ftp ftp://host[:port]/path[/]
- ftp http://host[:port]/file
diff --git a/release/picobsd/help/ftp.hlp.pl b/release/picobsd/help/ftp.hlp.pl
deleted file mode 100644
index 201aa17d694..00000000000
--- a/release/picobsd/help/ftp.hlp.pl
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mftp[m Program do przesylania plikow
-
- Sposob uzycia:
-
- ftp [-adeginptvV] [host [port]]
- ftp host:path[/]
- ftp ftp://host[:port]/path[/]
- ftp http://host[:port]/file
diff --git a/release/picobsd/help/gzip.hlp.en b/release/picobsd/help/gzip.hlp.en
deleted file mode 100644
index f125fe3ad13..00000000000
--- a/release/picobsd/help/gzip.hlp.en
+++ /dev/null
@@ -1,26 +0,0 @@
-[1mgzip, gunzip, zcat[m compress or expand files
-
- Usage:
-
- gzip [-cdfhlLnNrtvV19] [-S suffix] [file ...]
- -c --stdout write on standard output, keep original
- files unchanged
- -d --decompress decompress
- -f --force force overwrite of output file and compress
- links
- -h --help give this help
- -l --list list compressed file contents
- -L --license display software license
- -n --no-name do not save or restore the original name and
- time stamp
- -N --name save or restore the original name and time stamp
- -q --quiet suppress all warnings
- -r --recursive operate recursively on directories
- -S .suf --suffix .suf use suffix .suf on compressed files
- -t --test test compressed file integrity
- -v --verbose verbose mode
- -V --version display version number
- -1 --fast compress faster
- -9 --best compress better
- file... files to (de)compress. If none given, use
- standard input.
diff --git a/release/picobsd/help/gzip.hlp.pl b/release/picobsd/help/gzip.hlp.pl
deleted file mode 100644
index 807a95e6c27..00000000000
--- a/release/picobsd/help/gzip.hlp.pl
+++ /dev/null
@@ -1,12 +0,0 @@
-[1mgzip, gunzip, zcat[m kompresuj lub dekompresuj plik(i)
-
- Sposob uzycia:
-
- gzip [-cdfhlLnNrtvV19] [-S suffix] [file ...]
- -c --stdout dekompresuj na stdout
- -d --decompress dekompresuj
- -l --list pokaz zawartosc
- -t --test testuj poprawnosc archiwum
- -1 --fast szybka kompresja
- -9 --best dobra kompresja
- file... pliki do (de)kompresji.
diff --git a/release/picobsd/help/help.hlp.en b/release/picobsd/help/help.hlp.en
deleted file mode 100644
index b38db3d6c55..00000000000
--- a/release/picobsd/help/help.hlp.en
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mhelp[m Simple help system for PicoBSD
-
- This command displays short description of the commands included
- on PicoBSD floppy. When invoked with no argument, it displays this
- text :-). Any other argument is treated as a name of file located in
- /help.a archive on the floppy, and this file is displayed page by
- page.
diff --git a/release/picobsd/help/help.hlp.pl b/release/picobsd/help/help.hlp.pl
deleted file mode 100644
index 47e039d0c84..00000000000
--- a/release/picobsd/help/help.hlp.pl
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mhelp[m Prosty system pomocy dla PicoBSD
-
- To polecenie wyswietla krotka instrukcje obslugi programow na
- dyskietce. Uruchomione bez zadnego argumentu, wyswietla ten tekst. :-)
- Kazdy inny argument traktowany jest jak nazwa pliku znajdujacego sie
- w archiwum /help.a, po czym zostaje wyswietlona zawartosc tego pliku
- strona po stronie.
diff --git a/release/picobsd/help/hostname.hlp.en b/release/picobsd/help/hostname.hlp.en
deleted file mode 100644
index 0e29ffe18ff..00000000000
--- a/release/picobsd/help/hostname.hlp.en
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mhostname[m set or print name of current host system
-
- Usage:
-
- hostname [-s] [name-of-host]
diff --git a/release/picobsd/help/hostname.hlp.pl b/release/picobsd/help/hostname.hlp.pl
deleted file mode 100644
index b40bda80c33..00000000000
--- a/release/picobsd/help/hostname.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mhostname[m ustaw lub wyswietl nazwe maszyny
-
- Sposob uzycia:
-
- hostname [-s] [name-of-host]
diff --git a/release/picobsd/help/ifconfig.hlp.en b/release/picobsd/help/ifconfig.hlp.en
deleted file mode 100644
index 65da95f4952..00000000000
--- a/release/picobsd/help/ifconfig.hlp.en
+++ /dev/null
@@ -1,18 +0,0 @@
-[1mifconfig[m configure network interface parameters
-
- Usage:
-
- ifconfig -a [ -d ] [ -u ] [ af ]
- ifconfig -l [ -d ] [ -u ]
- [ af [ address [ dest_addr ] ] [ netmask mask ]
- [ broadcast addr ]
-
- [ alias ] [ delete ] ]
- [ up ] [ down ]
- [ metric n ]
- [ mtu n ]
- [ arp | -arp ]
- [ link0 | -link0 ] [ link1 | -link1 ] [ link2 | -link2 ]
- [ media mtype ]
- [ mediaopt mopts ]
- [ -mediaopt mopts ]
diff --git a/release/picobsd/help/ifconfig.hlp.pl b/release/picobsd/help/ifconfig.hlp.pl
deleted file mode 100644
index 7d35e4ead16..00000000000
--- a/release/picobsd/help/ifconfig.hlp.pl
+++ /dev/null
@@ -1,18 +0,0 @@
-[1mifconfig[m konfiguracja parametrow interfejsow sieciowych
-
- Sposob uzycia:
-
- ifconfig -a [ -d ] [ -u ] [ af ]
- ifconfig -l [ -d ] [ -u ]
- [ af [ address [ dest_addr ] ] [ netmask mask ]
- [ broadcast addr ]
-
- [ alias ] [ delete ] ]
- [ up ] [ down ]
- [ metric n ]
- [ mtu n ]
- [ arp | -arp ]
- [ link0 | -link0 ] [ link1 | -link1 ] [ link2 | -link2 ]
- [ media mtype ]
- [ mediaopt mopts ]
- [ -mediaopt mopts ]
diff --git a/release/picobsd/help/kbdcontrol.hlp.en b/release/picobsd/help/kbdcontrol.hlp.en
deleted file mode 100644
index 0a776568800..00000000000
--- a/release/picobsd/help/kbdcontrol.hlp.en
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mkbdcontrol[m a utility for manipulating the syscons keyboard driver section
-
- Usage:
-
- kbdcontrol [-dFx] [-b duration.pitch | belltype]
- [-r delay.repeat | speed] [-l mapfile] [-f # string]
- [-h size] [-L mapfile]
diff --git a/release/picobsd/help/kbdcontrol.hlp.pl b/release/picobsd/help/kbdcontrol.hlp.pl
deleted file mode 100644
index a4593370499..00000000000
--- a/release/picobsd/help/kbdcontrol.hlp.pl
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mkbdcontrol[m ustawianie parametrow klawiatury
-
- Sposob uzycia:
-
- kbdcontrol [-dFx] [-b dlugosc.wysokosc | rodzaj]
- [-r opoz.czest | szybk] [-l mapa] [-f # napis]
- [-h rozmiar] [-L mapa]
diff --git a/release/picobsd/help/kget.hlp.en b/release/picobsd/help/kget.hlp.en
deleted file mode 100644
index 632c807940f..00000000000
--- a/release/picobsd/help/kget.hlp.en
+++ /dev/null
@@ -1,21 +0,0 @@
-[1mkget[m Get list of kernel configuration.
-
- This utility allows to gather device configuration which possibly
- was changed in userconfig (-c) session, and to save it to /kernel.config
- file on startup floppy, so that when user boots next time, the
- settings will automatically be changed.
-
- Usage is straightforward:
-
- kget [-incore|kernel_name] [vanilla]
-
- E.g.: Get device configuration of running kernel
-
- kget -incore
-
- Produce list of parameters changed from /stand/vanilla
-
- kget -incore /stand/vanilla
-
- (You can redirect the stdout to /kernel.config - this list
- already contains all the requires keywords.)
diff --git a/release/picobsd/help/kget.hlp.pl b/release/picobsd/help/kget.hlp.pl
deleted file mode 100644
index 005fb26c8d1..00000000000
--- a/release/picobsd/help/kget.hlp.pl
+++ /dev/null
@@ -1,23 +0,0 @@
-[1mkget[m Utworz liste konfiguracji jadra
-
- Ten program pozwala uzyskac parametry sterownikow urzadzen,
- ktore byc moze zostaly zmienione na etapie uruchamiania systemu z
- flaga '-c', pozwala rowniez zachowac te liste w specjalnym formacie
- do pliku /kernel.config, zeby zostala uzyta jako dane konfiguracyjne
- przy nastepnym starcie systemu.
-
- Sposob uzycia:
-
- kget [-incore|nazwa_jadra] [vanilla]
-
- E.g.: Utworz liste parametrow dzialajacego jadra:
-
- kget -incore
-
- Utworz liste roznic w parametrach w stosunku do listy
- zawartej w pliku /stand/vanilla:
-
- kget -incore /stand/vanilla
-
- (Wynik tego polecenia mozna przekierowac wprost do pliku
- /kernel.config na dyskietce)
diff --git a/release/picobsd/help/kill.hlp.en b/release/picobsd/help/kill.hlp.en
deleted file mode 100644
index e6322e703b0..00000000000
--- a/release/picobsd/help/kill.hlp.en
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mkill[m terminate or signal a process
-
- Usage:
-
- kill [-s signal_name] pid ...
- kill -l [exit_status]
- kill -signal_name pid ...
- kill -signal_number pid ...
diff --git a/release/picobsd/help/kill.hlp.pl b/release/picobsd/help/kill.hlp.pl
deleted file mode 100644
index bde1e71686e..00000000000
--- a/release/picobsd/help/kill.hlp.pl
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mkill[m zakoncz proces, lub wyslij sygnal
-
- Sposob uzycia:
-
- kill [-s signal_name] pid ...
- kill -l [exit_status]
- kill -signal_name pid ...
- kill -signal_number pid ...
diff --git a/release/picobsd/help/ln.hlp.en b/release/picobsd/help/ln.hlp.en
deleted file mode 100644
index a7c7065a55a..00000000000
--- a/release/picobsd/help/ln.hlp.en
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mln[m make links
-
- Usage:
-
- ln [-fs] file1 file2
- ln [-fs] file ... directory
-
- -f Unlink any already existing file (force link)
- -s Create symbolic link
diff --git a/release/picobsd/help/ln.hlp.pl b/release/picobsd/help/ln.hlp.pl
deleted file mode 100644
index 22fbd0681f9..00000000000
--- a/release/picobsd/help/ln.hlp.pl
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mln[m utworz link
-
- Sposob uzycia:
-
- ln [-fs] plik1 plik2
- ln [-fs] plik ... katalog
-
- -f (force) usun uprzednio istniejacy plik o tej samej nazwie
- -s utworz link symboliczny
diff --git a/release/picobsd/help/ls.hlp.en b/release/picobsd/help/ls.hlp.en
deleted file mode 100644
index 7a171cba2ee..00000000000
--- a/release/picobsd/help/ls.hlp.en
+++ /dev/null
@@ -1,10 +0,0 @@
-[1mls[m list directory contents
-
- Usage:
-
- ls [-ACFLRTWacdfgikloqrstu1] [file ...]
-
- Most common switches are:
-
- -l list in long format
- -a include directory entries whose names begin with a dot '.'
diff --git a/release/picobsd/help/ls.hlp.pl b/release/picobsd/help/ls.hlp.pl
deleted file mode 100644
index f6860b69d91..00000000000
--- a/release/picobsd/help/ls.hlp.pl
+++ /dev/null
@@ -1,11 +0,0 @@
-[1mls[m wyswietl zawartosc katalogu
-
- Sposob uzycia:
-
- ls [-ACFLRTWacdfgikloqrstu1] [plik ...]
-
- Najczesciej uzywane opcje:
-
- -l (long) wyswietl w rozszerzonym formacie
- -a wyswietl rowniez te pliki, ktorych nazwy zaczynaja sie od '.'
- -R wyswietl rowniez zawartosc podkatalogow
diff --git a/release/picobsd/help/mkdir.hlp.en b/release/picobsd/help/mkdir.hlp.en
deleted file mode 100644
index 85c31422f25..00000000000
--- a/release/picobsd/help/mkdir.hlp.en
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mmkdir[m make directories
-
- Usage:
-
- mkdir [-p] [-m mode] directory ...
diff --git a/release/picobsd/help/mkdir.hlp.pl b/release/picobsd/help/mkdir.hlp.pl
deleted file mode 100644
index 2354766303c..00000000000
--- a/release/picobsd/help/mkdir.hlp.pl
+++ /dev/null
@@ -1,5 +0,0 @@
-[1mmkdir[m utworz katalog
-
- Sposob uzycia:
-
- mkdir [-p] [-m mode] nazwa_katalogu ...
diff --git a/release/picobsd/help/more.hlp.en b/release/picobsd/help/more.hlp.en
deleted file mode 100644
index 0333be22bca..00000000000
--- a/release/picobsd/help/more.hlp.en
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mmore[m file perusal filter for crt viewing
-
- Usage:
-
- more [-ceinus] [-t tag] [-x tabs] [-/ pattern] [-#] [file ...]
-
- But most commonly just 'more ' or e.g. 'ls -l|more'
diff --git a/release/picobsd/help/more.hlp.pl b/release/picobsd/help/more.hlp.pl
deleted file mode 100644
index 1e4d4e955fb..00000000000
--- a/release/picobsd/help/more.hlp.pl
+++ /dev/null
@@ -1,8 +0,0 @@
-[1mmore[m program do wyswietlania zawartosci plikow
-
- Sposob uzycia:
-
- more [-ceinus] [-t tag] [-x tabs] [-/ pattern] [-#] [plik ...]
-
- Najczesciej stosowany w postaci 'more nazwa pliku' lub jako
- filtr: 'ls -l | more'
diff --git a/release/picobsd/help/mount.hlp.en b/release/picobsd/help/mount.hlp.en
deleted file mode 100644
index d39003eb009..00000000000
--- a/release/picobsd/help/mount.hlp.en
+++ /dev/null
@@ -1,21 +0,0 @@
-[1mmount[m mount file systems
-
- Usage:
-
- mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
- mount [-adfpruvw] [-t ufs | external_type]
- mount [-dfpruvw] special | node
-
- E.g.:
-
- * mount UFS floppy A: on /mnt directory:
-
- mount /dev/fd0c /mnt
-
- * mount DOS primary partition (on primary IDE drive) on /dos:
-
- mount -t msdosfs /dev/wd0s1 /dos
-
- * mount Linux partition on /mnt
-
- mount -t ext2fs /dev/wd0s1 /mnt
diff --git a/release/picobsd/help/mount.hlp.pl b/release/picobsd/help/mount.hlp.pl
deleted file mode 100644
index 33609abff91..00000000000
--- a/release/picobsd/help/mount.hlp.pl
+++ /dev/null
@@ -1,19 +0,0 @@
-[1mmount[m zamontuj system plikow
-
- Sposob uzycia:
-
- mount [-dfpruvw] [-o opcje] [-t [ufs|msdosfs|ext2fs] urzadzenie punkt
-
- N.p.:
-
- * zamontuj dyskietke DOS A: na katalogu /mnt:
-
- mount -t msdosfs /dev/fd0a /mnt
-
- * zamontuj pierwsza partycje DOS (na pierwszym dysku IDE) na /dos:
-
- mount -t msdosfs /dev/wd0s1 /dos
-
- * zamontuj partycje Linux na /mnt:
-
- mount -t ext2fs /dev/wd0s1 /mnt
diff --git a/release/picobsd/help/mount_cd9660.hlp.en b/release/picobsd/help/mount_cd9660.hlp.en
deleted file mode 100644
index 1e138248cb2..00000000000
--- a/release/picobsd/help/mount_cd9660.hlp.en
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mmount_cd9660[m mount an ISO-9660 filesystem
-
- Usage:
-
- mount_cd9660 [-egrv] [-o options] [-s startsector] special node
-
- Most commonly, to mount an ATAPI CD-ROM on /mnt directory:
-
- mount_cd9660 /dev/wcd0c /mnt
diff --git a/release/picobsd/help/mount_cd9660.hlp.pl b/release/picobsd/help/mount_cd9660.hlp.pl
deleted file mode 100644
index d7b7d751117..00000000000
--- a/release/picobsd/help/mount_cd9660.hlp.pl
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mmount_cd9660[m zamontuj CD-ROM (ISO-9660 filesystem)
-
- Sposob uzycia:
-
- mount_cd9660 [-egrv] [-o options] [-s startsector] urzadzenie punkt
-
- Najczesciej w celu zamontowania CD-ROMu ATAPI:
-
- mount_cd9660 /dev/wcd0c /mnt
diff --git a/release/picobsd/help/mount_ext2fs.hlp.en b/release/picobsd/help/mount_ext2fs.hlp.en
deleted file mode 100644
index 636d9c90a72..00000000000
--- a/release/picobsd/help/mount_ext2fs.hlp.en
+++ /dev/null
@@ -1,11 +0,0 @@
-[1mmount_ext2fs[m mount a ext2fs (Linux) file system
-
- Usage:
-
- mount_ext2fs [-o options] special node
-
- E.g. to mount first partition of first IDE drive on /mnt:
-
- mount_ext2fs /dev/wd0s1 /mnt
-
- To mount it read-only, add '-o ro' as options.
diff --git a/release/picobsd/help/mount_ext2fs.hlp.pl b/release/picobsd/help/mount_ext2fs.hlp.pl
deleted file mode 100644
index f2c241c0a56..00000000000
--- a/release/picobsd/help/mount_ext2fs.hlp.pl
+++ /dev/null
@@ -1,11 +0,0 @@
-[1mmount_ext2fs[m zamontuj system plikow EXT2FS (Linux)
-
- Sposob uzycia:
-
- mount_ext2fs [-o opcje] urzadzenie punkt
-
- N.p. zeby zamontowac pierwsza partycje na pierwszym dysku IDE:
-
- mount_ext2fs /dev/wd0s1 /mnt
-
- W celu zamontowania tylko do odczytu, nalezy dodac opcje -o ro.
diff --git a/release/picobsd/help/mount_msdosfs.hlp.en b/release/picobsd/help/mount_msdosfs.hlp.en
deleted file mode 100644
index cda3082f4e2..00000000000
--- a/release/picobsd/help/mount_msdosfs.hlp.en
+++ /dev/null
@@ -1,13 +0,0 @@
-[1mmount_msdosfs[m mount an MS-DOS file system
-
- Usage:
-
- mount_msdosfs [-o options] [-u user] [-g group] [-m mask] bdev dir
-
- E.g. to mount primary DOS partition of primary IDE drive on /dos:
-
- mount_msdosfs /dev/wd0s1 /dos
-
- To mount first extended partition on /mnt:
-
- mount_msdosfs /dev/wd0s5 /mnt
diff --git a/release/picobsd/help/mount_msdosfs.hlp.pl b/release/picobsd/help/mount_msdosfs.hlp.pl
deleted file mode 100644
index 09bc0c2bc8e..00000000000
--- a/release/picobsd/help/mount_msdosfs.hlp.pl
+++ /dev/null
@@ -1,13 +0,0 @@
-[1mmount_msdosfs[m zamontuj system plikow MS-DOS
-
- Sposob uzycia:
-
- mount_msdosfs [-o opcje] [-u user] [-g grupa] [-m maska] bdev dir
-
- N.p. zeby zamontowac partycje C: z dysku IDE na /doc
-
- mount_msdosfs /dev/wd0s1 /dos
-
- W celu zamontowania pierwszej partycji extended"
-
- mount_msdosfs /dev/wd0s5 /mnt
diff --git a/release/picobsd/help/moused.hlp.en b/release/picobsd/help/moused.hlp.en
deleted file mode 100644
index 0b7f7f40181..00000000000
--- a/release/picobsd/help/moused.hlp.en
+++ /dev/null
@@ -1,44 +0,0 @@
-[1mmoused[m mouse daemon
-
- Usage:
-
- moused [-3DPRcdfs] [-F rate] [-r resolution] [-S baudrate] [-C threshold]
- [-m N=M] [-z target] [-t mousetype] -p port
-
- Most common options are:
-
- -3 Emulate the third (middle) button for 2-button mice. It is emu-
- lated by pressing the left and right physical buttons simultane-
- ously.
- -p port Use port to communicate with the mouse.
- -t type
- microsoft Microsoft (2-button) serial mouse protocol.
- intellimouse Microsoft IntelliMouse protocol. Genius Net-
- Mouse, ASCII Mie Mouse, Logitech MouseMan+ and
- FirstMouse+ use this protocol too.
- mousesystems MouseSystems 5-byte protocol. 3-button mice may
- use this protocol.
- mmseries MM Series mouse protocol.
- logitech Logitech mouse protocol. Note that this is for
- old Logitech models. mouseman or intellimouse
- should be specified for newer models.
- mouseman Logitech MouseMan and TrackMan protocol. Some
- 3-button mice may be compatible with this proto-
- col. Note that MouseMan+ and FirstMouse+ use
- intellimouse protocol rather than this one.
- glidepoint ALPS GlidePoint protocol.
- thinkingmouse Kensington ThinkingMouse protocol.
- mmhittab Hitachi tablet protocol.
-
-3-button serial mice may have a small switch to choose between
-``MS'' and ``PC'', or ``2'' and ``3''. ``MS'' or ``2'' usually mean
-the microsoft protocol. ``PC'' or ``3'' will choose the
-mousesystems protocol.
-To test if the selected protocol type is correct for the given mouse, en-
-able the mouse pointer in the current virtual console:
- vidcontrol -m on
-start the mouse daemon in the foreground mode:
- moused -f -p _selected_port_ -t _selected_protocol_
-and see if the mouse pointer travels correctly according to the mouse
-movement. Then try cut & paste features by clicking the left, right and
-middle buttons. Type ^C to stop the command.
diff --git a/release/picobsd/help/moused.hlp.pl b/release/picobsd/help/moused.hlp.pl
deleted file mode 100644
index 41791207e71..00000000000
--- a/release/picobsd/help/moused.hlp.pl
+++ /dev/null
@@ -1,29 +0,0 @@
-[1mmoused[m mouse daemon
-
- Sposob uzycia:
-
- moused [-3DPRcdfs] [-F rate] [-r resolution] [-S baudrate] [-C threshold]
- [-m N=M] [-z target] [-t mousetype] -p port
-
- Najczestsze opcje to:
-
- -3 emulacja trzeciego (srodkowego) przycisku na dwu-klawiszowych
- myszach.
- -p port nazwa portu: /dev/cuaa0 == COM1:, psm0 == gniazdo PS/2
- -t typ
- microsoft Microsoft (2 przyciski) mysz szeregowa.
- intellimouse Microsoft IntelliMouse, Genius Net- Mouse,
- ASCII Mie Mouse, Logitech MouseMan+, FirstMouse+
- mousesystems MouseSystems
- mmseries MM Series
- logitech Logitech. Ten protokol jest dla starszych typow
- myszy - dla nowszych trzeba uzywac mouseman lub
- intellimouse
- mouseman Logitech MouseMan i TrackMan
- glidepoint ALPS GlidePoint
- thinkingmouse Kensington ThinkingMouse protocol.
- mmhittab Hitachi tablet
-
-Mozna wlaczyc wyswietlanie wskaznika myszy przez:
-
- vidcontrol -m on
diff --git a/release/picobsd/help/mv.hlp.en b/release/picobsd/help/mv.hlp.en
deleted file mode 100644
index 0cbf6d8991c..00000000000
--- a/release/picobsd/help/mv.hlp.en
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mmv[m move files
-
- Usage:
-
- mv [-f | -i] source target
- mv [-f | -i] source ... directory
-
- -f Do not prompt for confirmation
- -i Prompt for confirmation
diff --git a/release/picobsd/help/mv.hlp.pl b/release/picobsd/help/mv.hlp.pl
deleted file mode 100644
index 5a6b27e50fb..00000000000
--- a/release/picobsd/help/mv.hlp.pl
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mmv[m przenis plik(i)
-
- Sposob uzycia:
-
- mv [-f | -i] plik1 plik2
- mv [-f | -i] plik1 ... plikN katalog
-
- -f nie pytaj o potwierdzenie
- -i pytaj o potwierdzenie
diff --git a/release/picobsd/help/ping.hlp.en b/release/picobsd/help/ping.hlp.en
deleted file mode 100644
index 6d3cb71079f..00000000000
--- a/release/picobsd/help/ping.hlp.en
+++ /dev/null
@@ -1,10 +0,0 @@
-[1mping[m send ICMP ECHO_REQUEST packets to network hosts
-
- Usage:
-
- ping [-QRadfnqrv] [-c count] [-i wait] [-l preload] [-p pattern]
- [-s packetsize] [host | [-L] [-I iface] [-T ttl] mcast-group]
-
- Most commonly:
-
- ping
diff --git a/release/picobsd/help/ping.hlp.pl b/release/picobsd/help/ping.hlp.pl
deleted file mode 100644
index 47faed6a12f..00000000000
--- a/release/picobsd/help/ping.hlp.pl
+++ /dev/null
@@ -1,10 +0,0 @@
-[1mping[m wyslij prosbe ICMP o echo
-
- Sposob uzycia:
-
- ping [-QRadfnqrv] [-c count] [-i wait] [-l preload] [-p pattern]
- [-s packetsize] [host | [-L] [-I iface] [-T ttl] mcast-group]
-
- Najczesciej:
-
- ping nazwa_maszyny
diff --git a/release/picobsd/help/ppp.hlp.en b/release/picobsd/help/ppp.hlp.en
deleted file mode 100644
index 55527dd7230..00000000000
--- a/release/picobsd/help/ppp.hlp.en
+++ /dev/null
@@ -1,16 +0,0 @@
-[1mppp[m Point to Point Protocol client
-
- Usage:
-
- ppp [-auto | -background | -direct | -dedicated | -ddial ] [system]
-
- In case of PicoBSD most probably this will be:
-
- ppp -background
-
- You should run 'dialup' script to configure automatic dialing. Then
- you can use
-
- ppp -background dialup
-
- to connect to your provider.
diff --git a/release/picobsd/help/ppp.hlp.pl b/release/picobsd/help/ppp.hlp.pl
deleted file mode 100644
index 7c5f6a6c597..00000000000
--- a/release/picobsd/help/ppp.hlp.pl
+++ /dev/null
@@ -1,14 +0,0 @@
-[1mppp[m obsluga protokolu PPP
-
- Sposob uzycia:
-
- ppp [-auto | -background | -direct | -dedicated | -ddial ] [system]
-
- W przypadku PicoBSD najczesciej bedzie to:
-
- ppp -background nazwa_polaczenia
-
- Nalezy przedtem uruchomic skrypt 'dialup' w celu poprawnej
- konfiguracji. Wowczas w celu dokonania polaczenia wystarczy:
-
- ppp -background dialup
diff --git a/release/picobsd/help/ps.hlp.en b/release/picobsd/help/ps.hlp.en
deleted file mode 100644
index 3e5125b3a04..00000000000
--- a/release/picobsd/help/ps.hlp.en
+++ /dev/null
@@ -1,9 +0,0 @@
-[1mps[m List running processes
-
- This is a small 'ps' replacement, which uses information
- available via sysctl(3) interface. It's primitive, but
- gives you the most important informations, i.e. how many
- processes are running and on which vty, and the pid number
- to kill some of them. :-)
-
- Currently, no options are implemented yet.
diff --git a/release/picobsd/help/ps.hlp.pl b/release/picobsd/help/ps.hlp.pl
deleted file mode 100644
index f9b61ccd550..00000000000
--- a/release/picobsd/help/ps.hlp.pl
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mps[m Pokaz dzialajace procesy
-
- Prosta wersja programu, korzystajaca z informacji dostepnych przez
- sysctl(3). Wyswietla wystarczajaco duzo informacji, zeby zorientowac
- sie w stanie systemu, oraz ewentualnie zastopowac jakies procesy.
-
- Obecnie nie posiada zadnych opcji.
diff --git a/release/picobsd/help/pwd.hlp.en b/release/picobsd/help/pwd.hlp.en
deleted file mode 100644
index 593a9ebd57d..00000000000
--- a/release/picobsd/help/pwd.hlp.en
+++ /dev/null
@@ -1 +0,0 @@
-[1mpwd[m return working directory name
diff --git a/release/picobsd/help/pwd.hlp.pl b/release/picobsd/help/pwd.hlp.pl
deleted file mode 100644
index 2a926bcfb6b..00000000000
--- a/release/picobsd/help/pwd.hlp.pl
+++ /dev/null
@@ -1 +0,0 @@
-[1mpwd[m wyswietl aktualny katalog.
diff --git a/release/picobsd/help/reboot.hlp.en b/release/picobsd/help/reboot.hlp.en
deleted file mode 100644
index d40c8ca398c..00000000000
--- a/release/picobsd/help/reboot.hlp.en
+++ /dev/null
@@ -1,3 +0,0 @@
-[1mreboot[m reboot the system
-
- Press Ctlr-Alt-Del instead of 'reboot'.
diff --git a/release/picobsd/help/reboot.hlp.pl b/release/picobsd/help/reboot.hlp.pl
deleted file mode 100644
index b809804f31d..00000000000
--- a/release/picobsd/help/reboot.hlp.pl
+++ /dev/null
@@ -1,3 +0,0 @@
-[1mreboot[m zrestartuj system
-
- Nacisnij Ctlr-Alt-Del.
diff --git a/release/picobsd/help/rm.hlp.en b/release/picobsd/help/rm.hlp.en
deleted file mode 100644
index 60f2cd11feb..00000000000
--- a/release/picobsd/help/rm.hlp.en
+++ /dev/null
@@ -1,13 +0,0 @@
-[1mrm[m remove directory entries
-
- Usage:
-
- rm [-f | -i] [-dPRrW] file ...
-
- -f attepmt removal without confirmation, regardless of
- premissions
- -i request confirmation before removing
- -r remove the whole tree rooted at "file" argument
-
- [1mWARNING:[m There is no way to "undelete" deleted files! They
- are lost forever.
diff --git a/release/picobsd/help/rm.hlp.pl b/release/picobsd/help/rm.hlp.pl
deleted file mode 100644
index d847ff0b48c..00000000000
--- a/release/picobsd/help/rm.hlp.pl
+++ /dev/null
@@ -1,12 +0,0 @@
-[1mrm[m usun plik(i)
-
- Sposob uzycia:
-
- rm [-f | -i] [-dPRrW] plik ...
-
- -f sprobuj usunac sila, nie sprawdzajac praw dostepu
- -i pytaj przed usunieciem
- -r usun cale drzewko zaczynajace sie od nazwy 'plik'
-
- [1mOSTRZEZENIE:[m Nie ma zadnego sposobu na odtworzenie
- skasowanych plikow!!! Sa one stracone na zawsze.
diff --git a/release/picobsd/help/route.hlp.en b/release/picobsd/help/route.hlp.en
deleted file mode 100644
index bf0061bc61a..00000000000
--- a/release/picobsd/help/route.hlp.en
+++ /dev/null
@@ -1,13 +0,0 @@
-[1mroute[m manually manipulate the routing tables
-
- Usage:
-
- route [ -nqv ] command [[ modifiers ] args ]
-
- Where 'command' is most commonly 'add' or 'delete', modifiers can be
- '-net' or '-host', and args are destination and gateway.
-
- E.g., to add default route to the gateway:
-
- route add default
-
diff --git a/release/picobsd/help/route.hlp.pl b/release/picobsd/help/route.hlp.pl
deleted file mode 100644
index 92f4f6d03a7..00000000000
--- a/release/picobsd/help/route.hlp.pl
+++ /dev/null
@@ -1,13 +0,0 @@
-[1mroute[m recznie manipuluj tablica routingu
-
- Sposob uzycia:
-
- route [ -nqv ] polecenie [[ opcje ] args ]
-
- 'Polecenie' to najczesciej 'add' (dodaj) lub 'delete' (usun),
- 'opcje to '-net' lub '-host', a argumenty to nazwa hosta lub routera.
-
- Np. w celu dodania routingu do podstawowego routera w sieci (default):
-
- route add default nazwa_routera
-
diff --git a/release/picobsd/help/sh.hlp.en b/release/picobsd/help/sh.hlp.en
deleted file mode 100644
index 6198b237eff..00000000000
--- a/release/picobsd/help/sh.hlp.en
+++ /dev/null
@@ -1,3 +0,0 @@
-[1msh[m a Bourne Shell (command interpreter)
-
- This version is a slightly stripped down /bin/sh, also known as Ash.
diff --git a/release/picobsd/help/sh.hlp.pl b/release/picobsd/help/sh.hlp.pl
deleted file mode 100644
index c278b8e3824..00000000000
--- a/release/picobsd/help/sh.hlp.pl
+++ /dev/null
@@ -1,3 +0,0 @@
-[1msh[m Bourne Shell (interpeter polecen)
-
- Jeest to Ash, nieco skromniejsz wersja standardowego /bin/sh.
diff --git a/release/picobsd/help/shutdown.hlp.en b/release/picobsd/help/shutdown.hlp.en
deleted file mode 100644
index f222d5ac372..00000000000
--- a/release/picobsd/help/shutdown.hlp.en
+++ /dev/null
@@ -1,3 +0,0 @@
-[1mshutdown[m shut down the system
-
- Press Ctlr-Alt-Del instead of 'shutdown'.
diff --git a/release/picobsd/help/shutdown.hlp.pl b/release/picobsd/help/shutdown.hlp.pl
deleted file mode 100644
index 2a9a47a3269..00000000000
--- a/release/picobsd/help/shutdown.hlp.pl
+++ /dev/null
@@ -1,3 +0,0 @@
-[1mshutdown[m zakoncz dzialanie systemu
-
- Nacisnij Ctlr-Alt-Del
diff --git a/release/picobsd/help/ssh.hlp.en b/release/picobsd/help/ssh.hlp.en
deleted file mode 100644
index bf6c168e22c..00000000000
--- a/release/picobsd/help/ssh.hlp.en
+++ /dev/null
@@ -1,29 +0,0 @@
-[1mssh[m Secure Shell remote access command
-
- Usage: ssh [options] host [command]
-
- -l user Log in using this user name.
- -n Redirect input from /dev/null.
- -a Disable authentication agent forwarding.
- -x Disable X11 connection forwarding.
- -i file Identity for RSA authentication (default: ~/.ssh/identity).
- -t Tty; allocate a tty even if command is given.
- -v Verbose; display verbose debugging messages.
- -V Display version number only.
- -q Quiet; don't display any warning messages.
- -f Fork into background after authentication.
- -e char Set escape character; ``none'' = disable (default: ~).
- -c cipher Select encryption algorithm: ``idea'', ``3des''
- -p port Connect to this port. Server must be on the same port.
- -P Don't use priviledged source port.
- -L listen-port:host:port Forward local port to remote address
- -R listen-port:host:port Forward remote port to local address
- These cause ssh to listen for connections on a port, and
- forward them to the other side by connecting to host:port.
- -C Enable compression.
- -o 'option' Process the option as if it was read from a configuration
- file.
-
- Most commonly this will be:
-
- ssh -l your_login remote_host
diff --git a/release/picobsd/help/ssh.hlp.pl b/release/picobsd/help/ssh.hlp.pl
deleted file mode 100644
index 5a0d3cbac97..00000000000
--- a/release/picobsd/help/ssh.hlp.pl
+++ /dev/null
@@ -1,29 +0,0 @@
-[1mssh[m Secure Shell
-
- Sposob uzycia: ssh [options] host [command]
-
- -l user Log in using this user name.
- -n Redirect input from /dev/null.
- -a Disable authentication agent forwarding.
- -x Disable X11 connection forwarding.
- -i file Identity for RSA authentication (default: ~/.ssh/identity).
- -t Tty; allocate a tty even if command is given.
- -v Verbose; display verbose debugging messages.
- -V Display version number only.
- -q Quiet; don't display any warning messages.
- -f Fork into background after authentication.
- -e char Set escape character; ``none'' = disable (default: ~).
- -c cipher Select encryption algorithm: ``idea'', ``3des''
- -p port Connect to this port. Server must be on the same port.
- -P Don't use priviledged source port.
- -L listen-port:host:port Forward local port to remote address
- -R listen-port:host:port Forward remote port to local address
- These cause ssh to listen for connections on a port, and
- forward them to the other side by connecting to host:port.
- -C Enable compression.
- -o 'option' Process the option as if it was read from a configuration
- file.
-
- Najczesciej uzywa sie w tej postaci:
-
- ssh -l nazwa_uzytk nazwa_maszyny
diff --git a/release/picobsd/help/sysctl.hlp.en b/release/picobsd/help/sysctl.hlp.en
deleted file mode 100644
index 8a2c911a5af..00000000000
--- a/release/picobsd/help/sysctl.hlp.en
+++ /dev/null
@@ -1,15 +0,0 @@
-[1msysctl[m get or set kernel state
-
- Usage:
-
- sysctl [-bnX] variable ...
- sysctl [-bnX] -w variable=value ...
- sysctl [-bnX] -a
- sysctl [-bnX] -A
-
- To see the whole MIB table use:
- sysctl -a
-
- To set specific variable to new value use:
-
- sysctl -w variable=value
diff --git a/release/picobsd/help/sysctl.hlp.pl b/release/picobsd/help/sysctl.hlp.pl
deleted file mode 100644
index abce3318bb1..00000000000
--- a/release/picobsd/help/sysctl.hlp.pl
+++ /dev/null
@@ -1,15 +0,0 @@
-[1msysctl[m ustaw lub wyswietl parametr jadra
-
- Sposob uzycia:
-
- sysctl [-bnX] zmienna ...
- sysctl [-bnX] -w zmienna=wartosc ...
- sysctl [-bnX] -a
- sysctl [-bnX] -A
-
- W celu wyswietlenia calego drzewa MIB:
- sysctl -a
-
- W celu przypisania wartosci zmiennek:
-
- sysctl -w zmienna=wartosc
diff --git a/release/picobsd/help/telnet.hlp.en b/release/picobsd/help/telnet.hlp.en
deleted file mode 100644
index ddceebd53e6..00000000000
--- a/release/picobsd/help/telnet.hlp.en
+++ /dev/null
@@ -1,14 +0,0 @@
-[1mtelnet[m user interface to the TELNET protocol
-
- Usage:
-
- telnet [-8] [-E] [-L] [-S tos] [-a] [-c] [-d] [-e char] [-l user]
- [-n tracefile][-r] [host-name [port]]
-
- Most commonly this will be just:
-
- telnet
-
- [1mWARNING:[m Telnet protocol is unsafe, as it passes the
- passwords in clear text over the network. Use 'ssh' instead, where it's
- possible.
diff --git a/release/picobsd/help/telnet.hlp.pl b/release/picobsd/help/telnet.hlp.pl
deleted file mode 100644
index be3f77b2aba..00000000000
--- a/release/picobsd/help/telnet.hlp.pl
+++ /dev/null
@@ -1,14 +0,0 @@
-[1mtelnet[m klient protokolu Telnet
-
- Sposob uzycia:
-
- telnet [-8] [-E] [-L] [-S tos] [-a] [-c] [-d] [-e char] [-l user]
- [-n tracefile][-r] [host-name [port]]
-
- Najczesciej jest to:
-
- telnet nazwa_maszyny
-
- [1mUWAGA:[m Protokol telnet jest niezbyt bezpieczny, gdyz
- przesyla niezaszyfrowane hasla przez siec. Jesli to mozliwe, uzywaj
- zamiast niego SSH.
diff --git a/release/picobsd/help/test.hlp.en b/release/picobsd/help/test.hlp.en
deleted file mode 100644
index 351dc764895..00000000000
--- a/release/picobsd/help/test.hlp.en
+++ /dev/null
@@ -1 +0,0 @@
-[1mtest[m condition evaluation utility
diff --git a/release/picobsd/help/test.hlp.pl b/release/picobsd/help/test.hlp.pl
deleted file mode 100644
index de1cec87fdc..00000000000
--- a/release/picobsd/help/test.hlp.pl
+++ /dev/null
@@ -1 +0,0 @@
-[1mtest[m sprawdz istnienie warunku
diff --git a/release/picobsd/help/traceroute.hlp.en b/release/picobsd/help/traceroute.hlp.en
deleted file mode 100644
index 6eccd46b29f..00000000000
--- a/release/picobsd/help/traceroute.hlp.en
+++ /dev/null
@@ -1,14 +0,0 @@
-[1mtraceroute[m print the route packets take to network host
-
- Usage:
-
- traceroute [-dnrv] [-w wait] [-m max_ttl] [-p port#] [-q nqueries]
- [-t tos] [-s src_addr] [-g gateway] host [data_size]
-
- Most commonly:
-
- traceroute
- or
- traceroute -n
-
- if you don't want to waste time for resolving IP addresses into names.
diff --git a/release/picobsd/help/traceroute.hlp.pl b/release/picobsd/help/traceroute.hlp.pl
deleted file mode 100644
index bddf4a479df..00000000000
--- a/release/picobsd/help/traceroute.hlp.pl
+++ /dev/null
@@ -1,14 +0,0 @@
-[1mtraceroute[m pokaż trasę pakietów w sieci
-
- Sposób użycia:
-
- traceroute [-dnrv] [-w wait] [-m max_ttl] [-p port#] [-q nqueries]
- [-t tos] [-s src_addr] [-g gateway] host [data_size]
-
- Najczęściej:
-
- traceroute
- lub
- traceroute -n
-
- jeśli nie chcesz tracić czasu na zamianę adresów IP na nazwy.
diff --git a/release/picobsd/help/umount.hlp.en b/release/picobsd/help/umount.hlp.en
deleted file mode 100644
index 910a0b4bed1..00000000000
--- a/release/picobsd/help/umount.hlp.en
+++ /dev/null
@@ -1,12 +0,0 @@
-[1mumount[m unmount filesystems
-
- Usage:
-
- umount [-fv] special | node
- umount -a | -A [-fv] [-h host] [-t type]
-
- Most commonly this will be:
-
- umount
-
- e.g. 'umount /mnt'
diff --git a/release/picobsd/help/umount.hlp.pl b/release/picobsd/help/umount.hlp.pl
deleted file mode 100644
index 20ea0d183d6..00000000000
--- a/release/picobsd/help/umount.hlp.pl
+++ /dev/null
@@ -1,12 +0,0 @@
-[1mumount[m odmontuj system plikow
-
- Sposob uzycia:
-
- umount [-fv] urzadzenie | punkt
- umount -a | -A [-fv] [-h host] [-t type]
-
- Najczesciej:
-
- umount /nazwa_katalogu
-
- Np. 'umount /mnt'
diff --git a/release/picobsd/help/vidcontrol.hlp.en b/release/picobsd/help/vidcontrol.hlp.en
deleted file mode 100644
index 0aafefbcfa3..00000000000
--- a/release/picobsd/help/vidcontrol.hlp.en
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mvidcontrol[m a utility for manipulating the syscons video driver
-
- Usage:
-
- vidcontrol [-r fg bg] [-b color] [-c appearance] [-d] [-l scrmap]
- [-L] [-m on|off] [-f size file] [-s number] [-t N|off]
- [-x] [mode] [fgcol [bgcol]] [show]
diff --git a/release/picobsd/help/vidcontrol.hlp.pl b/release/picobsd/help/vidcontrol.hlp.pl
deleted file mode 100644
index 5e8df49cbce..00000000000
--- a/release/picobsd/help/vidcontrol.hlp.pl
+++ /dev/null
@@ -1,7 +0,0 @@
-[1mvidcontrol[m ustwa parametry sterownika video
-
- Sposob uzycia:
-
- vidcontrol [-r fg bg] [-b kolor] [-c kursor] [-d] [-l mapa]
- [-L] [-m on|off] [-f rozmiar plik] [-s numer] [-t N|off]
- [-x] [mode] [fgcol [bgcol]] [show]
diff --git a/release/picobsd/help/vm.hlp.en b/release/picobsd/help/vm.hlp.en
deleted file mode 100644
index 6a391c1b195..00000000000
--- a/release/picobsd/help/vm.hlp.en
+++ /dev/null
@@ -1,12 +0,0 @@
-[1mvm[m Show memory usage.
-
- This program repeatedly displays current memory usage, showing the
- following numbers:
-
- * procs: number of processes; r - running, w - waiting for I/O,
- l - sleeping, s - swapping
- * virt mem: virtual memory amounts (total and active), in kB
- * real mem: real memory amounts (total and active), in kB
- * shared vm: amount of shared virtual memory (total and active), in kB
- * shared real: amount of shared real memory (total and active), in kB
- * free: amount of free memory, in kB
diff --git a/release/picobsd/help/vm.hlp.pl b/release/picobsd/help/vm.hlp.pl
deleted file mode 100644
index 00b8509a92d..00000000000
--- a/release/picobsd/help/vm.hlp.pl
+++ /dev/null
@@ -1,14 +0,0 @@
-[1mvm[m Pokaz zajetosc pamieci
-
- Program pokazuje aktualna zajetosc pamieci (do nacisniecia ^C),
- wyswietlajac nastepujace wartosci:
-
- * procs: liczba procesow: r - running (dzialajace),
- w - czekajace na I/O,
- l - sleeping,
- s - swapping,
- * virt mem: ilosc pamieci witrualnej (total i active), w kB
- * real mem: ilosc pamieci rzeczywistej (total i active) w kB
- * shared vm: ilosc dzielonej pamieci wirtualnej, w kB
- * shared real: ilosc dzielonej pamieci rzeczywistej, w kB
- * free: ilosc wolnej pamieci, w kB.