Subject: Linux-Development Digest #553 From: Digestifier To: Linux-Development@senator-bedfellow.MIT.EDU Reply-To: Linux-Development@senator-bedfellow.MIT.EDU Date: Tue, 15 Mar 94 00:13:08 EST Linux-Development Digest #553, Volume #1 Tue, 15 Mar 94 00:13:08 EST Contents: Re: Lint for Linux? (Matthias Urlichs) Re: A truely non-debugging Kernel? (Alan Cox) Re: Take a look at this netstat, please... (Alan Cox) Re: STRAW POLL: Linux groups automonitoring (Ian Jackson) Re: Error with ld when trying to use CheckerV0.3 (ld.so.1.9l.4) on linux (Reuben Sumner) Re: Wine Question (Gonzalo Diethelm) [Q] Unixware filesystem? (Barzilai Spinak) Re: select (Robert Andrew Ryan) Re: I'm developing UMSDOS Linux Pkg. (Jacques Gelinas) Re: UDP report card (Warner Losh) LILO help!?!? (Todd Huss) Re: select (Erik Nygren) fdisk that does not destroy data ?? (Tom J. Jarmolowski) Re: 127.x.x.x (was Re: UDP report card) (Warner Losh) SVGALIB only as root ? (Ralf Wirdemann) TCP and Linux (Dan) Re: Linux/Windows (Michael De La Rue) Re: 127.x.x.x (was Re: UDP report card) (Mark Evans) ---------------------------------------------------------------------------- From: urlichs@smurf.noris.de (Matthias Urlichs) Subject: Re: Lint for Linux? Date: 14 Mar 1994 10:32:38 +0100 In comp.os.linux.development, article , jaffer@zurich.ai.mit.edu (Aubrey Jaffer) writes: > In article stevev@miser.uoregon.edu (Steve VanDevender) writes: > > gcc -Wall is pretty close to lint for telling you about dumb C > coding practices. > > Not close enough! If you code with K&R style function prototypes (as > opposed to ANSI) then gcc -Wall tells you nothing about argument > mismatch and number of arguments mismatch between modules. In that case, I suggest you write your prototypes with __P macros (see /usr/include/anything.h). -- THINK - If you are already thinking, please disregard this button -- 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 Click here. ------------------------------ From: iiitac@uk.ac.swan.pyr (Alan Cox) Subject: Re: A truely non-debugging Kernel? Date: Mon, 14 Mar 1994 12:10:15 GMT In article <2loo9h$fo8@aurora.engr.latech.edu> ramos@engr.latech.edu (Alex Ramos) writes: > >Geez! The kernel has _so much_ debugging code (sanity checks, etc) that >I wonder how much smaller it could be. It seems most kernel developers >have never heard of #ifdef... Just a thought :-) > Since you have to do something when you get a completely bogus event the cost is pretty minimal. If you've worked with 386BSD or commercial kernels of almost any kind you'll find them full of sanity checks. Some of the realtime ones tend to just output things like 'OOPS 337 1EFA 226B:441C' and you look them up in a book but they are still there. Alan ------------------------------ From: iiitac@uk.ac.swan.pyr (Alan Cox) Subject: Re: Take a look at this netstat, please... Date: Mon, 14 Mar 1994 12:15:58 GMT In article jon@cs.iastate.edu (Jon Green) writes: >>I did this netstat at ~3:00 PM (my time). I had performed these >>two ftp's over *4* hours earlier. Why haven't these closed down? > >I've noticed the same problem when using term with tredir. If it closes >unexpectedly, the connection won't close properly and hangs there in >CLOSE_WAIT. I have to reboot to get the port back. This has also happened >when running a mud on port 4000 and telnetting to localhost from another >console (I'm not on a network). What's the deal here? > There are a combination of at least 4 small problems in the tcp closedown and timer code. Linus has done number 1 for SO_LINGER. I have patches for problems 2 and 3 although I'm still playing with them (Thanks Gerhard) and number 4 I haven't traced down yet. Alan iiitac@pyr.swan.ac.uk ------------------------------ From: iwj@cam-orl.co.uk (Ian Jackson) Crossposted-To: news.groups,comp.os.linux.misc,comp.os.linux.help,comp.os.linux.admin Subject: Re: STRAW POLL: Linux groups automonitoring Date: 14 Mar 1994 16:34:49 GMT Summary: I'm going for Subject line tags instead of Keywords lines. Please don't vote against the proposal because of technical difficulties with the Keywords header. In article <1994Mar13.175238.15537@cs.cornell.edu>, Ron "Asbestos" Dippold wrote: > STRAW POLL (Last Call) > Linux groups automonitoring > PROPOSAL (Ian) > ... > It will send email to the posters of any messages which either > (a) do not include one of a set or recognised keywords in the > Keywords line or > ... A number of people have criticised this, saying that 1. newsreaders have a tendency not to pay any attention to Keywords and 2. some posters may have technical problems inserting such headers. I've therefore been convinced to go for Subject line tags instead, as are used in several newsgroups. They often look like this: Subject: [keyword] rest of subject line I'll be happy to see or receive comments on the exact format. -- Ian Jackson iwj@cam-orl.co.uk ..!uknet!cam-orl!iwj These opinions are my own. 2 Lexington Close, Cambridge CB4 3LS. + 44 223 575512 Cambridge University Computer Laboratory, New Musems Site. + 44 223 334676 Email also via: ijackson@nyx.cs.du.edu PGP2 public key available on request ------------------------------ From: rasumner@undergrad.math.uwaterloo.ca (Reuben Sumner) Subject: Re: Error with ld when trying to use CheckerV0.3 (ld.so.1.9l.4) on linux Date: Mon, 14 Mar 1994 16:00:07 GMT In article <2m1udp$mq1@oak7.doc.ic.ac.uk>, Nicholas Ambrose wrote: > >In article <1994Mar10.053846.13233@mlb.semi.harris.com>, crw@maniac.mlb.semi.harris.com (Carl Williams) writes: >|> I am trying to get the Checker program (V0.3) to work and >|> am having trouble with ld when I try to run Checker. >|> >|> Specifically , I am running linux-0.99.15, and I just installed >|> gcc2.5.8, libc.4.5.21, and CheckerV0.3 (I installed all of the >|> above as I wanted to use Checker !! and the README said I needed >|> a gcc at least 2.5 something (I was at gcc2.4.5 before) ). >|> >|> In installing the above I installed ld.so.1.9l.4. >|> >|> After all this when I try to compile a program with checkergcc I get: >|> # checkergcc test.c -o test >|> ld: unrecognized option `-checker' >possibly Checker is using -checker instead of -l checker > >|> Usage: ld [-d] [-dc] [-dp] [-e symbol] [-l lib] [-n] [-noinhibit-exec] >|> [-nostdlib] [-o file] [-r] [-s] [-t] [-u symbol] [-x] [-y symbol] >|> [-z] [-A file] [-Bstatic] [-D size] [-L libdir] [-M] [-N] >|> [-static] [-nojump] [-dll-verbose] [-S] [-T[{text,data}] addr] >|> [-V prefix] [-X] [file...] >|> >|> I tried to use the ld.diff file (that came with the CheckerV0.3) >|> to make a new ld.so >|> , but it seemed wildly different >|> than the ld.c file the diff file was compared against (the ld.diff >|> file starts it's changes at line 1154, and the ld.so.c file >|> for ld.so.1.9l.4 has only 458 lines. >|> >|> Can you help/ any suggestions ? >|> >|> Thanks, >|> >|> --Carl >|> crw@harris.mlb.semi.harris.com >Well, a simple solution is to use dbmalloc. it's easy to use. Just include >their own malloc.h file, and link with -ldbmalloc. if this does what >you want, hen that would seem easier ... This is the most simple way >of using dbmalloc admittedly, but iot seeme to pick up most of the stupid >errors and works well for me ... I'm guessing that you haven't used checker yet. First off the doc says that you should have libc 4.5.19 not 21, I don't know if it will make a difference. Then you must replace as and ld with the checker versions. (the original upload to nic.funet.fi did not have 'em, try now or from Sunsite). In my Slackware 1.1.2 system I just make the symlinks that used to be as and ld point to the checker version of the above. It works quite well although I wish that it would work with C++ and iostream. Reuben ------------------------------ From: gonzo@malloco.ing.puc.cl (Gonzalo Diethelm) Subject: Re: Wine Question Date: Sun, 13 Mar 1994 07:32:31 GMT Dave Gardner (dgardner@netcom.com) wrote: > Elan Feingold (elan@tasha.cheme.cornell.edu) wrote: > : This may be a silly question, but when it is done, should it run > : most Windows programs, or only those that run in standard mode? > An FAQ is being written now which should answer this, and many other, > questions. Stay tuned. > -- > ============================================================================== > 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. > ============================================================================== Let me add a request for inclussion in the FAQ of any information about an API for Windows under Linux. Is one being planned? Will it support Win16 and Win32? Am I totally missing the point here? 8^) What I need to know is whether I'll be able to develop for Windows using a Linux box. Maybe a cross compiler would do the trick; OTOH maybe I'll be able to run Borland C++ on top of wine. So many questions, so little info... Gonzalo ------------------------------ From: barspi@wam.umd.edu (Barzilai Spinak) Subject: [Q] Unixware filesystem? Date: 14 Mar 1994 17:04:14 GMT After 1 1/2 years of waiting, I will shortly have a BIG computer and will install Unixware, Linux and Windows (ugh! ...I need to). My question is if there's a Unixware filesystem the Linux can use. I don't know anything about Unixware yet and I don't know if it uses a proprietary filesystem or not. Thanks. +---------------------------------+ | Barzilai Spinak | | ..... barspi@wam.umd.edu | | (-O-O-) barspi@eng.umd.edu | +nnn--U--nnn----------------------+ ------------------------------ From: Robert Andrew Ryan Subject: Re: select Date: Mon, 14 Mar 1994 12:59:18 -0500 Excerpts from netnews.comp.os.linux.development: 10-Mar-94 Re: select Mark Evans@mb48026.aston (1123) > What happens is that quite a few versions of select(), including on Suns, > never write to the timeout. So what is actually broken code runs ok on > them. What standard specifies select should write to the timeval? SunOS 4.1 is the only system I've seen where it's even mentioned as a possible future enhancement. I certainly agree it's a useful enhancement, but it is incompatible with a great number of previous implementations. This is a serious source of bugs for the unwary porting interactive network programs. -Rob ------------------------------ Crossposted-To: comp.os.linux.misc From: jack@solucorp.qc.ca (Jacques Gelinas) Subject: Re: I'm developing UMSDOS Linux Pkg. Date: Sun, 13 Mar 94 01:21:52 GMT Sounds like you do something in the line of L.A.D.R (Linux Advanced Desktop Release) which is the followup to the simple UMSDOS installation kit. Maybe we may split the job. I am currently doing experience with the andrew multimedia system. I hope to provide some sort of embeded help/administration system. My goal is to cleanup all(most) rough edges in linux. Many are show stopper for newbie and some experience users. These include at least: swap user admin printers Networking Mail In fact, I don't expect to make everything simple, but certainly enough so a newbie will be able to make some use of linux (and be impressed). -- ======================================================== Jacques Gelinas (jacques@solucorp.qc.ca) Maintainer of US4BINR jacques@us4binr.login.qc.ca ------------------------------ From: imp@boulder.parcplace.com (Warner Losh) Subject: Re: UDP report card Date: Mon, 14 Mar 1994 18:08:37 GMT In article hpa@nwu.edu (H. Peter Anvin) writes: >Personally I find this use of a class A network for this purpose pretty >ridiculous, but I can see where having multiple loopback addresses >could be of use; 127.0.0.1 should then be the equivalent to the >"outside" entrypoint. But a Class A? Give me a break. The address was assigned back in the days when the interet was but a few hundred hosts and nobody thought that it would ever be large enough to make assigning a large block of addresses a problem. Now they are redesigning IP to handle more than 4 billion hosts[*]... Warner [*] Due to subnetting and other name space issues, the actual upper limit is much smaller than this. -- Warner Losh imp@boulder.parcplace.COM ParcPlace Boulder "... but I can't promote you to "Prima Donna" unless you demonstrate a few more serious personality disorders" ------------------------------ From: thuss@moose.uvm.edu (Todd Huss) Subject: LILO help!?!? Date: Mon, 14 Mar 1994 17:00:03 GMT I just recently installed Linux with X and during the installation it asked me if I wanted to use LILO to boot and ofcourse I said yes, while I normally boot from my dos partition (/dev/hda1) and I'd like to have the option to not always use a boot floppy. I found the lilo directory on (/dev/hda2) which is my linux partition, however I don't really know what to do with it .... Apparently when I asked linux to boot using lilo it didn't touch my c drive or (dev/hda1). I was wondering how I go about setting up LILO on my c drive (/dev/hda1) so that I can boot to linux without a boot disk. Any help is greatly appreciated! -Todd -- ============================================================================= Todd C. Huss thuss@moose.uvm.edu huss@emba.uvm.edu ------------------------------ From: nygren@athena.mit.edu (Erik Nygren) Subject: Re: select Date: 15 Mar 1994 03:07:19 GMT In article , Robert Andrew Ryan writes: |> Excerpts from netnews.comp.os.linux.development: 10-Mar-94 Re: select |> Mark Evans@mb48026.aston (1123) |> |> > What happens is that quite a few versions of select(), including on Suns, |> > never write to the timeout. So what is actually broken code runs ok on |> > them. |> |> What standard specifies select should write to the timeval? SunOS 4.1 |> is the only system I've seen where it's even mentioned as a possible |> future enhancement. I certainly agree it's a useful enhancement, but it |> is incompatible with a great number of previous implementations. This |> is a serious source of bugs for the unwary porting interactive network |> programs. |> |> -Rob IRIX 5.0 also mentions in its man pages that this is a possible future enhancement. However, I have ported one thing which did spin because it relied on the timeout value not changing. --- Erik ------------------------------ From: tjj@visual.com (Tom J. Jarmolowski) Subject: fdisk that does not destroy data ?? Reply-To: tjj@visual.com Date: Mon, 14 Mar 1994 15:53:32 GMT Hi, I'm getting ready to do a first time install of linux on a currently dos/windows only system, hnece I have to partition my drive. Since the system is new, there is plenty of free space. My question is is there a version of fdisk that will partition my disk ** without ** destroying the data now on it ? I would really like to avoid doing a complete re-install of my windows stuff or a backup to floppy. Thanks. ps: please e-mail me a reply since we tend to loose a fair percent of news. I will post any positive replies. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Tom Jarmolowski _/_ tjj@visual.com Visual Technology / __ _____ ...uunet!visual!tjj 120 Flanders Rd (__ (_) ( ) ) Voice: 1-800-VISUAL-C Westboro MA 01581 (in MA) (508) 366-2949 Fax: (508) 366-4337 ------------------------------ Crossposted-To: comp.protocols.tcp-ip From: imp@boulder.parcplace.com (Warner Losh) Subject: Re: 127.x.x.x (was Re: UDP report card) Date: Mon, 14 Mar 1994 17:59:04 GMT In article <1994Mar14.011113.2735@unlv.edu> ftlofaro@unlv.edu (Frank Lofaro) writes: >Anyone in comp.os.linux.development or comp.protocols.tcp-ip want to >comment? If my interpretation is correct, 127.x.x.x should always be >looped back. > >Is rfc1122 obsolete? Or does the 127.x.x.x statemnet shown above still >hold? I know of at least two commercial versions of IP that have had bug fixes applied to them that stop them from spitting out 127.* to the wire. I'm not aware of anything that supplants this requirement in RFC 1122. Any system that does spits 127.* to the wire is broken. Warner -- Warner Losh imp@boulder.parcplace.COM ParcPlace Boulder "... but I can't promote you to "Prima Donna" unless you demonstrate a few more serious personality disorders" ------------------------------ From: d16i@zfn.uni-bremen.de (Ralf Wirdemann) Subject: SVGALIB only as root ? Date: 14 Mar 1994 16:21:42 GMT Hi, I have some problmes with my SVGALIB. I cant execute the programms, which use this lib. I allways get the message "svgalib: i/o permission denied". This porblems doesnt occurs as root. Does anybody know a solution ? Thanks in advance, Ralf. ------------------------------ From: galpin@cats.ucsc.edu (Dan) Subject: TCP and Linux Date: 14 Mar 1994 21:27:23 GMT I am having a problem with a socket connection to localhost with TCP/IP. The Linux system that I am using is patchlevel 14, and all the network services appear to function.. (telnet, ftp, nfs mount...) When I try to do TCP socket connects, I get an IMMEDIATE error return from the source code below. In the source code below, I am simply trying to connect to localhost. if ( connect(*piSocket, &stSocketIn, sizeof(stSocketIn)) < 0 ) return TCP_CONNECT_ERROR; /* error in errno */ return 0; Are there any setup issues with TCP that I should be aware of? Note that the source that I have will execute properly on a Solaris/SunOS, Unixware, SCO, HPUX or AIX box, so this has been a bit puzzling. Any Ideas? I wanted to try this first before wasting lots of bandwidth posting source. - Dan -- ****************************************************************************** * Dan Galpin galpin@cats.ucsc.edu * ****************************************************************************** -- ****************************************************************************** * Dan Galpin galpin@cats.ucsc.edu * ****************************************************************************** ------------------------------ From: p91152@PROBLEM_WITH_INEWS_GATEWAY_FILE (Michael De La Rue) Subject: Re: Linux/Windows Reply-To: miked@ed.ac.uk Date: Mon, 14 Mar 1994 18:07:19 GMT A windows emulator exists but it's not complete by any means. From what I hear all important windows software can be run though (solitare). For other stuff you have to wait. If you want to be involved they have their own mail list on the usual place (see the meta-faq etc). You are looking for 'Wine'. nice adj. 1. pleasent, satisfactory (of a person) kind, good-natured. 2.(iron) bad difficult awkward. 3. needing precision and care; subtle.... The Oxford Reference Dictionary. Linux/Unix clone/ftp:src.doc.ic.ac.uk//packages/linux/sunsite.unc-mirror/docs ------------------------------ Crossposted-To: comp.protocols.tcp-ip From: evansmp@mb48026.aston.ac.uk (Mark Evans) Subject: Re: 127.x.x.x (was Re: UDP report card) Date: Mon, 14 Mar 1994 19:07:12 GMT Frank Lofaro (ftlofaro@unlv.edu) wrote: : Well the route thing works. : However, I think that all 127.x.x.x addresses should be loopback. : 1: It does not break anybody's set up, unless they are violating RFC's : by using the 127 net for their own purposes (they deserve to lose, they : aren't interoperable) : 2: Have 127.x.x.x always be loopback is MANDATED by rfc1122. : (g) { 127, } : Internal host loopback address. Addresses of this form : MUST NOT appear outside a host. : Anyone in comp.os.linux.development or comp.protocols.tcp-ip want to : comment? If my interpretation is correct, 127.x.x.x should always be : looped back. Also a host should NEVER respond to an arp request for such an address. If it ever gets a datagram addressed to 127.x.x.x on any real device it should silently ignore it. (I'm not sure what the status of putting 127.x.x.x in a source route is, however) : Is rfc1122 obsolete? Or does the 127.x.x.x statemnet shown above still : hold? ------------------------------ ** 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 ******************************