8K.%),'$V'RE/ZR 6ZA!,B VD %j M@%H$G( @@*E1ICR% 7D:-^* +&(XN 6J0P7D3P!D ?/O[0@>[),"DT_PF3S]i MSP<4J1:HC5J@98*!^R8B;8N2-,)6P J8?]X(]!D.&0);BJ 1/()(, DJP27(h M!)N@$WR"4# *2L$I2 6KH!6\@E@P"VK!+<@%NZ 7_()@, R*P3%(!LN@&3R#g M:# -JL$UR ;;H!M\@W P#LK!.4@'ZZ =O(-X, _JP3W(!_N@'_R#@# 0"L)!f 92 @+H2$\A(@P$2K"1<@(&Z$C?(20,!(^!(-Xe d end --[0097]-- [0098] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 11/19/91 04:48 (82 lines) Subject: The new TODO list and a FTP-admin specific question Date: Tue, 19 Nov 91 10:27:48 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! I am just mailing to remind you that there still exists this TODO-file. If you have ported anything lately or can help me fill the questinable things, please mail me. Following at the end of the file is the latest release of TODO. But before you start dropping this into the trashbin: All FTP-Site-maintainers with Linux-specific stuff, please read at the end of the mail!! =============== Following is TODO ======================= This files contains the status of several tools for Linux Currently ported projects: Name: ported by: available at bison nicholas@cs.uwa.oz.au tupac-amaru nic.funet.fi flex ?? tupac-amaru nic.funet.fi diff ?? tupac-amaru nic.funet.fi kermit ?? tupac-amaru nic.funet.fi =============================================================================== Projects currently under development: Name: ported by: Remarks c386 blum@messua.informatik.rwth-aachen.de Is working under Linux A cc for this exists Is currently teached ANSI. Any help on this would be appreciated. gawk nicholas@cs.uwa.oz.au Still needs a working mathlib. VFS proven@athena.mit.edu VFS=Virtual File System Will probably out with Linux 0.11 Networking jtkohl@echidna.berkeley.edu Mainly the BSD code Perhaps even ffs =================End of TODO======================= Now the stuff for you site admins out there: What do you think of a kind of mailing list for new sources/binaries? E.G: You get the new kernel code. Instead of installing it directly, you post it to the mailing list, and it will be automatically installed on all FTP sites that have joined the mailing list, including yours. So we could keep the whole archives consistent and thus spread the load. Currently, the host who has it first will have the heaviest load. (But wait, funet.fi is the one to have it first... I think we shouldn't do the list :-) You might even offer the linux community to join this list read-only, so everybody who wants to, always finds the newest binaries in his mailbox. Of course, this depends on a) if you have to pay for mail b) how much you have to pay What do you think about this? Do you like the idea? Please send in any replies/thoughts you have concerning this OK, and thank you for listening Robert Blum --[0098]-- [0099] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 11/19/91 05:05 (98 lines) Subject: general Date: Tue, 19 Nov 1991 11:56:09 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi John T Kohl : > Anybody working on GNU emacs? "em" is passable, but I'd like the real > thing... I'd be interested to hear about this too.. I haven't got the disk-space to try to port it myself, but judging from the ease of porting other GNU software it shouldn't be too difficult. Of course, emacs is rather big, and probably wants some features... ? If anybody gets a working binary (and no, I don't think we need all the features: gif-viewing, mail, news etc :-), I'm sure it could be set up for ftp somewhere (both nic and amaru accept incoming ftp: nic in /pub/OS/Linux (but it won't show up immediately), amaru in msdos/replace/incoming or something like that). > In other news, I have now been able to observe program execution speed > differences when I toggle the Turbo switch (easiest to observe by > scrolling lots of text on the console). So it's probably some sort of > timing glitch that prevents booting at full-speed? Do you have any problems at all using the floppy or harddisk later on? It might be that linux uses the IO-ports too often (there are usually (always?) two "jmp $+2" between IO instructions, but on a 33MHz 486 this isn't too much of a delay). I cannot imagine what other timings might be wrong (but if I have forgotten "jmp $+2" somewhere, it's probably in the early code, ie the one that is used at bootup.. I'll check) mgfrank@acsu.buffalo.edu (Marc G. Frank): johnsonm@stolaf.edu (Michael K. Johnson): > [ mtools ] This has been said before on this forum, but it seems there are enough new linux-activists to rehash the problems with mtools: 1 - you have to tell mtools which device to use. This is done by linking (or mknod'ing) the files /dev/dos[A|B|C] to the correct device. (ie mknod /dev/dosA b 2 28 for a 1.44M dos floppy in A etc). 2 - linux-0.10 doesn't support reading/writing from partitions >64M. Be VERY careful if you write to such a partition: the blocks wrap around at 65536. This is easily fixed (I think): change the unsigned short b_blknr in buffer_head to unsigned long, and recompile the kernel. I cannot test it (both my harddisks are <64M), but this should work. Thanks to xxxx. 3 - due to the bug in /usr/include/ctype.h (tolower), mcopy isn't able to do things like "mcopy 'a:*' .", as the names get confused. You'll have to give the new names explicitly, or recompile the mtools with the corrected ctype.h (mtools source can be found at nic.funet.fi: pub/unix/i386/isc/source/mtools* and from several other ftp sites) 4 - /dev/dos[A|B] is hardcoded to 12-bit fats, /dev/dosC is hardcoded for 16-bit fats. There is no /dev/dosD etc. If you have a small harddisk (12-bit FAT), you have to call it A or B. Btw, mtools is not really needed: you can write a tar-file to disk with the rawrite program, and use "tar xvf /dev/xxxx" to untar it unto the linux partition. Thanks to "whoever" for pointing this out (and I hope nobody minds the fact that I never remember names) nicholas@cs.uwa.oz.au (Nicholas Yue) > > (i) 80386 with 80287 I've tried to get a 287 working with linux, but no luck so far. Does anybody know anything about the problems with 287? I tried to put it in protected mode (FSETPM), but that didn't seem to help. I seem to be able to correctly identify it (check for a x87, and if ET is cleared, it's a 287), but it simply won't work it seems? Any pointers to it? Is it at all possible to use a 287 in 386-protected mode? Again I have the problem that I cannot test my changes: the few (unsuccessful) things I tried had to me mailed to nicholas. jtkohl@antipodes.Berkeley.EDU (John T. Kohl): > > It seems whenever I type control-U while in a program, the console bash > dies and the system grinds to a halt. bug? feature? This is an old debugging tool I think. I was testing the keyboard interrupts, and got cc_c[VKILL] to send a SIGKILL to the processes in the tty-group. I used ^U as I never use it myself for other things, and thus promptly forgot about it when it worked. I should make VKILL work the right way (ie just kill the line in cooked mode(?)), but an easy fix to this would be to comment out the line in tty_io.c that calls tty_signal or whatever, and recompile the kernel. Thus you could call it a "feature", even though it isn't documented anywhere (unless you count the sources as docs, which might not be a bad idea anyway). Linus PS. I think I have found the "Invalid TSS: 0000" error that a couple of people have got after soft-booting from DOS: possibly the eflags NT-bit was set, in which case an iret would try to change to TSS 0000, which doesn't exist. It should be corrected in the next version (again, I'm unable to test it - I don't get that error). --[0099]-- [0100] daemon@ATHENA.MIT.EDU (Brian Syme) Linux_Activists 11/19/91 05:20 (18 lines) Subject: Newcomer (sorry folks just bear with me for a min..) Date: Tue, 19 Nov 1991 10:09:29 +0000 From: Brian Syme To: linux-activists@joker.cs.hut.fi Before I start pestering people with daft questions.. is there such a thing as a Linux frequently asked questions list, or similar? Also, is there a list of who is running the system, on what, etc. For info: I'm on a 386sx/20 4MB RAM, 90MB IDE HD, Trying & failing to get linux onto a third 20MB partition (/dev/hd3?), DOS 5 on the first two partitions, [problem is that the minix demo mkfs refuses to create a file system on /dev/hd3 - it complains about the size..] I'll shuddup now.. :-) Brian --[0100]-- [0101] daemon@ATHENA.MIT.EDU (Brian Syme) Linux_Activists 11/19/91 10:19 (20 lines) Subject: Newcomer.. a few questions.. Date: Tue, 19 Nov 1991 14:42:13 +0000 From: Brian Syme To: linux-activists@joker.cs.hut.fi ..the first of which is: Is there a "Frequently Asked Questions" or similar for Linux? If not,.. might be handy? Is there an archive of this mailing list? Is there also a list of who is running Linux, and on what? Might help in targetting questions, advice, etc. For info: I'm on a 386sx/20MHz (TOPCAT chipset), 4MB RAM, 90MB Seagate IDE HD, DOS 5 on 1st & 2nd partitions (FAT-12 then EXTEND, isn't fdisk a pain..) Linux on a final 20MB partition.. Brian Syme Glasgow University Library gxlr07@udcf.gla.ac.uk --[0101]-- [0102] daemon@ATHENA.MIT.EDU (Nicholas Yue) Linux_Activists 11/19/91 19:55 (31 lines) Subject: GCC problem ? Date: Wed, 20 Nov 91 09:52:10 WST From: nicholas@cs.uwa.oz.au (Nicholas Yue) To: linux-activists@joker.cs.hut.fi G'day, The following program does not behave as expected ----------------cut----------------------cut----------------------------------- #include const static double testvalue = 1.234e-09; int main(int argc, char **argv) { (void) printf("test value = %e\n",testvalue); return(0); } ----------------cut----------------------cut----------------------------------- when compiled under linux's gcc, it prints test value = 1.234000e+00 instead of test value = 1.234000e-09 Anybody have any clues? Thanks In Advance nicholas@cs.uwa.oz.au --[0102]-- [0103] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 11/20/91 00:40 (10 lines) Subject: New binaries uploaded --- pmake and less Date: Wed, 20 Nov 91 00:36:56 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: linux-activists@joker.cs.hut.fi Reply-To: tytso@athena.mit.edu Binaries for pmake (the make that comes with BSD 4.4) and for less have been uploaded to tsx-11.mit.edu, nic.funet.fi, and tupac-amaru. These binaries were supplied by John Kohl (jtkohl@cs.berkeley.edu). - Ted --[0103]-- [0104] daemon@ATHENA.MIT.EDU (Tony Travis) Linux_Activists 11/20/91 06:17 (30 lines) Subject: Re: Newcomer.. a few questions.. Date: Wed, 20 Nov 1991 10:41:00 +0000 From: Tony Travis To: linux-activists@joker.cs.hut.fi Cc: ajt@rowett.scot-agric-res-inst.ac.uk, Brian Syme > > ..the first of which is: Is there a "Frequently Asked Questions" or similar > for Linux? If not,.. might be handy? Is there an archive of this mailing > list? Lee McLoughlin is 'mirroring' the Linux archive on where there is already a Minix News archive. I've saved all the mail on the 'activist' list since I joined if that's any use? I could send you a tar of it if you like. > Is there also a list of who is running Linux, and on what? Might help in > targetting questions, advice, etc. For info: (knee tremble) I'm thinking of zapping my Minix 1.5.10/386 in favour of Linux, but I'm not sure! I've got an Elonex 386SX/B with two 40Mb IDE drives and 4Mb RAM. Tony ------------------------------------------------------------------------------- Tony Travis | Rowett Research Institute, | Greenburn Road, Bucksburn, Aberdeen, | UK. AB2 9SB. tel 0224-712751 --[0104]-- [0105] daemon@ATHENA.MIT.EDU (Robert Lund) Linux_Activists 11/20/91 11:18 (23 lines) Subject: FIFOs Date: Wed, 20 Nov 91 09:06:56 MST From: Robert Lund To: linux-activists@joker.cs.hut.fi Has anyone successfully used FIFOs. I have tried but I get the error message: (Read)inode->i_mode=010666 cat: fifo: EINVAL when I try: mknod fifo chmod 666 fifo cat fifo& I can successfully write to it, although its size is always 0. Any ideas. Bob Lund --[0105]-- [0106] daemon@ATHENA.MIT.EDU (Robert Lund) Linux_Activists 11/20/91 11:24 (14 lines) Subject: Re: FIFOs question Date: Wed, 20 Nov 91 09:14:19 MST From: Robert Lund To: linux-activists@joker.cs.hut.fi My example should have shown mkfifo fifo not mknod fifo Bob Lund --[0106]-- [0107] daemon@ATHENA.MIT.EDU (Michael K. Johnson) Linux_Activists 11/20/91 13:31 (27 lines) Subject: problems with binaries Date: Wed, 20 Nov 91 12:18:00 CST From: johnsonm@stolaf.edu (Michael K. Johnson) To: Linux-activists@joker.cs.hut.fi I am new to Linux, and have been having some problems. My main one right now is that I have been bringing binaries from tsx-11 to my computer via dos-formatted disks, and using mread to transfer them to Linux. They uncompress without a hitch, but when I try to run the executable, Linux complains that it cannot execute the binary file. I am also having trouble doing porting work, because I have (as far as I can tell) no editor and no pager. If I am wrong on either point, please point me in the right direction. Even my binaries for sed and tr didn't work, so I can't even use them as editors. I have all sorts of ideas as to why the binaries don't want to execute, but not enough knowledge. If I can get an editor or pager working, I can look at the source to see why this is happening, but I have a chicken/ egg problem here. Thanks for any help you can provide! michaelkjohnson johnsonm@stolaf.edu I don't do .sig 's (as you can tell here, I really don't do .sig's :-) --[0107]-- [0108] daemon@ATHENA.MIT.EDU (Robert Lund) Linux_Activists 11/20/91 15:27 (9 lines) Subject: fifos Date: Wed, 20 Nov 91 13:16:10 MST From: Robert Lund To: Linux-activists@joker.cs.hut.fi Has anyone had any luck getting fifos to work. If so, I'd appreciate hearing how. Bob Lund --[0108]-- [0109] daemon@ATHENA.MIT.EDU (0114) Linux_Activists 11/21/91 04:20 (47 lines) Subject: keyboard.S with GEerman keyboard Date: Thu, 21 Nov 91 10:09:42 +0100 From: 0114 To: linux-activists@joker.cs.hut.fi Cc: Reply_To: upsyf173@comparex.hrz.uni-bielefeld.de Hi all, I think it's time for a GERMAN KEYBOARD DRIVER. So, here it is. "Run this file through uud(ecode), uncompress it and feed it to patch. Don't forget to save the old kernel/chr_drv/keyboard.S. You should then #define KBD_GR in the config.h files and hit make in the src/kernel/chr_drv and src directories to get a new Image file". BTW: I think keyboard.S should be changed to get different key- codes for CursorUp / SHIFT+CursorUp / CONTROL+CursorUp .... which could be defined in a termcap entry. Editors could pro- fit from it. I'm new to GNU asssembler, so I couldn't do it right now. Wolfgang upsyf173@comparex.hrz.uni-bielefeld.de table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 kybd.cdif.Z M'YV0*@*"6%-&CILR;%Z,02/G"QDY=EX0S"/F31@Y9%Q,<1$#1H(I==R >#*&z M#H@8,T[:T#%#AHX:,4[FR!%#08N; PL>3+BPX<.($RM>S#@E 14T=4 X>6,'y MA(R8,&#HD'%#!PT:,FDJ",BUJU<56P7.F$&#Q=@<(+K:Q#FV[(P<,$#^Z,). N3,%C$8 $CL((5($8@3&,&!)DRA ^20;%$w M")$O1Z2D> R"],0O;<+ T4$:KUZ^(!)3;>TBS)PQ:=* $!%#!MD:-F[@@,N%v MRPD1M%_W[7V#10[:MG'K%A'G3D$Z>NJD>0,'R KDD%WO73Z#,?3;N7?;)F/Fu M#!HU:]ALZ>(%O&#EL5F<&'%>^NX\>(QAAQANM,&""RW8)QYLB9V@ F-FR9! t M B^H ,(,-K3P5EHOT$:882HIQMB$%5X81 LTH*5"A^'E-9Y?+4"86(,K4&@As M#2?24 2'R;TXHXQ >E0B#4:T4$,-/+:(WPD\>%C881V)V!ADI)$V!QJ4T8&:r M:JPIZ2,+L[4877HBA,"%"".04(()+Z"00@\_@*&@B[ QYUQ_9$9Q11%24*%%q M%4D\ 45Q*LR)'TKFB8G>=$%,08011R"AQ!),[-&''X9^><()>$Z7!19#6"&$p M$TWLH,,7F3*HWX.)M42BA1AJJ"*+@GT(I0U2OFHBBK/V"-L),?Y(HXT@X(CBo MCBOZVI>P08XX9)%')GG?BR?XX"2(42XV96F0A<&&EJFMIFQ^V^(UYG1

\_517+JI+IOHM+\"T2RS_(Y[@A^*E5-TPLD48B63&^??UU+92):5NEl I79*Q,4<9@4DFAQQOR+%;9T2T0$<> To: Linux-activists@joker.cs.hut.fi And here's the weekly bug-report again (although this time it's mostly harmless "features"). The current gcc for linux is buggy: it doesn't recognise exponents after a floating point number. This isn't gcc's fault: my library-routines are buggy. I've corrected this (I think this one routine was from the estdio suite), and my gcc now handles the correctly. I hope that nobody minds very much, and I'll upgrade the thing at the same time with version 0.11. These kind of library bugs will hopefully disappear with the GNU libc.a: I have a pre-release, and will slowly incorporate parts of it. I hope arl will port the whole thing some day. fifos can be made, but they aren't really supported. Sorry. I don't think they will be supported in the next release either: be patient (or implement them yourself: I'll be happy to use your code) Creating a new file ignores the current euid and egid, and all files will be owned by root/root. You don't ordinarily notice this, as you cannot be other than root without some hacking. Then to some happier things: I seem to have gotten the 287-support working. nicholas@whatever is porting the bsd math-functions to linux, and will make different libraries for none/287/387. Linus --[0110]-- [0111] daemon@ATHENA.MIT.EDU (Michael K. Johnson) Linux_Activists 11/21/91 10:04 (13 lines) Subject: binary problems Date: Thu, 21 Nov 91 08:56:26 CST From: johnsonm@stolaf.edu (Michael K. Johnson) To: Linux-activists@joker.cs.hut.fi Thanks to all who helped me with my binary problems. Seems staying up all hours makes one forget to chmod 755 I have also got editor and pager going, so I'm happy for now :-) michaelkjohnson johnsonm@stolaf.edu I don't do .sig's --[0111]-- [0112] daemon@ATHENA.MIT.EDU (Galen Hunt) Linux_Activists 11/21/91 11:03 (9 lines) Subject: BSD Network stuff... Date: Thu, 21 Nov 91 08:53:41 mst From: Galen Hunt To: Linux-activists@joker.cs.hut.fi To the person that said he would work on the Berkeley network stuff, please drop me an email message as I would like to help you out. galen g-hunt@ee.utah.edu --[0112]-- [0113] daemon@ATHENA.MIT.EDU (John T Kohl) Linux_Activists 11/21/91 12:21 (16 lines) Subject: re: BSD Network stuff... Date: Thu, 21 Nov 91 09:09:40 PST To: linux-activists@joker.cs.hut.fi Cc: g-hunt@ee.utah.edu From: John T Kohl Reply-To: jtkohl@cs.berkeley.edu Well, I may have *sounded* like I was going to tackle the BSD networking stuff, but what I really intended to mean was that I'm tackling code in the BSD "networking" release 2 (which includes a whole heap of code for utilities and libraries). Anybody who wants to deal with the networking code itself (sockets, tcp, etc) is welcome to look at that; for the moment I'm more interested in getting various utilities and libraries from BSD working (they seem to have a rather large C library; maybe even complete!). John --[0113]-- [0114] daemon@ATHENA.MIT.EDU (tthorn@daimi.aau.dk) Linux_Activists 11/23/91 21:58 (24 lines) Subject: Adaptech-1542 driver. Linking system. From: tthorn@daimi.aau.dk To: Linux-activists@joker.cs.hut.fi Date: Sun, 24 Nov 91 3:47:35 MET Hi Linuxers, I'm in the unfortunate situations that I cannot boot Linux:-< My problem is my Adaptech-1542 controler, that Linux doesn't know about. I set out to build a new kernel without harddisk driver using my Interactive Unix 2.0.2 and the GNU tools as development enviroment, but I ran into troubles: gld under ISC doesn't seem to do the same as the Linux version. As pr. default it originates the text at 0xc8 and the data at 0x400000. I can set the text to 0x0, but what's the start of the data- segment? Are there anyone else out there with an adaptech controler dealing with the same problem? Any on the ST-02? /Tommy Thorn --[0114]-- [0115] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 11/24/91 17:27 (27 lines) Subject: Problem with less and elvis Date: Sun, 24 Nov 91 23:21:42 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi I've got less.Z on tsx-11.mit.edu each time i use it, it works fine until the last line where it just stops at that time the only thing I can do is C and this only leads to "child 3 died with code 0000". The only thing i can do is a 3fingers salute About elvis, i've got it on amedeas, then i've done what C. Darken has recommanded BUT eval gcc -DDATE causes trouble "can't open /tmp/????? " and then gcc regexp causes the following message: invalid operand 0000 EIP 000f:0000C050 EFLAGS 00010202 ESP 0017:03FFF2A8 fs:0010 base:20000000 limit 04000000 Stack .... PID 167 process nr8 f0 85 d2 0f 85 fe fe ff ff 89 any ideas [mmc] --[0115]-- [0116] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 11/24/91 17:32 (11 lines) Subject: mea culpae Date: Sun, 24 Nov 91 23:28:06 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi How stupid am I, i've forgotten that less is vi oriented and so at the end :q is a good exit my only excuse is tht i'm used to utilize more on sun still remains the problem of compilation of elvis [mmc] --[0116]-- [0117] daemon@ATHENA.MIT.EDU (Michael K. Johnson) Linux_Activists 11/24/91 21:06 (19 lines) Subject: less Date: Sun, 24 Nov 91 19:59:22 CST From: johnsonm@stolaf.edu (Michael K. Johnson) To: Linux-activists@joker.cs.hut.fi I don't acually know if this will work on Linux, but I don't know why it wouldn't -- it works on the suns... If you hate the way that less makes you exit with :q, try adding these lines to your .profile: LESS="-e"; export LESS Then less should automatically exit at the end of files. Hope this helps those of us who are more or less annoyed with the default behavior of less...:-) michaelkjohnson johnsonm@stolaf.edu I don't do .sig's --[0117]-- [0118] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 11/25/91 03:32 (64 lines) Subject: The latest TODO list Date: Mon, 25 Nov 91 09:21:38 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! This is my weekly post (just to remind you that it exists, I get almost no feedback :-() of the TODO list, which is also available on tupac-amaru So if you have any additions to it please mail me. I hope in one or two weeks, there will also be a first FAQ. Again, if you have any ideas what should belong into it, please mail. BTW: Has anyone succesfully crosscompiled Linux under another OS? I tried it with DJGPP under DOS, and I can't get it running. *ANY* help with it would be appreciated. C U l8er, Robert Blum What follows is the new TODO-file: This files contains the status of several tools for Linux Currently ported projects: Name: ported by: bison nicholas@cs.uwa.oz.au diff tytso@mit.edu flex tytso@mit.edu kermit tytso@mit.edu less jtkohl@berkeley.cs.edu pmake jtkohl@berkeley.cs.edu All these programs can be FTPed as binaries from the following sites nic.funet.fi tsx-11.mit.edu tupac-amaru.informatik.rwth-aachen.de =============================================================================== Projects currently under development: Name: ported by: Remarks c386 blum@messua.informatik.rwth-aachen.de Is working under Linux A cc for this exists Is currently teached ANSI. Any help on this would be appreciated. gawk nicholas@cs.uwa.oz.au Still needs a working mathlib. networking jtkohl@echidna.berkeley.edu Mainly the BSD code Perhaps even ffs Networking= BSD networking Tape VOL2 mathlib nicholas@cs.uwa.oz.au Will be a library for 387/287/soft-float-code VFS proven@athena.mit.edu VFS=Virtual File System Will probably out with Linux 0.11 --[0118]-- [0119] daemon@ATHENA.MIT.EDU (Tony Travis) Linux_Activists 11/25/91 05:32 (61 lines) Subject: more or less Date: Mon, 25 Nov 1991 10:06:00 +0000 From: Tony Travis To: linux-activists@joker.cs.hut.fi I've been reading the comments about vi and less in the last few messages on this list. I much prefer ue (MicroEMACS) as an editor to be called from the pager rather than vi. On Minix/Linux you could edit the sources, and recompile but it's not so easy if you haven't got the sources and, under SunOS for example, the path /usr/bin/vi is hard-coded into the more binary. 'good' programs read and respect the EDITOR variable in the environment, but more seems to be a notable exception. Here is a vi stub that parses the goto argument for vi and invokes ue instead. Install it as /usr/bin/vi :-) Tony ------------------------------------------------------------------------------- Tony Travis | Rowett Research Institute, | Greenburn Road, Bucksburn, Aberdeen, | UK. AB2 9SB. tel 0224-712751 ----- 8< ----- cut here ----- 8< ----- static char *sccsid = "@(#)vi.c 05-Nov-90 A.J.Travis"; /* * kludge to call ue when programs exec vi (eg. more) */ #include #define SAME 0 /* strcmp() equal */ main(argc, argv) int argc; char *argv[]; { char command[BUFSIZ]; int line = 1; if (strcmp(getenv("EDITOR"), "vi") == SAME) { fprintf(stderr, "vi: editor not available on this system\n"); exit(-1); } if (argc > 3) { fprintf(stderr, "usage: vi [+line] [file]\n"); exit(-1); } if (argc > 2) { if (*argv[1] == '+') line = atoi(argv[1]) + 1; argv++; --argc; } if (argc > 1) sprintf(command, "ue -v -g%d %s", line, argv[1]); else sprintf(command, "ue"); system(command); } --[0119]-- [0120] daemon@ATHENA.MIT.EDU (Galen Hunt) Linux_Activists 11/25/91 10:19 (30 lines) Subject: Cross compiling Linux Date: Mon, 25 Nov 91 08:03:38 mst From: Galen Hunt To: linux-activists@joker.cs.hut.fi > BTW: Has anyone succesfully crosscompiled Linux under another OS? > I tried it with DJGPP under DOS, and I can't get it running. *ANY* help with > it would be appreciated. > > C U l8er, > Robert Blum I've successfully cross compiled Linux from the NeXT using GNU C which I had customized for doing the 68040 to 80386 cross compile. If Linux isn't compiling under DJGPP it probably has something to do with the wonderful 8 character dos file names. If it won't run you probably have a problem of another color. It wouldn't run for me at first until I discovered the following: Linux's a.out formatted files use a segment size of 1024 bytes as opposed to most implementations of unix which use either a 4096 or 8192 byte segment size. This will kill you in two ways, first the build.c program put together the boot image for a 1K segment size, this is very easy to get around, just touch up build.c. Evidence of this problem is that when Linux boots, it displays the message about loading the kernel goes out to disk for a few seconds and then either hangs or reboots the computer. The second problem is in the kernel code which loads executables because it once again looks at the 1024 segment offset to load code. The easiest approach of course is to simply recompiler GNU ld on your host machine so that it uses 1024 byte segment sizes. galen --[0120]-- [0121] daemon@ATHENA.MIT.EDU (David R. Giller) Linux_Activists 11/25/91 20:13 (42 lines) Subject: Re: Adaptech-1542 driver. Linking system. From: rafetmad@cheshire.oxy.edu (David R. Giller) To: linux-activists@joker.cs.hut.fi Date: Mon, 25 Nov 91 17:02:20 PST In-Reply-To: <9111240247.AA08306@ananke.daimi.aau.dk>; from "tthorn@daimi.aau.dk" at Nov 24, 91 3:47 am > Hi Linuxers, > > I'm in the unfortunate situations that I cannot boot > Linux:-< My problem is my Adaptech-1542 controler, that > Linux doesn't know about. I have some happy news for all you out there using an EISA bus PC with a Mylex EICS SCSI controller (probably just me). This also applies to all you with a SCSI controller that emulates IDE or ST-506. Linux works with these drives! I am going to see if I can slink some sample code from the Mylex people to include in my kernel to enable things like hardware caching and 32-bit mode, but as it is, the drive works. I am not out of trouble yet, though. I found out that my Mylex emulates IDE the hard way: I installed an IDE to coexist, and the combination trashed my drive. Bummer. After the dust cleared, however, I had a drive that was partitioned better and uses the controller features better under DOS and OS/2. Then, while trying to install Linux, to my dismay -- Minix no longer boots. No matter what I do, on any disk I might try, I always get 'root filesystem corrupted' and panic stop from the minix kernel on startup. Anyone have any clues? This setup worked before... All I chaanged was the partition table. Has anyone created a linux mkfs? Thanks, -Dave -- --------------------------------------------------------------------------- David Giller -- rafetmad@oxy.edu | "Some of us wake up, others roll over." Box 134, Occidental College | "Shrouds, they have no pockets." Los Angeles, CA 90041 | -John Lydon --------------------------------------------------------------------------- --[0121]-- [0122] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 11/25/91 22:36 (394 lines) Subject: newest mkfs for linux Date: Tue, 26 Nov 1991 05:22:04 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi Ok, here's a mkfs for those that want to try it out. It works on my system (limited testing), and hopefully we can get possible bugs ironed out in time for 0.11 (and currently I'm hoping to release that December 8th or something). This mkfs has two modes: checking and reckless. On a disk that you know has no problems, you just write "mkfs /dev/hdx size", and you should have a new system (DON'T do this on a mounted drive: unlike fsck there is NO way that will work, and you'll probably mess it up completely.) On a disk with possible read-errors, use "mkfs -c /dev/hdx size", which will read all the blocks and mark those unreable into a special file "/.badblocks". I'm not making any guarantees. This is a fast hack (mainly yesterday and today), and I have tested only on small filesystems, faking errors by telling mkfs that the filesystem is bigger than it actually is. If you think the algorithm for marking bad blocks is weird: you're right. Linus PS. Using -c on a big harddisk or on floppies is slow, even though I try to speed it up by reading 32kB at a time. Also, the current linux kernel will print out error messages for all the IO errors - that's normal, and that's what this mkfs should map out. ---------------- snip snip ---------- /* * mkfs.c - make a linux (minix) file-system. * * (C) 1991 Linus Torvalds. This file may be redistributed as per * the Linux copyright. */ /* * 24.11.91 - time began. Used the fsck sources to get started. * * 25.11.91 - corrected some bugs. Added support for ".badblocks" * The algorithm for ".badblocks" is a bit weird, but * it should work. Oh, well. * * Usuage: mkfs [-c] device size-in-blocks * * -c for readablility checking (SLOW!) * * The device may be a block device or a image of one, but this isn't * enforced (but it's not much fun on a character device :-). */ #include #include #include #include #include #include #include #include #include #ifndef __GNUC__ #error "needs gcc for the bitop-__asm__'s" #endif #ifndef __linux__ #define volatile #endif #define ROOT_INO 1 #define BAD_INO 2 #define TEST_BUFFER_BLOCKS 32 #define MAX_GOOD_BLOCKS 512 #define UPPER(size,n) ((size+((n)-1))/(n)) #define INODE_SIZE (sizeof(struct d_inode)) #define INODE_BLOCKS UPPER(INODES,INODES_PER_BLOCK) #define INODE_BUFFER_SIZE (INODE_BLOCKS * BLOCK_SIZE) #define BITS_PER_BLOCK (BLOCK_SIZE<<3) static char * program_name = "mkfs"; static char * device_name = NULL; static int DEV = -1; static long BLOCKS = 0; static int check = 0; static int badblocks = 0; #define ROOT_INO_STRING "\001\000" #define BAD_INO_STRING "\002\000" static char root_block[BLOCK_SIZE] = ROOT_INO_STRING ".\0\0\0\0\0\0\0\0\0\0\0\0\0" ROOT_INO_STRING "..\0\0\0\0\0\0\0\0\0\0\0\0" BAD_INO_STRING ".badblocks\0\0\0\0"; static char * inode_buffer = NULL; #define Inode (((struct d_inode *) inode_buffer)-1) static char super_block_buffer[BLOCK_SIZE]; #define Super (*(struct super_block *)super_block_buffer) #define INODES ((unsigned long)Super.s_ninodes) #define ZONES ((unsigned long)Super.s_nzones) #define IMAPS ((unsigned long)Super.s_imap_blocks) #define ZMAPS ((unsigned long)Super.s_zmap_blocks) #define FIRSTZONE ((unsigned long)Super.s_firstdatazone) #define ZONESIZE ((unsigned long)Super.s_log_zone_size) #define MAXSIZE ((unsigned long)Super.s_max_size) #define MAGIC (Super.s_magic) #define NORM_FIRSTZONE (2+IMAPS+ZMAPS+INODE_BLOCKS) static char inode_map[BLOCK_SIZE * I_MAP_SLOTS]; static char zone_map[BLOCK_SIZE * Z_MAP_SLOTS]; static unsigned short good_blocks_table[MAX_GOOD_BLOCKS]; static int used_good_blocks = 0; #define bitop(name,op) \ static inline int name(char * addr,unsigned int nr) \ { \ int __res; \ __asm__ __volatile__("bt" op " %1,%2; adcl $0,%0" \ :"=g" (__res) \ :"r" (nr),"m" (*(addr)),"0" (0)); \ return __res; \ } bitop(bit,"") bitop(setbit,"s") bitop(clrbit,"r") #define inode_in_use(x) (bit(inode_map,(x))) #define zone_in_use(x) (bit(zone_map,(x)-FIRSTZONE+1)) #define mark_inode(x) (setbit(inode_map,(x))) #define unmark_inode(x) (clrbit(inode_map,(x))) #define mark_zone(x) (setbit(zone_map,(x)-FIRSTZONE+1)) #define unmark_zone(x) (clrbit(zone_map,(x)-FIRSTZONE+1)) /* * Volatile to let gcc know that this doesn't return. When trying * to compile this under minix, volatile gives a warning, as * exit() isn't defined as volatile under minix. */ volatile void fatal_error(const char * fmt_string) { fprintf(stderr,fmt_string,program_name,device_name); exit(1); } #define usage() fatal_error("Usage: %s [-c] /dev/name blocks\n") #define die(str) fatal_error("%s: " str "\n") void write_tables(void) { if (BLOCK_SIZE != lseek(DEV, BLOCK_SIZE, SEEK_SET)) die("seek failed in write_tables"); if (BLOCK_SIZE != write(DEV, super_block_buffer, BLOCK_SIZE)) die("unable to write super-block"); if (IMAPS*BLOCK_SIZE != write(DEV,inode_map,IMAPS*BLOCK_SIZE)) die("Unable to write inode map"); if (ZMAPS*BLOCK_SIZE != write(DEV,zone_map,ZMAPS*BLOCK_SIZE)) die("Unable to write zone map"); if (INODE_BUFFER_SIZE != write(DEV,inode_buffer,INODE_BUFFER_SIZE)) die("Unable to write inodes"); } void write_block(int blk, char * buffer) { if (blk*BLOCK_SIZE != lseek(DEV, blk*BLOCK_SIZE, SEEK_SET)) die("seek failed in write_block"); if (BLOCK_SIZE != write(DEV, buffer, BLOCK_SIZE)) die("write failed in write_block"); } int get_free_block(void) { int blk; if (used_good_blocks+1 >= MAX_GOOD_BLOCKS) die("too many bad blocks"); if (used_good_blocks) blk = good_blocks_table[used_good_blocks-1]+1; else blk = FIRSTZONE; while (blk < ZONES && zone_in_use(blk)) blk++; if (blk >= ZONES) die("not enough good blocks"); good_blocks_table[used_good_blocks] = blk; used_good_blocks++; return blk; } void mark_good_blocks(void) { int blk; for (blk=0 ; blk < used_good_blocks ; blk++) mark_zone(good_blocks_table[blk]); } inline int next(int zone) { if (!zone) zone = FIRSTZONE-1; while (++zone < ZONES) if (zone_in_use(zone)) return zone; return 0; } void make_bad_inode(void) { struct d_inode * inode = &Inode[BAD_INO]; int i,j,zone; int ind=0,dind=0; unsigned short ind_block[BLOCK_SIZE>>1]; unsigned short dind_block[BLOCK_SIZE>>1]; #define NEXT_BAD (zone = next(zone)) if (!badblocks) return; mark_inode(BAD_INO); inode->i_nlinks = 1; inode->i_time = time(NULL); inode->i_mode = S_IFREG + 0000; inode->i_size = badblocks*BLOCK_SIZE; zone = next(0); for (i=0 ; i<7 ; i++) { inode->i_zone[i] = zone; if (!NEXT_BAD) goto end_bad; } inode->i_zone[7] = ind = get_free_block(); memset(ind_block,0,BLOCK_SIZE); for (i=0 ; i<512 ; i++) { ind_block[i] = zone; if (!NEXT_BAD) goto end_bad; } inode->i_zone[8] = dind = get_free_block(); memset(dind_block,0,BLOCK_SIZE); for (i=0 ; i<512 ; i++) { write_block(ind,(char *) ind_block); dind_block[i] = ind = get_free_block(); memset(ind_block,0,BLOCK_SIZE); for (j=0 ; j<512 ; j++) { ind_block[j] = zone; if (!NEXT_BAD) goto end_bad; } } die("too many bad blocks"); end_bad: if (ind) write_block(ind, (char *) ind_block); if (dind) write_block(dind, (char *) dind_block); } void make_root_inode(void) { struct d_inode * inode = &Inode[ROOT_INO]; mark_inode(ROOT_INO); inode->i_zone[0] = get_free_block(); inode->i_nlinks = 2; inode->i_time = time(NULL); if (badblocks) inode->i_size = 48; else inode->i_size = 32; inode->i_mode = S_IFDIR + 0755; write_block(inode->i_zone[0],root_block); } void setup_tables(void) { int i; memset(inode_map,0xff,sizeof(inode_map)); memset(zone_map,0xff,sizeof(zone_map)); memset(super_block_buffer,0,BLOCK_SIZE); MAGIC = SUPER_MAGIC; ZONESIZE = 0; MAXSIZE = (7+512+512*512)*1024; ZONES = BLOCKS; /* some magic nrs: 1 inode / 3 blocks */ INODES = BLOCKS/3; /* I don't want some off-by-one errors, so this hack... */ if ((INODES & 8191) > 8188) INODES -= 5; if ((INODES & 8191) < 10) INODES -= 20; IMAPS = UPPER(INODES,BITS_PER_BLOCK); ZMAPS = 0; while (ZMAPS != UPPER(BLOCKS - NORM_FIRSTZONE,BITS_PER_BLOCK)) ZMAPS = UPPER(BLOCKS - NORM_FIRSTZONE,BITS_PER_BLOCK); FIRSTZONE = NORM_FIRSTZONE; for (i = FIRSTZONE ; i ZONES) try = ZONES-current_block; got = read(DEV, buffer, try * BLOCK_SIZE); if (got<0) got = 0; if (got & (BLOCK_SIZE-1)) printf("Weird values in check_blocks: probably bugs\n"); got /= BLOCK_SIZE; current_block += got; if (got == try) continue; if (current_block < FIRSTZONE) die("bad blocks before data-area: cannot make fs"); mark_zone(current_block); badblocks++; current_block++; } if (badblocks) printf("%d bad block%s\n",badblocks,(badblocks>1)?"s":""); } int main(int argc, char ** argv) { char * tmp; struct stat statbuf; if (argc && *argv) program_name = *argv; if (INODE_SIZE * INODES_PER_BLOCK != BLOCK_SIZE) die("bad inode size"); while (argc-- > 1) { argv++; if (argv[0][0] != '-') if (device_name) { BLOCKS = strtol(argv[0],&tmp,0); if (*tmp) usage(); } else device_name = argv[0]; else while (*++argv[0]) switch (argv[0][0]) { case 'c': check=1; break; default: usage(); } } if (!device_name || BLOCKS<10 || BLOCKS > 65536) usage(); DEV = open(device_name,O_RDWR); if (DEV<0) die("unable to open %s"); if (fstat(DEV,&statbuf)<0) die("unable to stat %s"); if (!S_ISBLK(statbuf.st_mode)) check=0; else if (statbuf.st_rdev == 0x0300 || statbuf.st_rdev == 0x0305) die("Will not try to make filesystem on '%s'"); setup_tables(); if (check) check_blocks(); make_root_inode(); make_bad_inode(); mark_good_blocks(); write_tables(); return 0; } --[0122]-- [0123] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 11/27/91 03:56 (58 lines) Subject: help again and again Date: Wed, 27 Nov 91 09:48:06 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi Hi, there It seems that i have trouble with compilition under linux, these are the things i've remarked. first of all the config: 386sx, no 387, 2Mo ram, 30 Meg Linux partition on Hd the soft config: those on tsx11 mainly + those which appeared in this mailing list ok, now the things i tried compile fsck : noway (gcc -c works not the -o which complains in many undefined symbols such as IN or inode-map zone-map super-block-buffer .... the rest has been skipped compile elvis: not yet fixed (i'll try some C. Darken proposal) compile linux: first i've changer the buffer.c i've applied the build patch i've done some ack on keyboard.S to have a more french oriented kbd i've change the config.h for the kbd, and commented the lines in the linux/Makefile (those for the 16binaries and the chmem) and then just type make - the (cd ?????;make) *DOES NOT WORK* in the sense that it does not run the gcc -c commands, only the gld ones so ERROR - then i tried a bottom up compilation of linux subtree, i.e apply by hand the make on each subdirs, and then run make in linux. the make in sub-dirs works fine, not the final linking in general it complains about a lot of undefinde symbols - finally i've tried the make clean command funnily :-( it does not work, just clean the linux and boot directories (the one without make) THEN (again yes) i thought it was due to the place of the linux subtree which is not under /, but under /usr/src so i've change all the path in absolute path name. RESULT: NIET THEN and LAST: i've changed in the subdirs the clean order from rm -f blabla to rm -i blabla in that case the global clean works fine, and asks me for the deletion which i agree and it does clean. so questions are: has any one tried to compile linux under linux? has any one had such experience? has any one cast a spell on me? 8-) what about make/ PS: i've tried some simple compilation as uudecode/wc which were ok [mmc] --[0123]-- [0124] daemon@ATHENA.MIT.EDU (Mika Matti Jalava) Linux_Activists 11/27/91 04:07 (21 lines) Subject: Re: help again and again From: Mika Matti Jalava To: linux-activists@joker.cs.hut.fi Date: Wed, 27 Nov 91 11:01:37 EET In-Reply-To: <9111270848.AA17452@geocub.greco-prog.fr>; from "Marc CORSINI" at Nov 27, 91 9:48 am > ok, now the things i tried > compile fsck : noway (gcc -c works not the -o which complains in many > undefined symbols such as IN or inode-map zone-map super-block-buffer .... > the rest has been skipped Do you have all the includes in place? > has any one tried to compile linux under linux? Yes, no problems (with compiling, that is, the compiled images work great. I have had a LOT of problems with the file system but that's probably because of my old drives) > has any one cast a spell on me? 8-) Not me... Mika --[0124]-- [0125] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 11/27/91 05:17 (70 lines) Subject: Re:help again and again Date: Wed, 27 Nov 91 11:01:46 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! Today there was the following mail in my mbox: >From corsini@geocub.greco-prog.fr Wed Nov 27 09:52:10 1991 >Subject: help again and again and I think that the answer will be of (more or less) general interest, so I decided to not reply personally and instead via mailing list. Corsini wrote: >Hi, there >It seems that i have trouble with compilition under linux, these are >the things i've remarked. >first of all the config: >386sx, no 387, 2Mo ram, 30 Meg Linux partition on Hd And whoops, there's the problem. GCC dies silently if it has not enough memory instead of issuing any warnings. It simply produces incomplete .s/.o files, and nothing will work. If you think of it, it's quite simple: Memory you have: 2000 KB Kernel/Buffers: 1000 KB bash: approx. 300 KB cc1: approx. 500 KB =============================== Free space: approx. 200 KB And into these 200 KB gcc/bash have to squeeze their complete bss sections, and I forgot make in the list of memory hogs. Seems a little bit tight, huh? There are some solutions to it: 1) Buy another 2 Megs of memory, and all will work fine. 2) Wait for c386 to come out, it uses only 100 KB. I intended to make it available as soon as it understands __asm__ and ANSI, but if there's a real need for it, I could release it in its original version as a K&R compiler. But this means: No kernel compiling, compilation of other files only with tweaked #include-files 3) Join me in my efforts to make this beast ANSI conforming... 4) Try to cross-develop under DOS with DJGPP, but there are several obstacles a) The gcc header of system seems only 32 bytes, so change build.c b) gld links code starting at 0x1020, so give it a -Ttext 0 c) gld links data starting at 0x400000, so give it a -Tdata 15000 But even with these changes, my kernel does not work, so could anybody help me with this, please ? >so questions are: >has any one tried to compile linux under linux? Yes, and it worked no way. >has any one had such experience? Yes, not enough mem.... >has any one cast a spell on me? 8-) Yes, GNU has cast the "eat lots of memory"-spell onto it's software >what about make/ As far as I can tell from my experiences with c386, this seems to be working, but you might try pmake... >PS: i've tried some simple compilation as uudecode/wc which were ok This is *REALLY* surprising to me, since gcc doesn't manage to create a "hello world" program. Are the sources without any #include? Then it might work, otherwise we are in trouble.... Hope this helps, Robert Blum --[0125]-- [0126] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 11/27/91 05:41 (21 lines) Subject: Re:help again and again Date: Wed, 27 Nov 91 11:27:47 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: blum@cip-s01.informatik.rwth-aachen.de Cc: linux-activists@joker.cs.hut.fi In-Reply-To: Robert Blum's message of Wed, 27 Nov 91 11:01:46 +0100 <9111271001.AA26828@messua.informatik.rwth-aachen.de> Thanks for the help, about the uudecode and wc, indeed the includes are very few stdio,ctypes and one or two more. On the other hand i still suspect heavily the make since on elvis compiling with make all works fine except the gcc -O -o -c of cmd1.c the gcc -o of virec the gcc -o of refont BUT when i do these commands by hand they work great so .. i'll change to pmake [mmc] --[0126]-- [0127] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 11/27/91 06:24 (12 lines) Subject: elvis compilation/help again and again Date: Wed, 27 Nov 91 10:18:45 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi Ok just tried the elvis compilation nearly good, just a /tmp/cc000041.s can't open for Reading about the include i've put the include.tar.Z where it is supposed to be i guess in /usr/include, have i forgotten some thing? [mmc] --[0127]-- [0128] daemon@ATHENA.MIT.EDU (Nicholas Yue) Linux_Activists 11/27/91 09:53 (34 lines) Subject: 486 problem Date: Wed, 27 Nov 91 23:44:13 WST From: nicholas@cs.uwa.oz.au (Nicholas Yue) To: linux-activists@joker.cs.hut.fi G'day, Today, I upgraded my machine from a 386DX to a 486DX (using the old drives), I had the following problem. ------cut------------cut----------- Partiion table ok ...... W/X free blocks Y/Z free inodes HD-controller reset failed : 7f 501 buffers = 513024 bytes buffer space Free mem: 3145728 Ok. general protection: 0000 EIP : 000f:00000013 etc........ -------cut-----------cut------------- and then it hangs! I had it working beautifully on a 386DX, I don't have a 386 anymore! Any opinion? Thanks In Advance nicholas@cs.uwa.oz.au --[0128]-- [0129] daemon@ATHENA.MIT.EDU (Wolfgang Thiel) Linux_Activists 11/27/91 10:53 (11 lines) Subject: Re: help again and again Date: Wed, 27 Nov 91 11:36:37 CET From: Wolfgang Thiel To: Marc CORSINI , In-Reply-To: Your message of Wed, 27 Nov 91 09:48:06 EST Hi, I had absolutely no problems compilung linux under linux (486, 8MB). Sounds like gcc and/or make are running out of memory. Wolfgang --[0129]-- [0130] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 11/27/91 11:34 (36 lines) Subject: Re: help again and again Date: Wed, 27 Nov 91 11:25:02 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: blum@cip-s01.informatik.rwth-aachen.de Cc: linux-activists@joker.cs.hut.fi In-Reply-To: Robert Blum's message of Wed, 27 Nov 91 11:01:46 +0100, Reply-To: tytso@athena.mit.edu Date: Wed, 27 Nov 91 11:01:46 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) Memory you have: 2000 KB Kernel/Buffers: 1000 KB bash: approx. 300 KB cc1: approx. 500 KB =============================== Free space: approx. 200 KB And into these 200 KB gcc/bash have to squeeze their complete bss sections, and I forgot make in the list of memory hogs. Seems a little bit tight, huh? If this is the problem, one solution might be to modify the Makefile so that instead of compiling and assembling a file at the same time, to split it into two steps: .c.s: ; cc $(CFLAGS) -S $*.c .s.o: ; gas $(LDFLAGS) -o $*.o $*.s That way, the compiler and the assembler won't need to be in memory at the same time. Someone with two meg of memory should try this, and see if this will free enough memory so that a compile happens. Another solution, of course, is to implement paging under Linux. :-) - Ted --[0130]-- [0131] daemon@ATHENA.MIT.EDU (tthorn@daimi.aau.dk) Linux_Activists 11/27/91 12:25 (19 lines) Subject: Building a hd-less bootimage..? From: tthorn@daimi.aau.dk To: Linux-Activists@joker.cs.hut.fi (linux) Date: Wed, 27 Nov 91 18:17:33 MET Hi all (yes, yes, it's me again:-) I still haven't seen Linux run.) With the kind help of Galen Hunt, I've succed in building a new boot- image. I'm aware that it's most likely my adaptech 1542B that kills it, but just commenting hd_init out didn't help. The systems gets as far as to 'move_to_user_mode' in main.c. I would like to succed with a hd-less Linux, before attempting an adaptech driver. Any clues on what to remove/how to build such a kernel? Sorry to have taken your time. /Tommy "me again" Thorn --[0131]-- [0132] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 11/27/91 12:46 (27 lines) Subject: Re: Building a hd-less bootimage..? Date: Wed, 27 Nov 1991 19:29:00 +0200 From: Linus Benedict Torvalds In-Reply-To: tthorn@daimi.aau.dk's message as of Nov 27, 18:17 To: tthorn@daimi.aau.dk, Linux-Activists@joker.cs.hut.fi (linux) tthorn@daimi.aau.dk: "Building a hd-less bootimage..?" (Nov 27, 18:17): > Hi all (yes, yes, it's me again:-) I still haven't seen Linux run.) > > With the kind help of Galen Hunt, I've succed in building a new boot- > image. I'm aware that it's most likely my adaptech 1542B that kills > it, but just commenting hd_init out didn't help. The systems gets > as far as to 'move_to_user_mode' in main.c. > > I would like to succed with a hd-less Linux, before attempting > an adaptech driver. Any clues on what to remove/how to build such > a kernel? You'll have to comment out all the stuff in "sys_setup" which concerns harddisks. hd_init() just sets up the interrupt addresses and enables them, but doesn't read the partition tables etc. The reason is simple: hd_init() may not sleep, as it is called when we aren't really set up yet, so it cannot read the disk, just set up for it. sys_setup mounts the root etc, so you cannot just comment it out totally, you have to comment out just the partition-reading etc. Linus --[0132]-- [0133] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 11/27/91 14:56 (20 lines) Subject: X11R5 has 386/VGA support... Date: Wed, 27 Nov 91 14:48:04 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: linux-activists@joker.cs.hut.fi Reply-To: tytso@athena.mit.edu FYI, in case anybody feels like tackling it, the X11R5 distribution includes a 386/SVGA X server, with drivers to support the GVGA, PVGA1A, ET3000 and ET4000 chipsets in 256 color mode. It's designed for SCO Unix, but it shouldn't *too* hard to port it to Linux.... :-) I imagine that the major problems involved in porting it to Linux are (in order of severity) no FIFO support, no pty support, and no networking interface. The last actually isn't very important (the clients and the server could communicate through unix:0), but it would be nice to have, eventually. So, is anyone interesting in getting X11 to work on Linux? 'twould be really neat! - Ted --[0133]-- [0134] daemon@ATHENA.MIT.EDU (Hakkarainen Kimmo) Linux_Activists 11/28/91 05:54 (15 lines) Subject: kermit problem From: h108373@cs.tut.fi (Hakkarainen Kimmo) To: linux-activists@joker.cs.hut.fi (Linux activists) Date: Thu, 28 Nov 91 12:40:32 EET Hi linuxers, My kermit program terminates in my linux machine when I try to send CNTL-c to remote machine. Shouldn't kermit operate in raw-mode instead of c-break-mode ? Thank's in advance. -- Kimmo Hakkarainen (h108373@cc.tut.fi) --[0134]-- [0135] daemon@ATHENA.MIT.EDU (Nicholas Yue) Linux_Activists 11/29/91 19:47 (32 lines) Subject: 2nd Physical Hard-Disk Date: Sat, 30 Nov 91 09:18:22 WST From: nicholas@cs.uwa.oz.au (Nicholas Yue) To: linux-activists@joker.cs.hut.fi G'day, How do I mount the 2nd hard-disk (automagically ;-). The boot floppy can be configured to mount the root file system form /dev/hdX where 1<=X<=4 OR 6<=X<=9 I know I can mount the 2nd hardisk manually mount /dev/hd6 /home (example) Does this means that I have to have to umount /dev/hd6 (example) it everytime I reboot the machine or is it ok to leave it as it is? On the Sun, there is a file call "fstab" which the boot process looks for. Will there be a "shutdown" program to umount the hard-disk? Thanks In Advance nicholas@cs.uwa.oz.au --[0135]-- [0136] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 11/29/91 21:52 (50 lines) Subject: weekly (?) answers, bugreports etc Date: Sat, 30 Nov 1991 04:46:48 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi nicholas@cs.uwa.oz.au (Nicholas Yue): > G'day, > How do I mount the 2nd hard-disk (automagically ;-). The boot floppy can > be configured to mount the root file system form /dev/hdX Minix does this in /etc/rc, but as linux currently ignores that, the best way is to do it in your .profile (or /etc/.profile). You migh want to use 'mount /dev/hdX /home &> /dev/null' so that eventual multiple mounts won't print error messages. Likewise you can unmount in .logout, but unmounting isn't really necessary (but do remeber to sync). many: > > kermit works, but dies due to ^C. What's wrong? It also complains > about not being able to lock the line. This /seems/ to be standard behaviour of unix-kermit, and it is certainly not of my doing. It's a nuisance. Line-locking is done by creating a file in the directory /usr/spool/uucp/LCK, and unless that directory exists, kermit isn't able to lock it. Then to bug-reports and updates: hd.c is buggy, and I'm investigating it. When read-errors occur, weird things can happen, including writing to the disk. This might be the cause of some peoples problems: there is no problem if you have a sector-translating controller (eg IDE etc) that never returns errors. I think I've gotten it working, and hopefully the 0.11 version (due out in about a week) will be correct. 0.11 will also finally be totally self-sustaining: I have gotten the source to bruce evans' assembler and linker, and at least I haven't heard of many problems with mkfs and fsck. I didn't have time to implement symlinks, so there are no real new features: just bug-fixes and enhancements. Thanks to everybody who sent diffs etc. You know who you are, and I've tried to accnowledge everyone in the source. Wolfgang XXXX, who made the German keyboard patch, please mail me your last name. Known bugs still unresolved: at least one machine has trouble reading the floppy, and one 486 seems to have problems with the harddisk even with my new patches. Another machine seems to get divide by zero errors, and I have absolutely no idea why this happens. As it looks now, these won't be corrected in 0.11 unless I can find the reason for them within the week :-( Linus --[0136]-- [0137] daemon@ATHENA.MIT.EDU (Yanek Martinson) Linux_Activists 11/30/91 14:51 (26 lines) Subject: HELP. Linux boot disk boots but does not display any prompt (shell?) To: linux-activists@joker.cs.hut.fi Date: Sat, 30 Nov 91 14:34:40 EST From: Yanek Martinson I downloaded the boot-disk and root-disk from the mit ftp site. Also the rawrite that comes with minix demo, and the minix demo itself. I wrote minix demo out to a disk with rawrite, and it worked fine. I created a file system on the hard disk. Then I copied the root and boot linux images to disks (5.25" 1.2MB) and tried to boot from the boot image. It said "Loading system......" and then when It was done loading it did nothing. I could type anything, it would just echo the characters. When I pressed any of the F-keys, it gave this: 0: pid=0, state=1, eip=0017:00000000 what does this mean? What can I do about it? If it makes any difference, I was using the boot image that was supposed to turn caps lock key into control key. That part worked. When I pressed CAPSLOCK-N I saw ^N. -- yanek@mthvax.cs.miami.edu safe0%yanek@mthvax.cs.miami.edu --[0137]-- [0138] daemon@ATHENA.MIT.EDU (Yanek Martinson) Linux_Activists 11/30/91 20:35 (19 lines) Subject: linux problem (boots, no prompt) Date: Sat, 30 Nov 91 20:31:15 -0500 From: Yanek Martinson To: torvalds@cc.helsinki.fi, torvalds@kruuna.helsinki.fi Cc: linux-activists@joker.cs.hut.fi I sent a message before but I don't know if you received it I addressed it wrong. The problem is: I put the images of boot and root on disks, and boot. It boots, displays "Loading System..." and then when it's done there is no prompt. Whatever I type is echoed back to me. If I press any of the F- keys, I get this: 0: pid=0, state=1, eip=0017:00000000 What does this mean? Am I doing anything wrong? Is the shell on root or on boot disk? At what time am I supposed to insert the second disk? --[0138]-- [0139] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 11/30/91 21:31 (36 lines) Subject: Re: linux problem (boots, no prompt) Date: Sun, 1 Dec 1991 04:22:30 +0200 From: Linus Benedict Torvalds In-Reply-To: Yanek Martinson's message as of Nov 30, 20:31 To: Yanek Martinson , torvalds@cc.helsinki.fi Cc: linux-activists@joker.cs.hut.fi Yanek Martinson: "linux problem (boots, no prompt)" (Nov 30, 20:31): > I sent a message before but I don't know if you received it I addressed > it wrong. The problem is: I put the images of boot and root on disks, > and boot. It boots, displays "Loading System..." and then when it's > done there is no prompt. Whatever I type is echoed back to me. If > I press any of the F- keys, I get this: > > 0: pid=0, state=1, eip=0017:00000000 This is a kind of debugging info: it just means that the swapper (process 0) is the only task running. Normally state=1 means that the task is waiting (but wakeable by signals), but the swapper is a special case and simply ignores state. eip is useless: this value just means that you have never made a task-switch, and thus saved anything in the task-info. > Is the shell on root or on boot disk? At what time am I supposed to insert > the second disk? The kernel should prompt you for it, but my guess is that the fork is failing, as you only have the swapper task. This might happen if you have only 1M of memory, and nothing above it. True? Even with 384kB of extended memory (usual on 1M machines) the first fork should work, but this looks like you have no extended memory at all. If that wasn't it, please give more info on your hardware. Right now I cannot think of anything else, as most things seem to work (keyboard, screen -> interrupts work ok, no lock-up). Linus --[0139]-- [0140] daemon@ATHENA.MIT.EDU (Galen Hunt) Linux_Activists 12/01/91 23:37 (26 lines) Subject: Display drivers, and no messages after "Loading System..." Date: Sun, 1 Dec 91 21:30:03 mst From: Galen Hunt To: linux-activists@joker.cs.hut.fi > I sent a message before but I don't know if you received it I addressed > it wrong. The problem is: I put the images of boot and root on disks, > and boot. It boots, displays "Loading System..." and then when it's > done there is no prompt. Whatever I type is echoed back to me. If > I press any of the F- keys, I get this: > > 0: pid=0, state=1, eip=0017:00000000 > > What does this mean? > > Am I doing anything wrong? > > Is the shell on root or on boot disk? At what time am I supposed to insert > the second disk? I'd be willing to bet $50 dollars that you are trying to run Linux on a machine that doesn't have a VGA or EGA monitor. The .10 release doesn't have tty driver for monochrome cards (ala Hercules and MDA). galen =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= galen c. hunt g-hunt@ee.utah.edu --[0140]-- [0141] daemon@ATHENA.MIT.EDU (Yanek Martinson) Linux_Activists 12/02/91 00:46 (28 lines) Subject: linux not booting and $50 and memory To: g-hunt@ee.utah.edu (Galen Hunt) Date: Mon, 2 Dec 91 0:39:06 EST From: Yanek Martinson Cc: linux-activists@joker.cs.hut.fi In-Reply-To: <9112020430.AA03364@cs.utah.edu>; from "Galen Hunt" at Dec 1, 91 9:30 pm > I'd be willing to bet $50 dollars that you are trying to run Linux on > a machine that doesn't have a VGA or EGA monitor. The .10 release doesn't This is great. You can send a $50 check to Yanek Martinson 1321 N 65 Way Hollywood, FL 33024 Thank you. This will help me pay for the extra memory I need. The truth is, that I do have a VGA. The problem is, as Linus guessed correctly, that I only have 1MB of memory and that is not enough for linux. Thus the first fork fails, and that is why there is no init or shell or anything else. -- yanek@mthvax.cs.miami.edu safe0%yanek@mthvax.cs.miami.edu --[0141]-- [0142] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 12/02/91 19:18 (13 lines) Subject: microemacs Date: Tue, 3 Dec 91 01:08:10 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi Hi there, I've got micro-emacs 3.9 sources (I know the actual are 3.11), and tried to compile them (Now I've 386sx and 4Mo). I've selected USG in estruct.h and TERMCAP as entry for terminal. The compilation works fine but emacs doen't work. It seems that the system is not able to manage the virtual screen. Any clue? [mmc] --[0142]-- [0143] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/03/91 07:24 (41 lines) Subject: last call for diffs for 0.11 Date: Tue, 3 Dec 1991 13:57:58 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi Yow, as the subject says, this is the last call for diffs for the 0.11 kernel. If you have bug-fixes or enhancements, I'll have to get them before friday (6.12.91) in order for them to find their way into the new kernel. I'll do the "last rites" for the new kernel during the weekend, and put it out for ftp after that. Changes between 0.10 and 0.11: - fixed bugs in block-device drivers: floppies still have problems when accessing 2 floppies at the same time, but otherwise everything seems to work. - german keyboard (thiel) - console beeping (jtkohl). - corrected owner checks, #!-recognition in execve (tytso) - sticky directories (both me and tytso) - demand-loading - page-sharing between all processes. I doubt demand-loading makes anything any faster, but it made page-sharing possible, so it was "a good thing". Page sharing means that when executing a new image, the pages aren't loaded from disk if some other process has them. Especially on a multi-user setup (when we get the init/login), this will speed things up and save memory. I'll also release the bruce evans 86-assembler binaries at about the same time as 0.11, as well as a new root-disk with the new system binaries (mkfs, fsck and fdisk). Fdisk doesn't do anything, it just checks the partition table and prints out the partitions. Linus --[0143]-- [0144] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/04/91 00:40 (14 lines) Subject: compiling under minix? Date: Tue, 3 Dec 91 21:26:28 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Has anyone done this? When trying to compile Linux under Minix I get a missing "divi.." or something on link. I assume these to be soft floating point routines. Why? I have a problem with the harddisk driver under Linux being to fast. I had the same problem with minix, but being smaller and slower, I was able to do enough compiling to put a delay in the read function of wini.c. Linux uses GCC, which use causes so much disk reading to happen, that compiling is out of the question. --[0144]-- [0145] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/04/91 06:03 (24 lines) Subject: Re: compiling under minix? Date: Wed, 4 Dec 1991 12:57:53 +0200 From: Linus Benedict Torvalds In-Reply-To: Peter MacDonald's message as of Dec 3, 21:26 To: pmacdona@sol.UVic.CA (Peter MacDonald), linux-activists@joker.cs.hut.fi Peter MacDonald: "compiling under minix?" (Dec 3, 21:26): > Has anyone done this? When trying to compile Linux under Minix > I get a missing "divi.." or something on link. I assume these > to be soft floating point routines. > > Why? I have a problem with the harddisk driver under Linux > being to fast. I had the same problem with minix, but being smaller > and slower, I was able to do enough compiling to put a delay in the > read function of wini.c. Linux uses GCC, which use causes so much > disk reading to happen, that compiling is out of the question. When compiling under minix, you are probably using an older version of gcc (1.37.1 is the one that was on plains). Older versions are unable to inline the integer division routines, and use a function found in gnulib for division instead. Include gnulib in the final link, and all should work. (Use the gnulib with minix - at least that one has been tested with these functions). Linus --[0145]-- [0146] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/04/91 13:28 (25 lines) Subject: cc1 fails silently From: "LCDR Michael E. Dobson" To: linux-activists@joker.cs.hut.fi (Linix Mailing LIst) Date: Wed, 4 Dec 91 13:01:58 EST Today when I had some time I wanted to try installing a pager and some library routines. Imagine my surprise when nothing would compile! I could not even get the very simple fixit.c program to compile, even gcc -c fixit.c -o fixit.o produced nothing!! Using gcc -v and manually running the indiviual steps, it seems cc1 is failing silently, ie, if I run the cc1 command from gcc -v on the output from cpp, I get no .s file produced! This all used to work fine for me, I was even able to build the recently posted mawk with little effort. Does anyone have a clue as to what is going on? I'd like to get this solved so I can get less up and move on to bigger things. I'm looking to see what needs to be done to the posix/stdc lib routines that came with the new pdksh sources. THey look to have at least a complete string package which means I can then tackle uucp/mail/news. Any suggestions greatly appreciated. -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0146]-- [0147] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/04/91 14:33 (39 lines) Subject: Re: cc1 fails silently Date: Wed, 4 Dec 1991 21:13:38 +0200 From: Linus Benedict Torvalds In-Reply-To: "LCDR Michael E. Dobson"'s message as of Dec 4, 13:01 To: "LCDR Michael E. Dobson" , "LCDR Michael E. Dobson": "cc1 fails silently" (Dec 4, 13:01): > Today when I had some time I wanted to try installing a pager and some > library routines. Imagine my surprise when nothing would compile! I could > not even get the very simple fixit.c program to compile, even gcc -c > fixit.c -o fixit.o produced nothing!! Using gcc -v and manually running > the indiviual steps, it seems cc1 is failing silently, ie, if I run the cc1 > command from gcc -v on the output from cpp, I get no .s file produced! > This all used to work fine for me, I was even able to build the recently > posted mawk with little effort. Does anyone have a clue as to what is > going on? cc1 failing silently is usually due to out of memory errors, but as it worked for you before, that probably isn't it. The only other solution I can come up with is kernel bugs :-(. It seems there are a few race-conditions left in 0.10, which can cause filesystem errors. The worst of these was fixed with the new buffer.c, and if you don't have the updated binaries, filesystem errors are a certainty after a while (unless you are very lucky). Fsck is not (and never will be) able to find errors that have creapt in into the data-blocks of files - and as cc1 is the biggest binary linux uses, that's the one most likely to catch these errors. There was another race-condition I found only yesterday, but it shouldn't cause too many problems, especially not for harddisks. That one will be corrected in 0.11 (countdown: 4-5 days). I'm not even certain this one can ever happen. I'd suggest you verify your binary, and you might even upgrade to the gcc-cc1 that understands floats with exponents, available from Tupac-Amaru (incoming). If that doesn't cut it, I'd be interested in what changes you have made to your hardware/system? Linus --[0147]-- [0148] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/04/91 16:27 (51 lines) Subject: Re: cc1 fails silently From: "LCDR Michael E. Dobson" To: linux-activists@joker.cs.hut.fi (Linix Mailing LIst) Date: Wed, 4 Dec 91 15:50:07 EST In-Reply-To: <9112041942.AA05005@tsx-11.MIT.EDU>; from "Theodore Ts'o" at Dec 4, 91 2:42 pm In response to my question about cc1 failing silently I received the following: > > Date: Wed, 4 Dec 1991 21:13:38 +0200 > From: Linus Benedict Torvalds > > cc1 failing silently is usually due to out of memory errors, but as it > worked for you before, that probably isn't it. The only other solution > I can come up with is kernel bugs :-(. > From: <9112041942.AA05005@tsx-11.MIT.EDU>; from "Theodore Ts'o" at Dec 4, 91 2:24pm > Have you checked to see if you've filled your hard disk? This is > somewhat hard to check since there's no df utility. You can find out > the number of free blocks of your root partition at boot time, though. > It appears you both were wrong and it is something more trouble, possibly related to the race conditions Linus mentioned, but more likely some subtle kernel bugs. I forgot to mention I received a swapper panic when I soft booted from DOS the first time and just redid the soft boot. Just a few minutes ago I did a hard boot (ie hit the reset button) and saw the following at bootup: Partiton table ok. 5278/9860 free blocks 2798/3294 free inodes 507 buffers = 519168 bytes free buffer space Free mem: 3145728 bytes Ok. bash# A "du" on / gave 8423 /. The best part is that gcc now works just fine!! However, the make of less failed because I don't have a sgtty.h Will grab the Minix version and see what develops. It's also looking for libtermcap.a but we'll see ;-) Regards, -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0148]-- [0149] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/04/91 21:30 (42 lines) Subject: Re: cc1 fails silently Date: Wed, 4 Dec 91 21:13:22 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: "LCDR Michael E. Dobson" Cc: linux-activists@joker.cs.hut.fi In-Reply-To: LCDR Michael E. Dobson's message of Wed, 4 Dec 91 15:50:07 EST, Reply-To: tytso@athena.mit.edu It appears you both were wrong and it is something more trouble, possibly related to the race conditions Linus mentioned, but more likely some subtle kernel bugs. Well, maybe. The swapper panic which happens after you type ctrl-alt-del from DOS is standard in Linux 0.10 --- it's harmless, and typing ctrl-alt-del after the panic will allow Linux to boot successfully. Partiton table ok. 5278/9860 free blocks 2798/3294 free inodes 507 buffers = 519168 bytes free buffer space Free mem: 3145728 bytes Ok. bash# A "du" on / gave 8423 /. Remember that "du" outputs sizes in 512 byte blocks, courtesy of POSIX. My personal opinion is that it's one of the stupidest mistakes POSIX has committed, since most users care about file sizes in kilobytes, not in 512 byte blocks --- but then, I can alias du to "du -k", so the only losers are the innocent, naive users. [End of soapbox] With that said, you may have a problem, but it looks like the standard corrupted filesystem problem that happens when you are using a stock, unpatched version of Linux 0.10. The number of free blocks as caluclated by the "du" is (9860 - 8423/2) = 5644, which is larger than 5278, but only by 366k. I've seen that sort of lossage on the stock Linux 0.10, and I haven't seen it once the bug fix to buffer.c was applied. - Ted --[0149]-- [0150] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/04/91 22:31 (199 lines) Subject: Re: cc1 fails silently Date: Thu, 5 Dec 1991 05:15:29 +0200 From: Linus Benedict Torvalds In-Reply-To: Theodore Ts'o's message as of Dec 4, 21:13 To: tytso@athena.mit.edu, Cc: linux-activists@joker.cs.hut.fi Theodore Ts'o: "Re: cc1 fails silently" (Dec 4, 21:13): > > With that said, you may have a problem, but it looks like the standard > corrupted filesystem problem that happens when you are using a stock, > unpatched version of Linux 0.10. The number of free blocks as > caluclated by the "du" is (9860 - 8423/2) = 5644, which is larger than > 5278, but only by 366k. I've seen that sort of lossage on the stock > Linux 0.10, and I haven't seen it once the bug fix to buffer.c was > applied. It does seem so, but always remeber that du doesn't count blocks exactly: it uses a heuristic algorithm that doesn't work on sparse files etc. I'd still check the filesystem - that's the most likely problem. And then over to happier things: here's sources to mount and umount, as corsini wanted something that keeps track of mounted devices, and as I couldn't find anything more interesting to do I just hacked these together . These versions keep the file "/etc/mtab" up-to-date, just like real mount/umount should do. You can certainly confuse them, but they are a bit better than nothing. This is a 1/2 hour hack, so don't expect wonders, but my limited testing hasn't shown any problems yet. /etc/mtab will later be needed for "df", but as ustat isn't implemented yet, df won't work. Oh well. Meanwhile you can get mount-info by "cat /etc/mtab". Linus ---- mount.c ---------------- #include #include #include #include #define TAB_FILE "/etc/mtab" #define LOCK_FILE "/etc/mtab~" int tab = -1; int lock = -1; volatile void die(void) { if (lock >= 0) unlink(LOCK_FILE); exit(1); } main(int argc, char ** argv) { int i; char buffer[1024]; if (argc !=3) { fprintf(stderr,"mount: usage: mount dev dir\n"); die(); } lock = open(LOCK_FILE,O_CREAT | O_EXCL,0644); if (lock < 0) { fprintf(stderr,"mount: unable to open lock-file\n"); die(); } chmod(LOCK_FILE,0644); tab = open(TAB_FILE,O_RDONLY); if (mount(argv[1],argv[2],0)) { fprintf(stderr,"mount: error %d\n",errno); die(); } if (tab >= 0) while ((i=read(tab,buffer,1024))>0) write(lock,buffer,i); i=strlen(argv[1]); argv[1][i]=' '; write(lock,argv[1],i+1); i=strlen(argv[2]); argv[2][i]='\n'; write(lock,argv[2],i+1); unlink(TAB_FILE); link(LOCK_FILE,TAB_FILE); unlink(LOCK_FILE); return 0; } ----- umount.c --------------- #include #include #include #include #define TAB_FILE "/etc/mtab" #define LOCK_FILE "/etc/mtab~" #define CHECK 0 #define WRITE 1 #define NOWRITE 2 int tab = -1; int lock = -1; static int read_char(void) { static char buffer[1024]; static int i=0; static int pos=0; if (tab < 0) return -1; if (pos == i) { i = read(tab,buffer,1024); pos = 0; } if (i <= 0) return -1; return (unsigned) buffer[pos++]; } static void write_char(int c) { static char buffer[1024]; static int i=0; if (c<0) { if (i) write(lock,buffer,i); i = 0; return; } buffer[i++] = c; if (i<1024) return; write(lock,buffer,i); i=0; } volatile void die(void) { if (lock >= 0) unlink(LOCK_FILE); exit(1); } main(int argc, char ** argv) { int c,i,len; int state; if (argc != 2) { fprintf(stderr,"umount: usage: umount dev\n"); die(); } lock = open(LOCK_FILE,O_CREAT | O_EXCL,0600); if (lock < 0) { fprintf(stderr,"umount: unable to open lock-file\n"); die(); } tab = open(TAB_FILE,O_RDONLY); if (umount(argv[1])) { fprintf(stderr,"umount: error %d\n",errno); die(); } len = strlen(argv[1]); state = CHECK; i = 0; do { c = read_char(); if (state==CHECK && !argv[1][i] && (c==' ' || c=='\n')) state=NOWRITE; if (c=='\n') { if (state != NOWRITE) write_char(c); state = CHECK; i = 0; continue; } if (state == NOWRITE) continue; if (state == WRITE) { write_char(c); continue; } if (c == argv[1][i]) i++; else { for (state=0 ; state= 0); write_char(-1); unlink(TAB_FILE); link(LOCK_FILE,TAB_FILE); unlink(LOCK_FILE); return 0; } --[0150]-- [0151] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/05/91 09:08 (57 lines) Subject: Re: cc1 fails silently From: "LCDR Michael E. Dobson" To: tytso@athena.mit.edu Date: Thu, 5 Dec 91 8:37:35 EST Cc: linux-activists@joker.cs.hut.fi (Linix Mailing LIst) In-Reply-To: <9112050213.AA05299@tsx-11.MIT.EDU>; from "Theodore Ts'o" at Dec 4, 91 9:13 pm I previously said: > > It appears you both were wrong and it is something more trouble, possibly > related to the race conditions Linus mentioned, but more likely some > subtle kernel bugs. > To which Ted responded: > Well, maybe. The swapper panic which happens after you type > ctrl-alt-del from DOS is standard in Linux 0.10 --- it's harmless, and > typing ctrl-alt-del after the panic will allow Linux to boot > successfully. > Depends what you mean by successfully. If I can't run gcc after ctrl-alt-del boot, I don't consider the boot successfull. Remember, I said the cc1 failure disappeared when I did a hard boot, I did nothing else to the system, did not reload the gcc binaries nor mkfs a new system. Now I suppose it is therefore the in core image of the file system that was corrupted and not the hard disk fs itself. I haven't attempted to build a linux kernel myself yet so I didn't apply the buffer.c patch, will wait for 0.11 which will be able to compile itself without using Minix or some other OS. Ted then pointed out: > Remember that "du" outputs sizes in 512 byte blocks, courtesy of POSIX. > My personal opinion is that it's one of the stupidest mistakes POSIX > has committed, since most users care about file sizes in kilobytes, not > in 512 byte blocks --- but then, I can alias du to "du -k", so the only > losers are the innocent, naive users. [End of soapbox] > Guess it's time to set up a "proper" .profile with a few aliases in it ;-) Anyone know why the default TERM is "dumb" instead of "console"? BTW, once gcc was working, I successfully built less using only #define TERMIO 1 #define REGCMP 0 #define RECOMP 0 in defines.h and removing the reference to libtermcap.a in the Makefile. I also was able to compile all the stdc routines from the pdksh src with the exception of setvbuf.c, stdio.c (probably not needed) and vprintf.c. I had to change the #include "stdh.h" to #include in strstr.c and one of the mem*.c routines. Anyone got a good exerciser for the mem* and str* routines? These could be very useful additions to the Linux libc.a NOTE, I used the *.h files that came with pdksh. -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0151]-- [0152] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/05/91 14:42 (34 lines) Subject: Re: cc1 fails silently Date: Thu, 5 Dec 91 14:17:06 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: "LCDR Michael E. Dobson" Cc: linux-activists@joker.cs.hut.fi Reply-To: tytso@athena.mit.edu From: "LCDR Michael E. Dobson" Date: Thu, 5 Dec 91 8:37:35 EST corrupted and not the hard disk fs itself. I haven't attempted to build a linux kernel myself yet so I didn't apply the buffer.c patch, will wait for 0.11 which will be able to compile itself without using Minix or some other OS. Do you know about about TSX-11.MIT.EDU, or some of the other anonymous FTP sites? There are precompiled boot images of Linux 0.10 which have the patched buffer.c. There's also a pre-compiled image of less there already. You might want to look around; there's binaries for kermit, Bison (yacc), flex (lex), RCS, etc. Might help you from reiventing the wheel. :-) I also was able to compile all the stdc routines from the pdksh src with the exception of setvbuf.c, stdio.c (probably not needed) and vprintf.c. I had to change the #include "stdh.h" to #include in strstr.c and one of the mem*.c routines. Anyone got a good exerciser for the mem* and str* routines? These could be very useful additions to the Linux libc.a NOTE, I used the *.h files that came with pdksh. I believe the Linux libc.a already contains the mem* and str* routines, using the GNU libc routines. At least, the libc.a included in gccbin.tar.Z already has those routines. - Ted --[0152]-- [0153] daemon@ATHENA.MIT.EDU (chrisa@extro.ucc.su.OZ.AU) Linux_Activists 12/05/91 19:24 (25 lines) Subject: FAQ, port lists & shoelace Date: Fri, 6 Dec 1991 00:11:49 GMT To: linux-activists@joker.cs.hut.fi From: chrisa@extro.ucc.su.OZ.AU Hello * A few questions 1) Has anything been done for a FAQ list as yet? 2) It seems that there may be a little reinventing of the wheel going on in terms of porting stuff to linux. Maybe it would be a good idea to compile a list of what has been ported so far, by whom, and where it is (or patches to the original code) is available from. I guess if noone else is willing, I could do this. 3) I have read about shoelace in the minix newsgroup before, but i only have macminix. Do you need to compile shoelace under minix to get it working or can it be compiled under linux? enuff for now... chris. --[0153]-- [0154] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/05/91 23:26 (26 lines) Subject: Re: FAQ, port lists & shoelace Date: Thu, 5 Dec 91 22:49:20 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: chrisa@extro.ucc.su.OZ.AU Cc: linux-activists@joker.cs.hut.fi In-Reply-To: chrisa@extro.ucc.su.OZ.AU's message of Fri, 6 Dec 1991 00:11:49 GMT, Reply-To: tytso@athena.mit.edu >2) It seems that there may be a little reinventing of the wheel going on > in terms of porting stuff to linux. Maybe it would be a good idea to > compile a list of what has been ported so far, by whom, and where it is > (or patches to the original code) is available from. I guess if noone > else is willing, I could do this. blum@messua.informatik.rwth-aachen.de keeps such a list. Send mail to him for more info. Stuff regarding Linux can be found at these anonymous FTP sites: nic.funet.fi, tsx-11.mit.edu, and tupac-amaru.informatik.rwth-aachen.de. New files that hit one site generally hit all three (at least, I try to send binaries that get sent to tsx-11 to the other two sites, and I try to grab anything new that gets downloaded to nic.funet.fi and tupac-amaru). So you should also try looking at one of the anonymous FTP sites to see if you can just pick up the binaries. - Ted --[0154]-- [0155] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/06/91 04:01 (46 lines) Subject: The FAQ and other questions Date: Fri, 6 Dec 91 09:52:11 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! Following are some answers to some questions recently mailed: 1) Has anything been done for a FAQ list as yet? I am currently developing such a beast, and a LINUX Info sheet is already done (mostly). If you are interested in helping with the FAQ, mail me and you are on the list.... 2) It seems that there may be a little reinventing of the wheel going on in terms of porting stuff to linux. Maybe it would be a good idea to compile a list of what has been ported so far, by whom, and where it is (or patches to the original code) is available from. I guess if noone else is willing, I could do this. This list is available as TODO on tupac-amaru.informatik.rwth-aachen.de:/pub/msdos/replace as are all the binaries 3) I have read about shoelace in the minix newsgroup before, but i only have macminix. Do you need to compile shoelace under minix to get it working or can it be compiled under linux? I remember some patches for shoelace under linux sent out on this list, but I didn`t get them This leads me to an announcement: I think next year I will start another service for LINUX. I will save all the postings on the mailing list an make it available via anon ftp, perhaps even via a mailserver with the ability to grep for keywords.... If you like this idea, have other ideas, or have set up such a service yourself, please mail me See you, Robert "I'll do it ASAP" Blum --[0155]-- [0156] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/06/91 04:41 (67 lines) Subject: The new TODO file Date: Fri, 6 Dec 91 10:29:34 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! This is this weeks mailing of TODO :-) If you have any additions, send mail (please!) Robert Blum This files contains the status of several tools for Linux Currently ported/developed/compiled projects: Name: ported by: bison nicholas@cs.uwa.oz.au (binary only) diff tytso@mit.edu (binary only) flex tytso@mit.edu (binary only) fsck torvalds@kruuna.helsinki.fi (source only) gcc torvalds@kruuna.helsinki.fi (src &binary) german kbd upsyf173@comparex.hrz.uni-bielefeld.de (source only) id ???? (binary only) kermit tytso@mit.edu (binary only) less jtkohl@berkeley.cs.edu (binary only) mkfs torvalds@kruuna.helsinki.fi (source only) mount torvalds@kruuna.helsinki.fi (source only) pmake jtkohl@berkeley.cs.edu (binary only) rcs ???? (binary only) umount torvalds@kruuna.helsinki.fi (source only) whoami ???? (binary only) All these programs can be FTPed as binaries/sources from the following sites nic.funet.fi tsx-11.mit.edu tupac-amaru.informatik.rwth-aachen.de Try your nearest site first! If you can't find them there, you'll find them on tupac-amaru in every case. =============================================================================== Projects currently under development: Name: ported by: Remarks c386 blum@messua.informatik.rwth-aachen.de Is working under Linux A cc for this exists Is currently teached ANSI. Any help on this would be appreciated. gawk nicholas@cs.uwa.oz.au Still needs a working mathlib. networking jtkohl@echidna.berkeley.edu Mainly the BSD code Perhaps even ffs Networking= BSD networking Tape VOL2 mathlib nicholas@cs.uwa.oz.au Will be a library for 387/287/soft-float-code VFS proven@athena.mit.edu VFS=Virtual File System Will probably out with Linux 0.11 --[0156]-- [0157] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/06/91 10:42 (28 lines) Subject: Possible bug in termios.h? From: "LCDR Michael E. Dobson" To: linux-activists@joker.cs.hut.fi (Linix Mailing LIst) Date: Fri, 6 Dec 91 10:15:10 EST While working on a port of UUCP, I came across what may be a bug in the file. The values PARENB and PARODD where coming up undefined even though termios.h had been included. Checking the source against POSIX 1003.1-1988 we find: Linux 1003.1 c_cflag field c_cflag field CPARENB PARENB CPARODD PARODD It seems that we should be using the mask name symbols PARENB and PARODD to be compliant with section 7.1.2.4 of 1003.1 Any comments from the group? PS: before flamming me for working on UUCP, I know we don't have login/getty/uugetty nor do we have getlogin()/cuserid(), ttyname(), cget*(), or cfset*(). Stay tuned! -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0157]-- [0158] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 12/06/91 12:18 (70 lines) Subject: uemacs 3.11 Date: Fri, 6 Dec 91 17:55:42 +0100 From: corsini@numero6.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi Hi, I've compiled, nearly successfuly, micro emacs 3.11 under linux. To do so, 1) get the sources from midas.mgmt.perdue.edu 2) apply the patches available from comp.emacs, for unix boxes (if needed i can send it to this mailing list) 3) make the following changes: -a- in eproto.h line 24: change mlwrite(va_decl) to mlwrite(va_alist) this makes the error to be only a warning -b- in unix.c to fit the def of rename() in /usr/include/stdio.h change lines 1241 and 1242 char * file1; char * file2; by const char * file1; const char * file2; Moreover since linux has no ltermcap.a change also #if HPUX || VAT char PC, *UP; short ospeed; #else by #if HPUX || VAT || USG char PC, *UP; short ospeed; #else -c- finally set the following flags to 1 in estruct.h USG GCC TERMCAP supress the -ltermcap option when linking bin/emacs.exe that's all. Hope this helps [mmc] PS1: the nearly success is caused by when exiting emacs 3.11, the screen is not cleaned (apply cls by hand is what i do). I still dig on it. PS2: if u are interested, i can post the previous changes in cdif form. PS3: on MSX-11 there are a lot of patches, some were even not posted on this list. My questions and "requierement" are Are these patches also available on other sites (the european one)?, i can't verify myself 'cause my site can't access them ('cause of money) Would it be possible to make a README file for these patches where there would be: the order of apliance, the things they cure --[0158]-- [0159] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 12/07/91 10:49 (12 lines) Subject: micro emacs Date: Sat, 7 Dec 91 16:40:22 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi Hi there, it seems that the ^X^C is interpreted only as ^C which kill the emacs process in fact ^X C do the thing that ^X^C is supposed to do. The called function are correct, and there is no problem with the virtual screen functions. [mmc] PS as i mail with a blind terminal, the ^key must be read sa --[0159]-- [0160] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 12/08/91 10:40 (13 lines) Subject: micro emacs again Date: Sun, 8 Dec 91 16:31:14 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi Once again, ^X C is not a good solution, because it calls a sub-shell. X exit-emacs is correct, in fact it is the function bind to ^X^C, but the ^C is still catch by the system, and cause an interruption. [mmc] --[0160]-- [0161] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/08/91 10:59 (33 lines) Subject: linux-0.11 available Date: Sun, 8 Dec 1991 17:51:24 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi The subject says it all: I have uploaded linux version 0.11 to nic.funet.fi and tupac-amaru. They won't show up for a while on nic, but are already visible in pub/msdos/replace/incoming at amaru. rtx-11 is so slow to use from here that I didn't upload them there: I guess they'll show up within a couple of days (tytso?). The files uploaded were: bootimage.Z - US keyboard compressed bootimage rootimage.Z - 1200kB compressed root image linux-0.11.tar.Z - sources as86.tar.Z - linux binaries for bruce evans' 16-bit assembler and loader. INSTALL-0.11 - updated install-info This version has a lot of corrections, and is stable at least on my machine. I /hope/ every known bug is fixed, but no promises (and all unknown bugs are still there, probably with reinforcements ;-). Those who like to use caps lock as a ctrl-key, you'll have to re-patch the kernel. It's not implemented in the standard version. Linus PS. I'll be a bit busy with the #"$/% physics-course I'm taking, so I might not be as active on the net this coming week as I would like to. PPS. corsini: the problem you have with the recompiled uemacs sounds like it isn't resetting the ISIG bit in c_lflags when moving to raw mode. Search for c_lflags in the source: it should effectively be set to zero (I think) - no signals, no canonical mode etc. --[0161]-- [0162] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/08/91 11:42 (21 lines) Subject: ISIG bug already :-( Date: Sun, 8 Dec 1991 18:34:04 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi It seems God hates me or something: 5 minutes after sending out linux-0.11 I found a bug. This one also explains why corsini has had problems with uemacs: I had the meaning of ISIG reversed in the kernel. Happily the bug is not very important, and correcting it breaks /my/ version of uemacs, but I'm a bit shamefaced. The bug is in linux/kernel/char_drv/tty_io.c: search for the line containing "if (!L_ISIG" and remove the incorrect "!". I'll make a new kernel binary available, as well as a new uemacs. Hopefully nobody ever even gets to see the bad versions. I guess we'll have to rename the system: wirzeniu already suggested the name "buggyx" :-) Linus PS. Apologies to corsini for thinking he did something wrong. --[0162]-- [0163] daemon@ATHENA.MIT.EDU (Marc Peters) Linux_Activists 12/08/91 18:16 (20 lines) Subject: v 0.11 boot disk problem Date: Sun, 8 Dec 91 15:01:30 -0800 From: mpeters@polyslo.csc.calpoly.edu (Marc Peters) To: Linux-activists@joker.cs.hut.fi I just downloaded the new improved v0.11, but it doesn't want to load on my computer. It gives a couple errors similar to HD controller reset failed: 000 Kernel Panic: HD controller not ready and aborts the loading of the system. My computer has an MFM HD and controller which may account for the problem, but v0.10 didn't seem to mind. A friend has a machine with an IDE drive and controller, it gives the first error but loads the system and seems to work fine. If you could direct me toward a cure I'd be happy again, even if the cure involves replacing my HD and controller. But I'm wondering what differences could be in the new kernel that would obsolete my HD and if those changes can't be re-changed. Thank you for your time, Marc Peters --[0163]-- [0164] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/08/91 18:28 (16 lines) Subject: RE: v 0.11 boot disk problem Date: Mon, 9 Dec 1991 01:18:21 +0200 From: Ari Lemmke To: Linux-activists@joker.cs.hut.fi In-Reply-To: Marc Peters's message of Sun, 8 Dec 91 15:01:30 -0800 <9112082301.AA00933@polyslo.csc.calpoly.edu> Linus downloaded new stuff .. so: Linux 0.11 should now be available at nic.funet.fi ... everything needed is in INSTALL directory (actually stuff in INSTALL directory is hard linked from other directories). The main README file changes constantly ... arl --[0164]-- [0165] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/08/91 20:12 (51 lines) Subject: hd_reset fails in 0.11 Date: Mon, 9 Dec 1991 02:57:40 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi Marc Peters: "v 0.11 boot disk problem" (Dec 8, 15:01): > I just downloaded the new improved v0.11, but it doesn't want to load on my > computer. It gives a couple errors similar to > HD controller reset failed: 000 > Kernel Panic: HD controller not ready > and aborts the loading of the system. My computer has an MFM HD and > controller which may account for the problem, but v0.10 didn't seem to mind. > A friend has a machine with an IDE drive and controller, it gives the > first error but loads the system and seems to work fine. Thanks, this is why there are still debug-statements in the code. There are in fact two solutions (I hope) to the problem. Both of them require you to change the file "linux/kernel/blk_drv/hd.c" which does the harddisk specific stuff. As 0.10 doesn't try to reset the controller at bootup, it seems to work, and you can still use it to recompile 0.11. 1 - set static int reset to 0 at startup (currently 1). This means linux won't try to reset the controller in the beginning, but this is just a temporary hack: if there are errors later on that need a reset, you'll be in the same trouble. 2 - try to edit the timeouts in "reset_controller". If memory serves, it's a line that goes like this: outb_p(4,HD_CMD); >> for (i=0 ; i<100 ; i++) nop(); outb_p(xxx,HD_CMD); Change the max value to 10000 or something, and try again. I have only one controller to test, and timing-problems are always the worst kind. There are a couple of other timing-values that are completely arbitrary (guess a number between 1 and 100000, and if it works, it works :-), but this is the first suspect. I'd be very grateful if everybody who encounters this problem would try out (2), and report to me how big the value had to be before the reset made it (or indeed if it works even then). Don't do (1) unless nothing else works. I'd also be interested to know what kind of machine you are running (fast machine, slow disk?). Linus PS. I hope even old linux-users read the INSTALL-file: there is a change in how linux boots up. No more /bin/update, instead linux executes the shell script /etc/rc, which may mount/fsck etc, and start up update in the background. --[0165]-- [0166] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/08/91 21:02 (38 lines) Subject: hd_reset fails in 0.11 Date: Mon, 9 Dec 1991 03:51:38 +0200 From: Ari Lemmke To: Linux-activists@joker.cs.hut.fi In-Reply-To: Linus Benedict Torvalds's message of Mon, 9 Dec 1991 02:57:40 +0200 <199112090057.AA06512@kruuna.helsinki.fi> >2 - try to edit the timeouts in "reset_controller". If memory serves, >it's a line that goes like this: > outb_p(4,HD_CMD); > >> for (i=0 ; i<100 ; i++) > nop(); > outb_p(xxx,HD_CMD); >Change the max value to 10000 or something, and try again. I have only >one controller to test, and timing-problems are always the worst kind. >There are a couple of other timing-values that are completely arbitrary >(guess a number between 1 and 100000, and if it works, it works :-), but >this is the first suspect. I hacked one SCSI driver for Mach pc532 ... and there was a lot of static wait loops (aaaaaargh) .. what we did was changed wait loops as: Wait_uSec( 100 ); and Wait_uSec function has loop .. where is (should be) computed one uSec loop. But we have all only 25MHz 32532 chips .. so it was hard coded (ugh). There are many PC 386s around .. like mine .. I'm running my 386/25 with 16 MHz CPU, and don't have guts to run it full speed (gets really hot, and don't have peltier element or any other way to cool my machine just now ;-), so I'm running it about 6 MHz speed (my board has dip for it). arl --[0166]-- [0167] daemon@ATHENA.MIT.EDU (Michael Kronvold) Linux_Activists 12/08/91 22:13 (16 lines) Subject: Linux and SCSI (was: hd_reset fails in 0.11) Date: Sun, 8 Dec 91 21:01:14 GMT-0600 From: kronvold@sumter.cso.uiuc.edu (Michael Kronvold) To: Linux-activists@joker.cs.hut.fi In-Reply-To: Ari Lemmke's message of Mon, 9 Dec 1991 03:51:38 +0200 <199112090151.AA26582@zen.cs.hut.fi> > I hacked one SCSI driver for Mach pc532 ... and there > was a lot of static wait loops (aaaaaargh) .. what we did was > changed wait loops as: > Wait_uSec( 100 ); > and Wait_uSec function has loop .. where is (should be) > computed one uSec loop. I'm trying (and failing miserably) to get Linux up on my 386-40 with a SCSI drive... Anything you have that I could use as a referance? - Mike --[0167]-- [0168] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/09/91 03:49 (125 lines) Subject: The Linux info sheet Date: Mon, 9 Dec 91 09:06:54 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! Following is the first official version of a Linux info sheet. If you like it, I'd suggest posting this thing to: comp.os.misc comp.os.mach comp.os.minix comp.os.coherent comp.os.sysv.i386 comp.unix.programmers comp.binaries.ibm.pc.d Comments and suggestions are welcome. Ciao, Robert LINUX INFORMATION SHEET 1. WHAT IS LINUX 0.11 LINUX 0.11 is a freely distributable UNIX clone. It is almost fully System V compatible. LINUX has been written from scratch, and therefore does not contain any AT&T or MINIX code--not in the kernel, the compiler, the utilities, or the libraries. For this reason it can be made available with the complete source code via anonymous FTP. Sorrily, it runs only on 386/486 AT-bus-machines. EISA will probably do too, but you need an AT-Bus controller for your harddisk. Version 0.11 is still a beta release, but it provides almost full functionality. Various users have been able to compile bigger projects like bison/flex by only changing the makefile to their needs, and these tools are fully functional. 2. LINUX features - System call compatible with V7 of the UNIX operating system - Full multiprogramming (multiple programs can run at once) - Memory paging with copy-on-write - Demand loading of executables - Page sharing of executables - ANSI compliant C compiler (gcc) - A complete set of compiler writing tools (bison as yacc-replacement, flex as lex replacement) - The gnu-born again shell (bash) - Micro emacs - most utilities you need for development (cat, cp, kermit, ls, make, etc.) - Over 200 library procedures (atoi, fork, malloc, read, stdio, etc.) - Currently 3 national keyboards: finnish/us/german - Full source code (in C) for the OS is freely distributable - Full source code of the tools can be gotten from many anonymous ftp sites (It's almost completel the GNU project) - Runs in protected mode on 386 and above - Support for extended memory up to 16M on 386 and above - RS-232 serial line support with terminal emulation, kermit, zmodem, etc. - Supports the real time clock 3. HARDWARE REQUIRED - A 386 or 486 machine that is an AT-bus-machine. EISA will probably do too. - An IDE hard disk is required to use this system. - Both 5.25" and 3.5" diskettes are supported - At least 2 megabytes of RAM is required for LINUX to be operational, but gcc will only work from 4 MB on. - Any video card will do - Up to two serial lines are supported - The real time clock is supported 4. PARTIAL LIST OF UTILITIES INCLUDED IN OR AVAILABLE FOR LINUX 0.10 - The MTOOLS package (reading/writing to DOS) - The complete GNU filetools (ls,cat,cp,mv,...) - The GNU C compiler with GNU assembler,linker,ar,... - bison - flex - rcs - pmake (BSD 4.2 make) - kermit - Micro emacs - less - mkfs - fsck - mount/umount 5. LINUX BINARIES The LINUX binaries (including all the tools) are available at three anonymous FTP sites. These are: nic.funet.fi:/pub/OS/Linux tsx-11.mit.edu tupac-amaru.informatik.rwth-aachen.de:/pub/msdos/replace 6. LEGAL STATUS OF LINUX Although LINUX is supplied with the complete source code, it is copyrighted software. But it is, opposite to MINIX available for free, provided you obey to the rules specified in the LINUX copyright. 7. NEWS ABOUT LINUX Since LINUX's introduction to the public there has been a rapidly growing mailing list, "linux-activists@joker.cs.hut.fi". To subscribe to this list, mail to "linux-activists-requests@joker.cs.hut.fi". If the traffic in this lists increases further, there are plans to swap (at least partially) over to comp.os.misc, so watch out for any LINUX articles in this group. If you simply want to know whats the current state of the art, do a "finger torvalds@kruuna.helsinki.fi", and you'll get some information. 8. FUTURE PLANS The major current project is bringing LINUX to a version number greater than 1.0. It has also to undergo some (minor) revisions to be compatible to the IEEE POSIX P1003.1 and P1003.2 standards. Various people are currently working on - math support/fp emulation in the kernel - Page swapping (since paging is alreay implemented) - A virtual filesystem layer - STREAMS If you want to join the developers, join the mailing list --[0168]-- [0169] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/09/91 23:07 (8 lines) Subject: linux-.11 cures unexpected interupt problem Date: Mon, 9 Dec 91 19:56:31 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Just a word of praise for linux-0.11. I still get unexpected HD interrupt messages, but I could compile the system, and comment out that message. Which means linux can live with my brain-dead IDE drive, something minix couldn't do without my modifying the harddisk driver. --[0169]-- [0170] daemon@ATHENA.MIT.EDU (Drew Eckhardt) Linux_Activists 12/10/91 00:23 (56 lines) Subject: Re: Linux and SCSI (was: hd_reset fails in 0.11) Date: Mon, 9 Dec 1991 22:15:17 -0700 From: Drew Eckhardt To: Linux-activists@joker.cs.hut.fi, kronvold@sumter.cso.uiuc.edu > was a lot of static wait loops (aaaaaargh) .. what we did was > changed wait loops as: > Wait_uSec( 100 ); Accomodating the BUS settle time is a real pain. In my linux driver I am using small chunks of inline assembler to accomodate it and the glitch detection discussed in the standard. > and Wait_uSec function has loop .. where is (should be) > computed one uSec loop. I'm trying (and failing miserably) to get Linux up on my 386-40 with a SCSI drive... Anything you have that I could use as a referance? Before any one else starts on this, I'm currently working on a Linux SCSI driver (~60 - 70% complete). A brief description of the project : It's a multi-tiered design, with SCSI disk / tape Linux block device drivers, a high-level host independant module that has a generic interface to the low level module and host independant initialization routines, and a low level, host specific implementation. The interface between the low & high level part is through an array of host structures, where each host structure has a pointer to a detect function, an information function, and the actual SCSI command function. Use of multiple host adapters is supported. Code in the high-level SCSI initialization routine scans each present SCSI host for devices - target ID 0-6, LUN 0-7 if LUN 0 is found. Capacity of each device is determined, and a structure in either the ST tape driver or SD disk driver. This, in conjunction with the detect function supplied for each host, allows the drivers to be 100% self configuring. The SCSI disk and TAPE drivers simply pass SCSI commands through the high level interface to their appropriate devices. The disk device also automatically remaps bad sectors. It will initially be bundled with a low-level driver for the Seagate ST-01/ST-02 SCSI hosts - what I have. They're 8 bit, can't run 1:1 on SCSI disks, but they're dirt cheap... If any one has other hosts, and wants to volunteer to write a matching low level driver, I can supply the interface specifications for your driver now, and working disk block device driver within a couple days when I'm satisfied with it. --[0170]-- [0171] daemon@ATHENA.MIT.EDU (Michael Kronvold) Linux_Activists 12/10/91 02:30 (12 lines) Subject: Linux and SCSI (was: hd_reset fails in 0.11) Date: Tue, 10 Dec 91 01:16:26 GMT-0600 From: kronvold@sumter.cso.uiuc.edu (Michael Kronvold) To: drew@hazelrah.cs.colorado.edu Cc: Linux-activists@joker.cs.hut.fi In-Reply-To: Drew Eckhardt's message of Mon, 9 Dec 1991 22:15:17 -0700 <199112100515.AA13922@hazelrah.cs.Colorado.EDU> Well, I'm using a DTC controller, and I seriously doubt my ability to write the low level for it... BUT, I'm willing to try just in case someone else out there might have a similar controller. :) - Mike --[0171]-- [0172] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/10/91 02:55 (41 lines) Subject: Signal handler compatibility? Date: Tue, 10 Dec 91 02:47:13 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: Linux-activists@joker.cs.hut.fi Reply-To: tytso@athena.mit.edu Well, it looks like I have job control pretty much functioning with a version of bash that understands job control, and it pretty much works. One or two more days while I do more testing and packaging of diffs, and I'll be sending the kernel changes to Linus, and making them available on TSX-11 so that more adventurous souls who job control sooner rather than later can grab it and try it out. One of the problems which I've run into during my testing is that when a read gets interrupted with a ^Z, when you restart it, the system call that was in progress returns a -EINTR, and the program is supposed to understand the EINTR and restart the system call. Well, the problem is thatmost programs *don't* bother to understand EINTR, and so it is highly desirable to have restartable system calls ala BSD 4.3. Unfortunately, in order to do that, it will be necessary to change the signal trampoline code so the signal handler exits, a sigreturn system call is executed. This in fact will result in cleaner and clearer code in the kernel, but since the signal trampoline code is part of libc.a, it would mean that code which used signal handlers would need to be recompiled. In other words, a kernel which used the new way of doing signal handling would not be binary compatible with binaries that used signal handlers. Now, I can think of ways that would probably work in making the resulting kernel be backwards compatible, but they all involve really gross hacks that would be really painful, and I'm not sure that it would be good thing to be introducing ugly hacks to maintain backwards compatibility when Linux is still in beta test. How do people feel about this one? How much code which has been ported actually use signal handlers? Would people be willing to recompile them with a new libc.a? Linus, would you be willing to take a change in the signal handling code that might not be backwards compatible? - Ted --[0172]-- [0173] daemon@ATHENA.MIT.EDU (Patrick L. McGillan) Linux_Activists 12/10/91 09:19 (26 lines) Subject: hd controller problem From: Patrick L. McGillan To: linux-activists@joker.cs.hut.fi (Linux User Group) Date: Tue, 10 Dec 91 8:03:28 CST Hi all, Like others I had a problem when starting up Linux 0.11. The changes suggested sort of worked, i.e. not doing a reset on boot did, but making a bigger loop in reset_controller didn't. The method I used was to increase the loop in drive_busy from 10000 to 100000. The loop in reset_ controller is back to 100. No problems. Linus you asked about machines people are using that have the problem. My motherboard is a 33mhz-64k cache board. The controller is a HD/FD, with the HD portion locked to 1:1 interleave. As you may remember from earlier discussion the FD portion wouldn't work under Linux so I disabled it and put a floppy only controller card in. The Hard disk seems to be sluggish and usually responds slow, so I imagine that is where the problem is coming from. Later, -- Patrick L. McGillan Computer Systems Specialist University Of Wisconsin Ph: (715) 394-8191 Superior, Wisconsin pmcgilla@uwsuper.edu --[0173]-- [0174] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/10/91 11:17 (26 lines) Subject: Seg Faults under 0.11 From: "LCDR Michael E. Dobson" To: linux-activists@joker.cs.hut.fi (Linux Mailing List) Date: Tue, 10 Dec 91 10:44:17 EST I seem to be having some trouble with Out of memory errors under 0.11 that I didn't have under 0.10. Uncompress is failing with an: Out of memory. Segmentation Fault error on even small files. At bootup I show 3647 free blocks on the root hd device and 3145728 free bytes of mem. The cu from Will Rose's UUCP 1.2 package also fails with the above error even though I now have it compiling and linking with only some incompatible pointer type warnings, some unused variable warnings, and some implicit function declaration warnings. Can anyone shed some light as to what could be causing the above errors? -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0174]-- [0175] daemon@ATHENA.MIT.EDU (d7stfax@dtek.chalmers.se) Linux_Activists 12/10/91 12:56 (29 lines) Subject: IDE partitions larger than 65536? From: d7stfax@dtek.chalmers.se To: linux-activists@joker.cs.hut.fi (The Linux mailing list) Date: Tue, 10 Dec 91 18:45:55 MET I've finally come around to get Linux home (I've had other things to do, and thought I'd wait till the 0.11 release anyway.), and everything worked like a charm, until I tried the 'mkfs' it wouldn't run, but stopped with a USAGE:! To make a long story short, I've now found out that it was due to me wanting to use my entire 105 Meg hard disk as one partition, mkfs won't allocate more than 65536 blocks. My question is now simply, should I repartition my hard disk to two partitions, or can I easily change the 16 bit block number limit (e.g. DEFINE, and recompile)? I strongly suspect the former, but since I haven't begun to read the sources yet I'm not 100% sure. If it's repartition time could some kind soul point me to a good (DOS?) program that does that? DOS fdisk doesn't seem up to it, especially since the disk had only one 105 Meg Interactive Unix partition on it. My setup is: 386-25, IDE Plus co. 105 Meg hard disk, 10 Meg memory, VGA controler. I'm no MSDOS junkie, but I asked the ones here, and the above is as far as I got. Regards, -- Stefan Axelsson, Chalmers University of Technology, d7stfax@dtek.chalmers.se Sweden --[0175]-- [0176] daemon@ATHENA.MIT.EDU (Michael K. Johnson) Linux_Activists 12/10/91 13:28 (17 lines) Subject: DTC SCSI controllers Date: Tue, 10 Dec 91 12:17:07 CST From: johnsonm@stolaf.edu (Michael K. Johnson) To: Linux-activists@joker.cs.hut.fi I have a DTC SCSI controller, and would be willing to (as I become a bit more proficient) write the low-level driver for it. However, there is a catch -- I will almost assuredly, due to my schedule, not be able to start till february or so. Sooooo, if anyone else wants to pick this up, feel free:-) If anyone needs to talk to them, I have voice and BBS numbers for their tech support. michaelkjohnson johnsonm@stolaf.edu I do not do .sig's --[0176]-- [0177] daemon@ATHENA.MIT.EDU (Patrick L. McGillan) Linux_Activists 12/10/91 15:50 (14 lines) Subject: printing From: Patrick L. McGillan To: linux-activists@joker.cs.hut.fi (Linux User Group) Date: Tue, 10 Dec 91 14:36:28 CST Hi, Am I missing something or does linux have no way of printing something out. I.E. how do others obtain print outs of their work. -- Patrick L. McGillan Computer Systems Specialist University Of Wisconsin Ph: (715) 394-8191 Superior, Wisconsin pmcgilla@uwsuper.edu --[0177]-- [0178] daemon@ATHENA.MIT.EDU (David Darknell) Linux_Activists 12/10/91 16:19 (11 lines) Subject: Re: Linux and SCSI (was: hd_reset fails in 0.11) Date: Tue, 10 Dec 91 13:04:50 PST From: David Darknell To: Linux-activists@joker.cs.hut.fi, drew@hazelrah.cs.colorado.edu, YES! I am trying to write a driver for a FastCache High performance SCSI controller (I used to have a ST-01/02) but I am in a catch 22: I cannot run Linux on the drive without a driver, but cannot write the driver without Linux. So here is my plan: Install MFM controller and 40Meg drive long enough to write the SCSI driver, then dump it. I would be happy to get anything you have that might make my job easier! --[0178]-- [0179] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/10/91 16:31 (39 lines) Subject: More Seg Fault troubles From: "LCDR Michael E. Dobson" To: torvalds@kruuna.helsinki.fi (Linus Torvalds) Date: Tue, 10 Dec 91 16:05:11 EST Cc: linux-activists@joker.cs.hut.fi (Linux Mailing List) Linus, I've found another set of conditions where I can reproducibly generate the out of memory Segmentation fault messages using a simple command. Environment: drwxr-xr-x root sys /usr/spool drwxr-xr-x uucp uucp /usr/spool/uucp ls -l /usr/spool from anywhere but within /usr/spool generates : /usr/spool total 1 out of memory Segmentation fault a plain ls /usr/spool generates: uucp with no errors looks possibly like a EPERM problem during the stat of the directory. -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0179]-- [0180] daemon@ATHENA.MIT.EDU (Marc Peters) Linux_Activists 12/10/91 16:33 (35 lines) Subject: Serial Communications... Date: Tue, 10 Dec 91 13:22:00 -0800 From: mpeters@polyslo.csc.calpoly.edu (Marc Peters) To: linux-activists@joker.cs.hut.fi I may have missed this discussion, but is anyone else having a problem with modem communications? It seems that the serial communication is sending 16 bit words rather than 8 bit characters (ie. it sends two characters at a time). This works great if the command you send is of odd character length so when you hit a carriage return it makes it even, but when you have an even length command, you must hit return followed by say a to have the return sent. This happens in both V 0.10 and V 0.11 in both Kermit and Term. Note: It happens when sending the "at" string to the modem as well as when the modem is connected. Also, I was able to fix the HD not ready error by changing the length of the null loop in the hd_ready function (in hd.c) to 30,000. Changing the length of the controller reset function didn't accomplish anything more than delaying the time it took before it printed the error. I still get the controller reset error but it isn't fatal so things keep moving. I have a 386DX-33 with a MFM hard drive. The drive is pretty old so it is a little slow (which may be the problem). I did try V 0.11 on a 386DX-25 that has a faster IDE controller drive in it and it doesn't get the fatal error with the drive ready loop set to 10,000. It still get the controller reset error though. The last question I have is how do I change the source code to compile the kernel to boot from Major 0 minor 0 rather than Major 3 minor 6? I tried changing the defaults in build.c and changed bootsect.s to have 000 instead for the root device (should give the floppy). However, when I compile the kernel, the build program consistently uses (3, 6). What am I missing? Marc Peters mpeters@polyslo.calpoly.edu --[0180]-- [0181] daemon@ATHENA.MIT.EDU (LCDR Michael E. Dobson) Linux_Activists 12/11/91 12:36 (42 lines) Subject: Re: More Seg Fault troubles From: "LCDR Michael E. Dobson" To: torvalds@cc.helsinki.fi (Linus Benedict Torvalds) Date: Wed, 11 Dec 91 12:02:13 EST Cc: linux-activists@joker.cs.hut.fi (Linux Mailing List) In-Reply-To: <199112102246.AA07956@kruuna.helsinki.fi>; from "Linus Benedict Torvalds" at Dec 11, 91 12:46 am Linus, I've done some more investigating and can give you detailed info that should reproduce the bug on your system. Entry from /etc/passwd that causes problem uucp::5:5:/usr/lib/uucp **NOTE NO ":" on end of entry*** ls -l /usr/spool drwxr-xr-x uucp uucp 48 11 DEc 10:53 uucp /usr/spool total 1 out of memory Segmentation fault ls -lR /usr/spool is ok! cd /usr/spool ls -l is ok! Now for the interesting part: adding ":" to end of uucp entry in /etc/passwd cures problem!! So, you know the code involved, bug or "feature"? -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com --[0181]-- [0182] daemon@ATHENA.MIT.EDU (drew@anchor.cs.colorado.edu) Linux_Activists 12/11/91 18:57 (359 lines) Subject: Re: Linux and SCSI To: Linux-activists@joker.cs.hut.fi, Cc: drew@anchor.cs.colorado.edu Date: Wed, 11 Dec 91 16:41:04 MST From: drew@anchor.cs.colorado.edu -------- > > Date: Tue, 10 Dec 91 12:13:59 CST > To: drew@hazelrah.cs.Colorado.EDU > From: johnsonm@stolaf.edu (Michael K. Johnson) > Subject: Re: Linux and SCSI (was: hd_reset fails in 0.11) > > > Return-Path: johnsonm@stolaf.edu > Status: RO > > -------------------------------------------------------------------- > I am just learning unix systems programming with linux, but I have > a SCSI hard drive and a DTC adapter, and would be very willing to > write the device dependent stuff for it when I get to that ability > level if no one else has done it be then. I will be taking an OS > class next semester (starting february) so I could even use this > as a project. So although I can't do this right now, I would like > it if you could put me on your list to get the information, which > I can save and then hopefully work on when I am able. > > Thanks a lot! > > michaelkjohnson > > Date: Tue, 10 Dec 91 12:17:07 CST > To: Linux-activists@joker.cs.hut.fi > From: johnsonm@stolaf.edu (Michael K. Johnson) > Subject: DTC SCSI controllers > > > Return-Path: johnsonm@stolaf.edu > Status: RO > > -------------------------------------------------------------------- > > I have a DTC SCSI controller, and would be willing to (as I become a bit > more proficient) write the low-level driver for it. However, there is > a catch -- I will almost assuredly, due to my schedule, not be able to > start till february or so. Sooooo, if anyone else wants to pick this > up, feel free:-) > > If anyone needs to talk to them, I have voice and BBS numbers for their > tech support. > > michaelkjohnson > johnsonm@stolaf.edu > I do not do .sig's > > > > > Date: Tue, 10 Dec 91 13:04:50 PST > To: Linux-activists@joker.cs.hut.fi, drew@hazelrah.cs.Colorado.EDU, > kronvold@sumter.cso.uiuc.edu > From: David Darknell > Subject: Re: Linux and SCSI (was: hd_reset fails in 0.11) > > > Return-Path: david@maxwell.UCSC.EDU > Status: RO > > -------------------------------------------------------------------- > YES! I am trying to write a driver for a FastCache High performance > SCSI controller (I used to have a ST-01/02) but I am in a catch 22: > I cannot run Linux on the drive without a driver, but cannot write the > driver without Linux. So here is my plan: Install MFM controller and > 40Meg drive long enough to write the SCSI driver, then dump it. I > would > be happy to get anything you have that might make my job easier! -------- You don't have to compile Linux under Linux. Another possibility is cross compiling. If you have access to another little endian machine , LSB first, cross compiling is as easy as doing a make gcc with target machine set to some tm-i386 file. Depending on how the host system is set up, you may be able to use the native ld / ar - and even if not, it is no problem to compile the gnu binutils and have gcc/gas use them. Anyways, here's my hosts.h file, the generic interface to the lowlevel host specific drivers. There isn't much too it - the point here was to keep things SIMPLE, flexible, and 100% self configuring so we aren't recompiling just to get SCSI support. This is pretty firm - I have one idea I may / may not want to implement that I'll talk about in the end. -- cut here - hosts.h -- #ifndef __HOST_H__ #define __HOSTS_H__ /* File hosts.h SCSI host adapter include file. */ #define MAX_SCSI_HOSTS 1 /* The Scsi_Host type has all that is needed to interface with a SCSI host in a device independant matter. */ typedef struct { /* The name pointer is a pointer to the name of the SCSI device detected. */ char *name; /* The detect function shall return non zero on detection, and initialize all data necessary for this particular SCSI driver. */ int (* detect)(void); /* The info function will return whatever useful information the developer sees fit. */ char * (* info)(void); /* The command function shall return the SCSI return code in the low 8 bits, a driver error in the high 8 bits. Target is the target ID, IN normal numbers - not a bit. The cmnd is the variable length command to be sent, buff a pointer to the buffer which will be read from / written to, and bufflen the length of that buffer */ int (* command)(unsigned char target, const void *cmnd, void *buff, int bufflen); /* present contains a flag as to weather we are present - so we don't have to call detect multiple times. */ unsigned char present; } Scsi_Host; /* The scsi_hosts array is the array containing the data for all possible scsi hosts. */ extern Scsi_Host scsi_hosts[MAX_SCSI_HOSTS]; /* scsi_init initializes the scsi hosts. */ void scsi_init(void); #endif -- end -- And, for our return codes, useful SCSI stuff, etc, we have scsi.h -- scsi.h cut here -- #ifndef __SCSI_H__ #define __SCSI_H__ /* For documentation on the OPCODES, MESSAGES, and SENSE values, please consult the SCSI standard. */ /* SCSI opcodes */ #define TEST_UNIT_READY 0x00 #define REZERO_UNIT 0x01 #define REQUEST_SENSE 0x03 #define FORMAT_UNIT 0x04 #define REASSIGN_BLOCKS 0x07 #define READ_6 0x08 #define WRITE_6 0x0a #define SEEK 0x0b #define INQUIRY 0x12 #define MODE_SELECT 0x15 #define RESERVE 0x16 #define RELEASE 0x17 #define COPY 0x18 #define MODE_SENSE 0x1a #define START_STOP 0x1b #define RECIEVE_DAIGNOSTIC 0x1c #define SEND_DIAGNOSTIC 0x1d #define ALLOW_MEDIUM_REMOVAL 0x1e #define READ_CAPACITY 0x25 #define READ_10 0x28 #define WRITE_10 0x2a #define SEEK_10 0x2b #define WRITE_VERIFY 0x2e #define VERIFY 0x2f #define SEARCH_HIGH 0x30 #define SEARCH_EQUAL 0x31 #define SEARCH_LOW 0x32 #define SET_LIMITS 0x33 #define COMPARE 0x39 #define COPY_VERIFY 0x3a /* MESSAGE CODES */ #define COMMAND_COMPLETE 0x00 #define EXTENDED_MESSAGE 0x01 #define SAVE_POINTERS 0x02 #define RESTORE_POINTERS 0x03 #define DISCONNECT 0x04 #define INITIATOR_ERROR 0x05 #define ABORT 0x06 #define MESAGE_REJECT 0x07 #define NOP 0x08 #define MSG_PARITY_ERROR 0x09 #define LINKED_CMD_COMPLETE 0x0a #define LINKED_FLG_CMD_COMPLETE 0x0b #define BUS_DEVICE_RESET 0x0c #define IDENTIFY 0x80 /* Our errors returned by OUR driver, NOT SCSI message. Orr'd with SCSI message passed back to driver . */ /* NO error */ #define DID_OK 0x0000 /* Couldn't connect before timeout period */ #define DID_NO_CONNECT 0x0100 /* BUS stayed busy through time out period */ #define DID_BUS_BUSY 0x0200 /* TIMED OUT for other reason */ #define DID_TIME_OUT 0x0300 /* ERROR from TARGET */ #define DID_TERROR 0x0400 /* TARGET was busy */ #define DID_TBUSY 0x0500 /* TARGET disconnected prematurely */ #define DID_TDISCONNECT 0x0600 /* TARGET was off line */ #define DID_TOFFLINE 0x0700 /* TARGET wants US to send IT a message */ #defibe DID_TREQ_MSG_OUT 0x0800 /* TARGET parity error */ #define DID_TPARITY 0x0900 /* TARGET requested reselect */ #define DID_TRESELECT 0x0A00 /* TARGET was not in the range 0-6 inlclusive */ #define DID_BAD_TARGET 0x0B00 /* SENSE KEYS */ #define NO_SENSE 0x00 #define RECOVERED_ERROR 0x01 #define NOT_READY 0x02 #define MEDIUM_ERROR 0x03 #define HARDWARE_ERROR 0x04 #define ILLEGAL_REQUEST 0x05 #define UNIT_ATTENTION 0x06 #define DATA_PROTECT 0x07 #define BLANK_CHECK 0x08 #define COPY_ABORTED 0x0a #define ABORTED_COMMAND 0x0b #define VOLUME_OVERFLOW 0x0d #define MISCOMPARE 0x0e /* DEVICE TYPES */ #define TYPE_DISK 0x00 #define TYPE_TAPE 0x01 #define TYPE_WORM 0x04 /* Treated as ROM by our system */ #define TYPE_ROM 0x05 #define TYPE_NO_LUN 0x7f /* Every SCSI command starts with a one byte OP-code. The next byte's high three bits are the LUN of the device. Any multi-byte quantities are stored high byte first, and may have a 5 bit MSB in the same byte as the LUN. */ #endif -- end -- I'll divert work from the low level routines to the high & mid level routines to have something to pass around for when people start getting other low level drivers done. I *REALLY* like the above interface in terms of meeting the design criteria of simplicity, independance of the host-specific code, and the ability for the routines to configure automatically. The finaly interface will be almost identical to what is there now. However, it might also be nice to be able to queue commands for use with interrupt driven SCSI hosts that can function without the computer controlling everything- We may want to add a que_command call that will add a command to an internal queue in the host specific driver. This would be something like the command function, only it would also take a pointer to a routine that was called on completion, like int (*queue_command)(unsigned char target, const void *cmd, void *buff, int bufflen, void (*complete)(int host, int serial_no, int cmd_return)); Where it returns the serial number of the queued command, and calls the complete function on termination with the SCSI message / return code , host # and serial number of the command that terminated. Other solicitations for opinions 1. Other peoples opinions on when to remap 2. What we want to do about sector sizes that are not 512 bytes 3. Currently, I use only 10 byte read/writes in my disk / tape drivers. The rationale behind this is that 10 byte commands fall in the same compliance level as INQUIRY and READ CAPACITY commmands, and presumably a drive would have all. Is this a valid ssumption? Does anybody see a reason for me to bloat the code and check for 10 byte commmand failure, and implement the 6 byte read/write if so? --[0182]-- [0183] daemon@ATHENA.MIT.EDU (drew@anchor.cs.colorado.edu) Linux_Activists 12/11/91 19:39 (359 lines) Subject: Re: Linux and SCSI To: Linux-activists@joker.cs.hut.fi, Cc: drew@anchor.cs.colorado.edu Date: Wed, 11 Dec 91 17:17:25 MST From: drew@anchor.cs.colorado.edu -------- > > Date: Tue, 10 Dec 91 12:13:59 CST > To: drew@hazelrah.cs.Colorado.EDU > From: johnsonm@stolaf.edu (Michael K. Johnson) > Subject: Re: Linux and SCSI (was: hd_reset fails in 0.11) > > > Return-Path: johnsonm@stolaf.edu > Status: RO > > -------------------------------------------------------------------- > I am just learning unix systems programming with linux, but I have > a SCSI hard drive and a DTC adapter, and would be very willing to > write the device dependent stuff for it when I get to that ability > level if no one else has done it be then. I will be taking an OS > class next semester (starting february) so I could even use this > as a project. So although I can't do this right now, I would like > it if you could put me on your list to get the information, which > I can save and then hopefully work on when I am able. > > Thanks a lot! > > michaelkjohnson > > Date: Tue, 10 Dec 91 12:17:07 CST > To: Linux-activists@joker.cs.hut.fi > From: johnsonm@stolaf.edu (Michael K. Johnson) > Subject: DTC SCSI controllers > > > Return-Path: johnsonm@stolaf.edu > Status: RO > > -------------------------------------------------------------------- > > I have a DTC SCSI controller, and would be willing to (as I become a bit > more proficient) write the low-level driver for it. However, there is > a catch -- I will almost assuredly, due to my schedule, not be able to > start till february or so. Sooooo, if anyone else wants to pick this > up, feel free:-) > > If anyone needs to talk to them, I have voice and BBS numbers for their > tech support. > > michaelkjohnson > johnsonm@stolaf.edu > I do not do .sig's > > > > > Date: Tue, 10 Dec 91 13:04:50 PST > To: Linux-activists@joker.cs.hut.fi, drew@hazelrah.cs.Colorado.EDU, > kronvold@sumter.cso.uiuc.edu > From: David Darknell > Subject: Re: Linux and SCSI (was: hd_reset fails in 0.11) > > > Return-Path: david@maxwell.UCSC.EDU > Status: RO > > -------------------------------------------------------------------- > YES! I am trying to write a driver for a FastCache High performance > SCSI controller (I used to have a ST-01/02) but I am in a catch 22: > I cannot run Linux on the drive without a driver, but cannot write the > driver without Linux. So here is my plan: Install MFM controller and > 40Meg drive long enough to write the SCSI driver, then dump it. I > would > be happy to get anything you have that might make my job easier! -------- You don't have to compile Linux under Linux. Another possibility is cross compiling. If you have access to another little endian machine , LSB first, cross compiling is as easy as doing a make gcc with target machine set to some tm-i386 file. Depending on how the host system is set up, you may be able to use the native ld / ar - and even if not, it is no problem to compile the gnu binutils and have gcc/gas use them. Anyways, here's my hosts.h file, the generic interface to the lowlevel host specific drivers. There isn't much too it - the point here was to keep things SIMPLE, flexible, and 100% self configuring so we aren't recompiling just to get SCSI support. This is pretty firm - I have one idea I may / may not want to implement that I'll talk about in the end. -- cut here - hosts.h -- #ifndef __HOST_H__ #define __HOSTS_H__ /* File hosts.h SCSI host adapter include file. */ #define MAX_SCSI_HOSTS 1 /* The Scsi_Host type has all that is needed to interface with a SCSI host in a device independant matter. */ typedef struct { /* The name pointer is a pointer to the name of the SCSI device detected. */ char *name; /* The detect function shall return non zero on detection, and initialize all data necessary for this particular SCSI driver. */ int (* detect)(void); /* The info function will return whatever useful information the developer sees fit. */ char * (* info)(void); /* The command function shall return the SCSI return code in the low 8 bits, a driver error in the high 8 bits. Target is the target ID, IN normal numbers - not a bit. The cmnd is the variable length command to be sent, buff a pointer to the buffer which will be read from / written to, and bufflen the length of that buffer */ int (* command)(unsigned char target, const void *cmnd, void *buff, int bufflen); /* present contains a flag as to weather we are present - so we don't have to call detect multiple times. */ unsigned char present; } Scsi_Host; /* The scsi_hosts array is the array containing the data for all possible scsi hosts. */ extern Scsi_Host scsi_hosts[MAX_SCSI_HOSTS]; /* scsi_init initializes the scsi hosts. */ void scsi_init(void); #endif -- end -- And, for our return codes, useful SCSI stuff, etc, we have scsi.h -- scsi.h cut here -- #ifndef __SCSI_H__ #define __SCSI_H__ /* For documentation on the OPCODES, MESSAGES, and SENSE values, please consult the SCSI standard. */ /* SCSI opcodes */ #define TEST_UNIT_READY 0x00 #define REZERO_UNIT 0x01 #define REQUEST_SENSE 0x03 #define FORMAT_UNIT 0x04 #define REASSIGN_BLOCKS 0x07 #define READ_6 0x08 #define WRITE_6 0x0a #define SEEK 0x0b #define INQUIRY 0x12 #define MODE_SELECT 0x15 #define RESERVE 0x16 #define RELEASE 0x17 #define COPY 0x18 #define MODE_SENSE 0x1a #define START_STOP 0x1b #define RECIEVE_DAIGNOSTIC 0x1c #define SEND_DIAGNOSTIC 0x1d #define ALLOW_MEDIUM_REMOVAL 0x1e #define READ_CAPACITY 0x25 #define READ_10 0x28 #define WRITE_10 0x2a #define SEEK_10 0x2b #define WRITE_VERIFY 0x2e #define VERIFY 0x2f #define SEARCH_HIGH 0x30 #define SEARCH_EQUAL 0x31 #define SEARCH_LOW 0x32 #define SET_LIMITS 0x33 #define COMPARE 0x39 #define COPY_VERIFY 0x3a /* MESSAGE CODES */ #define COMMAND_COMPLETE 0x00 #define EXTENDED_MESSAGE 0x01 #define SAVE_POINTERS 0x02 #define RESTORE_POINTERS 0x03 #define DISCONNECT 0x04 #define INITIATOR_ERROR 0x05 #define ABORT 0x06 #define MESAGE_REJECT 0x07 #define NOP 0x08 #define MSG_PARITY_ERROR 0x09 #define LINKED_CMD_COMPLETE 0x0a #define LINKED_FLG_CMD_COMPLETE 0x0b #define BUS_DEVICE_RESET 0x0c #define IDENTIFY 0x80 /* Our errors returned by OUR driver, NOT SCSI message. Orr'd with SCSI message passed back to driver . */ /* NO error */ #define DID_OK 0x0000 /* Couldn't connect before timeout period */ #define DID_NO_CONNECT 0x0100 /* BUS stayed busy through time out period */ #define DID_BUS_BUSY 0x0200 /* TIMED OUT for other reason */ #define DID_TIME_OUT 0x0300 /* ERROR from TARGET */ #define DID_TERROR 0x0400 /* TARGET was busy */ #define DID_TBUSY 0x0500 /* TARGET disconnected prematurely */ #define DID_TDISCONNECT 0x0600 /* TARGET was off line */ #define DID_TOFFLINE 0x0700 /* TARGET wants US to send IT a message */ #defibe DID_TREQ_MSG_OUT 0x0800 /* TARGET parity error */ #define DID_TPARITY 0x0900 /* TARGET requested reselect */ #define DID_TRESELECT 0x0A00 /* TARGET was not in the range 0-6 inlclusive */ #define DID_BAD_TARGET 0x0B00 /* SENSE KEYS */ #define NO_SENSE 0x00 #define RECOVERED_ERROR 0x01 #define NOT_READY 0x02 #define MEDIUM_ERROR 0x03 #define HARDWARE_ERROR 0x04 #define ILLEGAL_REQUEST 0x05 #define UNIT_ATTENTION 0x06 #define DATA_PROTECT 0x07 #define BLANK_CHECK 0x08 #define COPY_ABORTED 0x0a #define ABORTED_COMMAND 0x0b #define VOLUME_OVERFLOW 0x0d #define MISCOMPARE 0x0e /* DEVICE TYPES */ #define TYPE_DISK 0x00 #define TYPE_TAPE 0x01 #define TYPE_WORM 0x04 /* Treated as ROM by our system */ #define TYPE_ROM 0x05 #define TYPE_NO_LUN 0x7f /* Every SCSI command starts with a one byte OP-code. The next byte's high three bits are the LUN of the device. Any multi-byte quantities are stored high byte first, and may have a 5 bit MSB in the same byte as the LUN. */ #endif -- end -- I'll divert work from the low level routines to the high & mid level routines to have something to pass around for when people start getting other low level drivers done. I *REALLY* like the above interface in terms of meeting the design criteria of simplicity, independance of the host-specific code, and the ability for the routines to configure automatically. The finaly interface will be almost identical to what is there now. However, it might also be nice to be able to queue commands for use with interrupt driven SCSI hosts that can function without the computer controlling everything- We may want to add a que_command call that will add a command to an internal queue in the host specific driver. This would be something like the command function, only it would also take a pointer to a routine that was called on completion, like int (*queue_command)(unsigned char target, const void *cmd, void *buff, int bufflen, void (*complete)(int host, int serial_no, int cmd_return)); Where it returns the serial number of the queued command, and calls the complete function on termination with the SCSI message / return code , host # and serial number of the command that terminated. Other solicitations for opinions 1. Other peoples opinions on when to remap 2. What we want to do about sector sizes that are not 512 bytes 3. Currently, I use only 10 byte read/writes in my disk / tape drivers. The rationale behind this is that 10 byte commands fall in the same compliance level as INQUIRY and READ CAPACITY commmands, and presumably a drive would have all. Is this a valid ssumption? Does anybody see a reason for me to bloat the code and check for 10 byte commmand failure, and implement the 6 byte read/write if so? --[0183]-- [0184] daemon@ATHENA.MIT.EDU (John T Kohl) Linux_Activists 12/12/91 00:12 (10 lines) Subject: GNU awk (binaries & sources) Date: Wed, 11 Dec 91 21:07:17 PST To: linux-activists@joker.cs.hut.fi From: John T Kohl Reply-To: jtkohl@cs.berkeley.edu I've had Ted Ts'o put my port of GNU awk (2.11, I think it was...) onto tsx-11.mit.edu, in ~ftp/pub/linux/binaries & ~ftp/pub/linux/ports (the latter has diffs from the FSF distributed sources). John --[0184]-- [0185] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 12/12/91 10:18 (8 lines) Subject: find-1.2 (binaries only) Date: Thu, 12 Dec 91 15:47:53 +0100 From: corsini@numero6.greco-prog.fr (Marc CORSINI) To: linux-activists@joker.cs.hut.fi The port of GNU find-1.2, is available on tsx-11.mit.edu in pub/linux/binaries [mmc] --[0185]-- [0186] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/12/91 11:49 (40 lines) Subject: find-1.2 Date: Thu, 12 Dec 1991 18:16:00 +0200 From: Ari Lemmke To: linux-activists@joker.cs.hut.fi In-Reply-To: Marc CORSINI's message of Thu, 12 Dec 91 15:47:53 +0100 <9112121447.AA03130@numero6.greco-prog.fr> > The port of GNU find-1.2, is available on tsx-11.mit.edu in > pub/linux/binaries Also available on nic.funet.fi: /pub/OS/Linux/bin: -rw-r--r-- 1 arl 51202 Dec 8 15:47 as86.tar.Z -rw-r--r-- 1 arl 146964 Sep 17 17:24 bash.Z -rw-r--r-- 1 arl 76265 Nov 17 04:01 bison.tar.Z -rw-r--r-- 1 arl 90721 Nov 17 20:53 diffbin.tar.Z -rw-r--r-- 1 arl 106429 Dec 12 03:56 find-1.2.tar.Z -rw-r--r-- 1 arl 76925 Nov 17 04:08 flex.tar.Z -rw-r--r-- 1 arl 7722 Dec 12 03:56 gawk-diffs -rw-r--r-- 1 arl 68625 Dec 12 03:57 gawk.Z -rw-r--r-- 1 arl 666231 Oct 2 14:49 gccbin.tar.Z -rw-r--r-- 1 arl 87613 Nov 17 20:53 kermit.Z -rw-r--r-- 1 arl 42737 Nov 20 07:31 less.Z -rw-r--r-- 1 arl 262475 Dec 6 05:38 rcs.tar.Z -rw-r--r-- 1 arl 91743 Dec 8 19:24 uemacs.Z -rw-r--r-- 1 arl 930 Sep 17 17:24 update.Z -rw-r--r-- 1 arl 898837 Oct 6 14:57 utilbin.tar.Z /pub/OS/Linux/xtra: -rw-r--r-- 1 arl 375 Nov 20 07:30 README.pmake -rw-r--r-- 1 arl 6380 Nov 20 07:30 pm_supp.tar.Z -rw-r--r-- 1 arl 72229 Nov 20 07:30 pmake.Z /pub/OS/Linux/tools: -rw-r--r-- 1 arl 16270 Nov 18 20:32 fsck.c arl --[0186]-- [0187] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/12/91 13:50 (31 lines) Subject: Looking for alpha testers for job control changes Date: Thu, 12 Dec 91 13:30:42 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: linux-activists@joker.cs.hut.fi Reply-To: tytso@athena.mit.edu I'm looking for a few people who are willing to take a look at my changes to add job control to Linux and test them out. The ideal alpha tester is someone who is willing to try out these changes and see if 1) they can find some way of using job control which breaks my implementation, 2) if they conflict with changes they are planning to make to the kernel (mostly changes in exit.c and signal.c, with additional changes in tty_io.c, tty_ioctl.c, sys.c, and open.c), and/or 3) if they reasonably correspond with other implementations of job control, particularily BSD 4.3 and Sys V. I make no guarantees about the correctness of these patches, and any future patches which I send out will be relative to Linux 0.11, NOT to these alpha patches. The main reason why I want people to try them out is that I've implemented job control almost entirely from the POSIX spec, and I would other people to check to see if my interpretation of the POSIX spec is compatible with the rest of the world. If you feel up to trying them out, please let me know. If you want to look at the changes before deciding, they can be found in TSX-11:~ftp/ALPHA/jobcontrol. One generic bug which will hit when you try this is out is that apparently there is a bug with how gcc handles signals. If you send gcc a SIGCONT (you don't even need to stop it first), it will die with an IOT trap. I suspect gcc needs to be recompiled with a recent libc.a to fix this problem. - Ted --[0187]-- [0188] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/12/91 14:06 (42 lines) Subject: "weekly" bugreport etc Date: Thu, 12 Dec 1991 20:52:46 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi Well, time for my weekly bug-report again. Nothing too bad this time. 1) linux/kernel/signal.c kills a process with the wrong error code when it gets a signal that the process doesn't handle. The easiest way to test this is by sending a SIGQUIT to some running program (with ^|) - bash will report that the program died due to "Illegal Instruction" This bug already got corrected in some version, but it wiggled its way back :-(. The line is something like this (in do_signal()): if (!sa_handler) { if (nr == SIGCHLD) return; else do_exit(1<<(nr-1)); } when it should be if (!sa_handler) { if ... ... else do_exit(nr); } 2) As has been shown, you can get spurious "out of memory" errors if the passwd file has the incorrect format. This wasn't a error in the kernel, but in the library - I'll correct it by using the GNU lib etc. I'll also make full library source available (not before sunday: I've got 1e3 things to do). In the meanwhile, this bug isn't easy to trigger, and not fatal even then, so... Linus PS. I'm interested in hearing about everybody that has problems with either the harddisk or the serial line. There was a report that serial lines sent out 2 characters at a time - does anybody else see this? --[0188]-- *** /afs/net/tools/src/play/play.c Tue Jul 23 13:15:03 1991 --- play.c Wed Dec 18 17:38:06 1991 *************** *** 30,35 **** --- 30,37 ---- #define OPTION_TICKLE_SSAVE 2 int Special_X_Error_Handler(); + int (*Default_X_Error_Handler)(); + int bad_window_found; /* This is set if a bad window error */ /* is ignored */ *************** *** 137,143 **** /* * Redirect the error routine so bad windows don't kill us. */ ! XSetErrorHandler(Special_X_Error_Handler); while (1) { int no_state; --- 139,145 ---- /* * Redirect the error routine so bad windows don't kill us. */ ! Default_X_Error_Handler = XSetErrorHandler(Special_X_Error_Handler); while (1) { int no_state; *************** *** 413,516 **** bad_window_found++; return 0; } ! if (_XPrintDefaultError(dpy, event, stderr) == 0) ! return 0; ! exit(1); ! } ! ! /* ! * Stolen from X11R4's XlibInt.c ! */ ! int _XPrintDefaultError (dpy, event, fp) ! Display *dpy; ! XErrorEvent *event; ! FILE *fp; ! { ! char buffer[BUFSIZ]; ! char mesg[BUFSIZ]; ! char number[32]; ! char *mtype = "XlibMessage"; ! register _XExtension *ext = (_XExtension *)NULL; ! XGetErrorText(dpy, event->error_code, buffer, BUFSIZ); ! XGetErrorDatabaseText(dpy, mtype, "XError", "X Error", mesg, BUFSIZ); ! (void) fprintf(fp, "%s: %s\n ", mesg, buffer); ! XGetErrorDatabaseText(dpy, mtype, "MajorCode", "Request Major code %d", ! mesg, BUFSIZ); ! (void) fprintf(fp, mesg, event->request_code); ! if (event->request_code < 128) { ! sprintf(number, "%d", event->request_code); ! XGetErrorDatabaseText(dpy, "XRequest", number, "", buffer, BUFSIZ); ! } else { ! for (ext = dpy->ext_procs; ! ext && (ext->codes.major_opcode != event->request_code); ! ext = ext->next) ! ; ! if (ext) ! strcpy(buffer, ext->name); ! else ! buffer[0] = '\0'; ! } ! (void) fprintf(fp, " (%s)\n ", buffer); ! if (event->request_code >= 128) { ! XGetErrorDatabaseText(dpy, mtype, "MinorCode", "Request Minor code %d", mesg, BUFSIZ); ! (void) fprintf(fp, mesg, event->minor_code); ! if (ext) { ! sprintf(mesg, "%s.%d", ext->name, event->minor_code); ! XGetErrorDatabaseText(dpy, "XRequest", mesg, "", buffer, BUFSIZ); ! (void) fprintf(fp, " (%s)", buffer); ! } ! fputs("\n ", fp); ! } ! if (event->error_code >= 128) { ! /* kludge, try to find the extension that caused it */ ! buffer[0] = '\0'; ! for (ext = dpy->ext_procs; ext; ext = ext->next) { ! if (ext->error_string) ! (*ext->error_string)(dpy, event->error_code, &ext->codes, ! buffer, BUFSIZ); ! if (buffer[0]) ! break; ! } ! if (buffer[0]) ! sprintf(buffer, "%s.%d", ext->name, ! event->error_code - ext->codes.first_error); ! else ! strcpy(buffer, "Value"); ! XGetErrorDatabaseText(dpy, mtype, buffer, "Value 0x%x", mesg, BUFSIZ); ! if (*mesg) { ! (void) fprintf(fp, mesg, event->resourceid); ! fputs("\n ", fp); ! } ! } else if ((event->error_code == BadWindow) || ! (event->error_code == BadPixmap) || ! (event->error_code == BadCursor) || ! (event->error_code == BadFont) || ! (event->error_code == BadDrawable) || ! (event->error_code == BadColor) || ! (event->error_code == BadGC) || ! (event->error_code == BadIDChoice) || ! (event->error_code == BadValue) || ! (event->error_code == BadAtom)) { ! if (event->error_code == BadValue) ! XGetErrorDatabaseText(dpy, mtype, "Value", "Value 0x%x", ! mesg, BUFSIZ); ! else if (event->error_code == BadAtom) ! XGetErrorDatabaseText(dpy, mtype, "AtomID", "AtomID 0x%x", ! mesg, BUFSIZ); ! else ! XGetErrorDatabaseText(dpy, mtype, "ResourceID", "ResourceID 0x%x", ! mesg, BUFSIZ); ! (void) fprintf(fp, mesg, event->resourceid); ! fputs("\n ", fp); ! } ! XGetErrorDatabaseText(dpy, mtype, "ErrorSerial", "Error Serial #%d", ! mesg, BUFSIZ); ! (void) fprintf(fp, mesg, event->serial); ! fputs("\n ", fp); ! XGetErrorDatabaseText(dpy, mtype, "CurrentSerial", "Current Serial #%d", ! mesg, BUFSIZ); ! (void) fprintf(fp, mesg, dpy->request); ! fputs("\n", fp); ! if (event->error_code == BadImplementation) return 0; ! return 1; } --- 415,420 ---- bad_window_found++; return 0; } ! else ! return(Default_X_Error_Handler(dpy, event)); } [0189] daemon@ATHENA.MIT.EDU (Ken Corey, CSCI Major...) Linux_Activists 12/12/91 19:35 (35 lines) Subject: Future Domain, SCSI, partition types, etc. Date: Thu, 12 Dec 1991 18:27 CDT From: "Ken Corey, CSCI Major..." To: Linux-activists@joker.cs.hut.fi X-Vms-To: IN%"Linux-activists@joker.cs.hut.fi" Has anyone had any luck installing Linux on a drive that uses a Future Domain chipset? I've got a 386/25 4MB ram, DOS 5.0, Maxtor 7120sr SCSI Hard drive, Future Domain chipset SCSI controller. I've gotten the boot and root disks to work, but when I run the fdisk, I get 5 errors. (I've got my drive partitioned into 4 32MB partitions) I read that if FDISK cannot recognize my partitions, then I an "f**ked" (from the documentation). Basically, I'm asking if anyone has gotten such a setup to work, and if so, what's the method. If not, is anyone working on a future domain compatible version? I understand that several people across the net are working on SCSI implementations...do you think that they will work with a future domain controller? I'd dearly love to use Linux, (as it's a 32-bit OS from the start, rather than a 16-bit emulating a 32-bit). If anyone has run into this problem, either reply to the net, or to my 'home' address. Many thanks. Talk to y'all later. , o <--- The too-many-hours-on-a-monitor blank stare _ | Ken Corey aka kenc@vaxb.acs.unt.edu aka kenc@sol.acs.unt.edu --[0189]-- [0190] daemon@ATHENA.MIT.EDU (John T Kohl) Linux_Activists 12/13/91 01:08 (17 lines) Subject: uniq binary & source; perl? Date: Thu, 12 Dec 91 22:01:08 PST To: linux-activists@joker.cs.hut.fi From: John T Kohl Reply-To: jtkohl@cs.berkeley.edu I've had uniq.Z and uniq.src.tar.Z (from the bsd-net-2 release) put onto tsx-11.mit.edu:pub/linux/{binaries,sources} for your enjoyment. Has anybody had luck in getting perl 4 working? I've tried various things, most of which cause test/base/lex.t to fail. -m80387 present/absent -O/-g -Dfloat=double no combination of the above makes a working perl. ?? John --[0190]-- [0191] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/13/91 04:40 (125 lines) Subject: New posting of INFO SHEET Date: Fri, 13 Dec 91 10:28:00 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! This is the corrected (Thanks for proofreading, tytso!) Linux information sheet. If there are no further remarks to it, I will post it to the following groups: comp.binaries.ibm.pc.d comp.os.coherent comp.os.mach comp.os.minix comp.os.misc comp.os.sysv.i386 comp.unix.programmers Thanks, and see you! Robert Blum LINUX INFORMATION SHEET 1. WHAT IS LINUX 0.11 LINUX 0.11 is a freely distributable UNIX clone. It is almost fully System V and POSIX compatible. LINUX has been written from scratch, and therefore does not contain any AT&T or MINIX code - not in the kernel, the compiler, the utilities, or the libraries. For this reason it can be made available with the complete source code via anonymous FTP. Sorrily it runs only on 386/486 AT-bus-machines.EISA will probably do too, but you need an AT-Bus controller for your harddisk. Version 0.11 is still a beta release, but it provides almost full functionality. Various users have been able to compile bigger projects like bison/flex by only changing the makefile to their needs, and these tools are fully functional. 2. LINUX features - System call compatible with System V and POSIX (well, almost..) - Full multiprogramming (multiple programs can run at once) - Memory paging with copy-on-write - Demand loading of executables - Page sharing of executables - ANSI compliant C compiler (gcc) - A complete set of compiler writing tools (bison as yacc-replacement, flex as lex replacement) - The gnu-born again shell (bash) - Micro emacs - most utilities you need for development (cat, cp, kermit, ls, make, etc.) - Over 200 library procedures (atoi, fork, malloc, read, stdio, etc.) - Currently 4 national keyboards: finnish/us/german/french - Full source code (in C) for the OS is freely distributable - Full source code of the tools can be gotten from many anonymous ftp sites (It's almost completely the GNU project) - Runs in protected mode on 386 and above - Support for extended memory up to 16M on 386 and above - RS-232 serial line support with terminal emulation, kermit, zmodem, etc. - Supports the real time clock 3. HARDWARE REQUIRED - A 386 or 486 machine that is an AT-bus-machine. EISA will probably do too. - An IDE hard disk is required to use this system. - Both 5.25" and 3.5" diskettes are supported - At least 2 megabytes of RAM is required for LINUX to be operational, but gcc will only work from 4 MB on. - Any video card will do - Up to two serial lines are supported - The real time clock is supported 4. PARTIAL LIST OF UTILITIES INCLUDED IN OR AVAILABLE FOR LINUX 0.10 - The MTOOLS package (reading/writing to DOS) - The complete GNU filetools (ls,cat,cp,mv,...) - The GNU C compiler with GNU assembler,linker,ar,... - bison - flex - rcs - pmake (BSD 4.3 Reno/BSD 4.4 make) - kermit - Micro emacs - less - mkfs - fsck - mount/umount 5. LINUX BINARIES The LINUX binaries (including all the tools) are available at three anonymous FTP sites. These are: nic.funet.fi:/pub/OS/Linux tsx-11.mit.edu:/pub/linux tupac-amaru.informatik.rwth-aachen.de:/pub/msdos/replace 6. LEGAL STATUS OF LINUX Although LINUX is supplied with the complete source code, it is copyrighted software. But it is, opposite to MINIX available for free, provided you obey to the rules specified in the LINUX copyright. 7. NEWS ABOUT LINUX Since LINUX's introduction to the public there has been a rapidly growing mailing list, "linux-activists@joker.cs.hut.fi". To subscribe to this list, mail to "linux-activists-requests@joker.cs.hut.fi". If the traffic in this lists increases further, there are plans to swap (at least partially) over to comp.os.misc, so watch out for any LINUX articles in this group. If you simply want to know whats the current state of the art, do a "finger torvalds@kruuna.helsinki.fi", and you'll get some information. 8. FUTURE PLANS The major current project is bringing LINUX to a version number greater than 1.0. It has also to undergo some (minor) revisions to be compatible to the IEEE POSIX P1003.1 and P1003.2 standards. Various people are currently working on - math support/fp emulation in the kernel - Page swapping (since paging is alreay implemented) - A virtual filesystem layer - STREAMS - POSIX job control (this is already alpha and will probably be out with Version 0.12) If you want to join the developers, join the mailing list --[0191]-- [0192] daemon@ATHENA.MIT.EDU (Drew Eckhardt) Linux_Activists 12/14/91 15:07 (533 lines) Subject: Dain bramaged boot sector and compatable clones Date: Sat, 14 Dec 1991 12:57:14 -0700 From: Drew Eckhardt To: linux-activists@joker.cs.hut.fi, torvalds@cc.helsinki.fi Cc: drew@hazelrah.cs.Colorado.EDU A few days ago, I mailed Linus about the bootsector not working on some machines. Specifically, some 386/486 boxes with AMI BIOS, not exactly rice paddy specials. The MS-DOS boot sector handles reads in a similar way, and it worked fine. The problem is some clones use the same messed up floppy disk parameter tables that the original PC used. You have to change the byte that reflects maximum sector number to something reasonable (18 works good - #sectors on a 1.44, doesn't matter if its too high) to keep from getting a sector not found error. MS-DOS does this, Linus's boot sector didn't, and was dying. I have changed the bootsector code to update this byte in the diskette parameter table. Also, I've made the following other changes : - Added error dump code. The error code in ax is printed (in hex) after any failed disk read. This contains an error code in the high byte, sectors successfully read in the low byte. In the code that reads the kernel, an error also dumps the registers that were used in the int 13h call - ie an error code of 0407 - sector not found, read 7 sectors might read 0407 AX:020F BX:1400 CX:0001 DX:0100 - Added a Loading... where one dot is printed per track read. Lets you know something is happening, and fills up some of that vast empty space in the bootsector... - Added conditional define to hard code #of sectors, and allow booting from a 360K disk in a 1.2M drive, etc. The BIOS routines return MAXIMUM number of sectors, not the actual count of the media in the drive. - Optimized. There are now two bytes free in the boot sector. Without any optimization, there were negative bytes free. The source code is currently only available in MASM format. This made debugging under a monitor program loaded in high memory under DOS quite simple.... some one (Eventually, I will. Before this is finalized though, I'd like to look at booting of any drive) can translate it back if they want it sooner... The binary included below is set up with root=boot drive, autodetect floppy. I had been testing it with HARD defined as 9, and root set as a 1.44 in drive 1, a fairly normal configuraiton, so this explains any failures.. And, if you do get an error code, PLEASE report it. -- bootsect.uue -- : section 1 of uuencode 2.8 of file bootsect.bin by R.E.M. begin 644 bootsect.bin MN,`'CMBX`)".P+D``2OV*__\\Z7J&0``D/J,R([0O/3^,\".P`:[>``FQ3>,W MR([`O_3^5[D&`/.E7R;&1002!R:)/XS()HE'`H[8CL#[,N0RTLT3,]*Y`@"[F M``*X!`+-$W,24.A)`8OLZ%P!6#+2,\#-$^O?,M*X``C-$S+M+HD.[P&X`)"." MP+0#,O_-$+D)`+L'`+WQ`;@!$\T0N``0CL#H/@#H/P&X#0Z[!P#-$+@*#LT0& M+J'\`0O`=1@)Q MZ#D`B\@N`P;<`"X[!N\!=16X`0`N*P;>`'4%+O\&X``NH]X`,\`NH]P`P>$)' M`]ESK(S`!0`0CL`SV^NA8%!3N"X.NP<`S1!;6"Z+%N``+HL.W`!!BNHNBQ;>* M`(KR,M*!X@`!M`)245-0S1-R!8/$"&'#4.@,`#+D,M+-$X/$"F'KNKD%`(OLP MZ!@`@/D%T#LT0XNG#4KKR`S+`[EK#Q 1```-"DQO861I;F<``!T"5:H"H `` end size 512 -- end -- You could write it with DEBUG like DEBUG bootsect.bin a 0300 mov ax, 0201 mov bx, 0100 mov cx, 0001 mov dx, 0000 int 13h int 20h ^C g=0300 q And the source -- bootsect.asm -- ; Created by 2masm perl script by Drew Eckhardt ; bootsect.asm modified by Drew Eckhardt - ; support added for TRUELY compatable ; BIOS's as well as error dump code. .286 ; ; SYS_SIZE is the number of clicks (16 bytes) to be loaded. ; 3000h is 30000h bytes equ 196kB, more than enough for current ; versions of linux ; SYSSIZE equ 3000h ; ; bootsect.s (C) 1991 Linus Torvalds ; ; bootsect.s is loaded at 7c00h by the bios-startup routines, and moves ; iself out of the way to address 90000h, and jumps there. ; ; It then loads 'setup' directly after itself (90200h), and the system ; at 10000h, using BIOS interrupts. ; ; NOTE; currently system is at most 8*65536 bytes long. This should be no ; problem, even in the future. I want to keep it simple. This 512 kB ; kernel size should be enough, especially as this doesn't contain the ; buffer cache as in minix ; ; The loader has been made as simple as possible, and continuos ; read errors will result in a unbreakable loop. Reboot by hand. It ; loads pretty fast by getting whole sectors at a time whenever possible. _TEXT segment para public 'CODE' assume cs:_TEXT SETUPLEN equ 4 ; nr of setup-sectors BOOTSEG equ 07c0h ; original address of boot-sector INITSEG equ 9000h ; we move boot here - out of the way SETUPSEG equ 9020h ; setup starts here SYSSEG equ 1000h ; system loaded at 10000h (65536). ENDSEG equ SYSSEG + SYSSIZE ; where to stop loading ; ROOT_DEV: 000h - same type of floppy as boot. ; 301h - first partition on first drive etc ROOTDEV equ 21dh start: mov ax,offset BOOTSEG mov ds,ax mov ax,offset INITSEG mov es,ax mov cx,256 sub si,si sub di,di cld rep movsw db 0eah ; jmp INITSEG:go dw offset go dw INITSEG go: cli mov ax, cs mov ss, ax mov sp, 0ff00h - 12 ; arbitrary num - 512 - disk param size xor ax, ax ; get diskette parameters from int 1eh mov es, ax ; vector (or 78h) push es ; save int table segment mov bx, 78h lds si, es:[bx] ; ds:si points to them mov ax,cs ; mov es,ax ; copy disk parameters mov di, 0ff00h - 12 ; es:di points to dsk_tab push di ; save dsk_tab offset mov cx, 6h ; 12 bytes rep movsw pop di ; restore dsk_tab mov byte ptr es:[di + 4], 18; set sectors pop es ; reset 1eh vector mov word ptr es:[bx], di ; offset mov ax, cs mov word ptr es:[bx+2], ax ; seg mov ds,ax ; load seg regs mov es,ax sti xor ah, ah ; reset FDC with no parameters. xor dl, dl int 13h ; load the setup-sectors directly after the bootblock. ; Note that 'es' is already set up. load_setup: xor dx,dx ; drive 0, head 0 mov cx,0002h ; sector 2, track 0 mov bx,0200h ; address equ 512, in INITSEG mov ax,0200h+SETUPLEN ; service 2, nr of sectors int 13h ; read it jnc ok_load_setup ; ok - continue push ax ; dump error code call print_nl mov bp, sp call print_hex pop ax xor dl, dl xor ax, ax ; reset the diskette int 13h jmp load_setup ok_load_setup: ; Get disk drive parameters, specifically nr of sectors/track IFDEF HARD mov cx, HARD ELSE xor dl,dl mov ax,0800h ; AH equ 8 is get drive parameters int 13h xor ch,ch ENDIF mov cs:sectors,cx mov ax,offset INITSEG mov es,ax ; Print some inane message mov ah,03h ; read cursor pos xor bh,bh int 10h mov cx,9 mov bx,0007h ; page 0, attribute 7 (normal) mov bp,offset msg1 mov ax,1301h ; write string, move cursor int 10h ; ok, we've written the message, now ; we want to load the system (at 10000h) mov ax,offset SYSSEG mov es,ax ; segment of 010000h call read_it call kill_motor mov ax, 0e0dh mov bx, 7 int 10h mov ax, 0e0ah int 10h ; After that we check which root-device to use. If the device is ; defined (; equ 0), nothing is done and the given device is used. ; Otherwise, either /dev/PS0 (2,28) or /dev/at0 (2,8), depending ; on the number of sectors that the BIOS reports currently. mov ax,cs:root_dev or ax, ax ; cmp ax, 0 jne root_defined mov bx,cs:sectors mov ax,0208h ; /dev/ps0 - 1.2Mb cmp bx,15 je root_defined mov ax,021ch ; /dev/PS0 - 1.44Mb cmp bx,18 je root_defined undef_root: jmp undef_root root_defined: mov cs:root_dev,ax ; after that (everyting loaded), we jump to ; the setup-routine loaded directly after ; the bootblock: db 0eah ; jmp SETUPSEG:0 dw 0 dw SETUPSEG ; This routine loads the system at address 10000h, making sure ; no 64kB boundaries are crossed. We try to load it as fast as ; possible, loading whole tracks whenever we can. ; ; in: es - starting address segment (normally 1000h) ; sread dw 1+SETUPLEN ; sectors read of current track head dw 0 ; current head track dw 0 ; current track read_it: mov ax,es test ax,0fffh die: jne die ; es must be at 64kB boundary xor bx,bx ; bx is starting address within segment rp_read: mov ax,es cmp ax,ENDSEG ; have we loaded all yet? jb ok1_read ret ok1_read: mov ax,cs:sectors ; this is the number of sectors we will sub ax,sread ; attempt to read ; mov ax, 1 mov cx,ax ; shl cx,9 ; * 512 bytes add cx,bx ; if overflow, then next segment jnc ok2_read je ok2_read xor ax,ax sub ax,bx shr ax,9 ok2_read: call read_track ; is called with num sectors wanted in al mov cx,ax add ax,sread ; add actual number read to ax cmp ax,cs:sectors jne ok3_read mov ax,1 sub ax,head jne ok4_read inc track ok4_read: mov head,ax xor ax,ax ok3_read: mov sread,ax shl cx,9 add bx,cx jnc rp_read mov ax,es add ax,1000h mov es,ax xor bx,bx jmp rp_read read_track: pusha push ax ; print loading... push bx mov ax, (0e00h + '.') mov bx, 7 int 10h pop bx pop ax mov dx,track mov cx,sread inc cx mov ch,dl mov dx,head mov dh,dl xor dl,dl and dx,0100h mov ah,2 push dx ; save for possible register dump push cx push bx push ax int 13h jc bad_rt add sp, 8 popa ret bad_rt: push ax ; save AX return - ; AH = errore code ; AL = successfully read. call print_all xor ah, ah ; reset FDC xor dl, dl int 13h add sp, 10 popa jmp read_track ; ; print_all is for debugging purposes. ; It will print out all of the registers. The assumtion is that this ; is called from the track read routine, with a stack frame like ; dx ; cx ; bx ; ax ; error ; ret <- sp print_all: mov cx, 5 ; error code + mov bp, sp print_loop: call print_nl cmp cl, 5 jae no_reg mov al, cl mov ax, 0e05h + 'A' - 1 sub al, cl int 10h mov ax, 0e00h + 'X' int 10h mov ax, 0e00h + ':' int 10h print_nl: mov ax, 0e0dh mov bx, 7 int 10h mov ax, 0e0ah int 10h ret no_reg: add bp, 2 call print_hex pop cx loop print_loop ret ; ; print_hex is for debugging purposes. It will print out the hex ; number pointed to by ss:[bp]. ; print_hex: mov cx, 4 ; 4 hex digits mov dx, word ptr [bp] ; load word into dx print_digit: rol dx, 4 ; will rotate, 4 bits will be highest mov ah, 0eh ; nibble, lowest nibble, etc. mov al, dl and al, 0fh add al, '0' cmp al, '9' jbe good_digit add al, 'A' - '0' - 0ah good_digit: mov ah, 0eh int 10h loop print_digit ret ; * This procedure turns off the floppy drive motor, so ; * that we enter the kernel in a known state, and ; * don't have to worry about it later. ; kill_motor: push dx mov dx,3f2h xor al,al out dx, al pop dx ret sectors dw 0 msg1 db 13,10 db "Loading" org 508 root_dev dw ROOTDEV boot_flag: dw 0AA55h _TEXT ends end -- ends -- Build with MASM, link, then exe2bin HARD may be defined with MASM bootsect.asm /DHARD=9; To get it to use the hardcoded sector count. TASM should also work, a86 will work if you change to its conditional define syntax. There are a few glitches there from my 2masm perl script - but it will assemble without warnings. Also note that the code will require more squeezing if more changes are made : there are 2 bytes free. --[0192]-- [0193] daemon@ATHENA.MIT.EDU (Drew Eckhardt) Linux_Activists 12/14/91 15:20 (15 lines) Subject: DEBUG stuff from my post Date: Sat, 14 Dec 1991 13:13:39 -0700 From: Drew Eckhardt To: linux-activists@joker.cs.hut.fi In hind sight, the mov ax, 0201 should be a mov ax, 0301 .... Write, not read. 7:30 am finals sort of have a way of doing things to a guy's mind.... --[0193]-- [0194] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/15/91 13:56 (7 lines) Subject: Is anyone working on pseudo ttys Date: Sun, 15 Dec 91 10:49:00 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Please let me know if someone is working on ptys. pmacdona@sol.uvic.ca Peter.MacDonald@bcsystems.gov.bc.ca --[0194]-- [0195] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/16/91 12:25 (56 lines) Subject: Complete library source available Date: Mon, 16 Dec 1991 19:07:47 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi Well, I just put out the full source to my library for ftp. Parts of it have been available before, but the package "library.tar.Z" should include everything. The library is meant to be installed in /usr/src/lib, but use your own directory structure if you find this impractical. It is further subdivided into more or less (mostly less) logical subdirectories: partly similar to minix, partly depending on where I got the source, and partly just on how it happened to be written :-) There are 4 major sources of library functions and they all have slightly different copyrights, but all should be freely distributable within the linux copyright rules: - Earl Chews estdio (estdio) - The GNU library (malloc, pwd, grp and misc) - me (dirent, unistd, misc) - some PD minix libs (at least termcap) I haven't really ported as much of the GNU libc.a as I would want, as it's not very interesting. Things that should still be done: - time functions. I haven't got the slightest idea about how they work, so the result is accordingly. GNU seems the best bet to find correct functions. - unistd will be slightly changed with the advent of job control. I am assuming that tytso will send diffs, and that some programs will have to be recompiled to correctly work with the new signals (among them gcc). - locale etc. Again gnu seems the best bet. Happily nobody uses locale anyway, so this isn't that much of a problem :-) Additionally I have also sent out a new include.tar.Z - it's mostly bug-corrections and a few new files that the GNU library functions want. Recompiling the library is easy: go to /usr/src/lib, and then do a make in all the subdirectories. The result should be a Libc.a file in /usr/src/lib. Run ranlib on it (ie "ranlib Libc.a"), and you have a new library. Just move it to the library directory (usually /usr/local/lib, but it depends on how you have installed gcc). It might be a good idea to save the old libc.a, in case something has gone wrong. Note that you probably won't really need to compile your own library: this one is a bit better than the original, but the changes shouldn't show up in normal circumstances. Recompilation of the library is usually only needed if you change the kernel heavily (new system calls etc) or if you find better routines for something. This release is more for the "completeness" of source availability for linux. Linus --[0195]-- [0196] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/16/91 23:02 (14 lines) Subject: man pages and ptys Date: Mon, 16 Dec 91 19:19:01 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi I have put together some man pages for some the GNU utilities together with a PD version of man. Ted was kind enough to put it on tsx-11.mit.edu for any interested party. Also, Matthias Lautner has provided me with the source to his minix ptys and select patch to Minix. It still has a bug with losing messages from tty to FS. But I am looking at how hard it is to port his design to Linux. --[0196]-- [0197] daemon@ATHENA.MIT.EDU (Pietro Caselli) Linux_Activists 12/17/91 00:12 (19 lines) Subject: Linux 0.11 is hard to die ! To: linux-activists@joker.cs.hut.fi Date: 17 Dec 91 00:14:28 MET (Tue) From: zaphod@petruz.sublink.org (Pietro Caselli) Yeaaaah ... just like a ninja Linux 0.11 refuses to die. When I logout from bash I login into bash again, and again, and ... quosque tandem Linuxe ! I like tenacity, but ... there is a limit !!! :-) Hmmm ... I passed from gremlins to ninja, with Linux 0.12 I hope not to deal with Godzilla :-) Happy hacking to everyone ... and Merry Christmas. Pietro Caselli | internet: zaphod@petruz.sublink.org | IF YOU MEET THE BUDDHA : pietro@deis33.cineca.it | ON THE ROAD,KILL HIM. Mail : V. Pietro Mattiolo, 4 | 40139 Bologna ITALY | --[0197]-- [0198] daemon@ATHENA.MIT.EDU ("Mark W. Eichin") Linux_Activists 12/17/91 05:23 (26 lines) Subject: getting started... Date: Tue, 17 Dec 91 05:15:12 -0500 From: eichin@ATHENA.MIT.EDU ("Mark W. Eichin") To: linux-activists@joker.cs.hut.fi I'm going to buy myself a 386 system some time after 1992 Jan 1 mostly for Linux hacking (if I can avoid DOS I will -- but I need a machine big enough to do GCC hacking on :-) I'll probably work on getting a socket library working, and probably stuff NOS or some of the other Amateur TCP/IP code behind it. I'm looking to spend between US$2500 and US$3000 on a system. Since this is a good deal of money, I'd like to hear any stories you've got (both good and bad) about buying such systems, and about getting Linux up on them. (Note that I'm soliciting *information* here, not actual systems, though of course you're free to send me email about anything you'd like, within Acceptable Use constraints of the networks you traverse...) Since I'm in the US, stories from over here are probably more useful -- but if you're outside the US and bought something from one of the big mail-order places, I'd appreciate any comments. Please be careful to email directly to me rather than to the list at large; I'll summarize what info I get (so if you've got a story you'd rather not have repeated, please note it in the message.) _Mark_ MIT Student Information Processing Board Cygnus Support --[0198]-- [0199] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/17/91 10:02 (27 lines) Subject: Linux 0.11 is hard to die ! Date: Tue, 17 Dec 1991 16:46:33 +0200 From: Ari Lemmke To: linux-activists@joker.cs.hut.fi In-Reply-To: Pietro Caselli's message of 17 Dec 91 00:14:28 MET (Tue) <9112170014.AA00046@petruz.sublink.ORG> >Yeaaaah ... just like a ninja Linux 0.11 refuses to die. When I logout >from bash I login into bash again, and again, and ... quosque tandem Linuxe ! That's because kernel init has while loop like (hey, that's pseudo-code, not the real one!): while (1) { exec("/bin/sh"); sync(); } So actually that was, what I did for 0.10 '/etc/init', because atleast my shell is (maybe with 0.11 was) constantly crashing. So it is safe to power off after first logout. arl --[0199]-- [0200] daemon@ATHENA.MIT.EDU (Michael K. Johnson) Linux_Activists 12/17/91 14:34 (20 lines) Subject: compress/out of memory Date: Tue, 17 Dec 91 13:13:35 CST From: johnsonm@stolaf.edu (Michael K. Johnson) To: Linux-activists@joker.cs.hut.fi This may have already been discussed, but I can't find it: uncompress gives me "out of memory" "segmentation violation" errors on some files, for instance uniq.Z as found on tsx-11. I am running .11 on a 386sx-16. Anyone have any ideas? I had no problems with compress under .10... Also, just a note to whoever wants to know -- I made a new filesystem with the mkfs distributed with .11, and used the -c flag, which was supposeed to eliminate all my hd i/o errors when I was through. Now, it may well be my hard drive, but I don't know. If anyone working on filesystem stuff wants any details, I will be glad to provide them. michaelkjohnson johnsonm@stolaf.edu I don't do .sig's --[0200]-- [0201] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/17/91 14:47 (21 lines) Subject: Re: compress/out of memory Date: Tue, 17 Dec 91 14:30:10 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: johnsonm@stolaf.edu Cc: Linux-activists@joker.cs.hut.fi In-Reply-To: Michael K. Johnson's message of Tue, 17 Dec 91 13:13:35 CST, Reply-To: tytso@athena.mit.edu Date: Tue, 17 Dec 91 13:13:35 CST From: johnsonm@stolaf.edu (Michael K. Johnson) This may have already been discussed, but I can't find it: uncompress gives me "out of memory" "segmentation violation" errors on some files, for instance uniq.Z as found on tsx-11. One of the things that will cause that is a corrupted .Z file. Are you sure you FTP'ed uniq.Z with the binary mode set? It is possible that uniq.Z on tsx-11 is corrupted, but I would rather doubt it, since I've been able to uncompress it using a unix zcat. - Ted --[0201]-- [0202] daemon@ATHENA.MIT.EDU (Michael K. Johnson) Linux_Activists 12/17/91 16:22 (20 lines) Subject: kermit Date: Tue, 17 Dec 91 15:13:15 CST From: johnsonm@stolaf.edu (Michael K. Johnson) To: Linux-activists@joker.cs.hut.fi Regarding my mailing a few hours ago, apparently my "uniq.Z" was corrupted. However, this is worth noting, because it is not corrupted on tsx-11, where I got it, and it is not corrupted on the unix system I ftp'd to either. I transfered it to my system using kermit, and it was apparently then that it was corrupted. I used kermit -i -s uniq.Z to send the file, and thought that image or ascii is determined by the sender. I *was* using the new kermit. Is this a misunderstanding, a bug, or a feature? thanks much! michaelkjohnson johnsonm@stolaf.edu I don't do .sig's --[0202]-- [0203] daemon@ATHENA.MIT.EDU (Ken Raeburn) Linux_Activists 12/17/91 17:04 (26 lines) Subject: C++? Date: Tue, 17 Dec 91 16:50:49 -0500 From: raeburn@ATHENA.MIT.EDU (Ken Raeburn) To: linux-activists@joker.cs.hut.fi Has anyone tried bringing up g++ on linux? On a related note, are any other gcc2 developers or testers reading this list, or should I start hacking on it when I get a machine (probably in January or February)? Ken P.S. If I understand correctly, c386 works on the small-memory machines but doesn't handle ANSI C. Has anyone tried using Ron Guilmette's "unprotoize" program? It includes a set of patches to gcc 1.something (which have also been incorporated in gcc2) and a program that can rewrite source files to add or remove prototypes and change function definition forms. A converted version of 0.11 might let the c386 users get enough work done to get the VM system up to handling gcc. It'd just require someone who can use gcc on their machine to do the conversion. (I *don't* advocate making converted versions of every release, or even necessarily more than one. If being able to use c386 is the goal, rather than getting linux up so the VM system can be worked on, then c386 should just be fixed.) I'd volunteer to do it myself, if I had a machine to work on, and if I knew someone would do the VM work...unfortunately, neither is the case right now. --[0203]-- [0204] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/17/91 18:00 (81 lines) Subject: one bug, possible other problems Date: Wed, 18 Dec 1991 00:48:24 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi > This may have already been discussed, but I can't find it: > uncompress gives me "out of memory" "segmentation violation" > errors on some files, for instance uniq.Z as found on tsx-11. > I am running .11 on a 386sx-16. Anyone have any ideas? I had > no problems with compress under .10... As already has been noted, this can be (and in this case seems to have been) due to corrupted Z-files. However, if anybody else sees the "out of memory" error, even though there should be enough memory there is always another possibility: if your "/etc/passwd" (or possibly "/etc/group") files are not in the right format, it triggers a bug in the old library which will use up all your memory. Great fun. Check that all entries in your "/etc/passwd" have the right nr of colons (even if there is no shell name, the last colon is supposed to exist). This same bug shows up in all programs that use the "getpwent()" library call with the old lib: ls -l, chown et.al. Easy to correct the /etc/passwd file, and then this should go away. Then on to a /real/ bug, which needs kernel recompilation, but isn't very noticeable: the execve system call incorrectly clears all signal handler addresses. It should leave the "SIG_IGN" addresses as is: nohup etc programs depend on that. The fix is easy: linux/fs/exec.c: do_execve(), right after the comment "point of no return" there is the for-loop that clears the sa.sa_handler entries. Change it from (something like) for (i=0 ; i<32 ; i++) current->sa[i].sa_handler = NULL; to for (i=0 ; i<32 ; i++) if (current->sa[i].sa_handler != SIG_IGN) current->sa[i].sa_handler = NULL; Additionally you need to include signal.h at the top of the file. (Note that this "patch" may not be exact - this is from memory). > [ kermit send/receive binary ] I use kermit to receive files, and even for terminal emulation, now that linux correctly handles the ISIG flag. I always "set filetype binary" in both ends, but don't know if it's really necessary (but it's easy to make a ".kermrc" file in your home-directory to do these kinds of setups automatically). I'd suggest you do likewise: then I know it works. > Has anyone tried bringing up g++ on linux? [ gcc2 and c386 ] I've been thinking about this (hi tytso :), and I will port gcc-2.0 (or 1.99) as soon as it is available. That should contain g++. Probably in january-february says tytso. During the holiday, I will implement VM (real paging to disk): I've been going over the algorithms in my head, and I think it can be done relatively easily, so hopefully we can scrap the c386 compiler (sorry, blum). The paging algorithm will at least in the beginning be extremely simple: no LRU or similar, just a simple "get next page in the VM-space". Note that VM isn't (even with a good algorithm) a "holy grail" - I don't want to be on the same machine when someone uses gcc in 2M real mem. Slooooowww. 4M will definitely be recommended even with VM, and 1M machines won't work with linux even with the VM (you /do/ need some real memory too :-). I have this small question when it comes to the swap-space setup - two different possibilities: 1 - a swap-device of it's own (ie own partition) 2 - file-system swap-area. There are a number of pros and cons: (1) is faster, easier to implement, and will need no changes when the filesystem eventually is changed to accept >64M etc. (2) has the good side that it means that it would be easy to change the size of the swap-area, but if something bad happens, it could probably trash the filesystem easily. I'll probably implement only (1) for now, but I'd like to hear what you say (and ignore it :-). Linus --[0204]-- (nref = [0207]) [0205] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/17/91 18:16 (18 lines) Subject: compress and VM Date: Tue, 17 Dec 91 15:08:24 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi I have seen a small problem with compress. uncompress *.Z fails to uncompress some of the files specified. Failure prints some message like EINVAL or something (-; sorry, its been weeks) But using uncompress afterwards on the individual file works. I wouldn't mention it, but for the compress problems posted. Certainly the easiest swap to disk to implement is the best, but using fdisk can be traumatic. Perhaps the way MS Windows (shudder) does it would be acceptable. ie. use the file system but set the swap size at the boot up time (a number in the kernel ala root device?) and allocate a single large file. Thus changing the swap size requires only a reboot - after modifying the kernel. --[0205]-- [0206] daemon@ATHENA.MIT.EDU (Jim Winstead Jr.) Linux_Activists 12/17/91 18:52 (31 lines) Subject: Re: compress, and other stuff Date: Tue, 17 Dec 91 15:40:55 PST From: "Jim Winstead Jr." To: linux-activists@joker.cs.hut.fi Peter MacDonald says: > I have seen a small problem with compress. uncompress *.Z fails to > uncompress some of the files specified. Failure prints some > message like EINVAL or something (-; sorry, its been weeks) I've seen this problem, too, but it's a little more consistent than one might normally think: compress fails (EINVAL) on every other if passed a wildcarded argument. That is "uncompress *Z" will give a EINVAL error on every other file it tries. > But using uncompress afterwards on the individual file works. It also works to repeat the command, answering yes to the questions it asks, as it will on try and decompress the files that have been decompressed. It still misses every other file of the repeated command, though. Perhaps it's a bug in the port of compress? Also, I've ported unzip, zoo, (un)yabba and a few other things to Linux. Any interest in putting these on tsx-11? They were all pretty painless, but it might save some people the trouble of compiling them. --- Jim Winstead Jr. (CSci '95) 3 "We are only immortal Harvey Mudd College 3 for a limited time.. jwinstea@jarthur.Claremont.EDU 3 when we are young." Disclaimer: Mine, not theirs! 3 -Rush, Dreamline --[0206]-- [0207] daemon@ATHENA.MIT.EDU ("Mark W. Eichin") Linux_Activists 12/17/91 19:02 (29 lines) Subject: Re: one bug, possible other problems (Swapping) Date: Tue, 17 Dec 91 18:52:53 -0500 From: eichin@ATHENA.MIT.EDU ("Mark W. Eichin") To: Linus Benedict Torvalds Cc: Linux-activists@joker.cs.hut.fi In-Reply-To: [204] >> I have this small question when it comes to the swap-space setup - two >> different possibilities: >> 1 - a swap-device of it's own (ie own partition) >> 2 - file-system swap-area. I'd argue for both, but do swap partition first because it'll be done sooner that way. Under SunOS, you get your swap partition which is big enough for normal work (and I think is faster but I could be wrong) and then when you need more space for a special project, you just create a big file and swap from that until next reboot. One of the biggest losses with the NeXT machine (at least up to OS 2.1) is that it uses in-file-system swapping. When disk space is tight, the OS heads for Mars... this is exacerbated by the fact that NeXT OS can grab more space dynamically, but never gives it back, and *can't control how much it will try to grab*. A good example of how a well intentioned design can turn around and bite you. _Mark_ MIT Student Information Processing Board (Another interesting feature of SunOS is the "tmpfs" temporary file system... it's like a ram disk, but it's in VM so it can get swapped out. It makes a rather fast /tmp since it doesn't have any of the guaranteed write-to-disk semantics of UFS, and in fact any actual disk writes get done "later". The problem is when you've got something both memory *and* disk intensive using it.) --[0207]-- (pref = [0204]) [0208] daemon@ATHENA.MIT.EDU (Tony Travis) Linux_Activists 12/18/91 06:23 (34 lines) Subject: Re: kermit Date: Wed, 18 Dec 1991 10:35:00 +0000 From: Tony Travis To: Linux-activists@joker.cs.hut.fi Michael, In my experience, both ends need to be set to 'i'mage (binary) mode with the single exception of MSDOS kermit which treats all files the same. Tony ------------------------------------------------------------------------------- Dr. A.J.Travis | Rowett Research Institute, | Greenburn Road, Bucksburn, Aberdeen, | AB2 9SB. UK. tel 0224-712751 > > Regarding my mailing a few hours ago, apparently my "uniq.Z" was corrupted. > However, this is worth noting, because it is not corrupted on tsx-11, where > I got it, and it is not corrupted on the unix system I ftp'd to either. I > transfered it to my system using kermit, and it was apparently then that it > was corrupted. I used > kermit -i -s uniq.Z > to send the file, and thought that image or ascii is determined by the > sender. I *was* using the new kermit. Is this a misunderstanding, a bug, > or a feature? > > thanks much! > > michaelkjohnson > johnsonm@stolaf.edu > I don't do .sig's > --[0208]-- [0209] daemon@ATHENA.MIT.EDU (John T Kohl) Linux_Activists 12/18/91 18:43 (13 lines) Subject: GNU find 2.1 on tsx-11 Date: Wed, 18 Dec 91 15:25:23 PST To: linux-activists@joker.cs.hut.fi From: John T Kohl Reply-To: jtkohl@cs.berkeley.edu You'll find GNU find 2.1 and associated tools, a README file, and diffs from the GNU distribution in tsx-11.mit.edu:/pub/linux/binaries/find-2.1/ [yes, I know that gnu find 1.2 is also there, but I figured why not use the latest & greatest] John --[0209]-- [0210] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/19/91 01:39 (253 lines) Subject: A FAQ is coming... Date: Thu, 19 Dec 91 07:29:21 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! Following is a FAQ-compilation (most credits to Linus) for Linux. Mail me, if you like it, and mail me, if you dislike it or have any ideas on changing this. Thanks in advance, Robert Blum QUESTION: What is linux? ANSWER: Linux is a small unix for 386-AT computers, that has the added advantage of being free. It is still in beta-testing, but is slowly getting useful even for somewhat real developement. QUESTION: Does it run on my computer? ANSWER: Linux has been written on a clone-386, with IDE drives and a VGA screen. It should work on most similar setups. The harddisk should be AT-standard (ie not SCSI, ESDI), and the system must be ISA. Otherwise the requirements seem relatively small: a 386 (SX, DX or any 486). The current version (0.10) needs a colour screen adapter, but this is not the case with the next version. It needs at least 2M to run, and 4M is definitely a plus. It can happily use up to 16M (and more if you change some things). QUESTION: Will linux run on a PC or 286-AT? If not, why? ANSWER: Linux uses the 386 chip protected mode functions extensively, and is a true 32-bit operating system. Thus x86 chips, x<3, will simply not run it. QUESTION: Does linux do paging? Can I have virtual memory on my small machine? ANSWER: Linux does use the 386 paging unit, but currently only for memory management. No use of disks as expansion RAM. This is one of the things that will be implemented sometime in the (far?) future. Linux also uses the paging unit to share pages between several processes after a fork: thus it needs less memory. However, almost all the user programs available for linux are GNU software, which want gobs and gobs of memory. This is the reason at least 4M is recommended: GNU cc (gcc) simply won't run in less. QUESTION: Can I have tasks spanning the full 4GB of addressable 386 memory? No more 64kB limits like in coherent or standard minix? ANSWER: Linux does limit the task-size, but at a much more reasonable 64MB (MEGA-byte, not kilos), so bigger programs are no problem. QUESTION: Does the bigger program sizes mean I can run X? ANSWER: X is not ported to linux, and though I hope it will be some day, I cannot guarantee it. It's big, and wants a lot from the system. QUESTION: Where can I get linux? Is there a mailserver? ANSWER: Linux can be gotten by anonymous ftp from nic.funet.fi (128.214.6.100): directory /pub/OS/Linux Tupac-Amaru.Informatik.RWTH-Aachen.DE (137.226.112.31): directory /pub/msdos/replace tsx-11.mit.edu (18.172.1.2): directory /pub/linux ftp.eecs.umich.edu (141.212.99.7): directory linux You might want to check out which of these is the most up-to-date. If you don't have ftp-capability, you are in trouble. You might try mailing "mailserver@nic.funet.fi" with "help" in the body of the mail. QUESTION: Is there a newsgroup or mailing-list about linux? Where can I get my questions answered? How about bug-reports? ANSWER: There is a mailing list set up at the address 'Linux-activists@niksula.hut.fi'. To join, mail a request to 'Linux-activists-request@niksula.hut.fi'. DO NOT mail "I want to [un]subscribe" to the mailing-list, use the request-address. Questions and bug-reports can be sent either to the mailing-list or to "torvalds@kruuna.helsinki.fi", depending on which you find more appropriate. QUESTION: I got the minix-demo, but it won't boot. Linux boots from floppy. What's wrong? ANSWER: You probably wrote the minix demo to a 1.44M disk, which (for some unfathomable reason) doesn't work. The minix demo wants a 720kB or 1.2M disk. QUESTION: The minix-demo boots all right, but doesn't seem to recognize my second harddisk. What's up? ANSWER: The minix-demo does support a second harddisk, but there are no special files made for it, and the minix demo doesn't include the "mknod" command. Mount the linux root-floppy, and use the devices on that. QUESTION: How can I be sure I won't be writing over anything important? I have to use DOS in on my machine, and I don't want to lose any files. ANSWER: Back up everything. Just in case. Then, write some easily recognizable pattern to the partition you have reserved for linux, using some DOS tool. You can then use "cat /dev/hdX" under minix to examine which of the partitions you used. QUESTION: Minix mkfs doesn't accept the size I give the device, although I double-checked with fdisk, and it's correct. ANSWER: Be sure you give the size in BLOCKS, ie 1024 bytes, not sectors. Also, make doubly certain that you have the correct partition. QUESTION: I used the minix mkfs to make a filesystem on /dev/hd3 after having checked that this was indeed the partition I had reserved. Minix mounts the new partition ok, but linux doesn't. What gives? ANSWER: In some cases partitions are numbered differently under minix and linux. This seems to correlate to the FDISK version you have used. /dev/hd3 under minix may be /dev/hd2 under linux etc. There are a few rules about this: /dev/hd0 and /dev/hd5 are always the same under linux and minix. DO NOT USE THEM, they are the whole raw disk, not partitions. Also if a partition is on drive 1 under minix (ie /dev/hd1-4), it is drive 1 under linux as well. QUESTION: I mounted the linux filesystem, and copied the files from the root-disk to the harddisk. Now I cannot find them any more, and somethimes linux dies with a "panic: trying to free unused inode". ANSWER: You have probably forgot to sync before rebooting. Linux, like all unices, use a "buffer cache" to speed up reads and writes to disk. On a machine that has enough memory, this buffer-cache is 1.5MB, and if you forget to sync before exiting, it may not be fully written out to disk. Re-mkfs and re-install (or try to use the preliminary fsck, but remeber that although fsck tries to correct the faults it finds, it may fail.) QUESTION: the mtools package on the root-disk won't work. I get an ENOENT error message for all devices. ANSWER: mtools needs to be told which device to look for. Use 'ln' or 'mknod' to create a sepcial file called "/dev/dosX", where X is A, B or C. This file should point to the device you want to read. QUESTION: Turbo (Microsoft) Assembler won't compile the Linux boot code. In fact, some of the opcodes in these files look completely unfamiliar. Why? ANSWER: The Linux boot codes are written in Bruce Evans' minix assembler, which has the same opcodes as the original minix assembler. There are a few differences between these and normal DOS assemblers: - No segments - everything is in the same segment (at least in the bootsectors and setup, as they don't use the .data segments) - mov[b|w|l] are shorter versions of mov ax,[byte|word|long] ptr [XXX]. This is how unix assemblers normally give the size (byte, word or long). Gas has similar constructs. - There is no "jmp short", the opcodes are "j" for a short jump and "jmp" for a long one. - "jmpi" is a jump with a segment:offset pair. I don't know how this is written in DOS assembly. QUESTION: While running du I get "Kernel panic: free_inode: bit already cleared". Also, du produces a ENOENT error for all the files in certain of my directories. What's going on? ANSWER: These are both consistent with a bad file-system. That's relatively easy to produce by not syncing before rebooting, as linux usually has 1.5MB of buffer space held in memory (unless you have <=4M RAM, in which case the buffers are only about 0.5MB). Also linux doesn't do anything special about the bit-map blocks, and as they are used often, those are the thing most likely to be in memory. If you reboot, and they haven't been written to disk ... I'm afraid that as long as there is no fsck for linux there is no way to correct the matter (unless you have minix and can run minix fsck), and the only thing to do is to reinstall the filesystem from scratch (ie do a mkfs from the minix demodisk and reboot from the original linux-floppy). A sync is done only every 30 seconds normally (standard unix practice), so do one by hand (some people think you should do 3 syncs after each other, but that's superstition), or by logging out from the startup-shell, which automatically syncs the system. Unmounting a filesystem also syncs it (but of course you can never unmount root). Another (sad) possibility is that you have bad blocks on your disk. Not very probable, as they would have to be in the inode-tables, just a couple of blocks in size. Again there aren't programs available to read a disk for bad sectors and put them in some kind of "bad-sector-file". On IDE drives this is no problem (bad sectors are automatically mapped away). QUESTION: What is the "em" binary? ANSWER: Em is micro-EMacs (probably version 3.10). QUESTION: I seem to be unable to compile anythong with gcc. Why? ANSWER: If you have only 2 MB RAM, gcc will die silently without compiling anything. You must have at least 4 MB to do compilations QUESTION: I'm using a program that uses signal handlers which are installed using sigaction() with the SA_NOMASK, and they get a general protection error right after the signal handler tries to return. What's going wrong? ANSWER: You are using a libc.a that has an out-of-date signal.o and sig_restore.o file, and they don't know how to deal with SA_NOMASK. (The one in gccbin.tar.Z is out-of-date.) You can obtain the newer signal.c from the unistd.tar.Z file, but don't use the associated sig_restore.c from there; the FTP sites should have a separate sig_restore.c which is up to date. While you're at it, you should also get an updated crt0.c file as well, and install your new crt0.o and libc.a in /usr/lib. (This answer will likely change in the near future, since there are plans to change the format of the signal trampoline code yet again.... but for now, this should be an accurate description of how things stand now.) QUESTION: gcc complains about not finding crt0.o and the system include files What am i doing wrong ? ANSWER: The include files normal place is in /usr/include. libc.a and *.a should be in /usr/lib --[0210]-- [0211] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/19/91 01:42 (143 lines) Subject: And another version of the INFO sheet Date: Thu, 19 Dec 91 07:34:10 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! Here is the re-edited version of the Linux info sheet. Thank you for all your replies, especially to the guy who sent me the diff. (Sorry, forgot your name) The list of groups it will be posted to has changed to: comp.binaries.ibm.pc.d comp.os.coherent comp.os.mach comp.os.minix comp.os.misc comp.unix.sysv386 comp.unix.programmers gnu.misc.discuss If you haven't any further additions or corrections, I'll send out the INFO sheet thursday, the 26th of december. Have a merry Xmas! Robert Blum LINUX INFORMATION SHEET (last updated 19 Dec 1991) 1. WHAT IS LINUX 0.11 LINUX 0.11 is a freely distributable UNIX clone. It implements a subset of System V and POSIX functionality. LINUX has been written from scratch, and therefore does not contain any AT&T or MINIX code--not in the kernel, the compiler, the utilities, or the libraries. For this reason it can be made available with the complete source code via anonymous FTP. LINUX runs only on 386/486 AT-bus machines; porting to non-Intel architectures is likely to be difficult, as the kernel makes extensive use of 386 memory management and task primitives. Version 0.11 is still a beta release, but it already provides much of the functionality of a System V.3 kernel. For example, various users have been able to port programs such as bison/flex without having to modify code at all. Another indication of its maturity is that it is now possible to do LINUX kernel development using LINUX itself and freely-available programming tools. 2. LINUX features - System call compatible with a subset of System V and POSIX - Full multiprogramming (multiple programs can run at once) - Memory paging with copy-on-write - Demand loading of executables - Page sharing of executables - ANSI compliant C compiler (gcc) - A complete set of compiler writing tools (bison as yacc-replacement, flex as lex replacement) - The GNU 'Bourne again' shell (bash) - Micro emacs - most utilities you need for development (cat, cp, kermit, ls, make, etc.) - Over 200 library procedures (atoi, fork, malloc, read, stdio, etc.) - Currently 4 national keyboards: Finnish/US/German/French - Full source code (in C) for the OS is freely distributable - Full source code of the tools can be gotten from many anonymous ftp sites (Almost the entire suite of GNU programs has been ported to Linux.) - Runs in protected mode on 386 and above - Support for extended memory up to 16M on 386 and above - RS-232 serial line support with terminal emulation, kermit, zmodem, etc. - Supports the real time clock 3. HARDWARE REQUIRED - A 386 or 486 machine with an AT-bus. (EISA will probably work, also, but you will need an AT-bus hard disk controller.) Both DX and SX processors will work. - A hard disk implementing the standard AT hard disk interface-- for example, an IDE drive. SCSI drives are not supported yet. - A high-density disk drive--either 5.25" (1.2MB) or 3.5" (1.44MB). - At least 2 megabytes of RAM. (LINUX will boot in 2 Mb. To use gcc at least 4 MB are required.) - Any video card of the following: Hercules,CGA,EGA,VGA In addition, LINUX supports - Up to two serial lines - A real time clock 4. PARTIAL LIST OF UTILITIES INCLUDED IN OR AVAILABLE FOR LINUX 0.11 - The MTOOLS package (reading/writing to DOS filesystems) - The complete GNU filetools (ls, cat, cp, mv, ...) - The GNU C compiler with GNU assembler, linker, ar, ... - bison - flex - rcs - pmake (BSD 4.3 Reno/BSD 4.4 make) - kermit - Micro emacs - less - mkfs - fsck - mount/umount 5. LINUX BINARIES The LINUX binaries and sources are available at three anonymous FTP sites. These are: nic.funet.fi:/pub/OS/Linux tsx-11.mit.edu:/pub/linux tupac-amaru.informatik.rwth-aachen.de:/pub/msdos/replace 6. LEGAL STATUS OF LINUX Although LINUX is supplied with the complete source code, it is copyrighted software. Unlike MINIX, however, it is available for free, provided you obey to the rules specified in the LINUX copyright. 7. NEWS ABOUT LINUX Since LINUX's introduction to the public there has been a rapidly growing mailing list, "linux-activists@niksula.hut.fi". To subscribe to this list, mail to "linux-activists-requests@niksula.hut.fi". If the traffic in this lists increases further, there are plans to swap ( at least partially ) over to comp.os.misc, so watch out for any LINUX articles in this group. For the current status of LINUX, do "finger torvalds@kruuna.helsinki.fi". 8. FUTURE PLANS Work is underway on LINUX version 1.0, which will close some of the gaps in the present implementation. Various people are currently working on: - Math support/fp emulation in the kernel - Page swapping (since paging is already implemented) - A virtual filesystem layer - STREAMS - POSIX job control (This is already alpha and will probably be out with Version 0.12.) - init/getty/login - symbolic links - Interprocess communication - IEEE POSIX P1003.1 / P1003.2 compatibility - SCSI support If you want to help, join the mailing list. --[0211]-- [0212] daemon@ATHENA.MIT.EDU (Linus Benedict Torvalds) Linux_Activists 12/19/91 13:25 (41 lines) Subject: VM, version 0.12 Date: Thu, 19 Dec 1991 19:51:45 +0200 From: Linus Benedict Torvalds To: Linux-activists@joker.cs.hut.fi /\ / \ / \ / \ Seasons Greetings / \ || Ho, ho ho, and a happy X-mas/chanukah/whatever to you all. I'm probably mailing to a lot of non-listening mail-boxes, but who cares. This is a warning for all you out there making changes to the linux kernel: if you want your changes to be in 0.12, I want them by early January (5th-10th ta the latest). As it looks now, 0.12 will be out about 15th of January, and will contain at least these new things: - POSIX job control (by tytso, alpha-release available already) - VM (by me - I'll probably make alphas available after X-mas) - Various small corrections (by me, tytso, jtkohl, drew etc) - Anything else people send me. I got VM working today (not bad in two days if I may say so :-), but haven't really tested extensively. I tried some compilations (I remade uemacs) on a 2M machine (or rather a 8M machine, of which Linux sees only 2M), and it worked (gcc, make, bash etc in memory ar the same time), albeit slowly. There are probably still problems, but it seems VM will definitely be in 0.12. Note that the earlier I get your fixes, the easier it will be to implement them all: if I get many fixes 0.12 may be a little late, so the January 15th date isn't really fixed. Also, after releasing 0.12 I'll probably have to study a bit harder than I did this autumn (which isn't hard per se :-), which may mean that the new releases won't be coming once per month or so any more. Hopefully 0.12 will be good enough to use. Linus "Ugly X-mas trees are my speciality" Torvalds --[0212]-- [0213] daemon@ATHENA.MIT.EDU (Pietro Caselli) Linux_Activists 12/20/91 00:07 (23 lines) Subject: Re: Re: compress, and other stuff To: linux-activists@joker.cs.hut.fi Date: 18 Dec 91 19:22:50 MET (Wed) From: zaphod@petruz.sublink.org (Pietro Caselli) > From: "Jim Winstead Jr." > > Also, I've ported unzip, zoo, (un)yabba and a few other things to > Linux. Any interest in putting these on tsx-11? They were all pretty > painless, but it might save some people the trouble of compiling them. > --- I ported zip 1.0 if there is interest I'll post it on funet. ( Zip1.0 works great, I had just to discard encryption/decription from it. ) Ciao. Pietro Caselli | internet: zaphod@petruz.sublink.org | IF YOU MEET THE BUDDHA : pietro@deis33.cineca.it | ON THE ROAD,KILL HIM. Mail : V. Pietro Mattiolo, 4 | 40139 Bologna ITALY | --[0213]-- [0214] daemon@ATHENA.MIT.EDU (Pietro Caselli) Linux_Activists 12/20/91 00:09 (49 lines) Subject: Re: one bug, possible other problems To: linux-activists@joker.cs.hut.fi Date: 18 Dec 91 19:18:14 MET (Wed) From: zaphod@petruz.sublink.org (Pietro Caselli) > > Has anyone tried bringing up g++ on linux? [ gcc2 and c386 ] Hmmmm, I'd like to test myself on gcc2 but ... where can I find it ? ( I asked archie but got no response :-( ) > I have this small question when it comes to the swap-space setup - two > different possibilities: > > 1 - a swap-device of it's own (ie own partition) > > 2 - file-system swap-area. > > There are a number of pros and cons: (1) is faster, easier to implement, > and will need no changes when the filesystem eventually is changed to > accept >64M etc. (2) has the good side that it means that it would be > easy to change the size of the swap-area, but if something bad happens, > it could probably trash the filesystem easily. I'll probably implement > only (1) for now, but I'd like to hear what you say (and ignore it :-). Ok, start discarding my hints :-). Solution 1) is the best, is faster, cleaner and easyer to mantain. But with the fu###ing limitation of four partition for HD it gives to me a lot of trouble. ( And think to many other ) Now I've a Dos partition, 2 Minix partitions ( root and /usr ) and a Linux partition. I can't add any more :-( When Linux gets older, i.e when it'll have virtual consoles, pttys etc I'll be pleased to kill minix but ... I know It needs time. So, why not add both 1) and 2) ? ( Christmass holidays are long, I'll go skiing but I think you'll have plainty of time to make both :-) ) > Linus Ciao. Pietro Pietro Caselli | internet: zaphod@petruz.sublink.org | IF YOU MEET THE BUDDHA : pietro@deis33.cineca.it | ON THE ROAD,KILL HIM. Mail : V. Pietro Mattiolo, 4 | 40139 Bologna ITALY | --[0214]-- [0215] daemon@ATHENA.MIT.EDU (Hakkarainen Kimmo) Linux_Activists 12/20/91 06:12 (20 lines) Subject: less version 177 From: Hakkarainen Kimmo To: linux-activists@joker.cs.hut.fi (Linux activists) Date: Fri, 20 Dec 91 12:59:21 EET Hello, I found sources for less 177 in garbo.uwasa.fi. I compiled it and noticed it being better than the version we already have (0.97). I will put both sources and binaries in nic.funet.fi. I hope those will show up in couple of days. BTW less 177 supports editor-escape (or what should it be called) and I changed the default editor to be emacs not "vi". If you have any questions, please feel fre to ask me. PS. Merry christmas to everyone. -- Kimmo Hakkarainen (h108373@cc.tut.fi) Fire, walk with me. --[0215]-- [0216] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/20/91 10:39 (22 lines) Subject: less version 177 Date: Fri, 20 Dec 1991 17:29:19 +0200 From: Ari Lemmke To: linux-activists@joker.cs.hut.fi In-Reply-To: Hakkarainen Kimmo's message of Fri, 20 Dec 91 12:59:21 EET <9112201059.AA09690@cc.tut.fi> Kimmo Hakkarainen writes: >I found sources for less 177 in garbo.uwasa.fi. I compiled it and >noticed it being better than the version we already have (0.97). >I will put both sources and binaries in nic.funet.fi. I hope >those will show up in couple of days. Available in nic.funet.fi:/pub/OS/Linux/bin less-177.bin.tar.Z less-177.src.tar.Z I really like version numbers within names ... arl PS. merry Xmas ... --[0216]-- [0217] daemon@ATHENA.MIT.EDU (Theodore Ts'o) Linux_Activists 12/20/91 11:14 (26 lines) Subject: Re: one bug, possible other problems Date: Fri, 20 Dec 91 11:03:59 -0500 From: tytso@ATHENA.MIT.EDU (Theodore Ts'o) To: linux-activists@joker.cs.hut.fi In-Reply-To: Pietro Caselli's message of 18 Dec 91 19:18:14 MET (Wed), Reply-To: tytso@athena.mit.edu X-Mailer: W-MAIL 3.64/MINIX (11/13/90) Date: 18 Dec 91 19:18:14 MET (Wed) From: zaphod@petruz.sublink.org (Pietro Caselli) Solution 1) is the best, is faster, cleaner and easyer to mantain. But with the fu###ing limitation of four partition for HD it gives to me a lot of trouble. ( And think to many other ) Now I've a Dos partition, 2 Minix partitions ( root and /usr ) and a Linux partition. I can't add any more :-( When Linux gets older, i.e when it'll have virtual consoles, pttys etc I'll be pleased to kill minix but ... I know It needs time. One solution to this which I've been kicking about, but haven't had time to implement, is run-time configurable partitions. So you could set up a 96 meg partition for Linux (at least as far as the MS-LOSS partitioning scheme is concerned) and have /dev/hd3 refer to it. Then in /etc/rc, you call a program which configures /dev/hd16 to be the last 32 megs of /dev/hd3, using ioctl's. Turn on swapping on /dev/hd16, and you're all set. - Ted --[0217]-- [0218] daemon@ATHENA.MIT.EDU (Robert Blum) Linux_Activists 12/20/91 14:05 (17 lines) Subject: gcc barfs at string.h Date: Fri, 20 Dec 91 19:56:31 +0100 From: blum@cip-s01.informatik.rwth-aachen.de (Robert Blum) To: linux-activists@joker.cs.hut.fi Hi Linuxers! While I was alpha-testing VM, the following occured: I compiled the kernel, and the first file to include string.h wouldn't compile at the line extern int __res __asm("ax"); (just quoted from mind, may not be exact, can be found first with strcmp) this gives a "parse error before )", and later on, an undefined __res Any clues what this could be? Is it me or is it a broken gcc or is it VM? Thanks for your help, and have a merry christmas Robert "blow it all" Blum --[0218]-- [0219] daemon@ATHENA.MIT.EDU (Bruce Evans) Linux_Activists 12/20/91 22:17 (17 lines) Subject: Re: less version 177 Date: Sat, 21 Dec 91 03:24:10 +1100 From: Bruce Evans To: linux-activists@joker.cs.hut.fi >I found sources for less 177 in garbo.uwasa.fi. I compiled it and >noticed it being better than the version we already have (0.97). I think version 0.97 is much better than 177 :-), mainly because my version of it has hacks to read compressed files. I seem to remember that the author of less strongly objected to such impurities, but when your disk has a lot of compressed files it's nice to be able to say "less *" and not get garbage or useless warnings about binary files. I looked at putting decompression in version 177 but the changes in buffering stdin made things too difficult considering that 0.97 already works. Bruce --[0219]-- [0220] daemon@ATHENA.MIT.EDU (Jim Winstead Jr.) Linux_Activists 12/20/91 23:01 (31 lines) Subject: Re: less v1.77 Date: Fri, 20 Dec 91 19:50:59 PST From: "Jim Winstead Jr." To: linux-activists@joker.cs.hut.fi You can set up a small shell script to view compressed files via less, as well. I have one called zless that is simply 'zcat $* | less', and it works wonders. Does the less v1.77 available include regular-expression searching? When I tried compiling less v1.77, I found that I had to replace the included regex.[ch] with ones from another GNU utility. Speaking of GNU utilities, someone mentioned making find 2.1 available, because it was the "latest and greatest". I looked on prep.ai.mit.edu, the official distribution point of GNU stuff, and it has find-3.2.tar.Z. Is there any interest in getting this ported to Linux? Has anyone had any luck porting gawk more successfully? The current port fails to pass the test programs included with the current GNU distribution, and when I've tried to build that version (3.?), it fails on eval.c due to error 32 or something nice and cryptic like that. I would assume it's trying to compile floating-point stuff, and since I lack a math coprocessor.... My main interest in getting a (better-)working gawk is to use awf as a replacement for nroff, at least until some maniac ports gtroff (which requires porting g++ first :) --- Jim Winstead Jr. (CSci '95) 3 "We are only immortal Harvey Mudd College 3 for a limited time.. jwinstea@jarthur.Claremont.EDU 3 when we are young." Disclaimer: Mine, not theirs! 3 -Rush, Dreamline --[0220]-- [0221] daemon@ATHENA.MIT.EDU (John T Kohl) Linux_Activists 12/21/91 00:03 (61 lines) Subject: Re: Serial Communications... Date: Fri, 20 Dec 91 20:56:14 PST To: mpeters@polyslo.csc.calpoly.edu (Marc Peters) Cc: linux-activists@joker.cs.hut.fi In-Reply-To: [180] From: John T Kohl Reply-To: jtkohl@cs.berkeley.edu re: weirdness with 2-char things for serial lines. I just saw the same thing for the first time. It appears to be a problem with the both sending and receiving data, as I saw weirdness with output from the far end of the call as well as weirdness with stuff I typed. To get the serial line in this pickle, I started up a tcsh shell on that line while I had a terminal connected, and then I turned up the baudrate to 9600. I then put my modem back on, ran kermit (which reset the baud rate to 2400), and saw the problem. I then rebooted, and it cleared. This is reproducible. Linus (or anybody who knows details on the serial lines), is this enough info to debug the problem? John P.S. If you have a terminal and want to spawn a shell on it, here's a program to do that. Just running the shell with redirected input/output doesn't work right, as the controlling terminal doesn't get set right. #include #include #include extern char *sys_errlist[]; main(int argc, char *argv[]) { if (argc != 3) { fprintf(stderr, "usage: doshell &\n"); exit(1); } /* close down fd's */ close(0); close(1); close(2); /* detach from parent process's group */ setsid(); /* open new tty */ if (open(argv[1], O_RDWR, 0) == -1) exit(2); dup(0); dup(0); execlp(argv[2], "-", 0); /* should appear on new tty...: */ fprintf(stderr, "can't exec shell: %s\n", sys_errlist[errno]); exit(3); } --[0221]-- (pref = [0180]) [0222] daemon@ATHENA.MIT.EDU (Bruce Evans) Linux_Activists 12/21/91 10:14 (32 lines) Subject: Re: less v1.77 Date: Sat, 21 Dec 91 15:25:34 +1100 From: Bruce Evans To: linux-activists@joker.cs.hut.fi Jim Winstead Jr. writes: >You can set up a small shell script to view compressed files via less, as >well. I have one called zless that is simply 'zcat $* | less', and it works This doesn't work so well for browsing through a lot of files. Working through the files in linear order is not so good either, but my system is fast enough to skip through files (even compressed) with the N and P keys - in less 0.97. Another thing I didn't like about 177 was the change on these keys to be like more (:n and something or other). >Speaking of GNU utilities, someone mentioned making find 2.1 available, >because it was the "latest and greatest". I looked on prep.ai.mit.edu, >the official distribution point of GNU stuff, and it has find-3.2.tar.Z. Perhaps someone got the version numbers confused. 3.2 has been out for a couple of months, and 3.1 was around for a long time before that. I have 3.2 on Minix. BTW, bash-1.10 broke updatedb in find, because x=y export x fails to set x. updatedb has a statement like this to set the PATH. Isn't this supposed to work? It worked for bash-1.08 and works for ksh on ISC Unix. It doesn't work for bash-1.10 on Minix or ISC Unix. Bruce --[0222]-- [0223] daemon@ATHENA.MIT.EDU (Drew Eckhardt) Linux_Activists 12/21/91 14:13 (472 lines) Subject: Boot sector Date: Sat, 21 Dec 1991 12:05:12 -0700 From: Drew Eckhardt To: drew@ophelia.cs.Colorado.EDU, linux-activists@joker.cs.hut.fi, Well, I was sitting around, running end-of-semester level 0 dumps on several gigs of disk space, and started looking at converting my MASM bootsector code back to the Unix assembler format.... To refresh everyone's memory : The original Linux boot sector had problems on some clones. Basically, what happens is the default floppy diskette parameter table specifies a low number of sectors. A multi-sector read involving a higher sector results in a sector not found error, and the boot sector goes into an infinite loop... I sent out a boot sector that corrected this problem. For me, it worked. I never got any complaints, so either it worked for other people, no one tried it, or it got lost. However, some how after I got the code working 100%, I dammaged the error dump routine. No more errors, error dump nolonger called.... never saw the problem. The following source code fixes the bunged error dump. With an added push, it should be within 1 byte of overflowing..... almost time for more pruning. Unfortunately, my SCSI host / floppy controller fried itself. Although Linux is on its own MFM drive - I can't boot the floppy , and can't run the DOS stuff (including assembler) - meaning this is totally untested. If some one wants to do the honors.... --bootsect.asm-- ; Created by 2masm perl script by Drew Eckhardt ; bootsect.asm modified by Drew Eckhardt - ; support added for TRUELY compatable ; BIOS's as well as error dump code. .286 ; ; SYS_SIZE is the number of clicks (16 bytes) to be loaded. ; 3000h is 30000h bytes equ 196kB, more than enough for current ; versions of linux ; SYSSIZE equ 3000h ; ; bootsect.s (C) 1991 Linus Torvalds ; ; bootsect.s is loaded at 7c00h by the bios-startup routines, and moves ; iself out of the way to address 90000h, and jumps there. ; ; It then loads 'setup' directly after itself (90200h), and the system ; at 10000h, using BIOS interrupts. ; ; NOTE; currently system is at most 8*65536 bytes long. This should be no ; problem, even in the future. I want to keep it simple. This 512 kB ; kernel size should be enough, especially as this doesn't contain the ; buffer cache as in minix ; ; The loader has been made as simple as possible, and continuos ; read errors will result in a unbreakable loop. Reboot by hand. It ; loads pretty fast by getting whole sectors at a time whenever possible. _TEXT segment para public 'CODE' assume cs:_TEXT SETUPLEN equ 4 ; nr of setup-sectors BOOTSEG equ 07c0h ; original address of boot-sector INITSEG equ 9000h ; we move boot here - out of the way SETUPSEG equ 9020h ; setup starts here SYSSEG equ 1000h ; system loaded at 10000h (65536). ENDSEG equ SYSSEG + SYSSIZE ; where to stop loading ; ROOT_DEV: 000h - same type of floppy as boot. ; 301h - first partition on first drive etc ROOTDEV equ 21dh start: mov ax,offset BOOTSEG mov ds,ax mov ax,offset INITSEG mov es,ax mov cx,256 sub si,si sub di,di cld rep movsw db 0eah ; jmp INITSEG:go dw offset go dw INITSEG go: cli ; don't want interrupts when stack moves mov ax, cs mov ss, ax mov sp, 0ff00h - 12 ; arbitrary num - 512 - disk param size ; ; Many BIOS's default disk parameter tables will not recognize multi- ; sector reads beyond the maximum sector specified in the default ; diskette parameter talbes - this means 7 sectors :( ; ; Since single sector reads are ... slow, we must patch this. We ; simply set the max sector count to the most we will expect - 18. ; High doesn't hurt. Low does. ; xor ax, ax ; get diskette parameters from int 1eh mov es, ax ; vector (or 78h) push es ; save int table segment mov bx, 78h lds si, es:[bx] ; ds:si points to actual parameter table mov ax,cs ; mov es,ax ; copy disk parameters to RAM mov di, 0ff00h - 12 ; es:di points to dsk_tab push di ; save dsk_tab offset mov cx, 6h ; 12 bytes rep movsw pop di ; restore dsk_tab offset mov byte ptr es:[di + 4], 18; set sectors pop es ; set 1eh vector to disk_tab mov word ptr es:[bx], di ; offset mov ax, cs mov word ptr es:[bx+2], ax ; seg mov ds,ax ; load seg regs mov es,ax sti ; stack & disk parms are good. xor ah, ah ; reset FDC with new parameters. xor dl, dl int 13h ; load the setup-sectors directly after the bootblock. ; Note that 'es' is already set up. load_setup: xor dx,dx ; drive 0, head 0 mov cx,0002h ; sector 2, track 0 mov bx,0200h ; address equ 512, in INITSEG mov ax,0200h+SETUPLEN ; service 2, nr of sectors int 13h ; read it jnc ok_load_setup ; ok - continue push ax ; dump error code call print_nl mov bp, sp call print_hex pop ax xor dl, dl xor ax, ax ; reset the diskette int 13h jmp load_setup ok_load_setup: ; Get disk drive parameters, specifically nr of sectors/track IFDEF HARD mov cx, HARD ELSE xor dl,dl mov ax,0800h ; AH equ 8 is get drive parameters int 13h xor ch,ch ENDIF mov cs:sectors,cx mov ax,offset INITSEG mov es,ax ; Print some inane message mov ah,03h ; read cursor pos xor bh,bh int 10h mov cx,9 mov bx,0007h ; page 0, attribute 7 (normal) mov bp,offset msg1 mov ax,1301h ; write string, move cursor int 10h ; ok, we've written the message, now ; we want to load the system (at 10000h) mov ax,offset SYSSEG mov es,ax ; segment of 010000h call read_it call kill_motor mov ax, 0e0dh mov bx, 7 int 10h mov ax, 0e0ah int 10h ; After that we check which root-device to use. If the device is ; defined (; equ 0), nothing is done and the given device is used. ; Otherwise, either /dev/PS0 (2,28) or /dev/at0 (2,8), depending ; on the number of sectors that the BIOS reports currently. mov ax,cs:root_dev or ax, ax ; cmp ax, 0 jne root_defined mov bx,cs:sectors mov ax,0208h ; /dev/ps0 - 1.2Mb cmp bx,15 je root_defined mov ax,021ch ; /dev/PS0 - 1.44Mb cmp bx,18 je root_defined undef_root: jmp undef_root root_defined: mov cs:root_dev,ax ; after that (everyting loaded), we jump to ; the setup-routine loaded directly after ; the bootblock: db 0eah ; jmp SETUPSEG:0 dw 0 dw SETUPSEG ; This routine loads the system at address 10000h, making sure ; no 64kB boundaries are crossed. We try to load it as fast as ; possible, loading whole tracks whenever we can. ; ; in: es - starting address segment (normally 1000h) ; sread dw 1+SETUPLEN ; sectors read of current track head dw 0 ; current head track dw 0 ; current track read_it: mov ax,es test ax,0fffh die: jne die ; es must be at 64kB boundary xor bx,bx ; bx is starting address within segment rp_read: mov ax,es cmp ax,ENDSEG ; have we loaded all yet? jb ok1_read ret ok1_read: mov ax,cs:sectors ; this is the number of sectors we will sub ax,sread ; attempt to read ; mov ax, 1 ; single sector read - testing only mov cx,ax ; shl cx,9 ; * 512 bytes add cx,bx ; if overflow, then next segment jnc ok2_read je ok2_read xor ax,ax sub ax,bx shr ax,9 ok2_read: call read_track ; is called with num sectors wanted in al mov cx,ax add ax,sread ; add actual number read to ax cmp ax,cs:sectors jne ok3_read mov ax,1 sub ax,head jne ok4_read inc track ok4_read: mov head,ax xor ax,ax ok3_read: mov sread,ax shl cx,9 add bx,cx jnc rp_read mov ax,es add ax,1000h mov es,ax xor bx,bx jmp rp_read read_track: pusha push ax ; print loading... push bx mov ax, (0e00h + '.') mov bx, 7 int 10h pop bx pop ax mov dx,track mov cx,sread inc cx mov ch,dl mov dx,head mov dh,dl xor dl,dl and dx,0100h mov ah,2 push dx ; save for possible register dump push cx push bx push ax int 13h jc bad_rt add sp, 8 popa ret bad_rt: push ax ; save AX return - ; AH = errore code ; AL = successfully read. call print_all xor ah, ah ; reset FDC xor dl, dl int 13h add sp, 10 popa jmp read_track ; ; print_all is for debugging purposes. ; It will print out all of the registers. The assumtion is that this ; is called from the track read routine, with a stack frame like ; dx ; cx ; bx ; ax ; error ; ret <- sp print_all: mov cx, 5 ; error code + 4 registers mov bp, sp ; first one starts sp + 1 word print_loop: push cx ; preserve count left call print_nl ; new line for readability cmp cl, 5 ; first one printed is error code - no reg jae no_reg mov al, cl ; convert number to first register letter. mov ax, 0e05h + 'A' - 1 sub al, cl int 10h mov ax, 0e00h + 'X' int 10h mov ax, 0e00h + ':' int 10h no_reg: ; print the next register value add bp, 2 call print_hex pop cx loop print_loop ret print_nl: mov ax, 0e0dh ; CR mov bx, 7 int 10h mov ax, 0e0ah ; LF int 10h ret ; ; print_hex is for debugging purposes. It will print out the hex ; number pointed to by ss:[bp]. ; print_hex: mov cx, 4 ; 4 hex digits mov dx, word ptr [bp] ; load word into dx print_digit: rol dx, 4 ; will rotate, 4 bits will be highest mov ah, 0eh ; nibble, lowest nibble, etc. mov al, dl ; convert to digit representation and al, 0fh ; mask low nibble add al, '0' ; convert to 0 based digit cmp al, '9' ; if overflow, then go to letter jbe good_digit add al, 'A' - '0' - 0ah good_digit: mov ah, 0eh ; print it int 10h loop print_digit ret ; * This procedure turns off the floppy drive motor, so ; * that we enter the kernel in a known state, and ; * don't have to worry about it later. ; kill_motor: push dx mov dx,3f2h xor al,al out dx, al pop dx ret sectors dw 0 msg1 db 13,10 db "Loading" org 508 root_dev dw ROOTDEV boot_flag: dw 0AA55h _TEXT ends end -- ends -- Build with MASM, link, then exe2bin HARD may be defined with MASM bootsect.asm /DHARD=9; To get it to use the hardcoded sector count. TASM should also work, a86 will work if you change to its conditional define syntax. --[0223]-- [0224] daemon@ATHENA.MIT.EDU (0114) Linux_Activists 12/21/91 21:06 (54 lines) Subject: No subject found in mail header Date: Sun, 22 Dec 91 03:02:42 +0100 From: 0114 Apparently-To: linux-activists@joker.cs.hut.fi Hi, As a X-mas present, you get a termcap cdif to make uemacs recognize these nice keypads like page-up, home and the like. I added a new terminal type called memacs to the termcap entries. To use it, enter TERM=memacs;export TERM Wolfgang Thiel 12/21/91=linux0.11 upsyf173@comparex.hrz.uni-bielefeld.de table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 tcapdif M*BHJ("]!+V5T8R]T97)M8V%P"5-U;B!$96,@(#@@,3,Z-3@Z,3D@,3DY,0HMz M+2T@=&5R;6-A< E&7!A9"!U<'!E2CIC;R,Xd M,#IL:2,R-3IC;#U<15M(7$5;2CIS9CU<140Z7 HK( DZ;&4]7D@Z8G,Z86TZc M8VT]7$5;)6DE9#LE9$@Z;F0]7$5;0SIU<#U<15M!.EP**R ).F-E/5Q%6TLZb M8V0]7$5;2CIS;SU<15LW;3IS93U<15MM.G5S/5Q%6S1M.G5E/5Q%6VTZ7 HKa M( DZ;60]7$5;,6TZ;7(]7$5;-VTZ;6(]7$5;-6TZ;64]7$5;;3II2#I<"BL@"3IH;SU<15M(.FM0/5Q%6S5^.FM./5Q%x M6S9^.FM(/5Q%6UDZ:V@]7$5;2#IK1#U<15LS?CIK23U<15LR?CI<"BL@"3IKw M,3U<15M;03IK,CU<15M;0CIK,SU<15M;0SIK-#U<15M;1#IK-3U<15M;13IKv M-CU<15M;1CI<"BL@"3IK-SU<15M;1SIK.#U<15M;2#IK.3U<15M;23IK,#U To: linux-activists@joker.cs.hut.fi Date: Sun, 22 Dec 91 21:29:18 EST Ok, I finally got the gccbin.tar to my linux system, and untar-red it. Now, which files go where? Also what other files do I need for gcc to work? What about header files? --[0225]-- [0226] daemon@ATHENA.MIT.EDU (d88-man@nada.kth.se) Linux_Activists 12/23/91 05:47 (20 lines) Subject: console Date: Mon, 23 Dec 91 11:39:44 +0100 From: d88-man@nada.kth.se To: Linux-activists@joker.cs.hut.fi Hello Linuxers, I have played around with the setup.s(/console.c) to initialize different screenmodes with a supervga. Everything worked just fine, though 132x60 is a bit hard to read :-) If there is interest I could write some general code to detect what kind of SVGA-card installed and choose mode interactively. I know it's kind of useless but it is rather neat (at least as I see it) to have for example 80x43 mode which greatly improves the use of memacs multiwindow feature. Suggestions welcome ! The question is do one want this stuff in the kernel ? Is it usefull enough ? /Mats Andersson (d88-man@nada.kth.se) PS A merry christmas to all of you (probably not many reading their mail now when you should be on holliday :-) and a happy new 1992 --[0226]-- [0227] daemon@ATHENA.MIT.EDU (Marc CORSINI) Linux_Activists 12/23/91 13:40 (21 lines) Subject: gccbin installation question Date: Mon, 23 Dec 91 19:32:50 EST From: corsini@geocub.greco-prog.fr (Marc CORSINI) To: yanek@mthvax.cs.miami.edu In-Reply-To: Yanek Martinson's message of Sun, 22 Dec 91 21:29:18 EST <9112230229.AA18367@mthvax.cs.miami.edu> Cc: linux-activists@joker.cs.hut.fi About the headers just ftp-ize the include.tar from nic.funet.fi, tsx-11.mit.edu or tupac-amaru.informatik.rwth-aachen.de Another useful thing is to read INSTALL-0.11 0.10 and also linux.tex also avilable on the different sites. Finally (this was in an old post of Linus). Most programs starting with a "g" are gnu software. U shoold have unpack ur gccbin.tar in /usr/local/lib/gcc-xxx. U should link them as /usr/local/bin/gxxx and /usr/local/bin/xxx Hope this helps [mmc] PS1: Merry X-mas and happy new year. PS2: May be this more or less should be added in the FAQ --[0227]-- [0228] daemon@ATHENA.MIT.EDU (proven@Athena.MIT.EDU) Linux_Activists 12/23/91 16:56 (22 lines) Subject: VFS From: proven@Athena.MIT.EDU Date: Mon, 23 Dec 91 16:49:41 -0500 To: linux-activists@joker.cs.hut.fi For those interested, the VFS is currently in pre-alpha stage. I'll try to have an alpha release Sunday night if anyone is interested. It's kinda messy and half the files in the fs directory are unrecognizable from linux-0.11. I plan to get it all cleaned up and ready for linux-0.12 release. The VFS add functionallity to accomidate multiple filesystems, and I do plan to implement a few when I'm done with the VFS. It will also have functionallity for file types. It should contain all the functionallity of the old linux fs and only two system calls will have different interfaces mount and unmount. I have not put any hooks in for select, so if someone wants to do them thats fine, but I'd suggest starting with a kernel with the VFS in place or one of us is going to have a royal good time incorporating the others modifications. I'll work on additional fs functionallity when I'm done with the VFS, and the list is quite long, but the first thing to do is finish what I've started. CAP --[0228]-- [0229] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/23/91 20:06 (37 lines) Subject: virtual consoles working. Date: Mon, 23 Dec 91 17:00:15 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Hi and merry Xmas. This note is coming to you from the virtual console of Linux. Yep. I have virtual consoles working under linux. Although this is based upon Gordon Irlams minix patches, virtually no code from there was actually used. This is more a product of minix's message passing kernel being so different from Linux's unified approach than by design. But I am trying to adapt as much of his setterm program as possible, so that a user interface for setting colors and the like is available. To get around the problem of no init/login I am using the "doshell" program posted here earlier. Actually, for standalone machines I think I prefer it over getty/login. I will post the patches to 0.11 as soon as I have tested a little more, and had a chance to bundle it up. I also have done all of the design and coding, but none of the testing on a select call, adapted from Mathius Lauttiners design. But as Proven has requested, I will probably wait until after 0.12 is out before going any further with that. Getting a peek at your VFS patches early, thought might help. It's funny how things work out. I was working on select, started eyeing how they might interact with pty's, and realized that virtual consoles would probably still be desirable after ptys, as well as being easier to do. Anyways, have a good christmas all. I am heading to the ski slopes so I know I'll have fun. Hope you do to. --[0229]-- [0230] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/24/91 04:00 (632 lines) Subject: virtual consoles: part 2 Date: Tue, 24 Dec 91 00:50:21 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi concatenate these to the previous message. ----SNIP HERE------------------------------------- M"7!O#TP.PI8("!]"E@@( I8(2!S=&%T:6,@=F]If M9"!D96PH:6YT(&-U"D@>PI8(" )"7!Oe MPI8(" )a M"6-API8(" );&]N9R!C;W5N="!?7V%S;5]?*")C>"(I.PI8(" );&]N9R!Sv M=&%R="!?7V%S;5]?*")D:2(I.PI8(" *6"$@"7-W:71C:" H=G!API8u M(" )"6-API8(" );&]N9R!C;W5N="!?j M7V%S;5]?*")C>"(I.PI8(" );&]N9R!S=&%R="!?7V%S;5]?*")D:2(I.PI8i M(" *6"$@"7-W:71C:" H=G!API8(" )"6-A"(L(F1I(BD["E@@('T*e M6" @"E@A('9O:60@8W-I7VTH=F]I9"D*6" @>PI8(" ):6YT(&D["E@@( I8d M(" )9F]R("AI/3 [:3P];G!API8(2 )"0EC87-E(# Z(&%T='(]*&ES8V]L;W(_9&5F7V%Tr M='(Z,'@P-RD[8G)E86L[(" O*B!D969A=6QT("HO"E@A( D)"6-A# X.C!X,&8I.V)R96%K.R @+RH@p M8F]L9" J+PI8(2 )"0EC87-E(#0Z(&%T='(]*&ES8V]L;W(_9&5F7V%T=')\o M,'@P.#HP>#!F*3MB&9F)B@H<&]S+79I9&5O7VUE;5]S=&%R="D^/CDI+"!V:61E;U]P;W)Tp M7W9A;"D["E@J*BHJ*BHJ*BHJ*BHJ*BH*6"HJ*B S,C L,S(V("HJ*BH*6" @o M"7-T:2@I.PI8("!]"E@@( I8(2!S=&%T:6,@=F]I9"!R97-P;VYD*'-T5]S=')U8W0@*B!T='DI"E@@('L*6" @"6-H87(@*B!P(#T@4D534$].j M4T4["E@@( I8*BHJ*BHJ*BHJ*BHJ*BHJ"E@J*BH@,S,S+#,S.2 J*BHJ"E@@i M( EC;W!Y7W1O7V-O;VME9"AT='DI.PI8("!]"E@@( I8(2!S=&%T:6,@=F]Ih M9"!I;G-E5]T;U]C;V]K960H='1Y*3L*6" @?0I8e M(" *6"$@PI8(" ):6YT(&]L9'1O<"QO;&1B;W1T;VT["E@@( I8*BHJf M*BHJ*BHJ*BHJ*BHJ"E@J*BH@,S@S+#,Y-" J*BHJ"E@@( EO;&1B;W1T;VT]e M8F]T=&]M.PI8(" )=&]P/7D["E@@( EB;W1T;VT@/2!V:61E;U]N=6U?;&ENd M97,["E@A( ES8W)U<"@I.PI8(" )=&]P/6]L9'1O<#L*6" @"6)O='1O;3UOc M;&1B;W1T;VT["E@@('T*6" @"E@A('-T871I8R!V;VED(&-S:5]A="AU;G-Ib M9VYE9"!I;G0@;G(I"E@@('L*6" @"6EF("ANPI8l M(" ):68@*&YR(#X@=FED96]?;G5M7VQI;F5S*0I8(" )"6YR(#T@=FED96]?k M;G5M7VQI;F5S.PI8*BHJ*BHJ*BHJ*BHJ*BHJ"E@J*BH@-# U+#0Q-" J*BHJj M"E@@( EE;'-E(&EF("@A;G(I"E@@( D);G(@/2 Q.PI8(" )=VAI;&4@*&YRi M+2TI"E@A( D):6YS97)T7VQI;F4H*3L*6" @?0I8(" *6"$@3TPn M.PI8(2 *6"$@PI8(" )m M#UX.PI8(" )3UY.PI8("!]"E@@( I8(2!S=&%T:6,@l M=F]I9"!R97-T;W)E7V-U'DH"P@2D["E@@('T*6" @"E@@('9O:60@8V]N7W=R:71E*'-TPI8b M(2 )9V]T;WAY*&-U5]S=')U8W0@*B!T='DI"E@@('L*6" @"6EN="!N7,@=W)I=&5S('1O('1H92!C=7)Rs M96YT(&]N92X@*B\*6"L@"2 @8W5R6%T='(@/2!A='1R.PI8(" );G(@/2!#2$%24RAT='DM/G=R:71E7W$I.PI8p M(" )=VAI;&4@*&YR+2TI('L*6" @"0E'151#2"AT='DM/G=R:71E7W$L8RD[o M"E@J*BHJ*BHJ*BHJ*BHJ*BH*6"HJ*B T-38L-#8T("HJ*BH*6" @"0D)"0EIn M9B H>#X]=FED96]?;G5M7V-O;'5M;G,I('L*6" @"0D)"0D)>" M/2!V:61Em M;U]N=6U?8V]L=6UNF5?"D@>PI8(" )"0D)"0EX+2T["E@M+2T@-30P+#4U," M+2TM"E@@v M( D)"0E](&5L2DI"E@A( D)"0D)9&5L*&-U"D@>PI8(" )"0D)"0EX+2T["E@J*BHJ*BHJp M*BHJ*BHJ*BH*6"HJ*B T.#0L-#DP("HJ*BH*6" @"0D)"0EI9B H>#YV:61Eo M;U]N=6U?8V]L=6UNPI8(" )"0D)"0EX("T]('9I9&5O7VYU;5]C;VQUn M;6YS.PI8(" )"0D)"0EP;W,@+3T@=FED96]?#YV:61Ek M;U]N=6U?8V]L=6UNPI8(" )"0D)"0EX("T]('9I9&5O7VYU;5]C;VQUj M;6YS.PI8(" )"0D)"0EP;W,@+3T@=FED96]?2LQ*3L*e M6" @"0D)"65L2LQ*3L*6" @"0D)"65L2UP87);,%TI.PI8e M(" )"0D)"0EB2MP87);,%TI.PI8(" )"0D)"0EB'DH>"UP87);,%TL>2D["E@@( D)"0D)"6)Rx M96%K.PI8(" )"0D)"6-A2@P+'DK<&%R6S!=*3L*6" @"0D)v M"0D)8G)E86L["E@@( D)"0D)8V%S92 G1B2UP87);,%TI.PI8t M(" )"0D)"0EB2AX+'!A'DH<&%R6S%=+'!A'DH8W5Rb M'DH8W5R"QY+7!A'DH8W5R"QYw M*W!A'DH8W5R"MP87);,%TL>2D["E@@( D)"0D)"6)Rt M96%K.PI8(" )"0D)"6-A2AC=7)R8V]N2MP87);,%TI.PI8(" )"0D)"0EB'DH8W5R2AC=7)R8V]N&(X,# P.PI8(" )"79I9&5O7W!O#-D-3L*6"HJ*BHJ*BHJ*BHJ*BHJ*@I8y M*BHJ(#8V,BPV-C<@*BHJ*@I8+2TM(#2A/4DE'7U@L3U))1U]9*3L*p M6" @"7-E=%]T#(Q*28P>&9D+#!X,C$I.PI8(" )83UI;F)?n M<"@P>#8Q*3L*6" @"6]U=&)?<"AA?#!X.# L,'@V,2D["E@A( EO=71B*&$Lm M,'@V,2D["E@@('T*6" @+RH@9G)O;2!BF5?# W.PI8*R @( ED969?871T# W.PI8*R @(" @(" @('-T871E/3 [h M"E@K( EQ=65S(#T@,#L*6"L@"6ES8V]L;W(@/2 P.PI8(" *6"$@"6=O=&]Xg M>2AC=7)R8V]N#(Q*28P>&9D+#!X,C$I.PI8(" )83UI;F)?<"@P>#8Q*3L*6" @"6]U=&)?d M<"AA?#!X.# L,'@V,2D["E@A( EO=71B7W H82PP>#8Q*3L*6"$@(" )9F]Rc M("AI/3$[(&D\3E)?0T].4T],15,[(&DK*RD*6"$@(" @(" @("![('9C7V-Ob M;G-;:5T@/2!V8U]C;VYS6S!=.PI8(2 )("!V8U]C;VYS6VE=+G9C7V]R:6=Ia M;@D]("AU;G-I9VYE9"!L;VYG*79C7W-C#P\,2D["E@A( D@(&UAs M>&H@/2!V:61E;U]N=6U?;&EN97,J=FED96]?;G5M7V-O;'5M;G,["E@A( D@r M(&9O&H[(&HK*RD*6"$@(" @(" @(" @(" @=F-?# V+" P>#0R*3L*6" @"2\J(#$O."!S96-O;F0@*B\*m M6" @"6)E97!C;W5N=" ]($A:+S@["0I8*R!]"E@K( I8*R *6"L@"E@K('-Tl M871I8R!I;G0@:V)?86-K*"!I;G0@9&%T85]P;W)T*0I8*R!["E@K(" @:6YTk M(')E=')I97,["E@K( I8*R @(')E=')I97,@/2 P>#$P,# ["E@K(" @=VAIj M;&4@*"TM7,N( I8*R!S=&%T:6,@=F]I9"!S971?;&5D#8P.PI8*R )#8T.PI8*R @('T*6"L@"E@Kn M(" @:V)?=V%I="AS=&%T=7-?<&]R="D["0I8*R @(&]U=&)?<"AD871A7W!Om M7!E(#T](%9)1$5/7U194$5?14=!0R!\h M?"!V:61E;U]T>7!E(#T](%9)1$5/7U194$5?14=!32D@)B8*6"L@(" @("AOg M2@H=F]I9" J*79C7W-C2@H=F]I9" J*79C7W-CF5?F5?s MF5?2@H=F]I9" J*79I9&5O7VUE;5]B87-E+" H=F]Ij M9" J*79C7W-C5]T86)L95MN=6TK,5TN'0@8V]N6YCr M:')O;F]U6)O87)D*"D@:6YT97)R=7!T"E@K(" @("H@'1E&ET+F,)36]N($1E8R Q-B Q,SHS.#HU," Qc M.3DQ"E@J*BHJ*BHJ*BHJ*BHJ*BH*6"HJ*B Q,C(L,3(X("HJ*BH*6" @"6EPb M=70H8W5R&5C=71Aa M8FQE/4Y53$P["E@@( EI9B H8W5R2 ^/2 P*0I8(2 )"71T>5]T86)L95MC=7)R96YT+3YT='E=+G!G I8(" )<'5S:&P@)65C> I8(" )<'5S:&P@)65D> I8(2 )8V%L;"!?k M I8(2 )<&]Pj M;" E96%X"E@A( ES=6)B("0P>#-"+"5A; I8(2 ):F(@96YD7V9U;F,*6" @i M"6-M<&(@)#DL)6%L"E@@( EJ8F4@;VM?9G5N8PI8(" )7,*6" @("HO"E@@(&9U;F,Z"E@A( ES=6)B("0P>#-"f M+"5A; I8(2 ):F(@96YD7V9U;F,*6" @"7!U I8(2 )c M:FUP("!E;F1?9G5N8PI8(" )8VUP8B D.2PE86P*6" @"6IB92!O:U]F=6YCb M"E@@( ES=6)B("0Q."PE86P*6"HJ*B!I;FET+VUA:6XN8RYO71EPI8(" )"0EI9B H8W5R3PP*2!["E@@( D)"0EC=7)R96YT+3YT='D@/2!-24Y/a M4BAI;F]D92T^:5]Z;VYE6S!=*3L*6"$@"0D)"71T>5]T86)L95MC=7)R96YTz M+3YT='E=+G!G3PP*2!["E@M+2T@,38T+#$W," M+2TM"E@@( D):68@w M*$U!2D]2*&EN;V1E+3YI7WIO;F5;,%TI/3TT*2!["E@@( D)"6EF("AC=7)Rv M96YT+3YL96%D97(@)B8@8W5R2 ]($U)3D]2*&EN;V1E+3YI7WIO;F5;,%TI.PI8(2 )"0D)5%19t M7U1!0DQ%*&-U2DM/G!G3PP*2!["E@J*BH@:V5R;F5Lq M+V-HPI8(" )#(T+')S,5]I;G1E#(T+')S,5]I;G1E#(Q*3L*6" @?0I8(" *6"HJ*B!Id M;F-L=61E+VQI;G5X+W1T>2YH+F]R:6<)36]N($1E8R Q-B Q,SHT,#HR,R Qc M.3DQ"E@M+2T@:6YC;'5D92]L:6YU>"]T='DN: E3=6X@1&5C(#(R(#$X.C,Pb M.C,X(#$Y.3$*6"HJ*BHJ*BHJ*BHJ*BHJ*@I8*BHJ(#(Q+#(V("HJ*BH*6"TMa M+2 R,2PS,R M+2TM"E@@( EC:&%R(&)U9EM45%E?0E5&7U-)6D5=.PI8("!]z M.PI8(" *6"L@(V1E9FEN92!.4E]315))04P@,@I8*R C9&5F:6YE($Y27T-/y M3E-/3$53(#0*6"L@(V1E9FEN92!.4E]45%E3("A.4E]315))04PK3E)?0T].x M4T],15,K,2D*6"L@(V1E9FEN92!&25)35%]315))04Q?1$56(#8T"E@K("-Dw M969I;F4@5%197U1!0DQ%*'1T>6YU;2D@*"@H='1Y;G5M*2 \($9)4E-47U-%v M4DE!3%]$158I(#\@='1Y7W1A8FQE*RAT='EN=6TI(#I<"E@K('1T>5]T86)Lu M92LH='1Y;G5M*2M.4E]#3TY33TQ%4RU&25)35%]315))04Q?1$56*S$I"E@Kt M( I8(" C9&5F:6YE($E.0RAA*2 H*&$I(#T@*"AA*2LQ*2 F("A45%E?0E5&s M7U-)6D4M,2DI"E@@("-D969I;F4@1$5#*&$I("@H82D@/2 H*&$I+3$I("8@r M*%1465]"549?4TE:12TQ*2D*6" @(V1E9FEN92!%35!462AA*2 H*&$I+FAEq M860@/3T@*&$I+G1A:6PI"E@J*BHJ*BHJ*BHJ*BHJ*BH*6"HJ*B U,RPU." Jp M*BHJ"E@M+2T@-C L-C8@+2TM+0I8(" )?3L*6" @"E@@(&5X=&5R;B!S=')Uo M8W0@='1Y7W-T5]I;RYC"4UO;B!$96,@,C,@,C,Z,#4Z-#0@,3DY,0I8*BHJi M*BHJ*BHJ*BHJ*BHJ"E@J*BH@-#@L-30@*BHJ*@I8(" C9&5F:6YE($]?3DQ2h M150H='1Y*0E?3U]&3$%'*"AT='DI+$].3%)%5"D*6" @(V1E9FEN92!/7TQ#g M54,H='1Y*0E?3U]&3$%'*"AT='DI+$],0U5#*0I8(" *6"$@5]S=')U8W0@='1Y7W1A8FQE6UT@/2!["E@@( E["E@@( D)>TE#4DY,+ D)e M+RH@8VAA;F=E(&EN8V]M:6YG($-2('1O($Y,("HO"E@@( D)3U!/4U1\3TY,d M0U(L"2\J(&-H86YG92!O=71G;VEN9R!.3"!T;R!#4DY,("HO"E@M+2T@-#@Lc M-30@+2TM+0I8(" C9&5F:6YE($]?3DQ2150H='1Y*0E?3U]&3$%'*"AT='DIb M+$].3%)%5"D*6" @(V1E9FEN92!/7TQ#54,H='1Y*0E?3U]&3$%'*"AT='DIa M+$],0U5#*0I8(" *6"$@5]S=')U8W0@='1Y7W1A8FQE6TY2z M7U1465-=(#T@>PI8(" )>PI8(" )"7M)0U).3"P)"2\J(&-H86YG92!I;F-Oy M;6EN9R!#4B!T;R!.3" J+PI8(" )"4]03U-4?$].3$-2+ DO*B!C:&%N9V4@x M;W5T9V]I;F<@3DP@=&\@0U).3" J+PI8*BHJ*BHJ*BHJ*BHJ*BHJ"E@J*BH@w M.3 L.38@*BHJ*@I8(" )"7LP+# L,"PP+"(B?0I8(" )?0I8("!].PI8+2 *v M6" @+RH*6" @("H@=&AE2!T:&4@u M;6%C:&EN92!C;V1E(&AA;F1L97)S+@I8(" @*B!Y;W4@8V%N(&EM<&QE;65Nt M="!P2@F='1Y7W1A8FQE6S!=p M+G-E8V]N9&%R>2D["E@@('T*6" @"E@@('9O:60@8V]P>5]T;U]C;V]K960Ho M5]S=')U8W0@*B!T='DI"E@M+2T@,3,V+#$T-2 M+2TM"E@@n M( ES=&DH*3L*6" @?0I8(" *6"L@97AT97)N(&EN="!F9U]C;VYS;VQE.PI8m M("!V;VED('=A:71?9F]R7VME>7!R97-S*'9O:60I"E@@('L*6"$@"7-L965Pl M7VEF7V5M<'1Y*"9T='E?=&%B;&5;9F=?8V]N2T^=&5R;6EO5]T86)L93L*6" @"7=H:6QE("AN5]S=')U8W0@*B!T='D["E@@( EC:&%R(&,L("IB/6)U9CL*6" @"E@A( EIh M9B H*"%)4U]!7U1462AC:&%N;F5L*2D@?'P@;G(\,"D@2!I;FYO8V5N="X*6" @("HO"E@@('9Oc M:60@9&]?='1Y7VEN=&5RPI8("!]"E@M+2T@,S0T+#,V." M+2TM"E@@z M(" J('1O=&%L;'D@:6YN;V-E;G0N"E@@(" J+PI8("!V;VED(&1O7W1T>5]Iy M;G1E2D*6"$@>R!I9B H='1Y(#T](# I"E@A(" @("!Tx M='D@/2!F9U]C;VYS;VQE*S$["E@A(" @96QS90I8(2 @(" @:68@*"AT='D^w M/3$I("8F("AT='D\/3(I*0I8(2 @(" @("!T='D@/2!T='D@*R!.4E]#3TY3v M3TQ%4SL*6"$@("!C;W!Y7W1O7V-O;VME9"A45%E?5$%"3$4H='1Y*2D["E@@u M('T*6" @"E@@('9O:60@8VAR7V1E=E]I;FET*'9O:60I"E@@('L*6"L@("!It M;G0@:3L*6"L@("!F;W(@*&D]3E)?4T5224%,.R!I/C [(&DM+2D@("\J($UOs M=F4@? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 vc.shar M96-H;R!X("T@4D5!1$U%"G-E9" G+UY8+W,O+R\G(#X@4D5!1$U%(#P\("2!M>0I8;6%C:&EN92$@(%1Ht M6]U7-T96TN"E@*6" @,2 M($%P<&QY('!A=&-H97,Z("!M;W9E('9Cc M+F-D:68@=&\@>6]U6]U(&%R92!N;W0@=7-I;F<@-3 @y M;&EN97,@*&%S(&%B;W9E*2P@961I="!C;VYS;VQE+F,@;F]W+@I8"4EF('EOx M=2!A2!H879E('1T>3$@86YD('1T>3(@9&]N92P@r M=&AE(&9O;&QO=VEN9PI8"71T>7,@;75S="!B92!C3$O='1Y,BD@=&AE>0I8"6%Rk M92!N;W<@6]U(&-A;B!M;V1I9GD@3E)?0T].h M4T],15,@:6X@:6YC;'5D92]L:6YU>"]T='DN: I8=&\@86X@87!P2X@($)U="!M;W)E('1H86X@,3$*6&UE86YS(&YO(&1U;7!I;F<@d M<')O8V5S6X@:7,@=FER='5A;"!T97)M:6YA;"!N('-Ea M;&5C=&5D('=I=&@@9G5N8W1I;VX@:V5Y($9N+@I8("!T='DV-"]T='DV-2!Az M2!C;VYSt M;VQE"E@@(" @*&5V96X@8F5F;W)E(&UY('!A=&-H97,I+"!A;F0@2X*6 I81V]A;#H*6 I8("!1=6%N=&ET>2!Nl M;W0@<75A;&ET>2X*6 I806-K;F]W;&5D9V5M96YT.@I8( I8("!';W)D;VX@k M27)L86T@;V8@8V]U" M(&1O6"]S+R\O)R ^(&1O&ET*#$I.PI8(" @('T*6 I8(" @("\J(&-L;W-E(&1O=VX@9F0G&ETv M*#(I.PI8(" @(&1U<"@P*3L*6" @("!D=7 H,"D["E@@(" @97AE8VQP*&%Ru M9W9;,ETL("(M(BP@,"D["E@@(" @+RH@" M('-E='1E6"]S+R\O)R ^q M('-E='1E#H*6" J"E@@*B!S971T97)M"E@@*B @(%L@+71E7!E(&ES(")Mq M:6YI>"UV8R(L(&]R"E@@*B B;6EN:7@M=F-A;2(@=&AE('-T"!V:7)T=6%L(&-O;G-O;&4@9')I=F5R(&ES(&]U='!U="X@n M($]P=&EO;G,@=&AA="!A2!T:&4@m M=&5R;6EN86P@87)E(&EG;F]R960N"E@@*@I8("H@5&AE(&9O;&QO=VEN9R!Ol M<'1I;VYS(&%R92!N;VXM;V)V:6]U0I8("H@(" @("!S971S('1He M92!T97)M:6YA;"=S(')E;F1E"UV8V%M(@I8u M"E@O*B!497)M8V%P(&-O;G-T86YT7!E7!E+B J+PI8:6YT(&]P=%]F;U]C;VQOPI8"2IO<'1?;VX@/2!4c M4E5%.PI8("!]"EA]"E@*6'9O:60@<&%R6)O87)D('1Y<&4@=&\@w M6)O87)D(#T@1%540T@["E@)96QS92!In M9B H'1E;F1E9"(I(#T](# I"E@)"2IO<'1?m M:V5Y8F]A6%N(BD@/3T@,"D*6 D)*F]P=%]C;VQOr M7!E+"!B861?87)G*3L*6" @96QS92!I9B H6%N?'=Hl M:71E?&1E9F%U;'0@75QN(BD["E@@(&9P2X@a M*B\*6 I88VAA2!E>&ES=',N"E@@*B\*6 I8("!C:&%R("IB=69?<'1R.PI8"E@@(&)U9E]Pv M='(@/2!T8U]E;G1?8G5F.PI8("!I9B H=&=E='-T2@B2@B=FDB*2D["E@@j M('T*6 I8(" O*B M:V5Y8F]A6)O87)D("8F('9C=&5Rh M;2D@>PI8"7-W:71C:" H;W!T7VME7W1Y<&4I('L*6 D@(" @8V%S92!00SH*g M6 D)<')I;G1F*"(E6)O87)D+F1U=&-H(BP@4U0I.PI8"0EB'1E;F1E9"(L(%-4*3L*6 D)8G)E86L["E@)?0I8("!]"E@*6" @+RH@+6QIz M;F5W2X@*B\*6" @:68@*&]P=%]L:6YEy M=W)A<" F)B!V8W1E2X*6" @("HO"E@@(&EF("AO<'1?9F]R96=R;W5N9" F)B!V8W1E65L;&]W?&)L=65\;6%G96YT87QC>6%N?'=H:71E?&1E9F%Uc M;'0N"E@@(" J(%9C(&]N;'DN"E@@(" J+PI8("!I9B H;W!T7V)A8VMGPI8"6EF("AO<'1?8F]?;VXI"E@)"7!R:6YTw M9B@B)7,B+"!T8U]E;G1R>2@B;60B*2D["E@)96QS92!["E@)"6EF("AV8W1Ev M2@B;64B*2D["E@)?0I8("!]"E@*t M6" @+RH@+6)L:6YK(%MO;GQO9F9=+B @5F,@8F5H879E'!E8W1Es M9"P@;W1H97)W:7-E(&]F9B!T=7)NPI8"6EF("AO<'1?f M=6Y?;VXI"E@)"7!R:6YT9B@B)7,B+"!T8U]E;G1R>2@B=7,B*2D["E@)96QSe M90I8"0EP2X@*B\*6" @:68@*&]P=%]S=&]R92 F)B!Vc M8W1EPI8"6EF("AO<'1?8VQ?86QL*0I8"0EPPI8"0D):68@*"IAPI8"71EPI8"69P&ET*# I.PI8?0HO"F5Cs M:&\@>" M('-T87)T8V]N6"]S+R\O)R ^('-T87)T8V]N3,@+V)I;B]Sp M:" F"E@O=7-R+VQO8V%L+V)I;B]D;W-H96QL("]D978O='1Y-" O8FEN+W-Ho M("8*6"]U6%N(%P*6" @+6-L96%R(')Em M3$*6"]U6%Ng M("UB86-K9W)O=6YD(&)L=64@7 I8(" M8VQE87(@86QL(#X@+V1E=B]T='DTf M"B\*96-H;R!X("T@=&5R;6-A< IS960@)R]>6"]S+R\O)R ^('1E"!H87-N)W0@>65T(&$@8V]M<&QE=&4@=G0Q,# Lh M('-O('=E(&IU2!C:&%N9V4N($YO=&4A(%=E(&%L&X@+2!I9VYO2#I<"E@).FAO/5Q%6T@Z:S$]n M7$5/4#IK,CU<14]1.FLS/5Q%3U(Z:S0]7$5/4SIP=#IS2#I<"E@)f M.FAO/5Q%6T@Z:S$]7$5/4#IK,CU<14]1.FLS/5Q%3U(Z:S0]7$5/4SIP=#ISe M6"]S+R\O)R ^('9C+F-Dc M:68@/#P@)R\G"E@J*BH@:V5R;F5L+V-H2YH/@I8(" C:6YC;'5D92 \87-M+VEO+F@^"E@@x M("-I;F-L=61E(#QA#DP,# T*0I8(" C9&5F:6YE($]224=?5DE$s M14]?34]$10D)*"@J*'5N&9Fr M*0I8(" C9&5F:6YE($]224=?5DE$14]?0T],4R )*"@H*BAU;G-I9VYE9"!Sq M:&]R=" J*3!X.3 P,#8I("8@,'AF9C P*2 ^/B X*0I8(2 C9&5F:6YE($]2p M24=?5DE$14]?3$E.15,)*#(U*0I8(" C9&5F:6YE($]224=?5DE$14]?14=!o M7T%8"2@J*'5N#DP,#!C*0I8+2TM(#0R+#0X("TM+2T*6" @(V1E9FEN92!/4DE'k M7U9)1$5/7U!!1T4)"2@J*'5N#DP,# V*2 F(#!X9F8P,"D@/CX@g M."D*6"$@(V1E9FEN92!/4DE'7U9)1$5/7TQ)3D53"2@U,"D*6" @(V1E9FENf M92!/4DE'7U9)1$5/7T5'05]!6 DH*BAU;G-I9VYE9"!S:&]R=" J*3!X.3 Pe M,#@I"E@@("-D969I;F4@3U))1U]6241%3U]%1T%?0E@)*"HH=6YS:6=N960@d M#DP,#!A*0I8(" C9&5F:6YE($]224=?5DE$14]?14=!7T-8c M"2@J*'5N7!E(&]F(&1I'0@8V]L=6UN"QY.PI8(2!S=&%T:6,@=6YS:6=N960@;&]N9PETg M;W L8F]T=&]M.PI8(2!S=&%T:6,@=6YS:6=N960@;&]N9PES=&%T93TP.PI8f M(2!S=&%T:6,@=6YS:6=N960@;&]N9PEN<&%R+'!A2!B96ENa M9R!UF5?3L*6"$@c M("!U;G-I9VYE9"!L;VYG"79C7W1O<"QV8U]B;W1T;VT["E@A(" @=6YS:6=Nb M960@;&]N9PEV8U]N<&%R+'9C7W!A#L*6"$@("!U;G-I9VYE9"!V8U]S879E9%]Y.PI8(2 @('5Nw M0DH=F-?8V]N2D*6"$@(V1E9FENe M92!V:61E;U]M96U?'D@=&AI;FMS('@]u M/79I9&5O7VYU;5]C;VQU;6YS(&ES(&]K("HO"E@A('-T871I8R!I;FQI;F4@t M=F]I9"!G;W1O>'DH=6YS:6=N960@:6YT(&YE=U]X+'5N2D*6" @>PI8(" ):68@*&YE=U]X(#X@=FED96]?;G5M7V-O;'5M;G,@r M?'P@;F5W7WD@/CT@=FED96]?;G5M7VQI;F5S*0I8(" )"7)E='5R;CL*6"TMq M+2 Q,C,L,3(Y("TM+2T*6" @(V1E9FEN92!215-03TY312 B7# S,UL_,3LRp M8R(*6" @"E@@("\J($Y/5$4A(&=O=&]X>2!T:&EN:W,@>#T]=FED96]?;G5Mo M7V-O;'5M;G,@:7,@;VL@*B\*6"$@2AI;G0@8W5R"QU;G-I9VYE9"!I;G0@;F5W7WDIm M"E@@('L*6" @"6EF("AN97=?>" ^('9I9&5O7VYU;5]C;VQU;6YS('Q\(&YEl M=U]Y(#X]('9I9&5O7VYU;5]L:6YE#P\,2D["E@@('T*6" @"E@A('-T871I8R!Ii M;FQI;F4@=F]I9"!S971?;W)I9VEN*'9O:60I"E@@('L*6" @"6-L:2@I.PI8h M(" );W5T8E]P*#$R+"!V:61E;U]P;W)T7W)E9RD["E@M+2T@,3,R+#$S." Mg M+2TM"E@@( EP;W,];W)I9VEN("L@>2IV:61E;U]S:7IE7W)O=R K("AX/#PQf M*3L*6" @?0I8(" *6"$@PI8(2 ):68@*'9I9&5O7W1Y<&4@/3T@5DE$14]?5%E0a M15]%1T%#('Q\('9I9&5O7W1Y<&4@/3T@5DE$14]?5%E015]%1T%-*0I8(" )z M>PI8(" )"6EF("@A=&]P("8F(&)O='1O;2 ]/2!V:61E;U]N=6U?;&EN97,Iy M('L*6" @"0D);W)I9VEN("L]('9I9&5O7W-I>F5?PI8(2 ):68@*"AC=7)R8V]N7!E(#T](%9)1$5/7U19u M4$5?14=!0R!\?"!V:61E;U]T>7!E(#T](%9)1$5/7U194$5?14=!32DI*0I8t M(" )>PI8(" )"6EF("@A=&]P("8F(&)O='1O;2 ]/2!V:61E;U]N=6U?;&ENs M97,I('L*6" @"0D);W)I9VEN("L]('9I9&5O7W-I>F5?F5?PI8(" )"0E?o M7V%S;5]?*")C;&1<;EQT(@I8(" )"0D)(G)E<%QN7'0B"E@M+2T@,3F5?7!E(#T](%9)1$5/7U19h M4$5?14=!0R!\?"!V:61E;U]T>7!E(#T](%9)1$5/7U194$5?14=!32D*6" @g M"7L*6" @"0E?7V%S;5]?*")S=&1<;EQT(@I8(" )"0DB2LQ/&)O='1O;2D@>PI8(" )"7DK*SL*6"TM+2 R-#$L,C0W("TM+2T*6" @x M"7T*6" @?0I8(" *6"$@2LQ/&)O='1O;2D@>PI8(" )"7DK*SL*6"HJ*BHJ*BHJv M*BHJ*BHJ*@I8*BHJ(#(P."PR,3<@*BHJ*@I8(" )"7!O3YTs M;W I('L*6" @"0EY+2T["E@M+2T@,C0X+#(U-R M+2TM"E@@( D)<&]S("L]r M('9I9&5O7W-I>F5?3YT;W I('L*6" @"0EY+2T["E@J*BHJo M*BHJ*BHJ*BHJ*BH*6"HJ*B R,3@L,C,S("HJ*BH*6" @"0EP;W,@+3T@=FEDn M96]?#P\,3L*6" @"7@],#L*6" @?0I8(" *6"$@F5?? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 cons.cdif M*BHJ(&-O;G,N,3$)5'5E($1E8R R-" P.3HQ-CHS,2 Q.3DQ"BTM+2!C;VYSz M;VQE+F,)5'5E($1E8R R-" P.#HR,#HQ,2 Q.3DQ"BHJ*BHJ*BHJ*BHJ*BHJy M*@HJ*BH@-S8L.#$@*BHJ*@HM+2T@-S8L.#(@+2TM+0H@(" @=6YS:6=N960@x M8VAA<@EV8U]D969?871TPHKh M(" @8VAA5]S=')U8W0@*B!T='DI"B @>PH@z M( EI;G0@;G(["B$@"6-H87(@8SL*(" *(" ):6YT(&-U2D["B$@"0D)"65L#T])S@G*0H@( D)"0D)2D["B$@"0D)"65LPH@( D)"0D)8V%S92 Gz M1RPH@( D)"0D)8V%S92 G1R2 J+PH@( D)"2 @8G)E86L["BL@"0D)s M8V%S92 V.@HK( D)"2 @:68@*&,@/3T@)S G*0HK( D)"2 @>R!S=&%T92 ]r M( HK( D)"2 @("!R97-T871E(#T@-SL**R )"0D@('T**R )"0D@(&5LR!S=&%T92 ]( HK( D)"2 @("!R97-T871E(#T@-SL**R )j M"0D@(" @8G)E86L["BL@"0D)("!]"BL@"0D)("!E;'-E(&EF("AC(#T](#(Wi M*0HK( D)"2 @>R!S=&%T92 ](#$["BL@"0D)(" @(&)R96%K.PHK( D)"2 @h M?0HK( D)"2 @96QS92 @"BL@"0D)("!I9B HF5?# W.PH@(" @"61E9E]Au M='1R/3!X,#<["B$@(" @(" @("!S=&%T93TP.PH@( EQ=65S(#T@,#L*(" )t M:7-C;VQO# W.PHA(" @(" @(" @ To: linux-activists@joker.cs.hut.fi In-Reply-To: Linus Benedict Torvalds's message of Wed, 25 Dec 1991 18:09:12 +0200 <199112251609.AA08539@kruuna.helsinki.fi> Linus: >I got a request that the ftp-sites shouldn't contain some very >out-of-date information: Linux.tex was the file mentioned ... I removed Linux.tex from nic.funet.fi (actually all old versions are available from directory 'testing' .. that is not visible althought .. possible to see it in file 'ls-laR'). It's possible to FTP put stuff to nic.funet.fi ;-) to either main directory or 'incoming' directory ... I prefer the authors put their work to FTP sites like nic.funet.fi and release them on mailing list. For those who don't have FTP, there's 'mail-server@nic.funet.fi' so, everyone is served (just send a mail to it with body containing 'help'). FTP site is nic.funet.fi:/pub/OS/Linux We should limit sources on mailing list (just the traffic is getting BIGger) .. and the FTP users of nic.funet.fi won't get sources sent to the mailing list .. because I don't have time (and will) to take sources out of mails (sorry) .. It might also be time to start comp.os.linux? Who's willing to handle voting etc.? We might 'steal' comp.os.misc too ... I would like to spit the mailing list to two parts 'users' i.e. activists and 'hackers' .. those who contribute patches and create new code instead of asking quite trivial questions i.e. like 'why my PC won't work?', 'how should I partition my 20 MB disk?' etc. Comments? arl --[0234]-- [0235] daemon@ATHENA.MIT.EDU (Wolfgang Thiel) Linux_Activists 12/25/91 21:23 (19 lines) Subject: Porting g++ 1.40.3 Date: Thu, 26 Dec 91 04:02:45 CET From: Wolfgang Thiel To: linux-activists@joker.cs.hut.fi Hi, Did somebody else try to port g++-1.40.3 to linux? I am having problems with the estdio FILE structure. I tried the MASSCOMP define, setting __rend and __rptr to something......., but - when trying to build libg++-1.39.0 - I always get errors in PlotFile.h; this has to do something with those inline functions, I'm shure. (And the problem with estdio only starts AFTER that!!). So, questions: 1. Who has come a step further ? 2. Who has - PD - sources for a USG compatible stdio library ? (I remember some PD source for some UNIX shell which included a stdio library; but I cannot remmeber the name....). Wolfgang Please reply to upsyf108@comparex.hrz.uni-bielefeld.de, I cannot receive the list at the moment: this wonderful vm/cms kermit is trying to send from my usual account upsyf173, and I cannot login again to read the mail. --[0235]-- [0236] daemon@ATHENA.MIT.EDU (Yanek Martinson) Linux_Activists 12/25/91 23:41 (13 lines) Subject: Re: Porting g++ 1.40.3 From: Yanek Martinson To: UPSYF108@comparex.hrz.uni-bielefeld.de (Wolfgang Thiel) Date: Wed, 25 Dec 91 23:34:37 EST Cc: linux-activists@joker.cs.hut.fi In-Reply-To: <9112260217.AA01049@joker.cs.hut.fi>; from "Wolfgang Thiel" at Dec 26, 91 4:02 am > 2. Who has - PD - sources for a USG compatible stdio library ? > (I remember some PD source for some UNIX shell which included a stdio > library; but I cannot remmeber the name....). nn newsreader includes a stdio library. They claim it is faster than the usual library. You might want to try that. It also has substitutes for many include files. --[0236]-- [0237] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/26/91 01:47 (32 lines) Subject: getting to VGA 50 line mode without shoelace. Date: Wed, 25 Dec 91 22:41:07 PST From: pmacdona@sol.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi The following quick hack sets up your VGA card for 50 line mode. It does NOT check to see if you have a VGA. It is NOT selectable back to 25 lines. It is a quick hack. But it should work. Just patch boot/setup.s and remake. *** setup.s.orig Tue Dec 24 17:44:51 1991 --- setup.s Tue Dec 24 17:56:30 1991 *************** *** 62,67 **** --- 62,75 ---- mov [10],bx mov [12],cx + mov ax,#0x0003 + int 0x10 + + mov ax,#0x1112 + mov bx,#0x0000 + int 0x10 + ! Get hd0 data mov ax,#0x0000 --[0237]-- [0239] daemon@ATHENA.MIT.EDU (Oleg Moroz) Linux_Activists 12/26/91 08:31 (17 lines) Subject: GNU STDIO for C++ To: Linux-activists@joker.cs.hut.fi From: moroz@inzer.demos.su (Oleg Moroz) Date: Thu, 26 Dec 91 14:56:25 +0200 (MSK) For those who's trying to port g++ to Linux and having trouble with estdio: there's (GPL-copylefted) version of AT&T 2.0 compatible iostreams implemen- tation by Per Bothner including ANSI-compliant stdio (based on streams, of course). The file name is iostreams-0.50.tar.Z; it's available in pub/gnu on nic.funet.fi, for example. Oleg -- * Oleg Moroz Surface address: P.O.Box 30, 103031, Moscow, USSR * * Software Designer Internet address: moroz@inzer.demos.su * * Steepler Ltd. Phone: +7 (095) 214-81-92, 245-86-62 (voice) * * "I've looked over jordan and I've seen/Things are not what they seem" - PF * --[0239]-- [0240] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/26/91 17:11 (29 lines) Subject: Please put me on the mailing list of LINUX. Date: Fri, 27 Dec 1991 00:06:08 +0200 From: Ari Lemmke To: rhwang@cs.utexas.edu Cc: Linux-activists@joker.cs.hut.fi In-Reply-To: Rwo-Hsi Wang's message of Thu, 26 Dec 1991 01:22:05 -0600 <9112260722.AA09811@cs.utexas.edu> >Thanks! > >Rwo-Hsi (rhwang@cs.utexas.edu) We will NOT allow any request posting to the mailing list, not this kind of noise to the mailing list, please. The _only_ address for the requests (unsubscribe or subscribe, address changes etc.) is: linux-activists-request@niksula.hut.fi We have about 110 Linux activists on the list, and the groving rate is about 10/week. I suggest, that everybody sends mail: 'Why should I know that?' to the ignorant ones (I usually do). The only way in network anarchy is everyone beeing active [your right]. ;-) Thanks, arl --[0240]-- [0241] daemon@ATHENA.MIT.EDU (Oleg Moroz) Linux_Activists 12/26/91 17:48 (17 lines) Subject: Init/getty/login ? To: Linux-activists@joker.cs.hut.fi From: moroz@inzer.demos.su (Oleg Moroz) Date: Thu, 26 Dec 91 23:49:15 +0200 (MSK) I wonder: is anybody doing standard (SystemV-style) init, getty and login for Linux ? I miss it very much (especially after the virtual console patch was posted) and I'm thinking about a possibility to do it myself. As it will cause the noticeable difference in system startup behaviour, I think that we Linux users & hackers should reach some agreement about it before some work will be done. Oleg -- * Oleg Moroz Surface address: P.O.Box 30, 103031, Moscow, USSR * * Software Designer Internet address: moroz@inzer.demos.su * * Steepler Ltd. Phone: +7 (095) 214-81-92, 245-86-62 (voice) * * "I've looked over jordan and I've seen/Things are not what they seem" - PF * --[0241]-- [0242] daemon@ATHENA.MIT.EDU (Yanek Martinson) Linux_Activists 12/26/91 18:00 (38 lines) Subject: Re: Init/getty/login ? From: Yanek Martinson To: moroz@inzer.demos.su (Oleg Moroz) Date: Thu, 26 Dec 91 17:56:28 EST Cc: Linux-activists@joker.cs.hut.fi In-Reply-To: ; from "Oleg Moroz" at Dec 26, 91 11:49 pm > I wonder: is anybody doing standard (SystemV-style) init, getty and login > for Linux ? I have started writing an init. I also have found a login, a cron, and an uucp (havent tried these on linux yet)... > As it will cause the noticeable difference in system startup behaviour, I don't think startup sequence will change that much. After running /etc/rc, instead of running shell, init will be run in it's place. And the code that sets up fd-s for shell can be left out (a getty will do that) and also the code after that 'child #### terminated' can be left out (init never dies (supposedly :-)). This will make the system image a bit smaller. I sont see any other changes.. > Linux users & hackers Are there any users yet? I mean is anybody using linux for anything other than hacking? > should reach some agreement about it before some work will be done. The SysV-style init is so flexible (with run-levels, and /etc/inittab) that there should be no problem for everybody to configure it whichever way they like it. p.s. the telinit command (run from command line) needs to communicate one byte (actually one of: '0123456SsQq') to the running init proccess. What is the best way to do this? Send a signal? Write to a file? A named pipe would be great but we dont have these yet. --[0242]-- [0243] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/26/91 19:13 (191 lines) Subject: A screen blanker for VC (also fixes reverse video problem) Date: Thu, 26 Dec 91 16:06:11 PST From: pmacdona@sanjuan.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Ok here is my third, and final patch for Virtual Consoles. This one implements screen blanking. It assumes you have already applied the two previous patches, (VC and VT100 graphics char) already. If there is demand, I will later post a single patch for all of these, but I think 0.12 will have these included in mid January. Also bootsect.s and setup.s should probably be changed in 0.12 to .S files like keyboard.S to allow conditional compilation and sharing of constants (like SYSSIZE in build.c and bootsect.s). I have done this in my system, and will submit them to Linus in Jan 5th, but will not post them now. There are already entirely too many patches floating around. good luck. table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 blank.tar.Z M'YV04HH$(=*D"("#"!,J7,BPH<.'$"-*1 BBH@T:-$ J,@1AD:.%3UN!%EQz M1HT:'D'4B"&CQ@T:-F3 J,'QQLL:&V%,W,FSI\^? .K,H1-&3D4 NVS.(MC($A&"W8*!8'"L>@Q=>2X=4.'S>XPG=/8$5X]u M!>@P<]R(66(6/;39X[8>0QAPL5:26:7'0M!UL;<)@'@GY=H=:5t M&,5M)L=G$;IZ$A&FZ#L=4:9A0:)P=E"@BQ&QEEF!%&s M'6QX]F&(^(&61F]QB48&5V>EQ1]8<2D%&!RGI=%&&02"0 6)914I6F,L** ?r M")55-$=I=!S7!@@M(+@&"&Y4IL =)KJ%)@BIA8%F'6W89Y1]=(0&ET<9@F #q M#%%. 6:/C9U&HA['D3CD'%;.H4"A89P1AEU1)O'@'('UMMN6WLU9YW(QP/#9p MDW/U&"H(;406YH"5!6%&F$:% 4>#>?38Z5=AF=@5"HP^Z552LI$1GFCP@4";o M>VH(99I;S3'X(Y0*&(@9KMM]20>L;;@P1G_\,?N&L]!!Z@9_;;RQ'IRFT4'Bn M"T+)\8)OP+'Q@AB4*E#%ER6*YD89=X P5%%A.>=O';-"MA]U1I4[I!F[Y?%&m M>/X2]5=SAQEJ&QG\*5 FB'2!<*JZ^>;EUU#^@BEFE-*"X)882L(8!!N(H;F4l M:(XAF09V#M?AXQQC@;PE2B! MB^J;]#X6 TU/S9Q9QA8@i M?%_6"9VU!+NP&-F+TZB:44 ++9K"T"H01%=NS$S&9V08-M_JI*5+HEASD0;"h M%%E,,4426H@-,@QXS ##\VU3^",9VL)HF?%5%#&%#I5E\3"J :+Y%G\@%QX&g M@&Y>%[)>O;W!&.0RP#D'IFK!6%$,[EF+;9"%K;(2C1?BD,=RB(;!9 $9)U"6V*@5!%+Y4YFIEE#[?K%)B1Y+F0"A Q_e M(CA!-\C&421I#H[X8Y_7D,A27TI+9_8#@NJXS0V284YXQE.>&;U!.+4SC7XHd M0Q(GA.%)#A*!%[:P!2>P000H0X/-NJ(6X"B'.LK!S!PD6!37# >(GS**$RP(c M$CSI"3-\&I>?XDB^__DF-'( #K[2,/\TH 6,];,- J$I&EDR 8-D:1P9WB#K4C4J4O"z M)5DD*U:A4F.F@[6-36G8CAZC%D,M'G*'2_3*1%1DG"+0XJ[*D($I"<*2_8G,@5?9(*)ERD&$4.@;PA--Px MX<$//KUR',Z1H2OJTV"XS)(>.S1F.B$C0_"6HSX)R2]H[H,15E;*TI:NU$S:w M6IA+9RH5CEPD(R/IR$= (A*2F)(&+9E!15;2DAO40"8W2$D,0B6#&>2$IE#%v MBK**8I'#%\@@!SL4%JUO4*L+t MV.I6T<1U6S+(R%V?9]<<>(RO?@6K:$=+6A4H0+0@P @+:.#9T?XUL*I="9D s MVP(V)J!<=A@,"9@7*A:4H QAP(-M<0N"$@37MQ<=KKF*>]S?.FH%(+BMN0;Sr M!3/9)8""\2UPA0M=Z>:VN-ME0755*4/RV!8/>QF,<=G@6\$D( $O4 %X@WM2q M!YZM:*)1P0ML:Q/A3>]E@VS$PR+\ +H.HUGO:L J.K&PQ$?7&T-:Wp M7G:N,:CK74^UU[Z^5K"$-:L<#ON"").2PI6%JUPS:TH8Z &,K!K_#H!Q>QM"@%+!Qn M#PKH[K\VMZWK[BA!_.E!WG9@VS+@ 5:8\;)]R@"'\M*!S-TU,YH!^.4UN!G.m MT96S8>EL7?(<)X5X3H">1PP"):>!AJK\@C/=@ )#DR$%@1XT9AS](#>82=%Ml MP62CEPSI+'.I(H(^\YXI/092j M=Y,=:_(ZFPY6[NX>$F F-P,VT,B&=34?[>GW[@%.ZO9V'<@#@AZ(N=L\\G-Ci M!=,"_+FGW:"NR+O77>\Q SRZ()GWI1>-[1UH&^$0[X.KNPMJB4\1_:/?.8)^#5W*$R&Z!-g MZ75@W][C8B=2OA79 IGF32,Ye MN X$6S ,'ZYCABZ H MWYXC>6Y!J-R&>(W@'/)G&H$ZC;,%S?'#+4 R/>.B"d M(/*+Y^068-""/SV^(J:%?.(%U8:Y<'D.W&,[:96^U!FP8*FM;;O'Z?U..LA2c M3&#TO>9+$_POV 6!@DD#HHKO4,1(60SJ;#-;W,O8%-X8UN)_OQ6=9,?,OM#44WRWKa M$4YFA'U\=QRN0V8A<'W1IVCJXA;,5WG6QT;Q!0)/$'V<LXN\*%]#4'F\,1BKH7ET0"#$"%U2Z'MH\06IX@;>s M"%_RE4HAXB^95A;HN%^N5HC@^"VM)T=_]Q7AU"-KN#FCR$2HMW:RYW87P0(Rr M8 .L:%I ]I VX)!]97<@,7,5H9$/1VD"^27C%2+H) =GL#:V09)V$'P76'R>q M\QF"0P;<2)(CYV5%49+Q.(%.0"=VTD/849-T4A;]LSHEDAJ]=X'YZ&G 8Q0Jp M4)-VL 5=<)/R%00D^9.6(Y0F592&<93J2&\J@)7P^%[R2!CB: 8@@A<@8RU:o M26==N8#=");3*(XG- >,D2L68RT]9!3#=XZ?MU];:1HJ\)(Q>090.3RE83$Hn M^%;)QD#'D11&D1HT$B8[1#U[Z6E8!ET3" 5%@2]RT@)_2%5SH!QC<#/9!!9&m M.9G0Y6D>!VLUN2T^X#$@P =\\'E>Z1Y_F1N!67!4( 79@V>HYY6XJ9M%P)OPl MQAVK66\JYQZ5&5UKZ7LG)&9@H4PC>09-"0-= '/1Q6THL)S<""2M^2?N 9Oj MD9FWZ)4HX)480I(FR90N:9LUR7-)*9L6:!B#>8@7&#F/ 5Q# CDGT (GH#)Ei M@%ND-)G8>)(VZ9;RE9-IQ),B2I5!R7Y#B5$/Z@9':8IMEV-7-V0Q\'EM!V0Sh M( ,X(&PT,8N@]I&W6#O[$IT'BI*?80+8UWAF!)@+:GT5$9]7 FM#D4<,,J Og M^ADBT)ER( +N86_E:5M"FHR59Z0%*IU)BGU9MBEIOMN9$*R79*-P,SD ,\AA$XVHHZ:@.VAW:>!:0<80: "J5YT:KD\:I#$:M:2JN,UX"BT06]^JOXQ*H'c M-*RPNIC'*GF<*8Z7UQN9IQ9TP*N^:IT5 :VN.JWB4:VAITJ 1WJF=WC-FFT$RI2TYF!C%3?.L4':4F&6M6(9D6%VY6)4IW9 x M-EB%-6)(%S=HH%B,Y5@:I38)$'7\,75CYV(T@+AKF4v MU[BB\;AOH[5N,#=U8[D5(;J:6[KPT08OP#FK>[F+2[H@P .Q6V("$B;9 KJMu M>[N.6Z7X4;L/"['R!52KI7462P.VEU<?EP+,DP// P,TP'/2^S1#4[W7F[U5SCU:[W8.S7Y^P5#\ 1,r M, 71A0(>K +C>Q@!?+[^DKX&W+[ON\"'ZL":\3SNX0.MB0,CI[AFX#3&HKU7q MDS5;TS5?$S93<+D2+!KV6\$X[#5@HST)@ (H,<.3"EWS2[T4C+_;V\-(C (Mp MP<3C7,1VC,%Y?,9[3,($K+Y_W,8Pn M, 97*Z-*9P/!]A*CFGH10YK;@L:.;,()X%$T$DNY]!=? &C?:"R'5@8DTGYk M;,T:/ 6$',?#\\W_*C:-ULJQ!!N(\@5)<0=87(?=@,RP (WD*J'ZR5$H.(%]4@:QO!RSi M+!JU?,MLA-!=1F^\G#O*N!K!C+C$+!KL_,W7S,':'+I!# (YK- 7G=!5RM"F@67'2WLQ (LYN,FN*!.WQZ/1^]-=?1SP<8L-RM4HBS9;f MX'-HTP4N8 '!)))F0(WM]2%+#\S;12-%MC.,=A#5-B'C;)<,=D\YV5Fe M< ;/>!@;5'#XZ6DNS61MC.,7+SJ4!B\ 775G:?T=6US,]C:)T)H-[LC0+,HQDFb MX,$JDK)DT )=_21MP( DP(PG ,I\-YC'=\I1-_VW=ZP6&@+[M'MY^".M-[7a MEM]FL-^\TA;^#>!C+> $_A<&[@/XH^"ES-X>W>!XII\MG=;;0FF:ETOC0MXPz MG=G.\1J'V=">RX +W=#RY;D\AV6@UJ#RQ21B%A!3 5/X 13$)S(;6NH1;$9y MNU=T#6K)I"YXD O$09B_@5Y\+2NEH#;36]MD =@@8+6x M1VD4\P4&U!AE8*<_GB[2X>-L_7G1D>97QE_TY@9R0&9 =E2@FE>&>V18OA1Ow ML.5=CN-?'N;[\05D[B]F?NEI;GWOFH#]>6B38^<'%"9Z_N<]OM9 'NA#3NBFv M8>AD]M93GED9.VQ7'ETL.NGB@3:U+42[[AP\T -.X,Y.KL':XW!>/@=$QW,Eu MQVV>^Z=40 59\ 54$ 1"P 1%H.MY=-[,WD:XL0:(?IVPENP^,.P8W.138.SPt MK#$0]Q5%. 8K6^=W'B8Z ">],88#Y+G."FH?E^SN,;-!+AU\P@8 XB'S+AP8s M]#\^!Y0]M"]'F8 EE^P%%]JCG3;6EW'X8EOY1.ES<&Z)5')<$E@^51%O'N? r M;!O7@%-P3A/,[=(1U =_!?$ ?9E@#8!!TH8.B A9RVE0#?BZ]($/-Yq M,/.E?HMQP *4C.B^IK&BSFGL'%CNU3@.PB';<@4._K]@6A??-T.O;)[O';!FO:CC:(O_7Hn MKN[?&9N;#^PP8)X'Y^[9%.^&0>IX7N\_DA:2,ACZ_K(@O_(G[_)/3?1&C^H'E)$PL3$;=,*#U(Q/9i M;ZQM/W[6_?8?6 I_H^\PW+SO9_XZX'M)?[$K_;D_<^%?2D!$ X!AP/ZY ?RGh M_ZC?>^E_YN+_!4#?0@"7H %$@&!) 3) !TC)6$ $#$^\PH2M+PN8);#@$VP#g M#M#D7< $R #Q =T@1\P!)H2$I@ 3:7ZS9\KQ%1;P)VC"]/.!"4 @;0$Wf M()"Z0.(C@82P*!Q"&[AERD /F %YZ/O%%VZS+>S-"=@")V -)H!WTPA[0 T@e M@17A[0$7<&<#)8Y^"7F^Q@;$-3XH VZ4U/M^@C 1R@%#>-JHGRQZ5P+W$)61=6; .c M %4027#E*%^35#2 R+1 L;1,0< +JP G@'DXP 9@C/A3>Y$ .-&ATD-Q b M0YOS7L;A"6 #Y[#=8$#L) BI$^(K?:])]/7#+A#LO--YPH G)]]@E\$@9I" a M%E !?T(%#$1T\_U"H;RA-V*FSRQ$BEC^].'W$X5C91>50AL($DEAM!F'-2#Vz M/"REA/_;&_(3@4w MB\L1K'\%L D"0J987*;@ R,O! #2D4N6!6]X%447UGQCY'!Q,C_'J,:5(H:v MT WNP+88!T4@"2R+>/ 4A16;8'ML O/:AH%EHE4D;1;U*EITZ6H#S75T!3%Cu MU.B8$?-A%P^^10K10!OG6!'K7M\K-XXUOL;8O(EIPP,P **=MNZRVS!BG;DNt M?P:DV1:<@P)J8Q';7U7C3]T Q[;*DH DZ0IRHES4CL3R+80$5V@0 6+Q7:/Hs MXM96(FK) =:0!>2 &W :296OX2L1+53, *VCJD""5D,>14#-/1SNAJLHC7P1r M<-;B#JP:_B!?Y@ +P&U]3'VMC?(FW%+%1/$V%U$@%N QPRNHB q M5".7]%]W68PY!P(2 0=HT+S@&.""%?)$;BDWZ 6'A+."+FX!,!":.=#B^!-Tp MH30+YQXQ&O3V<'86O@$SD@\OM*9^,W) 0HX,#_#(/46^UB9F#-_62@O"J7=@o M&J?3H5" E21M:0%<[9-6U@['VY=,&V+R3)8V,?/:W!."+ T*ZH(3W+$m M"".>K,66%'!>LO%=R3(@)KE-5Y,.\ 1,V49I!P6*l M@+[2&K4!/)U*8?2G5F46:)6O,@@T@9]%$CSE7@A@5(M2DDKAY"F5D#L4EG_2k M1WX:X!;C_)-\BL_\F4 S: K-H5D5_L7$< Y$TZO4!%&54T+"3M$I39,C,!6:f MH!)>T4L *BSA?C 5G9 WDF;2G"I&02-D%:RB)+RFV3R;:!, L(LYX"[@A6"8e M%W;A!>0.GH%T!H/<+ ..Q7/%#[CI!DK,6# !"F!MMLW?\#;I1=^3>8J)R9$VGB [00!VG/Rz MP"7N-+/ I^>: >1S<);.RZD\46?SK)?NL_U$3_Y@/QG(_%1#[^=#9$\VPCUCy M!?\4GIZ+!BB M,E!.Z@'_: @-(2*T!%*0DNH"3VA*#2%JM 5RD);J M]H3 Tx MALK0&4I#:Z@-O:$X-(?JT!W*0WNH#_VA0#2("M$A2D2+J!$]HD@TB2K1)= 0 && <= 60 not >= 0 || <= 60 Right, so why am I wasting your time... No ones going to try an invalid blank time now are they? --[0244]-- [0245] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/26/91 21:18 (15 lines) Subject: VC uploaded to nic:incoming + new patch Date: Thu, 26 Dec 91 18:14:57 PST From: pmacdona@sanjuan.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Here is a new patch to VC to try checking if someone is currently writing to a tty when a console switch or screen blank is detected. For screen blank, it just waits another 20 seconds and tries again. For console switch, it just fails. So you have to hit function key Fn again. For those of you getting sick of all these patches, I have uploaded lvc.uue (Linux Virtual Consoles) as a single patch to nic.funet.fi. Now it is up to ARL to make it available. --[0245]-- [0246] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/26/91 21:19 (43 lines) Subject: Oops, forgot the patch... Date: Thu, 26 Dec 91 18:16:39 PST From: pmacdona@sanjuan.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi here is the patch to watch for someone using the tty write during screen blank and console switch. I forgot it from last message. table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 inwrite.cdif M*BHJ(&-O;G,N8RYB860)5V5D($1E8R R-2 P,CHQ,CHQ." Q.3DQ"BTM+2!Cz M;VYS;VQE+F,)5V5D($1E8R R-2 P,CHP-CHT-" Q.3DQ"BHJ*BHJ*BHJ*BHJy M*BHJ*@HJ*BH@-3,P+#4S-2 J*BHJ"BTM+2 U,S L-3,W("TM+2T*("!]"B @x M"B @"BL@5]S=')U8W0@*B!T='DI"B @>PH@( EI;G0@v M;G(["BHJ*BHJ*BHJ*BHJ*BHJ*@HJ*BH@-3,W+#4T,B J*BHJ"BTM+2 U,SDLu M-30V("TM+2T*(" *(" ):6YT(&-U2 ]/2!45%E?5$%"3$4H8W5RR **R @(&EF("AI;E]C;VYWPHK(" @:68@*&EN7V-O;G=R:71E*0HK(" @g M>R!B;&%N:V-O=6YT(#T@2%HJ,C ["BL@(" @(')E='5R;CL@"BL@("!]"B @f M("!I9B H8FQA;FME9%]F9R \/2 M,2D*(" @(" @ To: linux-activists@joker.cs.hut.fi In-Reply-To: Peter MacDonald's message of Thu, 26 Dec 91 18:14:57 PST <9112270214.AA16543@sanjuan.UVic.CA> >For those of you getting sick of all these patches, I have >uploaded lvc.uue (Linux Virtual Consoles) as a single patch >to nic.funet.fi. Now it is up to ARL to make it available. Made patches available: nic.funet.fi:/pub/OS/Linux/kernel/lvc.tar.Z arl --[0247]-- [0248] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/27/91 02:51 (18 lines) Subject: setterm.c note Date: Thu, 26 Dec 91 23:48:25 PST From: pmacdona@sanjuan.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Some may notice that setterm -background color doesn't work from the command line, even though it works in the startcons script. Thats true if your using VGA 50 lines with a TERM=console50. There are two ways to get around this. 1) Change VCTERM_AM in setterm.c to "console50" (or whatever other wierd console you are using) or 2) Use setterm -term console -foreground color I have done the first, and uploaded a new lvc.tar.Z to nic. So once again ARL, could you replace the existing one, before hoards of puzzled hackers besiege me. --[0248]-- [0249] daemon@ATHENA.MIT.EDU (jim v5068vm.temple.edu) Linux_Activists 12/27/91 15:12 (18 lines) Subject: Parallel printer support (TODO) Date: Fri, 27 Dec 91 14:54:18 EST From: "jim v5068vm.temple.edu" To: Linux-activists@joker.cs.hut.fi Hi all; Linux is an extremely interesting and well-designed OS!!! Congrats to Lin us et. al.!!! I just installed it on a 31 meg partition on a 210 meg IDE drive on a 486-33 MHz AT bus machine. I was able to get 90% of the system working and comp ile the kernel in jus' a few days. Anyway, is anyone working on lp support? I was able to put a stub in for the lp major real easily in fs/char_dev.c & the parallel I/O seems basic enough from the BIOS listing I have. Does anyone have a FAQ sheet or tutorial on the GNU assembler? I am familiar with Intel syntax but am new to U**x. Also, is anyone working on tape drive support, like for the mountain 60/120 Jumbo? thanks in advance jim wiegand v5068u@vm.temple.edu --[0249]-- [0250] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/27/91 16:04 (16 lines) Subject: lvc.tar.Z (binary) + a few more fixes Date: Fri, 27 Dec 91 12:58:11 PST From: pmacdona@sanjuan.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi ARL: I have uploaded a proper lvc.tar.Z to nic. In it are a few more changes. First attributes should now be being handled correctly, including restoring defaults. Also setterm accepts the just the first 3 letters of commands ie. -background or -bac Also colors or numbers work No difs this time. If you want them, get console.c and setterm.c from nic (generate console.c from dif+0.11 console) --[0250]-- [0251] daemon@ATHENA.MIT.EDU (Ari Lemmke) Linux_Activists 12/27/91 16:07 (12 lines) Subject: lvc.tar.Z (binary) + a few more fixes Date: Fri, 27 Dec 1991 23:04:03 +0200 From: Ari Lemmke To: linux-activists@joker.cs.hut.fi In-Reply-To: Peter MacDonald's message of Fri, 27 Dec 91 12:58:11 PST <9112272058.AA00895@sanjuan.UVic.CA> Peter MacDonald: >ARL: I have uploaded a proper lvc.tar.Z to nic. nic.funet.fi:/pub/OS/Linux/kernel/lvc-3rd.tar.Z arl --[0251]-- [0252] daemon@ATHENA.MIT.EDU (Peter MacDonald) Linux_Activists 12/29/91 01:02 (214 lines) Subject: a select call for linux Date: Sat, 28 Dec 91 21:48:13 PST From: pmacdona@sanjuan.UVic.CA (Peter MacDonald) To: linux-activists@joker.cs.hut.fi Here is an an implementation of the select system call adapted for Linux 0.11. I have done only rudimentary testing on it, but decided to post it, not because I expect too many people will want to use it immediately, but rather to get some feedback. Unfortunately, there are no test programs included. If someone wants to write some test programs, or better still, knows where to get ahold of some already written, that would be great. Myself, I am still trying to size up pseudo ttys, and would rather devote time to that. WARNING: Both the VC patches and this one patch kernel/sched.c But this shouldn't cause any problems. How to use it: 0) Backup your system 1) move select.c to lib/ 2) move sel.c to fs/ 3) patch -p0 < sel.cdif 4) remake 5) reboot --------------------------------------------------------------- table !"#$%&'()*+,-./0123456789:;<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_ begin 644 sel.tar.Z M'YV04HH$(=*D"("#"!,J7,BPH<.'$"-*1 BBH@T:-$ J,@1AD:.%3UN!%DQz M!HT8-2K6B"'#Q@P9,6;,N,'QQHV9&V%,W,FSI\^? .K,H1-&3D4 .&*)TT;\:^,0."x M#IJN<\JD'4,'Q)P\0]6"&!. NP9,+ H5.&# @%9MX899+&31T\(&"XB!'#w M1<4D(-"$L=.53-RN<=GD 2&G#AFS;(G*63-T-PL0;I:"$#,\C-"NH,O@@3.\+_+D;<2NYOX&;=<[:0PKN"/6u M>_+KN[VV6?LZ#&/5SW_WE6/_KE'D()Q11E]SO+$6"&:4T9@888RQA@L**%"%t M&Y')04<=;MBG5Q[/V;555T5U%5U=930'1U)G\-<&6)6-P89KC4&8!%T%KG4:s M".RU!1: =\B1!F-^&=A5;7V=^$:*8:SXG&33#&B6

ZO/-,(Q5?-N:?FF'/F[L,'&KFV-=W(H.]N>P#CJFD?2:D9 $Z w M/P^,"B 6//%#N3%SA%#Q4?QB 8<5LH:[>:BX7Z(A?->^$MW=>L4*WJ2*XKI+v ME.K=^:A!ZKE-QB_9F@L:#V2K\<&+J74H*>\>) AC0BXQ-/P>?Y-OX+B;A^8Ku M7-^LA"N1/L@%A3PJ83YLX-.W()\RR%"(/,1@R&\2B?PKD8#CTYR!)*_(,QS1t MI"FAR*\/-;C[@E, #W=']\5H#P%0 !0PR/^1,,4;DLE[\I:\^O"!5_+IPQS@s M9A;RK,1T&5UP\K@\Q*#+R_*AO/GRON04I7STC0*@\JI\RL#*WQ:IR2O?2N3Rr MR?;Z0,A+\M"\16'+'\+./&;ARS,3O50OWQ3\\K8\I(T"!/)FS"Q/S6_S%D4Dq M;TI4\[L$T\$./(M "2?S;/S\SPZKV;;[2#:=M0Z$6(O@C>/8"3;;T$B\XNEp M$N&\6-*5B@D^7IG; KP'W(6W-07\+RX C[0>\W\@Z?P0_CSNGPVCTH$1@I]o M.Y*[^BI>=ES0%1P<9/I>,-)C%D;YH"[)C]IZM3!Q-JP^8 BP(B.@0'ZU2Q].n M[ Q_4&/ AU&K9,^3[V841)X/?_- _3$4:J"/2_R^[).G]"C# N]U=!=H! 0m MO42//5/TK@(.A]$3)+3$L%KRX2:?"Q?T'M53+U'?S2 ].L"4] @2.B@A$E_l MUM\0*KTIP=+7]*6!\8#3>[4R?6K;TN\W64U.KXJ@0(E+5D_0F_%Q?),=M0(Ok M&('H0DN!0Q>53_HC#>]C3SE[0U8"% 4E1'J;E*T5<3(J846j M4H&P$T7%J5(6Y.CLO/E@V3=/V\/$WLM4!!"D(), E!%^ GMA7?SIEL01@NS,i M$1)-DI-"K!"K/6N?7](0K[U(E-9_!2J".7(>C*DTQ&@SH50G9LQC4$9@ZT]Th M[G8$E)M+S.L4W'0"G %? 9C /IP!)L.9PA_,-O;F>7\&g MR)+B!"U3W@L9M$QZ'UG%99\%0C$.OS0B+?)D/0.3I[U8@MEK1F6$E-[9LP^?f MO<$0VE\AE>Y*3V<7IO#ZE$#T; $NT$J/9'0' ?e MV[<4SCSG &#<%;8]-X+;3QC/O0HAW7,$%WX1D.'O]M)]<%_2$_=W0\/PVR?Wd M*,!RW[PXZL_]'A'=K_8M_HOOXV>;OL\U[c MK][+]YW!>O]9"!#A@I0_W\OWM Q[;]^_]W:[XA7?C9"LK_B0 &P!.,# $K+Vb MN0O%F9\A#"QB ,EJY@@;UY8YGY:NH(<%W1$)I@a M@E12?:EM/IJOYLOYB?Z;#^,P^G: FU_G,ZN94L3CR%R;6%+U0,E8,J$,ML?Fz M1_J!_J#/$ZT]]'@",*:2^J0^H%_B"/IX@$G0$J3Z;7Z\W0> 3_24E0NC H[XF\#P?0$O5^_X[O$RASM4'S4?3[,\2_v M3UN_%G ?=*CBE4&O[[OGRS\QC*\G^][V R-2D#PXR<2/\ OG\ !TP7!'Z!Du M_ >_05,3$/P4"LBO[\<7!+\-T/!3_'# ?D'PWP K?\#/T)PC"W^P;/*S_.D-t MP9\#Q/P;?WW2[Z,$/#_"GW/UJ#MNT%\E_?P1OWX2\C,TT@C1CY_P_ X)0!&As M"*E)_X!"6T?]_'Z/*C%!_0+_U'^Z?/Q*?WP2]2O\BW?)'_87*%'_P[]XJ_PWr MO^02]5O\6C_,W_:_ %%_QZ_UV_QGO]LO\GO]J O7S]"@_ G*@NWWM_Q3_^M$q M:3_=;] T_8L_S#\NH 'CA8(RG6C\4;\\(UXP%YN@QH_PRS->B[MO^P<%%(4.o M@(C#PI%253*BU\:\\-92QHP#F_!6\(NE*IEPJF@?5 21-(",QPT%;A$m M&'LPPQZ/"/:__)H%Z#]'(%AT\/5!+^6,Q*9^1NXF90P!5 #A7IT!2+:IDJAXl M*=!WW OF6_YB@ &FX%X8J;H4#,#VA?D"!S>EB "6+TYPL[.5Q )P?]&_F QPk M]SQ@&T#T70<0HA<";-\Y*;AW!CH(8/ANV"9H*P&2+Q0(T047(/LB3"%KBU+(j M +472;P*8/BN^^50R%]0*389R2NOPFAK"3#:(-J--E@(H0,W5A, %&>FB*:%i M1,!G]@'6E6F*?+9_,Y^Q2#!I9S--FOO,50/DD%?,TLX&_8).R@%,\%7Y0I\Qh MQ+* 4:TXEQED8!&A.:CI1NA%E;N4%D(!"B@^8R1- 6PX/&;>(K7+/0BCI9PNE"QNY(7STH_A2J*!.K1A("/0#U ,W![0c M*CX6FAIK0G/BM- ]$0?N?-H.AEUXKZQ6(@P8Vb M)]Q>KJXWV-A+&4@IHP6" U$9V,#V0*O@[:4/E'O!N\I>?;)-BSE03S3:F 9Fa M 4A?,B_%B4/P9@,54]HL!#D"$T'#UT_,E6.H" B. G,=V\!NH!.@'6@%"QD$z M!,F!PQ_&B4P%W8HA3O9/!7#+2(@0x M## 6'2X!".!.Y9::>BZ\N%YUA@K?"&QER]%"\Z(U<@QUFK#T!1N##34Y4RO*QXX'H50),]Z'/4UOP*D@7] %46]!O=I(EG<9E+\@&N*'5v M!4=-=!)IW=?']E)A(@S>T*P5MY<-G_)*>,4$4.5E MD5UHLOX.SMN\'$RPIVu M8+:"KX,UQ9).%)@+W">(!6=,J,!)8!?J(\@I0&.(!#N"B@HH0!+ YR3R>@BJt M 2#'4&C($BP)Q@3U/"UB> #IP4"(!:"%.%E8E?,;DP.C!.BH!\P.,(:9)S!s M!&6"-,&68'!$-I@FN0G>!I\+UT#=8&N0-P@=! H:16@&DS%@U:G@1:"*4 U\r M%(0+2 THV:"N.*BL. Z: Y6#"(7FH)R$.\C+@#\810X-BX5$ 72AZH#1: HZq M"IZ"]@*=G)NB,QAU4@$LU]A,APH%0+=B- &;GB#KQn M(6R$G#H;A'9N3>$57%/X']PN;A,@X4=K*N@6C!PI (8XH,%&%<4-*U6KMLG:2$]S,TH(9+#<@_^Z A.4@I]PHUUUM*S;6M\)"5k M!M9*LX(4@,PIG. )&PNTH=QO0!8_()!C(:*-NA$",B:%Q[FIQJ706Y I1"@8j M(CB%*$(D!JBP4G@&&!72"TJ%,A<\ %4F52@I5)E0"G4:KD), :P0+M!.X10&i M"64/JD);8:C04KA4(#L@9-ANN=/RJSY"_V%9JR[@AK@='=?6@LZf MP7Q=]2%\H;[0"7 $B##XNJAN"8]\(1-@7VA)B $$S39J,1-R(<30XB$QW!?^e M!I](S(P?&1_"MH?12!3NNA8B \,\P7WI!=;FVG)T>P(HM(Z&?P%C8>5&9]@X0F(8(GJ&7S$7FI,":)@6-!CJb MAY*%A:_Q'=)0:5@M ^0$[)J&X4+($T)!:L@1H!IV%:R&:4,>8=809^@T1!9Va M#5, *D*P(1<-+#8V5,\I#JNX(5*.IS8U;-K=z M#15:C$.D8:,0'0'(44\5;6X\XX0?(%+63S8#$ 5F(:E'Q7KN8 J;#2ISXJ&]XVW6N\P25@T/$)$x M6=PFPT/:7-%PL;#ET, LX%2#RL.46CO,I,3$ 0XT*7H##(X86@ %Y)3KX!1*w M\20&:(Q4G1Y')$A7BB?YO'P8O9+P(0,MMH84<*#X!"MDD<#5(/)0?;@U\Q4,v M ]V'O4&E8/QPZ-"O<$9(*HPBR8XU0K&"BG4^U$9=!?L.V9$3$:4J^>BQHQ?Q@D:"-"P5*$X,,XHOI,C.@6B#*Ap M#N^([<$W22X0+F &<1[."GHK1S$DHL6MX'0TL"*^BNHT0$3,R1!Q=Z/PX)(,o M ?A:2T20 %6"4S@F]!5($MMN13<^5W-BES/:0+GQ;J@2/"]KH;0BN1)H,8KHn M#O&(HZ7!A!T@[%8S>RW\!O<%1 +XWQEQM.2K'N41> NBPZJ8E&B!8$JN)/1?F5 ^+B<B$?,8>T3EU?9@B^A&5!#)k M$^UA3,) (AAQD#A'+"3B".,#]!YJHCPQ9.=(I - $E5B!4'M56A!)(;Y,FMYj M&BQ2WT1PTHCDGTAQR2?&L&B"7$1_XC^1@?,1_"+Z >2(W0HZXA<+H>@=&"8Ni M%!N);L)'X@K *A91;#8=0AQD+AN+(EI+MY%1;$Z$B4:*72@4@$=1**-ID$[>*)L4PXC)QH_B=POQ(%<+LGX4 3(!Y@*SMf M"#O$/78&]P>V V9"+>e M"1-%.C5PDDN0&-@;_ DV%AF#C\5>462Q.8%6W :J%7V*NXJAP]!!>>@>D1ZZd M Z.'?T3?".7I=VA:Y%<\#8DG;[4KCMMDL]B=V:C!DBP$>$2$ OSK58 %@0N&c M ,B!BI.&HM*&#W$(C I&F;X,)T-1 O3K!:!B F\.=( 8HI+K9)A %+LQb M"JV%BL1:5YF+RJ5=4'/Q *:+3*[+(B*P9J;F0DQU%W==,42;0[\@V!0&]&E,a MOLB /ZT]8$/1DC@Y*R^6#K6+O"Z0@*^"8+8&^)>H%W$./0##&FOJO,CD"C"Vz MYE*&B0.W@(&1:0&W<@OT"U!X!$8(3B2,8#ASV $H%-\D_T6$TC+1^6))A(M$y M&-L /@ $8\%PF=A(XQP"[&*(A!RO2H4IL-:U.+\X"M GY$ \83F);_A;3 V&x M;LA1S<+;"V^QQ>)IR0RP%P 3W0%^Q+5(0?BKD(69E*2(_AGTFTL)R7@]-!JJw MW"@@VP,L!@9DR>A_ (#D?.Z)I\1C8@O13I(J8*O)$%6(DT06XEFK>HC1.")Vv M 8<./L/;RLLP:'AE! D<(MR&B:>FX=0N6W@(8;FP !2'*0">(=10MQ@<^1JBu M&<.&7K0U(^*P.?%FI!1^"^M:?XILX1'"<3BPF#.F +Z&>T8V5.#PSS@X%!L*t M&F-HUL)"X]M0;^5H- $L%AB-=T:[DQP B1$XC#1R!"R!%2;@8B;07N#NTS[Hs M_JI_#('>'_!OUMBVP$X<)[Q]QK_I!'0B0\ 2T G$!F"-SC_T0N""<+'NB_X!r M&X^-O D#GB7C?I?RT-\= $V .(A0>#?>Q 2.]D;F8<%1WV@40SAVo M/N8O1,)FH5B"E*(OL3FP#O9@ZB!<5)R=*\MXC18%;Q.H#Y'#( Q00&XGG*%D!#FR[Y,49%R#.C]m M$4>.P*\#E1[%5]!SO#C"V62'1<=]6?YK7\:KZ%K4_I"-4,>HH]1QZC@5X"N(5P 3/OTG JX!&Li MY7X51H;$@03N/E!S( WH-M ;]RK80(6A=[#]@]!8F<1T'(,F Q0@"]#)0 ($h M $<+Q*IMFY-'2A#\,/$-"IH&PS9ZQ'W _)#^J_\]]&8%=9NP1/H/?=!7J/]5g M!+8 RCS6@]W1,$.UU 9R/( #H8P7#H @"N#[*/)Z/*0/'5;E!4-)]Q#YJf M'P4LV4?% !_ /6 &6"UY'XN,V<>4P9(*+3 &6#^*!OX")8,T !_@WV 9X /Te MF<(%#(/W(T= ^Q@HBA-M =2/[$?WH_GQD9=B.$"Z =:/>0(%Y/* DCPXT+/?7"5.BQ$"VH0? "1!!^ AJ,=X /Dc M 4(48 $^ )C@S, '>.HA'_D 6RDQ 1^@[F RV#_B"?IT'4CXH_;1[&!S02.8b M(,,$*$@5) OR ?F"I O< 620MH,R0 WR4W&#S$$^('F04D@0Y )298"-23\^a M(!.00<@!9,I T<(RT$""(4.0%,C, &N -V"&C$"&(460OQ8^RPNC#1_(J4@;V 4&'=!$4R$N8?[6RC"W,$"7)B]",("P40:6R(&/5#_2Z;\#)0*P@,H!*2#Q\CA8]$ [" /1PA"A_G>+C!.Qv M(B<(HH$4')7L]3@HV*7T(-@%T\=EP]=D4/#.&5P==8 )38L)0?VO'$E..$=*u M"H1&185@).YQG# FFT1"(E@01P:D I$A+8"-?$56F?P,4( A0/VO"6".=#&Ht M":)2LXLI4EI-[+ KP$1&%RH"3X#]8-]@'AEN^ U0#.@,=H8BF&s M(&XX(@GB8_VODJ2?+KUXKTCW;!\K BT /:*[HJS9%X2//06X$N2n M&P0&Q\B)Y"/B&K(O4$Q&IAB3V,=XGNC!D> ^4$I.)M$5VCW+9%/JK?:7'.WYm M&J4"KTl MWGR W0HV@=X \. _(C*" )8 QH%G SYR2#B9C$MN"IH%[ H5EG* )PD2,)>,k MG8@BVDD 8%>A"2#9$FUX)_E.JP.BB'.2"F")RGQR",#+< (4K^1TJP-XQWX29MB?A. Li M%?Z3D94*FKS 6]"<[%8 ^_H2"80$026242>@W&10 9QH+X22P ]PYZ%@LF.\h M$&Q]SLDE@$ ID>0TL4Z&&K*3FXR )*G$UJ?"BC(D 9);NZNK :5!A44$J) Qg M0$ "QC(5EE*0J^ $B!X0 =H*4,%?16+@RQ*?)#*.*"<>ORME%!$P)/"DI(E f MG+9]5!!%1^*JPK !)@5*>FA/GQ*%U\00#W6 !02Z6L2$[6d M0YJ49TH1UA!@2AD;D%->$I@ :4H7A:-R2UD$Z%)6!+Z4.P\ZI9TR 6"FW&0$c M!(Z4( $VY28#X;'#,%#V$2@4*JPPY7MLXV$1<%3J*?F4-@%')88O4,D$&%0Fb M*3./ )"N /1!X_!I\!\)*1<>)XO)R P /+G)( (, =8'.A&>R P "D"LW'G@a M>RH"R"!> "Z">Q!%U4(X"%(2%09/R]!>>6 LDGF)/]$G[I!.NL,&>=%#&z MB0*4F,%N140RXM NJR>@I[Z1PX',Y+%AE=#$JD?F$"0J9\*R&0N'-?GV !3Ty M'Z +C+#QHYR07RE@^5=:89949L)K#,"R /GBX%>2[X(-#DL+I(7#*V"PW'ITx M)G$.%4NKE!&2P8%M5%A:88B0:X 29&NNRIAXPL94+,F0:#F2I1HRL88_(%G&w M(24'"O]%C6u M8/0C[SE^I6@ ;%FQ)-^1+2.69TN2Y<,@;0FP!!. +6.6_,K:3FS.92G 40P4t M-H0 9KV97G_*L/*B5%;D*VM:>X@Q26U#19D'&"CA#82374N9I16&Q5 5:2/Ps M*\T.C4OYAR]E2=FDVQ!Z+6L'5 ^O0(,I.:F*0 HP'RP$>Q#+I>+23_6%N6]Tr MCWX5V8B -KXCAY:!!:JD \(.1"+X;?85_Q?J+P,::)#WRp M*_L*_(&+F*#"4*&G$%0T[DZ7]@0;W7B047$[!#P0"M8(\DK_T=IE9#&GV%S^o M*H( Y$L[0_A/*"%G2%\F+IV$*$GWY5:!]6!&S!L "M277<./H+X2V0/O*%>&n M%IP-HCW_Y4.278$M-#N /P05^DOT5/ A ,+WT3W$"BP$OT?21+3A7LFN0%0Lm M")^7\ &99)G+%#D&R$>.'A4#S4DVE/?2QT32P5]:&U1U#DRJ!Z/"U06BW'((l M,*L.8*\:)I]1Z<*H*!P]BX(GNL$!)LH 4L&^'(Q!4;H6SLNV!)ZP5""]=!'$k MV R6ULL8YO:R8[E\Z&'J+XT=+8T]1?GR8";^JU^B) &8+"[V)9T"? F_7!S(j M+\^77DQK@^C2A7D?T%^N*ZL._4L[VP+3;XDZ,!!J+QD5$"]O&**+]\#@HHMYOQ2CC HL%^R*]:7,;;V)1DS?@E'V&76f MJWR9=$PK7OX2?/G&A W$,=$':TP!YML2?(FW; ST%HB7K$0%9GL *4!'C&;&e M,K\="DH]IO&-CXG+O!-<,!F2W@IFPDI"HE+(Q#8A,E]Y>[W1AF*@VX8E(F&:d M,".9*BFOK%@Na MJ;*7 SE_G%E*@ ,P$68TQX1QE3EXG&9&JJz M,>^7_DS])>'2<,E2/"[(,:.9)$N$);QCJ\FB/%PV-!28WDQ.9AZ3A("!J6":y M,_^8&4Q!YA.!D.F#7";ETW=YL&2M_DH;.!@u M 8B41LK@ID6SI5G3[,Z4,@5E1X'(Y4[SB=G*#%N2+.,?0$T9IE"S>VG%!%\>t M-;T:N4RE)OW2JCE\=&IV#<68^LNIIGJ3E[DK:&HR,.N8\DK])>7R=TGO06MBs M-;^;]1#]9CU$1T R2&L&-=>:5"D*YH?IK8G!3$9H,.>:[,RZYCMS!#GOV%ANr M,\>0F021I5VQA+G7;&_V-145*TS )H++GSG8%&\6-@N:$8?J)HBSDMG8- 4&q M1X:; (N/Y@ER#8#<1'4I-R.7"Y$HY:(RN-F%@G%"-$>;(HD:9VY0FBE 6FQ p MG'B<#,W/9FB3N,FI6$(*.3&;D9@!)Z2"4ND_0W*^.)6<'D<>'+>o M.(N!WN<94[:YLG"!FD42',2n M.:6<,X]2)1]AS/G# 6UF.7^<0XL\@)C S@G@_+(L1#25(T&-IFPSSLGD/%E@m M(0F=-DL\YZN2J\#G]'%*-D\69$5(9Y33T!GDHU4"!16=HJ# G5QB8B':= ?Il M!/U5A4YX4G$J0"+:I 7.7%:.+$U.YHFSCG+=+ UX<,PAGGA3&:Rj M,>V6X,LA0.>RJTG@_%_^-P&6S0']YK:3^9#-E&->.+N96,UO)H)S@DG.M"+Ti M+ANDVIY+*SH[#B;%3P,T><@DWVEZRSNNG/G'4Nh M-GV8)8&%YI63FK#DU')R*IH#FL[,Y6$@H_GF3'(R//^Ag M--V<*TV IHFSNAE5M"9(,SN>B)K_RU\D9X&3.f M,JN8PT[SYBTSJ2GM7&]2.U&8[LTP9C#SV=FMB'::+Z>=W4VPYC(3WJ'ME%EPe M._V;]TUEIJ]37'?N,=V:[TYT9B!3Gc M/(D$1,RX *N3N$D+I+C\/0\#J8KWT,GK\'D]K.1,-P>>>L_XB%O1Y$FR1'ERb MSTB9]@(5%KY'"C $^';]<$08<8=E4]R!/N#0C#N /@$@"1+73?.RY9G^D%<*a M%5&23DP^1>R3E?G--%2L7?*;S$R>I0&A:%8F. %(?BX,O82RYU"SEJGS+';Bz M,HF91T^?9](SZ FH@&\.,X^=R4_ZYO(SZBGP/'""+R687\\%9]@3D/G@7&=Vy M,"6<]4[H0'6 8Y#O/&%*,FF3;*C-9^<33"/S% 'T%;R+-*2@I(#J!(S 4K_S'\&+,F2 \O:IP14 /JA7'^^v M/JT-0PL;C 8T_1'Z68"N,AN@-DL;# P4&W6V%('.#2>@)5 "J 54!+"D6H%^u M-W2:+E#JI?USN5FX+&O.0 &7<@X(Z/QE!"H*HH">0*V7(@"&I0\4E6E8Z8 .t M0;$U]PHESQ%T; G+M'DR0;M03M#VY\/R#C %;8'V,!F@'M QZ!'4;-D%!8!^s M01458= =*&, =3>QK#]8-FV<\4\SJ.SS!9H&E5AB(->@>H@VJ'@S -H$S8%6r M0%&@F,X?9+]@"LH!#8)R-Z^@9$4E*"$4#&H(?8+&YD0 &DN_'\.p M0DVA1\!*:/L3UE(&365V0EF95U!8RRPT$!JVM(&6!.&@NM =*,JR%UH%_87.o M0O=R'E"WI2!T>XD+10&@0J&@*\NV!#/4,O *!5AF0RU0'E"Y93'4"WH#)8%Rn M/G6@J="7I?-@&_JS<89Z0-6ALX5W:-UR'.H&+8<60L^AAU H*,V2$QE"TVRDT&9H*I4),l M05^>[M!@*,#@&5JZI(?>0NVA)D_J9N03\^F@XK(4"(BD\*:6:XI.@TWT5%';0#]<(7R/4H*::(? KS#O-&3Zj M++:?A@.GP7>@+/ PR#T@/_> #HA= TK49X"NR$P9!? ^!>P!:%%MW%2(4^C[;#4*%Y4!#D'O4#Z+#.0"$@W9&:TIU(7_5DLe M1@6C%,CY(V73_IA6RS_N'Q,+; '_(Z() %D:V(W^R5"CD]'/*'"4 .D\@!-)d M#.B0IE'-*'1T*_H;78U^(!6A5A;GJ&24.TH9;8Q2($&A1\A, A22!KF$Q$$*c M.A^0*D@Z9]^&%M@;Y8JJ1D\6+D@8Y!,2"^F#O%B>!\2CVU&[:'DT-(KA+$+Bb M7$)$*,@9I!2R/6J%!$22 ::0WP'DXRR%4B$;!8WF1YV0.\@/00\2! D;[8Q&a M1^^C!%(NI)L%.WH8U8[&1C^DLU$*),K2-:H;[9#61[NCYE'MXS?T+$ B!9">z M2,FCTE'O:,H 'DHCS8W6(5VD%=+IZ"-O-&DC]9#B2$&D(D@^9/;Q#[D'R8[Ry M1H.D.E*502$2!G"(=)(""-44WDHXPK?2#+ %H$^^*5MQ8TRCAOO-7-9,T$E\x M-_-&#B(J^1KLA65U-21R 7FY)]w M/[L5< 5;U(.0[3EX:$]VN*H#62EWY^#K4; G[4$<&K9T:H3V9/T/3YJ-'"[Lv MUXH"C$GTY_V-_=4M@!PA<1:.U180HA='ZZ$E=7_M,%D%(X2X YRT8E#_M!1Xu M2BV;AC,F0(2!5#HKV)(^Q$X .Q'*#ZI14.HF_5C>ODBB?C!,06QJ*,>$6(7Tt M%6Z>]0]3Q_63C.C2X'\>!L!'3ZF#9'SJ3VK(%)8Z",<-O0V&@;QR6^EI.4IZs M.\N,?49OJ$$1B.D6S8LV+7JES@3_XAQ 5H$DDr M1GL%CLURJ=+B7$HKK:!Y'->E"#8HBKMT#SD:Q8[ZC]A0WTT;C,*S7DH#U63Rq M$_2EZ]+80;\T72H"^ NP2Z6;YA/%J+E48IK9\)=63 3;>F/-"WJ480V_1Q7&E"3.L/;%/2Z6\P"GHY[;V%j M-.>FK-,ZRL TGM> ])&.0"H"D--BQ.34.=F%(EFV1C.G-U/.J!T#)HZ+9RZ.GEJSE.[:-]4;6HT;9N>+*BGMU/#AN'T4=+7[%94h M(.F@&,C&Z>^492H\/9BV+"JG/@T_Z&U4:6,SO2LY-N&GC('/Z<,T;>HW]9ZFg M3>2G X[J*>X4U+D_?9YR3Z.G?U-.16VT#FJCRA-83^,CY=-W*5GQ<5J?B$SNf M%?F2F\?^PT P+, ;X$/>&@J .C2\(SVB=JE#HYS*3"V6?;J%J;'TKE1 U9[Ze M3;L'0P!.A0LH<',]!0@*30VH_-*.*<6T8G QU9UV2]&CP04DY!K 0;J"]!)5R(')SWJ$9,FXK(7NH>I8K:O+4FG UW:)V41<>,E0:0--"C)J^@(5&a M+CD5--0-RNX4UJ(^I:"R#Y(.S &*@ZR0[*E!/2)P4"53Q(3W233":^>O@A2(z M4/6.Z882ZJE4;8F-4:&R4O6GV5/?Z,84+C QK=^\#Dy M!F^H+E3N:=/"BWJR*#117B:D[L%J"<0TA\K^^Y?P4'.ILY-)JK.ED@H\K4]Tx M!C"IKDD5(2=5(.A)C1* 4N$"HM1!$;V*^3"8'*&F4G>')U24I2NU;#$4(NID(-(*C]AI;E/_9?$v M4VNISM0R0#TUFMHMG9%24]FGUU350B9UI<6">")T4B]CWM1!$3AU3%'0DWFPu M'TVIY514:A\5?CHC7:=0UG*I,9-=*C[U6*I/+:0.t M4Q&I -4;@$#UCE9339NR5#VFSU1:($,UCJL"T6TJSM*1*4=&IG5.:I2#5?EK(K*I"r M3[NG2-.3!095C4DR>*!*5,RJ25CNB)(@4QFDUM$""J D o M")^ 4P.8)[*TEHD3#50,/>L4IT&'@5IS61I3> ^(*3"8=8.G:).2Q(7SE#,-n M$T8#2)P:#XM+65K K$Z>V7:'[!3-*8+S&UF=A)8."*2E8Z=\YD'$.S#R/&F:m M*!N%?LU&A4!AV202]60:-@>F:$_/@' U*YICL7L.D/84U\-:I@K5M@JP$%0(l ML2 5OL_##Z*"GT#O3'L*&L![I@+[)FU2GT!;"3TB5QH:\2*ABLK* AD>0'0 EO.9F83TZ9KD_VI7UU/2+"@+#Fj M(SD%=P6[I\-$SU GJ@B8 $2L,TP%J\G"!& #U2>X5TVL"48DSN4GIJH\B"= i M/LVK3U-!14IPJ-JM( )LK!BE5:^K:-;IL^!MZ4'\5L4.P57H)X?RPTE0LWDZh M-F6B"E#"ITISOS:QP"A!5CTM1H GTDK1(\FUI+)V3@>I+0[60^GP_@F]G$RNg M126?/-8T:YEK:4B:H+']2WB2$]*IEYJ5;08T V)22%&DH%&P**2*.SEV(!,:f M/'((#,95YF1HH,IEK5;0*HBLOXHPZV&A&IDFK:!I5Y.!(P0X JO "N+B.I/Ve M%@&;0,P7Z8!4T)H8J#YX''Z1E-8(I5/A+:&T< $P&/D)d MIP $E2*\I+.TST SB)9F**52XM\HI8X:TBK\:K>#NNb M)S9Y!84C [)1Z_C[VSK6&M>4P@NP(TY@AN!6F#30!&X 9T>TH]K1V$@5:#N:a M6_^M#X'$!;JUQ^:D2N.5! A[X14OU;EMD[?8ZUH-]D07(KD9 A[OQ@7"@!N-z M^6AX%M?XT81DSN?HB_.UJ2)]=+Z!!;.*';;L,O:M^D1]^ E2#J[OU$?*D>*4y M7$%])]=6WXO"Y6KFD_71^@A]*M=90:XO0Q")^_4%^_I\Q#YPFJIOUB?JL_4!x M7(^N5P%AB )!ZFB<\/TE)[B.S8D,@>)%WLH24-),&F0"?(M?(\!UWTILE/[Qw M6Y&N8->#P&2ALD"3.%(!V$05(0K9GZC@HX!9$ L$V.0D"L)H0NZ@[-IV=0/ v M)P8+:=>EGUNA[OIV-0'$72D+YAZ.J)I!(5SMF'AG'$62$.6%DXKY/QM2(K#D9*J+LT&]TZGYQXD/;/THS0Lt M7BT+9E>WJ]51H1=Y'4]-7C6<6,C+JX930;IY%4WB<-2>3D_F0ZIBZ6LU\_H>E;U67J.0M5>QJO/5H+12q M'=FM3U=W*S@)(X#\8PE\^^ROM(0VX]>5_6IN)0/,p M /@ "SG5%P*6#I" @0'X(&4Q#%@-P=!*EP#8(I>L!:(V=( %6_+@\+" 7;!Uo M8%\G'=B80 M #3 '^,!224FP#]C50 96 DMNH!08$,H#*JLZJ Z@ JL#H!@Tn MY(H 13%)$47C!EL48P/H - &.@ R0$4.!PL%",+R8W0 I($>0'6%#<"#90($m M89FP7 <;!-@!FM-T &$"'BP)8 TP&<5P--A$ 0]V"6"%A<+B8)$ 4=@M@!+ "DL&X,'.84&;6%@M+(/#L(8$T &$k M"WBP0P =0(2 !QL$H,*22Q@#/%B=:A,2V <:P.%A%[,V !UL#\,0R8G&PF-@J;)3@!NL#B,/^i M &8 DA<<[ ^ !A"+_8G4 &JQ/X ; -]%%HL#V,4&+'8 EA0Y0"-V\Q,#Z,/2h M8%L#K%A7+"S6%4N+=<7>8EVQNEA7;"_6$*L#N, NY/X1&U@'[#4V)K" _4>Tg M -(/W=B8 #B610"!Q<;28 4+^[@[[!M@!'#/T &(!D8 MI;:0Q#5D<;"$V#9OCF '$8=FPPH1Y;!Q6'_L&N-S$816QDP&/+"H6$BN2+8I1d M8G,<$=DM0"J67**)+ %L8T,7Q]A(;!&@%2N+7<;*b M8INQLMAGK"PV&LN+E11E'GBP0)%=K!(V/P"6C0'$8GT U%A-P@WV"5"(70-La M8J4'0@ =P!H %/L$",2N =RP6 RY;.W+"R"4)9?H!GBP?=@U0 Q@+5N$70/(z M -:R40"Y[ Q@+2L%D,O2 -:R4P = '1!#,N/]7;I !9R(P#O#A[ #4"-O0[+:Hv MF"@.< 9.@4KAL) $4,V"9Y,(+ ,_ 40B$9&<]1EP#%H%DRY[27H6RBJ91)->u M.,4"JEGAPWAJM08[&P&H9FL'E@0EZ5%)->N%M2340s M!<(+V\ZE)11)?I,#K886_=A+P,[::/4BBPXR@!XGR.-.T#!Br M:#<)=X4(@7M6+G!7R-$>:64H_HP]2^N 9*":W5PD:0&0694FF36_<%6 M8D* PYR[$2-1<=Zp M =2Q[-C0Q3N6V"*/C8^6P7=@O;#^6&@N0Y9.FP=M@N;$?V(_N(#^2RAUEG;6)V#;"8==8Vl M9M< CUEG;61V,DM9.,->9ND F5D=P&:6&HN,C<*. 3JS0UC0[!!V-!NK3R@5HP+*$VQV&H1=06j M9!>U.%AW[6EV(?NHC=3V:BFR:UA,+< 6$R.-B&R.J 5KLZL-7V96NPX-K>A5IV4NNKY<$"h M:T6V=EEBK;%V+_NR5=:^89FUA%EH+6)6,4" [=IZ;;^V8-NPK=AV;$NV+=N:f M;<^V:-NTK=IV;^V>-N\K=YV;\NW[=OZe M;?^V@-O K>!V<$NX+=P:;@^WB-O$K>)V<1V To: linux-activists@joker.cs.hut.fi (Linux mailing list) Date: Tue, 31 Dec 91 20:02:55 CST Hello LINUXer's :-), A simple question: Is there a sigsetmask.c? Is sigsetmask() equivalent to ___ssetmask() ? PS. If anyone has a compile shoelace, I'd be very interested in a copy, since making it seems to require Minix. Gratefully, David. -- David Fenyes dfenyes@thesis1.med.uth.tmc.edu University of Texas Medical School Houston, Texas --[0262]--