Subject: Linux-Development Digest #523 From: Digestifier To: Linux-Development@senator-bedfellow.MIT.EDU Reply-To: Linux-Development@senator-bedfellow.MIT.EDU Date: Sun, 6 Mar 94 14:13:08 EST Linux-Development Digest #523, Volume #1 Sun, 6 Mar 94 14:13:08 EST Contents: Re: GOD SPEAKS ON LINUX! (Eternal Darkness) Re: Help! GCC errors (Dave Gardner) Re: Linux msdos File System Bug? (Alex Ramos) Re: Help! GCC errors (Robert Moser) Undefined C library functions: 1. light C shared image (Use (raarts@netland.nl) Re: Help! GCC errors [STUPID IDIOTS ON COMP.OS.LINUX.* GROUPS] (Zeyd M. Ben-Halim) Re: Using COFF-binaries on linux (Alfred Longyear) Re: Help: BASM to GAS, Syntax, Opcode? (Manish Gupta) Documentation of Kernel Clock Magic (Markus Kuhn) 0.99p15j: Caps-lock does no capital-letters (System Administrator) AMD 486DX problem (with Linux?) (Gregory McKesey) Re: TIOCLBIS and TIOCLBIC (Greg McGary) Re: Amiga FileSystem, Anyone? (Steven M. Palm) Re: Specialix driver (Anthony Lovell) ---------------------------------------------------------------------------- From: jake@acca.nmsu.edu (Eternal Darkness) Crossposted-To: comp.os.linux,comp.os.linux.admin,comp.os.linux.help,comp.os.linux.misc Subject: Re: GOD SPEAKS ON LINUX! Date: 6 Mar 1994 10:18:24 GMT : >God@Up.There.Above. Just one question, is God using a Unix platform? : It must be MS-DOS. Or why can people become ill or why do we have wars ? -- No, even worse... By the way God is calling Linux names, he/she must be using something like VMS (Hehehehehehe). Sincerely, Jake Skinner Garcia, Eternal Darkness(tm) ------------------------------ From: dgardner@netcom.com (Dave Gardner) Subject: Re: Help! GCC errors Date: Fri, 4 Mar 1994 21:20:15 GMT Dean Junk (us292121@bulldog.mmm.com) wrote: : Take this as you wish ... piss off! I can't beleive the attitude of some : of the people on this newsgroup. Dean, you're not alone. I started using Linux about a year ago with SLS, before I and many others knew just how broken it was. Many of us had lots of problems and asked lots of questions, most answered much the same way as you got here. Rather than politely either answer the question, or point out where the answer might be found, many Linux 'experts' chose to instead wield their often questionable wit to insult. And nobody, expert or newbie, likes to be insulted; it has nothing to do with the thickness of the skin. They drove a lot of people away from Linux, to either BSD or a commercial *nix, or back to DOS or OS/2, somewhere else where they can get help by asking, rather than getting trashed. This is Not a Good Thing(tm), and if it continues (as it will, no doubt, in at least some quarters), it will ultimately hurt Linux. I hope this doesn't happen because I happen to like Linux a lot, and want it to succeed as more than just a hobbyist OS with a small but devoted and sometimes overzealous club of acolytes. I'd like to see some heavy-hitting commercial AND free/shareware developed for it, and have it become a major player in the Unix market. But it's slowly gaining a reputation that it's got to shake soon, or it will die out. -- ============================================================================== Dave Gardner \ / The views expressed in this message are entirely dgardner@netcom.com -*- my own. I speak for no one else, and no one S. Pasadena, CA / \ else speaks for me .... I think. ============================================================================== ------------------------------ From: ramos@engr.latech.edu (Alex Ramos) Subject: Re: Linux msdos File System Bug? Date: 6 Mar 1994 02:22:28 GMT Andrew J. Piziali (andy@piziali.lonestar.org), quoted out of context, wrote: > If I use the file browser less(1) to examine a file on an MS-DOS file > system, I notice several peculiarities. > First, the less(1) command "G" (position to end of file) displays the first > line of the file on the last line of the screen instead of the last line of the > file. For example, "G" on file "tar.log" on an ext2 file system looks like so: I think you're having trouble with the CR/LF translation. Try piping the file through "perl -lpe {} | less" instead of just "less". -- Alex Ramos * This message is copyrighted material! Louisiana Tech University BSEE/Sr * All rights reserved. No warranty, etc ------------------------------ From: araw@iplab7.health.ufl.edu (Robert Moser) Subject: Re: Help! GCC errors Date: 05 Mar 1994 03:39:30 GMT In article dgardner@netcom.com (Dave Gardner) writes: Newsgroups: comp.os.linux.development Path: usenet.ufl.edu!gatech!howland.reston.ans.net!wupost!csus.edu!netcom.com!dgardner From: dgardner@netcom.com (Dave Gardner) Organization: miloNET Offline, South Pasadena, CA, USA X-Newsreader: TIN [version 1.2 PL1] References: <2l2f36$dn2@master.cs.rose-hulman.edu> <2l51cc$l3v@dawn.mmm.com> Date: Fri, 4 Mar 1994 21:20:15 GMT Lines: 32 Dean Junk (us292121@bulldog.mmm.com) wrote: : Take this as you wish ... piss off! I can't beleive the attitude of some : of the people on this newsgroup. Dean, you're not alone. I started using Linux about a year ago with SLS, before I and many others knew just how broken it was. Many of us had lots of problems and asked I started out with SLS also... also had problems... Now I'm a slackware user lots of questions, most answered much the same way as you got here. Rather than politely either answer the question, or point out where the answer might be found, many Linux 'experts' chose to instead wield their often questionable wit to insult. And nobody, expert or newbie, likes to be insulted; it has nothing to do with the thickness of the skin. I also have to agree. As a group we need to inculcate a more helpful attitude for newbies (on public channels like this one). Of course private maillists are quite a different matter (I've been trodden under with my own ignorance many times on these). I even recall an individual volunteer to act as a filter for the groups, in that he would gently direct the faq and really "green" newbies to the right place. But I don't think anyone ever took him seriously. [munch] I hope this doesn't happen because I happen to like Linux a lot, and want it to succeed as more than just a hobbyist OS with a small but devoted and sometimes overzealous club of acolytes. I'd like to see some heavy-hitting commercial AND free/shareware developed for it, and have it become a major player in the Unix market. You bet!!!! I've got an opportunity to use it as the OS of a medical imaging display station to demonstrate to the administration of my workplace. I want to see it kick !!!@@@!!! (esp. since "they", in ignorance, think that NT is the OS of choice for "highend PC workstations"... bah, humbug, get a life, I mean an OS, I mean an OS with some life in it.). But it's slowly gaining a reputation that it's got to shake soon, or it will die out. I haven't noticed a "rep", but I agree with the aforementioned parts of being more helpful and otherwise tolerant and keeping you !!!@@!!! mouth shut if you've nothing good or helpful to say. [munch] ARAW, aka Robert ------------------------------ From: raarts@netland.nl Subject: Undefined C library functions: 1. light C shared image (Use Date: Sat, 5 Mar 1994 00:18:58 GMT On upgrading to libc 4.5.19 I got the following on almost every command: Undefined C library functions: 1. light C shared image (Use the real one instead.) PLEASE explain to me what this is. If this is a FAQ, or you have any pointers PLEASE email me. Ron Arts raarts@netland.nl ------------------------------ Crossposted-To: alt.pud,alt.stupidity From: zmbenhal@netcom.com (Zeyd M. Ben-Halim) Subject: Re: Help! GCC errors [STUPID IDIOTS ON COMP.OS.LINUX.* GROUPS] Date: Fri, 4 Mar 1994 21:52:27 GMT In article <1994Mar4.161948.26471@mnemosyne.cs.du.edu> crfisher@nyx10.cs.du.edu (I am being repressed.) writes: >In article <2kvr8o$4iv@senator-bedfellow.mit.edu>, >Mitchum DSouza wrote: >>Dean Junk: >> Do one of the following: >> >>1) Read the library release notes TO THE LETTER - EVERY SINGLE SENTENCE. >>2) Read the GCC-FAQ before asking GCC related queries. >> >>Mitch > > WHAT IS THE POINT IN REPLYING IF YOU DO NOT KNOW THE ANSWER? ^^^^^^^^^^^ He DOES know the answer! The answer is in the release notes. > Although it may seem that every newsgroup in the c.o.l.* > series actually have the word flame in them, they do not. I am so > sick of the petty replies and responses I see here all the time. > If you can not help someone then do not bother to even reply. You > do no one any good when you do. All you do is waste resources > and show that you don't even know hot to flame properly. Well other are sick and tire of people asking questions without reading the docs first. The FIRST line of the release note says "IF YOU MISS ONE LINE IN THIS RELEASE THE LIBRARY WILL NOT WORK FOR YOU". How much clearer can things get. It questionable s to what wastes more resources: people who ask questions that are already answered, or those who flame them for not doing their homework before openning their (proverbial) mouths. There is such thing as nettiquette. People are supposed to read any available docs, and browse through the group before asking questions. The flame wasn't as directed at Junk, who by then had figured out the answer, but others who are inclined to ask questions that have been answered repeatedly. > Bah. > >-- >Unless you are born in finland you can't be finnish. > -- --- Zeyd M. Ben-Halim zmbenhal@netcom.com 10479 1/4 Santa Monica Blvd, LA, CA, 90025 (310) 470-0281 ------------------------------ From: longyear@netcom.com (Alfred Longyear) Subject: Re: Using COFF-binaries on linux Date: Fri, 4 Mar 1994 23:58:43 GMT aurel@dali.uni-paderborn.de (Aurel Balmosan) writes: >Hello, >I want to run coff-binaries (from sco-unix) on my linux-system but the only answer >from linux is segmention fault. I have seen (on tsx-11.mit.edu in the file ls-lR) >that there are some ibcs2 and coff library which I could not get from any linux-ftp- >server. >Where can I get this libraries and tools ? To run COFF binaries, you need only the COFF loader. To run iBCS programs, you need the iBCS emulator. The iBCS emulator is being developed. If you wish the development version of the code, then please join the developer's mail list. Instructions for joining the mail list may be obtained by sending an email message to "linux-activists-request@niksula.hut.fi" with the text of "help". The channel for iBCS is called IBCS2. Being able to run COFF binaries is probably not going to get you very much additional functionality. It is the iBCS compatability that you are truely seeking. (I say this because just having the COFF loader is pretty usless in itself. It is like having the ELF loader. Only when they are taken in concert with the emulator do they become useful; at the present time, of course.) ------------------------------ From: manish@ms.uky.edu (Manish Gupta) Subject: Re: Help: BASM to GAS, Syntax, Opcode? Date: 4 Mar 1994 23:46:11 -0500 Thanks to all those who replied to this posting. The answer to my question as told by many is push Offset AC_START /* BASM Syntax */ pushl $AC_START /* Corresponding GAS Statement */ thanks again. manish gupta. -- I call them as I see them. If I can't see them, I make them up. -- Biff Barf ------------------------------ From: unrza3@cd4680fs.rrze.uni-erlangen.de (Markus Kuhn) Subject: Documentation of Kernel Clock Magic Date: Sun, 6 Mar 1994 16:23:37 +0100 Reply-To: mskuhn@cip.informatik.uni-erlangen.de Just if anyone wondered, what all the magic code around the clock support (sched.c) and the _adjtimex() system call does: The new RFC 1589 documents this time and frequency PLL control code. It allows to gradually adjust the time offset as well as the frequency of the system clock to a reference clock (e.g. a radio time normal or a network time normal as with NTP). This allows to let the Linux clock tick with very high precision according to the official time. Markus -- Markus Kuhn, Computer Science student +0o0; University of Erlangen, Germany Internet: mskuhn@cip.informatik.uni-erlangen.de | X.500 entry available ------------------------------ From: root@desaster.sunflower.sub.org (System Administrator) Subject: 0.99p15j: Caps-lock does no capital-letters Date: Thu, 3 Mar 1994 10:23:29 GMT I do not know about the other older versions, but with 0.99pj I can switch on and off the caps-lock-LED on my keyboard only... ...it has no influence on the letters, they are always lowercase... I might not have noticed earlier since I use it so seldom... Normaly the SHIFT-key does the job :-) Is this a common problem with 0.99p15j? Cheers, Michael Will ------------------------------ From: mckesey@imaphics.prior.com (Gregory McKesey) Subject: AMD 486DX problem (with Linux?) Date: 05 Mar 1994 05:42:38 GMT 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. I decided to investigate further, and found a problem with single precesion (ie float) multiplys. The following is a sample program that illustrates the problem. ---cut here-----------------------cut here-------------------------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 (a != (float)x) { printf("Test Failed, this must be an AMD 486DX chip!\n"); } else { printf("Test succeeded!\n"); } } ---cut here-----------------------cut here-------------------------cut here--- This is the output that I obtained on my system: % ./amdtest 1.312500 * 7.999900 =10.499990 1.312500 * 7.999900 =10.499869 Test Failed, this must be an AMD 486DX chip! % The correct answer is 10.499869 rounded off. It certainly is not 10.499990. The a *= b gave an erroneous result. I thought that I may have a defective chip. So I tried running some coprocesser diagnostic software obtained on the net. Of course the chip passed all the test. FYI I tried CHKCOP ver 2.20 from Intel, 87TEST from Microway and MCPDIAG from Advance Computer Graphics. I also looked through some old news postings to see if anyone else might be having these problems. There were a few posts suggesting that some people are having problems with ghostscript. Perhaps all of these people had AMDs also. 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. For those interested my configuration is: AMD 486DX/40 AMI Enterprise III EISA/VESA MB ADAPTEC 1542B controller 16MB RAM Linux 0.99.15 & 0.99.15h gcc 2.5.8 libc 4.5.21 Any help, advice or solutions would be appreciated Greg. -- ____________________________________________________________________ Gregory McKesey (Software Manager) Gallium Software Inc. Tel: (613)721-0902 ext (431) 303 Moodie Dr., Suite 4000 Fax: (613)721-1278 Nepean, Ontario, Canada. gmckesey@gallium.com K2H-9R4 ==================================================================== ------------------------------ From: gkm@tmn.com (Greg McGary) Subject: Re: TIOCLBIS and TIOCLBIC Date: 6 Mar 1994 12:30:56 -0500 Reply-To: gkm@tmn.com | #define TIOCLBIS _IOW('t', 127, int) /* Bis local mode bits */ | #define TIOCLBIC _IOW('t', 126, int) /* Bic local mode bits */ | | This is one of the lines of code that uses TIOCLBIS. | | ioctl(ch->wr.num, TIOCLBIS, LLITOUT) TIOCLBI[CS] are BSD-specific tty modes, as you've no doubt surmised. It's been a number of years since I've hacked this stuff, but my recollection is that none of these modes are unique to the BSD, i.e., there are equivalent modes in the Sys-V and POSIX (Linux uses the POSIX interface) tty drivers. I know that LLITOUT is equivalent to turning off OPOST in termios->c_oflag. You'll have to get ahold of the man page for tty(7), and possibly stty(1) from a BSD system, find the modes used with TIOCLBI[CS], then map them onto the POSIX equivalents found in the termio (or is it termios?) man page. Hmm, it seems I don't seem to have one here on my system, so I don't know if Linux even has a termio man page... If not, the POSIX ioctl interface is derived from System-V, so in a pinch you can probably get by with a System-V version. | | The only other constant that is undefined is F_OK. | | This constant is defined to be 0 in the Ultrix file.h header and is | used to tell if a file exists. This is the line of code where it is used. | | | acc = access(fname.str->data, F_OK); This code works unchanged in Linux, but the file you need to include is . -- Greg McGary (703) 729-6217 gkm@tmn.com 525K East Market Street, #110, Leesburg, Virginia, 22075 ------------------------------ From: smp@agape.sol.net (Steven M. Palm) Subject: Re: Amiga FileSystem, Anyone? Date: Sat, 5 Mar 1994 18:32:00 GMT David Wright (dmw@prism1.prism1.com) wrote: : RJ> I think Amiga disks are physically incompatible with the machines Linux : RJ> normally runs on... : Amiga FLOPPY drives (not the disks) are different than PC floppy : drives, and I suppose that the PC's floppy controller might be incapable of : reading floppy disks in Amiga format. But if you have an Amiga *HARD* drive : there will be no difference between the drive & controller itself and a : standard PC unit. Bah Humbug. I installed numerous PC Floppy drives in Amiga computers and used them just fine in AmigaDOS. It's not the hardware of the drive, it's the hardware of the controller, part of the Amiga's custom chipset. The PC controller just cannot access the floppy drive in the same manner that the Amiga chipset can. ===== Steven M. Palm smp@agape.sol.net Milwaukee, WI FidoNet: 1:154/600 Linux! :) smp@solaria.mil.wi.us ------------------------------ Crossposted-To: gnu.misc.discuss From: alovell@kerberos.demon.co.uk (Anthony Lovell) Subject: Re: Specialix driver Date: Sun, 6 Mar 1994 15:29:31 GMT John Paul Morrison (jmorriso@bogomips.ee.ubc.ca) wrote: : In article , Robert Lipe wrote: : >Re: Specialix drivers. : > : >IMHO: The reason none of us supports LINUX, BSD-386, 386-BSD, NET/2, is : >summarized by the preceding 100 messages. We have proprietary card : >executables that have taken mongo R&D $$$ to develop. As proprietary as : >these executables is the interface as to how a programmer talks to them. : >Given the potential legal problems outlined above (I think there were 75 : >different interpretations in those 100 messages), most of us are willing : >to "just say no" and focus in a market w/o these hassles. : If this is about downloading code to the board, I wonder why noone complained : about the Digicom/Cardinal softmodem firmware downloader. I'd be inclined to agree with you here, the downloaded code on the board is as much a part of the card as an eprom image on a modem card . -- anthony ============================================================================== alovell@kerberos.demon.co.uk | If at first you don't succeed | alovell@cix.compulink.co.uk | Get a Bigger Hammer ============================================================================== ------------------------------ ** 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 ******************************