Linux-Misc Digest #450, Volume #19               Sun, 14 Mar 99 14:13:12 EST

Contents:
  Linux Frequently Asked Questions with Answers (Part 4 of 6) ([EMAIL PROTECTED])
  How to change localhost? (ChasonH)
  Re: Network ARP problem (brian moore)
  why does fetchmail insist sender domain exist??? ("Joseph A. Philbrook III")

----------------------------------------------------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: news.answers,comp.answers
Subject: Linux Frequently Asked Questions with Answers (Part 4 of 6)
Date: 14 Mar 1999 18:34:54 GMT

If you don't find anything, you could download the sources to the
program yourself and compile them. See "How do I port XXX to
Linux?" If it's a large package that may require some porting, post a
message to comp.os.linux.development.apps.

If you compile a large-ish program, please upload it to one or more of
the FTP sites, and post a message to comp.os.linux.announce (submit
your posting to [EMAIL PROTECTED]).

If you're looking for an application program, the chances are that
someone has already written a free version. The comp.sources.wanted
FAQ has instructions for finding the source code.


5.7 Can I use code or a compiler compiled for a 486 on my 386?

Yes, unless it's the kernel.

The -m486 option to GCC, which is used to compile binaries for x486
machines, merely changes certain optimizations. This makes for
slightly larger binaries that run somewhat faster on a 486. They still
work fine on a 386, though, with a small performance hit.

However, from version 1.3.35 the kernel uses 486 or Pentium-specific
instructions if configured for a 486 or Pentium, thus making it
unusable on a 386.

GCC can be configured for a 386 or 486; the only difference is that
configuring it for a 386 makes -m386 the default and configuring for a
486 makes -m486 the default. In either case, these can be overridden
on a per-compilation basis or by editing
/usr/lib/gcc-lib/i*-linux/n.n.n/specs.

There is an Alpha version of GCC which knows how to do optimization
well for the 586, but it is quite unreliable, especially at high
optimization settings. The Pentium GCC can be found on tsx-11.mit.edu
in /pub/linux/ALPHA/pentium-gcc. I'd recommend using the ordinary 486
GCC instead; word has it that using -m386 produces code that's better
for the Pentium, or at least slightly smaller.


5.8 What does gcc -O6 do?

Currently, the same as -O2 (GCC 2.5) or -O3 (GCC 2.6, 2.7). Any number
greater than that does the same thing. The Makefiles of newer kernels
use -O2, and you should probably do the same.


5.9 Where are linux/*.h and asm/*.h?

The files /usr/include/linux/ and /usr/include/asm/ are often soft
links to the directories where the kernel headers are. They are
usually under /usr/src/kernel*/.

If you don't have the kernel sources, download them--see, "How
do I upgrade/recompile my kernel?"

Then, use rm to remove any garbage, and ln to create the links:
rm -rf /usr/include/linux /usr/include/asm
ln -sf /usr/src/linux/include/linux /usr/include/linux
ln -sf /usr/src/linux/include/asm /usr/include/asm

/usr/src/linux/include/asm/ is a symbolic link to an
architecture-specific asm directory--if you have a freshly unpacked
kernel source tree, you must make symlinks. You'll also find that you
may need to do `make config' in a newly-unpacked kernel source tree,
to create linux/autoconf.h.


5.10 I get errors when I try to compile the kernel.

See the previous question regarding the header files.

Remember that when you apply a patch to the kernel, you must use the
-p0 or -p1 option: otherwise, the patch may be misapplied. See the
patch manual page for details.

"ld: unrecognized option `-qmagic"' means that you should get a
newer linker, from ftp://tsx-11.mit.edu/pub/linux/packages/GCC/,
in the file binutils-2.8.1.0.1.bin.tar.gz.


5.11 How do I make a shared library?

For ELF,
gcc -fPIC -c *.c
gcc -shared -Wl,-soname,libfoo.so.1 -o libfoo.so.1.0 *.o

For a.out, get tools-n.nn.tar.gz from tsx-11.mit.edu, in
/pub/linux/packages/GCC/src/. It comes with documentation that will
tell you what to do. Note that a.out shared libraries are a very
tricky business. Consider upgrading your libraries to ELF shared
libraries. See the ELF HOWTO, at
metalab.unc.edu/pub/Linux/docs/HOWTO/


5.12 My executables are (very) large.

With an ELF compiler ("What's all this about ELF?"), the most
common cause of large executables is the lack of an appropriate .so
library link for one of the libraries you're using. There should be a
link like libc.so for every library like libc.so.5.2.18.

With an a.out compiler the most common cause of large executables is
the -g linker (compiler) flag. This produces (as well as debugging
information in the output file) a program which is statically
linked--one which includes a copy of the C library instead of a
dynamically linked copy.

Other things worth investigating are -O and -O2, which enable
optimization (check the GCC documentation), and -s (or the strip
command) which strip the symbol information from the resulting binary
(making debugging totally impossible).

You may wish to use -N on very small executables (less than 8K with
the -N), but you shouldn't do this unless you understand its
performance implications, and definitely never with daemons.


5.13 Does Linux support threads or lightweight processes?

As well as the Unix multiprocessing model involving heavyweight
processes, which is of course part of the standard Linux kernel, there
are several implementations of lightweight processes or threads.
Recent kernels implement a thread model, kthreads. In addition, there
are the following packages available for Linux.
  * GNU glibc2 for Linux has optional support for threads. The archive
    is available from the same place as glibc2,
    ftp://ftp.gnu.org/pub/gnu
  * In sipb.mit.edu:/pub/pthread or
    ftp.ibp.fr:/pub/unix/threads/pthreads. Documentation isn't in the
    package, but is available on the World Wide Web at
    http://www.mit.edu:8001/people/proven/home_page.html. Newer Linux
    libc's contain the pthreads source. The GNU Ada compiler on
    metalab.unc.edu in
    /pub/Linux/devel/lang/ada/gnat-3.01-linux+elf.tar.gz contains
    binaries made from that source code.
  * In ftp.cs.washington.edu:/pub/qt-001.tar.Z is QuickThreads. More
    information can be found in the technical report, available on the
    same site as /tr/1993/05/UW-CSE-93-05-06.PS.Z.
  * In gummo.doc.ic.ac.uk/rex/ is lwp, a very minimal implementation.
  * In ftp.cs.fsu.edu:/pub/PART/, an Ada implementation. This is
    useful mainly because it has a lot of Postscript papers that
    you'll find useful in learning more about threads. This is not
    directly usable under Linux.
    
Please contact the authors of the packages in question for details.


5.14 Where can I get `lint' for Linux?

Roughly equivalent functionality is built into GCC. Use the -Wall
option to turn on most of the useful extra warnings. See the GCC
manual for more details (type control-h followed by i in Emacs and
select the entry for GCC).

There is a freely available program called `lclint' that does much the
same thing as traditional lint. The announcement and source code are
available at on larch.lcs.mit.edu in /pub/Larch/lclint/; on the World
Wide Web, look at http://larch-www.lcs.mit.edu:8001/larch/lclint.html.


5.15 Where can I find kermit for Linux?

Kermit is distributed under a non-GPL copyright that makes its terms
of distribution somewhat different. The sources and some binaries are
available on kermit.columbia.edu.

The WWW Home Page of the Columbia University Kermit project is
http://www.columbia.edu/kermit/.



6. Solutions to common miscellaneous problems.


6.1 Free dumps core.

In Linux 1.3.57 and later, the format of /proc/meminfo was changed in
a way that the implementation of free doesn't understand.

Get the latest version, from metalab.unc.edu, in
/pub/Linux/system/Status/ps/procps-0.99.tgz.


6.2 My clock is very wrong.

There are two clocks in your computer. The hardware (CMOS) clock runs
even when the computer is turned off, and is used when the system
starts up and by DOS (if you use DOS). The ordinary system time, shown
and set by "date," is maintained by the kernel while Linux is
running.

You can display the CMOS clock time, or set either clock from the
other, with /sbin/clock program--see "man 8 clock."

There are various other programs that can correct either or both
clocks for system drift or transfer time across the network. Some of
them may already be installed on your system. Try looking for adjtimex
(corrects for drift), netdate, and getdate (get the time from the
network), or xntp (accurate, full-featured network time daemon).


6.3 Setuid scripts don't seem to work.

That's right. This feature has been disabled in the Linux kernel on
purpose, because setuid scripts are almost always a security hole.
Sudo and SuidPerl can provide more security that setuid scripts or
binaries, especially if execute permissions are limited to a certain
user ID or group ID.

If you want to know why setuid scripts are a security hole, read the
FAQ for comp.unix.questions.


6.4 Free memory as reported by free keeps shrinking.

The "free" figure printed by free doesn't include memory used as a
disk buffer cache--shown in the "buffers" column. If you want to
know how much memory is really free add the "buffers" amount to
"free"--newer versions of free print an extra line with this info.

The disk buffer cache tends to grow soon after starting Linux up. As
you load more programs and use more files, the contents get cached. It
will stabilize after a while.


6.5 When I add more memory, the system slows to a crawl.

This is a common symptom of a failure to cache the additional memory.
The exact problem depends on your motherboard.

Sometimes you have to enable caching of certain regions in your BIOS
setup. Look in the CMOS setup and see if there is an option to cache
the new memory area which is currently switched off. This is
apparently most common on a '486.

Sometimes the RAM has to be in certain sockets to be cached.

Sometimes you have to set jumpers to enable caching.

Some motherboards don't cache all of the RAM if you have more RAM per
amount of cache than the hardware expects. Usually a full 256K cache
will solve this problem.

If in doubt, check the manual. If you still can't fix it because the
documentation is inadequate, you might like to post a message to
comp.os.linux.hardware giving all of the details--make, model number,
date code, etc., so other Linux users can avoid it.


6.6 Some programs (e.g. xdm) won't let me log in.

You are probably using non-shadow password programs and are using
shadow passwords.

If so, you have to get or compile a shadow password version of the
programs in question. The shadow password suite can be found at
tsx-11.mit.edu:/pub/linux/sources/usr.bin/shadow/. This is the source
code. The binaries are probably in linux/binaries/usr.bin/.


6.7 Some programs let me log in with no password.

You probably have the same problem as in "Some programs (e.g.
xdm) won't let me log in.", with an added wrinkle.

If you are using shadow passwords, you should put a letter `x' or an
asterisk in the password field of /etc/passwd for each account, so
that if a program doesn't know about the shadow passwords it won't
think it's a passwordless account and let anyone in.


6.8 My machine runs very slowly when I run GCC / X / ...

You may have too little real memory. If you have less RAM than all the
programs you're running at once, Linux will swap to your hard disk
instead and thrash horribly. The solution in this case is to not run
so many things at once or buy more memory. You can also reclaim some
memory by compiling and using a kernel with less options configured.
See "How do I upgrade/recompile my kernel?".

You can tell how much memory and swap you're using with the free
command, or by typing:
cat /proc/meminfo

If your kernel is configured with a RAM disk, this is probably wasted
space and will cause things to go slowly. Use LILO or rdev to tell the
kernel not to allocate a RAM disk (see the LILO documentation or type
man rdev).


6.9 I can only log in as root.

You probably have some permission problems, or you have a file
/etc/nologin.

In the latter case, put rm -f /etc/nologin in your /etc/rc.local or
/etc/rc.d/* scripts.

Otherwise, check the permissions on your shell, and any file names
that appear in error messages, and also the directories that contain
these files, up to and including the root directory.


6.10 My screen is all full of weird characters instead of letters.

You probably sent some binary data to your screen by mistake. Type
echo '\033c' to fix it. Many Linux distributions have a command,
"reset," that does this.

If that doesn't help, try a direct screen escape command.
echo <Ctrl-V><Ctrl-O>

This resets the default font of a Linux console. Remember to hold down
the Control key and type the letter, instead of, for example,
`Ctrl-V'. The sequence
echo <Ctrl-V><Esc>c

causes a full screen reset. If there's data left on the shell command
line after typing a binary file, press Ctrl-C a few times to restore
the shell command line.

[Bernhard Gabler]


6.11 I have screwed up my system and can't log in to fix it.

Reboot from an emergency floppy or floppy pair. For example, the
Slackware boot and root disk pair in the install subdirectory of the
Slackware distribution.

There are also two, do-it-yourself rescue disk creation packages in
metalab.unc.edu/pub/Linux/system/Recovery. These are better
because they have your own kernel on them, so you don't run the risk
of missing devices and file systems.

Get to a shell prompt and mount your hard disk with something like
mount -t ext2 /dev/hda1 /mnt

Then your file system is available under the directory /mnt and you
can fix the problem. Remember to unmount your hard disk before
rebooting (cd somewhere else first, or it will say it's busy).


6.12 I've discovered a huge security hole in rm!

No you haven't. You are obviously new to unices and need to read a
good book to find out how things work. Clue: the ability to delete
files depends on permission to write in that directory.


6.13 lpr(1) and/or lpd(8) don't work.

First make sure that your /dev/lp* port is correctly configured. Its
IRQ (if any) and port address need to match the settings on the
printer card. You should be able to dump a file directly to the
printer.
cat the_file >/dev/lp1

If lpr gives you a message like "myname@host: host not found," it
may mean that the TCP/IP loopback interface, lo, isn't working
properly. Loopback support is compiled into most distribution kernels.
Check that the interface is configured with the ifconfig command. By
Internet convention, the network number is 127.0.0.0, and the local
host address is 127.0.0.1. If everything is configured correctly, you
should be able to telnet to your own machine and get a login prompt.

Make sure that /etc/hosts.lpd contains the machine's host name.

If your machine has a network-aware lpd, like the one that comes with
LPRng, make sure that /etc/lpd.perms is configured correctly.

Also look at the Printing-HOWTO "Where can I get the HOWTO's
and other documentation?".


6.14 Timestamps on files on MS-DOS partitions are set incorrectly.

There is a bug in the program "clock" (often found in /sbin). It
miscounts a time zone offset, confusing seconds with minutes or
something like that. Get a recent version.


6.15 How do I get LILO to boot the kernel image?

>From kernel versions 1.1.80 on, the compressed kernel image, which is
what LILO needs to find, is in arch/i386/boot/zImage, or
arch/i386/boot/bzImage when it is built, and is normally stored in the
/boot/ directory. The /etc/lilo.conf file should refer to the vmlinuz
symbolic link, not the actual kernel image.

This was changed to make it easier to build kernel versions for
several different processors from one source tree.


6.16 I upgraded the kernel and now my PCMCIA card doesn't work.

The PCMCIA Card Services modules, which are located in
/lib/modules/<version>/pcmcia, where <version> is the version number
of the kernel, use configuration information that is specific to that
kernel image only. The PCMCIA modules on your system will not work
with a different kernel image. You need to upgrade the PCMCIA card
modules when you upgrade the kernel.

Important: If you use the PCMCIA Card Services, do not enable the
"Network device support/Pocket and portable adapters" option of the
kernel configuration menu, as this conflicts with the modules in Card
Services.

Knowing the PCMCIA module dependencies of the old kernel is useful.
You need to keep track of them. For example, if your PCMCIA card
depends on the serial port character device being installed as a
module for the old kernel, then you need to ensure that the serial
module is available for the new kernel and PCMCIA modules as well.

The procedure described here is somewhat kludgy, but it is much easier
than re-calculating module dependencies from scratch, and making sure
the upgrade modules get loaded so that both the non-PCMCIA and PCMCIA
are happy. Recent kernel releases contain a myriad of module options,
too many to keep track of easily. These steps use the existing module
dependencies as much as possible, instead of requiring you to
calculate new ones.

However, this procedure does not take into account instances where
module dependencies are incompatible from one kernel version to
another. In these cases, you'll need to load the modules yourself with
insmod, or adjust the module dependencies in the /etc/conf.modules
file. The Documentation/modules.txt file in the kernel source tree
contains a good description of how to use the kernel loadable modules
and the module utilities like insmode, modprobe, and depmod.
Modules.txt also contains a recommended procedure for determining
which features to include in a resident kernel, and which to build as
modules.

Essentially, you need to follow these steps when you install a new
kernel.
  * Before building the new kernel, make a record with the lsmod
    command of the module dependencies that your system currently
    uses. For example, part of lsmod's output might look like this:
memory_cs          2            0
ds                 2    [memory_cs]     3
i82365             4            2
pcmcia_core        8    [memory_cs ds i82365]   3
sg                 1            0
bsd_comp           1            0
ppp                5    [bsd_comp]      0
slhc               2    [ppp]   0
serial             8            0
psaux              1            0
lp                 2            0
Module         Pages    Used by
    This tells you for example that the memory_cs module needs the ds
    and pcmcia_core modules loaded first. What it doesn't say is that,
    in order to avoid recalculating the module dependencies, you may
    also need to have the serial, lp, psaux, and other standard
    modules available to prevent errors when insmod'ing the pcmcia
    routines at boot time. A glance at the /etc/modules file will tell
    you what modules the system currently loads, and in what order.
    Save a copy of this file for future reference, until you have
    successfully installed the new kernel's modules. Also save lsmod's
    output to a file, for example, with the command:
lsmod >lsmod.old-kernel.output
  * Build the new kernel, and install the boot image, either zImage or
    bzImage, to a floppy diskette. To do this, change to the
    arch/i386/boot directory (substitute the correct architecture
    directory if you don't have an Intel machine), and, with a floppy
    in the diskette drive, execute the command:
dd if=bzImage of=/dev/fd0 bs=512
    If you built the kernel with the "make bzImage" command, and if
    your floppy drive is /dev/fd0. This results in a bootable kernel
    image being written to the floppy, and allows you to try out the
    new kernel without replacing the existing one that LILO boots on
    the hard drive.
  * Boot the new kernel from the floppy to make sure that it works.
  * With the system running the new kernel, compile and install a
    current version of the PCMCIA Card Services package, available
    from metalab.unc.edu as well as other Linux archives. Before
    installing the Card Services utilities, change the names of
    /sbin/cardmgr and /sbin/cardctl to /sbin/cardmgr.old and
    /sbin/cardctl.old. The old versions of these utilities are not
    compatible with the replacement utilities that Card Services
    installs. In case something goes awry with the installation, the
    old utilities won't be overwritten, and you can revert to the
    older versions if necessary. When configuring Card Services with
    the "make config" command, make sure that the build scripts know
    where to locate the kernel configuration, either by using
    information from the running kernel, or telling the build process
    where the source tree of the new kernel is. The "make config" step
    should complete without errors. Installing the modules from the
    Card Services package places them in the directory
    /lib/modules/<version>/pcmcia, where <version> is the version
    number of the new kernel.
  * Reboot the system, and note which, if any, of the PCMCIA devices
    work. Also make sure that the non-PCMCIA hardware devices are
    working. It's likely that some or all of them won't work. Use
    lsmod to determine which modules the kernel loaded at boot time,
    and compare it with the module listing that the old kernel loaded,
    which you saved from the first step of the procedure. (If you
    didn't save a listing of lsmod's output, go back and reboot the
    old kernel, and make the listing now.)
  * When all modules are properly loaded, you can replace the old
    kernel image on the hard drive. This will most likely be the file
    pointed to by the /vmlinuz symlink. Remember to update the boot
    sector by running the lilo command after installing the new kernel
    image on the hard drive.
    
Also look at the questions, How do I upgrade/recompile my kernel?
and Modprobe can't locate module, "XXX," and similar messages.



7. How do I do this or find out that ... ?


7.1 How can I get scrollback in text mode?

With the default US keymap, you can use Shift with the PageUp and
PageDown keys. (The gray ones, not the ones on the numeric keypad.)
With other keymaps, look in /usr/lib/keytables. You can remap the
ScrollUp and ScrollDown keys to be whatever you like. For example, to
remap them to the keys on an 84-key, AT keyboard.

The "screen" program,
http://vector.co.jp/vpack/browse/person/an010455.html provides a
searchable scrollback buffer and the ability to take "snapshots" of
text-mode screens.

You can't increase the amount of scrollback, because it is implemented
using the video memory to store the scrollback text. You may be able
to get more scrollback in each virtual console by reducing the total
number of VC's. See linux/tty.h.


7.2 How do I switch virtual consoles? How do I enable them?

In text mode, press Left Alt-F1 to Alt-F12 to select the consoles tty1
to tty12; Right Alt-F1 gives tty13 and so on. To switch out of X you
must press Ctrl-Alt-F1, etc; Alt-F5 or whatever will switch back.

If you want to use a VC for ordinary login, it must be listed in
/etc/inittab, which controls which terminals and virtual consoles have
login prompts. The X Window System needs at least one free VC in order
to start.


7.3 How do I set the time zone?

Change directory to /usr/lib/zoneinfo/. Get the time zone package if
you don't have this directory. The source is available in
metalab.unc.edu/pub/Linux/system/admin/time/.

Then make a symbolic link named localtime pointing to one of the files
in this directory (or a subdirectory), and one called posixrules
pointing to localtime. For example:
ln -sf US/Mountain localtime
ln -sf localtime posixrules

This change will take effect immediately--try date(1).

The manual page for tzset describes setting the time zone. Some
programs recognize the TZ environment variable, but this is not
POSIX-correct.

You should also make sure that your Linux kernel clock is set to the
correct GMT time--type date -u and check that the correct UTC time is
displayed. ("My clock is very wrong.")


7.4 What version of Linux and what machine name am I using?

Type:
uname -a


-- 
[EMAIL PROTECTED]

------------------------------

From: [EMAIL PROTECTED] (ChasonH)
Subject: How to change localhost?
Date: 14 Mar 1999 14:16:01 GMT

I was trying to configure networking and I must have changed a file
accidentally and now localhost is ocalhost when I log on.  Please tell me where
to reconfigure this.

Thank you
[EMAIL PROTECTED]
(please email)
Chason Hayes

------------------------------

From: [EMAIL PROTECTED] (brian moore)
Subject: Re: Network ARP problem
Date: 14 Mar 1999 18:45:02 GMT

On Mon, 08 Mar 1999 11:16:21 -0500, 
 Patrick Lemire <[EMAIL PROTECTED]> wrote:
> I've just setup a 3com 509b card in my SuSE 5.3 (K2.0.35) system.  I
> followed the sample setup in Net-3-Howto and everything worked well
> until i try to ping a station on the network.  The ping never respond on
> the machine.
> 
> The ARP Broadcast went on the network, i could see it with a sniffer,
> and the pinged station responded.
> 
> If i check in the ARP table, my neighbor station is in the list (there
> is only one entry),  with the addresss 00.00.00.00.00.00.  So i suppose
> that after the ARP request the TCP stack couldn't send the ICMP request
> to an address of 00s and didn't sent it.
> 
> Could anybody tell me where should i check to correct this problem ?  Is
> my ARP is in fault or something i miss in my configuration?

My bet is cabling.

The all zero's address is because it has a pending request out with no
answer: your Linux box didn't see the other machine.

-- 
Brian Moore                       | "The Zen nature of a spammer resembles
      Sysadmin, C/Perl Hacker     |  a cockroach, except that the cockroach
      Usenet Vandal               |  is higher up on the evolutionary chain."
      Netscum, Bane of Elves.                 Peter Olson, Delphi Postmaster

------------------------------

From: "Joseph A. Philbrook III" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.slackware
Subject: why does fetchmail insist sender domain exist???
Date: Sun, 14 Mar 1999 13:27:44 +0000
Reply-To: "Joseph A. Philbrook III" <[EMAIL PROTECTED]>

So far this is the 2nd time I've had something in my pop3 mailbox that
prevented fetchmail from retrieving my mail from the isp...

This is what happened when I tried to recieve my mail a few minutes ago.

/home/jtwdyp
> fetchmail -a
2 messages for jtwdyp at pop3.ttlc.net (6338 bytes).
reading message 1 of 2 (1464 bytes) fetchmail: SMTP error: 501
<[EMAIL PROTECTED]>... Sender domain must exist
fetchmail: SMTP error: 553 <jtwdyp>... Domain name required
fetchmail: SMTP transaction error while fetching from pop3.ttlc.net
/home/jtwdyp
>

I'm faily certain it's fetchmail on my linux thats complaining because I
can retrieve the message with "Uncle Dave's dos reader <nettamer>...

This one message will stop fetchmail from recieving ANY E-mail from the pop3
server. the only way I know how to fix it is to boot my dos mail reader
<NetTamer> and use it to retrieve and flush the messages. Unfortuanately
this will put the messages in nettamers mail.dlu file which is an octet
stream that pine doesn't know how to open, even if I copy the file to my
linux ext2 filesystem first.  And while I could care less if that happens
to the offending message, I get iritated when there turns out to be good
stuff in the folowing message(s) 

I suppose I can save the mesage to a new file with nettamer, and then from
my linux I can compose an E-mail to myself, and import the saved nettamer
file into the messaage body... But it is still agravating...

 to reply by E-mail, replace the obvious and glue it together...

 <jtwdtp AT ttlc DOT net>



------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.misc) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Misc Digest
******************************

Reply via email to