Linux-Misc Digest #671, Volume #21 Sat, 4 Sep 99 17:13:09 EDT
Contents:
Netscape color (ORRIN)
Re: Amiga, QNX, Linux and Revolution (Linus Torvalds)
Re: Figure Out The MS Source Code Yourself (Tim Roberts)
Re: PDFs for Linux (Bob Tennent)
Re: PDFs for Linux (Coy A Hile)
Re: Conversions: PDF, Postscript, etc. (Thomas R. Shannon)
Re: I WANT TO DITCH WINDOZE BUT I CANT!!! (Donovan Rebbechi)
Problems with SATAN, HELP (Warren Bell)
Re: [Q] Editing large (~GB) files ? vi ? (Andrei A. Dergatchev)
Re: Amiga, QNX, Linux and Revolution (Guy Macon)
Re: Shutdown Problem (Randall Parker)
Re: Which distribution to use? ("James Lohse")
Re: POP3 and SMTP for Sendmail/Linux ("William Evans")
Re: fsck after power failure (Ollie)
Linux Software Archive + more (noname)
Re: Shutdown Problem (Randall Parker)
Re: Star Office 5.1 and KDE (Mike Bosschaert)
----------------------------------------------------------------------------
From: ORRIN <[EMAIL PROTECTED]>
Subject: Netscape color
Date: Sat, 04 Sep 1999 15:25:10 -0400
I noticed that the copy of Netscape (4.5.1) that came with my copy of
SuSE 6.1, has a black & white heading and icons rather than color like
my old Windows version. It that the way it is, or is there a way to
fix it. I didn't see anything in the options.
=============================
Orrin - Long Island, New York
Orrin's Caribbean Index - http://www.orrin.org/carib/
Syosset Camera Club - http://www.orrin.org/syocc/
HS Class Reunion - http://www.orrin.org/wphs/
Our e-mail address is at http://www.orrin.org/email.html
------------------------------
From: [EMAIL PROTECTED] (Linus Torvalds)
Crossposted-To: comp.os.qnx,comp.sys.amiga.misc
Subject: Re: Amiga, QNX, Linux and Revolution
Date: 4 Sep 1999 18:37:53 GMT
In article <[EMAIL PROTECTED]>,
Juergen Fischer <[EMAIL PROTECTED]> wrote:
>x-no-archive: yes
>
>[EMAIL PROTECTED] (Linus Torvalds) wrote:
>
>> Sure, teh QNX microkernel is pretty uncrashable. But have you ever asked
>> yourself why? Maybe because it doesn't do all that much.
>
>hello Linus, how much of change would the kernel need to get it
>sheduling a la QNX and Kickstart ?
And we would like to have that exactly why?
Somebody ported lmbench to QNX, and preliminary results show QNX having
rather worse scheduling latencies etc than Linux. I don't think you
realize how many people have NOT used QNX, and as such there's a lot of
things that people just take for granted rather than actually have any
proof for.
Linus
------------------------------
From: [EMAIL PROTECTED] (Tim Roberts)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development.system
Subject: Re: Figure Out The MS Source Code Yourself
Reply-To: [EMAIL PROTECTED]
Date: Sat, 04 Sep 1999 18:40:23 GMT
In article <[EMAIL PROTECTED]>, Cocheese wrote:
>
>Here is my question:
>--------------------
>
>if a program must be compiled before running, is it possible to "Uncompile"
>it somehow? and if so... Could it be possible to reveal (even to some
>degree) the code in order to figure out what we all want to know?
Yes. This technique is called "reverse engineering". It is a relatively
well-understood technique, and there are many tools for doing so.
The problem with reverse engineering something like Windows is two-fold. First,
it is illegal; the Windows license agreement prohibits it. Second, Windows is
just too big. Windows 2000 consists of something like 20 million lines of
source code.
--
- Tim Roberts, [EMAIL PROTECTED]
Providenza & Boekelheide, Inc.
------------------------------
From: [EMAIL PROTECTED] (Bob Tennent)
Subject: Re: PDFs for Linux
Date: 4 Sep 1999 19:42:50 GMT
On Tue, 31 Aug 1999 21:16:08 -0600, Kerry J. Cox wrote:
>Does the Adobe available for Linux has any utility for making pdf
>files? I'd like to start making my won pdf files and I don't use
>Windows.
Check out
http://www.babinszki.com/distiller/
Bob T.
------------------------------
From: [EMAIL PROTECTED] (Coy A Hile)
Subject: Re: PDFs for Linux
Date: 4 Sep 1999 15:00:24 -0400
In article <[EMAIL PROTECTED]>,
Christopher R. Carlen <[EMAIL PROTECTED]> wrote:
>Chris Mahmood wrote:
>>
>> "Kerry J. Cox" <[EMAIL PROTECTED]> writes:
>>
>> > Does the Adobe available for Linux has any utility for making pdf
>> > files? I'd like to start making my won pdf files and I don't use
>> > Windows.
>> ps2pdf(1).
>> -ckm
>
>
>Where does ps2pdf come from?
>
from the manpage, it uses ghostscript, so i think it may come with that
distrubution, though i've seen it in the TeX and *roff distributionsa as
well.
HTH
Coy
--
Coy Hile
[EMAIL PROTECTED]
"Theirs not to reason why; theirs but to do...."
Tennyson, "Charge of the Light Brigade"
------------------------------
From: [EMAIL PROTECTED] (Thomas R. Shannon)
Subject: Re: Conversions: PDF, Postscript, etc.
Date: 03 Sep 1999 20:04:53 -0500
"Steve D. Perkins" <[EMAIL PROTECTED]> writes:
> This may sound quite dumb... but I was wondering if any
> utilities exist in the Linux world for converting documents in
> Postscript, PDF, or HTML (particularly Postscript and PDF)
> between each other's formats?
ps2pdf
You need to be using Adobe Type 1 fonts.
Tom
--
Quote of the day for Friday, 3 September, 1999:
"The only limits are, as always, those of vision."
- James Broughton
------------------------------
From: [EMAIL PROTECTED] (Donovan Rebbechi)
Crossposted-To: comp.os.linux.advocacy,comp.os.linux.questions
Subject: Re: I WANT TO DITCH WINDOZE BUT I CANT!!!
Date: 4 Sep 1999 15:53:46 -0400
On Fri, 3 Sep 1999 13:02:17 -0500, Azzy wrote:
> * Quicken 98
Don't know.
> * Cold Fusion Studio (aka Homesite.. the best HTML editor I have seen)
webtk has a forms builder. Netscape composer has a WYSIWYG html
editor.
If you want a nice non-"wysiwyg" html editor, emacs, and gvim both do
a very good job . They have syntax highlighting for html and all
the embedded code such as javascript. in gvim, you can roll your own
keyboard shortcuts to draw tags.
If you want database connectivity, your best bet is probably
PHP ( which lets you embed SQL queries via perl in your code )
> * A good Java IDE (Visual Cafe Pro or VisualAge for Java are among my
>favs)
I believe there are some java IDEs for linux, though I haven't
tried them.
See the other followups for your other points
--
Donovan
------------------------------
Date: Sat, 04 Sep 1999 19:51:57 +0000
From: Warren Bell <[EMAIL PROTECTED]>
Subject: Problems with SATAN, HELP
:) I'm trying to install SATAN on Mandrake Linux 6.0. I've tried both
the prepatched tarball and rebuilding the SRC RPM on my machine. They
both get the same error and quit. Does anyone know what could be
causing it and how I can get around it?
The error:
rex.c: In function `rex_command':
rex.c:178: warning: passing arg 3 from incompatible pointer type
rex.c:178: warning: passing arg 5 from incompatible pointer type
rex.c: In function `rex_exit':
rex.c:222: warning: passing arg 3 from incompatible pointer type
rex.c:222: warning: passing arg 5 from incompatible pointer type
cc -O -I. -DAUTH_GID_T=gid_t -c rex_xdr.c -o rex_xdr.o
cc -O -I. -DAUTH_GID_T=gid_t -o ../../bin/rex rex.o rex_xdr.o
make[2]: Leaving directory `/usr/src/RPM/BUILD/satan-1.1.1/src/misc'
cd src/boot; make "LIBS=" "XFLAGS=-DAUTH_GID_T=gid_t" "RPCGEN=rpcgen"
make[2]: Entering directory `/usr/src/RPM/BUILD/satan-1.1.1/src/boot'
rpcgen bootparam_prot.x 2>/dev/null
cc -I. -O -DAUTH_GID_T=gid_t -c boot.c -o boot.o
boot.c:24: macro `strchr' used without args
make[2]: *** [boot.o] Error 1
make[2]: Leaving directory `/usr/src/RPM/BUILD/satan-1.1.1/src/boot'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/RPM/BUILD/satan-1.1.1'
make: *** [linux] Error 2
Bad exit status from /var/tmp/rpm-tmp.45482 (%build)
------------------------------
From: [EMAIL PROTECTED] (Andrei A. Dergatchev)
Subject: Re: [Q] Editing large (~GB) files ? vi ?
Date: Sat, 04 Sep 1999 18:42:24 GMT
Hi,
Thanks a lot for your answer. I'm not familiar with any of
these :-( - I came from MS DOS world, where I used to write
C programs for such tasks :-((
I'll try to learn how to do it in awk. I don't have python
and sed installed I think.
Thanks again,
Andrei
>
>If you just want to delete lines, why not use 'awk', 'sed', or
>'python'?
>
------------------------------
From: [EMAIL PROTECTED] (Guy Macon)
Crossposted-To: comp.os.qnx,comp.realtime
Subject: Re: Amiga, QNX, Linux and Revolution
Date: 04 Sep 1999 13:13:08 PDT
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Thomas Tavoly) wrote:
> Actually, take a look (if you haven't already) at the Ballista project
> at Carnegie Mellon
(URL deleted.� He listed a URL that the official URL redirects to,
which may change.� The proper URL is:
http://www.ices.cmu.edu/ballista
> in which QNX� was found to be the least robust amongst several
> major POSIX compliant� OS's (including Linux).� An interesting
> response by QNX is also posted there.
Here is that response:
***** Start of Quote *****
To: "'Philip Koopman'" <[EMAIL PROTECTED]>
Subject: Automated Robustness testing research
From: Greg Bergsma <[EMAIL PROTECTED]>
Date: Thu, 12 Mar 1998 13:56:50 -0500
Dear Mr. Koopman,
As you are aware, we at QNX Software Systems Ltd (QSSL) are following
your research into comparing operating systems with robustness benchmarks.
Coming up with an appropriate benchmark suite poses a significant
challenge and we commend you and your colleagues in taking such an
active role. We are particularly interested in the opportunity for us
to improve the robustness of QNX as a result of your research.
We would like to take this opportunity to explain the architectural
response we have taken to failures that you have identified as "abort"
failures. We believe our approach to handling corrupt pointers has
significant merit as an alternative to the approach you propose in
your research.
Corrupt pointers are the nemesis of all C programmers. They indicate
that something wrong has happened, something unexpected. It is the
role of the OS to ensure corrupt pointers in one process cannot affect
other processes in the system or the OS kernel itself. Taking advantage
of the MMU is crucial for any OS that is to be considered for
mission-critical applications.
Finding the code which resulted in the corrupt pointer can be very
difficult, particularly in large programs. The OS must provide the
maximum amount of feedback to the programmer to allow him to track
down the problem.
Although returning EFAULT from C library routines provides definite
feedback that an invalid pointer is being used, we knew it was possible
to provide additional feedback - feedback that could be crucial to
finding the source of the fault. If a library routine returns EFAULT,
then it is up to the calling program to determine how it should recover
from the error. Having a stray pointer in many cases indicates some
other inherent problem with the program, a problem that the programmer
may not be able to identify in any recovery code that would follow the
function call. In fact, writing recovery code can only handle situations
where you think you MAY have had a problem - the problem itself could be
quite different to what you might have coded for. The recovery code may
be totally inappropriate for the condition that occurred. You may do
further damage by continuing to use data areas and variables that may
have contributed to the stray pointer in the first place. In most cases,
the only course of action would be to restart the process. We also
recognized that coding for handling the EFAULT error was not part of most
C programmers programming paradigm. If you look at the source for X and
BSD TCP/IP and a whole host of related source code you find a negligible
amount of code handling the EFAULT condition. Thus we decided it was
essential to terminate processes with a memory violation (even in a C
library function) - provided we also gave the developer recovery
mechanisms and maximum feedback on the fault.
So the mechanisms we provide developers are :
1. The ability for the OS to notify an overseer process (we call this a
"software watchdog" - written by the developer) that can intelligently
recover from the fault (i.e.. Restart the process and/or any related
processes).
2. Process dump capabilities whereby the process that is being terminated
is first dumped to disk (all code and data), before it is terminated.
We then provide post-mortem dump capability in our debugger that allows
the developer to view the state of the process at the exact instruction
where the violation occurred (including variables, stack trace, function
trace, C and assembly source trees). The dump can be analyzed off-line,
while the software watchdog can keep the system running.
This is MUCH more accurate than checking for EFAULT, pointing the
programmer to the precise instruction which caused the fault. However,
if the program wants to deal with memory access violations itself, it
can also catch the SIGSEGV signal and have it's own signal handler
execute. Again, this is more accurate than simply checking for an
EFAULT return value, and doesn't require modifying potentially huge
amounts of source code.
With QNX adopting such a philosophy, it comes as no surprise that you
have identified more Abort failures with QNX than other OS' evaluated
in your research.
Our approach provides enormous advantages in the amount of feedback we
provide developers to assist them in getting to the root of these sorts
of programming errors. We feel that the identification of so many Abort
failures and subsequently how that affects our rating in your report
is not representative of the level of robustness we deliver - rather
it represents a difference in philosophy. Had we no recovery and feedback
mechanisms then we would agree with the rating. We have no issue with the
other categories of failure you identify.
One last issue is that you might wish to consider is one that reflects
directly on the architecture of the OS and how drivers can have an affect
on system reliability and robustness. In the embedded and real-time
arenas, many systems require the use of custom hardware. For applications
to access that hardware, drivers need to be written. These drivers vary
in complexity, and in most operating systems end up running as part of
the kernel - in kernel space. What would happen if a driver started
using a corrupt pointer? It doesn't run with any memory-protection so it
has free reign to clobber any part of memory - even the kernel (possibly
causing a kernel fault). Tracking these problems can be a nightmare.
However, an OS with a microkernel architecture like QNX solves this
problem - drivers run in user space with full memory protection. In
other� OS's, any attempt to use a bad pointer would crash the OS. Under
QNX, it� becomes a routine bug to be analyzed as easily as any other
application-level programming error".
We look forward to your response to these issues and will continue to
eagerly monitor your research. We would like to pursue a conference call
with you to discuss these issue - please nominate a time that would be
convenient for you.
Sincerely,
Greg Bergsma - Senior Technology Analyst ([EMAIL PROTECTED])
Dan Hildebrand - Senior Architect ([EMAIL PROTECTED])
________________________________________________________
QNX Software Systems Ltd���� | Phone: +1 (613) 591 0931
175 Terence Matthews Crescent| Fax:�� +1 (613) 591 3579
Kanata, Ontario, Canada����� | Email: [EMAIL PROTECTED]
K2M1W8���������������������� | WWW:�� http://www.qnx.com
________________________________________________________
***** End of Quote *****
I have two problems with what the Ballista project is doing here.
[1] They fail to differentiate between an OS failing to handle one
��� of the test cases and an OS purposefully handling the test case
��� in a different way than their assumption of what the Only Valid
��� Way To Handle Errors is.
[2] They printed posters and put up web pages containing bar charts
��� showing "Robustness Failure Rate" for various Operating Systems,
��� despite the fact that what they are measuring is not robustness.
I believe that the Ballista project should measure the ability of
each OS to exhibit whatever error-response behavior is documented
for that OS.� That's what most programmers would expect of a test
of "operating system robustness".
I also believe that a process failure which prevents the failing
process alone from completing it's task should be listed differently
from a process failure which prevents unrelated processes or the
operating system itself from completing their tasks.� In the real
world of high reliability systems, the ability of a critical module
to continue despite the failure of a non critical module is an
important reliability issue.
What the Ballista Project is testing for is very useful and I am glad
to see them do it.� I just wish that they wouldn't call what they are
testing for "Robustness Failure Rate", and that they would realize that
they are not in charge of deciding what the proper response to a bad
input is for all operating systems.�
------------------------------
From: [EMAIL PROTECTED] (Randall Parker)
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.x
Subject: Re: Shutdown Problem
Date: Sat, 4 Sep 1999 13:24:28 -0700
In article <wgu20.935827785@riemann>, [EMAIL PROTECTED]
says...
> So, DO NOT SWITCH OFF THE MACHNE WITHOUT A PROPER SHUTDOWN.
What if this can not always be done?
> And when it happens, accept your punishment of waiting while linux tries
> to make sure you have not corrupted your disk, and saves you from your
> stupidity.
What if the causes of this owe nothing to your stupidity?
This sort of tone treats uses with a contempt that they really do not
deserve.
> Ie, make sure that you educate your users-- shout at them, paste huge
> signs around the computer, etc, to always shut down before switching
> off.
I'll also convince them to stop smoking, eat less fatty foods, and get
more exercise.
Right after pigs start flying.
------------------------------
From: "James Lohse" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.help,comp.os.linux.setup,linux.dev.newbie
Subject: Re: Which distribution to use?
Date: Sat, 4 Sep 1999 16:24:25 -0400
Richard Steiner <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Here in comp.os.linux.misc, "Johnny" <[EMAIL PROTECTED]>
> spake unto us, saying:
>
> >If Linux is to survive as an OS and as an alternative - then EASE of
> >use is a MUST.
>
> Why? Linux's survival isn't dependent on being a commercial success.
>
No, evidently it's not. I'd add that IMHO Linux has come much further in a
shorter spanse of time than Windoze. Being free 'ain't' too bad either.
Just my 2cents
------------------------------
From: "William Evans" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,redhat.security.general
Subject: Re: POP3 and SMTP for Sendmail/Linux
Date: 04 Sep 1999 16:27:49 -0400
>>>>> "Andrew" == Andrew James <[EMAIL PROTECTED]> writes:
Andrew> I have a similar problem, have uncommented the imap and
Andrew> pop3 lines from inetd.conf -,, can't telnet 25 , I think
Andrew> sendmail is running
I'll try to work with what you've given.
(1) Uncommenting imap and pop3 has nothing to do with port 25.
Specifically, imap works on port 143 and pop3 on port 110. 25 is
for SMTP, a different (but related) protocol. (IMAP and POP3 are
used to download/manage mail that has already been delivered to a
remote mailbox; neither of them have nothing to do with how mail
is sent out. SMTP has to do with delivering mail both locally and
remotely, but doesn't deal with how local users access it.)
(2) Whenever you comment or uncomment something in inetd.conf, you
need to tell inetd to reread the configuration; do this by sending
it a SIGHUP ("/etc/rc.d/init.d/inet restart" should work if you
haven't modified it).
(3) To see if sendmail is up, "ps fax | grep sendmail | grep -v grep".
If not, then check to make sure it's installed ("rpm -q
sendmail"), configured correctly (too lengthy to get into here,
though a default install should work in a vanilla fashion), and
started (via redhat's rc scripts, generally from
/etc/rc.d/init.d/sendmail).
(4) If you're typing it as "telnet 25", well, it's trying to find a
host with the name of "25". Try "telnet localhost 25" or use you
actual local hostname, and see what happens.
There are so many other issues possibly at work here ... make sure
these are okay before extending too far, though.
(There have been other suggestions to install qpopper, make sure
you're using imapd, etc. Though the suggestions may be good, I don't
think they are answering your question of whether sendmail is up and
running or not.)
-bill
--
William Evans < william . evans @ computer . org >
------------------------------
From: Ollie <[EMAIL PROTECTED]>
Subject: Re: fsck after power failure
Date: Sat, 04 Sep 1999 20:31:06 GMT
I am having a similar problem (I think)
I shut down my computer normally last night, but when booting this morning
I get an error message saying there was a problem with my file system on
/dev/hdc5 . After a series of tests it told me this:
"/dev/hdc5 : 2 inodes containing duplicate bad blocks
/dev/hdc5 File /var/log/wtmp (inode # 26587 has 6 duplicate blocks shared
with 1 file:
/dev/hdc5 File /var/log/messages (inode # 26535)"
It then goes on to say that I should "RUN fsck MANUALLY" and recommends I
use the -a or -p options. Then I get dropped into a shell and am asked for
my root password.
So I enter my root password and try "fsck -a" but it doesn't seem to do
anything. it just tells me what version of fsck I have and returns me to
the prompt. same thing for "fsck -p", "fsck --help" and "fsck -?"
Rebooting after each of these attempts changes nothing to the error
messages during boot-up.
Also, where it asks me to enter my su password it also says that I can do
Control-D to continue a normal boot-up. but it doesn't work. All it does is
re-boot and I end up where I started.
I am very new at Linux so I really don't have a clue what to do next.
If anybody can help that would be greatly appreciated.
Ollie
[EMAIL PROTECTED]
Jim McIntyre wrote:
> I recently had a power failure and lost my system. Upon reboot, I had
> numerous file system errors. I ran fsck several times, and got rid of
> all problems except for the partition containing /usr. After 45 minutes
> of trying, I could not go into a normal boot, since fsck could not clear
> up all the problems on this partition. I don't have a ups or a Linux
> compatible backup device (Syquest Sparq 1 gb external ide).
>
> Are there any other methods or tricks I could use to correct a file
> system. It is unacceptable for me to have to reinstall. Maybe I could
> sue some options with fsck, or a third party utility.
> Any help is greatly appreciated
> Thankx in advance.
>
> Jim McIntyre
> Webmaster Program
> Dalhousie University
> Halifax, Nova Scotia
>
>
================== Posted via CNET Linux Help ==================
http://www.searchlinux.com
------------------------------
From: [EMAIL PROTECTED] (noname)
Subject: Linux Software Archive + more
Date: Fri, 03 Sep 1999 20:43:31 GMT
Hi
http://mylinuxworld.virtualave.net
includes a new Linux Help Forum for beginners and advanced users. This
forum is still new, so start posting. But the main feature of this
site is its software archive for Linux.
Check out this site now.
------------------------------
From: [EMAIL PROTECTED] (Randall Parker)
Crossposted-To:
comp.os.linux.development.apps,comp.os.linux.development.system,comp.os.linux.x
Subject: Re: Shutdown Problem
Date: Sat, 4 Sep 1999 13:24:27 -0700
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] says...
> I'm no expert on the subject, but couldn't you use the -sync option, so that
> all filesystem writes are done with no write-behind?
The BSDs let you just do sync on the metadata. That way it is less likely
that inconsistent metadata will render a partition unreadable. Its a nice
tradeoff between the performance improvement of asynchronous writes and
the resistance to corruption of asynchronous writes
>
> Just tossing out ideas here.
>
> GW
>
------------------------------
From: Mike Bosschaert <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: Re: Star Office 5.1 and KDE
Date: Sat, 04 Sep 1999 22:43:15 +0200
In your menu list, there is a item called 'Panel', which contains the
item 'Edit Menus'. Start that menu and you can customize the items in
the menus. You can also add new items (use right mouse button).
Succes
Mike
John English wrote:
>
> I've just installed Star Office 5.1, and the last thing the installer
> does is to say "updating your KDE desktop -- restart the desktop after
> this finishes" or words to that effect. When I restart my desktop
> there doesn't seem to be any change. No new menu items, no new desktop
> icons.
>
> So, can anyone tell me how to make Star Office appear as (a) an icon
> on the desktop toolbar, or (b) a menu item? At the moment I have to
> open a terminal window and start it from the command line...
>
> And in general, how do you set up KDE menu items and icons?
>
> TIA,
>
> -----------------------------------------------------------------
> John English | mailto:[EMAIL PROTECTED]
> Senior Lecturer | http://www.it.bton.ac.uk/staff/je
> Dept. of Computing | ** NON-PROFIT CD FOR CS STUDENTS **
> University of Brighton | -- see http://burks.bton.ac.uk
> -----------------------------------------------------------------
------------------------------
** 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
******************************
