LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

updated

This commit is contained in:
gferg 2000-11-15 14:39:53 +00:00
parent c7dd693edb
commit 98dcb653e8
7 changed files with 477 additions and 183 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

172
LDP/howto/docbook/Bootdisk-HOWTO.sgml
View File

@ -1,4 +1,3 @@
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
<Article Lang="en">
@ -17,7 +16,7 @@
<Copyright>
<Year>1995,1996,1997,1998,1999,2000</Year>
<Holder>Tom Fawcett.</Holder>
<Holder>Tom Fawcett</Holder>
</Copyright>
<Legalnotice>
@ -30,7 +29,7 @@
</Para>
</Legalnotice>
<Pubdate>v4.1, September 2000</Pubdate>
<Pubdate>v4.2, November 2000</Pubdate>
<Abstract>
<Para> This document describes how to design and build boot/root
@ -84,15 +83,12 @@
<Sect2><Title>Yet to do</Title>
<Para>
Any volunteers?
<Orderedlist>
<Listitem>
<Para>
Describe (or link to another document that describes) how to
create other bootable disk-like things, such as CDROMs, ZIP
disks and LS110 disks.
Describe how to create bootable LS110 disks.
</Para>
</Listitem>
@ -1008,8 +1004,9 @@ should contain is surprisingly small.
/bin/hostname Kangaroo
</Programlisting>
Be sure the directories are right. You don't really need to run
<Command>hostname</Command> &mdash; it just looks nicer if you do.
Be sure it is executable, and be sure any absolute filenames are
correct. You don't really need to run <Command>hostname</Command>
&mdash; it just looks nicer if you do.
</Para>
</Listitem>
@ -2340,6 +2337,142 @@ user through installation. It appears to use both a customized
</sect1>
<sect1><Title>Creating bootable CD-ROMs</Title>
<note>
<para>This section was contributed by Rizwan Mohammed Darwe
(<literal>rizwan AT clovertechnologies dot com</literal>)
</para>
</note>
<para>
This section assumes that you are familiar with the process and workings of
writing CDs in linux. Consider this to be a quick reference to include the
ability to boot the CD which you will burn. The CD-Writing-HOWTO should give you
an in-depth reference.
</para>
<sect2><title>What is El Torito?</title>
<para>
For the x86 platform, many BIOS's have begun to support bootable CDs.
The patches for mkisofs is based on the standard called "El Torito".
Simply put, El Torito is a specification that says how a cdrom should
be formatted such that you can directly boot from it.
</para>
<para>
The "El Torito" spec says that <emphasis>any</emphasis> cdrom drive should
work (SCSI or EIDE) as long as the BIOS supports El Torito. So far this has
only been tested with EIDE drives because none of the SCSI controllers that
has been tested so far appears to support El Torito. The motherboard
definately has to support El Torito. How do you if your motherboard supports
"El Torito"? Well, the ones that support lets you choose booting from HD,
Floppy, Network or CDROM.
</para>
</Sect2>
<Sect2>
<title>How it Works</title>
<para> The El Torito standard works by making the CD drive appear, through
BIOS calls, to be a normal floppy drive. This way you simply put any floppy
size image (exactly 1440k for a 1.44 meg floppy) somewhere in the ISO
filesystem. In the headers of the ISO fs you place a pointer to this image.
The BIOS will then grab this image from the CD and for all purposes it acts as
if it were booting from the floppy drive. This allows a working LILO boot
disk, for example, to simply be used as is. </para>
<para>Roughly speaking, the first 1.44 (or 2.88 if supported) Mbytes of the
CD-ROM contains a floppy-disk image supplied by you. This image is treated
like a floppy by the BIOS and booted from. (As a consequence, while booting
from this virtual floppy, your original drive A:
(<filename>/dev/fd0</filename>) may not be accessible, but you can try with
<filename>/dev/fd1</filename>). </para>
</Sect2>
<sect2><title>How to make it work</title>
<para>
First create a file, say "boot.img", which is an exact image of the bootable
floppy-disk which you want to boot via the CD-ROM. This must be an 1.44 MB
bootable floppy-disk. The command below will do this
<Screen>
dd if=/dev/fd0 of=boot.img bs=10k count=144
</Screen>
assuming the floppy is in the A: drive.
</para>
<para>
Place this image somewhere in the hierarchy which will be the source
for the iso9660 filesystem. It is a good idea to put all boot related
files in their own directory ("boot/" under the root of the iso9660 fs,
for example).
</para>
<para>
One caveat -- Your boot floppy <emphasis>must</emphasis> load any initial
ramdisk via LILO, not the kernel ramdisk driver! This is because once the
linux kernel starts up, the BIOS emulation of the CD as a floppy disk is
circumvented and will fail. LILO will load the initial ramdisk using BIOS
disk calls, so the emulation works as designed.
</para>
<para>
The El Torito specification requires a "boot catalog" to be created as
well. This is a 2048 byte file which is of no interest except it is required.
The patchwork done by the author of mkisofs will cause it to automatically
create the boot catalog, but you must specify where the boot catalog will go
in the iso9660 filesystem. Usually it is a good idea to put it in the same
place as the boot image, and a name like <filename>boot.catalog</filename>
seems appropriate.
</para>
<para>So we have our boot image in the file <filename>boot.img</filename>,
and we are going to put it in the directory <filename
class="directory">boot/</filename> under the root of the iso9660 filesystem.
We will have the boot catalog go in the same directory with the name
<filename>boot.catalog</filename>. The command to create the iso9660 fs in
the file <filename>bootcd.iso</filename> is then:
<screen>
mkisofs -r -b boot/boot.img -c boot/boot.catalog -o bootcd.iso .
</screen>
The <option>-b</option> option specifies the boot image to be used (note the
path is relative to the root of the iso9660 disk), and the <option>-c</option>
option is for the boot catalog file. The <option>-r</option> option will make
approptiate file ownerships and modes (see the <filename>mkisofs</filename>
manpage). The "." in the end says to take the source from the current
directory. </para>
<para>
Now burn the CD with the usual cdrecord command and it is ready to boot.
</para>
</sect2>
<sect2><title>Create Win9x Bootable CD-Roms</title>
<para>The first step is to get hold of the bootable image used by the source
CD. But you cannot simply mount the CD under linux and dd the first 1440k to
a floppy disk or to a file like <filename>boot.img</filename>. Instead you
simply boot with the source CD-ROM. </para>
<para>When you boot the Win98 CD you are dropped to A: prompt which is the
actual ramdisk. And D: or Z: is where all the installables are residing. By
using the diskcopy command of dos copy the A: image into the actual floppy
drive which is now B: The command below will do this.
<screen>
diskcopy A: B:
</screen>
It works just like dd. You can try booting from this newly created disk to
test if the booting process is similar to that of the source CD. Then the
usual dd of this floppy to a file like boot.img and then rest is as usual.
</para>
</sect2>
</sect1>
<sect1><title>Frequently Asked Question (FAQ) list</title>
<QandAset defaultlabel='qanda'>
@ -2944,25 +3077,6 @@ available on Metalab and mirrors.
</Sect1>
<Sect1><title>Linux FAQ and HOWTOs</title>
<para>
These are available from many sources. Look at the usenet newsgroups
<literal>news.answers</literal> and <literal>comp.os.linux.announce</literal>.
</para>
<para>
The FAQ is available from <ulink
url="http://linuxdoc.org/FAQ/Linux-FAQ.html">
http://linuxdoc.org/FAQ/Linux-FAQ.html</ulink>
and the HOWTOs from <ulink url="http://linuxdoc.org/HOWTO/HOWTO-INDEX.html">http://linuxdoc.org/HOWTO/HOWTO-INDEX.html</ulink>. Most documentation for
Linux may be found at <ulink url="http://linuxdoc.org/">The Linux
Documentation Project homepage</ulink>.
</para>
</Sect1>
<Sect1><Title>Ramdisk usage</title>
<Indexterm><Primary>ramdisk</Primary></Indexterm>
@ -3172,6 +3286,7 @@ Guide for an explanation of these.
</Appendix>
<Appendix id="Listings">
<Title>Sample root filesystem listings</title>
<Indexterm><Primary>root filesystem</Primary></Indexterm>
@ -3527,4 +3642,3 @@ lrwxrwxrwx 1 root root 5 Jul 29 21:35 vi &ndash;&#62; elvis
</Para>
</Appendix>
</Article>

2
LDP/howto/docbook/HOWTO-INDEX/adminSect.sgml
View File

@ -41,7 +41,7 @@ The Linux Bootdisk HOWTO</CiteTitle>
</Para>
<Para>
<CiteTitle>
Updated: September 2000</CiteTitle>.
Updated: November 2000</CiteTitle>.
How to design and build your own boot/root diskettes for Linux.
</Para>
</ListItem>

2
LDP/howto/docbook/HOWTO-INDEX/howtoChap.sgml
View File

@ -218,7 +218,7 @@ for bootable raid mounted on root using standard LILO. </Para>
Bootdisk-HOWTO</ULink>,
<CiteTitle>The Linux Bootdisk HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: September 2000</CiteTitle>.
<CiteTitle>Updated: November 2000</CiteTitle>.
How to design and build your own boot/root diskettes for Linux. </Para>
</ListItem>

2
LDP/howto/docbook/HOWTO-INDEX/osSect.sgml
View File

@ -431,7 +431,7 @@ host, and the usage of various process accounting commands</Para>
Bootdisk-HOWTO</ULink>,
<CiteTitle>The Linux Bootdisk HOWTO</CiteTitle>
</Para><Para>
<CiteTitle>Updated: September 2000</CiteTitle>.
<CiteTitle>Updated: November 2000</CiteTitle>.
How to design and build your own boot/root diskettes for Linux. </Para>
</ListItem>

199
LDP/howto/linuxdoc/FBB.sgml
View File

@ -2,12 +2,13 @@
<article>
<title>FBB packet-radio BBS mini-HOWTO
<title>FBB Packet-radio BBS mini-HOWTO
<author>Miroslav "Misko" Skoric, YT7MPB,
<tt/m.skoric@eunet.yu/
<date>v1.3, 12 November 2000
<date>v1.4, 15 November 2000
<abstract>
<nidx>linux!windows nt!amateur!packet!radio!modem!TNC</nidx>
<nidx>linux windows nt amateur packet radio</nidx>
This mini-HOWTO covers the installation and use of
the most popular amateur packet-radio BBS
software FBB. That software works under Linux, DOS
@ -87,58 +88,56 @@ LinFBB ...
be ok too (or any other GUI available).
<p>
<item>Download or get a copy of LinFBB (the main ftp site
<item>Download or copy LinFBB (the main ftp site
is <url url="http://ftp.f6fbb.org/" name=
"ftp.f6fbb.org"> but there are many mirror
sites too). For example, if you get a file
like <tscreen><verb>x700e_full.tgz</verb></tscreen>
it means that it is X11 version 7.00e and it
contains in a tgz archive all you need to install
contains all you need in tgz archive to install
the BBS. On the other hand, a name like
<tscreen><verb>xd700g_full.tgz</verb></tscreen>
means that it is <em>not</em> X11 but <em>daemon</em>
version 7.00g that is also complete to unpack. Further,
means that it is not X11 but daemon version 7.00g
and it is also complete to unpack. Further,
<tscreen><verb>x700f01.tgz</verb></tscreen>
and <tscreen><verb>x700g.tgz</verb></tscreen>
are "upgrades" to any previous "full" package.
<p>
<item>Copy the archive file in <filename id="directory">/tmp
</filename> directory.
<item>Copy the archive file in <bf>/tmp</bf> directory.
<p>
<item>You have to make a "base" directory where
your FBB will be installed. For example you
may type: <command>mkdir /usr/local/fbb</command> if you want
may type: <bf>mkdir /usr/local/fbb</bf> if you want
FBB to be there. You have to be logged as
'root' or 'superuser' to install FBB.
<p>
<item>Then, you should locate yourself in that
directory: <command>cd /usr/local/fbb</command>.
directory: <bf>cd /usr/local/fbb</bf>.
<p>
<item>Now, you should unpack the archive:
<command>tar xvzf /tmp/x700b25.tgz</command> (<-- use the right
<bf>tar xvzf /tmp/x700b25.tgz</bf> (<-- use the right
name of the archive here).
<p>
<item>When you finished unpacking the archive,
you may continue installing the software:
<command>./install.sh</command> is the command for that. The
<bf>./install.sh</bf> is the command for that. The
setup will ask you for the 'base' directory
where FBB will be installed. If you chose
<filename id="directory">/usr/local/fbb</filename> again,
you will be told that
<bf>/usr/local/fbb</bf> again, you will be told that
such directory already exists and all files
will be overwritten. It is ok, so you should
answer yes. If everything is ok, you should
see on the screen that fbb system
directories are created. At the beginning
of that procedure, program will ask you for
the BBS's callsign, name of the city, QTH
locator, your name etc. These details will
become a part of <filename>/usr/local/fbb/init.srv</filename>
bbs's callsign, name of the city, QTH
locator, your name etc. That details will
become a part of <bf>/usr/local/fbb/init.srv</bf>
file.
<p>
@ -150,30 +149,30 @@ LinFBB ...
<p>
<item>Well, so far - so good. After you have checked
all configuration files, you may start the
software: <command>./xfbb.sh</command> (<-- type this within
an <em>xterm</em> or something similar). When you
start FBB for the <em>first</em> time, it will ask
software: <bf>./xfbb.sh</bf> (<-- type this within
an xterm or something similar). When you
start FBB for the first time, it will ask
you to create some files it needs, so you
should answer "yes" to the questions.
</itemize>
<p>
<sect1>How to install LinFBB in addition to existing WinFBB
<sect1>How to install LinFBB beside WinFBB
<p>
<em>Notice: Folks, you see, at my place, I have a
dual-boot system, consisting of Windows NT and
Linux (each of them having their own partition(s)
and file system). I wanted to have 'independent'
operating systems that won't "see" each other. So, I
have made two partitions of NTFS type for NT. The
operating systems that won't see each other. So I
made two NT's partitions as NTFS partitions and
rest of the space used Linux as ext2 partitions.
Well, first I have installed WinFBB under NT and
LinFBB under Linux. Both of them worked, but there
was a big "problem": I could not share their
system files. You might say: So, what a big deal.
But, my FBB's should serve as a packet-radio forwarding
But, my FBB's should serve as packet-radio forwarding
stations (regardless of which one I boot at the
moment), so it was really needed for new LinFBB
to "know", for example, the position where WinFBB
@ -184,15 +183,15 @@ versa, of course).</em>
<itemize>
<item>Well, in order to allow both WinFBB under
Windows NT and LinFBB under Linux to share
their system files, it is needed to put those
Windows NT and LinFBB under Linux to use
some common files, it is needed to put these
files in a place both operating systems can
"see". So, I do that by re-installing
"see" them. So I do that by re-installing
WinFBB onto a FAT (FAT16) partition that is
recognized by NT and Linux. The best way to do
that is: a) to install a fresh copy of WinFBB on
a FAT partition and b) to copy the complete old
WinFBB from an NTFS partition over the fresh
seen by NT and Linux. The best way to do
that is to install a fresh copy of WinFBB on
a FAT partition and to copy complete old
WinFBB from NTFS partition over the fresh
installation (whenever you are asked to
rewrite existing files, you should answer
"yes").
@ -201,8 +200,8 @@ versa, of course).</em>
<item>When that is finished, you should have a "clone"
of the existing old WinFBB, but this time on
the FAT partition that is visible from under
Linux. Anyway, you should check if the "new"
installation might be properly run as earliere.
Linux. Anyway, you should check if the "new"
installation might be properly run as earlier.
<p>
<item>I could also recommended you to check the file
@ -241,73 +240,72 @@ versa, of course).</em>
<p>
<item>Mount a shared FAT directory:
<command>mount -t vfat /dev/hda2 /mnt/win </command>
<bf>mount -t vfat /dev/hda2 /mnt/win</bf>
(for example).
<p>
<item>Copy LinFBB archive to <filename id="directory">/tmp</filename> directory.
<item>Copy LinFBB archive to <bf>/tmp</bf> directory.
<p>
<item>Position yourself to the 'base' directory:
<command>cd /usr/local/fbb</command> (for example).
<bf>cd /usr/local/fbb</bf> (for example).
<p>
<item>Unpack the archive: <command>tar xvzf /tmp/filename</command>.
<item>Unpack the archive: <bf>tar xvzf /tmp/filename</bf>.
<p>
<item>Start the installation script <command>./install.sh</command>
and, after being asked for the 'base' installation
directory, chose <filename id="directory">/usr/local/fbb
</filename>. It doesn't matter if the program
warns you that such directory already exists so
existing files will be overwritten (by the way,
if you chose a mounted directory shared with NT,
many original WinFBB files, located there, would be
<item>Start the installation script <bf>./install.sh</bf>
and, after asked for the 'base' installation
directory, chose <bf>/usr/local/fbb</bf>. It doesn't
matter if the program warns you that such
directory already exists so existing files
will be overwritten (by the way, if you
choose a mounted directory shared with NT,
many original WinFBB files, located there, would be
over-written by LinFBB files, so after returning
to Windows, its WinFBB might be not functional
as before).
to Windows, WinFBB might not be functional
like before).
<p>
<item>Copy <filename>/usr/local/fbb</filename> to
<filename>/mnt/win/fbb</filename> but do
<item>Copy <bf>/usr/local/fbb</bf> to <bf>/mnt/win/fbb</bf> but do
*not* over-write existing files with the new files
having the same names.
<p>
<item>Copy <filename>/mnt/win/fbb/init_w.srv</filename> to a file
<filename>/mnt/win/fbb/init_l.srv</filename>
<item>Copy <bf>/mnt/win/fbb/init_w.srv</bf> to a file
<bf>/mnt/win/fbb/init_l.srv</bf>
<p>
<item>Edit <filename>/mnt/win/fbb/init_l.srv</filename> to that what is
needed for Linux and LinFBB. You may use the existing
file <filename>/mnt/win/fbb/init.srv</filename> as an example.
<item>Edit <bf>/mnt/win/fbb/init_l.srv</bf> to what is
needed for Linux. You may use the existing
file <bf>/mnt/win/fbb/init.srv</bf> as an example.
<p>
<item>Copy newly edited <filename>/mnt/win/fbb/init_l.srv</filename>
over the <filename>/mnt/win/fbb/init.srv</filename> (if you do
<item>Copy newly edited <bf>/mnt/win/fbb/init_l.srv</bf>
over the <bf>/mnt/win/fbb/init.srv</bf> (if you do
not do that, maybe you wouldn't be able to start LinFBB
using <command>./xfbb.sh</command>, like me).
using <bf>./xfbb.sh</bf>, like me).
<p>
<item>Copy <filename>/mnt/win/fbb/system/port_w.sys</filename> to
<filename>/mnt/win/fbb/system/port_l.sys</filename> file.
<item>Copy <bf>/mnt/win/fbb/system/port_w.sys</bf> to
<bf>/mnt/win/fbb/system/port_l.sys</bf> file.
<p>
<item>Edit <filename>/mnt/win/fbb/system/port_l.sys</filename> to
<item>Edit <bf>/mnt/win/fbb/system/port_l.sys</bf> to
what is needed for Linux and LinFBB. You may use the
existing file <filename>/mnt/win/fbb/system/port.sys</filename>
existing file <bf>/mnt/win/fbb/system/port.sys</bf>
as an example.
<p>
<item>Edit <filename>/mnt/win/fbb/xfbb.sh</filename> in order to fix
<item>Edit <bf>/mnt/win/fbb/xfbb.sh</bf> in order to fix
the right path.
<p>
<item>Ensure that you are in FBB's main directory:
<command>cd /mnt/win/fbb</command> (for example).
<bf>cd /mnt/win/fbb</bf> (for example).
<p>
<item>Start the script <command>./xfbb.sh</command> to run LinFBB.
<item>Start the script <bf>./xfbb.sh</bf> to run LinFBB.
If everything is ok, your LinFBB under Linux
should run with the same configuration as
your "old" WinFBB under Windows.
@ -331,7 +329,7 @@ haven't made a manual in english yet. I keep
trying to translate the original manuals
from spanish into english, but it is a hard
process. Any good 'spanish-to-english'
translator is welcomed to contact me:
translator is welcomed to contact me:
<htmlurl url="mailto:m.skoric@eunet.yu"
name="m.skoric@eunet.yu">.</em>
@ -378,11 +376,11 @@ Protus offers several interesting features:
for different BBS ports,
<p>
<item>Protus could be activated/deactivated at various
intervals of time using <filename>cron.sys</filename> system file,
<item>Protus could be activated/deactivated at various
intervals of time using CRON.SYS system file,
<p>
<item>Passwords could be managed remotely using an
<item>Passwords could be remotely managed, using an
external server, developed by Jose EB5IVB,
<p>
@ -401,12 +399,12 @@ radio BBS, using Protus type of <em>c_filter</em>:
<item>Users of Dos/WinFBB versions of Protus
already know that it is needed to create a new
directory <tt>\FBB\PROTUS</tt> where several *.PRT
directory <bf>\FBB\PROTUS</bf> where several *.PRT
files should be placed. In addition, the
main C_FILT*.DLL files should be copied
into <tt>\FBB\BIN</tt> as well as a couple of "system",
into <bf>\FBB\BIN</bf> as well as a couple of "system",
i.e. config *.PRT files that are going to be
within <tt>\FBB\SYSTEM</tt> directory.
within <bf>\FBB\SYSTEM</bf> directory.
<p>
<item>After the sysop has copied all files into
@ -421,7 +419,7 @@ radio BBS, using Protus type of <em>c_filter</em>:
information that are sent to users who
connect to the BBS). For your information,
I usualy don't care much about, because my
BBS's are, so called, "open systems". It means,
BBS's are so called "open systems". It means
they work quite normal for all users in the
same way as they worked before using Protus.
Only a couple of callsigns have password
@ -435,7 +433,7 @@ radio BBS, using Protus type of <em>c_filter</em>:
for Protus utility to be activated. In all
connections to your BBS (including console),
you should see a line like this: <bf>{PROTUS-4.0}</bf>
just after a line [FBB-7.00-AB1FHMRX$]. It
just after a line [[FBB-7.00-AB1FHMRX$]. It
only designates that Protus is active on the
system. Users of your system who don't have
their password, connect normally as before.
@ -449,7 +447,7 @@ radio BBS, using Protus type of <em>c_filter</em>:
of security: a fixed phrase as a password
(similar when you connect to the Internet
via telephone line, but this way the phrase
can be masqueraded within some longer answer);
can be masqueraded within the longer answer);
a changeable answer to the 5 numbers (just
like usual FBB sysop's password); a mode
that uses automatic answer from user's client
@ -475,19 +473,19 @@ radio BBS, using Protus type of <em>c_filter</em>:
and LinFBB under Linux (see also <tt>Linux+WinNT
mini-HOWTO</tt> and <tt>Lilo mini-HOWTO</tt>). That means
all Protus stuff has already been installed,
except Linux executable <filename>c_filter</filename> file.
I put that file into <tt>/fbb/bin</tt> directory and,
except Linux executable of <em>c_filter</em> file. I
put that file into <bf>/fbb/bin</bf> directory and,
after the next restart of LinFBB, I got the
info mentioned above: {PROTUS-4.0}. But the
password protection was not likely to work.
I was told to make a new directory <tt>/var/ax25/fbb/protus</tt>
I was told to make a new directory <bf>/var/ax25/fbb/protus</bf>
and put *.prt files there. I <em>didn't move</em> *.PRT
files from <tt>\FBB\PROTUS</tt> but <em>copied</em> them into
files from <bf>\FBB\PROTUS</bf> but <em>copied</em> them into
the new location, because I wanted Protus to
run further under WinFBB as before. The utility
still didn't want to run, unless I also copied
<em>also</em> *.PRT files from <tt>\FBB\SYSTEM</tt> to the
new location (<tt>/var/ax25/fbb/protus</tt>). After I
still didn't want to run, unless I copied
<em>also</em> *.PRT files from <bf>\FBB\SYSTEM</bf> to the
new location (<bf>/var/ax25/fbb/protus</bf>). After I
did that, Protus became functional.
<p>
@ -495,14 +493,14 @@ radio BBS, using Protus type of <em>c_filter</em>:
useful for those of you who intend to run
both Windows and Linux on the same machine.
For the majority of LinFBB-only users, it is just
important to make <tt>/var/local/fbb/protus</tt>
important to make <bf>/var/local/fbb/protus</bf>
where <em>all</em> *.prt files should be placed. <em>Only</em>
<filename>c_filter</filename> executable should go to <tt>/fbb/bin</tt>
c_filter executable should go to <bf>/fbb/bin</bf>
and that's it.
<p>
<item>About FBB-to-FBB protection: *both* partners
have to install Protus and the password for the
have to install Protus and password for the
forwarding partner's callsign must be the
same at *both* sides of the link. The versions
of Protus don't need to be the same (neither
@ -515,13 +513,13 @@ radio BBS, using Protus type of <em>c_filter</em>:
<p>
<item>One of the interesting features of Protus is to
log unsuccessful connections and other errors. Due to the
<em>different</em> locations of <filename>*.prt</filename>
files here, I have separate logs for WinFBB and LinFBB.
Those of you who are going to run only one version of
FBB, will have <em>one</em> complete log of all
log unsuccessful connections. Due to the
<em>different</em> locations of *.prt files here, I have
separate logs for WinFBB and LinFBB. Those of
you who are going to run only one version of
FBB, will have <em>one</em> complete log of connection
errors, your users make when they try
connecting your BBS.
connecting your BBS.
<p>
<item>As it was told earlier, if you implemented
@ -529,17 +527,18 @@ radio BBS, using Protus type of <em>c_filter</em>:
users (but not for all of them who connect
normally) - your system is considered as
an "open" one. It means that will be logged
only these unsuccessful tries to enter the system
by "protected" callsigns. But, if you have decided
that your BBS is to be accessed by <em>only</em> those
only unsuccessful tries to enter the system
by "protected" callsigns. But, if you decided
that your BBS can be accessed by <em>only</em> those
callsigns who are protected with Protus, it
means that your system is considered as the "closed" one.
Then, there is no way that other users (without passwords
given) could enter your FBB. Any unauthorized try to
connect your BBS is also logged. In addition,
means that your system is the "closed" one.
Then, there is no way a user could enter your
FBB unless its callsign has given a password
within your Protus. Any unauthorized try to
connect your BBS is logged. In addition,
you may decide to have a "guest" access or
a "read-only" as <em>default</em> for some ports and/or
for those users who enter the wrong password.
a "read-only" as <em>default</em> for some ports
and/or for users who enter the wrong password.
Many combinations are possible. You could
even password protect your own FBB console!

255
LDP/howto/linuxdoc/LILO.sgml
View File

@ -4,7 +4,7 @@
<title>Lilo mini-HOWTO
<author>Miroslav "Misko" Skoric, <tt/m.skoric@eunet.yu/
<date>v3.3, 12 November 2000
<date>v3.4, 15 November 2000
<abstract>
<nidx>linux loader windows nt boot</nidx>
LILO is the most used <bf/Li/nux <bf/Lo/ader for the x86 flavour of
@ -20,11 +20,13 @@ of this document)
<p>
This version of Lilo mini-HOWTO is based on work of Cameron Spitzer
(<tt/cls@truffula.sj.ca.us/) and Alessandro Rubini (<tt/rubini@linux.it/).
There is also a contribution from Tony Harris (<tt/tony@nmr.mgh.harvard.edu/)
(<tt>cls@truffula.sj.ca.us</tt>) and Alessandro Rubini
(<tt>rubini@linux.it</tt>). There is also a contribution from Tony Harris
(<tt>tony@nmr.mgh.harvard.edu</tt>).
</abstract>
<sect>Introduction
<p>
@ -58,11 +60,12 @@ installations:
</itemize>
<p>
The last three examples are by Cameron, <tt/cls@truffula.sj.ca.us/>,
who wrote the original document. Alessandro <tt/rubini@linux.it/>
The last three examples are by Cameron, <tt>cls@truffula.sj.ca.us</tt>,
who wrote the original document. Alessandro <tt>rubini@linux.it</tt>
doesn't run anything but Linux, so he can't check
nor update them by himself. Needless to say, any feedback is welcome.
<sect>Background Information and Standard Installation
<p>
@ -73,7 +76,7 @@ kernel must live in some place that can be accessed by the bios.
<p>
At boot time, Lilo is not able to read filesystem data, and any
pathname you put in <tt>/etc/lilo.conf</tt> is resolved at
installation time (when you invoke <command>/sbin/lilo</command>). Installation
installation time (when you invoke <bf>/sbin/lilo</bf>). Installation
time is when the program builds the tables that list which sectors are
used by the files used to load the operating system. As a consequence,
all of these files must live in a partition that can be accessed by
@ -83,7 +86,7 @@ system needs to be accessed via the BIOS).
<p>
Another consequence of being BIOS-based is that you must reinstall the
loader (i.e., you must reinvoke <command>/sbin/lilo</command>) any time you
loader (i.e., you must reinvoke <bf>/sbin/lilo</bf>) any time you
modify the Lilo setup. Whenever you recompile your kernel and
overwrite your old image you must reinstall Lilo.
@ -100,8 +103,8 @@ or <tt>/dev/hda2</tt>).
If you have another operating system installed in your hard drive,
you'd better install Lilo to the root partition instead of the MBR. In
this case, you must mark the partition as ``bootable'' using the ``a''
command of <command>fdisk</command> or the ``b'' command of <command>cfdisk
</command>. If you don't overwrite the master boot sector you'll find it
command of <bf>fdisk</bf> or the ``b'' command of <bf>cfdisk</bf>.
If you don't overwrite the master boot sector you'll find it
easier to uninstall Linux and Lilo if needed.
<p>
@ -132,7 +135,7 @@ more. All recent Lilo distribution are able to deal with LBA and LARGE
disk settings.
<p>
Note that the "<tt/linear/" keyword in <tt>/etc/lilo.conf</tt> can
Note that the <tt>"linear"</tt> keyword in <tt>/etc/lilo.conf</tt> can
help in dealing with geometry problems. The keyword instructs Lilo to
use linear sector addresses instead of sector/head/cylinder tuples.
Conversion to 3D addresses is delayed to run-time, therefore making
@ -148,9 +151,9 @@ in my computers, but I never touch the BIOS configuration.
<sect1>How Can I Interact at Boot Time?
<p>
When you see the Lilo prompt, you can hit the &lt;Tab&gt; key to show
When you see the Lilo prompt, you can hit the &lt;Tab&gt; key to show
the list of possible choices. If Lilo is not configured to be
interactive, press and hold the &lt;Alt&gt; or &lt;Shift&gt; key
interactive, press and hold the &lt;Alt&gt; or &lt;Shift&gt; key
before the ``LILO'' message appears.
<p>
@ -163,20 +166,20 @@ important and worth describing here:
<itemize>
<item><tt/root=/: you can tell the Linux kernel to mount as root
a different partition than the one appearing in <tt/lilo.conf/.
<item><tt>root=</tt>: you can tell the Linux kernel to mount as root
a different partition than the one appearing in <tt>/lilo.conf</tt>.
For example, my system has a tiny partition hosting a minimal Linux
installation, and I've been able to boot the system after
destroying my root partition by mistake.
<item><tt/init=/: version 1.3.43 and newer of the Linux kernel can
execute another command instead of <command>/sbin/init</command>,
<item><tt>init=</tt>: version 1.3.43 and newer of the Linux kernel can
execute another command instead of <bf>/sbin/init</bf>,
as specified on the command line. If you experience bad problems
during the boot process, you can access the bare system by
specifying <tt>init=/bin/sh</tt> (when you are at the shell
prompt you most likely will need to mount your disks: try
``<command>mount -w -n -o remount /; mount -a</command>'',
and remember to ``<command>umount -a</command>'' before turning off
``<bf>mount -w -n -o remount /; mount -a</bf>'',
and remember to ``<bf>umount -a</bf>'' before turning off
the computer).
<item>A number: by specifying a number on the kernel command line, you
@ -193,8 +196,8 @@ important and worth describing here:
When Lilo overwrites a boot sector, it saves a backup copy in
<tt>/boot/boot.</tt><em/xxyy/, where <em/xxyy/ are the major and minor
numbers of the device, in hex. You can see the major and minor numbers
of your disk or partition by running ``<command>ls -l
/dev/<em>/device</em></command>''. For example, the first sector of
of your disk or partition by running ``<bf>ls -l
/dev/<em>/device</em></bf>''. For example, the first sector of
<tt>/dev/hda</tt> (major 3, minor 0) will be saved in
<tt>/boot/boot.0300</tt>, installing Lilo on <tt>/dev/fd0</tt> creates
<tt>/boot/boot.0200</tt> and installing on <tt>/dev/sdb3</tt> (major
@ -208,28 +211,28 @@ are always the snapshot of the situation before installing any Lilo.
If you ever need to uninstall Lilo (for example, in the unfortunate
case you need to uninstall Linux), you just need to restore the
original boot sector. If Lilo is installed in <tt>/dev/hda</tt>, just
do ``<command>dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1</command>''
(I personally just do ``<command>cat /boot/boot.0300 > /dev/hda</command>'',
do ``<bf>dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1</bf>''
(I personally just do ``<bf>cat /boot/boot.0300 > /dev/hda</bf>'',
but this is not safe, as this will restore the original partition table as
well, which you might have modified in the meanwhile). This command is
much easier to run than trying ``<command>fdisk /mbr</command>'' from a DOS
much easier to run than trying ``<bf>fdisk /mbr</bf>'' from a DOS
shell: it allows you to cleanly remove Linux from a disk without ever
booting anything but Linux. After removing Lilo remember to run Linux'
<command>fdisk</command> to destroy any Linux partition (DOS' <command>fdisk
</command> is unable to remove non-dos partitions).
<bf>fdisk</bf> to destroy any Linux partition (DOS' <bf>fdisk
</bf> is unable to remove non-dos partitions).
<p>
If you installed Lilo on your root partition (e.g., <tt>/dev/hda2</tt>),
nothing special needs to be done to uninstall Lilo. Just run Linux'
<command>fdisk</command> to remove Linux partitions from the partition
<bf>fdisk</bf> to remove Linux partitions from the partition
table. You must also mark the DOS partition as bootable.
<sect1>How to make a ram disk?
<p>
<em>Notice: If you find the next section hard to read, you may also look for
the web page: http://surfer.nmr.mgh.harvard.edu/partition/ramdisk.html where
you would find the original of the contributed section.
the web page: <tt>http://surfer.nmr.mgh.harvard.edu/partition/ramdisk.html</tt>
where you would find the original of the contributed section.
</em>
<p>
@ -246,14 +249,16 @@ as a module very early in the boot cycle.
There are only two easy steps:
<itemize>
<item>make a ram disk image with <command>/mkinitrd</command>
<item>make a ram disk image with <bf>/mkinitrd</bf>
<item>modify <tt>lilo.conf</tt> to point to the image
</itemize>
First, I <command>cd</command> over to <tt//boot/:
First, I <bf>cd</bf> over to <tt>/boot</tt>:
<p>
<verb>
System.map chain.b module-info-2.2.16-3ext3
System.map-2.2.16-3 initrd-2.2.16-3.img vmlinux-2.2.16-3
System.map-2.2.16-3ext3 vmlinux-2.2.16-3ext3
@ -261,7 +266,7 @@ vmlinuz kernel.h
boot.b map vmlinuz-2.2.16-3
bz.2.2.15.juke.Image module-info vmlinuz-2.2.16-3ext3
bzImage-2.2.14 module-info-2.2.16-3
</verb>
<p>
Here you can see that I have a 2.2.16-3 kernel and I have added a
@ -271,15 +276,15 @@ already a ram disk image for my first kernel (<tt/initrd-2.2.16-3.img/)
To make a new image for the second kernel, I type the following (stuff I
type is in bold):
boot#<command>mkinitrd initrd-2.2-16-3ext3.img 2.2.16-3ext3</command>
boot# <bf>mkinitrd initrd-2.2-16-3ext3.img 2.2.16-3ext3</bf>
<tt/mkinitrd/ is a shellscript that looks at the modules needed by my
kernel, then makes an ext2 filesystem containing them.
If we look inside the image we see this is the case:
boot#<command>cat initrd-2.2.16-3ext3.img | gunzip > /tmp/myimage</command>
boot# <bf>cat initrd-2.2.16-3ext3.img | gunzip > /tmp/myimage</bf>
boot#<command>file /tmp/myimage</command>
boot# <bf>file /tmp/myimage</bf>
/tmp/myimage: Linux/i386 ext2 filesystem/
@ -291,13 +296,13 @@ image is provided for pedagogic purposes.
In order to look inside, I need to mount the image as though it were
a filesystem:
boot#<command>mount /tmp/myimage /mnt/tmp -t ext2 -o loop=/dev/loop3</command>
boot# <bf>mount /tmp/myimage /mnt/tmp -t ext2 -o loop=/dev/loop3</bf>
boot#<command>ls /mnt/tmp</command>
boot# <bf>ls /mnt/tmp</bf>
<tt/bin dev etc lib linuxrc/
boot#<command>find /mnt/tmp</command>
boot# <bf>find /mnt/tmp</bf>
<tt//mnt/tmp/
@ -333,12 +338,12 @@ boot#<command>find /mnt/tmp</command>
<tt//mnt/tmp/linuxrc/
The most important part of this ram disk image is (<tt/aic7xxx.o/,
The most important part of this ram disk image is <tt/aic7xxx.o/,
which is my scsi module.
Finally, I move on to the last step, modifying (<tt//etc/lilo.conf/:
Finally, I move on to the last step, modifying <tt//etc/lilo.conf/:
Here is my entry in (<tt/lilo.conf/ that corresponds to the kernel and
Here is my entry in <tt/lilo.conf/ that corresponds to the kernel and
image I just created:
<tt/image=/boot/vmlinuz-2.2.16-3ext3/
@ -351,12 +356,12 @@ image I just created:
<tt/root=/dev/hdb3/
That's it. Run <command>/lilo</command> as root and reboot.
That's it. Run <bf>/lilo</bf> as root and reboot.
<p>
If you have problems, check out the kernel <tt/HOWTO/. There are a
couple things you need to have covered: you need your kernel modules
compiled and living in (<tt//etc/conf.modules/.
compiled and living in <tt>/etc/conf.modules</tt>.
<sect>The Simple Configuration
@ -549,6 +554,7 @@ disk = /dev/sda
bios = 0x80
</verb>
<sect>Using Lilo When the BIOS Can't See the Root Partition
<p>
@ -607,6 +613,7 @@ other = /dev/hda1
alias = m
</verb>
<sect>Accessing Huge Disks When the BIOS Can't
<p>
@ -686,6 +693,7 @@ the precompiled Slackware kernel. Eventually, IBM sent me an
me Linux is broken because Linux doesn't use BIOS. I gave their
diskette away.
<sect>Booting from a Rescue Floppy
<p>
@ -754,6 +762,7 @@ other = /dev/sda1
With this modification MSDOS-6.2 runs, and it thinks it is on C: and
Windows-95 is on D:.
<sect>Further Information
<p>
@ -822,7 +831,7 @@ You are strongly recommended to take a backup of
your system before major installation and backups
at regular intervals.
<sect1>Other Sources of Information
<sect1>News
<p>
In addition to the Lilo docs, there are a number
@ -864,4 +873,164 @@ email address:
<htmlurl url="mailto:m.skoric@eunet.yu"
name="m.skoric@eunet.yu">.
<sect1>HOWTO
<p>
<nidx>disk!information resources!HOWTOs</nidx>
These are intended as the primary starting points to
get the background information as well as show you how to solve
a specific problem.
Some relevant HOWTOs are <tt/Bootdisk/, <tt/Installation/, <tt/SCSI/ and <tt/UMSDOS/.
The main site for these is the
<url url="http://metalab.unc.edu/LDP/"
name="LDP archive">
at Metalab (formerly known as Sunsite).
<sect1>Mini-HOWTO
<p>
<nidx>disk!information resources!mini-HOWTOs</nidx>
These are the smaller free text relatives to the HOWTOs.
Some relevant mini-HOWTOs are
<tt/Backup-With-MSDOS/, <tt/Diskless/, <tt/LILO/, <tt/Large Disk/,
<tt/Linux+DOS+Win95+OS2/, <tt/Linux+OS2+DOS/, <tt/Linux+Win95/,
<tt/Linux+WinNT/, <tt/Linux+NT-Loader/, <tt/NFS-Root/, <tt/Win95+Win+Linux/,
<tt/ZIP Drive/, <tt/FBB packet-radio BBS/.
You can find these at the same place as the HOWTOs, usually in a sub directory
called <tt/mini/. Note that these are scheduled to be converted into SGML and
become proper HOWTOs in the near future.
<sect1>Local Resources
<p>
<nidx>disk!information resources!local</nidx>
In most distributions of Linux there is a document directory installed,
have a look in the
<htmlurl url="file:///usr/doc"
name="/usr/doc"> directory.
where most packages store their main documentation and README files etc.
Also you will here find the HOWTO archive (
<htmlurl url="file:///usr/doc/HOWTO"
name="/usr/doc/HOWTO">)
of ready formatted HOWTOs
and also the mini-HOWTO archive (
<url url="file:///usr/doc/HOWTO/mini"
name="/usr/doc/HOWTO/mini">)
of plain text documents.
Many of the configuration files mentioned earlier can be found in the
<htmlurl url="file:///etc"
name="/etc">
directory. In particular you will want to work with the
<htmlurl url="file:///etc/fstab"
name="/etc/fstab">
file that sets up the mounting of partitions
and possibly also
<htmlurl url="file:///etc/mdtab"
name="/etc/mdtab">
file that is used for the <tt/md/ system to set up RAID.
The kernel source in
<url url="file:///usr/src/linux"
name="/usr/src/linux">
is, of course, the ultimate documentation. In other
words, <em>use the source, Luke</em>.
It should also be pointed out that the kernel comes not only with
source code which is even commented (well, partially at least)
but also an informative
<url url="file:///usr/src/linux/Documentation"
name="documentation directory">.
If you are about to ask any questions about the kernel you should
read this first, it will save you and many others a lot of time
and possibly embarrassment.
Also have a look in your system log file (
<htmlurl url="file:///var/log/messages"
name="/var/log/messages">)
to see what is going on and in particular how the booting went if
too much scrolled off your screen. Using <tt>tail -f /var/log/messages</tt>
in a separate window or screen will give you a continuous update of what is
going on in your system.
You can also take advantage of the
<htmlurl url="file:///proc"
name="/proc">
file system that is a window into the inner workings of your system.
Use <tt/cat/ rather than <tt/more/ to view the files as they are
reported as being zero length. Reports are that <tt/less/ works well here.
<sect1>Web Pages
<p>
<nidx>disk!information resources!WWW</nidx>
<nidx>disk!information resources!web pages</nidx>
There is a huge number of informative web pages out there and by their very
nature they change quickly so don't be too surprised if these links become
quickly outdated.
A good starting point is of course the
<url url="http://www.linuxdoc.org/"
name="Linux Documentation Project"> home page,
an information central for documentation, project pages and much, much more.
Please let me know if you have any other leads that can be of interest.
<sect>GETTING HELP
<p>
<nidx>(your index root)!assistance, obtaining</nidx>
In the end you might find yourself unable to solve your problems and need
help from someone else. The most efficient way is either to ask someone
local or in your nearest Linux user group, search the web for the nearest
one.
Another possibility is to ask on Usenet News in one of the many, many
newsgroups available. The problem is that these have such a high
volume and noise (called low signal-to-noise ratio) that your question
can easily fall through unanswered.
No matter where you ask it is important to ask well or you will not be
taken seriously. Saying just <it/my disk does not work/ is not going
to help you and instead the noise level is increased even further and if
you are lucky someone will ask you to clarify.
Instead describe your problems in some detail that
will enable people to help you. The problem could lie somewhere you did
not expect. Therefore you are advised to list up the following information
on your system:
<descrip>
<tag/Hardware/
<itemize>
<item>Processor
<item>DMA
<item>IRQ
<item>Chip set (LX, BX etc)
<item>Bus (ISA, VESA, PCI etc)
<item>Expansion cards used (Disk controllers, video, IO etc)
</itemize>
<tag/Software/
<itemize>
<item>BIOS (On motherboard and possibly SCSI host adapters)
<item>LILO, if used
<item>Linux kernel version as well as possible modifications and patches
<item>Kernel parameters, if any
<item>Software that shows the error (with version number or date)
</itemize>
<tag/Peripherals/
<itemize>
<item>Type of disk drives with manufacturer name, version and type
<item>Other relevant peripherals connected to the same busses
</itemize>
</descrip>
Remember that booting text is logged to <tt>/var/log/messages</tt> which can
answer most of the questions above. Obviously if the drives fail you might not
be able to get the log saved to disk but you can at least scroll back up the
screen using the <tt/SHIFT/ and <tt/PAGE UP/ keys. It may also be useful to
include part of this in your request for help but do not go overboard, keep
it <em/brief/ as a complete log file dumped to Usenet News is more than a
little annoying.
</article>

28
LDP/howto/linuxdoc/Linux+WinNT.sgml
View File

@ -4,7 +4,7 @@
<title>Linux+WindowsNT mini-HOWTO
<author>Miroslav Skoric, <tt/m.skoric@eunet.yu/
<date>v2.4, 12 November 2000
<date>v2.5, 15 November 2000
<abstract>
<nidx>linux loader windows nt boot</nidx>
This mini-HOWTO covers some ways on how to install both Linux
@ -73,7 +73,7 @@ this mini-HOWTO, has been using:
<p>
2. Edit <tt>/etc/lilo.conf</tt> and use <bf>boot=/dev/sda</bf> (I
was not successful
at installing LILO on the Linux partition--/dev/sda3 in my case) and
at installing LILO on the Linux partition--<tt>/dev/sda3</tt> in my case) and
run "lilo". You'll have to use the editor ae. You'll live.
<p>
@ -88,14 +88,13 @@ this mini-HOWTO, has been using:
<p>
5. Add NT stanza to /etc/lilo.conf, e.g.:
<verb><tt>
<verb>
other=/dev/sda1
label=NT
table=/dev/sda
</tt><verb>
</verb>
<p>
and run lilo. If lilo complains about this (I forget the message),
add the "linear" flag to /etc/lilo.conf near the "compact" keyword.
Furthermore, if your partition table is screwed up by NT you'll
@ -115,20 +114,27 @@ this mini-HOWTO, has been using:
still have this error on the NT partition though, but this seems to
be OK.
<p>
<p>
<verb>
/dev/sda1 1 1 322 329301 6 DOS 16-bit >=32M
</verb>
<p>
Partition 1 does not end on cylinder boundary:
<p>
phys=(321, 39, 9) should be (321, 63, 32)
<p>
Cfdisk reports strangeness, but it seems OK:
<verb>
Unusable 0.04*
/dev/sda1 Primary DOS 16-bit >=32Mb 321.59*
Unusable 0.39*
</verb>
<p>
If you do get the cylinder boundary warning on your Linux
partitions, it is sufficient to use cfdisk to do something innocuous
@ -141,9 +147,11 @@ Partition 1 does not end on cylinder boundary:
previously. Clear and restore the MBR (but not the signature) with:
<p>
<verb>
dd if=/dev/zero of=/dev/sda bs=512 count=1
dd if=/dev/fd0 of=/dev/sda bs=510 count=1
</verb>
<p>
8. Install the rest of Linux. Easy, huh?
@ -153,15 +161,19 @@ Partition 1 does not end on cylinder boundary:
<itemize>
<p>
<item>dd if=/dev/zero of=/dev/sda bs=446 count=1 (in Linux) or perform
a low-level format with the SCSI utilities. I've heard that a
low-level format of an IDE disk is fatal, so don't do it.
<p>
<item>fdisk /mbr (you've obviously already created a DOS boot
disk that contains fdisk).
<p>
<item>delete NT partition and create it again in NT install.
<p>
<item>continue with NT install.
</itemize>