Subject: Linux-Admin Digest #164
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Sat, 8 Oct 94 16:13:35 EDT

Linux-Admin Digest #164, Volume #2                Sat, 8 Oct 94 16:13:35 EDT

Contents:
  Re: Is there a firewall for slackware? (Andrew PRUSEK)
  Puzzle (Dongxiao Yue)
  Q: Max # of ftp/gopher/http users on a Linux PC? (Warren Ernst)
  Need advice on terminalservers (Ron Arts)
  Re: SCSI vs IDE (Drew Eckhardt)
  Re: Yggdrasil & large SCSI disk??? ([email-masked])
  Re: Installing XFree 3.1... (Andre Schoorl)
  Re: Fast Scsi-2 COMPAQ (Anthony Marriott)
  dip-3.3.7h-uri & Zyxel U1496E SOLVED!!! (Dirk Hillbrecht)
  Re: CDD-522 recorder (or any other) on a linux box (Roger C. Pao)
  Re: Dial-in and Dial-out on one modem? (Mark A. Horton KA4YBR)
  Re: packet size w/ uucp? (Mark A. Horton KA4YBR)
  Re: Modem Question .. (Mark A. Horton KA4YBR)
  Re: booting in single user mode? (Mark A. Horton KA4YBR)
  Re: Upgrade SLS .99.12 to current (Tom Wilson)
  Re: XFree86-3.1 - Whoopee! (Rene COUGNENC)

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

From: [email-masked] (Andrew PRUSEK)
Subject: Re: Is there a firewall for slackware?
Date: Fri, 07 Oct 1994 13:42:24 +0930

In article <[email-masked]>, [email-masked]
(The Weasel !!) wrote:

> We are tring to setup a firewall to help protect data on our system.
> Is there a firewall out there for slackware? I need to install it
> on our gateway linux box.

You need to take your kernel to about 1.1.49 and apply the ipfirewall patch
then take a look at:

tcp-wrapper
socks
fwtk (ftp.tis.com)

regards
Andrew

-- 
Andrew PRUSEK                         Phone: +61 86 40 4590
BHP Information Technology              Fax: +61 86 40 4720
PO Box 21 / Port Augusta Road         Email: [email-masked]
Whyalla SA 5600                 Prefered OS: Linux
Australia                        Disclaimer: My opinions are my own.

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

From: [email-masked] (Dongxiao Yue)
Subject: Puzzle
Date: Sat, 8 Oct 1994 00:59:50 GMT

Hi, Hackers,

  I recently had a problem running dip, whenever I run
  it for the first time AFTER A COLD REBOOT, I get errors
  "getc: I/O error". However after the first time, I can run it
  without any problem, even if I warm reboot the system(say run
  dos for a while).

  This puzzles me, hope some of you knows the answer and kindly
  tells me, so I can correct the problem.

  Thanks,

  Dongxiao

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

From: [email-masked] (Warren Ernst)
Subject: Q: Max # of ftp/gopher/http users on a Linux PC?
Date: 6 Oct 1994 15:09:04 -0700

All,

Our company is considering making a Linux equipped PC an ftp/gopher/http
server, but I don't know if such machines are able to handle the load. We
will ultimately be giving the machine its own router and 56k line, but we
have no idea what CPU's are appropriate -- 486 DX2/66, P60, P66, P90,
etc. The PC would have 16 Meg ram and at least a gig SCSI drive.

What I'm really looking for is something like: "a 486-66 starts to bog
down at 100 ftp logins transferring data out, but a p60 could take at
least 400 without breaking into a sweat".

We aren't sure what the average size of concurrent ftp/http accesses will
be, but we would like to be more than 200. If a Linux PC is simply
incapible of doing this, we would probably get a used Sun.

Feel free to email or post your answers. I could really use your help. Thanx

Virtually,
warr
/-----------------------------------------------------------------------\
| Warren Ernst      \ Computer Consultant / "Never quote me on this..." | 
| [email-masked]     \ Technical Writer  / "Overclock - it's your 486." |
| Fullerton, CA, USA  \  Graphic Artist / "Llama, llama, llama, llama!" |
| Will Write for Food  \     Nerd      / "I'm EXACTLY one Warren tall." |
\-----------------------------------------------------------------------/

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

Crossposted-To: comp.unix.admin
From: [email-masked] (Ron Arts)
Subject: Need advice on terminalservers
Date: Sat, 8 Oct 1994 20:49:04 GMT

(If someone knows a better group to post this please say so)

I'm expanding the number of dial-up lines to my unix box, and am thinking
of installing a terminal server.
Now I need some advice. Which kinds/brands are there? Is there a FAQ for this?
It should support SLIP/PPP, and shouldn't be too expensive of course.

Thanks for any info,
Ron Arts

PS: please email me, I'll summarize if requested.

--

NetLand Internet Services - Email, Usenet, gopher, WWW, ftp, telnet etc
We also set up Internet-connected BBS'es or a WWW server for your organisation
Info: +31-(0)20-6943664, dial-up +31-(0)20-6940350, Email: [email-masked]
<A HREF = "http://www.netland.nl/">Info</A> (dutch language only).

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

From: [email-masked] (Drew Eckhardt)
Subject: Re: SCSI vs IDE
Date: 5 Oct 1994 17:26:27 GMT

In article <[email-masked]>,
George R. Welch <[email-masked]> wrote:
>In article <[email-masked]>,
>Iain J. Bryson <[email-masked]> wrote:
>>Hi.  I am interested in hearing people advocating
>>which is better, IDE or SCSI.
>
>       While we are wading through the wave of followups, how about
>someone explaining the difference between all the SCSI.  I have heard of
>SCSI

The original SCSI standard.

>SCSI-2

SCSI-2 introduces a number of interesting new features, such as 
tagged queing which allows you to send multiple commands to a device 
and let it order them optimally and pipeline processing and execution,
standard audio commands for CD ROMs, etc.

However, nearly everything new in SCSI-II (and SCSI-III for that
matter) are options and not mandatory, and SCSI is backwards compatable.  
So, if you didn't do anything silly (ie, choose the SCSI-I single 
initiator option), your marketing department can promote your 
SCSI-I host adapter to SCSI-II or even SCSI-III if they want.

>fast SCSI-2

Standard SCSI allows for 5Mhz synchronous transfers, the fast option
allows for transfers between 5 and 10Mhz. 

>wide SCSI

Standard SCSI is eight bits wide, where as WIDE scsi is sixteen
bits wide, allowing for fifteen devices instead of seven, and 
double the transfer rates.

There are some provisions for 32 bit WIDE SCSI, but I haven't 
seen any devices.

>and AV-SCSI

Drives made for AV applications won't drop out for thermal 
recalibration (ie, they'll either not do it ever, or will abort 
if a command comes in) so you have the necessary guaranteed 
maximum response time.

>Which is best?  

Fast+Wide SCSI-III, differential and not single ended.

Of course, you will pay hundreds (if not thousands) of dollars 
in the premiums for wide and differential devices...

>Which is worst?  How do you tell which one you have?

If you're talking about SCSI targets, you ask them with a SCSI
INQUIRY command.  They'll tell you what revision of the specification
they conform with, what options they support, who made them, and 
all sorts of other good stuff.

The Linux kernel does this at bootup, so it will be in your 
kernel messages.  

Or you can run the scsiinfo program.

>Are any of them compatible with the others?  

With the exception of single ended/differential, unless you've done
something really stupid when you wrote the firmware, they're all compatable.

>Why is this not addressed
>in the SCSI-Howto?

Because it isn't yet.

There will be something in the next revision which will detail the 
differences between the various revisions of the specification, 
the options allowed in each one, and the practical ramifications 
thereof.
-- 
Since our leaders won't respect The Constitution, the highest law of our 
country, you can't expect them to obey lesser laws of any country. 
Boycott the United States until this changes.

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

From: [email-masked]
Crossposted-To: comp.os.linux.help
Subject: Re: Yggdrasil & large SCSI disk???
Date: Thu, 06 Oct 94 21:44:05 PDT

In article <[email-masked]>, <[email-masked]> writes:
> 
> I dunno if this will help you any, but what I did with my ncr5380 generic 
> driver (which can't read geometry either) was to boot up DOS and run my 
> old DOS format utility (SpeedStor in my case) and it showed me the right 
> values for the drive, which I then wrote into the front of my linux manual.
> 

Jeff,

as it turned out, the Summer '94 Yggdrasil has a Rev. B boot diskette
(available via ftp) which supports the NCR 53C810 SCSI chip. So you can
install Linux this way. But since the 1.0.19 kernel is not on the CD-ROM,
it does not get copied to the SCSI disk - and you get an unbootable
system. 

This is probably good enough if you have an IDE disk plus a SCSI disk
hanging off the NCR chip. Then you can install from CD-ROM with the Rev.B
boot disk and replace the kernel by the one from the boot disk. But it
doesn't work too well if the SCSI disk is all you have.

I installed the Slackware distribution in the meantime and everything
works fine (after I figured out how to install the undocumented "NCR"
disk set...).

Karl Finkemeyer, [email-masked]

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

From: [email-masked] (Andre Schoorl)
Subject: Re: Installing XFree 3.1...
Date: Thu, 6 Oct 94 22:37:26 GMT

In article <[email-masked]>,
FORSEILLES STEPHAN <[email-masked]> wrote:
>
>        I've been triyng for some time to get XFree 3.1 working with
>my Nr9 GXE/64 video card. The problem is that it doesn't seem to be any clock
>rate that matches the rates of the card on the examples files. In fact
>I think the problem comes from somewere else: XFree seems to be unable
>to detect corectly the clocks of the card. Here's what it gives:
>
>(--) S3: card type: 386/486 localbus
>(--) S3: chipset:   864 rev. 0
>(--) S3: chipset driver: mmio_928
>(--) S3: videoram:  1024k
>(--) S3: Detected an ATT 20C498 RAMDAC
>(--) S3: Ramdac type: att20c498
>(--) S3: Ramdac speed: 135
>(--) S3: clocks:  25.21  28.32  28.32   0.00  25.16  28.31  28.38  28.35
>(--) S3: clocks:  25.16  28.32  28.32  28.32  25.17  28.32  28.32  28.49

I have the #9GXE64 as well, and had similar problems.  Use
ClockChip = "icd29061a"  ( I think, check the icd* though )
in your XF86Config.

All resolutions work no problem for me now. :^)

-- 
Andre Schoorl <[email-masked]>   PGP key available via finger/keyserver
C.Eng Student, U.Vic, Canada.  -> LINUX! <- http://www-engr.uvic.ca/~aschoorl

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

From: [email-masked] (Anthony Marriott)
Subject: Re: Fast Scsi-2 COMPAQ
Date: Thu, 6 Oct 1994 15:15:36 GMT

Please e-mail me if you figure out how to get linux
running on a Compaq server (in my case I have a proliant 
1000 with a pentium processor).

Since SCO/Unix and Novell/Netware run on this
machine, I assume linux could run on this machine. 
I guess linux is not considered strategic to Compaq.

Anyway, I do not have the time to play infinite
loops with Compaq or to write the drivers myself.

Oh well...

For now, I assume linux will not run on my Compaq
until I buy different hardware.

NOTE: I have cross posted the same question to a couple
      of other linux groups very few replies?

-Tony-

Anmar, Inc.
Anthony R. Marriott

---

Bret A. Johnson ([email-masked]) wrote:
: Hello all,

: I am tryingto install Linux Slackware Pro. ver. 2.0 on a Compaq
: server.  However, when the boot disk boots it does not see teh Scsi card.
: It is a compaq fast scsi-2 card. Is there a driver I need to get for
: this to work?

: Can I infact run Linux on a compaq server?

: Any help is needed!!!!!
: Thanks...

: |-------------------------------------------------------------------------|
: | Bret Johnson                      Internet: [email-masked]         |
: | PGP Key Fingerprint = 1C BF 78 7C 62 2B 96 7F  F9 22 8D C5 A7 6C D4 37  |
: |-------------------------------------------------------------------------|

: -

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

From: [email-masked] (Dirk Hillbrecht)
Subject: dip-3.3.7h-uri & Zyxel U1496E SOLVED!!!
Reply-To: [email-masked]
Date: Fri, 7 Oct 1994 08:51:48 GMT

Hi everyone,

many thanks for all of you who replied by eMail or in this group. Meanwhile,
after some more excessive testing, I'm up and running with the two above!!!

The clue was the "dial"-command. Richard J Wyble <[email-masked]> wrote to
me, that

> This version of dip (and several preceeding it) have Hayes command-strings
> compiled in as default. Take a look at the source to see what it is actually
> sending to the modem when issued this 'dial' command.
>
> An alternate is to issue the dial string yourself, e.g., 'atdt1613075' and
> then 'wait CONNECT' . . .

I did the last one changing the dial-command into
send ATDT1613075\r

and it connected!

Another error was waiting for the wrong prompt afterwards. I recovered this one
by using the "debug" mode. It can be involved through

echo on

in the script file. After this, all output from the modem is echoed.

Once again, many thanks,

Cheers, Dirk

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

From: [email-masked] (Roger C. Pao)
Subject: Re: CDD-522 recorder (or any other) on a linux box
Date: Thu, 6 Oct 1994 04:02:02 GMT

[email-masked] (Me) writes:

>I'm looking into purchasing a Philips CDD-522 recorder, but most of the software
>that I've seen for writing disks is written for DOS or Windows, and tends to be
>more than $800.  I was cautioned against hanging a CD-recorder on *any*
>multitasking system.  Has anyone had successful experiences writing CDs under
>linux?  What software is used?  (Does one use one package to make an
>ISO-compliant disk image, and then another package to actually copy the image
>onto the CD-ROM?)  
> 
>Any information regarding CD-recorders on a unix box would be helpful.

CD recorders require a steady stream of data going from the hard disk
image to the CD recorder.  To guarantee this, you do not want background
tasks to spontaneously start up and disrupt this continuous stream.
I suppose if a driver and software were available, you could get it
to work if you kill crond prior to writing.

rp94
-- 
Roger C. Pao <[email-masked]>

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

From: [email-masked] (Mark A. Horton KA4YBR)
Subject: Re: Dial-in and Dial-out on one modem?
Date: Sat, 8 Oct 1994 02:02:42 GMT

Steve Miller ([email-masked]) wrote:
: Can I dial in and out over the same modem? I do this on SCO Unix machines 
: all the time with no problems. The dialer changes the modem settings
: to turn echo on to dial out (to detect "CONNECT" messages) and turns
: echo off when done. If I leave echo on, the port sees the login
: message echoed back and thinks someone is trying to login. This 
: causes TD and RD lights to be on all the time. If I run ps it tells
: me someone is logging in as "login: Welcome to ........." (whatever
: displays from the /etc/issue file and the login prompt). If I turn
: echo off (Q1E0) then cu never sees the "CONNECT" message. How can
: Linux change these settings each time I dial out, and change them
: back when I am done like SCO does?

        See the mini-HOWTO about getty_ps on sunsite.unc.edu in
        /pub/Linux/docs/....
        Should tell you what you need to make it all work.
        - Mark
----
"Linux!     Why waste your money on anything less? "
============================================================
Mark A. Horton       ka4ybr           [email-masked]
P.O. Box 747 Decatur GA US 30031-0747   [email-masked]
+1.404.371.0291 : 33 45 31 N / 084 16 59 W    [email-masked]

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

From: [email-masked] (Mark A. Horton KA4YBR)
Subject: Re: packet size w/ uucp?
Date: Wed, 5 Oct 1994 12:55:35 GMT

Kevin Cummings ([email-masked]) wrote:
: In article <[email-masked]>, [email-masked] (John Dee) writes:
: > Is there a way to increase packet size with UUCP to get a better transfer 
: > rate?

: Yes, change the protocol you are using.  "G" protocol is limited to 64 byte
: packets, but someone wrote up a "g" protocol which supports larger packet
: sizes (or do I have them backwards?).  BOTH ends of your UUCP connection must
: support it.  Login to your UUCP host by hand and check out the protocols it allows.
: Or increase your debugging output for one call and look in the log files for it.
: Then get some documentation on UUCP that describes the various protocols, and see
: what your options are.  (You could always get a faster modem, but that is probably
: not a useful answer B^).

Righto Kevin,

        Except "g" is the 64byte packets and "G" allows larger. 
        From the "info" entries supplied with Taylor UUCP:

The UUCP `G' Protocol
=====================
   The `G' protocol is apparently simply the `g' protocol, except that
it is known to support all possible window and packet sizes.  It was
introduced by SVR4 UUCP; the SVR4 implementation of the `g' protocol is
apparently fixed at a packet size of 64 and a window size of 7.  Taylor
UUCP does not recognize the `G' protocol.  It does support all window
and packet sizes for the `g' protocol.

        Also, if your Taylor uucp discovers that it's talking to another
        Taylor uucp, you can achieve much better throughput because,
        according to the file /usr/lib/uucp/README :

If you are talking to another instance of the package, you can use
the new bidirectional protocol for rapid data transfer in both
directions at once.  You can also restrict file transfers by size
based on the time of day and who placed the call.

                                and:

IMPORTANT: the default when talking to another version of 1.04 is to
use the new bidirectional 'i' protocol.  If you are using a
half-duplex modem, such as a Telebit T2500, you will want to either
mark the port as half-duplex with the ``half-duplex'' command, or
force use of the 'g' protocol by using the ``protocol'' command in the
sys or port file or by adding ``,g'' after the port name in the
Systems or L.sys or Devices file.

        Sadly, most instances of uucp out there are never set up to try
        any of the higher-density protocols and thus use the "g" 
        protocol as a default.  When you connect to them, the highest
        protocol supported by both systems is the one that wins the
        negotiation and you are usually stuck with "g" unless you are
        lucky enough to hit another Taylor.  :(

        -- Mark

--
"Linux!     Guerrilla UNIX Development     Venimus, Vidimus, Dolavimus."
============================================================
Mark A. Horton       ka4ybr           [email-masked]
P.O. Box 747 Decatur GA US 30031-0747   [email-masked]
+1.404.371.0291 : 33 45 31 N / 084 16 59 W    [email-masked]

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

From: [email-masked] (Mark A. Horton KA4YBR)
Subject: Re: Modem Question ..
Date: Wed, 5 Oct 1994 13:13:30 GMT

Tony_Teague ([email-masked]) wrote:
: hi, 
:   I want to set up my modem than is connected to my linux box to receive 
: incoming calls .. Can anyone tell me how to set it up or where I can get the
: information from .. 
:  
:                                                              tony 
 
The serial-HOWTO, the mini-getty_ps-HOWTO, the Network Administrators' Guide
from sunsite.unc.edu. in /pub/Linux/docs

--
"Linux!     Guerrilla UNIX Development     Venimus, Vidimus, Dolavimus."
============================================================
Mark A. Horton       ka4ybr           [email-masked]
P.O. Box 747 Decatur GA US 30031-0747   [email-masked]
+1.404.371.0291 : 33 45 31 N / 084 16 59 W    [email-masked]

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

From: [email-masked] (Mark A. Horton KA4YBR)
Subject: Re: booting in single user mode?
Date: Wed, 5 Oct 1994 13:19:59 GMT

CVL staff member Nate Sammons ([email-masked]) wrote:
: Can you issue a "boot -s" type command to get into single user mode?

: The problem is, my machine goes to init 6 (xdm) but X is not
: configured properly, so it sits there and flicks in and out of sync
: with the monitor, and I cannot do anything.  I need to be able to go in
: and change the initial init state of the machine, and the easiest
: way I can think of (with other UN*Xs) is to boot it into single user mode.

: Any suggestions?  (not in the FAQ that I could find)

        from /usr/src/lilo/README :

        Example:
        boot: linux single root=200

single  boots the system in single-user mode. This bypasses all system
initialization procedures and directly starts a root shell on the console.
Multi-user mode can be entered by exiting the single-user shell or by
rebooting.

root=<device>  changes the root device. This overrides settings that may have
been made in the boot image and on the LILO command line. <device> is either
a hexadecimal device number or the full path name of the device, e.g.
/dev/hda3  (The device names are hard-coded in the kernel. Therefore, only the
"standard" names are supported and some less common devices may not be
recognized.)

ro  instructs the kernel to mount the root file system read-only.  rw  mounts
it read-write. If neither  ro  nor  rw  is specified, the setting from the
boot image is used. no387  disables using the hardware FPU.
 
-- Mark 
--
"Linux!     Guerrilla UNIX Development     Venimus, Vidimus, Dolavimus."
============================================================
Mark A. Horton       ka4ybr           [email-masked]
P.O. Box 747 Decatur GA US 30031-0747   [email-masked]
+1.404.371.0291 : 33 45 31 N / 084 16 59 W    [email-masked]

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

From: [email-masked] (Tom Wilson)
Subject: Re: Upgrade SLS .99.12 to current
Date: 6 Oct 1994 22:59:58 -0400

In article <[email-masked]>, Steve Miller <[email-masked]> wrote:
:I dug up my old copy of SLS .99.12 and installed it without too much 
:trouble. Now I see everyone discussing 1.50 What are the advantages
:to upgrading and what is the least painful way to do it? Is there a
:way to just upgrade, or do I need to re-install? I dread the thought 
:of downloading all those disks again! 
:
:Will I get SCO Unix binary compatibility with this upgrade? Or is 
:that a seperate package I can add to my installation?

The best thing you can do is forget SLS and grab Slackware or one of
*many* CDROM distributions (or MCC-Interim [my choice] and build up 
from there ;-)

SLS *is dead*, and has been for quite some time.  Among ftpable 
distributions, slackware is currently king of the hill...reinstall
with slackware and I think you'll be pleased with what you get.
By all accounts, it's much (and much more mature, of course) better
than SLS ever was.

SLS'er flames to /dev/null.
-- 
/-----------------------------------------------------------------------\
|  Tom Wilson                      |  "I can't complain, but sometimes  |
|  [email-masked]       |   I still do."                     |
|                                  |                -Joe Walsh          |

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

From: [email-masked] (Rene COUGNENC)
Subject: Re: XFree86-3.1 - Whoopee!
Date: 6 Oct 1994 04:11:33 GMT
Reply-To: [email-masked] (Rene COUGNENC)

Ce brave Patrick J. Volkerding ecrit:

> libXpm-3.4c _seemed_ to compile fine under XFree86 3.1, but any apps 
> linked with the resulting shared library seg fault when executed.  The 
> static version of libXpm works, though.  (Mitch - are you planning to 
> look at this?)

Well, I tried it and... It works fine.
Make sure you have only the newly compiled libXpm-3.4c on your disk,
to avoid confusing ld and ldconfig...

I have now fvwm, with XPM stuff freshly recompiled under XFree 3.1
with the new libs and it works with no problems.

(But on a test directory, since I won't recompile all my clients and
 probably keep 2.1.1 for a while...)

--
 linux linux linux linux -[ [email-masked] ]- linux linux linux 

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

** 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-masked]

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

    Internet: [email-masked]

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

End of Linux-Admin Digest
******************************