Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA01759; Sun, 3 Dec 95 05:19:59 EST Received: from SENATOR-BEDFELLOW.MIT.EDU by MIT.EDU with SMTP id AA13223; Sun, 3 Dec 95 05:18:55 EST Received: (from root@localhost) by senator-bedfellow.MIT.EDU (8.6.12/2.3JIK) id FAA14254 for Linux-Development-System-Dist@senator-bedfellow.mit.edu; Sun, 3 Dec 1995 05:14:03 -0500 Message-Id: <199512031014.FAA14254@senator-bedfellow.MIT.EDU> From: Digestifier To: Linux-Development-System@senator-bedfellow.MIT.EDU Reply-To: Linux-Development-System@senator-bedfellow.MIT.EDU Date: Sun, 3 Dec 95 05:13:58 EST Subject: Linux-Development-System Digest #80 Linux-Development-System Digest #80, Volume #2 Sun, 3 Dec 95 05:13:58 EST Contents: Re: Where the offical place for libc? (Joseph Vigneau) Re: Fork, shmget, etc. (Thomas Koenig) REAL-TIME (Evgeny V Leybzon) Re: CTRL-ALT-DEL under XFree86 (Albert Cahalan) module kernel driver problem (Jay Goldberg) Downgrading libc (Theodore Buswell) Bug in getserv*() in libc 4.7.2 (and probably the rest too) (Rick Cochran) Can console do a VT220 emulation? (Christoph Lameter) Info on the kernel (Kristian Nilssen) How do you compile an old module? (Thomas Koenig) Kernel panic in 1.3.45 (CM206 & (Ioannis Schoinas) Re: old aout binaries (Patrick J. Volkerding) Re: PLIP: not detected. My system, or bug in 1.2.13? (M.Buchenrieder) Re: [kernel patch] Interface-based firewalling for point-to-point links (Matthias Urlichs) Re: kernel 1.3.45 and PPP --> not working :((( (Ronald S. Maston) Re: Weak Thread Support: Linux Weakness ? (Tim Bass) /proc filesystem permissions (Christian Evans) HELP - CDROM (acdu31a=0x340) not recognised in 1.3.xx kernels ! (Henrik Soderstrom) HELP! aha1542/dx4-120 problems! (Fairlight) ---------------------------------------------------------------------------- From: joev@pyramid.res.wpi.edu (Joseph Vigneau) Subject: Re: Where the offical place for libc? Date: 3 Dec 1995 01:08:15 GMT In article <49prlm$4vm@news.ox.ac.uk>, Daniel Barlow wrote: > >5.0.9 _is_ the most recent update. 5.2.x is beta code for testers to >test. Now, what exactly is this? The GNU glibc is up to version 1.0.9, and libg++ is up to 2.7.1... Are these just specialized versions for Linux? -- joev@wpi.edu WPI Computer Science '97 Linux! ------------------------------ From: ig25@fg70.rz.uni-karlsruhe.de (Thomas Koenig) Subject: Re: Fork, shmget, etc. Date: 2 Dec 1995 20:25:10 +0100 Reply-To: Thomas.Koenig@ciw.uni-karlsruhe.de In comp.os.linux.development.system, gbutler@Phoenix.kent.edu (Butler Gerald E ) wrote: > I'm new to Linux programming ( and Unix programming for that matter ) >and am trying to learn how to implement child processes & such. Does anyone >know of a good source of info, other than the man pages, that gives good >explanations and perhaps some examples? Stevens, "Advanced Programming in the UNIX environment". That belongs in everybody's bookshelf :-) -- Thomas Kvnig, Thomas.Koenig@ciw.uni-karlsruhe.de, ig25@dkauni2.bitnet. The joy of engineering is to find a straight line on a double logarithmic diagram. ------------------------------ From: evl1@ritz.cec.wustl.edu (Evgeny V Leybzon) Subject: REAL-TIME Date: 29 Nov 1995 12:43:32 -0600 Looking for real-time Linux info! Thanks! ------------------------------ From: albert@krakatoa.ccs.neu.edu (Albert Cahalan) Subject: Re: CTRL-ALT-DEL under XFree86 Date: 03 Dec 1995 03:37:49 GMT >>>>> "A" == Aurel Balmosan writes: >>> Hi, I am searching for a patch that enables the CTRL-ALT-DEL boot key >>> under XFree86. (I think a patch in the keyboard driver that disable >>> the reassignment of this key combination should work) >> I have it at http://www.ccs.neu.edu/home/albert/linux.html. >> Use Lynx or Mosaic to get it. > Thanks for your reply, but I was unable to find the keyboard > patch on your WWW site. What I have found was a video-kernel > in a very ALPHA state. I got it but I have not read the manuals > yet. So my question is: Can I install the video-kernel and my > XFree86 will work without problems (I am using an ATI Mach32 > 2M-vram). Also can I use the CTRL-ALT-DEL to shutdown my linux? 1: Wrong link. The patch is labled 'SAK' and does not require the kernel video drivers to work. 2: You can install the video stuff but you need to write your own ATI Mach32 support. Please do! The two things are not much more related than they are to the msdosfs patches also on my web page. -- Albert Cahalan albert@ccs.neu.edu ------------------------------ From: jayg@iwl.net (Jay Goldberg) Subject: module kernel driver problem Date: 29 Nov 1995 16:10:11 GMT I am trying to access a card in my PC with a Linux module kernel driver. The card is at 0xd400 but any calls to inb and outb using that address or the few addresses above it don't look like they are accessing the card at all. I have debug in the driver looking at the data coming from the card so I am sure that it's not a transfer to user space problem. A friend of mine has the exact same problem with a different card. So my questions are: Can you even write a loadable module kernel driver in Linux to access a card? If you can, then am I addressing the card properly? If I am addressing the card properly then what am I doing wrong? any clues appreciated -- Procrastinate now! Jay Goldberg jayg@accessware.com jayg@iwl.net http://www.tlmworks.com/People/jrg/jhp.html http://www.iwl.net/customers/jayg ------------------------------ From: tbuswell@bio.bu.edu (Theodore Buswell) Subject: Downgrading libc Date: 3 Dec 1995 00:13:31 GMT I'm having trouble backing down my a.out libc. Previously it had been at 4.7.2, and I'd like to step down to 4.5.26. So far I have removed the 4.7.2 version and run '/sbin/ldconfig -v' so that libc.so.4 points to /lib/libc.so.4.5.26. Now, I've got a hello world program that when I ldd on it I get the following (even after a re-compile): libc.so.4 (DLL Jump 4.7pl2) => /usr/i486-linuxaout/lib/libc.so.4.5.26 Why does it say "Jump 4.7ps2" still? Trivial experimenting tells me that no matter what I say the current libc.so.4 is, ldd still reports that it needs 4.7pl2. What do I need to do in order to get it to accept 4.5.26? Any thoughts appreciated.. -Ted ------------------------------ From: rick@msc.cornell.edu (Rick Cochran) Subject: Bug in getserv*() in libc 4.7.2 (and probably the rest too) Date: 1 Dec 1995 15:34:51 GMT getservent() treats s_port as a short: serv.s_port = htons((u_short)atoi(p)); but getservbyport() treats it as a long: port = htonl (port); causing getservbyport to fail miserably. It is declared as an int in /usr/include/netdb.h. It used to work, as of libc 4.6.27, but I haven't checked the source for that yet. -Rick -- |Rick Cochran 607-255-7223| |Cornell Materials Science Center rick@msc.cornell.edu| |E20 Clark Hall, Ithaca, N.Y. 14853 cornell!msc.cornell.edu!rick| | "Workstations - I bet you can't eat just one!" | ------------------------------ From: clameter@miriam.fuller.edu (Christoph Lameter) Subject: Can console do a VT220 emulation? Date: 2 Dec 1995 10:31:37 -0800 I would like to use Linux boxes to access a VAX. And most of the applications there require at least vt220. Does that work? -- ============================================================================= Christoph Lameter FTS Box 466, Pasadena, CA 91182 Internet Administrator Who is like Jesus... who is like God...? ------------------------------ From: kxn@dcs.ed.ac.uk (Kristian Nilssen) Subject: Info on the kernel Date: Sat, 2 Dec 1995 20:17:14 GMT I need information on the real gubbins behind the linux kernel. Can anyone point me in the right direction? - cheers, Kristian. ------------------------------ From: ig25@fg70.rz.uni-karlsruhe.de (Thomas Koenig) Subject: How do you compile an old module? Date: 30 Nov 1995 19:29:57 +0100 Reply-To: Thomas.Koenig@ciw.uni-karlsruhe.de What's changed in module handling? I'd like to run the iBCS module under 1.3.45, but I'm stuck with an older version until I can figure out what to change... -- Thomas Kvnig, Thomas.Koenig@ciw.uni-karlsruhe.de, ig25@dkauni2.bitnet. The joy of engineering is to find a straight line on a double logarithmic diagram. ------------------------------ From: schoinas@fox.cs.wisc.edu (Ioannis Schoinas) Subject: Kernel panic in 1.3.45 (CM206 & Date: 30 Nov 1995 18:41:03 GMT Hello, I have a rather crazy setup with a Phillips CM206 disk drive and a PAS16 card with a SCSI interface. Whenever, I compile all three into the kernel, it fails to boot up. It gives up with a invalid reference somewhere after calling the cm206_interrupt() function (it seems to die inside the _read_chan function with an NULL pointer reference but this doesn't make much sense to me). I fixed the problem by returning immediately from the interrupt function during the kernel initialization process. What I suspect is that the device responds with some error code which results in the wake_up_interruptible being called from the interrupt handler. The bug appears always when I configure the SCSI and sound support (PAS16 & SB) but only very rarely otherwise (I haven't tried just the sound and the cdrom drivers. though). Anyway, my question is whether it is permissible to call the wake_up_interruptible() function during the device initialization phase. Yannis. ------------------------------ From: gonzo@magnet.mednet.net (Patrick J. Volkerding) Crossposted-To: comp.os.linux.development.apps Subject: Re: old aout binaries Date: 1 Dec 1995 19:31:05 GMT Mark Shadley (shadcat@catcher.com) wrote: : Hi, : While converting to ELF, I've come across a few files that 'file' : reports are 'Linux/i386 impure executable (OMAGIC)'. The one's : that I've tried, do run. What does impure mean? It means that the code in the binary was packed in without regard to page boundaries. This won't allow the binary to be demand-loaded, so the entire thing gets loaded into memory when you run it. Before QMAGIC, you could save a few K on a small binary by compiling like this (using the -N flag), but then QMAGIC came along and made it possible to save a few K and still get demand loading. I don't think ELF supports impure executables. Later, Pat ------------------------------ From: mibu@scrum.greenie.muc.de (M.Buchenrieder) Subject: Re: PLIP: not detected. My system, or bug in 1.2.13? Date: Thu, 30 Nov 1995 21:33:19 +0000 controzz@cli.di.unipi.it (Andrea Controzzi) writes: >James Murray (jsm@jsm-net.demon.co.uk) wrote: >: (Apologies for the long lines) >: Last week I decided to configure PLIP on my system and I recompiled my 1.2.13 >: kernel with PLIP enabled, but it is not detected on startup. >Perhaps I say something REALLY stupid, but the first time I tried PLIP it >was not recognazed because I compiled the kernel with parallel printer >enabled. >You did the same error? >: Nov 19 14:02:03 jsm-net kernel: lp1 at 0x0378, using polling driver Yep. Seems so. -- * Michael Buchenrieder * mibu@scrum.muc.de / mibu@scrum.greenie.muc.de * ************************************************************************** * Our continuing mission: To seek out knowledge of C, to explore strange * * UNIX commands and to boldly code where no one has manpage 4... * ------------------------------ From: urlichs@smurf.noris.de (Matthias Urlichs) Crossposted-To: comp.os.linux.networking Subject: Re: [kernel patch] Interface-based firewalling for point-to-point links Date: 1 Dec 1995 19:22:26 +0100 In comp.os.linux.development.system, article <49b3r5$a2s@piglet.amscons.com>, bob@piglet.amscons.com (Bob Amstadt) writes: > >In article rjs@spider.compart.fi (Riku Saikkonen) writes: > > > This changes the firewalling code so that the interface address specified to > > ipfw (iface xxx.xxx.xxx.xxx) is the address of the _other_ end of the link > > (not this machine) for point-to-point links (and this machine's address for > > all other links, as it has always been). > Good idea. Still better idea: Interfaces have NAMES, dammit. Use them. > As a matter of fact, you should never give two different interfaces the same > IP address. I have one system that many PPP links and one ethernet link, and > I give all of the interfaces unique IP addresses. Once you do this, everything > including the firewall code works just as it should. Whereas if you use one IP address for everything, all the tools _except_ the firewall code works just as it should. Being able to reuse one address for multiple interfaces is a Good Thing. It doesn't make sense to waste two per link if it can be avoided. I vote for fixing the problem instead of falling back to the behavior of age-old networking code which doesn't understand IP networking. -- He who is good for making excuses is seldom good for anything else. -- Matthias Urlichs \ XLink-POP N|rnberg | EMail: urlichs@smurf.noris.de Schleiermacherstra_e 12 \ Unix+Linux+Mac | Phone: ...please use email. 90491 N|rnberg (Germany) \ Consulting+Networking+Programming+etc'ing 42 PGP: 1B 89 E2 1C 43 EA 80 44 15 D2 29 CF C6 C7 E0 DE Click here. ------------------------------ From: rmaston@webstar.net (Ronald S. Maston) Subject: Re: kernel 1.3.45 and PPP --> not working :((( Date: Sat, 02 Dec 1995 05:16:48 GMT Pavel Korensky wrote: >Hello, >yesterday, I tried to compile kernel 1.3.45. Everything seems OK, except PPP. >I compiled kernel with SLIP and PPP support (I triple check it). >When I tried to run pppd, I got the message "PPP is not on system" or >similar. >Any idea where is the problem ? When I looked on the screen, the ppp.c >module was compiled. >My last version 1.3.30 was without any problem. >Thank you for any hint >PavelK You need to get ppp-2.2.0c from sunsite... This will fix the problem you are having... ------------------------------ From: bass@cais.cais.com (Tim Bass ) Subject: Re: Weak Thread Support: Linux Weakness ? Date: 30 Nov 1995 18:03:55 GMT Reply-To: bass@silkroad.com William S. Gribble (grib@cs.utexas.edu) wrote: Bill Gribble must be practicing how to be pedantic without really trying... First he decides to launch a flame.... Bill: I think that you're speaking from ignorance. There are at least two : implementations of the POSIX thread API for Linux, one of which (Chris : Provenzano's MIT PThreads) I have been using for a couple of years in : a distributed object system for real-time vision research. What kind : of ``multithreaded environment'' is it that Linux doesn't have? Then he states that Linux does not have kernel thread, which was the basis of my original question. Bill again: : It would be nice if Linux had kernel threads, but on a non-SMP machine : it just doesn't matter as far as performance. POSIX threads are what : every other UNIX either has or is moving towards, and that's good enough : for Java. Then, Bill finishes with another pointless dribble... Bill: : Maybe it's a wake-up call if you don't know what's already out there :) What every happened to the days when jerks like this were not a part of the comp.os.linux.* groups. Please Mr. Gribble, take your pedantic, anal attitude elsewhere, OR just don't answer questions. If you don't have a nice answer, just don't answer. Best Regards, Tim : Bill Gribble -- +--------------------------------------------------------------------------+ | Tim Bass | #include | | Principal Network Systems Engineer | for(beer=100;beer>1;beer++){ | | The Silk Road Group, Ltd. | take_one_down(); | | | pass_it_around(); | | http://www.silkroad.com/ | } | | | back_to_work(); /*never reached */ | +--------------------------------------------------------------------------+ ------------------------------ From: lady0110@sable.ox.ac.uk (Christian Evans) Subject: /proc filesystem permissions Date: 3 Dec 1995 01:45:31 GMT I posted an article a little while back about a patch to give changeable permissions on the /proc filesystem, so, for example, non-root users can make processes completely invisible from each other. My patch is now available on a (VERY) temporary server. Look at, ftp://jcr00.lmh.ox.ac.uk/pub/linux/kernpatch/dynamic_procperms.tar.gz It's probably a kludgy implementation - please read the README in the tarfile if interested, and any feedback is appreciated, as is anyone who will mirror the file at a more permanent site. Also on the server reside recent things like kernel 1.3.45, libc 5.2.16, gcc 2.7.2, many useful security pacakges, latest Wine, quota patches, other useful kernel patches. Feel free to take a look before the server dies... you probably have a few days... And don't moan if the address does not work, please. -- Chris >> PGP key available on request << >>Presence in pub available on request<< ------------------------------ From: Henrik Soderstrom Crossposted-To: comp.os.linux.hardware Subject: HELP - CDROM (acdu31a=0x340) not recognised in 1.3.xx kernels ! Date: 30 Nov 1995 07:06:15 GMT Need help to have CDROM recognised in 1.3.xx kernels. Have read the HOWTO's and it does NOT seem to be the polling problem ... I am consistently getting the CDROM recognised in kernel 1.2.13 and failing with 1.3.xx (tried 45,43,39,35) - all these were compiled with the cdu31a options enabled. I know the address is correct (0x340) cause 2.1.13 fails as well when I try giving it a different address in the kernel parameter cdu31a as follows (booting with LOADLIN): kernel param: none cdu31a=0x340 cdu31a=0x230 (or other) 1.2.13 kernel WORKS WORKS FAILS 1.3.xx kernel FAILS FAILS FAILS Equipment is Sony CDU33A connected to an SB-compatible soundcard. Any ideas much appreciated, Cheers /Henrik ------------------------------ Crossposted-To: comp.os.linux.setup,comp.os.linux.misc From: fairlite@iglou.com (Fairlight) Subject: HELP! aha1542/dx4-120 problems! Date: Wed, 29 Nov 1995 20:48:28 GMT To anyone that can help: I've got the following setup: aha1542, 5.0mbit/sec rate, 2 scsi drives (internal), and a scsi cdrom (external), termination all verified correct. I'm running linux 1.3.45. My problem is this. I was running a dx33 with this hardware. All ran fine and without incident. However, last night, I upgraded my CPU to a dx4/120. Now, when I do anything that's very disk intensive (read: more than 1 compile at a time, or a large "find"), I get errors like: scsi0: channel0: resetting for second half of retries If I keep going with whatever is running, eventually I see that message a few more times, and then I start getting scsidisk errors, ext2-fs errors, and possibly a system crash. I've run the adaptec's disk verify, and there is nothing whatsoever wrong with the media. Everything also works fine under DOS...works like a charm. I've not changed anything on my scsi bus in months. I called the place where I bought the motherboard, they say that chip works fine in the board I have. I called the place I bought the chip from...they say it should work fine. I called Adaptec...they say that no matter what chip I put in there, the card is on the ISA bus, and should work fine. They claim it's not a hardware issue, but most likely the Linux driver for the aha1542 that "probably has some incorrect timing loops" was how he put it. He said that would make it go flaky like that. Does anyone know how to correct this problem? Thanks in advance... mark-> -- Fairlight-> ||| fairlite@iglou.com | Fairlight Consulting __/\__ ||| "I'm talking for free... | http://www.fairlite.com <__<>__> ||| It's a New Religion..." | info@fairlite.com \/ ||| PGP Public Key available via finger @iglou, or Key servers ------------------------------ ** 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-System-Request@NEWS-DIGESTS.MIT.EDU You can send mail to the entire list (and comp.os.linux.development.system) via: Internet: Linux-Development-System@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-System Digest ******************************