Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA00163; Fri, 8 Dec 95 16:27:34 EST Received: from SENATOR-BEDFELLOW.MIT.EDU by MIT.EDU with SMTP id AA16127; Fri, 8 Dec 95 16:26:27 EST Received: (from root@localhost) by senator-bedfellow.MIT.EDU (8.6.12/2.3JIK) id QAA00491 for Linux-Development-System-Dist@senator-bedfellow.mit.edu; Fri, 8 Dec 1995 16:13:52 -0500 Message-Id: <199512082113.QAA00491@senator-bedfellow.MIT.EDU> From: Digestifier To: Linux-Development-System@senator-bedfellow.MIT.EDU Reply-To: Linux-Development-System@senator-bedfellow.MIT.EDU Date: Fri, 8 Dec 95 16:13:48 EST Subject: Linux-Development-System Digest #96 Linux-Development-System Digest #96, Volume #2 Fri, 8 Dec 95 16:13:48 EST Contents: Patch to kernel for GCC 2.7.[12] (Richard Jones) Re: Library version number bugs (Wolfram Gloger) Scheduler (Matthew Singer) Re: [kernel patch] Interface-based firewalling for point-to-point links (Matthias Urlichs) Re: Linux on BeBox? (James H. Cloos Jr.) problem referencing files (Oscar E Masters Jr.) Re: Help compiling non-ELF objects (Chopin6) 3c595 with modules and kernel 1.3.45... (Wayne Veilleux) Re: Will Linux work with the P6 ??? (Matthias Urlichs) Re: using lilo to boot dos from 2nd scsi drive (Jeffrey Graham) Re: [Q] How to upgrade easily to a new hard disk? (David J. Liu) Re: Standardized Printing for Linux (Dave Carrigan) Re: Linux Security - C2 and beyond (Albert Cahalan) ---------------------------------------------------------------------------- From: rwmj@doc.ic.ac.uk (Richard Jones) Subject: Patch to kernel for GCC 2.7.[12] Date: 6 Dec 1995 13:26:01 GMT I've been asked to post the patch that makes the kernel 1.2.13 work with GCC 2.7.1 (and possibly with 2.7.2 also). So here goes ... > From doc.ic.ac.uk!sunsite.doc.ic.ac.uk!demon!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!usc!ccnet.com!rahul.net!a2i!dandelion.com!not-for-mail Fri Nov 17 09:41:48 1995 > Path: doc.ic.ac.uk!sunsite.doc.ic.ac.uk!demon!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!in1.uu.net!usc!ccnet.com!rahul.net!a2i!dandelion.com!not-for-mail > From: "Leonard N. Zubkoff" > Newsgroups: comp.os.linux.development.system > Subject: Linux 1.2.13 and GCC 2.7.1 > Date: 16 Nov 1995 00:14:24 -0800 > Organization: Dandelion Digital > Lines: 35 > Sender: lnz@dandelion.com > Message-ID: <48ert0$bag@kelewan.dandelion.com> > NNTP-Posting-Host: dandelion.com > NNTP-Posting-User: root > > The following patch is necessary to get Linux 1.2.13 to compile using the > newly released GCC 2.7.1. I haven't verified that the kernel actually > works properly, just that the compile now succeeds. Note that I am not an > expert on GCC's __asm__ magic, but I noticed that the necessary change had > already been made in 1.3.x. > > Leonard --- ./linux/include/asm-i386/io.h- Mon Aug 15 00:56:19 1994 +++ ./linux/include/asm-i386/io.h Wed Nov 15 23:04:25 1995 @@ -49,9 +49,9 @@ #define __OUT(s,s1,x) \ __OUT1(s,x) __OUT2(s,s1,"w") : : "a" (value), "d" (port)); } \ -__OUT1(s##c,x) __OUT2(s,s1,"") : : "a" (value), "i" (port)); } \ +__OUT1(s##c,x) __OUT2(s,s1,"") : : "a" (value), "id" (port)); } \ __OUT1(s##_p,x) __OUT2(s,s1,"w") : : "a" (value), "d" (port)); SLOW_DOWN_IO; } \ -__OUT1(s##c_p,x) __OUT2(s,s1,"") : : "a" (value), "i" (port)); SLOW_DOWN_IO; } +__OUT1(s##c_p,x) __OUT2(s,s1,"") : : "a" (value), "id" (port)); SLOW_DOWN_IO; } #define __IN1(s) \ extern inline unsigned int __in##s(unsigned short port) { unsigned int _v; @@ -61,9 +61,9 @@ #define __IN(s,s1,i...) \ __IN1(s) __IN2(s,s1,"w") : "=a" (_v) : "d" (port) ,##i ); return _v; } \ -__IN1(s##c) __IN2(s,s1,"") : "=a" (_v) : "i" (port) ,##i ); return _v; } \ +__IN1(s##c) __IN2(s,s1,"") : "=a" (_v) : "id" (port) ,##i ); return _v; } \ __IN1(s##_p) __IN2(s,s1,"w") : "=a" (_v) : "d" (port) ,##i ); SLOW_DOWN_IO; return _v; } \ -__IN1(s##c_p) __IN2(s,s1,"") : "=a" (_v) : "i" (port) ,##i ); SLOW_DOWN_IO; return _v; } +__IN1(s##c_p) __IN2(s,s1,"") : "=a" (_v) : "id" (port) ,##i ); SLOW_DOWN_IO; return _v; } #define __INS(s) \ extern inline void ins##s(unsigned short port, void * addr, unsigned long count) \ -- "The real tight interface is between the book and the reader - the world of the book is plugged right into your brain, never mind the [virtual reality] bodysuit" -- from The Age of Missing Information, by Bill McKibben. ------------------------------ From: Gloger@lrz.uni-muenchen.de (Wolfram Gloger) Subject: Re: Library version number bugs Date: 8 Dec 1995 12:30:38 GMT Reply-To: Gloger@lrz.uni-muenchen.de gonzo@magnet.mednet.net (Patrick J. Volkerding) writes: >I've noticed what I think are serious problems in the selection of version >numbers for shared libraries under Linux. Allow me to provide a couple of >examples: >1. Linux libc-5.2.16 has been made public. The GNU gdbm and db libraries > are no longer part of this release, and we've been pointed to what are > supposed to be the new versions. However, both of these libraries have > lower version numbers (*.so.1 instead of *.so.2) than the ones in > libc-5.0.9. This effectively breaks all existing apps linked with the > versions from the last public release. Well, you could move the old *.so.2.* versions to a /usr/lib/compat directory (added to ld.so.conf), so that newly compiled apps are linked to the new *.so.1 versions. You have a point here, however. >2. An even crazier example: The first public release of shared ncurses > libraries was just made on tsx-11.mit.edu in /pub/linux/packages/GCC. > The links for the shared libraries have a totally different version > number than the libraries, e.g.: > -rw-r--r-- 226650 /usr/lib/libncurses.so.1.9.7a > lrwxrwxrwx 0 /usr/lib/libncurses.so.2.1 -> libncurses.so.1.9.7a > This is the expected name. If the link is changed to libncurses.so.1.9 > or libncurses.so.1 (the expected name, IMO) it won't work. Resulting > binaries will be expecting to find libncurses.so.2.1 and therefore won't > start. Now this complaint directly contradicts your point 1. above. With ncurses, the author decided to seperate release version number from API version number, and to avoid confusion, he started with API version 2.0 (since several 1.x shared libs were in use before he supported shared libs officially). So where's the problem ? Regards, Wolfram. ------------------------------ From: msinger@griffon.oe.fau.edu (Matthew Singer) Subject: Scheduler Date: 8 Dec 1995 14:50:25 GMT Reply-To: msinger@griffon.oe.fau.edu (Matthew Singer) Are there any plans to extend the scheduler to handle real time tasks? Just dying to port a Solaris 2.4 system over... -- =============================================================================== Matthew R. Singer msinger@oe.fau.edu Systems Engineer Voice: 407-367-2947 Florida Atlantic University Fax : 407-367-3885 Dept of Ocean Engineering =============================================================================== ------------------------------ From: smurf@work.smurf.noris.de (Matthias Urlichs) Crossposted-To: comp.os.linux.networking Subject: Re: [kernel patch] Interface-based firewalling for point-to-point links Date: 7 Dec 1995 12:14:07 +0100 In comp.os.linux.development.system, article <4a1d7n$2ek@grebble.oau.org>, eww@grebble.oau.org (Eric Wampner) writes: > > It depends on what you are doing I suppose. What I understand to be > "more" standard, your PPP link has its own address so that it can be > a part of the other network. Your ethernet has its own address so it > can be a part of the local network. As long as > Actually, there's no need for the local side of a PPP connection to be part of a remote network. (On the other side, the remote side would be part of the local network, and you'd either need a separate (sub)net or ProxyARP.) > As I understood it, IP Aliasing was making your machine look like several > different machines. Yep, either via the aliasing patch or via dummy devices. Both of which have nothing at all to do with pointopoint links, however. -- 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: cloos@JHCloos.COM (James H. Cloos Jr.) Subject: Re: Linux on BeBox? Date: 08 Dec 1995 05:50:08 -0600 >>>>> "Joe" == Joe Zbiciak writes: Joe> Has there been any talk of Linux on the BeBox? There was an annoucement on the linux-ppc list that Be has donated some (4, I think) BoBoxen to the ppc porting team, so it looks good that it'll happen. -JimC -- James H. Cloos, Jr. cloos@jhcloos.com Work: cloos@io.com LPF,Usenix,SAGE,ISOC ------------------------------ From: oem@metronet.com (Oscar E Masters Jr.) Subject: problem referencing files Date: 8 Dec 1995 16:02:20 GMT I left the subject off my first post sorry. oem ------------------------------ From: chopin6@aol.com (Chopin6) Subject: Re: Help compiling non-ELF objects Date: 7 Dec 1995 20:50:31 -0500 Reply-To: chopin6@aol.com (Chopin6) >>I am trying to compile the PHOST distribution for Linux. It is distibuted as a bunch of .o files and a couple of libraries(.a files) and a Makefile.<< In the ELF-HOW-TO, its shown how to compile normal a.out programs on the Slackware 3.0 system that is set up for a.out and ELF binaries. In the Makefile, you must have a line like CC= ..... . Change this to cc -b i486-linuxaout, and the program should be compiled/linked as an a.out program. To verify, do 'file and see the binary format. I can compile a.out binaries on my Slackware 3.0 system, I just have trouble running them. I get loads of 'undefined reference to .....' when the binaries run. :( -fwiw/thomas ------------------------------ From: wayne@I_should_put_my_domain_in_etc_NNTP_INEWS_DOMAIN (Wayne Veilleux) Subject: 3c595 with modules and kernel 1.3.45... Date: Fri, 8 Dec 1995 16:40:44 GMT Hi: I'm trying to use insmod to load the driver for the fast-ethernet card 3c595. I compile the kernel with the 3c595 driver with the patch from cesdis.gsfc.nasa.gov. It worked fine. But I want the use kernel 1.3 to use samba filesystem so I upload the source code from http://cesdis.gsfc.nasa.gov/linux/drivers/3c59x-new.c and compile it like this to generate the 3c59x.o: gcc -DMODULE -D__KERNEL__ -I/usr/src/linux/net/ipv4 -I/usr/src/linux/net/core -I/usr/src/linux/net -I/usr/src/linux/net/ethernet -I/usr/src/linux/net/ipx -I/usr/src/linux/net/appletalk -I/usr/src/linux/net/802 -I/usr/src/linux/net/netrom -I/usr/src/linux/net/unix -Wall -Wstrict-prototypes -O6 -m486 -c 3c59x.c 3c59x.c: In function `vortex_probe1': 3c59x.c:340: warning: assignment from incompatible pointer type Here is my kernel config (others options = n): CONFIG_MATH_EMULATION=y CONFIG_BLK_DEV_FD=y CONFIG_ST506=y CONFIG_BLK_DEV_IDE=y CONFIG_NET=y CONFIG_PCI=y CONFIG_SYSVIPC=y CONFIG_BINFMT_ELF=y CONFIG_M486=y CONFIG_MODVERSIONS=y CONFIG_INET=y CONFIG_INET_SNARL=y CONFIG_IPX=y CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y CONFIG_CHR_DEV_ST=y CONFIG_BLK_DEV_SR=y CONFIG_CHR_DEV_SG=y CONFIG_SCSI_AHA1542=y CONFIG_SCSI_AIC7XXX=y CONFIG_NETDEVICES=y CONFIG_DUMMY=y CONFIG_SLIP=y CONFIG_SLIP_COMPRESSED=y CONFIG_PPP=y CONFIG_MINIX_FS=y CONFIG_EXT2_FS=y CONFIG_MSDOS_FS=y CONFIG_UMSDOS_FS=y CONFIG_PROC_FS=y CONFIG_NFS_FS=y CONFIG_ISO9660_FS=y CONFIG_HPFS_FS=y CONFIG_SYSV_FS=y CONFIG_PRINTER=y CONFIG_BUSMOUSE=y CONFIG_SOUND=y CONFIG_SCSI_CONSTANTS=y Here is what happened when I try to load it: insmod -fv /usr/src/drivers/net/3c59x.o Section 1: (.text) at 0x8010000 Section 2: (.rel.text) at 0x8015000 Section 3: (.data) at 0x8010fb4 Section 4: (.rel.data) at 0x800ef80 Section 7: (.rodata) at 0x801101c Section 8: (.comment) at 0x8011565 Section 9: (.shstrtab) at 0x800ef00 Section 10: (.symtab) at 0x8015800 Section 11: (.strtab) at 0x800fc00 textseg = 0x8010000 bss_size = 134288760 last byte = 0x8011578 module size = 5496 versioned kernel: yes versioned module: no ELF kernel ELF module irq2dev_map undefined Failed to load module! The symbols from kernel 1.3.45 don't match 1.3.45 Does anyone try this or has any hint to help me. Thanks for any help. Bye. -- Wayne Veilleux wayne@smtl.hydro.qc.ca ------------------------------ From: smurf@smurf.noris.de (Matthias Urlichs) Subject: Re: Will Linux work with the P6 ??? Date: 7 Dec 1995 10:49:02 +0100 In comp.os.linux.development.system, article <4a0pnq$vqh@taco.cc.ncsu.edu>, rao@hell.catt.ncsu.edu (Rao) writes: > Molnar Ingo (mingo@PROBLEM_WITH_INEWS_GATEWAY_FILE) wrote: > : kernel recompilation in 2 minutes 50 seconds Fast hard disk, I presume. > That's extremely fast. Does anyone know how a P6 200Mhz compares to > a dual-pentium 133 system under Linux? .. since the price ranges are > roughly the same .. > No. If you do test that, though, remember to make with -j2. ;-) Actually, I find that on machines with enough RAM, this speeds up the kernel compilation even on one-processor machines. -- 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: jgraham@tenagra.com (Jeffrey Graham) Crossposted-To: comp.os.linux.setup,comp.os.linux.hardware Subject: Re: using lilo to boot dos from 2nd scsi drive Date: Fri, 08 Dec 95 12:57:24 GMT >Jeffrey Graham (jgraham@tenagra.com) wrote: > >.... > >: I have Linux and LILO on my 1st scsi disk (id 0) /dev/sda >: I have DOS/windows on my 2nd scsi disk (id 1) /dev/sdb >: >: Lilo boots linux just fine. >: >: Lilo wont boot DOS. I get an error message about "non-system disk blah blah >: blah..." >: > >.... > >Your SCSI BIOS must support starting from a disk other than disk 0. I have emailed the maker of my pc (Micron) about this. My Ultrastore Doc says in several places that the first (lowest scsi ID) drive is the boot device. This limitation did surprise me. The doc does not mention a method around this. It does mention that I can disable its bios, but I have no idea what this means for DOS or Linux. Anyway, I *DO* want the 34f scsi controller to boot off of the 1st disk, so I can find Linux and LILO. The problem is that LILO will not, in turn, boot DOS off the 2nd scsi drive. Are you saying that LILO does some trickery to the 34f that causes it to reseek the 1st drive? IF so, then I am screwed. My knee-jerk reaction is that DOS and/or its bios are the problem... but that is what LILO is all about, isnt it???? >Most BOISes do not support this. If your card/bios doesn't support >booting from a drive other than 0, you'll have to install LILO's boot >info on your DOS disk and switch their ID's. If you need help or >clarification please email me =) Still hoping to avoid this.... Thank you for the enlightening conversation! -Jeffrey ------------------------------ From: liudj0@minerva.cis.yale.edu (David J. Liu) Subject: Re: [Q] How to upgrade easily to a new hard disk? Date: 8 Dec 1995 19:32:34 GMT Michal Szymanski (msz@sirius.astrouw.edu.pl) wrote: # I am going to upgrade my linux box with a new, bigger HD. I could # attach the new drive as a secondary HD, then make partitions there, # "tar" all files. The only thing I am not sure is how to install # the LILO loader on a secondary drive (i.e. /dev/hdb), having in mind # that it should have a reference to /dev/hda as a boot device (as # the old HD is to be removed and the new one will become "hda"). Since setting up LILO happens once in the life time of a hard disk, you may save much trouble by simply removing the old disk, then boot from a floppy, and run lilo with the new disk configured as /dev/hda ------------------------------ Subject: Re: Standardized Printing for Linux From: dcarriga@nofc.forestry.ca (Dave Carrigan) Date: 5 Dec 1995 19:37:23 -0700 mandtbac@news.abo.fi (Mats Andtbacka) writes: >Albert Cahalan, in : >>OK, here is the request: print a man page on an inkjet printer. >What you need here is a PCL (or whatever) driver for groff. >Or, hell, a dvi or TeX driver for groff. That's going the awkward way >around, I know, but... In fact, there is a dvi driver for groff: ================================================================= groff is a front-end to the groff document formatting sys tem. Normally it runs the gtroff program and a postpro cessor appropriate for the selected device. Available devices are: ps For PostScript printers and previewers dvi For TeX dvi format ^^^ X75 For a 75 dpi X11 previewer X100 For a 100dpi X11 previewer ================================================================= In fact, that's how I've got my magic filter set up, using the command eval `/usr/bin/grog -Tdvi $FILE` and man pages print out very nicely on my OL400, and much faster than the ghostscript route. Cheers, Dave Carrigan ------------------------------ From: albert@krakatoa.ccs.neu.edu (Albert Cahalan) Subject: Re: Linux Security - C2 and beyond Date: 08 Dec 1995 20:21:16 GMT >>>>> Darren J Moffat writes: > Many moons ago in the Linux world there was discussion about > bringing together the required options to make Linux conform > to the C2 requirements for system security. > I gather there is now an (almost?) working shadow password suite, > but there is a lot more work to get upto C2. > I propose starting a project to get Linux upto the same level > of functionallity as the Basic Security Module of Solaris 2.5. > This includes such things as: Shadow Passwords, Device Allocation, > System call level, and application level auditing. > I would also like to propose that we do this in such away that we can > further enhance the Linux system to be a full CMW (Compartmented Mode > Workstation), for those that are unfamiliar this includes things like: > security classifications on all files - Mandatory Access Control, (ext2) Some of this exists (secure deletion), and some of it would completely bog down normal system usage. Just get a DOS PC in a locked room with no network and Norton encrypted disks if you need this. > removal of single all powerfull super-user, (kernel) Windows NT does this, and it is absurd. Think for a moment: Your system crashes and you need to fix a corrupt filesystem. If you can do that, you are all powerful. You need to upgrade the kernel. If you can do that, you are all powerful. You have a DOS boot floppy and put your hand on the reset button. If you can do that, you are all powerful. You have a chainsaw and are standing next to... > least privalage system rather than set-uid programs, (kernel) Great idea - but how? Many things have been proposed here before. > access control list (ext2) Done? > MaxSix Networking for secure TCP/IP (kernel/net) Huh? > Secure Window System including Labeled Windows (fvwm/X11) Run xauth and give all your windows titles. -- Albert Cahalan albert@ccs.neu.edu ------------------------------ ** 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 ******************************