[5784] daemon@ATHENA.MIT.EDU (Digestifier) Linux Digest Archive 03/08/94 10:35 (572 lines) Subject: Linux-Development Digest #528 From: Digestifier To: Linux-Development@senator-bedfellow.MIT.EDU Reply-To: Linux-Development@senator-bedfellow.MIT.EDU Date: Tue, 8 Mar 94 10:13:13 EST Linux-Development Digest #528, Volume #1 Tue, 8 Mar 94 10:13:13 EST Contents: as86/ld86 for sparc cross-compiler anywhere? (John Ladwig) Re: program runs fine in xxgdb, but not in xterm! (Stupid me!) (David Fox) Re: Tired question (PS/2 availability) (Rob Janssen) Re: effectiveness of cache ram? (Volker Otto) Re: AMD 486DX problem (with Linux?) (Hans Christoph Rohland) [Q]: Tool to make X-windows programs?? (Kraen David Christensen) Re: Tired question (PS/2 availability) (Kai Henningsen) Gated ported to Linux. (Arsenio Monteiro dos Reis - lisbbs SU) Re: boottime in kernel-variable (Nick Holloway) boottime in kernel-variable (Kai Fritscjh) Re: AMD 486DX problem (with Linux?) (Hans Christoph Rohland) Re: LINUX FOR SUN (Nicholas Ambrose) Fortran g77 (Ferny) Small pre-1.0 problem (Kevin Lentin) Re: Context switch for pthreads (Marino Ladavac) Re: [Q]: Tool to make X-windows programs?? (Christian Moen) Re: as86/ld86 for sparc cross-compiler anywhere? (Peter Holzer) ---------------------------------------------------------------------------- From: jladwig@soils.umn.edu (John Ladwig) Subject: as86/ld86 for sparc cross-compiler anywhere? Reply-To: jladwig@soils.umn.edu Date: Mon, 7 Mar 1994 16:43:27 GMT Thanks to the gcc-2.4.5 info pages and the Linux GCC-faq, I now have a working cross-compiler on my sun4c machine which generates nice code for my Linux box at home. Many thanks to those who made building the cross-compiler possible (and not all that painful). Now, there's only one thing holding me back from trading my Linux development kit for TeX (limited diskspace on the home box); kernel builds. as86/ld86 to be precise. I checked into the original bin86 and the recently released bin86-0.1 distributions, and see that cross-compiler support is desired, but not implemented. I'm not likely to undertake the project myself at this time, but I tought it was worth a public query. Anyone got a working cross-compiler version on sun4c or other big-endian machine? Can I have a look at the mods? -jml -- UMN Department of Soil Science; St. Paul, MN Internet: john.ladwig@soils.umn.edu Fidonet: John Ladwig 1:282/341 GS (1.01): d* -p+ c++ l++ e+ m+ s n++ h--- f g+ w+ t r- x* ------------------------------ From: fox@graphics.cs.nyu.edu (David Fox) Subject: Re: program runs fine in xxgdb, but not in xterm! (Stupid me!) Date: 07 Mar 1994 20:40:42 GMT In article <2lfeql$en9@louie.udel.edu> mvkasich@eos.ncsu.edu (Manoj Kasichainula) writes: ] Thanks for all of your help! With some help, I've found the problem. ] Apparently, there is a GNU program called "test" wich I had never heard ] of. Just a note - the test command has been part of Unix for a long long time. It is not a GNU program. It is also known as "[". ------------------------------ From: rob@pe1chl.ampr.org (Rob Janssen) Subject: Re: Tired question (PS/2 availability) Date: Mon, 7 Mar 1994 22:24:36 GMT Reply-To: pe1chl@rabo.nl In <5KNSTvZEcsB@khms.westfalen.de> kai@khms.westfalen.de (Kai Henningsen) writes: >rob@pe1chl.ampr.org wrote on 03.03.94 in <1994Mar3.091839.3976@pe1chl.ampr.org>: >> But is it so much easier to program DMA and disk controllers on a 370? >Well, in a word: yes! >For a somewhat longer explanation: there isn't really something like PC >DMA or disk controllers. On a 370, you use "channels" (I/O coprocessors) >by giving them a "channel program" (a linked sequence of data transfer >commands, somewhat like the Mac SCSI Manager). Then you simply start those >and wait for completion. I/O addressing works by every device having one >12-bit-address, which is used for communication with the channel. >The channel then does all the ugly details for you. I know that it works like that. Of course there is always a level where programming is easy. (like calling BIOS on a PC, or accessing /dev/hda in Linux) Of course there are DMA channels and disk controllers on a 370, and they need to be controlled by code as well. To be on a comparable level, you should talk about the (micro)code that makes the channel processors do their work... Rob -- ========================================================================= | Rob Janssen | AMPRnet: rob@pe1chl.ampr.org | | e-mail: pe1chl@rabo.nl | AX.25 BBS: PE1CHL@PI8UTR.#UTR.NLD.EU | ========================================================================= ------------------------------ From: volker@cs.sun.ac.za (Volker Otto ) Subject: Re: effectiveness of cache ram? Date: 7 Mar 1994 23:01:13 GMT If anyone's interested I have run the following tests. SHASTA based system 486DX2 66 16MB RAM (4*4MB Simms) compilation of Linux kernel via NFS LAN Adapter NE2100 clone. compile time 28 minutes. SIS EISA based system 486DX2 66 16MB RAM (1*16MB Simm) compilation of same kernel via NFS LAN Adapter NE2000 clone. compile time 23 minutes. BTW the EISA board has 256k Cache RAM. In my eyes the SHASTA based machine should have the upper hand, after all it's got a bus master based LAN card but still it was substantially slower than the EISA board. Under DOG/Windows the SHASTA shows up to be the quicker of the two when running various benchmarks. I should have rather gotten 8 * 1MB simms and tested that as well since at this stage the SHASTA only has one bank of RAM ie. no interleaving, but the same is true for the EISA board. At the end of the day, as far as I'm concerned CACHE RAM can be a good thing if implimented correctly, the SHASTA based board however can also perform quite well and is, at least in this country, substantially cheaper than the SIS EISA board. Having run various benchmarks in the past has shown me that the SIS board is one of the quicker around. If anyone's interested I will conduct more tests and post the results. ------------------------------ From: hrohlan@gwdu03.gwdg.de (Hans Christoph Rohland ) Subject: Re: AMD 486DX problem (with Linux?) Date: Mon, 7 Mar 1994 18:30:33 GMT Gregory McKesey (mckesey@imaphics.prior.com) wrote: : I have found an annoying problem with the AMD 486DX chip and : Linux that is leading me to believe that there may be a compatibility : problem with this chips math functions. One reported symptom is : that ghostscript dies during initialization. While trying to track : down the problem I booted my kernel with the no387 option (using Lilo). : To my surprise ghostscript worked in this configuration. : Anyways, I was hoping that someone else with an AMD 486DX : could verify that this is an AMD problem (or whether it is just : limited to me :( ). If someone also had another OS/Compiler : combination to ensure that this is not just a AMD486DX/GCC/Linux : problem. This is obviously no AMD Problem! I get a similar error with an Intel 486DX66 (Linux 0.99.15 from Slack 1.1.2). The testprogram for AMD works fine but ghostview gives the following error: Unrecoverable error: typecheck in setstrokeadjust Operand stack: 0.988235 0.992157 0.996078 1.0 true gs sometimes works, sometimes failes... Perhaps it has something to do with the swapping mechanism? I always run with low memory when starting ghostview... Christoph ------------------------------ From: kdc@iesd.auc.dk (Kraen David Christensen) Subject: [Q]: Tool to make X-windows programs?? Date: 07 Mar 1994 17:09:51 GMT Is there a tool-program for linux that helps me in designing my own windows for a program running under 'openwin'. I am looking for a tool I can use to (fast and easy) draw some windows and then let the program do some C/C++ code that I can use in my own application-program using these windows. On our university we have a program called GUIDE running on our SUN's and it does what I am looking for. Is there a such tool out there for linux-openwin?? and if yes I would appreciate to hear where to get it. best regards Kraen David Christensen -- / Kraen D. Christensen ------------------------------ Date: 06 Mar 1994 15:47:00 +0100 From: kai@khms.westfalen.de (Kai Henningsen) Subject: Re: Tired question (PS/2 availability) rob@pe1chl.ampr.org wrote on 03.03.94 in <1994Mar3.091839.3976@pe1chl.ampr.org>: > But is it so much easier to program DMA and disk controllers on a 370? Well, in a word: yes! For a somewhat longer explanation: there isn't really something like PC DMA or disk controllers. On a 370, you use "channels" (I/O coprocessors) by giving them a "channel program" (a linked sequence of data transfer commands, somewhat like the Mac SCSI Manager). Then you simply start those and wait for completion. I/O addressing works by every device having one 12-bit-address, which is used for communication with the channel. The channel then does all the ugly details for you. Kai -- Internet: kh@ms.maus.de, kai@khms.westfalen.de Bang: major_backbone!{ms.maus.de!kh,khms.westfalen.de!kai} ## CrossPoint v2.93 ## ------------------------------ From: arsenio@uc.pt (Arsenio Monteiro dos Reis - lisbbs SU) Subject: Gated ported to Linux. Date: Mon, 7 Mar 1994 10:11:26 GMT [ Article crossposted from comp.os.linux.admin ] [ Author was Arsenio Monteiro dos Reis - lisbbs SU ] [ Posted on Fri, 4 Mar 1994 17:21:53 GMT ] Hi, i'm using linux to connect two LANs, i need to spread RIP information and as far as i know gated is the right tool to do so. The problem is that i've tryed to compile gated and nothing, there's allways some error. It seems to me that gated and linux don't work together. If you know anything about it, or know any alternative to gated, please email me. Thanx. -- _ /_| / |rsenio Reis arsenio@lisbbs.uc.pt Laboratorio de Informatica e Sistemas Quinta da boavista lote I, 1 3000 Coimbra /---------------------------------------\ Portugal < Living in a box, a Linux Box. > \---------------------------------------/ -- _ i /_| arsenio@ciunix.ci.uc.pt / |rsenio Reis arsenio@lisbbs.uc.pt Laboratorio de Informatica e Sistemas Quinta da boavista lote I, 1 3000 Coimbra /---------------------------------------\ Portugal < Living in a box, a Linux Box. > \---------------------------------------/ ------------------------------ From: alfie@dcs.warwick.ac.uk (Nick Holloway) Subject: Re: boottime in kernel-variable Date: Tue, 8 Mar 1994 09:55:08 GMT In kai@beholder2.rz.uni-mannheim.de (Kai Fritscjh) writes: > As the subject line says, I need the time, when the system was started > to calculate time differences since system start up. Have a look in /proc/uptime -- the first number is the number of seconds that the system has been up. If you really want to grub around in the kernel, 'jiffies' contains the number of clock ticks since the system has been up, and the clock ticks every 1/100 second. BTW: Now that /proc/kstat exists to read the cpu states from which the idle time can be calculated, does /proc/uptime also need to have the idle time in it? I would say not. -- Nick Holloway | `O O' | alfie@dcs.warwick.ac.uk, alfie@warwick.UUCP, [aka `Alfie'] | // ^ \\ | ..!uunet!mcsun!uknet!warwick!alfie ------------------------------ From: kai@beholder2.rz.uni-mannheim.de (Kai Fritscjh) Subject: boottime in kernel-variable Date: 08 Mar 1994 10:31:52 GMT Hi, As the subject line says, I need the time, when the system was started to calculate time differences since system start up. I need the kernel-variable, has the startime SUN-OS delivers the starttime in the kernel-variable "_boottime". What is the similar name in Linux ? Thanks, Kai. -- ======================================================================== Kai Fritsch Network Management Group Computing Center Voice : ++49-0621-2921434 University Mannheim E-Mail: kai@beholder2.rz.uni-mannheim.de L15,16 ======================================================================== ------------------------------ From: hrohlan@gwdu03.gwdg.de (Hans Christoph Rohland ) Subject: Re: AMD 486DX problem (with Linux?) Date: Tue, 8 Mar 1994 09:58:39 GMT I wrote: : This is obviously no AMD Problem! I get a similar error with an Intel 486DX66 : (Linux 0.99.15 from Slack 1.1.2). The testprogram for AMD works fine but This was not true! I checked only the manual for the main board and asked the person who installed the board. Now I looked for the cpu and it is an AMD! The test program was successful but buggy: The cast in the final test is double to float and should be float to double! Down the corrected test program. Christoph ================================ cut here ===================================== main() { float a=1.3125; float b=7.9999; double x= 1.3125; double y= 7.9999; printf ("%f * %f =", a, b); a *= b; printf ("%f\n", a); printf ("%f * %f =", x, y); x *= y; printf ("%f\n", x); if ((double) a != x) { printf("Test Failed, this must be an AMD 486DX chip!\n"); } else { printf("Test succeeded!\n"); } } ------------------------------ From: na2@doc.ic.ac.uk (Nicholas Ambrose) Subject: Re: LINUX FOR SUN Date: 8 Mar 1994 11:43:31 -0000 In article , armb@setanta.demon.co.uk (Alan Braggins) writes: |> In article <2l1tuc$8nt@ifi.uio.no> gunnarr@ifi.uio.no (Gunnar Rxnning) writes: |> > Probably, but there are an ongoing port to the 680x0 architechture |> |> But the machines listed ("IPC, IPX, Classic, LX, etc.") are not 680x0 Suns. |> -- |> Alan Braggins armb@setanta.demon.co.uk abraggins@cix.compulink.co.uk |> "Any technology distinguishable from magic is insufficiently advanced" True, but after the first port the next is easy(er?) :) Nick -- Never offend people with style when you can offend them with substance. -- Sam Brown, "The Washington Post", January 26, 1977 ------------------------------ From: FernyM@pc64.maths.bris.ac.uk (Ferny) Subject: Fortran g77 Reply-To: Mark.Fernyhough@bristol.ac.uk Date: Tue, 8 Mar 1994 10:56:40 GMT Does anyone know how long before the gnu f77 fortran complier will be ready? If it is still in development is there anyway of getting a test version to experiment with. Thanks in advance Mark -- ============================================================================== | Ferny (Mark Fernyhough) | Email: Mark.Fernyhough@bristol.ac.uk | | Dept Maths, Uni of Bristol | or root@pc64.maths.bris.ac.uk | | Bristol, Uk. | Tel: (0272) 303319 | ============================================================================== ------------------------------ From: kevinl@bruce.cs.monash.edu.au (Kevin Lentin) Subject: Small pre-1.0 problem Date: 8 Mar 1994 12:06:13 GMT I have just compiled pre-1.0 and have a strange problem. I've never seen it before. My /proc/version contains: Linux version pre-1.0 (root@krayzee) #87 Tue Mar 8 21:01:21 EST 1994 [87 rebuilds, that's sick!] My /etc/issue contains (generated from /proc/version in rc.local): Linux version pre-1.0 (root@krayzee) #87 Tue Mar 8 21:01:21 EST 1994 BUT muy virtual consoles say this above the login prompt: Linux version pre-1.0 (rootrayzee) #87 Tue Mar 8 21:01:21 EST 1994 Note the contents of the brackets. Where did those 2 characters disappear to? [486/dx50, 32 meg ram, 2xide, 1xSCSI, T130B controller, cluster patches] -- [==================================================================] [ Kevin Lentin |___/~\__/~\___/~~~~\__/~\__/~\_| ] [ kevinl@bruce.cs.monash.edu.au |___/~\/~\_____/~\______/~\/~\__| ] [ Macintrash: 'Just say NO!' |___/~\__/~\___/~~~~\____/~~\___| ] [==================================================================] ------------------------------ From: lan_lada@aaf.alcatel.at (Marino Ladavac) Subject: Re: Context switch for pthreads Date: Tue, 8 Mar 1994 13:19:40 GMT dminer@nyx10.cs.du.edu (Dan Miner) writes: : In article <2ku1ct$igp@meaddata.meaddata.com>, : Peyton Reed wrote: : >In article <2klvbb$5b9@genesis.ait.psu.edu>, donadio@mxd120.rh.psu.edu (Matthew Donadio) writes: : >|> Christopher Andrew Smith (z1g192@rick.cs.ubc.ca) wrote: : >|> : As one of my currrent projects, I am attempting to port a package called : >|> : pthreads ( for preemptive threads ) to Linux. Most of the code should be : >|> : relatively straightforward to port, since it is written in Ansi C, but : >|> : >|> You shouldn't have to do any porting. The file : >|> sipb.mit.edu:/pub/pthreads/pthreads-1.??.tar.gz : >|> has a linux port the should work with pl15. I haven't had time to test : >|> it thouroughly, but all the built in tests seemed to work. : > : >I tried ftp from anonymous@sipb.mit.edu, bot got "Anonymous ftp not allowed." : >Is there another site for this, or another method at this site? : > : >Thanks. : > : >Peyton : > : : That's odd.. I got 1.19 from there a couple of days ago. Maybe : I should upload it to the linux archives? :) [BTW, I've not : check it for "working" order. :)] : : Dan Same here. However, I did look at the source (not too thoroughly, though :) and I *think* that the package is non-preemptive. P-threads stands for POSIX (1003.?, I think) thread package. As such, it seems to use setjump/ longjump to switch context. Reschedule seems to be called from within the p-thread kernel (syscalls, etc,) or manually (on heavily compute-bound threads.) It would be very interesting to verify whether it is true. If the package really *is* non-preemptive, it would be very interesting to add pre-emption. As a matter of fact, I might actually do just that (if I manage to find the time--not very likely :( .) Anyone interested to give a hand?[1] /Alby [1] "Give the man a hand." RoboCop 1. -- Proof by Intimidation: "I'm bigger, therefore I'm right." noone@nowhere.in.particular ------------------------------ From: christim@ifi.uio.no (Christian Moen) Subject: Re: [Q]: Tool to make X-windows programs?? Date: 7 Mar 1994 18:36:11 GMT windows for a program running under 'openwin'. I am looking for a tool I can use to (fast and easy) draw some windows and then let the program do some C/C++ code that I can use in my own application-program using these windows. On our university we have a program called GUIDE running on our SUN's and it does what I am looking for. Is there a such tool out there for linux-openwin?? and if yes I would appreciate to hear where to get it. Please take a look at ParcPlace's ObjectBuilder and ObjectInterface available for free on Linux. Binaries are available from sunsite, tsx-11 and funet. If you need written manuals for this product, try contacting ParcPlace. -- / Christian Moen - christim@ifi.uio.no - http://www.ifi.uio.no/~christim/ \ \ Fjellbirkeland 21A 114, N-0864 Oslo, Norway - Tel: +47 22 187103 - *<8O) / ------------------------------ From: hp@vmars.tuwien.ac.at (Peter Holzer) Subject: Re: as86/ld86 for sparc cross-compiler anywhere? Date: 8 Mar 1994 14:29:29 GMT jladwig@soils.umn.edu (John Ladwig) writes: >Thanks to the gcc-2.4.5 info pages and the Linux GCC-faq, I now have a >working cross-compiler on my sun4c machine which generates nice code >for my Linux box at home. Many thanks to those who made building the >cross-compiler possible (and not all that painful). >Now, there's only one thing holding me back from trading my Linux >development kit for TeX (limited diskspace on the home box); kernel >builds. as86/ld86 to be precise. I checked into the original bin86 >and the recently released bin86-0.1 distributions, and see that >cross-compiler support is desired, but not implemented. I haven't tried to compile or even run them on a big-endian machine, but from what I remember from the source, endianness should not be a problem, since the programs never write ints directly to a file, but use conversion functions. You may have to change a few defines, though. hp -- _ | hp@vmars.tuwien.ac.at | Peter Holzer | TU Vienna | CS/Real-Time Systems |_|_) |------------------------------------------------------------------------ | | | It's not what we don't know that gets us into trouble, it's __/ | what we know that ain't so. -- Will Rogers ------------------------------ ** FOR YOUR REFERENCE ** The service address, to which questions about the list itself and requests to be added to or deleted from it should be directed, is: Internet: Linux-Development-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development) via: Internet: Linux-Development@NEWS-DIGESTS.MIT.EDU Linux may be obtained via one of these FTP sites: nic.funet.fi pub/OS/Linux tsx-11.mit.edu pub/linux sunsite.unc.edu pub/Linux End of Linux-Development Digest ****************************** --[5784]--