mirror of https://github.com/tLDP/LDP
updated
This commit is contained in:
parent
4ab1990d29
commit
7dd0b6cbba
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
|
||||
|
||||
<!ENTITY version "0.6c">
|
||||
<!ENTITY version "0.6d">
|
||||
|
||||
<!ENTITY s-intro "<link linkend=s-intro>Introduction</link>">
|
||||
<!ENTITY s-doyou "<link linkend=s-doyou>Do you need assembly?</link>">
|
||||
|
@ -1094,7 +1094,7 @@ to eventually support all known syntaxes and object formats.
|
|||
<title>Where to find NASM</title>
|
||||
|
||||
<para>
|
||||
<ulink url="http://nasm.dhs.org">http://nasm.dhs.org</ulink>,
|
||||
<ulink url="http://nasm.2y.net">http://nasm.2y.net</ulink>,
|
||||
<ulink url="http://www.cryogen.com/nasm/">http://www.cryogen.com/nasm/</ulink>
|
||||
</para>
|
||||
|
||||
|
@ -1241,6 +1241,48 @@ but that could be quite useful if the assembler must be integrated
|
|||
in the software you're designing (i.e. an OS or development environment).
|
||||
</para>
|
||||
|
||||
<section><title>Free Pascal</title>
|
||||
|
||||
<para>
|
||||
<ulink url="http://www.freepascal.org">Free Pascal</ulink>
|
||||
has an internal 32-bit assembler (based on NASM tables)
|
||||
and a switchable output that allows:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
Binary (ELF and coff when crosscompiled .o) output
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
NASM
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
MASM
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
TASM
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
AS (aout,coff, elf32)
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The MASM and TASM output are not as good debugged as the other two,
|
||||
but can be handy sometimes.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The assembler's look and feel are based on Turbo Pascal's internal BASM,
|
||||
and the IDE supports similar highlighting, and FPC can fully integrate
|
||||
with gcc (on C level, not C++).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Using a dummy RTL, one can even generate pure assembler programs.
|
||||
</para>
|
||||
|
||||
</section>
|
||||
|
||||
<section><title>Win32Forth assembler</title>
|
||||
|
||||
<para>
|
||||
|
@ -1868,7 +1910,7 @@ replacements for parts of the libc -- check them out!
|
|||
(Redhat's minilibc,
|
||||
Rick Hohensee's <ulink url="ftp://linux01.gwdg.de/pub/cLIeNUX/interim/libsys.tgz">libsys</ulink>,
|
||||
Felix von Leitner's <ulink url="http://www.fefe.de/dietlibc/">dietlibc</ulink>,
|
||||
Christian Fowelin's <ulink url="http://www.fowelin.de/christian/computer/assembly/libASM/">libASM</ulink>,
|
||||
Christian Fowelin's <ulink url="http://www.fowelin.de/christian/computer/libASM/">libASM</ulink>,
|
||||
<ulink url="http://linuxassembly.org/asmutils.html">asmutils</ulink>
|
||||
project is working on pure assembly libc)
|
||||
</para></listitem>
|
||||
|
@ -2597,7 +2639,7 @@ How do I debug pure assembly code under Linux?
|
|||
|
||||
<para>
|
||||
There's an early version of the
|
||||
<ulink url="http://www.ellipse.magenet.com/ald.html">Assembly Language Debugger</ulink>,
|
||||
<ulink url="http://ellipse.mcs.drexel.edu/ald.html">Assembly Language Debugger</ulink>,
|
||||
which is designed to work with assembly code,
|
||||
and is portable enough to run on Linux and *BSD.
|
||||
It is already functional and should be the right choice, check it out!
|
||||
|
@ -2964,6 +3006,14 @@ that need not to be repeatedly mentioned every time.
|
|||
|
||||
<para><revhistory>
|
||||
|
||||
<revision>
|
||||
<revnumber>0.6d</revnumber><date>18 Mar 2001</date><authorinitials>konst</authorinitials>
|
||||
<revremark>
|
||||
Added Free Pascal;
|
||||
new NASM URL again
|
||||
</revremark>
|
||||
</revision>
|
||||
|
||||
<revision>
|
||||
<revnumber>0.6c</revnumber><date>15 Feb 2001</date><authorinitials>konst</authorinitials>
|
||||
<revremark>
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<title>FBB Packet-radio BBS mini-HOWTO
|
||||
<author>Miroslav "Misko" Skoric, YT7MPB,
|
||||
<tt/m.skoric@eunet.yu/
|
||||
<date>v1.7, 08 December 2000
|
||||
<date>v1.8, 17 March 2001
|
||||
<abstract>
|
||||
<nidx>linux windows nt amateur packet radio</nidx>
|
||||
This mini-HOWTO covers the installation and use of
|
||||
|
@ -21,7 +21,7 @@ connecting computers via amateur radio stations.
|
|||
</abstract>
|
||||
|
||||
|
||||
<sect>INTRODUCTION
|
||||
<sect>Introduction
|
||||
|
||||
<p>
|
||||
I have been using FBB amateur radio software since
|
||||
|
@ -74,10 +74,7 @@ disk that has enough room to install Linux and try
|
|||
LinFBB ...
|
||||
|
||||
|
||||
<sect>INSTALLATION
|
||||
|
||||
<p>
|
||||
<sect1>How to install X11 (Xwindows) version of LinFBB
|
||||
<sect>How to install X11 (Xwindows) version of LinFBB
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
|
@ -162,7 +159,7 @@ LinFBB ...
|
|||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect1>How to install LinFBB in addition to existing WinFBB
|
||||
<sect>How to install LinFBB in addition to existing WinFBB
|
||||
|
||||
<p>
|
||||
<em>Notice: Folks, you see, at my place, I have a
|
||||
|
@ -330,7 +327,7 @@ versa, of course).</em>
|
|||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect1>How to install Protus password utility
|
||||
<sect>How to install Protus password utility
|
||||
|
||||
<p>
|
||||
<em>Notice: Well, I have been using Protus
|
||||
|
@ -409,7 +406,7 @@ Protus offers several interesting features:
|
|||
|
||||
Well, let's see what should be done in order to
|
||||
implement secure access to the FBB packet
|
||||
radio BBS, using Protus type of <em>c_filter</em>:
|
||||
radio BBS, using Protus type of, so called, <em>c_filter</em>:
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
|
@ -580,7 +577,7 @@ radio BBS, using Protus type of <em>c_filter</em>:
|
|||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect1>How to install daemon version of LinFBB
|
||||
<sect>How to install daemon version of LinFBB
|
||||
|
||||
<p>
|
||||
<em>Notice: You see, folks, that I keep trying to get
|
||||
|
@ -734,7 +731,10 @@ to the existing two: X11 LinFBB and WinFBB!</em>
|
|||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect1>How to install an "upgrade" to daemon version of LinFBB
|
||||
<sect>How to install an "upgrade" to daemon version of LinFBB
|
||||
|
||||
<p>
|
||||
<sect1>LinFBB v7.02g
|
||||
|
||||
<p>
|
||||
<em>Notice: Well, the main trouble I have discovered with 7.01f
|
||||
|
@ -764,20 +764,26 @@ special requirements over some "third-party" software.</em>
|
|||
complained about some existing LinFBB files.
|
||||
|
||||
<p>
|
||||
<item>Then I had to de-install the old package, after what
|
||||
some config files remained as <tt>.rpmsave</tt>
|
||||
files. It was nice, so I could use them to update my
|
||||
new-installed config files.
|
||||
<item>Then I had to uninstall the old package, after what
|
||||
some config files remained in their locations, but
|
||||
with new <tt>.rpmsave</tt> extensions. It was nice,
|
||||
so I could use them later to update my new-installed
|
||||
config files.
|
||||
|
||||
<p>
|
||||
<item>Btw, the installation of Jose's package was performed
|
||||
without problems, but the new daemon was not likely to run
|
||||
as I expected, although I tried to configure it as best
|
||||
as I could. So, I have decided to make copies of new
|
||||
<tt>xfbbd</tt> and <tt>xfbbC</tt> from 7.02g package and
|
||||
*de-install* the rest of its <tt>.rpm</tt>, in order to
|
||||
install the previous version of LinFBB once again - the
|
||||
version that I was satisfied with.
|
||||
as I could. Not quite sure, but it looked to me that F6FBB
|
||||
is likely to implement some changes not only to the main
|
||||
executables but to shell files too. So, I have decided to
|
||||
save copies of these new
|
||||
<tt>xfbbd</tt> and <tt>xfbbC</tt> executables from 7.02g
|
||||
package (I have made it with adding extensions like
|
||||
.702 to the files). After that, I *uninstalled* the rest
|
||||
of that 7.02 <tt>.rpm</tt>, in order to install the previous
|
||||
version of LinFBB once again - the version that I was
|
||||
satisfied with.
|
||||
|
||||
<p>
|
||||
<item>So far - so good. The "old" 7.01f version was installed again
|
||||
|
@ -799,17 +805,160 @@ special requirements over some "third-party" software.</em>
|
|||
<item>An interesting question might be: is that now a really upgraded
|
||||
LinFBB daemon or not? Actually, I haven't changed the "old"
|
||||
script <tt>xfbbd.sh</tt> with the new one, because during the
|
||||
first tests with the new one I was getting lots of error messages.
|
||||
first tests with the new 7.02 I was getting lots of error messages.
|
||||
Looks that the directory structure was a bit complicated for me
|
||||
to set properly within the new version of <tt>xfbbd.sh</tt>.
|
||||
After I returned to <tt>xfbbd.sh</tt> from 7.01 package, the
|
||||
BBS finally started to be run, though without some functions
|
||||
like over-night maintaining (that one problem I solve in a way
|
||||
to boot the BBS as WinFBB under Windows NT where that task is ok).
|
||||
In addition, there are still some mysterious messages telling
|
||||
that <tt>m_filter</tt> has not been found or something like that.
|
||||
The next tasks are to solve these issues.
|
||||
|
||||
</itemize>
|
||||
|
||||
<p>
|
||||
<sect1>LinFBB v7.03
|
||||
|
||||
<sect>FURTHER INFORMATION
|
||||
<p>
|
||||
<em>Notice: As I have said in the previous section,
|
||||
I haven't found an easy way to upgrade FBB's (its main
|
||||
executables), without temporary uninstalling of an
|
||||
older version, then to install a newer version in
|
||||
order to get new executables. After that, a reverse
|
||||
procedure must be put in place.</em>
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
|
||||
<item>Well, it was needed to get 7.03 package (09. December 2000)
|
||||
as an <tt>.rpm</tt> package from
|
||||
<url url="http://www.f6fbb.org/versions.html"
|
||||
name="www.f6fbb.org/versions.html">,
|
||||
that was suggested by Jean-Paul, F6FBB. Anyway,
|
||||
soon after there appeared several mirror sites,
|
||||
offering 7.03 too.
|
||||
|
||||
<p>
|
||||
<item>If you use <em>GnomeRPM</em>, it is easy to uninstall
|
||||
your actual LinFBB (If you just try to install new
|
||||
<tt>.rpm</tt> over the existing LinFBB you will get
|
||||
some error messages complaining that you already have
|
||||
FBB installed on the computer). Anyway, after
|
||||
the uninstallation, there you will find some config
|
||||
files as <tt>.rpmsave</tt> files, so you could use
|
||||
them later again.
|
||||
|
||||
<p>
|
||||
<item>Installation of 7.03 package will give you
|
||||
new executables in <bf>/usr/sbin</bf> directory.
|
||||
Those new executables should be temporary given
|
||||
extensions like <tt>.703</tt> (for example).
|
||||
|
||||
<p>
|
||||
<item>So far - so good. Now you should *uninstall* the
|
||||
7.03 package (of course, <tt>.703</tt> files won't
|
||||
be unistalled automatically).
|
||||
|
||||
<p>
|
||||
<item>Once again, you should *install* the <em>last</em>
|
||||
one version of LinFBB daemon, that works ok with its
|
||||
own <tt>xfbb.sh</tt> (in my case, that is 7.01f).
|
||||
|
||||
<p>
|
||||
<item>For sure, many of you might find it odd, but
|
||||
now it is the right time for the executables from
|
||||
<bf>/usr/sbin</bf> (I mean of all fbb executables,
|
||||
except those who were renamed to <tt>.703</tt>) to get
|
||||
their new extensions (in my case, that is <tt>.701</tt>).
|
||||
|
||||
<p>
|
||||
<item>Well, after that is performed, <tt>.703</tt> files
|
||||
should *lose* their previously attached extensions,
|
||||
in order to become usable.
|
||||
|
||||
<p>
|
||||
<item>Folks, on that point I usually hold my breath, <bf>cd</bf>
|
||||
to <bf>/usr/sbin</bf> and type: <bf>xfbb.sh</bf>
|
||||
following with an Enter. If everything is fine, several
|
||||
lines should scroll on the screen, ending with
|
||||
something like:
|
||||
<p>
|
||||
<tscreen><verb>
|
||||
xfbbC/X server running ...
|
||||
xfbbd ready and running ...
|
||||
</verb></tscreen>
|
||||
|
||||
<p>
|
||||
<item>If you don't get something similar on your <em>xterm</em>
|
||||
'window' (or on other appropriate terminal
|
||||
utility), you're out of luck, so you might go
|
||||
thru the procedure once again in order to be
|
||||
sure you did all what was needed to be done :->
|
||||
|
||||
<p>
|
||||
<item><bf>/usr/sbin/xfbbC</bf> is the easiest way to
|
||||
check if your new 7.03 is in the game
|
||||
or not. When I mention xfbbC it is good to let
|
||||
you know, that I kept living in a belief that
|
||||
xfbbC is also useful for regular telnet users
|
||||
(who are also supposed to 'connect' to the BBS via
|
||||
the same computer's console, where LinFBB is
|
||||
running from). But, I have discovered that my
|
||||
users, who were <em>not</em> declared as sysops,
|
||||
are allowed to read all messages (including all
|
||||
private messages), as well as to have some
|
||||
other sysop's abilities. I did think it was
|
||||
a matter of probably wrong declared security flags.
|
||||
But, it was not.
|
||||
|
||||
<p>
|
||||
<item>Recently, I was informed that <bf>xfbbC</bf>
|
||||
is suitable only for sysops, but other users
|
||||
(who also might have local keyboard access)
|
||||
should rather try:
|
||||
|
||||
<p>
|
||||
<tscreen><verb>
|
||||
telnet localhost 6300
|
||||
</verb></tscreen>
|
||||
|
||||
<p>
|
||||
<item>... where 'localhost' and '6300' may vary from
|
||||
system to system. I was pleasently surprised
|
||||
when discovered that <bf>telnet</bf> is much more
|
||||
useful for regular users than <bf>xfbbC</bf>.
|
||||
|
||||
<p>
|
||||
<item>Folks, I think of making a section about the
|
||||
FBB's system configuration. Until something
|
||||
like that appear on the net, you should know
|
||||
that all of those callsigns who are going to
|
||||
use <bf>xfbbC</bf> have to be added into
|
||||
your <tt>passwd.sys</tt> file. And, all of
|
||||
those who are going to <bf>telnet</bf> into
|
||||
the BBS have to be declared as users with
|
||||
a 'M' flag (modem users). It is up to your
|
||||
security precautions, if either of them will
|
||||
have <em>'root'</em> abilities to the Linux box.
|
||||
<p>
|
||||
<item>My next issue is to use an old 286/12 MHz box,
|
||||
having 1 MB of RAM and running DOS 5.0 as a
|
||||
'telnet client' computer. That box also has
|
||||
a NIC and I would like to 'connect' to the
|
||||
BBS computer from that 'telnet client' box.
|
||||
Due to my preparation for starting another
|
||||
LinFBB in the local school club, where I
|
||||
should have several old 286 boxes, would
|
||||
be nice to offer more than one kid to
|
||||
'connect' the BBS simultanously, using
|
||||
a bunch of 'telnet client' computers.
|
||||
|
||||
</itemize>
|
||||
|
||||
|
||||
<sect>Further information
|
||||
|
||||
<p>
|
||||
<sect1>Copyright
|
||||
|
|
Loading…
Reference in New Issue