-linux!windows nt!amateur!packet!radio!modem!TNC
+linux windows nt amateur packet radio
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).
-- Download or get a copy of LinFBB (the main ftp site
+
- Download or copy LinFBB (the main ftp site
is but there are many mirror
sites too). For example, if you get a file
like x700e_full.tgz
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
xd700g_full.tgz
- means that it is not X11 but daemon
- 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,
x700f01.tgz
and x700g.tgz
are "upgrades" to any previous "full" package.
-- Copy the archive file in /tmp
- directory.
+
- Copy the archive file in /tmp directory.
- You have to make a "base" directory where
your FBB will be installed. For example you
- may type: mkdir /usr/local/fbb if you want
+ may type: mkdir /usr/local/fbb if you want
FBB to be there. You have to be logged as
'root' or 'superuser' to install FBB.
- Then, you should locate yourself in that
- directory: cd /usr/local/fbb.
+ directory: cd /usr/local/fbb.
- Now, you should unpack the archive:
- tar xvzf /tmp/x700b25.tgz (<-- use the right
+ tar xvzf /tmp/x700b25.tgz (<-- use the right
name of the archive here).
- When you finished unpacking the archive,
you may continue installing the software:
- ./install.sh is the command for that. The
+ ./install.sh is the command for that. The
setup will ask you for the 'base' directory
where FBB will be installed. If you chose
- /usr/local/fbb again,
- you will be told that
+ /usr/local/fbb 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 /usr/local/fbb/init.srv
+ bbs's callsign, name of the city, QTH
+ locator, your name etc. That details will
+ become a part of /usr/local/fbb/init.srv
file.
@@ -150,30 +149,30 @@ LinFBB ...
- Well, so far - so good. After you have checked
all configuration files, you may start the
- software: ./xfbb.sh (<-- type this within
- an xterm or something similar). When you
- start FBB for the first time, it will ask
+ software: ./xfbb.sh (<-- 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.
-How to install LinFBB in addition to existing WinFBB
+How to install LinFBB beside WinFBB
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).
- 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).
- 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.
- I could also recommended you to check the file
@@ -241,73 +240,72 @@ versa, of course).
- Mount a shared FAT directory:
- mount -t vfat /dev/hda2 /mnt/win
+ mount -t vfat /dev/hda2 /mnt/win
(for example).
-- Copy LinFBB archive to /tmp directory.
+
- Copy LinFBB archive to /tmp directory.
- Position yourself to the 'base' directory:
- cd /usr/local/fbb (for example).
+ cd /usr/local/fbb (for example).
-- Unpack the archive: tar xvzf /tmp/filename.
+
- Unpack the archive: tar xvzf /tmp/filename.
-- Start the installation script ./install.sh
- and, after being asked for the 'base' installation
- directory, chose /usr/local/fbb
- . 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
+
- Start the installation script ./install.sh
+ and, after asked for the 'base' installation
+ directory, chose /usr/local/fbb. 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).
-- Copy /usr/local/fbb to
- /mnt/win/fbb but do
+
- Copy /usr/local/fbb to /mnt/win/fbb but do
*not* over-write existing files with the new files
having the same names.
-- Copy /mnt/win/fbb/init_w.srv to a file
- /mnt/win/fbb/init_l.srv
+
- Copy /mnt/win/fbb/init_w.srv to a file
+ /mnt/win/fbb/init_l.srv
-- Edit /mnt/win/fbb/init_l.srv to that what is
- needed for Linux and LinFBB. You may use the existing
- file /mnt/win/fbb/init.srv as an example.
+
- Edit /mnt/win/fbb/init_l.srv to what is
+ needed for Linux. You may use the existing
+ file /mnt/win/fbb/init.srv as an example.
-- Copy newly edited /mnt/win/fbb/init_l.srv
- over the /mnt/win/fbb/init.srv (if you do
+
- Copy newly edited /mnt/win/fbb/init_l.srv
+ over the /mnt/win/fbb/init.srv (if you do
not do that, maybe you wouldn't be able to start LinFBB
- using ./xfbb.sh, like me).
+ using ./xfbb.sh, like me).
-- Copy /mnt/win/fbb/system/port_w.sys to
- /mnt/win/fbb/system/port_l.sys file.
+
- Copy /mnt/win/fbb/system/port_w.sys to
+ /mnt/win/fbb/system/port_l.sys file.
-- Edit /mnt/win/fbb/system/port_l.sys to
+
- Edit /mnt/win/fbb/system/port_l.sys to
what is needed for Linux and LinFBB. You may use the
- existing file /mnt/win/fbb/system/port.sys
+ existing file /mnt/win/fbb/system/port.sys
as an example.
-- Edit /mnt/win/fbb/xfbb.sh in order to fix
+
- Edit /mnt/win/fbb/xfbb.sh in order to fix
the right path.
- Ensure that you are in FBB's main directory:
- cd /mnt/win/fbb (for example).
+ cd /mnt/win/fbb (for example).
-- Start the script ./xfbb.sh to run LinFBB.
+
- Start the script ./xfbb.sh 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:
.
@@ -378,11 +376,11 @@ Protus offers several interesting features:
for different BBS ports,
-- Protus could be activated/deactivated at various
- intervals of time using cron.sys system file,
+
- Protus could be activated/deactivated at various
+ intervals of time using CRON.SYS system file,
-- Passwords could be managed remotely using an
+
- Passwords could be remotely managed, using an
external server, developed by Jose EB5IVB,
@@ -401,12 +399,12 @@ radio BBS, using Protus type of c_filter:
- Users of Dos/WinFBB versions of Protus
already know that it is needed to create a new
- directory \FBB\PROTUS where several *.PRT
+ directory \FBB\PROTUS where several *.PRT
files should be placed. In addition, the
main C_FILT*.DLL files should be copied
- into \FBB\BIN as well as a couple of "system",
+ into \FBB\BIN as well as a couple of "system",
i.e. config *.PRT files that are going to be
- within \FBB\SYSTEM directory.
+ within \FBB\SYSTEM directory.
- After the sysop has copied all files into
@@ -421,7 +419,7 @@ radio BBS, using Protus type of c_filter:
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 c_filter:
for Protus utility to be activated. In all
connections to your BBS (including console),
you should see a line like this: {PROTUS-4.0}
- 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 c_filter:
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 c_filter:
and LinFBB under Linux (see also Linux+WinNT
mini-HOWTO and Lilo mini-HOWTO). That means
all Protus stuff has already been installed,
- except Linux executable c_filter file.
- I put that file into /fbb/bin directory and,
+ except Linux executable of c_filter file. I
+ put that file into /fbb/bin 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 /var/ax25/fbb/protus
+ I was told to make a new directory /var/ax25/fbb/protus
and put *.prt files there. I didn't move *.PRT
- files from \FBB\PROTUS but copied them into
+ files from \FBB\PROTUS but copied 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
- also *.PRT files from \FBB\SYSTEM to the
- new location (/var/ax25/fbb/protus). After I
+ still didn't want to run, unless I copied
+ also *.PRT files from \FBB\SYSTEM to the
+ new location (/var/ax25/fbb/protus). After I
did that, Protus became functional.
@@ -495,14 +493,14 @@ radio BBS, using Protus type of c_filter:
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 /var/local/fbb/protus
+ important to make /var/local/fbb/protus
where all *.prt files should be placed. Only
- c_filter executable should go to /fbb/bin
+ c_filter executable should go to /fbb/bin
and that's it.
- 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 c_filter:
- One of the interesting features of Protus is to
- log unsuccessful connections and other errors. Due to the
- different 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 one complete log of all
+ log unsuccessful connections. Due to the
+ different 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 one complete log of connection
errors, your users make when they try
- connecting your BBS.
+ connecting your BBS.
- As it was told earlier, if you implemented
@@ -529,17 +527,18 @@ radio BBS, using Protus type of c_filter:
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 only those
+ only unsuccessful tries to enter the system
+ by "protected" callsigns. But, if you decided
+ that your BBS can be accessed by only 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 default for some ports and/or
- for those users who enter the wrong password.
+ a "read-only" as default 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!
diff --git a/LDP/howto/linuxdoc/LILO.sgml b/LDP/howto/linuxdoc/LILO.sgml
index ba4c4c85..8f366be8 100644
--- a/LDP/howto/linuxdoc/LILO.sgml
+++ b/LDP/howto/linuxdoc/LILO.sgml
@@ -4,7 +4,7 @@
Lilo mini-HOWTO
Miroslav "Misko" Skoric, v3.3, 12 November 2000
+v3.4, 15 November 2000
linux loader windows nt boot
LILO is the most used
This version of Lilo mini-HOWTO is based on work of Cameron Spitzer
-(cls@truffula.sj.ca.us) and Alessandro Rubini
+(rubini@linux.it). There is also a contribution from Tony Harris
+(tony@nmr.mgh.harvard.edu).
+
Introduction
@@ -58,11 +60,12 @@ installations:
-The last three examples are by Cameron, ,
-who wrote the original document. Alessandro
+The last three examples are by Cameron, cls@truffula.sj.ca.us,
+who wrote the original document. Alessandro rubini@linux.it
doesn't run anything but Linux, so he can't check
nor update them by himself. Needless to say, any feedback is welcome.
+
Background Information and Standard Installation
@@ -73,7 +76,7 @@ kernel must live in some place that can be accessed by the bios.
At boot time, Lilo is not able to read filesystem data, and any
pathname you put in /etc/lilo.conf is resolved at
-installation time (when you invoke /sbin/lilo). Installation
+installation time (when you invoke /sbin/lilo). 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).
Another consequence of being BIOS-based is that you must reinstall the
-loader (i.e., you must reinvoke /sbin/lilo) any time you
+loader (i.e., you must reinvoke /sbin/lilo) 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 /dev/hda2).
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 fdisk or the ``b'' command of cfdisk
-. If you don't overwrite the master boot sector you'll find it
+command of fdisk or the ``b'' command of cfdisk.
+If you don't overwrite the master boot sector you'll find it
easier to uninstall Linux and Lilo if needed.
@@ -132,7 +135,7 @@ more. All recent Lilo distribution are able to deal with LBA and LARGE
disk settings.
-Note that the "/etc/lilo.conf can
+Note that the "linear" keyword in /etc/lilo.conf 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.
How Can I Interact at Boot Time?
-When you see the Lilo prompt, you can hit the <Tab> key to show
+When you see the Lilo prompt, you can hit the <Tab> key to show
the list of possible choices. If Lilo is not configured to be
-interactive, press and hold the <Alt> or <Shift> key
+interactive, press and hold the <Alt> or <Shift> key
before the ``LILO'' message appears.
@@ -163,20 +166,20 @@ important and worth describing here:
-- root=: you can tell the Linux kernel to mount as root
+ a different partition than the one appearing in /lilo.conf.
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.
-
- /sbin/init,
+
- init=: version 1.3.43 and newer of the Linux kernel can
+ execute another command instead of /sbin/init,
as specified on the command line. If you experience bad problems
during the boot process, you can access the bare system by
specifying init=/bin/sh (when you are at the shell
prompt you most likely will need to mount your disks: try
- ``mount -w -n -o remount /; mount -a'',
- and remember to ``umount -a'' before turning off
+ ``mount -w -n -o remount /; mount -a'',
+ and remember to ``umount -a'' before turning off
the computer).
- 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
/boot/boot.ls -l
-/dev//device''. For example, the first sector of
+of your disk or partition by running ``ls -l
+/dev//device''. For example, the first sector of
/dev/hda (major 3, minor 0) will be saved in
/boot/boot.0300, installing Lilo on /dev/fd0 creates
/boot/boot.0200 and installing on /dev/sdb3 (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 /dev/hda, just
-do ``dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1''
-(I personally just do ``cat /boot/boot.0300 > /dev/hda'',
+do ``dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1''
+(I personally just do ``cat /boot/boot.0300 > /dev/hda'',
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 ``fdisk /mbr'' from a DOS
+much easier to run than trying ``fdisk /mbr'' 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'
-fdisk to destroy any Linux partition (DOS' fdisk
- is unable to remove non-dos partitions).
+fdisk to destroy any Linux partition (DOS' fdisk
+ is unable to remove non-dos partitions).
If you installed Lilo on your root partition (e.g., /dev/hda2),
nothing special needs to be done to uninstall Lilo. Just run Linux'
-fdisk to remove Linux partitions from the partition
+fdisk to remove Linux partitions from the partition
table. You must also mark the DOS partition as bootable.
How to make a ram disk?
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: http://surfer.nmr.mgh.harvard.edu/partition/ramdisk.html
+where you would find the original of the contributed section.
@@ -246,14 +249,16 @@ as a module very early in the boot cycle.
There are only two easy steps:
-- make a ram disk image with /mkinitrd
+
- make a ram disk image with /mkinitrd
- modify lilo.conf to point to the image
-First, I cd over to cd over to /boot:
+
+
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
-
+
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 (mkinitrd initrd-2.2-16-3ext3.img 2.2.16-3ext3
+boot# mkinitrd initrd-2.2-16-3ext3.img 2.2.16-3ext3
cat initrd-2.2.16-3ext3.img | gunzip > /tmp/myimage
+boot# cat initrd-2.2.16-3ext3.img | gunzip > /tmp/myimage
-boot#file /tmp/myimage
+boot# file /tmp/myimage
/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#mount /tmp/myimage /mnt/tmp -t ext2 -o loop=/dev/loop3
+boot# mount /tmp/myimage /mnt/tmp -t ext2 -o loop=/dev/loop3
-boot#ls /mnt/tmp
+boot# ls /mnt/tmp
find /mnt/tmp
+boot# find /mnt/tmp
find /mnt/tmp
/lilo as root and reboot.
+That's it. Run /lilo as root and reboot.
If you have problems, check out the kernel /etc/conf.modules.
The Simple Configuration
@@ -549,6 +554,7 @@ disk = /dev/sda
bios = 0x80
+
Using Lilo When the BIOS Can't See the Root Partition
@@ -607,6 +613,7 @@ other = /dev/hda1
alias = m
+
Accessing Huge Disks When the BIOS Can't
@@ -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.
+
Booting from a Rescue Floppy
@@ -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:.
+
Further Information
@@ -822,7 +831,7 @@ You are strongly recommended to take a backup of
your system before major installation and backups
at regular intervals.
-Other Sources of Information
+News
In addition to the Lilo docs, there are a number
@@ -864,4 +873,164 @@ email address:
.
+HOWTO
+
+disk!information resources!HOWTOs
+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
+at Metalab (formerly known as Sunsite).
+
+Mini-HOWTO
+
+disk!information resources!mini-HOWTOs
+These are the smaller free text relatives to the HOWTOs.
+Some relevant mini-HOWTOs are
+Local Resources
+
+disk!information resources!local
+In most distributions of Linux there is a document directory installed,
+have a look in the
+ directory.
+where most packages store their main documentation and README files etc.
+Also you will here find the HOWTO archive (
+)
+of ready formatted HOWTOs
+and also the mini-HOWTO archive (
+)
+of plain text documents.
+
+Many of the configuration files mentioned earlier can be found in the
+
+directory. In particular you will want to work with the
+
+file that sets up the mounting of partitions
+and possibly also
+
+file that is used for the
+is, of course, the ultimate documentation. In other
+words, use the source, Luke.
+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
+.
+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 (
+)
+to see what is going on and in particular how the booting went if
+too much scrolled off your screen. Using tail -f /var/log/messages
+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
+
+file system that is a window into the inner workings of your system.
+Use Web Pages
+
+disk!information resources!WWW
+disk!information resources!web pages
+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
+ 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.
+
+
+GETTING HELP
+
+
+(your index root)!assistance, obtaining
+
+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
+
+- Processor
+
- DMA
+
- IRQ
+
- Chip set (LX, BX etc)
+
- Bus (ISA, VESA, PCI etc)
+
- Expansion cards used (Disk controllers, video, IO etc)
+
+
+
+- BIOS (On motherboard and possibly SCSI host adapters)
+
- LILO, if used
+
- Linux kernel version as well as possible modifications and patches
+
- Kernel parameters, if any
+
- Software that shows the error (with version number or date)
+
+
+
+
- Type of disk drives with manufacturer name, version and type
+
- Other relevant peripherals connected to the same busses
+
+
+
+
+Remember that booting text is logged to /var/log/messages 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
diff --git a/LDP/howto/linuxdoc/Linux+WinNT.sgml b/LDP/howto/linuxdoc/Linux+WinNT.sgml
index af0913d4..3cacc2d0 100644
--- a/LDP/howto/linuxdoc/Linux+WinNT.sgml
+++ b/LDP/howto/linuxdoc/Linux+WinNT.sgml
@@ -4,7 +4,7 @@
Linux+WindowsNT mini-HOWTO
Miroslav Skoric, v2.4, 12 November 2000
+v2.5, 15 November 2000
linux loader windows nt boot
This mini-HOWTO covers some ways on how to install both Linux
@@ -73,7 +73,7 @@ this mini-HOWTO, has been using:
2. Edit /etc/lilo.conf and use boot=/dev/sda (I
was not successful
- at installing LILO on the Linux partition--/dev/sda3 in my case) and
+ at installing LILO on the Linux partition--/dev/sda3 in my case) and
run "lilo". You'll have to use the editor ae. You'll live.
@@ -88,14 +88,13 @@ this mini-HOWTO, has been using:
5. Add NT stanza to /etc/lilo.conf, e.g.:
-
+
other=/dev/sda1
-
label=NT
-
table=/dev/sda
-
+
+
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.
-
+
+
/dev/sda1 1 1 322 329301 6 DOS 16-bit >=32M
+
+
Partition 1 does not end on cylinder boundary:
+
phys=(321, 39, 9) should be (321, 63, 32)
-
+
Cfdisk reports strangeness, but it seems OK:
+
Unusable 0.04*
/dev/sda1 Primary DOS 16-bit >=32Mb 321.59*
Unusable 0.39*
+
+
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:
+
dd if=/dev/zero of=/dev/sda bs=512 count=1
dd if=/dev/fd0 of=/dev/sda bs=510 count=1
+
8. Install the rest of Linux. Easy, huh?
@@ -153,15 +161,19 @@ Partition 1 does not end on cylinder boundary:
+
- 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.
+
- fdisk /mbr (you've obviously already created a DOS boot
disk that contains fdisk).
+
- delete NT partition and create it again in NT install.
+
- continue with NT install.