From: Digestifier To: Linux-Development@senator-bedfellow.mit.edu Reply-To: Linux-Development@senator-bedfellow.mit.edu Date: Sun, 11 Sep 94 10:13:05 EDT Subject: Linux-Development Digest #155 Linux-Development Digest #155, Volume #2 Sun, 11 Sep 94 10:13:05 EDT Contents: Re: Alpha Linux (Herbert Xu) Re: Don't use Linux?! (Kevin Martinez) Re: DOSEMU 0.53pl18 und 1.1.49 : Serial Problems (Rob Janssen) Re: Not identifying ST-506 drives (was: Re: IDE Hard Drives w/ over 1024 cylinders) (Rob Janssen) Re: atdisk2 and E-IDE (Rob Janssen) Re: GoldStar VLB IDE controller (Rob Janssen) Re: 3c509 Problems (Rob Janssen) Re: Alpha Linux (Rob Janssen) Re: 320x200 X resolution? (Olli Vinberg) New 53c400 patch (Kevin Lentin) [SOLUTION] DOSEMU 0.53pl18 : Serial Problems (James MacLean) Re: Don't use Linux?! (Michaela Merz) Re: Digi Intelligent Boards? (William C. Fenner) Re: Alpha Linux (N J Plant) RFD: Linux and end-users (Was: Don't use Linux?!) (Ted Harding) Kernel change summary 1.1.49 -> 1.1.50 (Russell Nelson) ---------------------------------------------------------------------------- From: herbert@greathan.apana.org.au (Herbert Xu) Subject: Re: Alpha Linux Date: 11 Sep 1994 12:54:58 +1000 David Holland (dholland@husc7.harvard.edu) wrote: : adc@bach.coe.neu.edu's message of 06 Sep 1994 16:38:15 GMT said: : > Why drop one? : > 16 bits = short int : > 32 bits = int : > 64 bits = long : Over in the next thread people were talking about Unicode; why not : 16 bits = char : 32 bits = short : 64 bits = int, long : Of course that would break a lot of things, but such is the price of : progress :-) Only non-ANSI conforming C codes. -- A. B <=> True B. A <=> False Email: Herbert Xu ~{PmV>HI~} PGP Key: pgp-public-keys@pgp.mit.edu or any other key sites ------------------------------ From: Kevin Martinez Subject: Re: Don't use Linux?! Date: Sat, 10 Sep 1994 23:04:51 GMT hightec@sbusol.rz.uni-sb.de (Michael Schumacher) writes: > the box", no reasonable documentation is available, nor hotline support. > What will happen? I'm quite sure that most of these desperated people > will close the Linux chapter - forever. This is a joke? Have you ever tried to get hotline support for Netware? $200 up front, then wait for them to call back! (2 days in the case I am familiar with). Try getting hotline support from Macrosoft: tell them that "xcopy" trashes your command history. Will they lift a finger? h0h0h0h0 (and you are on a 900 number paying by the minute!) I called a major hardware vendor that our corporation has "special" support available. I wanted to know why I couldn't get certain transfer modes working with a certain hard disk. The response was silly: Was it plugged in? powered on? (Yes, this was *technical* support!). How about Sun Microsystems? They are certainly a commercial operation. Ask them to make hardware flow control work properly. (to their credit, it is half fixed but the bug history goes back to the mid-80s at least) Our corporation seems to have a very effective support line: put them on hold and play elevator music and they go away after an hour or so. I doubt this is the "official" policy that we tell the customer but I get complaints from people that know where I work..... As far as I can tell, support seems to rely on "the good 'ole boy" network and that is just what the Linux community is all about! P.S. Linux is not for the person who uses a computer because he/she is required to; it is for the person who enjoys their computer and looks for ways to enjoy it further.... -- ======================================================================== Kevin Martinez lps@rahul.net Member of the Julie Kangas Fan Club Work: 1 800 I FEEL OK Home: 1 510 676 1111 ======================================================================== ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: DOSEMU 0.53pl18 und 1.1.49 : Serial Problems Reply-To: pe1chl@rabo.nl Date: Sun, 11 Sep 1994 09:10:05 GMT In <1994Sep8.193016.470@yacc.central.de> engel@yacc.central.de (C. Engelmann) writes: >root@fabsoft2.zarm.uni-bremen.de (Martin Cornelius) wrote: >>I just successfully installed Kernel 1.1.49 and Dosemu 0.53pl18, >>but the serial Ports seem to be not working at all. When I try >>to install the MS mouse-driver or the Logimouse driver, they >>both say that no mouse can be found. Also, Procomm cannot access >>the ports. I'm sure the harware is o.k. as i can use the ports >>with kermit, selection and X. The serial entries in my dosemu.conf >>didn't change since dosemu 0.52, where everything worked fine. >>Any Hints ?? >Not a hint, but the same problem using kernel 1.1.44. >DOSEMU locks up if I try to load the mouse driver. >Under X things are working well(the first time !). Get the next (0.53pl19) DOSEMU... That is said to fix the problem. Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: Not identifying ST-506 drives (was: Re: IDE Hard Drives w/ over 1024 cylinders) Reply-To: pe1chl@rabo.nl Date: Sun, 11 Sep 1994 09:14:58 GMT In <9409091592@fangorn> Michael Haardt <(michael)u31b3hs@pool.informatik.rwth-aachen.de> writes: >davism@latcs2.lat.oz.au (Mitch Davis) writes: >> I used to think this was because the ST-506 interface was so old that >> no-one was particularly bothered about identifying it. But from the >> quoted message above, it appears _something_ in the kernel knows it's >> an ST-506.... >Yes, I don't have a clue why it was done that way. The following patch >fixes it: > if (unmask_intr[dev]) > sti(); > if (stat & (BUSY_STAT|ERR_STAT)) >! printk ("hd%c: ST506 interface, %dMB, CHS=%d/%d/%d\n", >! dev+'a',hd_info[dev].cyl*hd_info[dev].head*hd_info[dev].sect/2048,hd_info[dev].cyl,hd_info[dev].head,hd_info[dev].sect); > else { > insw(HD_DATA, (char *)&id, sizeof(id)/2); /* get ID bytes */ > max_mult[dev] = id.max_multsect; >Once I sent this to Linus, but no response. IDE drives can tell you >their parameters, whereas for ST506 interface drives, you need to >believe the BIOS, which may be incorrent. Nevertheless, I like to see >the parameters at booting. You wouldn't believe how much stir-up a small patch like this can sometimes cause. I think Linus has become more careful before incorporating things like this.... (e.g. at one time a "small patch that makes a PS/1 disk recognized and seems to be harmless" caused a lot of messages from people that did not have an IDE/ST506 disk at all, and complained that it was still "recognized"...) Moral: before you submit it, test it on some friends machines (including machines with unusual configurations like ESDI or only-SCSI) and submit it including a statement that this caused no problems. Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: atdisk2 and E-IDE Reply-To: pe1chl@rabo.nl Date: Sun, 11 Sep 1994 09:17:48 GMT In rkwtgs@pukrs3.puk.ac.za (Theo Scott) writes: >Hi, >I've got a 2nd IDE controller (with a drive) on IRQ-15. >I've apllied the patch and it worked but only with a drive with <= 16 heads >The one drive that I want to use is a Conner with 17 heads. >I saw in the "hd.c" that Mark Lord made some inprovements so that >1st Controller can use a drive with >16 heads. Does anyone knows of >a patch for "hd1.c" ? The patch for using >16 heads on "hd.c" would >be fine to. Any ftp sites ? Here you see the exact reason why the atdisk2 patches will be reworked before they are accepted into the main release :-) Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: GoldStar VLB IDE controller Reply-To: pe1chl@rabo.nl Date: Sun, 11 Sep 1994 09:21:09 GMT In <1994Sep10.151839.18366@wisipc.weizmann.ac.il> yuvalt@black.weizmann.ac.il (Tal Yuval) writes: >I have a GoldStar VLB IDE controller. Linux seems to work fine with it. >However, along with the controller I got a diskette with device drivers which >seem to boost things. Did someone hack the kernel to use GoldStar's >functions? You can't use DOS drivers with Linux. Instead, ask GoldStar what the drivers do, and you cna incorporate similar functionality in the Linux drivers... Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ Crossposted-To: comp.os.linux.help From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: 3c509 Problems Reply-To: pe1chl@rabo.nl Date: Sun, 11 Sep 1994 09:36:58 GMT In <34tbn3$6nv@dns.crocker.com> matthew@crocker.com (Matthew S. Crocker) writes: >Danek Duvall (duvall@sage.wlu.edu) wrote: >: I recently set up my 3Com Etherlink III Combo on my linux machine. >: The first boot after the network stuff was configured, it worked fine. >: In fact, it worked fine continuously for over a day. Then, today, I >: was having some problems compiling and installing sendmail, I rebooted >: my machine. At that point, I couldn't find anything on the network. >: I hadn't changed any relevant pieces of the network config files, so >: it couldn't have been that. Then I checked /var/adm/messages, which >: had the line: >: eth0: Missed interrupt, status then 2011 now 2011 Tx 00 Rx 383c >I get this every once and a while too (on my 486-66 VLB/ISA) I never >get it on my P5-90 PCI/ISA. Do you get it when you do a hard boot? >try shutdown -h now then press teh reset button... I only get it when >I shutdown -r now or 'reboot' Same on the machine I use at work (486/33). It only issues the message on a CTRL-ALT-DEL reboot. But it has never caused a hard problem for me, other than dropping the first packet. When the problem Danek has is the same, there is something else that has caused the networking to die and the "Missed interrupt" is not the cause. However, there is another datapoint I can add: someone at work tried CTRL-ALT-DEL booting a system that had been running as a Novell Netware server just before, into Linux. This really freaked out the 3c509 driver... It issued continuous error messages which he unfortunately did not write down. Probably it can be repeated when required. I think the 3c509 driver does not completely initialize the card, and relies on some power-on defaults that are no longer valid after a warm boot. Could that be true, Donald? Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: Alpha Linux Reply-To: pe1chl@rabo.nl Date: Sun, 11 Sep 1994 09:42:35 GMT In im14u2c@cegt201.bradley.edu (Joe Zbiciak) writes: >In jem@snakemail.hut.fi (Johan Myreen) writes: >>What is the natural word size of the 68000? Or the 8088? Or a >Even better: The 68008... 8 bit data path, 16 bit registers, 32 bit ALU. >By 32 bit ALU, I mean two registers would combine together and make a 32 bit >register for ADD & SUB and MUL & DIV (I think.) Actually, the 68008 has only a 16-bit ALU and performs 32-bit ADD and SUB operations using muliple passes. It can't even perform 32-bit MUL and DIV. The natural word size of a 68000/68008 is 16 bits. For a 68020 it would be 32 bits. Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: vinberg@cc.Helsinki.FI (Olli Vinberg) Crossposted-To: comp.os.linux.misc Subject: Re: 320x200 X resolution? Date: 11 Sep 1994 15:09:02 +0300 Reply-To: Olli Vinberg In article <1994Sep10.202313.3057@titan.central.de>, Andreas Matthias wrote: > >: So.... 320x200 resolution anyone? :) >: I'll post if I figure out how to do it. > >I have one that's working here (ET4000 with 17'' AOC monitor), but it >occupies only about half of the screen in vertical direction. I did >not find out how to make it bigger vertically. Perhaps someone else >can continue with this: > >********************************************************************** >ModeDB ># name clock horizontal timing vertical timing flags > > "320x200" 25 320 360 424 440 200 200 240 250 >********************************************************************** I seriously doupt that your monitor can handle that kind of refresh-rates.. Te above modedb-entry would mean a refresh-rate of 250Hz!!! I tried to make a 320x200 too, and the closest I got was 500x400 with a refresh-rate of 100Hz. -- ======================================================================= Olli Vinberg \ Our OS who art in CPU, UNIX be thy name. vinberg@cc.helsinki.fi \ Thy programs run, thy syscalls done, http://www.helsinki.fi/~vinberg \ in kernel as it is in user! ------------------------------ From: kevinl@bruce.cs.monash.edu.au (Kevin Lentin) Subject: New 53c400 patch Date: 11 Sep 1994 12:57:58 GMT I've uploaded a new version of my 53c400 (T130B) Scsi patches. They are functionally identical to the previous set but some of the patches in the 40's affected the NCR code and my patch stopped working flawlessly. Here is the .lsm entry Begin3 Title: Patch to Linux 1.1.49+ for 53c400/t130b scsi Version: 1(beta) Entered-date: 18/8/94 Description: These patches allow the Trantor T130B and any other NCR53c400 based card to work with the Generic NCR5380 SCSI driver under Linux. Ineterupts and PSEUDO-DMA are supported. This will become part of the development kernel eventually. This also includes some patches from Drew Eckhardt to do with resets and aborts as well as some timing issues. I couldn't be bothered separating them out. They'll all go in eventually anyway. Keywords: SCSI T130B NCR5380 NCR53C400 Author: kevinl@cs.monash.edu.au (Kevin Lentin) Maintained-by: kevinl@cs.monash.edu.au (Kevin Lentin) Primary-site: sunsite.unc.edu /pub/Linux/kernel/patches/scsi 13k 53c400.tar.gz Alternate-site: Original-site: Platform: Linux 1.1.49+ Copying-policy: GPL End -- [==================================================================] [ Kevin Lentin |___/~\__/~\___/~~~~\__/~\__/~\_| ] [ kevinl@bruce.cs.monash.edu.au |___/~\/~\_____/~\______/~\/~\__| ] [ Macintrash: 'Just say NO!' |___/~\__/~\___/~~~~\____/~~\___| ] [==================================================================] ------------------------------ From: jmaclean@localhost (James MacLean) Subject: [SOLUTION] DOSEMU 0.53pl18 : Serial Problems Date: 10 Sep 1994 23:43:48 -0300 Martin Cornelius (root@fabsoft2.zarm.uni-bremen.de) wrote: : I just successfully installed Kernel 1.1.49 and Dosemu 0.53pl18, : but the serial Ports seem to be not working at all. When I try : to install the MS mouse-driver or the Logimouse driver, they : both say that no mouse can be found. Also, Procomm cannot access : the ports. I'm sure the harware is o.k. as i can use the ports : with kermit, selection and X. The serial entries in my dosemu.conf : didn't change since dosemu 0.52, where everything worked fine. : Any Hints ?? : ---------------------------------------------------- : Martin Cornelius, ZARM-FAB, Uni Bremen 0421-218-4807 : Hochschulring / Am Fallturm 28359 BREMEN : ---------------------------------------------------- A strong hint is to try: tsx-11.mit.edu:/pub/linux/ALPHA/dosemu/private/devel/pre53_19.tgz & tsx-11.mit.edu:/pub/linux/ALPHA/dosemu/private/devel/pre53_19.dif.gz as the serial SHOULD be back in working order. Thanks for all who E-mailed me about this one. JES ------------------------------ From: misch@elara.fsag.de (Michaela Merz) Subject: Re: Don't use Linux?! Date: Sun, 11 Sep 1994 04:13:15 GMT Bogdan Urma wrote in article <34sref$klu@newsstand.cit.cornell.edu> : > >Michael Schumacher (hightec@sbusol.rz.uni-sb.de) wrote: > >: Hello Linuxers! > >: Okay. Before you start sending me endless flames, I want to make sure >: that you know that I *love* Linux. It's probably the best PC Un*x you > > That's pretty funny, since Maple V Release 3 has just been ported to Linux. > >Bogdan He is _perfectly_ right! There a thousands of programs. Maple is _just_ one of them ... mm. --- The Free Software (Phone) ++49-69-6312083 Association of Germany, FSAG We have a target! ------------------------------ From: fenner@cmf.nrl.navy.mil (William C. Fenner) Subject: Re: Digi Intelligent Boards? Date: 11 Sep 1994 13:14:30 GMT In article , Simon Park wrote: >AFAIK there are no Linux drivers available for any of the >intelligent serial cards. Someone from Arnet told me that there was a Linux driver available for the Arnet Smartport; I haven't gotten a reply back telling me how to get it, though. Bill -- Bill Fenner fenner@cmf.nrl.navy.mil ------------------------------ From: nick@lepton.demon.co.uk (N J Plant) Subject: Re: Alpha Linux Reply-To: nick@lepton.demon.co.uk Date: Sun, 11 Sep 1994 13:34:09 +0000 In article im14u2c@cegt201.bradley.edu "Joe Zbiciak" writes: > >In jem@snakemail.hut.fi (Johan Myreen) >writes: > >>What is the natural word size of the 68000? Or the 8088? Or a > >Even better: The 68008... 8 bit data path, 16 bit registers, 32 bit ALU. >By 32 bit ALU, I mean two registers would combine together and make a 32 bit >register for ADD & SUB and MUL & DIV (I think.) > On the 68000 the external address bus is 20 bits and the external data bus is 8. Internally, the registers, buses and ALU are all 32 bit. It can ADD and SUBtract 32 bit numbers or MULtiply 2 16 bit numbers to give a 32 bit result. It has fewer pins than a 68040, but its still a 32 bit chip. The sizeof the integral types should be the same as any other 68K chip. The Intel 8088 has a 20 bit address bus, but is otherwise an 8 bit device. So: short = 8 bits int = 16 bits long = 16 bits Neither of these processors has the address space or MMU necessary for Linux to run on them, so the natural word size is irrelevant. >How do you define the "natural wordsize" nowadays? On the alpha the instruction word length is 32 bits. The registers are 64 bit and there is plenty of them. I'd go for: short = 32 bits To save memory on kernal data structures which need to be in our level 2 cache. int = 64 bits Small enough to avoid any significant performance penalty on file system hashing. Large enough for the next generation of disk drives. long = 128 bits Large enough for most other purposes. Nick -- N J Plant ------------------------------ From: Ted Harding Subject: RFD: Linux and end-users (Was: Don't use Linux?!) Date: 11 Sep 1994 09:59:27 -0400 Reply-To: Ted.Harding@nessie.mcc.ac.uk And Greetings to Mike Schumacher for raising, in sane terms, a very worrying issue. Let me show my own IFF status and say I'm personally committed to Linux: it's excellent in itself, and in various ways outdoes many other versions of UNIX. Despite problems, the Linux Community Spirit provides a pretty effective user support service. What Linux lacks, so far, is a /good/ base of applications software. Say what you like about DOS (DR- or MS-), there's a huge repertoire of often excellent DOS-based applications software. Agreed the software developers started writing for DOS because everyone was buying PCs with DOS on them; the boot's now on the other foot - everyone buys DOS/Windows because that's what all the software is written for. An example of what's /good/ on the Linux scene: as a mathematician and statistician I get most of what I need computationally from 'octave'; thank God I don't have to program from scratch what's been available in MatLab for DOS for years. An example of what's no so good: I also need spreadsheet facilities; 'sc' is fine for small quick jobs, 'oleo' looks promising but doesn't seem to be there yet, and certainly doesn't go very far, and 'scc' under X (= sc with some graphics) roughly equals "basic use of Quattro". Not inadequate for modest demands, but not good enough for active professional life. An example of what's not good: I really need database facilities. The Linux options seem to be Ingres and Postgres. The Ingres available for Linux is so bare-bones as to be almost unusable (where are the menu interfaces, anyone?) and I haven't yet succeeded in getting Postgres to work. If even the now obsolescent dBase-III for DOS were ported to Linux this would make work a lot easier. (BTW in the above "need" means NEED: I have work to do). No doubt others can parallel these examples in their own situations. So the possibility of porting good DOS packages to Linux is attractive; they needn't be up-to-date versions since not many people would be stopped in their tracks by lack of the most recent capabilities. Naively, this looks like a good idea. What worries me is that /commercial/ software is a Trojan horse. You want a database? Sure, here, $100, good value at the price. You want graphics too? No, you can't access Linux graphics from within the database. But here's a graphics add-on at $200 that can. And so it goes. Back to the DOS jungle. Is this too pessimistic? The non-commercial alternative is the likes of John Eaton's great 'octave' enterprise. Maybe as Linux matures, and time passes, such things will happen in other areas. I'm optimistic, but not expecting much in the near future. However, unless something happens on one front or the other, Linux is possibly doomed outside the "UNIX ham" world. My basis for hope is that so many people use it and want to carry on using it that positive developments are very likely. Mike pointed out some of the dangers arising from the shifting state of Linux kernels and libraries, etc. I think the time is close where someone has to say: "Here's a kernel; here's a system; and (above all) here's adequate documentation for that, and it's all - in itself - OK", regardless of how fast things are moving at the leading edge of Linux development. Then, but not before, people (e.g. myself) can decide to devote time to developing on top of that for their own purposes. " ....... I changed the subject line in the hope that " you carefully read what I've written, and that you now are willing to start " a serious discussion." (Mike) I hope I've understood, and this is my bit towards a serious discussion. I'm also willing to put my penny of effort in the kitty towards development, but large-scale stuff is not what I'm capable of. Cheers, Ted. ------------------------------ From: nelson@crynwr.crynwr.com (Russell Nelson) Crossposted-To: comp.os.linux.announce Subject: Kernel change summary 1.1.49 -> 1.1.50 Date: 11 Sep 1994 13:59:43 GMT CONFIG_I_AM_A_BROKEN_BSD_WEENIE taken out of config.in Missed a check for the floppy device in the I/O request queuer. Support for detecting the "ST11 BIOS V1.7" added to XT hard disk driver. 3c501 driver made somewhat more reliable by eliminating a critical region. LANCE driver improved to work with VLB NE2100 compatibles, and the HP J2405A and HP Vectra built-in adapter. AHA152x now knows about the VTech Platinum SMP. SCSI drivers know about the QUANTUM PD1225S. Oops. Memory mapper wasn't checking for failed kmalloc's. Moved the arphdr structure to if_arp.h for compatibility with BSD based programs. The 802.2 network handler didn't work with more than one protocol registered. Yet more small nasties removed from the TCP code. BSD accept sematics fixed. -- -russ http://www.crynwr.com/crynwr/nelson.html Crynwr Software | Crynwr Software sells packet driver support | ask4 PGP key 11 Grant St. | +1 315 268 1925 (9201 FAX) | What is thee doing about it? Potsdam, NY 13676 | LPF member - ask me about the harm software patents do. ------------------------------ ** 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 ****************************** .