docs: clean up old readme files

Removal of information which is simply wrong.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
This commit is contained in:
Sami Kerola 2011-08-12 22:00:13 +02:00
parent 0420105003
commit 1a06cbf4f6
6 changed files with 7 additions and 166 deletions

View File

@ -12,16 +12,6 @@ installation process easier.
If you write a bad partition table to disk, it may destroy data and
partitions.
You can FTP cfdisk from ftp.cs.unc.edu in the /pub/martin/linux
directory.
I would also like comments (good and bad) on the user interface, logic
and ease of use. If you have any suggestions for improvements, I
would be happy to hear them.
My e-mail address is martin@cs.unc.edu.
-------------------------------------------------------------------
Copyright (C) 1994 Kevin E. Martin (martin@cs.unc.edu)

View File

@ -2,13 +2,6 @@
col - filter out reverse line feeds.
Options are:
-b do not print any backspaces (last character written is printed)
-f allow half line feeds in output, by default characters between
lines are pushed to the line below
-x do not compress spaces into tabs.
-l num keep (at least) num lines in memory, 128 are kept by default
In the 32V source code to col(1) the default behavior was to NOT compress
spaces into tabs. There was a -h option which caused it to compress spaces
into tabs. There was no -x flag.

View File

@ -143,13 +143,13 @@ You can have up to 64 partitions on a single IDE disk, or up to 16
partitions on a single SCSI disk, at least as far as Linux is
concerned; in practice you will rarely want so many. The maximum size
of a Linux file system on a single partition depends on the type of
file system you use. Minix file systems are limited to 64 megabytes.
You may have all of your Linux files in a single partition, or you may
have two, three, or more Linux file systems. Similarly you may have
one or more DOS partitions. If you have several small partitions, you
run much less risk of losing all your files if your disk gets
corrupted. On the other hand, you may run out of space on a small
partition more easily.
file system you use. Minix file systems (version 1) are limited to 64
megabytes. You may have all of your Linux files in a single partition,
or you may have two, three, or more Linux file systems. Similarly you
may have one or more DOS partitions. If you have several small
partitions, you run much less risk of losing all your files if your
disk gets corrupted. On the other hand, you may run out of space on a
small partition more easily.
Under DOS, you must refer to each partition by a separate drive
letter, but all partitions are automatically accessible. Under Linux
@ -171,8 +171,6 @@ space in a file, but you need a partition big enough to hold it, and
this will probably be less efficient than having a partition devoted to
swap.
The disk space you need for Linux is discussed in README.prepare.
Are you going to boot Linux from the hard disk, or will you boot
from a floppy? Some boot programs place severe restrictions on where
the boot partition can be. LILO is more relaxed about this, but does

View File

@ -3,50 +3,6 @@ This package contains a reimplementation of getopt(1).
PREFACE
Getopt(1) is a program to help shell scripts parse command-line parameters.
It is for example included in the util-linux distribution (upto version
2.7.1). But, there are some problems with that getopt(1) implementation,
as listed in the 'BUGS' section of its man-page:
>BUGS
> Whatever getopt(3) has.
>
> Arguments containing white space or imbedded shell metacharacters gener-
> ally will not survive intact; this looks easy to fix but isn't.
>
> The error message for an invalid option is identified as coming from
> getopt rather than from the shell procedure containing the invocation of
> getopt; this again is hard to fix.
>
> The precise best way to use the set command to set the arguments without
> disrupting the value(s) of shell options varies from one shell version to
> another.
This implementation of getopt(1) is written to solve some of these problems,
while still staying (for all practical purposes) completely compatible with
other getopt(1) implementations.
INSTALLATION
Installation should be very easy. Just type 'make' to compile the sources.
It should compile cleanly, without any warnings, but even if it does not
you probably don't have to worry. You must use GNU Make and gcc, or you
will have to edit the Makefile.
Type 'make install' to install the binary and the manual page. It installs
by default in /usr/local/bin and /usr/local/man/man1, to install in /usr/bin
and /usr/man/man1 try 'make install prefix=/usr'.
The example files can be installed in /usr/local/lib/getopt by calling
'make install_doc'.
If you do not trust the getopt(3) in your libc, or if you do not use a libc
with the GNU getopt(3) routines, you can use the gnu sources as provided
in the gnu directory. Try 'make LIBCGETOPT=0'. Ignore any compile warnings.
You can check whether the new implementation of getopt is found first
in your path by calling 'bash test.bash'.
HIGHLIGHTS
@ -73,9 +29,3 @@ copy it, it is copyright (c) 1997-2005 by Frodo Looijaard
<frodo@frodo.looijaard.name>.
Files in the gnu directory are from glibc-2.0.4: copyright (C) 1987, 88,
89, 90, 91, 92, 93, 94, 95, 96, 97 Free Software Foundation, Inc.
DOWNLOADING
You can find the latest version of this program at:
http://software.frodo.looijaard.name/getopt/

View File

@ -8,16 +8,6 @@ Contrasting to the System V implementation, this one filters backspace
formatting sequences while searching, so you can comfortably search in nroff
output like manual pages.
This code uses routines as defined by SUSv2, so a glibc version of 2.1 or
higher is required on Linux. A curses implementation (like ncurses) must
be present as well.
If large files > 2GB are supported by the kernel and the C library, pg is
able to handle them.
Please send comments, bug-reports and especially bug-fixes to
<g-r@bigfoot.de> .
Gunnar Ritter
Freiburg i. Br.
Germany

View File

@ -7,16 +7,6 @@ domainname, hostid, cage and mesg.
Most of this software has been contributed by others, I basically just
ported the things to Linux.
About installation: See the bottom of this file. Check the Makefile!
Be sure you know what you are doing! You may well be able to lock
yourself out from your machine. Especially: The init provided here
(simpleinit) is NOT a SYSV compatible init and the inittab format
is different.
If you are uncertain whether you got the latest version, check out
ftp://ftp.daimi.aau.dk/pub/linux/poe/
Version 1.49 (20-Jun-97)
Small patches for new util-linux distribution and glibc compat.
PAM support in login.c by Erik Troan.
@ -484,32 +474,9 @@ login.c The login program. This is a portation of BSD login, first
to HP-UX 8.0 by Michael Glad (glad@daimi.aau.dk), and
to Linux (initially to 0.12) by me.
who.c A simple who(1) util. to list utmp. Done by me.
You may prefer the GNU who util. with more options
and features.
hostname.c A hostname(1) command to get and set the hostname. I did
this too.
domainname.c Like hostname, only reads out or sets the domainname.
agetty.c The getty program. From comp.sources.misc, by W.Z. Venema.
Hacked a bit by me.
simpleinit.c A simple init program, written by me. Uses /etc/inittab
A "kill -HUP" to init makes it re-read /etc/inittab.
A "kill -TSTP" to init makes it stop spawning gettys on the
ttys. A second "kill -TSTP" starts it again.
A kill -INT to init makes it attempt a reboot of the machine.
this works in connection with kernel support for softboot
when Ctrl-Alt-Del is pressed.
Init will start up in singleuser mode if /etc/singleboot
exists at boottime, or if it is given an argument of "single"
via eg. LILO. If /etc/securesingle exists it will ask for the
root password before starting single user.
write.c A write(1) command, used to pass messages between users
at different terminals. This code doubles as code for
a wall(1) command. Make a symlink: /usr/bin/wall ->
@ -518,56 +485,9 @@ write.c A write(1) command, used to pass messages between users
mesg A tiny shellscript, so you can avoid that other people write
to your shell.
users Another script that uses awk(1) and tr(1) to process the
output from who(1) into a one-liner.
If you don't have awk, but have Perl, this does the same:
who | perl -ane 'print "$F[0] "'; echo ""
pathnames.h:
Header.
param.h
Header, extended with getdtablesize() macro, should go
in /usr/include/sys
Building.
---------
A "make all" should do. At least it does for me.
Installation:
-------------
login should go in /bin, if you don't like this change
pathnames.h and recompile at least agetty.
getty, init Put them in SBINDIR
who, hostname, write, wall, mesg, users:
/usr/bin
securetty login needs this in /etc, defines which ttys that root
can login on. This should *never* include ttys{1,2}
inittab the simpleinit code needs this in /etc. Note that the syntax
of /etc/inittab has little to do with the syntax of a real
SysV inittab. Edit this one for your local setup.
shells The chsh program will use this if it's placed in /etc. It
defines the valid shell-programs. Have one abs. path on
each line.
You can also do a "make install" as root, but don't just do it because I
say so, check the Makefile first.
"Make install" will install only the new binaries, and not motd, inittab,
securetty and issue. To install these configuration files, do a
"make Install".
Getty requires a /dev/console to write errors to. I just made it a symlink
to /dev/tty1. Because of a bug in the tty driver this errorlogging may
cause the shell on tty1 to logout.
Getty will print the contents of /etc/issue if it's present before asking
for username. Login will print the contents of /etc/motd after successful
login. Login doesn't print /etc/motd, and doesn't check for mail if