Subject: Linux-Admin Digest #205
From: Digestifier <[email-masked]>
To: [email-masked]
Date: Sun, 16 Oct 94 20:14:33 EDT

Linux-Admin Digest #205, Volume #2               Sun, 16 Oct 94 20:14:33 EDT

Contents:
  Future Domain SCSI-x All in One (Thomas Aeby)
  Re: Why aren't runlevels used more? (H. Peter Anvin)
  Re: more LEDs? (Brian Lane)
  Re: shadow-332: -f bug present (Patrick D. Ashmore)
  Re: XFree86-3.1 - Whoopee! (Richard W Kaszeta)
  Re: Broken pipe,x,client error (Joerg Fries)
  Help! Probelms w/new kernel booting :( (Frederick Smith)
  Re: Whats wrong with sunsite.unc.edu? (Rob Kean)
  Re: Slackware color xterm (Stormy Henderson)
  Problem with olvwm of XFree86 v2.11 (Rick Crow)
  Re: /tmp/ is not cleaned up (Rob Ransbottom)
  Re: HD Timeout problems (Mikael Nordqvist)
  SLIP/PPP and talk (Dopey (Andy Wang))
  Re: Kernel getting too big ? (was: Re: LILO error message question) (Eric V. Bruno)
  mgetty -- how to setup?? (To Siu Pong (BACS2 student))
  Re: source code of zless - Where? (Austin Donnelly)
  ftape driver for 1.1.49 ?
  Re: PPP indirectly?? (Al Longyear)
  Diskless linux boxes (Mike Cruse)
  Re: RPC info / setup (Polaris)
  Re: Telnet in is slow (Orjan Stromberg)

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

Crossposted-To: comp.os.linux.help,comp.os.linux.misc
From: [email-masked] (Thomas Aeby)
Subject: Future Domain SCSI-x All in One
Reply-To: [email-masked]
Date: Fri, 14 Oct 1994 17:56:05 GMT

I have got the kernel 1.00 running and the chance to get an Future Domain
SCSI-1 All in One plus (with TMC-950) or a SCSI-2 All in One (with TMC-1800)
quite cheap. Now I wonder if anyone has got any experience with one of them
- most important if they are supported or not (the doc is not fully clear -
it says "Seagate .../Future Domain ... TMC-950" with some problems, "Future
Domain 16x0 with TMC-1800" - I don't know if the SCSI-2 board is compatible
with any 16x0 board).

Sorry if this question was treated here already - I've just joined the group
(yeap, I know - strongly against netiquette).
And again against netiquette: Could you please answer through Email as my
newsfeed isn't too stable at the moment and I could easily miss an article.
I'll post a summary if something of common interest arrives.

Thank you very much for any help!

Bye,
Thomas
-- 
Thomas Aeby, Graeffet 406, 1735 Giffers, Switzerland, Voice : (+41)37 381600
Internet: [email-masked]                  PGP public key available
============================================================================
UNiX is like Sex:   If you don't know it, you don't miss is.
                    But if you know it, you'll need it.
                    But if you know it, you'll need it.

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

From: [email-masked] (H. Peter Anvin)
Subject: Re: Why aren't runlevels used more?
Reply-To: [email-masked] (H. Peter Anvin)
Date: Sat, 15 Oct 1994 04:52:13 GMT

Followup to:  <[email-masked]>
By author:    [email-masked]
In newsgroup: comp.os.linux.admin
>
> Runlevels seem to be somewhat underused in current Linux distributions.
> 
> For example, it should be fairly easy to set up /etc/inittab so that
> on level 4, there's multiuser capability (from different consoles),
> but no networking.
> 

The point of runlevels, beyond basic single/multiuser, is dependent on
your configuration.  For most installations I think you'd find that
multiuser without networking is meaningless.

        /hpa

-- 
INTERNET: [email-masked]             --- Allah'u'abha ---
IBM MAIL: I0050052 at IBMMAIL     HAM RADIO:   N9ITP or SM4TKN
FIDONET:  1:115/511 or 1:115/512  STORMNET:    181:294/1 or 181:294/101
First hug free; all subsequent ones free.

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

From: [email-masked] (Brian Lane)
Subject: Re: more LEDs?
Date: 16 Oct 1994 12:21:52 -0700

Steven M. Doyle ([email-masked]) wrote:
: I am interested in undertaking a programmable LCD project, perhaps using /dev/lcd
: device name, connected to parallel port if possible or bus if necessary.  All I
: would need is someone to write the kernel driver :)

  I don't think we need to do a device for it. Just a simple daemon to 
wake up every xx seconds, read info to display, write to LCD, adn go back 
to sleep should work. I have a 16x2 LCD that I wired to my parallel port 
last night working okay. I'm working on the daemon to display 
loadaverages, users and memory usage.

  It's also possible that I may be able to connect it so that the printer 
can be used as well(LCD code would have to make sure the printer was not 
in use before writing to the LCD).

    Brian

-- 
==============================================================================
"A little rebellion now and then is a good thing." | finger [email-masked] 
 President Thomas Jefferson                        | PGP 2.6 email accepted
==============================================================================

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

From: [email-masked] (Patrick D. Ashmore)
Subject: Re: shadow-332: -f bug present
Date: 14 Oct 1994 19:28:29 GMT

Harald Milz ([email-masked]) wrote:
> I installed the shadow-3.3.2 suite a couple of minute ago and found
> that the old -f bug is again in there. What's wrong?

Get the shadow suite and appropriate bins from 
ftp.procyon.com:/pub/linux/shadow. It's protected against the -f "bug."

Patrick

--
Patrick D. Ashmore          Network Administrator         1322 W. Cleveland
[email-masked]              Procyon  Networking       Fayetteville,  AR 72701
Finger for PGP key      URL: http://procyon.com/~pda/      +1 501 443 4393
[email-masked]                 [email-masked]            publius  enigma

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

From: [email-masked] (Richard W Kaszeta)
Subject: Re: XFree86-3.1 - Whoopee!
Date: 16 Oct 1994 19:25:48 GMT

Kevin C. Fandre (kfandre@comp..uark.edu) wrote:

: Does Xfree86 3.1 "feel" like a memory hog to anyone?  I've recompiled
: everything I regularly use, fvwm and all, to use the X11R6 libraries
: and it still feels like the hard drive has to thrash a bit to even run
: a few measly xterms and xtetris.

For just simple stuff, like twm and xterm, 3.1 runs noticeable faster.
Much of this however could be do to changes in the Mach32 driver.

One important thing I've noticed is problems recompiling under 3.1
involving ld. My copy of ld (slackware 2.0.1) is hard-coded to use
libs in /usr/X386, so even when I thought I was fixing the problem, some
old libs were being loaded (try running ldd on some of your favorite
executables).

Any ideas how I can _neatly_ fix this system?

Rich

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

From: [email-masked] (Joerg Fries)
Subject: Re: Broken pipe,x,client error
Date: 14 Oct 1994 12:29:37 GMT

Erich E. Singer ([email-masked]) wrote:
> help :
>
> my video card is ATI Mach64, monitor is Gateway 2000,
> crystal scan. Since there is no batabase for my card
> from modeDB.txt, I just chose vgawonder as my shipset,
> and set vgawonder's clock as my clock. resolution
> I chose 1024x768, 800x600,640x480.
> After I run stratx(I use XF86_SVGA as my server),
> machine can detect the clocks,mode,virtual resolution,
> but gives me info like this:
> XIO :fatal IO error(Broken pipe) on X server ":0.0"
> after 386 requests(390 known proceeed) with 0
> events remaning.
> waiting for X server to shutdown
> xinit:Unknown error(error 0):client error.
> .................................................
> did anybody have the same experience?
> pls let me know! many thanks!!!

I think this is no video card problem. The line
> xinit:Unknown error(error 0):client error.
tells about a client error. Perhaps there is something wrong in
$HOME/.xinitrc or in the global xinit file.

But there is another possibility: Be sure that your mouse is correctly
installed. X tries to initialize it and if the entry in XConfig is
wrong or the mouse is not connected, you get this error (its error 0...).

To the error
> XIO :fatal IO error(Broken pipe) on X server ":0.0"
> after 386 requests(390 known proceeed) with 0
> events remaning.
: This message will always appear when you shutdown the Xserver but
you have running clients on this server. Maybe the last entry
in your ~/.xinitrc is fvwm, the window manager. If you kill him with
'exit fvwm', the Xserver will be shutdowned. If there is a xterm
running this client will announce you the message showed above.

Hope that helps,

Joerg
(please answer via email...)
--

==============================================================================
Joerg Fries
Department of Computer Science
Technical University of Darmstadt, Germany

email: [email-masked]
==============================================================================

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

From: [email-masked] (Frederick Smith)
Subject: Help! Probelms w/new kernel booting :(
Date: 16 Oct 1994 15:20:39 -0400

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

From: [email-masked] (Rob Kean)
Subject: Re: Whats wrong with sunsite.unc.edu?
Date: Sun, 16 Oct 1994 15:37:21

>>I have been trying to access sunsite for the last several days.
>>Sometimes I am able to, but most of the time I get the following
>>error message:

>>250 CWD command successful.
>>ftp> ls
>>200 PORT command successful.
>>425 Can't create data socket (198.86.40.81,20): Address already in use.
>>ftp> ls
>>200 PORT command successful.
>>425 Can't create data socket (198.86.40.81,20): Address already in use.

>>First:  Does anyone know when/if sunsite is going to be fixed?

>>Second:  Does anyone know a mirror for sunsite, preferably close to
>>California?

>I have the same problem. It is very frustrating. Anybody knows more about this?

>Bart.

>------------------------------------------------------------------------------------
>Bart Kindt (ZL4FOX) System Operator, Efficient Software NZ LTD, Dunedin, New Zealand
>------------------------------------------------------------------------------------

wuarchive.wustl.edu echoes both sunsite.unc.edu and tsx-11.mit.edu.....

rhk

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

From: [email-masked] (Stormy Henderson)
Subject: Re: Slackware color xterm
Date: 16 Oct 1994 12:12:26 GMT
Reply-To: [email-masked]

Daniel M. Coleman wrote:

   I recently downloaded the slackware distribution, and I noticed that some of
   the default settings on the color_xterm are not quite right.  Whenever I press
   the backspace key, instead of backspacing, it acts as if I had pressed the
   enter key.  The normal (noncolor) xterm works fine.  What could be wrong?

I've had this problem too, except it's not acting like I've pressed enter, 
because it ignores my input, more like just a newline and carriage return 
while clearing the input buffer.

Anyway, I noticed that the ONLY time this happend was when I logged out of 
the shell calling openwin BEFORE the xterm was started, as in exec openwin or
simply typing openwin & and then hitting control-d to logout.

I never found a solution, cept for waiting till X was done booting before I
exited my console shell.

Be happy...

- Stormy the happinator     "The Moving Finger writes; and, having writ
                             Moves on: nor all your Piety nor Wit
  Reply to:                  Shall lure it back to cancel half a line, 
  [email-masked]       Nor all your Tears wash out a Word of it."

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

From: [email-masked] (Rick Crow)
Subject: Problem with olvwm of XFree86 v2.11
Date: Fri, 14 Oct 1994 16:08:50

Hi!
                 This is probably another stupid question, but I need help. I 
am running slackware ver 2.0.1 with XFree86 v2.1.1 and when I use Fvwm I can 
access all my apps, but when I switch to olvwm I can't access half the stuff 
on the pull down menu to include: X11 programs, XVIEW programs, Games, Tools,  
and windows menus. I just installed x windows, x apps, and the xv series 
(virtual). Is there some type of configuration required to get olvwm to work? 
I would greatly appreciate any help anyone could provide.

                                                                 Thanks,

                                                               Rick Crow

[email-masked]       

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

From: [email-masked] (Rob Ransbottom)
Subject: Re: /tmp/ is not cleaned up
Date: Sat, 15 Oct 1994 03:13:11 GMT

In article <[email-masked]>,
Patrick J. Volkerding <[email-masked]> wrote:
>In article <[email-masked]>,
>Srihanto A. Nugroho <[email-masked]> wrote:

>>Is there any reason for not cleaning up /tmp directory when the system boot ?

>It will if you add this to /etc/rc.d/rc.local:
>( cd /tmp ; rm -rf * )

>Since I'm not the admin for your machine, it would be presumptuous of 
>me to clear out your /tmp automatically.  What if you'd put something 
>important in /tmp and didn't know Slackware was going to wipe it out on 
>your next reboot?  Policies like the wiping of /tmp are best determined 
>locally.  (That way, someone can be blamed locally ;^)

I can appreciate your consideration.  

Files in tmp directories should NEVER be expected 
to outlast their related processes.

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

From: [email-masked] (Mikael Nordqvist)
Subject: Re: HD Timeout problems
Date: 16 Oct 1994 12:33:17 GMT

Cc: 

In article <[email-masked]> [email-masked] writes:
>Hi, 
>  I keep getting hd timeout errors, here is the exact message:
>Oct 15 22:32:58 Satsuma kernel: HD timeout
>Oct 15 22:32:58 Satsuma kernel: HD-controller reset
>Oct 15 22:32:58 Satsuma kernel: HD: win_result: status = 0xff
>Oct 15 22:32:58 Satsuma kernel: HD: win_result: error = 0xff
>Oct 15 22:32:58 Satsuma kernel: harddisk I/O error
>Oct 15 22:32:58 Satsuma kernel: dev 0341, sector 8
>Oct 15 22:32:58 Satsuma kernel: HD-controller reset
>
>Anyone got any ideas? It all started when I put my new hard disk in. 
>A seagate ST5660A (540Mb) it's set to 504Mb though; to stop things complaining.
>I'm using 1.1.53 but I tried 1.0 and it gave me the same error.
>Can anyone help? is anyone having the same problem ?

I got the same drive (isn't it a small mean little black box? :-) and
I get those "HD timeout" too. But never the other errors.

The reason (in my case at least), is that the drive has to spin up
after the power-saving has done it's job. The whole systems freezes for
about a second, then everything is fine again. This was discussed on
the KERNEL-channel a while ago. Don't know if it'll be fixed or not.

I am using the full capacity without problems (fdisk complains, but that
is no "real" problem). I only use it for Linux though.

/Mikael
-- 
Mikael Nordqvist, student    | [email-masked] | I'm not paraniod, it's just
Lund Institute of Technology | [email-masked]   | that everyone is out to get me

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

From: [email-masked] (Dopey (Andy Wang))
Subject: SLIP/PPP and talk
Date: Sun, 16 Oct 1994 19:39:19 GMT

does anyone know how to get talk to work over a slip or ppp connection?
talk requests cmoe in fine.
but if i try to respond. or talk to another machine it gives me
a message checking for invitation on caller's machine.
and then it just sits there..
anyone know how to fix this?

-- 
*******************************************************************************
* Life's Great Mystery:   * Legalize Marijuana * [email-masked]       *
* Do I really exist or am * Don't let the      * [email-masked]     *
* I just a dreamer afraid * government fuck up * [email-masked]     *
* to wake up and live?    * your rights.       * [email-masked] *
***************************** Dopey (Andy Wang) *******************************

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

From: [email-masked] (Eric V. Bruno)
Subject: Re: Kernel getting too big ? (was: Re: LILO error message question)
Date: Wed, 12 Oct 1994 16:16:22 GMT

Werner Almesberger ([email-masked]) wrote:
: In article <[email-masked]> [email-masked] (Eric V. Bruno) writes:
: > Kernel vmlinuz too big!

: Ugly. Either something's broken or your kernel is really too big (are we
: already at that point again ?). Maybe leaving out some non-essential
: device drivers and other kernel features would shrink it to a more
: reasonable size.

  The file was 1.3 meg I created the file by cp /dev/fd0 vmlinuz
  the Kernel was compressed on the floppy.  I have since built
  a custom kernel with only the hardware I need for my system and
  that works fine since it is much smaller.

: > What is this really telling me?

: This tells you that LILO thinks your kernel would be too big to load.
: Either LILO is wrong or what it thinks is the kernel isn't or the
: (compressed) kernel is really bigger than half a megabyte. (Re-building
: the kernel and examining the paths listed in /etc/lilo.conf should help
: eliminating the first two (unlikely) possibilities.)

: Has anybody seen this problem too ? Is it time to finally start the
: heavy rewrite to run LILO in protected mode ? :-(

: > Do I need to leave more room before defining partition 1.

: No, that's not a failing copy operation. LILO typically only allocates
: a few kB of disk space.

: - Werner
: -- 
:    _________________________________________________________________________
:   / Werner Almesberger, sending this from    [email-masked] /
:  /[email-masked]/

Perhaps this information on size limitations could be added to Matt Walsh's
Linux Manual (which is one of best Install/Getting Started Manual's I have
seen in 20 years of working with computer systems).  Also perhaps this 
information could be added to the FAQ's on building kernels?  These
are the first to spots I looked and came up dry.

===============================================================
|Eric Bruno, Santa Clara, CA       | All opinions are my own. |
[email-masked]               |                          |
|CompuServe ID - 71540,36001       |                          |
===============================================================

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

From: [email-masked] (To Siu Pong (BACS2 student))
Subject: mgetty -- how to setup??
Date: Sun, 16 Oct 1994 05:53:20 GMT

Hello all,

        I've got the mgetty and have installed, however how can I config
        it??  The modem doesn't answer when a there's a call and when
        I type "mgetty", it said that

                        mgetty FATAL : no line give 

        What should I do now??

Danny To
[email-masked]
[email-masked]

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

From: [email-masked] (Austin Donnelly)
Subject: Re: source code of zless - Where?
Date: 16 Oct 1994 13:55:32 GMT

In article <[email-masked]>,
Jozsef Kadlecsik <[email-masked]> wrote:
>Hello,
>
>Where can I find the source code of zless?
>I tried to find it from the LSM, by archie, nothing.
>Could somebody help me?

You can use a shell script to do zless:

========== cut cut cut ==============
#!/bin/sh
for args
do
   zcat $args | less
done
========== cut cut cut ==============

Save this as a file called zless, and do a chmod 755 on it to make it
runnable.

Austin

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

From: [email-masked] ()
Subject: ftape driver for 1.1.49 ?
Date: Sun, 16 Oct 1994 11:35:51 GMT

I have compiled 1.1.49 - make config asked if I wanted ftape
(I chose yes) but I do not seem to have a /dev/ftape or
for that matter any ftape source code.

Is ftape now a module - if so where is it, and why does
make config still ask about it ???

Steve Hunt    [email-masked]

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

From: [email-masked] (Al Longyear)
Subject: Re: PPP indirectly??
Date: Sat, 15 Oct 1994 02:28:02 GMT

[email-masked] (Donald Griffin (CE)) writes:

>I am interested in setting up a PPP link to put my linux box on the 
>internet.  I used to live in a location where I had root access to a 
>machine on the internet and I have since moved to a place where I just 
>have dial-up access.  Would it be possible for me to set up the PPP 
>client on my Linux box and then dial-up -> telnet into the machine that I 
>have root privledges on to complete the PPP connection (I dont think this 
>is possible without some sort of mod to the code or addition).

You're out of luck. The kernel must be built to support the PPP devices.
In addition, the pppd process must be run from root or suid to root to
allow the ioctl operations needed to establish the PPP connection.

If the remote admin did not suid the pppd process to root then there is
nothing that you can do to make it so.

You will be able to use the term link.

From what I hear, there is a Linux port of "TIA" in the plans. This would
give you natural SLIP and (probably by that time) PPP.

-- 
Al Longyear           [email-masked]

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

From: [email-masked] (Mike Cruse)
Subject: Diskless linux boxes
Date: 16 Oct 1994 13:03:15 -0700

Does anybody know where I can get source for NE2000 boot
roms using the BOOTP protocol. I want to set up some 
diskless linux boxes and have them boot off a Linux
BOOTP server. I have bootpc working pretty well on the 
server with a single floppy kernel boot disk. It works 
fine but it's a little slow to boot and floppy disks don't
last for ever.

Has anybody done this before? 

Thanks, 

Mike

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

From: [email-masked] (Polaris)
Subject: Re: RPC info / setup
Date: Fri, 14 Oct 1994 13:14:31 GMT

[email-masked] (Robert Sink) writes:

>I have installed a couple rpc functions on my system primarily just to 
>learn what all is entailed.  I have my inetd.conf set up correctly, I have
>/etc/rpc, I run rpc.portmap and I have this one problem.  I was under the
>impression that inetd would run rpc.rusersd apon receiving the request,
>however it does not.  It just sits there and the other end gets RPC:
>program not registered.  However, if I type rpc.rusersd beforehand and
>load it up, it works fine.   Is this correct, or am I missing something?

rusers doesn't connect directly to the rusersd. It first contacts the portmap
to see if rusersd is registered, and asks what port it is on. When you run
rpc.rusersd it registers itself with the portmap. You have to start up all
your rpc services manually, not with inetd.

                                Richard.

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

From: connor@tekla (Orjan Stromberg)
Subject: Re: Telnet in is slow
Date: 16 Oct 1994 14:44:03 GMT

Scott Jennings ([email-masked]) wrote:
: Orjan Stromberg (connor@tekla) wrote:
: : The lines out are as fast as you can possible wish, but as soon as I try to
: : telnet in to the machine it goes SLOOW. People have been telnetting into the
: : machine, and stopped at the login for five minutes. If I check locally, they
: : are logged in, but they are still stuck on the login-screen.

: Are they using BASH?

Everybody is using TCSH. Some of the users have an old .bash_history, but
not the ones with problems. :)

  /Orjan

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

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