From: Digestifier To: Linux-Development@senator-bedfellow.mit.edu Reply-To: Linux-Development@senator-bedfellow.mit.edu Date: Thu, 23 Sep 93 20:13:26 EDT Subject: Linux-Development Digest #121 Linux-Development Digest #121, Volume #1 Thu, 23 Sep 93 20:13:26 EDT Contents: New Ultrastor 14/24/34 driver uploaded. (Eric Youngdale) ISO: Ultra 34F SCSI driver for SCO UNIX 2.0v2 (arch harris) Re: Net-2 Patches are GREAT (John Paul Morrison) Re: Linux Slowly Dying Off? (Matt Welsh) Re: To all device driver writers; boot-time messages. (Michael Griffith) Re: Will there be a port of Linux to the upcoming PowerPC? (Ari Lemmke) Qtronix tape drive problems (Mika Jalava) gdb doesn't work with pl12? (Bill McCune) Re: no libipc.a with slackware (Zeyd M. Ben-Halim) Re: PATCH!:Linux and a mouse demon (Re:Whatdopeoplethinkabout/config?) (John E. Stump) Re: Make >1.44M floppies standard in kernel? (Brett Person) Re: port of Linux to the upcoming PowerPC? Free manual available (lou Williams) Re: What do people think about /config? (Ian McCloghrie) Re: Please no /config. (Ian McCloghrie) ---------------------------------------------------------------------------- From: eric@tantalus.nrl.navy.mil (Eric Youngdale) Subject: New Ultrastor 14/24/34 driver uploaded. Date: Thu, 23 Sep 1993 18:16:53 GMT I have uploaded a new version of the [1,2,3]4f Ultrastor driver to tsx-11 in pub/linux/ALPHA/scsi. The file is called ultrastor-1.11c.tar.z. There have been a few changes and bugfixes - the most difference is that Caleb Epstein reports that the 24f now works reliably, where previously under the same conditions the kernel would die a horrible death. Also, there is no longer a separate version of scsi.[c,h], or hosts.[c,h], and this should drop right in to 0.99pl13. It will probably drop into pl12 and maybe even pl11. I would like people to try this and ensure that it actually works properly. Caleb and I have both made some minor changes while away from our Linux boxes, and in theory there could be problems, but this is unlikely. It is especially important for people with the 14f and 34f to try this and make sure that everything is stable because this version will go into the distribution kernel if no one reports any problems. -Eric -- "When Gregor Samsa woke up one morning from unsettling dreams, he found himself changed in his bed into a lawyer." ------------------------------ Crossposted-To: gnu.gnusenet.test,comp.unix.sysv386,comp.unix.sysv.r3,comp.unix.pc-clone.32bit,biz.sco.general From: arch@hub.cs.jmu.edu (arch harris) Subject: ISO: Ultra 34F SCSI driver for SCO UNIX 2.0v2 Date: Thu, 23 Sep 1993 18:41:27 GMT I have a Tri-Star 486 DX66 ISA VLbus machine with an Ultrastor 34F SCSI controller. I want to install SCO UNIX 2.0v2 on it but Ultrastor only has a driver for SCO UNIX 2.0v4. I was going to see if their Ultrastor 14F driver for SCO UNIX 2.0v2 would work but they said it would not work because that version of the 14F driver relies on the WD emulation which the 34F does not have. Has anyone written a Ultrastor 34F device driver for SCO UNIX they would be willing to share? Even if it is not for 2.0v2, it might be easily adaptable for 2.0v2 (I imagine it would be fairly simple to adapt Ultrastor's 2.0v4 drvier but they will not give me a copy of their source code :(, only the specs on their driver). Maybe one of the Linux 34F driver developers has also worked with SCO UNIX? Has anyone written any kind of SCSI host adapter driver for SCO UNIX? Can you give me an idea as to how difficult a task it is? -- Dr. J. Archer Harris Dept of Computer Science arch@hub.cs.jmu.edu James Madison University (703) 568 - 6847 Harrisonburg, VA 22807 -- Arch Harris Dept of Computer Science arch@hub.cs.JMU.EDU James Madison University (703) 568-6847 Harrisonburg, VA 22807 ------------------------------ From: jmorriso@rflab.ee.ubc.ca (John Paul Morrison) Crossposted-To: comp.os.linux.misc Subject: Re: Net-2 Patches are GREAT Date: 23 Sep 1993 19:32:58 GMT In article <27qj40$cli@bigbird.csd.scarolina.edu>, Billy L. Williams Jr. wrote: :Hello Fellow net-users, : :I would just like to remark that the net-2 patches found on sunsite under :/pub/Linux/system/Network/net2-debugged-tcp.tar.z really work wonders for :me. My system (pl 12, 13 alpha, and 13) really wasn't stable at all under :any kind of net load, but the new patches really help my system stay up :under normal usage. Take a look: OK, what's the secret? I can get pl13 with net-2e4 running, although it isnt very stable. I'm about to give up on net-2e, so I downloaded the newest pl13 source and followed the net2-debugged instructions. The instructions tell you to move your inet directory, then unpack the new code. No Makefile or CONFIG is included with net2-debugged, so I assume you are supposed to copy the old ones (from inet.old!). After compiled and booting, the new net2 stuff won't even detect my ethercard. : :[1] % uptime : 6:14pm up 17:47, 2 users, load average: 0.01, 0.06, 0.02 : :and I've been hitting the net fairly hard trying to crash the machine :(it didn't crash 17:47 ago either, just rebooted after applying patches). :This would have been unthinkable without these patches--a simple repition :of "tcpspray" commands would eventually bring it down (after approx. :100 or so such commands in a row). : :Oh, my hardware: 386-40, 20 meg ram (but with kernel 16 meg limit due to :the ethernet card drivers), Boca AT1500 compatible card, nothing else :special. : :Thank you, Swansea University, for making my net stable! : :By the way, can anybody direct me to the newest telnetd and rlogind? I :realize that I should get them for pl 13, but I have been unable to find :any kind of new sources for them.... : :Billy L. Williams, Jr. :-- : Billy L. Williams, Jr. e-mail: williams@vierzk.bates.scarolina.edu : University of South Carolina Master of International Business Candidate : Try Linux--it will be the last OS you ever install............Go Cocks! : ..................finger me for pgp key and more info.................. -- ___________________________________________________________________________ John Paul Morrison | University of British Columbia, Canada | Hey hey!! Ho ho!! Electrical Engineering | Tax & spend liberals jmorriso@rflab.ee.ubc.ca VE7JPM | have got to go!! ________________________________________|__________________________________ ------------------------------ From: mdw@sunSITE.unc.edu (Matt Welsh) Crossposted-To: comp.os.linux.help,comp.os.linux.misc Subject: Re: Linux Slowly Dying Off? Date: 23 Sep 1993 20:52:46 GMT Goodness. This should not be posted to 3 of the 4 unmoderated Linux groups. Please don't crosspost. Followups to c.o.l.m. In article <1993Sep23.155008.29374@iitmax.iit.edu>, Rob Grzywinski wrote: >I remember back to the days where a new SLS was comming out every three >weeks, the news groups were filled to the point of breaking with new >updates and the project was full speed ahead. > I hope not to start any crap (to put it mildly) with this, but I think >that we (you) have a great product going here and I don't want to see it >dying out. It's not dying off... not at all. It's simply stabilizing. Things aren't changing as rapidly, which is a sign of maturity. > I hope that we can rejuvinate our love for the project and continue full >speed again!!! Believe me, we're running at 105% maximum warp, captain, and I'm not sure that this ship can take any more. Granted, there are some projects that have fallen by the wayside, but I don't see that as a general trend. mdw -- Send submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu ------------------------------ From: grif@ucrengr.ucr.edu (Michael Griffith) Subject: Re: To all device driver writers; boot-time messages. Date: 23 Sep 1993 21:06:56 GMT In article <27she7$qin@kruuna.helsinki.fi>, Lars Wirzenius wrote: >I quite agree with this suggestion, although I'd use slithgly longer >prefixes ("Info:", "Warning:", and "ERROR:", perhaps). > >What about making all merely informational bootup messages optional? >That would make the bootup screen less cluttered and it would be >easier to spot problems. These type of issues have been already taken care of by the syslog mechanism. Perhaps we could add a severity field to printk so that the interface between the kernel and syslogd can be more useful. -- Michael A. Griffith grif@cs.ucr.edu ------------------------------ From: arl@cs.hut.fi (Ari Lemmke) Crossposted-To: comp.os.linux.misc Subject: Re: Will there be a port of Linux to the upcoming PowerPC? Date: 21 Sep 1993 22:18:35 GMT In article <1993Sep16.211424.7634@iitmax.iit.edu> grzyrob@elof.acc.iit.edu (Rob Grzywinski) writes: : With all of the work going into the development and porting of Linux : will there be an effort to port over to the PowerPC (running on the : MPC601 Motorola chip) when they are released? I'll start it as soon as you send me a PowerPC machine ;-) : Thanks in advance The same... : Rob Grzywinski arl ------------------------------ From: mjalava@ahti.hut.fi (Mika Jalava) Subject: Qtronix tape drive problems Date: 22 Sep 1993 21:44:48 GMT I'm trying to get a Qtronix TDB-250F QIC-80 tape drive to work with linux. Kernel is 0.99.12, the ftape-0.9.6 with the accompanying modules package is installed. When trying mt -f /dev/ftape rewind the results are like this: ftape-io.c (_ftape_open) - drive wake-up method: Colorado DJ-10. ftape-io.c (ftape_report_operation) - timeout on Acknowledge. ftape-io.c (ftape_report_operation) - timeout on Acknowledge. ftape-io.c (ftape_report_operation) - timeout on Acknowledge. (...hundreds of these) ftape-io.c (_ftape_open) - report_error_code failed. ftape-rw.c (ftape_flush_buffers) - flushing write buffers. ftape-io.c (_ftape_close) - calling ftape_abort_operation. ftape-io.c (_ftape_close) - rewinding tape. ftape-io.c (ftape_report_operation) - timeout on Acknowledge. ftape-io.c (_ftape_close) - disabling drive. During all this the drive whirs back and forth. So no "unknown drive type" or "unknown vendor id". Any suggestions about what could be wrong? Mika ------------------------------ From: mccune@lutra.mcs.anl.gov (Bill McCune) Subject: gdb doesn't work with pl12? Reply-To: mccune@lutra.mcs.anl.gov (Bill McCune) Date: Thu, 23 Sep 1993 21:42:06 GMT When I call a function from gdb, I always get writing register number 10(0): I/O error. Unable to restore previously selected frame. This is with pl12 and either gdb 4.8 and 4.10.pl1. I hear that the problem does not exist with pl11. Does this happen to anyone else? -- Bill --------------------------------------------------------------------- | William W. McCune | e-mail: mccune@mcs.anl.gov | | MCS-221 | phone: (708) 252-3065 | | Argonne National Laboratory | FAX: (708) 252-5986 | | Argonne, IL 60439-4844 | | | U.S.A | | --------------------------------------------------------------------- ------------------------------ From: zmbenhal@netcom.com (Zeyd M. Ben-Halim) Subject: Re: no libipc.a with slackware Date: Thu, 23 Sep 1993 21:05:24 GMT In article <13124@obelix.icce.rug.nl> karel@icce.rug.nl (Karel Kubat) writes: >In skj@oasis.icl.co.uk (Simon Johnston) writes: > >>My Slackware distribution contains a kernel 0.99.12, and a dosemu 0.49. I >>tried to compile the dosemu yesterday but there is no libipc library ! >>does anyone have the libipc which would match the 0.99.12 kernel, and can >>anyone tell me why I don't have one. > >Simon: > >The same problem occurred to me. It seems that the standard libc.a should >have the ipc routines included; therefore; all you'd have to do is to remove >the flag -lipc from the makefile at the location where the linking occurs (I >think that this flag is somewhere in the LFLAGS definition, but I'm not >sure). > >For me, however, this didn't work. It did produce a program and shared >library, but a defect one.. Sadly, I can only use dosemu with the old Linux >version (pl10), where it has to be linked explicitely with a libipc.a. The >problems I have with pl12 is that Dosemu comes up, but that the keyboard is >dead.. no matter which flags for dosemu itself (raw or not raw keyborad IO) >are used. The error log prints messages like, "shmget(): function not >supported" etc.. You did remember to enable the ipc stuff from /etc/rc, didn't you? If not, get the latest ipc patches as they inlclude docs and the ipcs program. >Any suggestions on this, how to make dosemu run with pl12? I'd be much >obliged.. > >Karel. >-- > The ICCE usenet account > providing access to usenet news > for the ICCE Experience > _WERKEN_AAN_DE_GRENZEN_VAN_HET_KUNNEN_ -- Zeyd M. Ben-Halim zmbenhal@netcom.com 10479 1/4 Santa Monica Blvd, LA, CA, 90025 (310) 470-0281 ------------------------------ From: jstump@mstu41.intel.com (John E. Stump) Subject: Re: PATCH!:Linux and a mouse demon (Re:Whatdopeoplethinkabout/config?) Date: 23 Sep 1993 23:06:51 GMT In article <27ekt4$k9m@klaava.Helsinki.FI> lukka@klaava.Helsinki.FI (Tuomas J Lukka) writes: >> Also, outside of selection, has anyone thought of a way to allow >>hooking into the mouse in an easy, integrated into linux way? What do >>people thing about some mouse hook routines as part of the linux api? > >I've actually done this. I've patched my A-pl13 kernel and selection >to use the xterm control codes for mouse tracking on the consoles that >want it and standard selection on others. It's not perfect but it's >a proof-of-a-concept thing. I made them to be able to use, on a vc, >the new fancy newsreader (strn) that uses xterm mouse tracking at school. > >Now if only someone would extend ncurses to use this and make a fancy >text-mode windowing system ;) I'm working on it. What it is is a text-mode window library that supports colors and exotic keys (ALT keys and Function keys). Curses was way too primative for the display layer, so I had to write my own library which takes advantage of today's modern consoles (but still supports the old dumb terminals). One of the things lacking is mouse support, but I was planning on doing exactly what you have already done; i.e. use the xterm mouse tracking method. I will be looking very closely at your work. As a method of testing this windowing library, I am also developing a nifty system administration tool that everyone has been complaining Linux needs. It is lightly based on the SMIT utility found on AIX, but much prettier. Keep your eyes peeled here for future announcements as I progress. Unfortunately, the amount of time I have to spend on Linux work is small. john ------------------------------ From: person@plains.NoDak.edu (Brett Person) Subject: Re: Make >1.44M floppies standard in kernel? Date: Thu, 23 Sep 1993 23:05:20 GMT In article <27a56a$h9a@hermes.acs.ryerson.ca> ylam@acs.ryerson.ca (York Lam - ACPS/F93) writes: > > Are there any plans in making the floppy patches, for extra >tracked/sectored disks, a standard part of the kernel? It never patched >cleanly into the newer patch-levels. I probably should pulls diffs from >what I got now (p11) for "future reference". Probably not. > 1.44 floppies are unreliable enough that they probably shouldn't be used at all. -- Brett Person Guest Account North Dakota State University person@plains.nodak.edu || person@plains.bitnet ------------------------------ Crossposted-To: comp.os.linux.misc From: nsyslaw@straylight.acs.ncsu.edu (lou Williams) Subject: Re: port of Linux to the upcoming PowerPC? Free manual available Date: Thu, 23 Sep 1993 16:12:18 GMT Hansruedi Heeb (heeb@watson.ibm.com) wrote: : In article SHOVERST@atc.sp.paramax.com (Shane Hoversten) writes: : >In article heeb@watson.ibm.com (Hansruedi Heeb) writes: : > : >>Just in case someone wants to get started on this: the (free) manual : >>of the PowerPC 601 is available. It also contains a detailed : >> ... : > : > I don't know about the other numbers you gave, but this is NOT free, at : >least according to the lady at IBM. She said she had been getting lots of : >calls concerning this; Apparently someone misinterpreted something. : > : Yup, it's not free. I cancelled the article and sent one without : the word free. You read it too fast ... :-) : Hansruedi I believe there is a *free* manual, but it's from Motorola, and it only covers the MPC-601 processor, not the entire PowerPC system. It gives tech details, instruction sets, timing diagrams, pinouts, etc for (hopefully?) those wishing to (dirty word, ahead) clone the MPC-601? At the very least it should give _more_ than enough detail for programming the low levels of the processor. Now for the rest of the system, guess it's back to big blue... :( +-----------------------------------------------------------------------------+ | Lou Williams (nsyslaw@acs.ncsu.edu) | Amatuer Radio: KE4ARM | | Unix Systems Programmer | Phone: (919) 515-2794 | | NCSU Administrative Computing Services | FAX: (919) 515-3787 | +-----------------------------------------------------------------------------+ | Ack! Thpppppffffffft!!!! -Bill The Cat. | +-----------------------------------------------------------------------------+ ------------------------------ From: imcclogh@cs.ucsd.edu (Ian McCloghrie) Subject: Re: What do people think about /config? Date: 23 Sep 93 22:38:52 GMT warb@faatcrl.faa.gov (Dan Warburton) writes: >BTW /etc/ probably started out this way. /conf is a mistake. If all the binaries are moved out of /etc into /bin and /sbin, depending upon what they are (as is a standard unix practice these days) then that leaves /etc with... guess what. Config files. Since /conf and /etc now have identical contents, it makes little to no sense to have both. If one should be eliminated, then, IMHO, for lack of any better reason, why not keep the one that is used on every unix system out there, instead of the one that's new and unknown? BTW, this issue has been addressed at length on the linux FSSTND channel. -- /~> Ian McCloghrie | Commandant of Secret Police - Cal Animage Beta. < < /~\ |~\ |~> | | <~ | email: ian@ucsd.edu Net/2, USL 0! \_> \_/ |_/ |~\ |__| _> | Card Carrying Member, UCSD Secret Islandia Club ------------------------------ From: imcclogh@cs.ucsd.edu (Ian McCloghrie) Subject: Re: Please no /config. Date: 23 Sep 93 22:44:14 GMT dillon@moonshot.west.oic.com (Matthew Dillon) writes: > I'm half and half on it... for myself, having a separate /conf to hold >system-specific files on the root partition makes managing multiple machines >much easier... the entire root partition is the same on each machine except for >/conf (or /config or whatever you want to call it). /conf actually makes this HARDER in an NFS environment. Think about it. If you NFS mount a package (X11, say) should you have to keep separate copies of the default twmrc and xinitrc on every single system's root partition? Now, Xconfig is a special file, it has hardware dependencies in it, and NEEDS to be kept separate. But the software configuration files don't. Configuration files should be kept in directories with the packages that they go with, so that when you mount the package you get the config file at the same time. -- /~> Ian McCloghrie | Commandant of Secret Police - Cal Animage Beta. < < /~\ |~\ |~> | | <~ | email: ian@ucsd.edu Net/2, USL 0! \_> \_/ |_/ |~\ |__| _> | Card Carrying Member, UCSD Secret Islandia Club ------------------------------ ** 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-Development-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development) via: Internet: Linux-Development@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-Development Digest ******************************