From: Digestifier To: Linux-Admin@senator-bedfellow.mit.edu Reply-To: Linux-Admin@senator-bedfellow.mit.edu Date: Tue, 7 Dec 93 14:13:43 EST Subject: Linux-Admin Digest #208 Linux-Admin Digest #208, Volume #1 Tue, 7 Dec 93 14:13:43 EST Contents: XDM & sessreg (Benjamin Ryzman) Serial port blues with Slackware 1.1.0 (Rennolet Charles) A Linux Users Manual (John Will) Re: Linux as a DOS filese (John Will) Re: Linux as a DOS filese (John Will) Re: Linux as a DOS filese (John Will) Re: NFS-Problems, package > mtu (=1500) (Klaus-Georg Adams) Problem w/display after shutting down X server (ATI card) (Theodore J Hajek-1) ttyS1 time-out problem? (mlarkin) Serial IRQ problems. (Wolfgang Jung) Re: A Linux Users Manual (Kai Jendrian) SCSI Install Failure (Eric Keen) Re: Linux as a DOS fileserver? (Terrance M. Darcey, PhD) Re: How to get syslogd to listen to net (Scott W. Adkins) Re: Problem w/display after shutting down X server (ATI card) (Adam Karpowicz) Re: lpd (Robeo) Re: Serial IRQ problems. (Daniel M. Coleman) Re: Problem w/display after shutting down X server (ATI card) (Frank Lofaro) ---------------------------------------------------------------------------- From: zarkdav@zarkdav.frmug.fr.net (Benjamin Ryzman) Subject: XDM & sessreg Date: 5 Dec 1993 15:25:34 GMT I've got a problem using XDM with sessreg in my XStartup and XReset scripts: whenever it executes the line 'sessreg -a $USER' or 'sessreg -d $USER' or the BSD variations of them (although I think the sessreg binary I have is SYSV compiled), I get an lseek error, and the session does not start. I suspect that maybe my /etc/utmp and /etc/wtmp are broken and/or incompatible. I got the xdm and sessreg binaries from the xf86-2.0 binary distribution. -- ===================[Warning! Intended-Humour zone ahead]====================== DELPHI: Dimwitted Egoistical Lamers Perpetrating Histeria on the Internet. -- excerpt from a hilarious flamewar (quote from Daniel Leeds). =================[PGP public key available on keyservers]===================== ------------------------------ From: rennolet@knife.cs.umn.edu (Rennolet Charles) Subject: Serial port blues with Slackware 1.1.0 Date: Tue, 7 Dec 1993 01:11:56 GMT Well, I've read the FAQ, I've asked Ian Taylor via email, and now I'm asking for help publicly. Here's the problems. First, uugetty does not appear to be working right (although it may be init that's the problem) in that, instead of spawning once, I've had as many as 9 copies of uugetty spawned one second apart and still running as far as ps can tell. Needless to say, each tries to grab the serial port and the result is mayhem. The second problem is that, when either uucico or cu tries to dial up another system, I get all the way through the chat script, the connected message comes up, and then, when the first characters come from the other side, my machine drops the DTR line and hangs up. This happens on both a 486DX-33 with 16450's and a 386DX-40 with both 16450's and 16550's. I am running high-speed modems, and have pegged the serial port speed at 38400, with the modem locked at 38400 as well. Any clues? Suggestions? This thing won't work as a uucp box as is, which is what I need right now. Charles. ------------------------------ Subject: A Linux Users Manual From: john.will@satalink.com (John Will) Date: Mon, 6 Dec 93 10:11:00 -0640 DA>As a MsDos user who had problems himself with installing Linux I figured DA>it wouldn't be a bad idea if somebody wrote basically a Installation and DA>Command Reference Book for new Linux users. I've started work on it DA>already and was wondering what people would want in a book like this. You might want to check the Linux documentation project, there is already such a book in the works! Perhaps you could assist in their efforts and not duplicate them, I'm sure they would appreciate the help. ------------------------------ Subject: Re: Linux as a DOS filese From: john.will@satalink.com (John Will) Date: Mon, 6 Dec 93 10:14:00 -0640 J >Well, I might be totally off the planet here, but what about linux J >running pc-nfs, and the dosmachines running some sort of pc-nfs too? That would work fine, but NFS client drivers for MS-DOS cost $100's for each machine, so if he has more than one or two PC's, he could just set up a dedicated DOS LAN server for less money. :-) ------------------------------ Subject: Re: Linux as a DOS filese From: john.will@satalink.com (John Will) Date: Mon, 6 Dec 93 10:16:00 -0640 R >The source code for pcnfsd is supplied with the PC-NFS package. It R >should be fairly simple to compile pcnfsd, and run it on the linux R >server. Although I can't guarantee it would work without tweeking, R >it does use standard socket calls. I believe I saw some mail out R >there in one of the c.o.l.* news groups a few months ago from some- R >one who was doing this. I'm running pcnfsd on my Linux box, works fine. ------------------------------ Subject: Re: Linux as a DOS filese From: john.will@satalink.com (John Will) Date: Mon, 6 Dec 93 16:19:00 -0640 JR>On the DOS side of things, we run a commercial TCP/IP networking packages JR>called PC-NFS, put out by FTP Software. BOY! Is Sun going to be pissed that FTP Software is selling their package! Maybe you are talking about PC-TCP? JR>Soooo... does that answer your question? Linux can INDEED perform as a DOS JR>file server, as long as you use the right networking software (TCP/IP JR>compliant) on your DOS PC's. There are several commercial offerings other JR>than from FTP Software, but I am not totally familiar with them. And you don't seem to know the name of the one you have. :-) BTW, I don't think the original poster had in mind spending $100's on each DOS workstation for either PC-TCP or PC-NFS... ------------------------------ From: adams@achibm1.chemie.uni-karlsruhe.de (Klaus-Georg Adams) Subject: Re: NFS-Problems, package > mtu (=1500) Date: 7 Dec 1993 08:31:05 GMT Reply-To: Poster In article , klaus@Rhoen.ime.rwth-aachen.de (Klaus Wilhelm) writes: |> We are using Linux pl12 on IBM 486-DX2/66. When mounting this Linux PC |> via NFS on an IBM RS6000 Workstation (AIX 3.2.4) we get the following |> message: |> |> UDP: send: length 3040 > mtu 1500 (ignored) |> |> Mounting the IBM RS6000 on the Linux PC works fine. We tried to |> enlarge the parameter dev->mtu in 8396.c, but the new kernel told us |> something like: kmalloc is called with impossibly large argument(43..). |> |> What must we do to get NFS working correctly ? You have to reduce the blocksize for read and write operations on the RS/6000. I quote from my /etc/filesystems on the AIX-machine: /pc6usr: dev = /usr vfs = nfs nodename = achpc6 mount = false type = linuxnfs options = bg,soft,intr,rsize=1024,wsize=1024 account = true With these options I don't have a problem accessing the linux fs's. My problem is the other way round. If I write a file from the linux- box to an NFS-drive on the RS6k performance is very very bad (I estimate it at perhaps 40times slower than using ftp between the two machines). Any comments, ideas? Klaus-Georg Adams (adams@achibm1.chemie.uni-karlsruhe.de) ------------------------------ From: Theodore.J.Hajek-1@p3.f506.n163.z1.fidonet.org (Theodore J Hajek-1) Subject: Problem w/display after shutting down X server (ATI card) Date: Fri, 03 Dec 1993 17:26:16 -0500 I'm running the XF86_SVGA server over linux 0.99pl13r using an older ATI card with 512K of RAM. It has the 28000-2 chip, which isn't supported by the server. X works fine at the 800x600 resolution, but when I shut down the X server, all characters on the console are replaced with vertical lines. The card must not be going back to the proper video mode. I've just been going 'su' and rebooting the system. Is there a more graceful way of dealing with this problem? Getting a new video card is an option, but I'd rather get the current one to work. Thanks. -- ======================================================================= Ted Hajek Computer and Information Services 192 Shepherd Labs 100 Union Street Minneapolis, MN 55455 tedhajek@boombox.micro.umn.edu ======================================================================= * Origin: R&D BBS's * `Side_of_Ham' Packet/UseNet/FidoNet Gateway (1:163/506.3) ------------------------------ From: mlarkin@p3.f506.n163.z1.fidonet.org (mlarkin) Subject: ttyS1 time-out problem? Date: Fri, 03 Dec 1993 22:27:55 -0500 I recently installed Slackware 1.1.0 on my 386-33 with 12mb ram. Linux is installed in a 89mb partition. My problem is this: I have a properly configured null-modem connecting the linux box with another 386 running telix under dos. The null modem is configured as follows: 2 & 3 crossed (send/recieve data) 4 & 5 crossed (cts/rts) 6 crossed to 8 and 20, 20 and 8 crossed to 6 (dsr/dtr) 7 straight through (sig. ground) I also have a null modem with just 2,3, and 7 wired.. (no cts/rts/dtr/dsr). No matter which cable I use, i get the same results. Upon bootup, when the main machine has printed the login: prompt, the remote terminal only has about 10-15 characters of the issue file printed.. Sometimes, the remote terminal will actually make it to the login: prompt , but its usually can't manage to print the whole thing, usually printing: Welcome to li ..or.. Welcome ..or.. Welcome to linux 0.99.13. lo etc.. It never makes it COMPLETLY to login: and never accepts any input. running top reveals that there is indeed a getty running for that tty (ttyS1). when I reboot the machine using ctrl-alt-del, the next character that would have been printed had it worked correctly on the remote terminal is >THEN< printed.. Very odd.. I have used MANY different settings in inittab/gettydefs, and am to the point which i think it to be a hardware problem.. Has anyone else had this happen to them? I would like to hear from you, either by reply to this thread, or via email.. Thanks in advance.. -mlarkin@csupomona.edu -mlarkin@eis.calstate.edu * Origin: R&D BBS's * `Side_of_Ham' Packet/UseNet/FidoNet Gateway (1:163/506.3) ------------------------------ From: Wolfgang.Jung@p3.f506.n163.z1.fidonet.org (Wolfgang Jung) Subject: Serial IRQ problems. Date: Sat, 04 Dec 1993 11:11:14 -0500 Fritz Ganter (ganter@fvkmapc02.tu-graz.ac.at) wrote: : Kevin Cummings (cummings@hammer.CV.COM) wrote: : : In article <2cup17$j27@usenet.mcs.kent.edu>, marmstro@Nimitz.mcs.kent.edu (Marc Armstrong) writes: : : > I've got a USR Sportster 14.4 modem on COM1, my mouse on COM2, and a VT-102 : : > terminal on COM3. Now for the fun... I set the interrupt on the modem to : : > IRQ 5 so that it doesn't conflict with COM3's IRQ 4 or COM2's IRQ 3. When : : > booting, the kernel still says that COM1 is still on IRQ 4 and not on IRQ 5. : : > I would really like to use my modem with linux. If anyone can help, I would : : > appreciate it. : : Get the setserial program (available at a Linux archive site near you). Read : : the documentation that comes with it. It will tell you how to tell your : : system that your modem is really on IRQ 5. : Or, you can change it in the kernel permanently. There is a file named : serial.c, search for the proper entry and change it to your IRQ. How about using setserial in the /etc/rc scripts ? Since all kernels after pl10 ( I think) had the auto_configure of the Serial Ports disabled and you needed setserial (This I was told by the README) and with 2.01 of the setserial package it works fine.. so it should do it with your machine too... -- Gruss Wolfgang finally: DO NOT EVER give DOS REALLY ANY CHANCE to survive !!!! * Origin: R&D BBS's * `Side_of_Ham' Packet/UseNet/FidoNet Gateway (1:163/506.3) ------------------------------ From: kai@dpsg.sub.org (Kai Jendrian) Subject: Re: A Linux Users Manual Date: Tue, 7 Dec 1993 09:20:17 GMT john.will@satalink.com (John Will) writes: >DA>As a MsDos user who had problems himself with installing Linux I figured >DA>it wouldn't be a bad idea if somebody wrote basically a Installation and >DA>Command Reference Book for new Linux users. I've started work on it >DA>already and was wondering what people would want in a book like this. >You might want to check the Linux documentation project, there is already >such a book in the works! Perhaps you could assist in their efforts and >not duplicate them, I'm sure they would appreciate the help. If you can read german books, there is a German book "Linuxhandbuch" available. You can get it as .dvi-file on some german ftp-servers as well as a printed book. For more info send a mail to linux@lunetix.de Greetings, Kai. -- Kai Jendrian kai@dpsg.sub.org Phone: +49-721-813291 FAX: +49-721-818126 "Forget about your worries and your strife" from the JUNGLE BOOK ------------------------------ From: e_keen@access.digex.net (Eric Keen) Subject: SCSI Install Failure Date: 6 Dec 1993 22:43:15 -0500 I'm attempting to install the new LGX CD on an AMI BIOS 486 that has an Adaptec 1520/1522 SCSI with a Chinon 535 CD-ROM. It gets as far as the boot diskette with line: aha 152x Vital Data: PORTBASE=0340; IRQ=11 SCSI ID = 7 Reconnect=Enabled Adaptech 152x SCSI Driver; $Revision 9.4$ (at this point, the floppy spins and the screen saver kicks in after a while) Is this an unsupported setup? It even runs Windows-NT without problems. IRQ 11 is free and clear - and without conflicts. Thanks, Eric e_keen@digex.net ------------------------------ From: darcey@[129.170.16.50] (Terrance M. Darcey, PhD) Subject: Re: Linux as a DOS fileserver? Date: Tue, 7 Dec 1993 13:42:38 GMT In article jornj@edb.tih.no (Joern Jensen) writes: >: What I'm getting at here is that I want a server for DOS files on a network >: (10BaseT) and I want a Unix box on that same network. It would be spiffy >: if they could both be the same machine. >Well, I might be totally off the planet here, but what about linux >running pc-nfs, and the dosmachines running some sort of pc-nfs too? We do just this...It works fine...The only problem is that there isn't a public domain NFS client for DOS...We use Sun's PC-NFS, which we got thru a special deal for $50/copy... ------------------------------ From: sadkins@bigbird.cs.ohiou.edu (Scott W. Adkins) Subject: Re: How to get syslogd to listen to net Date: Tue, 7 Dec 1993 14:54:34 GMT In article thompsch@ccmail.orst.edu (Chris Thompson) writes: >Does some one out there know how to get syslogd to listen over a network. >I have a terminal server that will write messages to a BSD compliant syslogd. >In the man pages for the syslogd that comes with slackware 1.0.3 it >says that it is BSD compliant. However, I can not seem to get syslogd to >write the messages. >.99pl13 / slackware 1.0.3 / 486-33DX Yeah, I have noticed the same thing with the syslogd that came with SLS. I wanted to redirect the messages from my linux machine to another machine on campus that I am usually logged on. I have done this already to several other BSDI machines, and it works fine. But it doesn't seem to work at all with the Linux machine. The man page *does* say that you can redirect the messages to a server machine located elsewhere on the network... Where can we get a syslogd that will work on Linux that does its job? (I guess I can try to find a BSD version and compile it... but I just don't relish the thought of porting it over myself...) Scott -- Scott W. Adkins Internet: sadkins@ohiou.edu ~~~~~~~~~~~~~~~ ak323@cleveland.freenet.edu Ohio University of Athens Bitnet: adkins@ouaccvma.bitnet ------------------------------ From: akarpowicz@mta.ca (Adam Karpowicz) Subject: Re: Problem w/display after shutting down X server (ATI card) Reply-To: akarpowicz@mta.ca Date: Tue, 7 Dec 1993 16:22:20 GMT In article <755235109.AA00000@owl.isis.org>, Theodore.J.Hajek-1@p3.f506.n163.z1.fidonet.org (Theodore J Hajek-1) writes: >I'm running the XF86_SVGA server over linux 0.99pl13r using an older >ATI card with 512K of RAM. It has the 28000-2 chip, which isn't >supported by the server. X works fine at the 800x600 resolution, but >when I shut down the X server, all characters on the console are >replaced with vertical lines. The card must not be going back to the >proper video mode. > >I've just been going 'su' and rebooting the system. Is there a more >graceful way of dealing with this problem? Getting a new video card >is an option, but I'd rather get the current one to work. > >Thanks. >-- >----------------------------------------------------------------------- >Ted Hajek >Computer and Information Services >192 Shepherd Labs >100 Union Street >Minneapolis, MN 55455 tedhajek@boombox.micro.umn.edu >----------------------------------------------------------------------- > > * Origin: R&D BBS's * `Side_of_Ham' Packet/UseNet/FidoNet Gateway >(1:163/506.3) As someone has recently explained on *x.i386 group the problem can be solved with the svgalib0** package (it comes with slackware). Once installed it allows to save screen font data in a file /tmp/fontdata befor xinit is run via restorefont routine, and upon exiting X restore it back. It is all done automatically if you start X with a script "runx". It worked for me. Adam Karpowicz akarpowicz@mta.ca ------------------------------ From: scc016rf@unm.edu (Robeo) Subject: Re: lpd Date: 7 Dec 1993 09:55:01 -0700 In article <2dv65s$bu@sisifo.arcetri.astro.it>, Francesco Tribioli wrote: >Run pl14 kernel. There is a problem in pl13 sockets that prevent lpd to work. >The problem has gone with one of the beta release of pl13 and lpd works ok >on pl14. I did this,I downloaded the new kernel about a week ago and I was hoping that would solve the problem but it has not. the errror mesg has changed tho... lpr :connect :no such file or directory jobs qued but cannot start daemon or something like that... Robert scc016rf@carina.unm.edu ch118rf@alpha.lanl.gov ch118rf@technet.nm.org ------------------------------ From: dcoleman@mbs.telesys.utexas.edu (Daniel M. Coleman) Subject: Re: Serial IRQ problems. Date: 7 Dec 1993 16:31:45 GMT >: : In article <2cup17$j27@usenet.mcs.kent.edu>, marmstro@Nimitz.mcs.kent.edu >(Marc Armstrong) writes: >: : > I've got a USR Sportster 14.4 modem on COM1, my mouse on COM2, and a >VT-102 >: : > terminal on COM3. Now for the fun... I set the interrupt on the modem >to >: : > IRQ 5 so that it doesn't conflict with COM3's IRQ 4 or COM2's IRQ 3. >When >: : > booting, the kernel still says that COM1 is still on IRQ 4 and not on >IRQ 5. >: : > I would really like to use my modem with linux. If anyone can help, I >would >: : > appreciate it. You can go into your linux kernel sources ../linux/drivers/char/serial.c, and edit the serial.c file to reflect the proper IRQ, and then recompile your kernel. That way the proper IRQ will be hardcoded in there. Don't forget to make this change with each kernel update you get, though. Dan -- Daniel Matthew Coleman | Internet: dcoleman@mbs.telesys.utexas.edu ===================================+ : dcoleman@mcl.cc.utexas.edu The University of Texas at Austin | : dcoleman@utxvms.cc.utexas.edu Electrical/Computer Engineering | : dcoleman@ccwf.cc.utexas.edu ------------------------------ From: ftlofaro@unlv.edu (Frank Lofaro) Subject: Re: Problem w/display after shutting down X server (ATI card) Date: Tue, 7 Dec 93 17:53:35 GMT In article <1993Dec7.162220.29785@jupiter.sun.csd.unb.ca> akarpowicz@mta.ca writes: >In article <755235109.AA00000@owl.isis.org>, Theodore.J.Hajek-1@p3.f506.n163.z1.fidonet.org (Theodore J Hajek-1) writes: >>I'm running the XF86_SVGA server over linux 0.99pl13r using an older >>ATI card with 512K of RAM. It has the 28000-2 chip, which isn't >>supported by the server. X works fine at the 800x600 resolution, but >>when I shut down the X server, all characters on the console are >>replaced with vertical lines. The card must not be going back to the >>proper video mode. >> >>I've just been going 'su' and rebooting the system. Is there a more >>graceful way of dealing with this problem? Getting a new video card >>is an option, but I'd rather get the current one to work. >> >>Thanks. >>-- >>----------------------------------------------------------------------- >>Ted Hajek >>Computer and Information Services >>192 Shepherd Labs >>100 Union Street >>Minneapolis, MN 55455 tedhajek@boombox.micro.umn.edu >>----------------------------------------------------------------------- >> >> * Origin: R&D BBS's * `Side_of_Ham' Packet/UseNet/FidoNet Gateway >>(1:163/506.3) > > >As someone has recently explained on *x.i386 group the problem can be >solved with the svgalib0** package (it comes with slackware). Once installed >it allows to save screen font data in a file /tmp/fontdata befor xinit is >run via restorefont routine, and upon exiting X restore it back. It is all >done automatically if you start X with a script "runx". It worked for me. > >Adam Karpowicz akarpowicz@mta.ca > Does it work if you ctrl-alt-fkey to switch vc's? If not, you are still _HOSED_! Plus I think there are non-broken versions of the X server around, are they not? > > ------------------------------ ** 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: Linux-Admin-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.admin) via: Internet: Linux-Admin@NEWS-DIGESTS.MIT.EDU 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 ******************************