From owner-freebsd-stable Wed Oct 18 04:43:43 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA07450 for stable-outgoing; Wed, 18 Oct 1995 04:43:43 -0700 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA07443 for ; Wed, 18 Oct 1995 04:43:41 -0700 Received: from hawk.gnome.co.uk (gnome.demon.co.uk [158.152.22.16]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id EAA20922 for ; Wed, 18 Oct 1995 04:42:37 -0700 Received: (from jacs@localhost) by hawk.gnome.co.uk (8.6.12/8.6.12) id MAA01799; Wed, 18 Oct 1995 12:39:49 +0100 Date: Wed, 18 Oct 1995 12:39:49 +0100 Subject: src.doc.ic.ac.uk mirror site problem? To: freebsd-stable@freebsd.org From: jacs@gnome.co.uk (Chris Stenton) Message-Id: Sender: owner-stable@freebsd.org Precedence: bulk Hi, I have just pulled over the freebsd-stable source tree again from src.doc.ic.ac.uk and have noticed that it still has not changed since sept 30th. Is there any know problems with the mirror sites? Chris From owner-freebsd-stable Wed Oct 18 15:15:46 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA25134 for stable-outgoing; Wed, 18 Oct 1995 15:15:46 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA25129 for ; Wed, 18 Oct 1995 15:15:39 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id QAA11314; Wed, 18 Oct 1995 16:17:58 -0600 Date: Wed, 18 Oct 1995 16:17:58 -0600 From: Nate Williams Message-Id: <199510182217.QAA11314@rocky.sri.MT.net> To: stable@FreeBSD.org CC: nate@rocky.sri.MT.net Subject: Linux emulator working? Sender: owner-stable@FreeBSD.org Precedence: bulk Does anyone have the emulator working under -stable? Here's the steps I did: 1) Re-compiled and install a new kernel with COMPAT_LINUX and all of the SHM* options. 2) Install the Linux versions of ld.so, shlibs for normal stuff, and X libraries from the Slackware 2.3 disk on cdrom.com into /compat/linux/lib. 3) modload -e linux_init /lkm/linix_mod.o 4) Attempt to run a linux program, which dies with a core dump. 5) Ktrace of the output gives me this. 184 ktrace RET ktrace 0 184 ktrace CALL execve(0xefbfd88b,0xefbfd7f4,0xefbfd7fc) 184 ktrace NAMI "./xinstall.linux" 184 xinstall.linux RET execve 0 184 xinstall.linux CALL getitimer(0xd7792) 184 xinstall.linux NAMI "/compat/linux/lib/ld.so" 184 xinstall.linux RET getitimer 0 184 xinstall.linux PSIG SIGSEGV SIG_DFL OK, thinking maybe this program had something weird in it, I downloaded executor which Bill Pechter already claimed success on, and I get the exact same error. :( What am I doing wrong? What can I do to fix this? I'm going to try to get Linux-IDL running under FreeBSD to see how the performance compares to the SPARC version we have. Thanks! Nate From owner-freebsd-stable Wed Oct 18 15:42:30 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA26227 for stable-outgoing; Wed, 18 Oct 1995 15:42:30 -0700 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA26222 for ; Wed, 18 Oct 1995 15:42:27 -0700 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.11/8.6.9) id RAA13700; Wed, 18 Oct 1995 17:41:49 -0500 Date: Wed, 18 Oct 1995 17:41:48 -0500 (EST) From: John Fieber To: Nate Williams cc: stable@FreeBSD.org Subject: Re: Linux emulator working? In-Reply-To: <199510182217.QAA11314@rocky.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.org Precedence: bulk On Wed, 18 Oct 1995, Nate Williams wrote: > Does anyone have the emulator working under -stable? > > Here's the steps I did: ... > What am I doing wrong? What can I do to fix this? I'm going to try to > get Linux-IDL running under FreeBSD to see how the performance compares > to the SPARC version we have. Maybe the attached will help? -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ >From rich@lamprey.utmb.eduWed Oct 18 17:40:15 1995 Date: Wed, 20 Sep 1995 09:27:00 -0500 From: Rich Murphey To: FreeBSD-current@freefall.freebsd.org Subject: linux compatibility man page I took netbsd's man page for linux compatibility and added a brief installation guide. I've sent Jordan the nroff source for review. Any suggestions are welcome! Many thanks to Soren Schmidt for the emulator itself! Rich COMPAT LINUX(8) UNIX System Manager's Manual COMPAT LINUX(8) - - NAME COMPAT LINUX - setup procedure for running Linux binaries - INSTALL In order to run static and dynamicly linked Linux binaries, you need a kernel configured with options COMPAT LINUX. Include options SYSVSHM as - well if you plan to run the linux version of doom. cd /sys/i386/conf echo options '"COMPAT LINUX"' >> GENERIC - echo options SYSVSHM >> GENERIC config GENERIC cd /sys/compile/GENERIC make depend; make make install If you don't already have it, build the loadable kernel module /lkm/linux mod.o. - cd /usr/src/lkm/linux make all install clean Once you have both the kernel and lkm installed, invoke linux as root to load the emulator into the kernel. TESTING To test the emulator using the linux version of the game doom, first get the linux shared libraries. mkdir /compat/linux cd /compat/linux ncftp ftp.freebsd.org:pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/linux-emu.tar.gz tar xzf linux-emu.tar.gz rm -rf usr lkm linux-emu.tar.gz The lkm and usr portion of this tar file are redundant since you already have the lkm and /usr/bin/linux. Next install doom itself. ncftp ftp.freebsd.org:pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/linux-doom-1.8.tar.gz tar xzf linux-doom-1.8.tar.gz cd doom-1.8 xdoom DESCRIPTION Most Linux binaries should work, except programs that use Linux-specific features. These include the Linux /proc filesystem (which is different from the optional FreeBSD /proc filesystem), and i386-specific calls, such as enabling virtual 8086 mode. Many linux programs are dynamically linked. So you will also need the Linux shared libraries that the program depends on, and the runtime link- er. Also, you will need to create a "shadow root" directory for Linux binaries on your FreeBSD system. This directory is named /compat/linux. Any file operations done by Linux programs run under FreeBSD will look in this directory first. So, if a Linux program opens, for example, /etc/passwd, FreeBSD will first try to open /compat/linux/etc/passwd, and if that does not exist open the packages that include configuration files, etc under /compat/linux, to avoid naming conflicts with possible FreeBSD counterparts. Shared libraries should also be installed in the shadow tree. Generally, you will need to look for the shared libraries that Linux bi- naries depend on only the first few times that you install a Linux pro- gram on your FreeBSD system. After a while, you will have a sufficient set of Linux shared libraries on your system to be able to run newly im- ported Linux binaries without any extra work. Setting up shared libraries How to get to know which shared libraries Linux binaries need, and where to get them? Basically, there are 2 possibilities (when following these instructions: you will need to be root on your FreeBSD system to do the necessary installation steps). 1. If you have access to a Linux system, see what shared libraries it needs, and copy them to your FreeBSD system. Example: you have just ftp-ed the Linux binary of Doom. Put it on the Linux system you have access to, and check which shared libraries it needs by running `ldd linuxxdoom': (me@linux) ldd linuxxdoom libXt.so.3 (DLL Jump 3.1) => /usr/X11/lib/libXt.so.3.1.0 libX11.so.3 (DLL Jump 3.1) => /usr/X11/lib/libX11.so.3.1.0 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 You would need go get all the files from the last column, and put them under /compat/linux, with the names in the first column as sym- bolic links pointing to them. This means you eventually have these files on your FreeBSD system: /compat/linux/usr/X11/lib/libXt.so.3.1.0 /compat/linux/usr/X11/lib/libXt.so.3 (symbolic link to the above) /compat/linux/usr/X11/lib/libX11.so.3.1.0 /compat/linux/usr/X11/lib/libX11.so.3 (symbolic link to the above) /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 (symbolic link to the above) Note that if you already have a Linux shared library with a matching major revision number to the first column of the 'ldd' output, you won't need to copy the file named in the last column to your system, the one you already have should work. It is advisable to copy the shared library anyway if it is a newer version, though. You can re- move the old one, as long as you make the symbolic link point to the new one. So, if you have these libraries on your system: /compat/linux/lib/libc.so.4.6.27 /compat/linux/lib/libc.so.4 -> /compat/linux/lib/libc.so.4.6.27 and you find that the ldd output for a new binary you want to in- stall is: libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 you won't need to worry about copying /lib/libc.so.4.6.29 too, be- cause the program should work fine with the slightly older version. You can decide to replace the libc.so anyway, and that should leave you with: /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 -> /compat/linux/lib/libc.so.4.6.29 Please note that the symbolic link mechanism is only needed for Lin- ux binaries, the FreeBSD runtime linker takes care of looking for matching major revision numbers itself, you don't need to worry about that. Finally, you must make sure that you have the Linux runtime linker and its config files on your system. You should copy these files from the Linux system to their appropriate place on your FreeBSD system (to the /compat/linux tree): /lib/ld.so /etc/ld.so.cache /etc/ld.so.config 2. You don't have access to a Linux system. In that case, you should get the extra files you need from various ftp sites. Information on where to look for the various files is appended below. For now, let's assume you know where to get the files. Retrieve the following files (all from the same ftp site to avoid any version mismatches), and install them under /compat/linux (i.e. /foo/bar is installed as /compat/linux/foo/bar): /sbin/ldconfig /usr/bin/ldd /lib/libc.so.x.y.z /lib/ld.so ldconfig and ldd don't necessarily need to be under /compat/linux, you can install them elsewhere in the system too. Just make sure they don't conflict with their FreeBSD counterparts. A good idea would be to install them in /usr/local/bin as ldconfig-linux and ldd-linux. Create the file /compat/linux/etc/ld.so.conf, containing the direc- tories in which the Linux runtime linker should look for shared libs. It is a plain text file, containing a directory name on each line. /lib and /usr/lib are standard, you could add the following: /usr/X11/lib /usr/local/lib Note that these are mapped to /compat/linux/XXXX by FreeBSD's compat code, and should exist as such on your system. Run the Linux ldconfig program. It should be statically linked, so it doesn't need any shared libraries by itself. It will create the file /compat/linux/etc/ld.so.cache You should rerun the Linux ver- sion of the ldconfig program each time you add a new shared library. You should now be set up for Linux binaries which only need a shared libc. You can test this by running the Linux ldd on itself. Suppose that you have it installed as ldd-linux, it should produce something like: (me@FreeBSD) ldd-linux `which ldd-linux` libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 This being done, you are ready to install new Linux binaries. When- ever you install a new Linux program, you should check if it needs shared libraries, and if so, whether you have them installed in the /compat/linux tree. To do this, you run the Linux version ldd on the new program, and watch its output. ldd (see also the manual page for ldd(1)) will print a list of shared libraries that the program depends on, in the form () => . If it prints "not found" in stead of it means that you need an extra library. Which library this is, is shown in , which will be of the form libXXXX.so. You will need to find a libXXXX.so.. on a Linux ftp site, and install it on your system. The XXXX (name) and (major revision number) should match; the minor number(s) are less important, though it is ad- vised to take the most recent version. Finding the necessary files. Note: the information below is valid as of the ime this document was written (March, 1995), but certain details such as names of ftp sites, directories and distribution names may have changed by the time you read this. Linux is distributed by several groups that make their own set of bina- ries that they distribute. Each distribution has its own name, like "Slackware" or "Yggdrasil". The distributions are available on a lot of ftp sites. Sometimes the files are unpacked, and you can get the individ- ual files you need, but mostly they are stored in distribution sets, usu- ally consisting of subdirectories with gzipped tar files in them. The primary ftp sites for the distributions are: sunsite.unc.edu:/pub/Linux/distributions tsx-11.mit.edu:/pub/linux/distributions Some European mirrors: ftp.luth.se:/pub/linux/distributions ftp.demon.co.uk:/pub/linux/distributions src.doc.ic.ac.uk:/packages/linux/distributions For simplicity, let's concentrate on Slackware here. This distribution consists of a number of subdirectories, containing separate packages. Normally, they're controlled by an install program, but you can retrieve files "by hand" too. First of all, you will need to look in the "con- tents" subdir of the distribution. You will find a lot of small textfiles here describing the contents of the seperate packages. The fastest way to look something up is to retrieve all the files in the contents subdirec- tory, and grep through them for the file you need. Here is an example of a list of files that you might need, and in which contents-file you will find it by grepping through them: Needed Package ld.so ldso ldconfig ldso ldd ldso libc.so.4 shlibs libX11.so.6.0 xf lib - libXt.so.6.0 xf lib - libX11.so.3 oldlibs libXt.so.3 oldlibs So, in this case, you will need the packages ldso, shlibs, xf lib and - oldlibs. In each of the contents-files for these packages, look for a line saying "PACKAGE LOCATION", it will tell you on which 'disk' the package is, in our case it will tell us in which subdirectory we need to look. For our example, we would find the following locations: Package Location ldso diska2 shlibs diska2 oldlibs diskx6 xf lib diskx9 - The locations called "diskXX" refer to the "slakware/XX" subdirectories of the distribution, others may be found in the "contrib" subdirectory. In this case, we could now retrieve the packages we need by retrieving the following files (relative to the root of the Slackware distribution tree): slakware/a2/ldso.tgz slakware/a2/shlibs.tgz slakware/x6/oldlibs/tgz slakware/x9/xf lib.tgz - Extract the files from these gzipped tarfiles in your /compat/linux di- rectory (possibly omitting or afterwards removing files you don't need), and you are done. BUGS The information about Linux distributions may become outdated. SEE ALSO ftp.freebsd.org:pub/FreeBSD/2.0.5-RELEASE/xperimnt/linux-emu/README /usr/src/sys/i386/ibcs2/README.iBCS2 4th Berkeley Distribution March 2, 1995 5 From owner-freebsd-stable Wed Oct 18 16:03:40 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA00672 for stable-outgoing; Wed, 18 Oct 1995 16:03:40 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA00645 for ; Wed, 18 Oct 1995 16:03:36 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA11430; Wed, 18 Oct 1995 17:05:46 -0600 Date: Wed, 18 Oct 1995 17:05:46 -0600 From: Nate Williams Message-Id: <199510182305.RAA11430@rocky.sri.MT.net> To: John Fieber Cc: Nate Williams , stable@FreeBSD.org Subject: Re: Linux emulator working? In-Reply-To: References: <199510182217.QAA11314@rocky.sri.MT.net> Sender: owner-stable@FreeBSD.org Precedence: bulk > > Does anyone have the emulator working under -stable? > > > > Here's the steps I did: > > ... > > > What am I doing wrong? What can I do to fix this? I'm going to try to > > get Linux-IDL running under FreeBSD to see how the performance compares > > to the SPARC version we have. > > Maybe the attached will help? It did sort of. I downloaded the stuff from the xperiment directory which basically let me know that I need newer versions of the older type of libraries. Basically, I got newer libraries and run-time linker, but unfortunately they are the wrong binary type. moth# file lib.new/* lib.new/ld-linux.so.1.6.5: ELF 32-bit LSB dynamic lib i386 (386 and up) Version 1 lib.new/ld.so: Linux/i386 demand-paged executable (QMAGIC) lib.new/libc.so.4.6.27: Linux/i386 demand-paged executable (QMAGIC) lib.new/libcurses.so.0.1.2: Linux/i386 demand-paged executable (QMAGIC) lib.new/libm.so.4.6.27: Linux/i386 demand-paged executable (QMAGIC) Versus the versions which seem to work: moth# file lib/* lib/ld.so: Linux/i386 demand-paged executable (ZMAGIC) lib/libc.so.4: Linux/i386 demand-paged executable (ZMAGIC) lib/libm.so.4: Linux/i386 demand-paged executable (ZMAGIC) lib/libX11.so.3: Linux/i386 demand-paged executable (ZMAGIC) lib/libXt.so.3: Linux/i386 demand-paged executable (ZMAGIC) Note that the newer versions also have a minor #, and the older versions are ZMAGIC executables while the new versions are QMAGIC executables. Where would I find 'newer' libraries and run-time linker which use the (older?) ZMAGIC format? In particular, I need newer X libraries. :( Thanks so far, Nate From owner-freebsd-stable Wed Oct 18 16:30:41 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA01583 for stable-outgoing; Wed, 18 Oct 1995 16:30:41 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA01578 for ; Wed, 18 Oct 1995 16:30:34 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA11497; Wed, 18 Oct 1995 17:32:50 -0600 Date: Wed, 18 Oct 1995 17:32:50 -0600 From: Nate Williams Message-Id: <199510182332.RAA11497@rocky.sri.MT.net> To: stable@freebsd.org Cc: nate@rocky.sri.MT.net (Nate Williams) Subject: Success ( was Re: Linux emulator working?) <199510182243.SAA22201@shell.monmouth.com> Sender: owner-stable@freebsd.org Precedence: bulk > > Does anyone have the emulator working under -stable? YES! I used archie to find a linux site with newer libraries on the net (which I'm in the process of downloading), and so far things are looking very promising. I'm now able to run the X installation program supplied by IDL. Now, to find the disk space to install it all. :( Thanks for the pointers. Nate From owner-freebsd-stable Sat Oct 21 16:36:11 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA17067 for stable-outgoing; Sat, 21 Oct 1995 16:36:11 -0700 Received: from crash.ops.neosoft.com (root@crash.ops.NeoSoft.COM [198.64.212.50]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA17062 for ; Sat, 21 Oct 1995 16:36:08 -0700 Received: (from smace@localhost) by crash.ops.neosoft.com (8.7.1/8.7.1) id SAA04884 for stable@freebsd.org; Sat, 21 Oct 1995 18:33:28 -0500 (CDT) From: Scott Mace Message-Id: <199510212333.SAA04884@crash.ops.neosoft.com> Subject: problem with DES and telnet To: stable@freebsd.org Date: Sat, 21 Oct 1995 18:33:26 -0500 (CDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org Precedence: bulk I just installed the 1020 snap, no problems except, if you install DES (and get the DES telnet and others) it is getting a telnet binary linked for kerberos but not installing the kerberos libraries... so if you just select DES binaries on the DES submenu and nothing else, it gets the follwing error: can't find shared library "libdes.so.2.0" Scott From owner-freebsd-stable Sat Oct 21 22:12:30 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA25507 for stable-outgoing; Sat, 21 Oct 1995 22:12:30 -0700 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id WAA25502 for ; Sat, 21 Oct 1995 22:12:25 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA20625 (5.65c8/HUTCS-S 1.4 for ); Sun, 22 Oct 1995 07:12:20 +0200 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id HAA11965; Sun, 22 Oct 1995 07:12:29 +0200 Date: Sun, 22 Oct 1995 07:12:29 +0200 Message-Id: <199510220512.HAA11965@shadows.cs.hut.fi> From: Heikki Suonsivu To: "Jordan K. Hubbard" Cc: stable@freebsd.org In-Reply-To: "Jordan K. Hubbard"'s message of 21 Oct 1995 17:02:36 +0200 Subject: 2.1.0-951020-SNAP - 2.1 *Release Candidate* Sender: owner-stable@freebsd.org Precedence: bulk The 2.1 release candidate is now available for testing. Modulo whatever problems all of you find between now and the final build, this will be what you find in 2.1! There are a few small things known-missing or broken in this snapshot, and those things ARE scheduled to be added before 2.1 is built. However, it may still be instructive to list them here so that snapshot installers don't stumble over them: o The WEB configuration is unimplemented. o The package installer may or may not do the right thing with chained adds. I haven't had the chance to adequately test this, given my limited testing hardware (I'm using a laptop with an 120MB hard disk!). o Some instrumentation is probably missing from the configuration file mechanism. o The HTML documentation reader menu may need some work. o The commercial distribution is still the 2.0.5 version - this will be updated before the final 2.1 release. o The bindist now includes all documentation from /usr/share/doc. If this ends up blowing up some of the minimally configured systems, we may need to make an optional `doc' distribution sooner than planned. Is the slirp panic bug already catched up or still there? I have seen it PR'd at least two times in addition to my case, and we get regular panics almost every day on this. I can provide dumps & kernels with full symbols if someone is interested, it always panics in fchmod and it is quite consistent. v_mount is NULL, I don't know what circumstances this happens (it is a pipe or something which isn't on any file system, maybe?). Could just returning error from the fchmod system call when v_mount is NULL be enough of a workaround? The code seems to be similar in several other system calls, but I know too little about the kernel to know whether any of these could exhibit the same problem, if suitably misused. The PR is kern/782. ftp://clinet.fi/pub/FreeBSD/crashdumps/*.29.gz is one example (I have more of them). slirp is quite popular slip/ppp emulation kludge, unfortunately large number of our users use it. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-stable Sat Oct 21 23:02:31 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA26143 for stable-outgoing; Sat, 21 Oct 1995 23:02:31 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA26137 for ; Sat, 21 Oct 1995 23:02:26 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id XAA01822; Sat, 21 Oct 1995 23:02:24 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id XAA04220; Sat, 21 Oct 1995 23:01:54 -0700 Message-Id: <199510220601.XAA04220@corbin.Root.COM> To: Heikki Suonsivu cc: "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: 2.1.0-951020-SNAP - 2.1 *Release Candidate* In-reply-to: Your message of "Sun, 22 Oct 95 07:12:29 +0200." <199510220512.HAA11965@shadows.cs.hut.fi> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 21 Oct 1995 23:01:53 -0700 Sender: owner-stable@freebsd.org Precedence: bulk >Is the slirp panic bug already catched up or still there? I have seen it >PR'd at least two times in addition to my case, and we get regular panics >almost every day on this. I can provide dumps & kernels with full symbols >if someone is interested, it always panics in fchmod and it is quite >consistent. v_mount is NULL, I don't know what circumstances this happens >(it is a pipe or something which isn't on any file system, maybe?). Could >just returning error from the fchmod system call when v_mount is NULL be >enough of a workaround? Sorry that I missed your bug report...you really should trim down your kernel config file - it was so long that I missed the important information at the end of your bug report. :-) Anyway, I've just looked at the problem...it is fixable, but requires an architectural change (one that was made to 4.4BSD-lite/2, but not yet to FreeBSD). Basically, the check for the filesystem being read-only is done at the wrong layer and whenever a filesystem is forcibly dismounted, there is a chance that operations on still-open files will cause this panic. This happens because the filesystem mountpoint has been ripped away. The type/ops vector is also changed to VBAD/deadfs so that future operations on the vnode are directed to the deadfs, but in your case, v_mount is referenced when it obviously shouldn't have been (before it gets to the FS layer). The fix is to move the references to v_mount into the filesystem layer and out of the syscall - this way the fchown (and many other syscalls) will end up in the dead_setattr() (which is defined to return EBADF), before v_mount is ever referenced. ...problem solved. I don't know if I consider this a "critical" bug, however, as it might be difficult to manifest during normal operations. I think that "slirp" must be doing something strange - like an fchown() on a TTY. I'll have to look into this in more detail. -DG From owner-freebsd-stable Sat Oct 21 23:55:35 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA27166 for stable-outgoing; Sat, 21 Oct 1995 23:55:35 -0700 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id XAA27161 for ; Sat, 21 Oct 1995 23:55:31 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA20931 (5.65c8/HUTCS-S 1.4 for ); Sun, 22 Oct 1995 08:55:20 +0200 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id IAA12565; Sun, 22 Oct 1995 08:55:30 +0200 Date: Sun, 22 Oct 1995 08:55:30 +0200 Message-Id: <199510220655.IAA12565@shadows.cs.hut.fi> From: Heikki Suonsivu To: davidg@root.com Cc: Heikki Suonsivu , "Jordan K. Hubbard" , stable@freebsd.org Subject: Re: 2.1.0-951020-SNAP - 2.1 *Release Candidate* In-Reply-To: <199510220601.XAA04220@corbin.Root.COM> References: <199510220512.HAA11965@shadows.cs.hut.fi> <199510220601.XAA04220@corbin.Root.COM> Sender: owner-stable@freebsd.org Precedence: bulk David Greenman writes: > Sorry that I missed your bug report...you really should trim down your > kernel config file - it was so long that I missed the important information > at the end of your bug report. :-) Sorry, I forgot about using sed :-( > syscall - this way the fchown (and many other syscalls) will end up in the > dead_setattr() (which is defined to return EBADF), before v_mount is ever > referenced. ...problem solved. > I don't know if I consider this a "critical" bug, however, as it might be > difficult to manifest during normal operations. I think that "slirp" must be I think most generic servers get just this kind of pounding; many universities do not provide IP routing for students, but they do provide unix systems to play with, so things like slirp are common. Similarly getting a unix account is often cheaper than getting a SLIP/PPP account. Slirp isn't old thing, so this isn't yet happening world-wide. I think it found its way into the ports just a couple of weeks ago? > doing something strange - like an fchown() on a TTY. I'll have to look into > this in more detail. In a system where 40 people are learning to program in C in unix environment, you can be pretty sure to find that someone doing fchown on a tty is quite normal, just like "main() { char b; read("filename", b, 100); }" :-) -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN