From owner-freebsd-stable Sun Jun 27 2:16:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id D719F14E57 for ; Sun, 27 Jun 1999 02:16:31 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id TAA18400; Sun, 27 Jun 1999 19:16:29 +1000 (EST) Message-ID: <19990627191626.53465@welearn.com.au> Date: Sun, 27 Jun 1999 19:16:26 +1000 From: Sue Blake To: freebsd-stable@freebsd.org Subject: Upgrading - one more time please Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this has been done to death, I've read it all, and each round of upgrading advice just keeps getting more confusing. I've been sitting here like a chook in the middle of the highway watching the traffic buzz by for months while my legs atrophy, and now I just gotta move. I've got a machine running 2.2.7-STABLE which I want to upgrade to the current -STABLE. I also want the full repository. I have a 3.1-RELEASE CD, so I can grab its repository, cvsup, and pull out the latest -STABLE sources. Then, according to Jordan's post, I just go 'make upgrade' and build a new kernel, but according to Mike's post it might not work, according to other people I might have to upgrade first to 2.2.8 and/or do or not do lots of other hoop jumping. Then I look at Ruslan Ermilov's nice tutorial for 3.0-STABLE and it's telling a whole different story again. And there was some murmuring about "installing new boot blocks" a while ago but I don't recall seeing an explanation of what exactly one has to do. I wonder what else I've forgotten and where it might be written down. I've found nothing relevant in the Handbook or the tutorials or the *.TXT files for 3.1 and 3.2-RELEASE, and the URL given for the most recent 3.1-RELEASE errata comes up 404. Everything I need is probably written in some handy place that hasn't popped up yet, and it's sure to be in the mail archives *somewhere* among a lot of conflicting opinions and horror stories, but I can't identify the correct advice. I only have facilities to backup the most essential of my data, and it'd be really nice if I could keep the rest too, so I don't want to take too many unnecessary risks. If there's anyone left who's neither sick of this topic nor uncertain about what to do, could you help me find what the relevant procedure is? -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 2:43:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ceia.nordier.com (m1-32-dbn.dial-up.net [196.34.155.32]) by hub.freebsd.org (Postfix) with ESMTP id 8E7AD151B2 for ; Sun, 27 Jun 1999 02:43:23 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA15120; Sun, 27 Jun 1999 11:42:25 +0200 (SAST) From: Robert Nordier Message-Id: <199906270942.LAA15120@ceia.nordier.com> Subject: Re: Upgrading - one more time please In-Reply-To: <19990627191626.53465@welearn.com.au> from Sue Blake at "Jun 27, 1999 07:16:26 pm" To: sue@welearn.com.au (Sue Blake) Date: Sun, 27 Jun 1999 11:42:23 +0200 (SAST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've got a machine running 2.2.7-STABLE which I want to upgrade to > the current -STABLE. I also want the full repository. > I have a 3.1-RELEASE CD, so I can grab its repository, cvsup, and > pull out the latest -STABLE sources. > > Then, according to Jordan's post, I just go 'make upgrade' and build a > new kernel, but according to Mike's post it might not work, according > to other people I might have to upgrade first to 2.2.8 and/or do or not > do lots of other hoop jumping. Then I look at Ruslan Ermilov's nice > tutorial for 3.0-STABLE and it's telling a whole different story again. > And there was some murmuring about "installing new boot blocks" a while > ago but I don't recall seeing an explanation of what exactly one has to > do. I wonder what else I've forgotten and where it might be written > down. We did a number of 2.2.1R to 3.2R upgrades here recently. Probably the simplest approach is to use your 3.1R CD-ROM and install over the existing files in "upgrade" mode, preferably after backing up at least your own files. The 3.1R binaries should then have little or no difficult doing a "make world" on the -stable sources, once you have them. Regarding the boot blocks: if you get an error message when rebooting 3.1R, type in /boot/loader at the "boot: " prompt and the machine should boot. Thereafter, you can do a disklabel -B wd0 (or equivalent) to install the new boot blocks. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 10:57:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 925D715065 for ; Sun, 27 Jun 1999 10:57:57 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn1156.bossig.com [208.26.241.156]) by revolution.3-cities.com (8.9.3/8.9.3) with ESMTP id KAA23724; Sun, 27 Jun 1999 10:57:20 -0700 (PDT) Message-ID: <377665F2.9E60992B@3-cities.com> Date: Sun, 27 Jun 1999 10:57:06 -0700 From: Kent Stewart Reply-To: kstewart@3-cities.com Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Nordier Cc: Sue Blake , freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading - one more time please References: <199906270942.LAA15120@ceia.nordier.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > > > I've got a machine running 2.2.7-STABLE which I want to upgrade to > > the current -STABLE. I also want the full repository. > > I have a 3.1-RELEASE CD, so I can grab its repository, cvsup, and > > pull out the latest -STABLE sources. > > > > Then, according to Jordan's post, I just go 'make upgrade' and build a > > new kernel, but according to Mike's post it might not work, according > > to other people I might have to upgrade first to 2.2.8 and/or do or not > > do lots of other hoop jumping. Then I look at Ruslan Ermilov's nice > > tutorial for 3.0-STABLE and it's telling a whole different story again. > > And there was some murmuring about "installing new boot blocks" a while > > ago but I don't recall seeing an explanation of what exactly one has to > > do. I wonder what else I've forgotten and where it might be written > > down. > > We did a number of 2.2.1R to 3.2R upgrades here recently. Probably > the simplest approach is to use your 3.1R CD-ROM and install over > the existing files in "upgrade" mode, preferably after backing up > at least your own files. The 3.1R binaries should then have little > or no difficult doing a "make world" on the -stable sources, once > you have them. You want to do this from a floppy boot. At 3.1 the boot became too large for a single floppy and you have two to create. The bootblocks are upgraded at the same time when you do the sysinstall upgrade from the floppy. The upgrade to 3.2-stable is also a big step. The structure of files such as rc.conf changed with the base file in /etc/defaults and then incremental changes in /etc. Device names changed and there are new devices that may need to be created. Mergemaster makes the 3.1-release to 3.2-stable upgrade much easier. Kent > > Regarding the boot blocks: if you get an error message when rebooting > 3.1R, type in > > /boot/loader > > at the "boot: " prompt and the machine should boot. Thereafter, you > can do a > > disklabel -B wd0 > > (or equivalent) to install the new boot blocks. > > -- > Robert Nordier > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 12: 9:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 7ACD714C38 for ; Sun, 27 Jun 1999 12:09:40 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA16380; Sun, 27 Jun 1999 12:09:27 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <377676E8.360985EA@gorean.org> Date: Sun, 27 Jun 1999 12:09:28 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Randall Hopper Cc: stable@freebsd.org Subject: Re: 3.2-RELEASE Feedback References: <19990626184311.A5290@ipass.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thank you for your very detailed report. We definitely need feedback like this. Randall Hopper wrote: > 2) Where's the tcpdump port/package -- missing? Hmmm.. you want to use a tcpdump other than the one that comes with the system in /usr/sbin/tcpdump? I don't remember ever seeing a tcpdump port, but that's not really my area of expertise, so I might have missed it. > 3) If I switch the console to 43 or 60 line mode with vidcontrol, "man" and > other full-screen progs don't automatically pick up the correct number > of lines like they did in 3.0-RELEASE. They assume 25-line mode. > > vidcontrol < /dev/ttyv0 -f 8x8 cp866-8x8 > vidcontrol < /dev/ttyv0 132x43 > vidcontrol < /dev/ttyv1 132x43 > vidcontrol < /dev/ttyv2 132x43 > > I have to fiddle with "stty rows" and hand the console the right number. This is usually a function of your pager, and/or your shell. If you use bash, try setting 'shopt -s checkwinsize' and see if that helps. If you are still using 'more' as the default pager, try installing less from the ports and then do, 'export PAGER=/usr/local/bin/less' (or the appropriate *csh setenv command) and see if that helps. If neither do, you should send in a PR for this since (TMK) you shouldn't have to jump through those hoops. Do 'man send-pr' for more details if needed. > 7) wcd0 became acd0 in the kernel config file, but we still mount wcd0c. (?) > Is this an oversight? It's in the default fstab for example. More of a compatability issue. We like to rename things for no good reason, then keep the old names lying about to confuse people. Welcome to FreeBSD. :) > Also, the kernel config and build doesn't fail with the wcd0 device in > it; but the CDROM doesn't work after booting on that kernel. Hmmm.. are you sure that you have included the controller that the CD is on in your kernel config? These are the wdc[01] devices. Also, do you have the ATAPI options in there properly? > 8) (Nit) Boot-up probes spelling error: > "bt_isa_probe: Probe failled for card at 0x330" This is something you should definitely send a PR for. It will get fixed 10 times faster than just pointing it out here. Also, if you supply a patch (thereby indicating that you have found the exact location and have saved people looking at the PR that much more work) it will almost certainly be committed. If you need a hint on how to find it, grep is your friend. > 9) rc.firewall - if firewall_type is a file, it feeds each line in it to > ipfw. > > BUT ipfw doesn't toss comments, so you can't document your firewall > commands, and this IMO isn't a good option. This has been kicked around many times, and each time there is a "good" reason not to "fix" this. So, the consensus is, if you want to do it that way, go right ahead. I don't agree with the consensus, but there are some things around here not worth beating your head against. > 10) There was no ports_update package in the packages dir when I downloaded. > I found a reference to this in DejaNews, and grabbed the /usr/ports/Mk > tree from ftp.freebsd.org. It worked, but what should users really be > doing? What has been happening of late is that in order to follow the ports you kind of had to follow -stable. Some of the recent changes, like including the mk stuff in the /usr/ports tree have helped this situation. I think that after the next release it will be even easier because it seems like the rest of the bogons have shaken out of this, but for now what users "should" do is kind of up in the air. I personally encourage people not to update ports unless they also update the system at least to a recent version of -stable. > 11) When copying directory trees between two IDE drives on the PCI > bus, the system really dogs down -- emacs takes 15 seconds to come up > when normally it takes 1 -- didn't do that on 3.0-RELEASE. I would raise this issue in a seperate e-mail. It sounds to me like something worthy of attention. > 13) 3.2-RELEASE still locks the system hard when a file system is mismounted, > just as 3.0-RELEASE did: > > # mount /dev/wd4s1 /mnt > - fails with incorrect superblock (it's a FAT partition) > # mount -t msdos /dev/wd4s1 /mnt > - locks the system hard Also something that deserves a seperate e-mail. Is it possible for you to add DDB to your kernel and then drop into the debugger when this happens and do a backtrace? That would probably be very helpful to the developers of the disk system. I'd say that you should raise 11) and 13) on the -hackers list. > 14) I repartitioned and labeled a slice on wd4, and each time Fdisk > succeeded and Label failed the first time ("Invalid Argument"). Then, > after I exited sysinstall and restarted it, Label and Newfs worked -- > strange. I repeated this procedure twice -- same results. The sysinstall interface to those programs is notoriously tempermental. The command line versions are rather difficult to learn, but more consistent in their behavior. > 15) /opt/bin/xanim.2.70.1 +Ze +B +CF4 +Av10 -geometry +100+100 fox.mov > ld.so failed: Can't find shared library "libgnumalloc.so.2.0" > > Something missing from the compat libs. I pulled it off my 3.0-R > partition on another disk. I believe this is fixed in -stable, I have that file and I didn't do anything special to get it. Once again, thank you for your detailed feedback. I hope the above is helpful. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 15:50:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 1C19315160 for ; Sun, 27 Jun 1999 15:50:17 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-79.dialup.rdu.ipass.net [209.170.132.79]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id SAA23152; Sun, 27 Jun 1999 18:50:13 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id SAA01522; Sun, 27 Jun 1999 18:52:03 -0400 (EDT) (envelope-from rhh) Date: Sun, 27 Jun 1999 18:52:03 -0400 From: Randall Hopper To: Doug Cc: stable@freebsd.org Subject: Re: 3.2-RELEASE Feedback Message-ID: <19990627185202.A750@ipass.net> References: <19990626184311.A5290@ipass.net> <377676E8.360985EA@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <377676E8.360985EA@gorean.org>; from Doug on Sun, Jun 27, 1999 at 12:09:28PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |> 2) Where's the tcpdump port/package -- missing? | | Hmmm.. you want to use a tcpdump other than the one that comes with the |system in /usr/sbin/tcpdump? I don't remember ever seeing a tcpdump port, |but that's not really my area of expertise, so I might have missed it. My bad. Don't know how I missed seeing that. I was looking for a port to incorporate a switch I patch into tcpdump whenever I upgrade. In the past, I've patched it directly into the source and forgotten there wasn't a port (and I didn't realize it was in bindist). |> 3) If I switch the console to 43 or 60 line mode with vidcontrol, "man" and |> other full-screen progs don't automatically pick up the correct number |> of lines like they did in 3.0-RELEASE. They assume 25-line mode. |> |> vidcontrol < /dev/ttyv0 -f 8x8 cp866-8x8 |> vidcontrol < /dev/ttyv0 132x43 |> vidcontrol < /dev/ttyv1 132x43 |> vidcontrol < /dev/ttyv2 132x43 |> |> I have to fiddle with "stty rows" and hand the console the right number. | | This is usually a function of your pager, and/or your shell. If you use |bash, try setting 'shopt -s checkwinsize' and see if that helps. If you are |still using 'more' as the default pager, try installing less from the ports |and then do, 'export PAGER=/usr/local/bin/less' (or the appropriate *csh |setenv command) and see if that helps. If neither do, you should send in a |PR for this since (TMK) you shouldn't have to jump through those hoops. Do |'man send-pr' for more details if needed. less is actually what I'm using. I'll back out and try both pagers, and file a PR if I don't have any luck. |> Also, the kernel config and build doesn't fail with the wcd0 device in |> it; but the CDROM doesn't work after booting on that kernel. | | Hmmm.. are you sure that you have included the controller that the CD is |on in your kernel config? These are the wdc[01] devices. Also, do you have |the ATAPI options in there properly? I believe I have it right: controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 # Can't get FreeBSD folks to commit IO_WD3 to isa.h, so we hard-code the addr #controller wdc2 at isa? port "IO_WD3" bio irq 11 flags 0xa0ffa0ff controller wdc2 at isa? port "0x1e8" bio irq 11 flags 0xa0ffa0ff disk wd4 at wdc2 drive 0 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM This is my current config. The same lines with acd0 replaced with wcd0 is when I had the trouble I described (kernel builds, but IDE CD-ROM doesn't work). This is the same text I had for 3.0-RELEASE, except that I removed the "vector wdintr". Seems that's not needed anymore |> 8) (Nit) Boot-up probes spelling error: |> "bt_isa_probe: Probe failled for card at 0x330" | | This is something you should definitely send a PR for. It will get fixed |10 times faster than just pointing it out here. Also, if you supply a patch |(thereby indicating that you have found the exact location and have saved |people looking at the PR that much more work) it will almost certainly be |committed. If you need a hint on how to find it, grep is your friend. Ok, ...done. |> 14) I repartitioned and labeled a slice on wd4, and each time Fdisk |> succeeded and Label failed the first time ("Invalid Argument"). Then, |> after I exited sysinstall and restarted it, Label and Newfs worked -- |> strange. I repeated this procedure twice -- same results. | | The sysinstall interface to those programs is notoriously tempermental. Right. That's why I was using sysinstall. :-) |The command line versions are rather difficult to learn, but more |consistent in their behavior. | Once again, thank you for your detailed feedback. I hope the above is |helpful. And thanks for the reply. I'll follow-up on those few you suggested separate handling for. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 16: 8:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from muffin.highwire.local (pool-1-p69.innotts.co.uk [212.56.33.69]) by hub.freebsd.org (Postfix) with ESMTP id D5B621518E for ; Sun, 27 Jun 1999 16:08:03 -0700 (PDT) (envelope-from robmel@innotts.co.uk) Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20]) by muffin.highwire.local (8.9.3/8.9.3) with ESMTP id AAA20263 for ; Mon, 28 Jun 1999 00:07:25 +0100 (BST) (envelope-from robmel@innotts.co.uk) X-Sender: robmel@muffin.highwire.local Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Jun 1999 00:08:08 +0100 To: freebsd-stable@freebsd.org From: Robin Melville Subject: NFS hanging in 3.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I searched the mailing list for clues on this with no luck. Running 3.2-STABLE on a variety of garage-sale pentium I and K6 boxes with and without scsi I almost always get hung and unkillable userland processes when they are reading writing NFS shares mounted over udp. Mounting -otcp always works well. Using NFS 2 makes no difference. None of the machines are using softupdates. While I'm happy to always use tcp mounts I wonder whether something is quite badly wrong with the kernel nfs code, or whether I've done something wrong. I'd be happy to further diagnose the problems if someone would tell me what they would like me to do. BTW 3.2-STABLE is turning out to be as robust and excellent as 2.2.8 was in every other respect. Best regards Robin. ---------------------------------------------------------------------- Robin Melville, Addiction Information Service Nottingham Alcohol & Drug Team Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 work: robmel@nadt.org.uk home: robmel@innotts.co.uk Pages: http://www.innotts.co.uk/nadt ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 16:22:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 87BB814ECD for ; Sun, 27 Jun 1999 16:22:23 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-79.dialup.rdu.ipass.net [209.170.132.79]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id TAA26743 for ; Sun, 27 Jun 1999 19:22:19 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id TAA01825 for stable@freebsd.org; Sun, 27 Jun 1999 19:24:07 -0400 (EDT) (envelope-from rhh) Date: Sun, 27 Jun 1999 19:24:07 -0400 From: Randall Hopper To: stable@freebsd.org Subject: 3.2-R Disk Performance Woes Message-ID: <19990627192407.A1735@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When copying directory trees between two IDE drives on the PCI bus, the system really dogs down -- emacs takes 15 seconds to come up when normally it takes 1 -- didn't do that on 3.0-RELEASE. I have these drives configed up for DMA: controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0xa0ffa0ff disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0xa0ffa0ff disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 These are stock IBM Deskstar drives: wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , DMA, 32-bit, multi-block-16 wd1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S Any thoughts? Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 16:26: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 8B747151BC for ; Sun, 27 Jun 1999 16:26:04 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-79.dialup.rdu.ipass.net [209.170.132.79]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id TAA27146 for ; Sun, 27 Jun 1999 19:25:56 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id TAA01918 for stable@freebsd.org; Sun, 27 Jun 1999 19:27:40 -0400 (EDT) (envelope-from rhh) Date: Sun, 27 Jun 1999 19:27:40 -0400 From: Randall Hopper To: stable@freebsd.org Subject: 3.2-R mount lockup Message-ID: <19990627192740.A1837@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.2-RELEASE still locks the system hard when a file system is mismounted, just as 3.0-RELEASE did: # mount /dev/wd4s1 /mnt - fails with incorrect superblock (it's a FAT partition) # mount -t msdos /dev/wd4s1 /mnt - locks the system hard If you omit the first (incorrect) mount command, then it mounts successfully. Is this a known problem, or should I file a PR? Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 16:49: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from the.oneinsane.net (the.oneinsane.net [207.113.133.228]) by hub.freebsd.org (Postfix) with ESMTP id DDC4714E85 for ; Sun, 27 Jun 1999 16:49:00 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: from lunatic.oneinsane.net (insane@lunatic.oneinsane.net [207.113.133.231]) by the.oneinsane.net (8.9.3/8.9.3) with ESMTP id QAA23139 for ; Sun, 27 Jun 1999 16:48:59 -0700 (PDT) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.3/8.9.3) id QAA04767 for freebsd-stable@freebsd.org; Sun, 27 Jun 1999 16:48:58 -0700 (PDT) (envelope-from insane) Date: Sun, 27 Jun 1999 16:48:58 -0700 From: "Ron 'The InSaNe One' Rosson" To: freebsd-stable@freebsd.org Subject: Natd unrecognized command Message-ID: <19990627164858.A4742@lunatic.oneinsane.net> Reply-To: Ron Rosson Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Operating-System: FreeBSD lunatic.oneinsane.net 3.2-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 4:46PM up 4 hrs, 2 users, load averages: 0.00, 0.02, 0.03 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to get a VPN to a Machine on my local network from another outside machine. When I type the following: natd -pptpalias 192.168.2.7 Here is the response I get: natd: unknown option pptpalias Did I miss something.. It is there in the man page. The box is running 3.2-STABLE as of Yesterday. TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- All I wanted was a signature, and I got my two front teeth. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 17:45: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 055C715229 for ; Sun, 27 Jun 1999 17:44:56 -0700 (PDT) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.3/8.9.2) id TAA00518; Sun, 27 Jun 1999 19:44:59 -0500 (CDT) (envelope-from bob) Date: Sun, 27 Jun 1999 19:44:59 -0500 From: Bob Willcox To: "Andrew W. Flury" Cc: "Danny J. Zerkel" , freebsd-stable@FreeBSD.ORG, holtor@yahoo.com Subject: Re: kern/10411: top, vmstat, iostat show 0% cpu idle & usage on SMP system Message-ID: <19990627194459.A452@luke.pmr.com> Reply-To: Bob Willcox References: <37591E90.2FD85193@columbus.rr.com> <199906052249.PAA13811@madrugada.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199906052249.PAA13811@madrugada.nas.nasa.gov>; from Andrew W. Flury on Sat, Jun 05, 1999 at 03:49:29PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 05, 1999 at 03:49:29PM -0700, Andrew W. Flury wrote: > > FYI, this problem also exists if you have APM enabled in your BIOS setup but > not enabled in your kernel. Disabling it in the BIOS is one way to fix it > (it's enabled on ASUS P2B boards by default). Hmm, well I tried Danny's suggestion of adding apm to my kernel configuration and that solved the problem on my system (w/ASUS XG-DLS MB). My APM has never been enabled in the BIOS, however (that's always one of the first things I do with a new MB). Bob > > > Joe, > > > > Do you have apm configured in your kernel? If so, try: > > > > device apm0 at isa? flags 0x20 > > > > So far, this seems to correct it. > > > > When I started digging around, I found that the stat clock had been > > disabled. > > The only thing that can disable it is apm, but the test looks backwards > > to me: > > > > *** /usr/src/sys/i386/isa/clock.c: > > line 946: > > cpu_initclocks() > > { > > int diag; > > #ifdef APIC_IO > > int apic_8254_trial; > > #endif /* APIC_IO */ > > > > if (statclock_disable) { > > /* > > * The stat interrupt mask is different without the > > * statistics clock. Also, don't set the interrupt > > * flag which would normally cause the RTC to generate > > * interrupts. > > */ > > stat_imask = HWI_MASK | SWI_MASK; > > rtc_statusb = RTCSB_24HR; > > } else { > > /* Setting stathz to nonzero early helps avoid races. */ > > stathz = RTC_NOPROFRATE; > > profhz = RTC_PROFRATE; > > } > > > > The problem seems to be that the statclock gets disabled if > > statclock_disable > > ISN'T set. My stathz was set to RTC_NOPROFRATE, which disables > > collection > > of stats. > > > > > > After installing a MP kernel on my system I have noticed that the various > > > > system utilities that display cpu usage all report 0.0% for everything. > > > > The UP kernel does not have this problem and the MP kernel will work ok > > > > briefly after rebooting, until I apply a load (such as starting X or > > > > building a kernel). > > > > > > I am seeing this problem as well. > > > > > > ASUS P2B-DS, 2 x PII-400/512, disks moved from an HP Vectra XU/200 that > > > worked just fine. I was running a mildly modified 3.0R on the Vectra > > > which reported statistics correctly. Moving these to the P2B-DS broke, > > > for reasons unknown, since I have other P2B-DS's on 3.0R which report > > > statistics fine. > > > > > > I then upgraded the box to 3.1R since I thought maybe my mods were causing > > > the problem, but it is still broken. > > > > > > Oddly, it appears to work fine in single-user, although I didn't play with > > > it for more than a few minutes. > > > > > > More oddly, load average appears to report properly. > > > > > > If any bug whacker would like access to the box in question, it can be > > > arranged easily enough (its a games machine). I'd sure like to see a fix > > > for this. > > > > > > ... Joe > > > > -- Danny J. Zerkel > > dzerkel@columbus.rr.com > > "Sursum ad Absurdum" > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 17:49:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id E2D6014D21 for ; Sun, 27 Jun 1999 17:49:32 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id RAA04248; Sun, 27 Jun 1999 17:49:29 -0700 Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda04244; Sun Jun 27 17:49:27 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id KAA49471; Sun, 27 Jun 1999 10:14:04 -0700 (PDT) Message-Id: <199906271714.KAA49471@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdj49467; Sun Jun 27 17:13:51 1999 X-Mailer: exmh version 2.0.2 2/24/98 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 2.2.8-RELEASE X-Sender: cy To: Dag-Erling Smorgrav Cc: Kiril Mitev , cyouse@cybersites.com (Chuck Youse), greg@swlct.sthames.nhs.uk, freebsd-stable@FreeBSD.ORG Subject: Re: PR broken? was Re: Linux not FreeBSD? In-reply-to: Your message of "24 Jun 1999 10:11:04 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jun 1999 10:13:51 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: > Everything journalists write is true, except when they write about > something you know. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no Your comment should be incorporated into the fortune database. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 18:19:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 2098D15291 for ; Sun, 27 Jun 1999 18:19:52 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA19155; Sun, 27 Jun 1999 18:19:46 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <3776CDB1.B7453C3@gorean.org> Date: Sun, 27 Jun 1999 18:19:45 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Robin Melville Cc: freebsd-stable@freebsd.org Subject: Re: NFS hanging in 3.2-STABLE References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robin Melville wrote: > While I'm happy to always use tcp mounts I wonder whether something is > quite badly wrong with the kernel nfs code, Yes, that's about the size of it. Fortunately these problems are A) old, B) well-known, and C) being worked on in -current. When the fixes are stable enough they are backported to -stable, so before the next release you should see big improvement. > or whether I've done something wrong. Nope. In fact your fix of using tcp transport is the correct one. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 19:10:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (nat197.79.mpoweredpc.net [142.177.197.79]) by hub.freebsd.org (Postfix) with ESMTP id 1E8C0150F3; Sun, 27 Jun 1999 19:10:12 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA46836; Sun, 27 Jun 1999 23:10:12 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 27 Jun 1999 23:10:11 -0300 (ADT) From: The Hermit Hacker To: freebsd-stable@freebsd.org Cc: freebsd-chat@freebsd.org Subject: 3.2-STABLE unable to stably run NEWEST INN Code... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to heavy usage of MMAP() in the newest INN's, 3.2-STABLE is unable to handle the load of a full news server :( The last I heard, Matt Dillon knew about and was planning on working on ~6 MMAP() related race conditions...with the latest decision by "the Core" concerning his commit privileges, I'm not sure how enthusiastic Matt is going to be towards working on these, and am working if there is anyone else out there that is going to be able to handle these problems? There have been several other admin's out there that have reported the same problems with 3.2-STABLE+INN-CURRENT, as regards to hanging, so it isn't an isolated "hardware-related" problem... Matt...is this something you are still planning on addressing? Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 19:27: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from imap0.glue.umd.edu (imap0.glue.umd.edu [128.8.10.158]) by hub.freebsd.org (Postfix) with ESMTP id 87B30152F5 for ; Sun, 27 Jun 1999 19:26:53 -0700 (PDT) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (ppp-27-188.tidalwave.net [208.220.27.188]) by imap0.glue.umd.edu (8.9.3/8.9.3) with ESMTP id WAA18029; Sun, 27 Jun 1999 22:26:14 -0400 (EDT) Message-ID: <3776DC65.47670121@glue.umd.edu> Date: Sun, 27 Jun 1999 22:22:29 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.6 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Cy Schubert - ITSD Open Systems Group Cc: Dag-Erling Smorgrav , Kiril Mitev , Chuck Youse , greg@swlct.sthames.nhs.uk, freebsd-stable@FreeBSD.ORG Subject: Re: PR broken? was Re: Linux not FreeBSD? References: <199906271714.KAA49471@cwsys.cwsent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Cy Schubert - ITSD Open Systems Group wrote: > > In message , Dag-Erling Smorgrav > writes: > > Everything journalists write is true, except when they write about > > something you know. > > > > DES > > -- > > Dag-Erling Smorgrav - des@flood.ping.uio.no > > Your comment should be incorporated into the fortune database. > I second that. -Brandon -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 19:30:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from imap0.glue.umd.edu (imap0.glue.umd.edu [128.8.10.158]) by hub.freebsd.org (Postfix) with ESMTP id BAF6315468 for ; Sun, 27 Jun 1999 19:30:49 -0700 (PDT) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (ppp-27-188.tidalwave.net [208.220.27.188]) by imap0.glue.umd.edu (8.9.3/8.9.3) with ESMTP id WAA18115 for ; Sun, 27 Jun 1999 22:30:40 -0400 (EDT) Message-ID: <3776DD59.C5686D5D@glue.umd.edu> Date: Sun, 27 Jun 1999 22:26:33 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.6 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: Re: 3.2-RELEASE Feedback References: <19990626184311.A5290@ipass.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper wrote: > 8) (Nit) Boot-up probes spelling error: > "bt_isa_probe: Probe failled for card at 0x330" > > 9) rc.firewall - if firewall_type is a file, it feeds each line in it to > ipfw. > > BUT ipfw doesn't toss comments, so you can't document your firewall > commands, and this IMO isn't a good option. If rc.firewall tossed lines > beginning with "#" this would be a nice way to go without having to hack > rc.firewall. As it is, I made this add to rc.firewall: > > elif [ "${firewall_type}" = "custom" ]; then > . /etc/rc.firewall.rules > Since we're mentioning problems... I've noticed that setting any of the firewall options in /etc/rc.conf has no effect. I have to set them in /etc/defaults/rc.conf before they'll work. Anybody else have this problem? I haven't cvsup'd in a few weeks. -Brandon -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Jun 27 23:24:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netrinsics.com (unknown [210.74.174.132]) by hub.freebsd.org (Postfix) with ESMTP id 25CB215369 for ; Sun, 27 Jun 1999 23:24:32 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id OAA55841 for freebsd-stable@freebsd.org; Mon, 28 Jun 1999 14:22:02 +0800 (CST) (envelope-from robinson) Date: Mon, 28 Jun 1999 14:22:02 +0800 (CST) From: Michael Robinson Message-Id: <199906280622.OAA55841@netrinsics.com> To: freebsd-stable@freebsd.org Subject: stable vs. current question Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The handbook sez: > What is FreeBSD-current not? [...] > 3.In any way ``officially supported'' by us. We do our best to > help people genuinely in one of the 3 ``legitimate'' FreeBSD-current > categories, but we simply do not have the time to provide > tech support for it. This is not because we are mean and > nasty people who do not like helping people out (we would > not even be doing FreeBSD if we were), it is literally > because we cannot answer 400 messages a day and actually > work on FreeBSD! How does this differ from FreeBSD-stable? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 11:20:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from galatea.neptune.on.ca (mail.neptune.on.ca [205.233.176.3]) by hub.freebsd.org (Postfix) with ESMTP id 2980714F85 for ; Mon, 28 Jun 1999 11:20:39 -0700 (PDT) (envelope-from steve@neptune.on.ca) Received: from triton.neptune.on.ca (steve@triton.neptune.on.ca [205.233.176.2]) by galatea.neptune.on.ca (8.8.7/8.8.7) with SMTP id OAA04203 for ; Mon, 28 Jun 1999 14:20:47 -0400 Date: Mon, 28 Jun 1999 14:20:38 -0400 (EDT) From: Steve Mickeler To: FreeBSD Stable List Subject: comconsole Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been searching the web and testing hi and low, but have yet to see a straight answer about getting COMCONSOLE working under 3.2 Stable. Can anyone shed some light on this ? Thanks! -- Steve Todays root password is brought to you by /dev/random .-------------------------------------. | Steve Mickeler * Network Operations | | Neptune Internet Services | |-------------------------------------| | Mirabilis ICQ UIN - 5806610 | `-------------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 12: 2:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with SMTP id 65B4F14F97 for ; Mon, 28 Jun 1999 12:02:27 -0700 (PDT) (envelope-from jedgar@fxp.org) Received: (qmail 90962 invoked by uid 1003); 28 Jun 1999 19:02:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Jun 1999 19:02:53 -0000 Date: Mon, 28 Jun 1999 15:02:53 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: Steve Mickeler Cc: FreeBSD Stable List Subject: Re: comconsole In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Steve Mickeler wrote: > I have been searching the web and testing hi and low, but have yet to see > a straight answer about getting COMCONSOLE working under 3.2 Stable. > > Can anyone shed some light on this ? > COMCONSOLE has been depricated...see sio(4) flags. In addition, /sys/i386/boot/biosboot/README.serial has further tips on serial consoles. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 12:24:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 4E3D214CCA for ; Mon, 28 Jun 1999 12:24:20 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00421; Mon, 28 Jun 1999 12:20:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199906281920.MAA00421@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steve Mickeler Cc: FreeBSD Stable List Subject: Re: comconsole In-reply-to: Your message of "Mon, 28 Jun 1999 14:20:38 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Jun 1999 12:20:58 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I have been searching the web and testing hi and low, but have yet to see > a straight answer about getting COMCONSOLE working under 3.2 Stable. You read the sio(4) manpage, and add -P to /boot.config as documented in boot(8). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 13:33:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id DD42D14FC4 for ; Mon, 28 Jun 1999 13:33:28 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id NAA06637; Mon, 28 Jun 1999 13:32:32 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 28 Jun 1999 13:32:32 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: "Chris D. Faulhaber" Cc: Steve Mickeler , FreeBSD Stable List Subject: Re: comconsole In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Chris D. Faulhaber wrote: > On Mon, 28 Jun 1999, Steve Mickeler wrote: > > > I have been searching the web and testing hi and low, but have yet to see > > a straight answer about getting COMCONSOLE working under 3.2 Stable. > > > > Can anyone shed some light on this ? > > > > COMCONSOLE has been depricated...see sio(4) flags. In addition, > /sys/i386/boot/biosboot/README.serial has further tips on serial consoles. Only you should note that rebuilding the boot blocks there won't change anything for you, the new place to do that is /sys/boot. Also, what kind of com console are you interested in having? There are two different things, one is getting a login prompt on the com console that allows you to log in directly to the machine as if it were a real monitor and keyboard console. The other is directing the boot messages to the serial console. Assuming that you have the proper cabling, the first is easy to set up, just follow the instructions in the handbook. Once you get the login prompt set up, redirecting the boot messages should be easy. First, the COMCONSOLE kernel option is now deprecated, see the sio options in LINT for more details. Also, you should read the info in the /boot directory, and read the man pages for loader and boot. At this point the easiest way to use the -P option is to put 'boot -P' as the last line of your /boot/loader.rc file. Good luck, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 13:59:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179]) by hub.freebsd.org (Postfix) with ESMTP id 09E74151DD for ; Mon, 28 Jun 1999 13:59:13 -0700 (PDT) (envelope-from root@eyelab.psy.msu.edu) Received: from DEVEL-EYELAB (eyelab.psy.msu.edu [35.8.64.179]) by eyelab.psy.msu.edu (8.9.3/8.9.2) with ESMTP id QAA00792 for ; Mon, 28 Jun 1999 16:59:11 -0400 (EDT) (envelope-from root@eyelab.psy.msu.edu) Message-Id: <4.2.0.58.19990628165456.00abe6f0@localhost> X-Sender: root@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 28 Jun 1999 17:05:36 -0700 To: freebsd-stable@freebsd.org From: Gary Schrock Subject: named dies after being up for a little while in 3.2-stable? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just updated a box from somewhere in the 3.1-stable area to about last friday's (6/26/99) 3.2-stable line, and since doing this named seems to be keeling over dead after being up for a little while (suspiciously, the first time it was exactly 1 hour, it also seems to have occured exactly 15 minutes after bringing it back up). The relevant log in messages is: Jun 28 16:07:44 eyelab named[122]: /usr/src/lib/libbind/../../contrib/bind/lib/isc/memcluster.c:246: INSIST(stats[size].gets != 0) failed. Below is the contents of my named.conf file: options { directory "/etc/namedb"; forwarders { 35.8.2.41; }; dump-file "s/named_dump.db"; }; zone "." { type hint; file "named.root"; }; zone "0.0.127.IN-ADDR.ARPA" { type master; file "localhost.rev"; }; zone "msu.edu" { type slave; file "s/msu.zone.bak"; masters { 35.8.2.41; }; }; zone "8.35.in-addr.arpa" { type slave; file "s/msu.rev.bak"; masters { 35.8.2.41; }; }; Anybody have any suggestions? Thanks, Gary Schrock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 14:45:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E3D8915488 for ; Mon, 28 Jun 1999 14:45:28 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id OAA14033; Mon, 28 Jun 1999 14:45:09 -0700 (PDT) (envelope-from obrien) Message-ID: <19990628144508.A13964@nuxi.com> Date: Mon, 28 Jun 1999 14:45:08 -0700 From: "David O'Brien" To: Ray Wang , stable@FreeBSD.ORG Subject: Re: gcc-2.8.1 Reply-To: obrien@FreeBSD.ORG References: <3774A02246.AEA7RAYW@pchome.com.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3774A02246.AEA7RAYW@pchome.com.tw>; from Ray Wang on Sat, Jun 26, 1999 at 05:40:50PM +0800 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While i make gcc-2.8.1 under 3.2 Stable have some problem > the error code is > /usr/libexec/elf/ld: cannot open crt0.o: No such file or directory For some reason the Port thinks you have an a.out system. For ELF it would be looking for crt1.o. > is someone can tell me how to recover the problem You would need to post the complete build log. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 16:48:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 96A4A1520F for ; Mon, 28 Jun 1999 16:47:52 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id BAA07835; Tue, 29 Jun 1999 01:47:31 +0200 (MET DST) Date: Tue, 29 Jun 1999 01:47:29 +0200 (MET DST) From: Gerald Pfeifer To: stable@freebsd.org Cc: obrien@nuxi.com Subject: Re: NFSv3 seriously broken in 3.1 In-Reply-To: <19990428154346.A77100@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Apr 1999, David O'Brien wrote: >> With this setup, I experience serious NFS problems, unless I explicitely >> set "opts:=nfsv2" in all AMD maps. > ... >> Has there been any change to fix this on -STABLE after 3.1? > As I've said, the default is v3/UDP. In previous postings that seemed to > make everybody happy. I'll review my mail archive and verify that. Just to make sure, there has been no change between FreeBSD 3.1 and 3.2, right? We have some new FreeBSD 3.2 boxes and experience strange hangs when sending mail from Pine ("Sending 0%" forever), which are exactly the symptoms we had on FreeBSD 3.1 until I fixed "opts:=nfsv2" in all AMD maps. This is rather annoying and I feel a bit lost, for this never occurs on FreeBSD 3.1 with exactly the same AMD map. Have there been any changes concerning direct mounts via fstab? /var/mail is mounted like that. Respectively, I believe someone mentioned a way to "lock" an entire host to NFS 2, so that specifying this in individual AMD maps is not needed any more, but failed to find _where_ to configure that. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 16:55:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 817251520F for ; Mon, 28 Jun 1999 16:55:24 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id QAA14679; Mon, 28 Jun 1999 16:55:18 -0700 (PDT) (envelope-from obrien) Message-ID: <19990628165518.A14652@nuxi.com> Date: Mon, 28 Jun 1999 16:55:18 -0700 From: "David O'Brien" To: Gerald Pfeifer , stable@freebsd.org Subject: Re: NFSv3 seriously broken in 3.1 Reply-To: obrien@freebsd.org References: <19990428154346.A77100@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Gerald Pfeifer on Tue, Jun 29, 1999 at 01:47:29AM +0200 X-Operating-System: FreeBSD 3.2-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Has there been any change to fix this on -STABLE after 3.1? > > As I've said, the default is v3/UDP. In previous postings that seemed to > > make everybody happy. I'll review my mail archive and verify that. > > Just to make sure, there has been no change between FreeBSD 3.1 and 3.2, > right? 3.1 defaulted to v3/TCP. 3.2 defaults to v3/UDP (or at least should). HOWEVER /etc/amd.map specifies v2/UDP. Are you able to use ``snoop -v'' on a Sun to verify the protocols used? (or tcpdump if you don't have Solaris) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 21:10:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 4E987151B7; Mon, 28 Jun 1999 21:10:12 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA95594; Mon, 28 Jun 1999 21:09:42 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: stable@freebsd.org Cc: jb@freebsd.org, eischen@vigrid.com Subject: pthreads in -stable Date: Mon, 28 Jun 1999 21:09:41 -0700 Message-ID: <95582.930629381@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't help but notice that pthread support in -current is *much* different than that currently in -stable and the reason I ask is that a certain large, well-known application is having looping problems within the current libc_r code, to wit: #0 0x282738e0 in _thread_sys_select () from /usr/lib/libc_r.so.3 #1 0x28272f9d in _thread_kern_select (wait_reqd=1) at /a/time/src/lib/libc_r/uthread/uthread_kern.c:816 #2 0x28272876 in _thread_kern_sched (scp=0x0) at /a/time/src/lib/libc_r/uthread/uthread_kern.c:376 #3 0x28272a2f in _thread_kern_sched_state (state=PS_SLEEP_WAIT, fname=0x282a4343 "/a/time/src/lib/libc_r/uthread/uthread_nanosleep.c", lineno=72) at /a/time/src/lib/libc_r/uthread/uthread_kern.c:471 #4 0x282841d7 in nanosleep (time_to_sleep=0xbfbfd2bc, time_remaining=0xbfbfd2b4) at /a/time/src/lib/libc_r/uthread/uthread_nanosleep.c:72 #5 0x2818fd57 in sleep () from /usr/lib/libc.so.3 When I went to trace this out, I then found that the code to deal with this case in -current was significantly different than the code in -stable and it set me to wondering if a MFC was simply in order. I'm currently trying to build this product under -current (a very laborious process) to see if the problem has automagically gone away with the new libc_r, but even if this fixes it we'll still be screwed until we MFC since this product has to run under production versions of the OS and that means 3.3 at the very minimum. The failure mode is that the thread_sys_select() eventually times out and falls through some code in thread_kern_sched after which it loops back and does it all over again. The code never proceeds past this point. If somebody has encountered this specific problem in -stable and has a fix for it, I'd also be more than happy to have it since it would give me the freedom to hand this nameless ISV a small patch to 3.2 to get them going again, otherwise that's going to be a more traumatic cvsup and rebuild away (assuming again that this problem is even fixed in -current). Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 21:20:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 0D48E1508D; Mon, 28 Jun 1999 21:20:09 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id OAA11718; Tue, 29 Jun 1999 14:22:37 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906290422.OAA11718@cimlogic.com.au> Subject: Re: pthreads in -stable In-Reply-To: <95582.930629381@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jun 28, 1999 9: 9:41 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Tue, 29 Jun 1999 14:22:37 +1000 (EST) Cc: stable@freebsd.org, jb@freebsd.org, eischen@vigrid.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > I can't help but notice that pthread support in -current is *much* > different than that currently in -stable and the reason I ask is that > a certain large, well-known application is having looping problems > within the current libc_r code, to wit: There have been a few big commits to -current quite recently. The MFC is pending people getting a chance to try the code. > When I went to trace this out, I then found that the code to deal with > this case in -current was significantly different than the code in > -stable and it set me to wondering if a MFC was simply in order. I'm > currently trying to build this product under -current (a very > laborious process) to see if the problem has automagically gone away > with the new libc_r, but even if this fixes it we'll still be screwed > until we MFC since this product has to run under production versions > of the OS and that means 3.3 at the very minimum. Just take the libc_r from your current system. The internals of the implementation are (supposed to be) opaque. Should be easy to try out if the application is dynamically linked. At worst it'll be a relink if the application is statically linked. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 21:40: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1220314D67; Mon, 28 Jun 1999 21:40:07 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA09337; Mon, 28 Jun 1999 21:39:30 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: John Birrell Cc: stable@freebsd.org, jb@freebsd.org, eischen@vigrid.com Subject: Re: pthreads in -stable In-reply-to: Your message of "Tue, 29 Jun 1999 14:22:37 +1000." <199906290422.OAA11718@cimlogic.com.au> Date: Mon, 28 Jun 1999 21:39:28 -0700 Message-ID: <9333.930631168@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just take the libc_r from your current system. The internals of the > implementation are (supposed to be) opaque. Should be easy to try > out if the application is dynamically linked. At worst it'll be a > relink if the application is statically linked. Hmmm. The internals may be opaque but you bumped the revision number for *some* reason that involved changing the interface or there'd have been no reason to bump the number, si senor? :-) In any case, the test app they sent me was indeed linked dynamic and so I did attempt to simply copy a new -current libc_r.so.4 to libc_r.so.3 for the app to use, and doing so caused it to die with a signal 11 rather than an infinite loop so I deemed it a probable mismatch and moved on. Whether that judgement was too hasty will, I hope, be proven either way once I get this product building under -current entirely. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 21:48:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 6A502151A6; Mon, 28 Jun 1999 21:48:00 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id OAA11854; Tue, 29 Jun 1999 14:50:31 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906290450.OAA11854@cimlogic.com.au> Subject: Re: pthreads in -stable In-Reply-To: <9333.930631168@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jun 28, 1999 9:39:28 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Tue, 29 Jun 1999 14:50:30 +1000 (EST) Cc: jb@cimlogic.com.au, stable@freebsd.org, jb@freebsd.org, eischen@vigrid.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > Just take the libc_r from your current system. The internals of the > > implementation are (supposed to be) opaque. Should be easy to try > > out if the application is dynamically linked. At worst it'll be a > > relink if the application is statically linked. > > Hmmm. The internals may be opaque but you bumped the revision number > for *some* reason that involved changing the interface or there'd have > been no reason to bump the number, si senor? :-) I bumped the version number because the implementation changed from being based on select() to poll(). > In any case, the test app they sent me was indeed linked dynamic and > so I did attempt to simply copy a new -current libc_r.so.4 to > libc_r.so.3 for the app to use, and doing so caused it to die with a > signal 11 rather than an infinite loop so I deemed it a probable > mismatch and moved on. I guess it was worth a try. I wonder if the application is doing something illegal. If select() is looping in the -stable version, is it possible that the application has somehow closed the pipe that libc_r thread uses internally? If you can rebuild libc_r in -stable, check for the internal pipe being reported in the exception fd_set. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 22:15:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 1612914DED; Mon, 28 Jun 1999 22:15:12 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA55857; Mon, 28 Jun 1999 22:14:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: John Birrell Cc: stable@freebsd.org, jb@freebsd.org, eischen@vigrid.com Subject: Re: pthreads in -stable In-reply-to: Your message of "Tue, 29 Jun 1999 14:50:30 +1000." <199906290450.OAA11854@cimlogic.com.au> Date: Mon, 28 Jun 1999 22:14:34 -0700 Message-ID: <55853.930633274@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I bumped the version number because the implementation changed from > being based on select() to poll(). Hmmm. Could you perhaps explain to me the potential effects this had on applications linking with it? I don't mean to be so obtuse here, I'm simply trying to determine whether this was a necessary version bump or if the interface has actually not changed. If the change is totally transparent to applications then it's certainly been my understanding that a revision bump should not take place since such changes merely represent internal shuffling and the library version number is for communicating interface changes to external client apps. > I guess it was worth a try. I wonder if the application is doing something > illegal. If select() is looping in the -stable version, is it possible > that the application has somehow closed the pipe that libc_r thread > uses internally? If you can rebuild libc_r in -stable, check for the > internal pipe being reported in the exception fd_set. That's a good point, thanks - I'll check for that. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Jun 28 22:20:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (Postfix) with ESMTP id 2D36B14DED; Mon, 28 Jun 1999 22:20:08 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id PAA11964; Tue, 29 Jun 1999 15:22:38 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199906290522.PAA11964@cimlogic.com.au> Subject: Re: pthreads in -stable In-Reply-To: <55853.930633274@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jun 28, 1999 10:14:34 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Tue, 29 Jun 1999 15:22:38 +1000 (EST) Cc: jb@cimlogic.com.au, stable@freebsd.org, jb@freebsd.org, eischen@vigrid.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: > > I bumped the version number because the implementation changed from > > being based on select() to poll(). > > Hmmm. Could you perhaps explain to me the potential effects this had > on applications linking with it? I don't mean to be so obtuse here, > I'm simply trying to determine whether this was a necessary version > bump or if the interface has actually not changed. If the change is > totally transparent to applications then it's certainly been my > understanding that a revision bump should not take place since such > changes merely represent internal shuffling and the library version > number is for communicating interface changes to external client apps. The change also adds poll(), so running GNU configure scripts will probably result in a different configuration of an application. This is why I bumped the rev. If you just look at things from the perspective of the library functionality, then poll is an additional function, so a rev bump is not warranted. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 0:34:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id 6A0D214D5B for ; Tue, 29 Jun 1999 00:33:57 -0700 (PDT) (envelope-from conradj@is.co.za) Received: from admin.is.co.za (admin.is.co.za [196.23.0.9]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id JAA19478; Tue, 29 Jun 1999 09:33:18 +0200 Received: (from conradj@localhost) by admin.is.co.za (8.8.6/8.7.3/ISsubsidiary#1) id JAA20594; Tue, 29 Jun 1999 09:33:30 +0200 (GMT) Message-ID: <19990629093325.55802@is.co.za> Date: Tue, 29 Jun 1999 09:33:25 +0200 From: Conrad Juleff To: Gary Schrock Cc: freebsd-stable@FreeBSD.ORG Subject: Re: named dies after being up for a little while in 3.2-stable? References: <4.2.0.58.19990628165456.00abe6f0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <4.2.0.58.19990628165456.00abe6f0@localhost>; from Gary Schrock on Mon, Jun 28, 1999 at 05:05:36PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You don't say what version of bind you are running but it looks like 8.2. If so you need to install patch1 to fix this problem. Get it from ftp://ftp.isc.org/isc/bind/src/8.2/ On Mon, Jun 28, 1999 at 05:05:36PM -0700, Gary Schrock wrote: > I just updated a box from somewhere in the 3.1-stable area to about last > friday's (6/26/99) 3.2-stable line, and since doing this named seems to be > keeling over dead after being up for a little while (suspiciously, the > first time it was exactly 1 hour, it also seems to have occured exactly 15 > minutes after bringing it back up). The relevant log in messages is: > > Jun 28 16:07:44 eyelab named[122]: > /usr/src/lib/libbind/../../contrib/bind/lib/isc/memcluster.c:246: > INSIST(stats[size].gets != 0) failed. > > Below is the contents of my named.conf file: > options { > directory "/etc/namedb"; > forwarders { > 35.8.2.41; > }; > dump-file "s/named_dump.db"; > }; > zone "." { > type hint; > file "named.root"; > }; > > zone "0.0.127.IN-ADDR.ARPA" { > type master; > file "localhost.rev"; > }; > > zone "msu.edu" { > type slave; > file "s/msu.zone.bak"; > masters { > 35.8.2.41; > }; > }; > > zone "8.35.in-addr.arpa" { > type slave; > file "s/msu.rev.bak"; > masters { > 35.8.2.41; > }; > }; > > > Anybody have any suggestions? > > Thanks, > Gary Schrock > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 0:47:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ceia.nordier.com (m2-39-dbn.dial-up.net [196.34.155.103]) by hub.freebsd.org (Postfix) with ESMTP id 87D191529C for ; Tue, 29 Jun 1999 00:46:18 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id JAA26343; Tue, 29 Jun 1999 09:44:43 +0200 (SAST) From: Robert Nordier Message-Id: <199906290744.JAA26343@ceia.nordier.com> Subject: Re: comconsole In-Reply-To: from Doug at "Jun 28, 1999 01:32:32 pm" To: Doug@gorean.org (Doug) Date: Tue, 29 Jun 1999 09:44:42 +0200 (SAST) Cc: jedgar@fxp.org (Chris D. Faulhaber), steve@neptune.on.ca (Steve Mickeler), freebsd-stable@FreeBSD.ORG (FreeBSD Stable List) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Once you get the login prompt set up, redirecting the boot > messages should be easy. First, the COMCONSOLE kernel option is now > deprecated, see the sio options in LINT for more details. Also, you should > read the info in the /boot directory, and read the man pages for loader > and boot. At this point the easiest way to use the -P option is to put > 'boot -P' as the last line of your /boot/loader.rc file. A -P option to boot is ignored. Put the -P in /boot.config. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 0:47:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id 034BF14E94 for ; Tue, 29 Jun 1999 00:47:35 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA04245; Tue, 29 Jun 1999 17:17:34 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA11015; Tue, 29 Jun 1999 17:17:33 +0930 Date: Tue, 29 Jun 1999 17:17:33 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Conrad Juleff Cc: Gary Schrock , freebsd-stable@freebsd.org Subject: Re: named dies after being up for a little while in 3.2-stable? In-Reply-To: <19990629093325.55802@is.co.za> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Conrad Juleff wrote: > You don't say what version of bind you are running but it looks like 8.2. If > so you need to install patch1 to fix this problem. Get it from > ftp://ftp.isc.org/isc/bind/src/8.2/ Or upgrade to 8.2.1 Kris ----- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 1: 2: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (Postfix) with ESMTP id DFED614E94 for ; Tue, 29 Jun 1999 01:01:58 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.9.3/8.9.3) id BAA26553; Tue, 29 Jun 1999 01:01:45 -0700 (PDT) Date: Tue, 29 Jun 1999 01:01:45 -0700 From: Shawn Ramsey To: Kris Kennaway Cc: Conrad Juleff , Gary Schrock , freebsd-stable@FreeBSD.ORG Subject: Re: named dies after being up for a little while in 3.2-stable? Message-ID: <19990629010145.C24502@cpl.net> References: <19990629093325.55802@is.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Kris Kennaway on Tue, Jun 29, 1999 at 05:17:33PM +0930 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > You don't say what version of bind you are running but it looks like 8.2. If > > so you need to install patch1 to fix this problem. Get it from > > ftp://ftp.isc.org/isc/bind/src/8.2/ > > Or upgrade to 8.2.1 Does anyone have any clue as to why 4.9.7-T1B would be dieing occasionally? This problem just recently started, after being rock solid. When it dies it leaves this message in dmesg : pid 88 (named), uid 0: exited on signal 6 pid 6497 (named), uid 0: exited on signal 11 (core dumped) (thats the last two times it has died since the server was rebooted) Could it be running out of resources? There are aprox. 220 primary or secondary entried in named.boot... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 1:10:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from extra.gc.lviv.ua (gc.cscd.lviv.ua [195.5.56.19]) by hub.freebsd.org (Postfix) with ESMTP id C753914E94 for ; Tue, 29 Jun 1999 01:09:03 -0700 (PDT) (envelope-from vadim@gc.lviv.ua) Received: from gate.gc.lviv.ua (gate.gc.lviv.ua [192.168.168.18]) by extra.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id LAA10028 for ; Tue, 29 Jun 1999 11:08:55 +0300 (EEST) Received: from gc.lviv.ua (intra.lviv.gc.com.ua [192.168.1.93]) by gate.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id LAA89202 for ; Tue, 29 Jun 1999 11:08:43 +0300 (EEST) Message-ID: <37787E13.C8B5D2FB@gc.lviv.ua> Date: Tue, 29 Jun 1999 11:04:35 +0300 From: Vadim Chekan Organization: Galitsky Kontrakty X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: Change IP Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everybody! I changed my IP ifconfig xl1 down ifconfig xl1 inet xxx netmask yyy ifconfig xl1 inet xxx2 netmask yyy2 alias And now have in logs: Jun 29 10:49:31 extra /kernel: arplookup 195.5.17.241 failed: host is not on loc al network Jun 29 10:49:31 extra /kernel: arpresolve: can't allocate llinfo for 195.5.17.24 1rt Jun 29 10:49:31 extra /kernel: arplookup 195.5.17.241 failed: host is not on loc al network Jun 29 10:49:31 extra /kernel: arpresolve: can't allocate llinfo for 195.5.17.24 1rt Jun 29 10:49:33 extra /kernel: arplookup 195.5.17.241 failed: host is not on loc al network Jun 29 10:49:33 extra /kernel: arpresolve: can't allocate llinfo for 195.5.17.24 1rt Jun 29 10:49:33 extra /kernel: arplookup 195.5.17.241 failed: host is not on loc al network Jun 29 10:49:33 extra /kernel: arpresolve: can't allocate llinfo for 195.5.17.24 1rt Jun 29 10:49:33 extra /kernel: arplookup 195.5.17.241 failed: host is not on loc al network Jun 29 10:49:33 extra /kernel: arpresolve: can't allocate llinfo for 195.5.17.24 1rt What is llinfo? Vadim Chekan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 2:44:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id EFF0914D84; Tue, 29 Jun 1999 02:44:26 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id FAA05148; Tue, 29 Jun 1999 05:43:26 -0400 (EDT) Date: Tue, 29 Jun 1999 05:43:26 -0400 (EDT) From: Daniel Eischen Message-Id: <199906290943.FAA05148@pcnet1.pcnet.com> To: jb@cimlogic.com.au, jkh@zippy.cdrom.com Subject: Re: pthreads in -stable Cc: eischen@vigrid.com, jb@freebsd.org, stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In any case, the test app they sent me was indeed linked dynamic and > so I did attempt to simply copy a new -current libc_r.so.4 to > libc_r.so.3 for the app to use, and doing so caused it to die with a > signal 11 rather than an infinite loop so I deemed it a probable > mismatch and moved on. Whether that judgement was too hasty will, I > hope, be proven either way once I get this product building under > -current entirely. Can you build libc_r from -current with _PTHREADS_INVARIANTS defined and try again? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 2:53: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vax.chrillesen.dk (vax.chrillesen.dk [193.88.12.35]) by hub.freebsd.org (Postfix) with SMTP id 083D714E92 for ; Tue, 29 Jun 1999 02:52:54 -0700 (PDT) (envelope-from jan@chrillesen.dk) Received: (qmail 23328 invoked by uid 1000); 29 Jun 1999 09:52:52 -0000 From: jan@chrillesen.dk Date: Tue, 29 Jun 1999 11:52:52 +0200 (CEST) To: freebsd-stable@freebsd.org Subject: Adaptec 2944 and 3.2-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. 3.2-stable does not seem to recognize my Adaptec 2944uw. It seems the kernel finds the device (vendor 9004 = Adaptec) but does not recognize it as a SCSI adaptor. I've tried building a UP kernel and tried leaving out the various AHC-options, but without luck. Linux works fine on the same setup, so I don't believe it's a hardware problem. Hardware: HP Netserver LPr, 2 CPU's, build-in NCR 53c875 SCSI. I'm still rather new to FreeBSD so I might have overlooked something obviuosly. TIA /Jan avail memory = 62087168 (60632K bytes) Programming 24 pins in IOAPIC #0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Found BIOS32 Service Directory header at 0xc00f7340 Entry = 0xfd83c (0xc00fd83c) Rev = 0 Len = 1 PCI BIOS entry at 0x3c2 SMIBIOS header at 0xc00f72b0 Version 2.1 Table at 0xef4b0, 44 entries, 1654 bytes, largest entry 319 bytes DMI header at 0xc00f72c0 Version 2.1 Table at 0xef4b0, 44 entries, 1654 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7310 Preloaded elf kernel "kernel" at 0xc0254000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc025409c. SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71928086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7192, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base 00000000, size 28 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x02 on pci0.4.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 00001020, size 4 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=19 map[0]: type 4, range 32, base 00001000, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip2: rev 0x02 on pci0.4.3 found-> vendor=0x1011, dev=0x0024, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip3: rev 0x02 on pci0.7.0 Freeing (NOT implemented) redirected PCI irq 15. found-> vendor=0x9004, dev=0x8478, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[0]: type 4, range 32, base 00001400, size 8 map[1]: type 1, range 32, base fa000000, size 12 found-> vendor=0x1013, dev=0x00b8, revid=0x45 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base fc000000, size 25 map[1]: type 1, range 32, base fa001000, size 12 vga0: rev 0x45 on pci0.13.0 Probing for devices on PCI bus 1: Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=19 map[0]: type 3, range 32, base fa500000, size 12 map[1]: type 4, range 32, base 00009400, size 5 map[2]: type 1, range 32, base fa100000, size 20 fxp0: rev 0x05 int a irq 19 on pci1.3.0 fxp0: Ethernet address 00:90:27:27:61:15 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x1000, dev=0x000c, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[0]: type 4, range 32, base 00009000, size 8 map[1]: type 1, range 32, base fa201000, size 8 map[2]: type 1, range 32, base fa200000, size 12 ncr0: rev 0x01 int a irq 18 on pci1.4.0 ncr0: minsync=10, maxsync=137, maxoffs=31, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 not found at 0x2f8 sio2: disabled, not probed. sio3: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 06 90 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface imasks: bio c8000040, tty c3000012, net c6080000 SMP: enabled INTs: 1, 4, 6, 18, 19, apic_imen: 0x00f3ffad BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 Waiting 5 seconds for SCSI devices to settle ncr0: restart (scsi reset). SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number LN801087000019221JBD pass0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number LN801087000019221JBD da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4067MB (8330543 512 byte sectors: 255H 63S/T 518C) Considering FFS root f/s. da0s1: type 0xa5, start 63, end = 8321669, size 8321607 : OK Kernel config: machine "i386" cpu "I686_CPU" ident NEWSFEED maxusers 512 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options CHILD_MAX=1024 options OPEN_MAX=1024 options "MAXDSIZ=(256*1024*1024)" options "DFLDSIZ=(256*1024*1024)" options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SOFTUPDATES config kernel root on da0s1a options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 controller ahc0 # controller ahc1 options AHC_ALLOW_MEMIO options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE controller ncr0 controller scbus0 at ncr0 controller scbus1 at ahc0 device da0 # device sa0 device pass0 controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device vga0 at isa? port ? conflicts # pseudo-device splash device sc0 at isa? tty device npx0 at isa? port IO_NPX irq 13 device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) pseudo-device loop pseudo-device ether pseudo-device pty 64 options KTRACE #kernel tracing # options SYSVSHM # options SYSVMSG # options SYSVSEM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 2:57:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from extra.gc.lviv.ua (gc.cscd.lviv.ua [195.5.56.19]) by hub.freebsd.org (Postfix) with ESMTP id C5391152B0 for ; Tue, 29 Jun 1999 02:57:10 -0700 (PDT) (envelope-from vadim@gc.lviv.ua) Received: from gate.gc.lviv.ua (gate.gc.lviv.ua [192.168.168.18]) by extra.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id MAA10475; Tue, 29 Jun 1999 12:55:33 +0300 (EEST) Received: from gc.lviv.ua (intra.lviv.gc.com.ua [192.168.1.93]) by gate.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id MAA95454; Tue, 29 Jun 1999 12:55:23 +0300 (EEST) Message-ID: <37789710.1F6CAE0E@gc.lviv.ua> Date: Tue, 29 Jun 1999 12:51:12 +0300 From: Vadim Chekan Organization: Galitsky Kontrakty X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Cc: "Andy V. Oleynik" Subject: Re: Change IP References: <37787E13.C8B5D2FB@gc.lviv.ua> <377894B8.87DA046E@prime.net.ua> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Andy V. Oleynik" wrote: > > And what ifconfig -a sais? I preffer to delete > interface then down it then configure from scratch. I figured out it. 195.5.17.241 was my default route and it wasn't avialable in local network. This message I understand. But I wander about llinfo: is this expected message or it's bug? > Vadim Chekan wrote: > > > Hello everybody! > > > > I changed my IP > > > > ifconfig xl1 down > > ifconfig xl1 inet xxx netmask yyy > > ifconfig xl1 inet xxx2 netmask yyy2 alias > > > > And now have in logs: > > > > Jun 29 10:49:31 extra /kernel: arplookup 195.5.17.241 failed: host is > > not on loc > > al network > > Jun 29 10:49:31 extra /kernel: arpresolve: can't allocate llinfo for > > 195.5.17.24 > > 1rt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 2:59: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rigel.vigrid.com (pm3-pt38.pcnet.net [206.105.29.112]) by hub.freebsd.org (Postfix) with ESMTP id D247514EFA; Tue, 29 Jun 1999 02:57:45 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from vigrid.com (localhost [127.0.0.1]) by rigel.vigrid.com (8.9.3/8.9.3) with ESMTP id BAA01363; Tue, 29 Jun 1999 01:50:44 -0400 (EDT) (envelope-from eischen@vigrid.com) Message-ID: <37785EB4.EDB29492@vigrid.com> Date: Tue, 29 Jun 1999 01:50:44 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: John Birrell , stable@FreeBSD.ORG, jb@FreeBSD.ORG Subject: Re: pthreads in -stable References: <55853.930633274@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > I guess it was worth a try. I wonder if the application is doing something > > illegal. If select() is looping in the -stable version, is it possible > > that the application has somehow closed the pipe that libc_r thread > > uses internally? If you can rebuild libc_r in -stable, check for the > > internal pipe being reported in the exception fd_set. > > That's a good point, thanks - I'll check for that. BTW, this was fixed in -current, and you can probably merge the change from uthread_close.c into -stable. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 3:23: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rigel.vigrid.com (pm3-pt25.pcnet.net [206.105.29.99]) by hub.freebsd.org (Postfix) with ESMTP id EBB6514C39; Tue, 29 Jun 1999 03:22:59 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from vigrid.com (localhost [127.0.0.1]) by rigel.vigrid.com (8.9.3/8.9.3) with ESMTP id CAA01496; Tue, 29 Jun 1999 02:15:46 -0400 (EDT) (envelope-from eischen@vigrid.com) Message-ID: <37786492.EC9D52F6@vigrid.com> Date: Tue, 29 Jun 1999 02:15:46 -0400 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: John Birrell , stable@FreeBSD.ORG, jb@FreeBSD.ORG Subject: Re: pthreads in -stable References: <9333.930631168@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > In any case, the test app they sent me was indeed linked dynamic and > so I did attempt to simply copy a new -current libc_r.so.4 to > libc_r.so.3 for the app to use, and doing so caused it to die with a > signal 11 rather than an infinite loop so I deemed it a probable > mismatch and moved on. Whether that judgement was too hasty will, I > hope, be proven either way once I get this product building under > -current entirely. If it's a pain to rebuild the product under -current, it would be easier to just copy libc_r/uthead/* from -current and rebuild libc_r under -stable. Others have done this to fix Mysql problems under -stable. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 6: 0:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.det.ameritech.net (mpdr0.detroit.mi.ameritech.net [206.141.239.206]) by hub.freebsd.org (Postfix) with ESMTP id 597EB14D28 for ; Tue, 29 Jun 1999 06:00:14 -0700 (PDT) (envelope-from gschrock@ameritech.net) Received: from piper.mydomain.com ([206.141.209.112]) by mailhost.det.ameritech.net (InterMail v03.02.07 118 124) with ESMTP id <19990629130009.CWOO21662@piper.mydomain.com>; Tue, 29 Jun 1999 09:00:09 -0400 Message-Id: <4.2.0.58.19990629084815.00a301c0@eyelab.msu.edu> X-Sender: gschrock@mailhost.det.ameritech.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 29 Jun 1999 08:53:29 -0400 To: Kris Kennaway , Conrad Juleff From: Gary Schrock Subject: Re: named dies after being up for a little while in 3.2-stable? Cc: freebsd-stable@freebsd.org In-Reply-To: References: <19990629093325.55802@is.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:17 PM 6/29/99 +0930, Kris Kennaway wrote: >On Tue, 29 Jun 1999, Conrad Juleff wrote: > > > You don't say what version of bind you are running but it looks like > 8.2. If > > so you need to install patch1 to fix this problem. Get it from > > ftp://ftp.isc.org/isc/bind/src/8.2/ > >Or upgrade to 8.2.1 Duh, guess that's one thing I should have thought of to put in. Here's the syslog output on the version: Jun 28 16:35:18 eyelab named[121]: starting. named 8.1.2 Thu Apr 29 18:37:50 EDT 1999 gary@eyelab.msu.edu:/usr/obj/usr/src/usr.sbin/named This is the named that's built and installed when doing a make world, I haven't tried installing a more recent version (silly me figured the one in the base system should actually work). The version number is the same as the one that was running on the machine before I made world with 3.2-stable: Apr 30 14:29:47 eyelab named[121]: starting. named 8.1.2 Thu Apr 29 18:37:50 EDT 1999 gary@eyelab.msu.edu:/usr/obj/usr/src/usr.sbin/named (That would be from the last time I made world, no problems during the 2 months it was running after that). Guess I'll have to dig through the cvs archives and see if anything was changed during those two months. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 6:19:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27]) by hub.freebsd.org (Postfix) with ESMTP id 1BD6B14E1F for ; Tue, 29 Jun 1999 06:19:33 -0700 (PDT) (envelope-from frodef@dslab7.cs.uit.no) Received: (from frodef@localhost) by dslab7.cs.uit.no (8.9.3/8.9.1) id PAA20740; Tue, 29 Jun 1999 15:17:24 +0200 (CEST) (envelope-from frodef) To: freebsd-stable@freebsd.org Subject: MMX From: Frode Vatvedt Fjeld Date: 29 Jun 1999 15:17:23 +0200 Message-ID: <2hwvwnqh7g.fsf@dslab7.cs.uit.no> Lines: 7 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the preferred way for my application to determine if the CPU is MMX-capable? Thanks, -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 6:37:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.raditex.se (www.raditex.se [192.5.36.20]) by hub.freebsd.org (Postfix) with ESMTP id 9108715081 for ; Tue, 29 Jun 1999 06:37:44 -0700 (PDT) (envelope-from kaj@raditex.se) Received: from localhost (gandalf.raditex.se [192.5.36.18]) by ns.raditex.se (8.8.8/8.8.8) with ESMTP id PAA03846; Tue, 29 Jun 1999 15:37:36 +0200 (CEST) (envelope-from kaj@raditex.se) To: frodef@acm.org Cc: freebsd-stable@FreeBSD.ORG Cc: Rasmus Kaj Subject: Re: MMX From: Rasmus Kaj In-Reply-To: Your message of "29 Jun 1999 15:17:23 +0200" <2hwvwnqh7g.fsf@dslab7.cs.uit.no> References: <2hwvwnqh7g.fsf@dslab7.cs.uit.no> X-Mailer: Mew version 1.93 on XEmacs 20.4 (Emerald) X-URL: http://www.e.kth.se/~kaj/ X-Phone: +46 (0)8 - 694 92 80 X-Attribution: Kaj X-Face: M9cR~WYav<"fu%MaslX0`43PAYY?uIsM8[#E(0\Xuy9rj>4gE\h3jm.7DD?]R8*^7T\o&vT U@[53Dwkuup4[0@gw#~kyu>`unH?kVj9CJa02(h>Ki\+i=%rn%sDf^KC.!?IHkKjMAbkd\jgmphp^' d|Q;OeXEAhq?ybGqOs1CHb6TJT42'C`Krnk61//AOfXtNjj/t'`5>Vw0QX!dKfOL$.f+S"LIuwR<;I Z0Qnnx(F^F]o@*V%TUtEV'1Z[TkOl^FFV9Z~A[b19%}uP*,huCU Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990629153736F.kaj@raditex.se> Date: Tue, 29 Jun 1999 15:37:36 +0200 X-Dispatcher: imput version 980905(IM100) Lines: 17 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "FVF" == Frode Vatvedt Fjeld writes: FVF> What is the preferred way for my application to determine if the FVF> CPU is MMX-capable? I don't know about 'preferred', but look at `dmesg`, after CPU there a line features=0xXXXXXX this line should include MMX if you have it (at least it does for me). If you mean from a program, I pass the question for someone with more clues than me ... -- Rasmus Kaj ---------------- rasmus@kaj.a.se - http://www.e.kth.se/~kaj/ \ Talk sense to a fool and he calls you foolish. -Euripides \--------------------------------------------- http://www.Raditex.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 9: 3:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id D99A1150D3 for ; Tue, 29 Jun 1999 09:03:51 -0700 (PDT) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (ppp080.dialup.st.keio.ac.jp [131.113.27.80]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id BAA03664 for ; Wed, 30 Jun 1999 01:03:48 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.9.3/3.7W) id BAA10973; Wed, 30 Jun 1999 01:03:45 +0900 (JST) Date: Wed, 30 Jun 1999 01:03:45 +0900 (JST) Message-Id: <199906291603.BAA10973@lavender.yy.cs.keio.ac.jp> To: freebsd-stable@FreeBSD.ORG Subject: Re: comconsole In-Reply-To: Your message of "Tue, 29 Jun 1999 16:44:42 JST". <199906290744.JAA26343@ceia.nordier.com> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rnordier@nordier.com Wrote: >> > Once you get the login prompt set up, redirecting the boot >> > messages should be easy. First, the COMCONSOLE kernel option is now >> > deprecated, see the sio options in LINT for more details. Also, you should >> > read the info in the /boot directory, and read the man pages for loader >> > and boot. At this point the easiest way to use the -P option is to put >> > 'boot -P' as the last line of your /boot/loader.rc file. >> >> A -P option to boot is ignored. Put the -P in /boot.config. When I setup server box(without VGA console, 3.1-RELEASE), I added ``set console=comconsole'' to /boot/loader.rc. Also enable serial console getty in /etc/ttys Which method is better for serial(com) console? MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 9:38: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ceia.nordier.com (m1-1-dbn.dial-up.net [196.34.155.1]) by hub.freebsd.org (Postfix) with ESMTP id AC7FC14C1D for ; Tue, 29 Jun 1999 09:37:28 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id SAA28420; Tue, 29 Jun 1999 18:36:00 +0200 (SAST) From: Robert Nordier Message-Id: <199906291636.SAA28420@ceia.nordier.com> Subject: Re: comconsole In-Reply-To: <199906291603.BAA10973@lavender.yy.cs.keio.ac.jp> from MIHIRA Yoshiro at "Jun 30, 1999 01:03:45 am" To: sanpei@sanpei.org (MIHIRA Yoshiro) Date: Tue, 29 Jun 1999 18:35:58 +0200 (SAST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> > Once you get the login prompt set up, redirecting the boot > >> > messages should be easy. First, the COMCONSOLE kernel option is now > >> > deprecated, see the sio options in LINT for more details. Also, you should > >> > read the info in the /boot directory, and read the man pages for loader > >> > and boot. At this point the easiest way to use the -P option is to put > >> > 'boot -P' as the last line of your /boot/loader.rc file. > >> > >> A -P option to boot is ignored. Put the -P in /boot.config. > > When I setup server box(without VGA console, 3.1-RELEASE), > I added ``set console=comconsole'' to /boot/loader.rc. > Also enable serial console getty in /etc/ttys > > Which method is better for serial(com) console? If you are using a serial console, it is generally best to enable it as soon as possible. There is a lot of stuff that happens before loader(8) gets control. The flow is roughly as follows: boot1 btx boot2 btxldr btx loader Also, bear in mind that boot2 cannot guarantee to run loader at all: if loader is inaccessible for some reason (eg. missing or corrupt), an attempt will be made to boot the kernel directly. To avoid missing potentially informative diagnostics, etc., the best place to start the serial console is therefore in boot2, using one of the options -D, -P, or -h, according to needs and preference. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 10: 3:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (Postfix) with SMTP id AC03814BEF for ; Tue, 29 Jun 1999 10:03:10 -0700 (PDT) (envelope-from barrett@phoenix.aye.net) Received: (qmail 20411 invoked by uid 1000); 29 Jun 1999 17:01:07 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Jun 1999 17:01:07 -0000 Date: Tue, 29 Jun 1999 13:01:07 -0400 (EDT) From: Barrett Richardson To: Gary Schrock Cc: freebsd-stable@freebsd.org Subject: Re: named dies after being up for a little while in 3.2-stable? In-Reply-To: <4.2.0.58.19990628165456.00abe6f0@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Gary Schrock wrote: > > Jun 28 16:07:44 eyelab named[122]: > /usr/src/lib/libbind/../../contrib/bind/lib/isc/memcluster.c:246: > INSIST(stats[size].gets != 0) failed. > There is some chatter about this on comp.protocols.dns.bind. I've run into it on two other platforms. Upgrading to 8.2.1 fixed it for me. -- Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 12:58:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 8D8B514D3E for ; Tue, 29 Jun 1999 12:58:14 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA20543; Tue, 29 Jun 1999 12:57:32 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 29 Jun 1999 12:57:32 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Robert Nordier Cc: MIHIRA Yoshiro , freebsd-stable@FreeBSD.ORG Subject: Re: comconsole In-Reply-To: <199906291636.SAA28420@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Jun 1999, Robert Nordier wrote: > > >> > Once you get the login prompt set up, redirecting the boot > > >> > messages should be easy. First, the COMCONSOLE kernel option is now > > >> > deprecated, see the sio options in LINT for more details. Also, you should > > >> > read the info in the /boot directory, and read the man pages for loader > > >> > and boot. At this point the easiest way to use the -P option is to put > > >> > 'boot -P' as the last line of your /boot/loader.rc file. > > >> > > >> A -P option to boot is ignored. Put the -P in /boot.config. Hrrm... it works fine in /boot/loader.rc on -current, maybe it doesn't work in -stable. My apologies if so. > > When I setup server box(without VGA console, 3.1-RELEASE), > > I added ``set console=comconsole'' to /boot/loader.rc. > > Also enable serial console getty in /etc/ttys > > > > Which method is better for serial(com) console? > > If you are using a serial console, it is generally best to enable it > as soon as possible. Agreed, however there are two issues here. First, the man pages all say that /boot.config is deprecated. Also, what I'd *really* like to do is get a 'boot -P' in as early as possible, then still have the autoboot option in loader. As far as I can see, that's just not possible, although I'd love to be proven wrong. > There is a lot of stuff that happens before > loader(8) gets control. The flow is roughly as follows: > > boot1 > btx > boot2 > btxldr > btx > loader Wow.... where were you last week when I asked for a list like this. :-/ Could you add one more detail to this list, namely what config files get executed when in this schedule? It would be really helpful to me, and I'm sure others. I've read the man pages till I'm going loopy on them and it's sinking in very slowly, but not fully there yet. > To avoid missing potentially informative diagnostics, etc., the best > place to start the serial console is therefore in boot2, using one > of the options -D, -P, or -h, according to needs and preference. I'm assuming that by this you mean to put it in /boot.config? Thanks for the feedback, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 13:23:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.30.145]) by hub.freebsd.org (Postfix) with ESMTP id 3739E14D73 for ; Tue, 29 Jun 1999 13:23:03 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id WAA29982 for ; Tue, 29 Jun 1999 22:23:00 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id WAA00880 for ; Tue, 29 Jun 1999 22:23:00 +0200 Date: Tue, 29 Jun 1999 22:23:00 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: stable@FreeBSD.ORG Subject: Partition with FFS filesystem locator Message-ID: <9906292218520.785-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It flew by last week, if I recall correctly on this mailing list, but I can't find it in the mailing list archives at www.freebsd.org and deleted the message. I'm in some need of a program that can search disks for the beginning of partitions containing FFS filesystems. Two different people mentioned the existance of such a beast; could someone please send it to me? (The cause is a disk that has been installed using OpenBSD in another machine, and the geometry doesn't match what FreeBSD sees, and I don't have enough space to install OpenBSD and copy over the files...) Thanks in advance! -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 17:39:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moose.tgsoft.com (cx20270-a.pwy1.sdca.home.com [24.0.169.3]) by hub.freebsd.org (Postfix) with SMTP id 25E8C151C9 for ; Tue, 29 Jun 1999 17:39:31 -0700 (PDT) (envelope-from thompson@moose.tgsoft.com) Received: (qmail 71271 invoked by uid 128); 30 Jun 1999 00:39:29 -0000 Date: 30 Jun 1999 00:39:29 -0000 Message-ID: <19990630003929.71270.qmail@moose.tgsoft.com> From: mark thompson To: freebsd-stable@freebsd.org Subject: aout -> elf Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a tool to convert a library from aout to elf? Has anybody wanted to do this? Perhaps bintools would know how to do it? I have a library that i actually bought and paid for that i would like to drag kicking and screaming into this modern new age. -mark -- "Well, How WOODE!" Jar Jar Binks must die... -mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 18: 2:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from golgotha.dons.net.au (spare6.gsoft.com.au [203.38.152.108]) by hub.freebsd.org (Postfix) with ESMTP id 580FB14F73 for ; Tue, 29 Jun 1999 18:02:12 -0700 (PDT) (envelope-from doconnor@golgotha.dons.net.au) Received: (from doconnor@localhost) by golgotha.dons.net.au (8.9.3/8.9.3) id KAA00453; Wed, 30 Jun 1999 10:31:48 +0930 (CST) (envelope-from doconnor) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990630103147:329=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <2hwvwnqh7g.fsf@dslab7.cs.uit.no> Date: Wed, 30 Jun 1999 10:31:47 +0930 (CST) From: "Daniel J. O'Connor" To: Frode Vatvedt Fjeld Subject: RE: MMX Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990630103147:329=_ Content-Type: text/plain; charset=us-ascii On 29-Jun-99 Frode Vatvedt Fjeld wrote: > What is the preferred way for my application to determine if the CPU > is MMX-capable? Use some MMX instructions and see if you catch a SIGILL or not? :) You could look through /var/run/dmesg.boot and have a look for -> CPU: Pentium/P55C (quarter-micron) (233.86-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x581 Stepping=1 Features=0x8001bf Which is probably a much more sensible way. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990630103147:329=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN3lse2j0TqzKxF7VAQEPfQP/Q/8K2UvHsRYLMXDlul3Q3wld1+tz8k05 jZEcsixTO8JWVXDVgivZLnwOVyD+tX85fc21OuhQ6XbNT1cA/TUdXiSlOrpOYen6 4PqMMYr7Ypn4p+sVS5KBxdTrus8RIHHkHQ/4vuKaLtj2WhjHsfcO+UPpkYDF9cDY inUgC9Pmf90= =tnn6 -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990630103147:329=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Jun 29 19:29:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kusanagi.boing.com (silver234.mminternet.com [209.241.149.234]) by hub.freebsd.org (Postfix) with ESMTP id 7DE74152B2 for ; Tue, 29 Jun 1999 19:29:33 -0700 (PDT) (envelope-from boing@kusanagi.boing.com) Received: (from boing@localhost) by kusanagi.boing.com (8.9.3/8.9.3) id TAA06545; Tue, 29 Jun 1999 19:29:23 -0700 (PDT) (envelope-from boing) Message-Id: <199906300229.TAA06545@kusanagi.boing.com> Date: Tue, 29 Jun 1999 19:29:22 -0700 (PDT) From: Geff Hanoian Subject: RE: MMX To: darius@dons.net.au Cc: frodef@acm.org, freebsd-stable@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30 Jun, Daniel J. O'Connor wrote: > > On 29-Jun-99 Frode Vatvedt Fjeld wrote: >> What is the preferred way for my application to determine if the CPU >> is MMX-capable? What about taking the code from /usr/src/sys/i386/i386/identcpu.c? (and which ever defines, etc are necessary). Can users execute such code without special privledges and after boot time? ----- static void do_cpuid(u_int ax, u_int *p) { __asm __volatile( ".byte 0x0f, 0xa2;" "movl %%eax, (%2);" "movl %%ebx, 4(%2);" "movl %%ecx, 8(%2);" "movl %%edx, 12(%2);" : "=a" (ax) : "0" (ax), "S" (p) : "bx", "cx", "dx" ); } ---- do_cpuid(1, regs); cpu_id = regs[0]; /* eax */ cpu_feature = regs[3]; /* edx */ ---- cpu_feature appears to contain a "feature set". Geff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 3: 6:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from amanda.swlct.sthames.nhs.uk (hide14.nhs.uk [194.6.81.14]) by hub.freebsd.org (Postfix) with ESMTP id 36EA914D47 for ; Wed, 30 Jun 1999 03:06:14 -0700 (PDT) (envelope-from greg@swlct.sthames.nhs.uk) Received: from greg (gquinlan [194.81.0.56]) by amanda.swlct.sthames.nhs.uk (8.9.3/8.9.3) with SMTP id LAA50536 for ; Wed, 30 Jun 1999 11:03:57 +0100 (BST) Message-ID: <033901bec2e0$262b7e40$380051c2@qmpgmc.ac.uk> Reply-To: "Greg Quinlan" From: "Greg Quinlan" To: References: <19990630003929.71270.qmail@moose.tgsoft.com> Subject: Man page "makemap" Date: Wed, 30 Jun 1999 11:05:57 +0100 Organization: Queen Mary's Hospital (SWLCT) X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know this is trivial; (but it would have saved me a lot of wasted effort) The "makemap" man page refers to "dbm" which isn't supported. (makemap: Type dbm not supported in this version) Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 7:51:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id D4FD614E7A; Wed, 30 Jun 1999 07:51:02 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from markab (markab [128.130.111.33]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id QAA08619; Wed, 30 Jun 1999 16:50:58 +0200 (MET DST) Date: Wed, 30 Jun 1999 16:50:58 +0200 (MET DST) From: Gerald Pfeifer To: obrien@freebsd.org Cc: stable@freebsd.org Subject: Re: NFSv3 seriously broken in 3.1 In-Reply-To: <19990628165518.A14652@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, David O'Brien wrote: >> Just to make sure, there has been no change between FreeBSD 3.1 and 3.2, >> right? > 3.1 defaulted to v3/TCP. 3.2 defaults to v3/UDP (or at least should). > HOWEVER /etc/amd.map specifies v2/UDP. > > Are you able to use ``snoop -v'' on a Sun to verify the protocols used? > (or tcpdump if you don't have Solaris) Yes. I checked with `snoop -v` and indeed I only saw NFS2 requests going over the wire from that specific FreeBSD box. In addition to our AMD maps we statically mount /var/mail; either without any options or when forced to v2/UDP, a 3.2 client hangs now and then when sending mail from Pine. Finally, please note that we are on an extremely bad network with ~10% Ethernet collisions. Perhaps a history might be helpful? 1. 2.2.x clients against a SunOS 4.x host. No problems. 2. 2.2.x clients against a Solaris 2.6 host. No problems. 3. 3.1 clients have long hangs now and then; sending mail with Pine hangs forever now and then. 2.2.x clients are fine. 4. Force v2/UDP for all AMD maps. Both 2.2.x and 3.1 clients are fine. 5. 3.2 clients experience infinite hangs when sending mail with Pine now and then, all others are fine. 6. Force v2/UDP for /var/mail on 3.2 client. No change. Frankly, I feel lost. :-( Any suggestions what I could try? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 9:37:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guard.polynet.lviv.ua (Guard.PolyNet.Lviv.UA [194.44.138.1]) by hub.freebsd.org (Postfix) with SMTP id 7F8BB15537 for ; Wed, 30 Jun 1999 09:37:47 -0700 (PDT) (envelope-from akorud@postoffice.polynet.lviv.ua) Received: (qmail 21708 invoked from network); 30 Jun 1999 16:37:44 -0000 Received: from unknown (HELO postoffice.polynet.lviv.ua) (unknown) by unknown with SMTP; 30 Jun 1999 16:37:44 -0000 Received: (qmail 36406 invoked by uid 1084); 30 Jun 1999 16:37:44 -0000 Date: 30 Jun 1999 19:37:44 +0300 Date: Wed, 30 Jun 1999 19:37:44 +0300 (EEST) From: Andrij Korud X-Sender: akorud@NetSurfer.lp.lviv.ua To: freebsd-stable@freebsd.org Subject: Linux emulation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. While trying to run PowerAlert plus for Linux on FreeBSD 3.2-STABLE box I got a message: "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" Any ideas? regards, Andrij Korud To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 9:50:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id F273A15532 for ; Wed, 30 Jun 1999 09:50:52 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA10746; Wed, 30 Jun 1999 09:43:29 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 30 Jun 1999 09:43:29 -0700 Date: Wed, 30 Jun 1999 09:43:29 -0700 (PDT) From: X-Sender: kip@luna To: Andrij Korud Cc: freebsd-stable@freebsd.org Subject: Re: Linux emulation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: akorud@polynet.lviv.ua,freebsd-stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got a similar ioctl complaint when I tried to run executor with OSS installed. -Kip On 30 Jun 1999, Andrij Korud wrote: > Hi. > While trying to run PowerAlert plus for Linux on FreeBSD 3.2-STABLE box I > got a message: > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > Any ideas? > > regards, > Andrij Korud > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 10:47:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 896AC155A0 for ; Wed, 30 Jun 1999 10:47:39 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id KAA04888; Wed, 30 Jun 1999 10:47:34 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA06939; Wed, 30 Jun 1999 10:47:31 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 30 Jun 1999 10:47:31 -0700 (PDT) Message-Id: <199906301747.KAA06939@vashon.polstra.com> To: thompson@moose.tgsoft.com Subject: Re: aout -> elf In-Reply-To: <19990630003929.71270.qmail@moose.tgsoft.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990630003929.71270.qmail@moose.tgsoft.com>, mark thompson wrote: > Is there a tool to convert a library from aout to elf? No, there is not. At one time I said I was going to write one, but I changed my mind. I had no use for it myself, it wasn't an interesting project at all, and nobody wanted to pay for it either. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 10:52:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ceia.nordier.com (m1-33-dbn.dial-up.net [196.34.155.33]) by hub.freebsd.org (Postfix) with ESMTP id 0D2EA153C5 for ; Wed, 30 Jun 1999 10:52:13 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id TAA05813; Wed, 30 Jun 1999 19:51:14 +0200 (SAST) From: Robert Nordier Message-Id: <199906301751.TAA05813@ceia.nordier.com> Subject: Re: comconsole In-Reply-To: from Doug at "Jun 29, 1999 12:57:32 pm" To: Doug@gorean.org (Doug) Date: Wed, 30 Jun 1999 19:51:12 +0200 (SAST) Cc: stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Cc trimmed] > > > >> > Once you get the login prompt set up, redirecting the boot > > > >> > messages should be easy. First, the COMCONSOLE kernel option is now > > > >> > deprecated, see the sio options in LINT for more details. Also, you should > > > >> > read the info in the /boot directory, and read the man pages for loader > > > >> > and boot. At this point the easiest way to use the -P option is to put > > > >> > 'boot -P' as the last line of your /boot/loader.rc file. > > > >> > > > >> A -P option to boot is ignored. Put the -P in /boot.config. > > Hrrm... it works fine in /boot/loader.rc on -current, maybe it > doesn't work in -stable. My apologies if so. It does nothing. Valid option letters are [acCdghrsv]. > > > When I setup server box(without VGA console, 3.1-RELEASE), > > > I added ``set console=comconsole'' to /boot/loader.rc. > > > Also enable serial console getty in /etc/ttys > > > > > > Which method is better for serial(com) console? > > > > If you are using a serial console, it is generally best to enable it > > as soon as possible. > > Agreed, however there are two issues here. First, the man pages > all say that /boot.config is deprecated. All which man pages? > Also, what I'd *really* like to > do is get a 'boot -P' in as early as possible, then still have the > autoboot option in loader. As far as I can see, that's just not possible, > although I'd love to be proven wrong. The loader "boot" command means "boot immediately", as documented in the help. The "autoboot" command means "boot after a delay", as documented in the help. They're mutually exclusive, so you're right: the way you want to do it is just not possible. > > > There is a lot of stuff that happens before > > loader(8) gets control. The flow is roughly as follows: > > > > boot1 > > btx > > boot2 > > btxldr > > btx > > loader > > Wow.... where were you last week when I asked for a list like > this. :-/ Could you add one more detail to this list, namely what config > files get executed when in this schedule? It would be really helpful to > me, and I'm sure others. I've read the man pages till I'm going loopy on > them and it's sinking in very slowly, but not fully there yet. boot2: /boot.config loader: /boot/loader.rc /boot/defaults/loader.conf /boot/loader.conf /boot/loader.conf.local kernel: /boot/kernel.conf > > To avoid missing potentially informative diagnostics, etc., the best > > place to start the serial console is therefore in boot2, using one > > of the options -D, -P, or -h, according to needs and preference. > > I'm assuming that by this you mean to put it in /boot.config? Yes. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 11:29:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id D1946155EA for ; Wed, 30 Jun 1999 11:29:11 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id NAA41897; Wed, 30 Jun 1999 13:28:58 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 30 Jun 1999 13:28:57 -0500 (CDT) From: Chris Dillon To: Andrij Korud Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Linux emulation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30 Jun 1999, Andrij Korud wrote: > Hi. > While trying to run PowerAlert plus for Linux on FreeBSD 3.2-STABLE box I > got a message: > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > Any ideas? > > regards, > Andrij Korud I'll be darned if I wasn't trying the same thing yesterday. :-) I'm betting that ioctl has something to do with opening the serial port, since the daemon keeps spitting out "Communication to UPS lost" in the logs, even though I verified communication by using tip(1) on the port and chatting with the UPS (the UPS "driver" files, which are actually Win-INI style text files, are a good albeit cryptic reference to what commands each UPS uses.) I also couldn't get the Shutdown Client to work with the server running on an NT box, even though no errors were displayed. I've already modified the installation script to detect FreeBSD and DTRT for the most part, and if I ever get this to work under emulation, I think I'll make a port out of it (ala the StarOffice and WP ports), and possibly even submit the installation script patches to TrippLite, while at the same time pushing them for a native FreeBSD version. :-) -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 11:31:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from callisto.fortean.com (callisto.fortean.com [209.42.229.241]) by hub.freebsd.org (Postfix) with ESMTP id BAA0D15642 for ; Wed, 30 Jun 1999 11:31:02 -0700 (PDT) (envelope-from walter@fortean.com) Received: from localhost (walter@localhost) by callisto.fortean.com (8.9.3/8.9.3) with SMTP id OAA55595; Wed, 30 Jun 1999 14:31:22 -0400 (EDT) (envelope-from walter@fortean.com) X-Authentication-Warning: callisto.fortean.com: walter owned process doing -bs Date: Wed, 30 Jun 1999 14:31:22 -0400 (EDT) From: Bruce Walter To: John Polstra Cc: thompson@moose.tgsoft.com, stable@FreeBSD.ORG Subject: Re: aout -> elf In-Reply-To: <199906301747.KAA06939@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Jun 1999, John Polstra wrote: > In article <19990630003929.71270.qmail@moose.tgsoft.com>, > mark thompson wrote: > > Is there a tool to convert a library from aout to elf? > > No, there is not. At one time I said I was going to write one, but I > changed my mind. I had no use for it myself, it wasn't an interesting > project at all, and nobody wanted to pay for it either. Arghhh! I need this tool too. I started to poke around binutils, but ran out of available time. I'll check into it again. Is this something libbfd could make less painless? I'm not as familiar with this area as I would need to be useful. - Bruce ______________________ Bruce M. Walter, Principal NIXdesign Group Inc. 426 S. Dawson Street Raleigh NC 27601 USA 919.829.4901 Tel (ext 11) 919.829.4993 Fax http://www.nixdesign.com Visual communications | concept + code To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 11:34:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 85DDD15628 for ; Wed, 30 Jun 1999 11:34:31 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id LAA05160; Wed, 30 Jun 1999 11:34:30 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA07144; Wed, 30 Jun 1999 11:34:29 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 30 Jun 1999 11:34:29 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Bruce Walter Subject: Re: aout -> elf Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Walter wrote: > Is this something libbfd could make less painless? Yes, "less painless" is an apt description of the effects of using libbfd. ;-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 11:50:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 661D214EFE for ; Wed, 30 Jun 1999 11:50:06 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Wed, 30 Jun 1999 11:50:05 -0700 From: "David Schwartz" To: "Chris Dillon" , "Andrij Korud" Cc: Subject: RE: Linux emulation Date: Wed, 30 Jun 1999 11:50:05 -0700 Message-ID: <000101bec329$5e488900$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It does. It has to do with how the modem control lines are handled. DS > > Hi. > > While trying to run PowerAlert plus for Linux on FreeBSD > 3.2-STABLE box I > > got a message: > > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > > Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 12:17:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guard.polynet.lviv.ua (Guard.PolyNet.Lviv.UA [194.44.138.1]) by hub.freebsd.org (Postfix) with SMTP id 1321B15660 for ; Wed, 30 Jun 1999 12:17:03 -0700 (PDT) (envelope-from akorud@polynet.lviv.ua) Received: (qmail 25748 invoked from network); 30 Jun 1999 19:17:00 -0000 Received: from unknown (HELO postoffice.polynet.lviv.ua) (unknown) by unknown with SMTP; 30 Jun 1999 19:17:00 -0000 Received: (qmail 42419 invoked from network); 30 Jun 1999 19:16:59 -0000 Received: (ofmipd unknown); 30 Jun 1999 19:16:37 -0000 Date: 30 Jun 1999 22:16:58 +0300 Message-ID: From: "Andrij Korud" To: "Chris Dillon" Cc: freebsd-stable@freebsd.org Subject: RE: Linux emulation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 30 Jun 1999, Andrij Korud wrote: > > > Hi. > > While trying to run PowerAlert plus for Linux on FreeBSD > 3.2-STABLE box I > > got a message: > > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > > Any ideas? > > > > regards, > > Andrij Korud > > I'll be darned if I wasn't trying the same thing yesterday. :-) I'm > betting that ioctl has something to do with opening the serial port, > since the daemon keeps spitting out "Communication to UPS lost" in the > logs, even though I verified communication by using tip(1) on the port > and chatting with the UPS (the UPS "driver" files, which are actually > Win-INI style text files, are a good albeit cryptic reference to what > commands each UPS uses.) > > I also couldn't get the Shutdown Client to work with the server > running on an NT box, even though no errors were displayed. > > I've already modified the installation script to detect FreeBSD and > DTRT for the most part, and if I ever get this to work under > emulation, I think I'll make a port out of it (ala the StarOffice and > WP ports), and possibly even submit the installation script patches to > TrippLite, while at the same time pushing them for a native FreeBSD > version. :-) > > Just now I've traced it under Linux using strace utility and found that it fail on ioctl(comport, TIOCMBIC... but now I really don't know what this operation should do. regards, Andrij Korud To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 12:24:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id B6DDC153C5 for ; Wed, 30 Jun 1999 12:24:07 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Wed, 30 Jun 1999 12:24:05 -0700 From: "David Schwartz" To: "Andrij Korud" , "Chris Dillon" Cc: Subject: RE: Linux emulation Date: Wed, 30 Jun 1999 12:24:05 -0700 Message-ID: <000001bec32e$1e4828b0$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's trying to control DTR. DS > > On 30 Jun 1999, Andrij Korud wrote: > > > > > Hi. > > > While trying to run PowerAlert plus for Linux on FreeBSD > > 3.2-STABLE box I > > > got a message: > > > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > > > Any ideas? > > > > > > regards, > > > Andrij Korud > > > > I'll be darned if I wasn't trying the same thing yesterday. :-) I'm > > betting that ioctl has something to do with opening the serial port, > > since the daemon keeps spitting out "Communication to UPS lost" in the > > logs, even though I verified communication by using tip(1) on the port > > and chatting with the UPS (the UPS "driver" files, which are actually > > Win-INI style text files, are a good albeit cryptic reference to what > > commands each UPS uses.) > > > > I also couldn't get the Shutdown Client to work with the server > > running on an NT box, even though no errors were displayed. > > > > I've already modified the installation script to detect FreeBSD and > > DTRT for the most part, and if I ever get this to work under > > emulation, I think I'll make a port out of it (ala the StarOffice and > > WP ports), and possibly even submit the installation script patches to > > TrippLite, while at the same time pushing them for a native FreeBSD > > version. :-) > > > > > Just now I've traced it under Linux using strace utility and found that it > fail on ioctl(comport, TIOCMBIC... > but now I really don't know what this operation should do. > > regards, Andrij Korud > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 18:54:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5ECFA15502; Wed, 30 Jun 1999 18:54:24 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA07057; Wed, 30 Jun 1999 18:54:24 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA08285; Wed, 30 Jun 1999 18:54:23 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Wed, 30 Jun 1999 18:54:23 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org, stable@freebsd.org Subject: HEADS UP: Soft-updates sources are moving soon Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sometime this weekend (July 3-5) I am planning to repository-copy the soft-updates sources from their current location in "src/contrib/sys/softupdates" to "src/sys/contrib/softupdates". All of you using soft-updates will need to adjust your symbolic links in "src/sys/ufs/ffs" after this change has taken effect. The reasons for the move have been discussed before. Briefly, we want to move all of the kernel code to "src/sys" so that the sys tree will be more self-contained. Kirk McKusick has agreed to this change -- in fact he favors it. I'm going to do this in both the -current and RELENG_3 branches. Here is the 1-question FAQ: Q. These symbolic links are a pain. Why don't you just edit "src/sys/conf/files" appropriately? A. The license terms for soft-updates do not permit that. See the FreeBSD mailing list archives (the FreeBSD-current list, probably) for more details. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 19: 5:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E52814EFE; Wed, 30 Jun 1999 19:05:31 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id MAA32098; Thu, 1 Jul 1999 12:05:29 +1000 (EST) Received: from dstc.edu.au (localhost [127.0.0.1]) by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) with ESMTP id MAA02271; Thu, 1 Jul 1999 12:05:29 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: HEADS UP: Soft-updates sources are moving soon In-reply-to: Your message of "Wed, 30 Jun 1999 18:54:23 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 12:05:29 +1000 Message-ID: <2269.930794729@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the 1-question FAQ: Q. These symbolic links are a pain. Why don't you just edit "src/sys/conf/files" appropriately? A. The license terms for soft-updates do not permit that. See the FreeBSD mailing list archives (the FreeBSD-current list, probably) for more details. Would it be legal under the licence to include a rule in some Makefile which did the damn things, but was not automatically invoked anywhere? o Seems to me this would preserve the fundamental "intentionality" of the desire to have, and enable the softupdates. Would it be legal to include in standard CVSUP configs rules which prevent loss of the links if installed? o I may be wrong, but I think I loose them when I refresh if some rules are present. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 19:12:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E58F7151F9; Wed, 30 Jun 1999 19:12:26 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id TAA07135; Wed, 30 Jun 1999 19:12:25 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA08842; Wed, 30 Jun 1999 19:12:24 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2269.930794729@dstc.edu.au> Date: Wed, 30 Jun 1999 19:12:24 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: George Michaelson Subject: Re: HEADS UP: Soft-updates sources are moving soon Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG George Michaelson wrote: > Q. These symbolic links are a pain. Why don't you just edit > "src/sys/conf/files" appropriately? > > A. The license terms for soft-updates do not permit that. See the > FreeBSD mailing list archives (the FreeBSD-current list, probably) for > more details. > > Would it be legal under the licence to include a rule in some Makefile > which did the damn things, but was not automatically invoked anywhere? Please don't start a discussion about this without first studying the mailing list archives. All of this stuff has been discussed before, and needn't be rehashed again. > Would it be legal to include in standard CVSUP configs rules which prevent > loss of the links if installed? > > o I may be wrong, but I think I loose them when I refresh if some rules > are present. CVSup won't touch your symbolic links. It won't touch any file that it doesn't know anything about. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 19:52:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id A52B814A09; Wed, 30 Jun 1999 19:52:39 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id MAA09795; Thu, 1 Jul 1999 12:52:38 +1000 (EST) Received: from dstc.edu.au (localhost [127.0.0.1]) by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) with ESMTP id MAA02322; Thu, 1 Jul 1999 12:52:37 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Soft-updates sources are moving soon In-reply-to: Your message of "Wed, 30 Jun 1999 19:12:24 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 12:52:37 +1000 Message-ID: <2320.930797557@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cool. endit. -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 20:17: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id D813514CBE; Wed, 30 Jun 1999 20:16:57 -0700 (PDT) (envelope-from ggm@dstc.edu.au) Received: from asuncion.dstc.edu.au (asuncion.dstc.edu.au [130.102.176.155]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id NAA23601; Thu, 1 Jul 1999 13:16:53 +1000 (EST) Received: from dstc.edu.au (localhost [127.0.0.1]) by asuncion.dstc.edu.au (8.8.8+Sun/8.8.8) with ESMTP id NAA02360; Thu, 1 Jul 1999 13:16:52 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: John Polstra Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Soft-updates sources are moving soon In-reply-to: Your message of "Wed, 30 Jun 1999 19:12:24 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 13:16:52 +1000 Message-ID: <2358.930799012@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The discussion(s) took place on hackers@FreeBSD.org. The search string in the archives which works is: kirk AND soft-update AND integration note the soft-update, not softupdates. note hackers. not current or stable. If you search anywhere else you will get techno-related issues. cheers -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 20:58:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id EF73C14CBE; Wed, 30 Jun 1999 20:58:12 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id UAA07398; Wed, 30 Jun 1999 20:58:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id UAA09050; Wed, 30 Jun 1999 20:58:09 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <2358.930799012@dstc.edu.au> Date: Wed, 30 Jun 1999 20:58:09 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: George Michaelson Subject: Re: HEADS UP: Soft-updates sources are moving soon Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG George Michaelson wrote: > > The discussion(s) took place on hackers@FreeBSD.org. > > The search string in the archives which works is: > > kirk AND soft-update AND integration > > note the soft-update, not softupdates. Thanks! I couldn't remember for sure where the discussion had been. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 21:29:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id A103F15518; Wed, 30 Jun 1999 21:29:39 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip145.houston3.tx.pub-ip.psi.net [38.12.169.145]) by leap.innerx.net (Postfix) with ESMTP id 31E17370E0; Thu, 1 Jul 1999 00:29:33 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id XAA71287; Wed, 30 Jun 1999 23:28:59 -0500 (CDT) (envelope-from chris) Date: Wed, 30 Jun 1999 23:28:58 -0500 From: Chris Costello To: Randall Hopper Cc: stable@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: 3.2-RELEASE Feedback Message-ID: <19990630232857.A71244@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990626184311.A5290@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990626184311.A5290@ipass.net>; from Randall Hopper on Sat, Jun 26, 1999 at 06:43:11PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jun 26, 1999, Randall Hopper wrote: > 8) (Nit) Boot-up probes spelling error: > "bt_isa_probe: Probe failled for card at 0x330" That was patched, but apparently it was not merged to 3.2 from -CURRENT. Perhaps you'd like to do it, Justin? -- Chris Costello It is easier to change the specification to fit the program than vice versa. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Jun 30 23:53: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2A9D215683 for ; Wed, 30 Jun 1999 23:52:55 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA40472; Thu, 1 Jul 1999 00:52:50 -0600 (MDT) (envelope-from ken) Message-Id: <199907010652.AAA40472@panzer.kdm.org> Subject: Re: Adaptec 2944 and 3.2-stable In-Reply-To: from "jan@chrillesen.dk" at "Jun 29, 1999 11:52:52 am" To: jan@chrillesen.dk Date: Thu, 1 Jul 1999 00:52:50 -0600 (MDT) Cc: freebsd-stable@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jan@chrillesen.dk wrote... > Hi. > > 3.2-stable does not seem to recognize my Adaptec 2944uw. It seems the > kernel finds the device (vendor 9004 = Adaptec) but does not recognize it > as a SCSI adaptor. > > I've tried building a UP kernel and tried leaving out the various > AHC-options, but without luck. Linux works fine on the same setup, so I > don't believe it's a hardware problem. > > Hardware: HP Netserver LPr, 2 CPU's, build-in NCR 53c875 SCSI. > > I'm still rather new to FreeBSD so I might have overlooked something > obviuosly. You left out one critical detail -- what version of 3.2-stable are you using? Justin supposedly fixed this on May 26th in -current and -stable. If you're using a version of -stable newer than that, there may still be a problem in the driver. Otherwise, you probably need to upgrade. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 0:44:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.welearn.com.au (phoenix.welearn.com.au [139.130.44.81]) by hub.freebsd.org (Postfix) with ESMTP id 6381915620 for ; Thu, 1 Jul 1999 00:44:27 -0700 (PDT) (envelope-from sue@phoenix.welearn.com.au) Received: (from sue@localhost) by phoenix.welearn.com.au (8.9.1/8.9.0) id RAA05937; Thu, 1 Jul 1999 17:44:28 +1000 (EST) Message-ID: <19990701174424.31398@welearn.com.au> Date: Thu, 1 Jul 1999 17:44:24 +1000 From: Sue Blake To: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading - one more time please References: <19990627191626.53465@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19990627191626.53465@welearn.com.au>; from Sue Blake on Sun, Jun 27, 1999 at 07:16:26PM +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all the replies to this one :-) On Sun, Jun 27, 1999 at 07:16:26PM +1000, Sue Blake wrote: > > I've got a machine running 2.2.7-STABLE which I want to upgrade to > the current -STABLE. I also want the full repository. > I have a 3.1-RELEASE CD, so I can grab its repository, cvsup, and > pull out the latest -STABLE sources. OK, that's where I'm up to, got the full repository and need to replace last year's sources with the newies. Now I've got a mental block or hole or something, just spent the last two hours reading doccos and writing down a list of possibly correct ways to checkout the sources for 3.2-STABLE so that they replace the existing 2.2.7-STABLE sources. If I try to represent what my mind is juggling, it's something like cvs [-q] [co|update] [-P] [-d] [-r RELENG_3] [src|world] where [] means maybe needed. As you see, the only part I'm sure of is the "cvs" at the start :-) It used to be so simple, and I could write an essay on what each bit does, but I'm buggered if I can work out which bits I need to stick together to get the job done. How will the CVS stuff that's already in the sources from the other branch affect this? Should I just delete the whole lot and start again with a fresh checkout? Is that necessary/safer, or would that just be cheating? I guess I'd rather know what's the most correct way here. Then from the responses I got to my other questions, it seems that I can try 'make upgrade' before messing around and see how I go, and if it doesn't work then do a binary upgrade install from the 3.1 CDs. At the end I'll have either an updated system or a hilarious web page :-) -- Regards, -*Sue*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 2:21:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id CE4CE1572D for ; Thu, 1 Jul 1999 02:21:13 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id EAA00511; Thu, 1 Jul 1999 04:20:31 -0500 (CDT) Date: Thu, 1 Jul 1999 04:20:31 -0500 From: "Matthew D. Fuller" To: Sue Blake Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading - one more time please Message-ID: <19990701042031.L26878@futuresouth.com> References: <19990627191626.53465@welearn.com.au> <19990701174424.31398@welearn.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990701174424.31398@welearn.com.au>; from Sue Blake on Thu, Jul 01, 1999 at 05:44:24PM +1000 X-OS: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 05:44:24PM +1000, a little birdie told me that Sue Blake remarked > > OK, that's where I'm up to, got the full repository and need to replace > last year's sources with the newies. Now I've got a mental block or > hole or something, just spent the last two hours reading doccos and > writing down a list of possibly correct ways to checkout the sources > for 3.2-STABLE so that they replace the existing 2.2.7-STABLE sources. > > If I try to represent what my mind is juggling, it's something like > cvs [-q] [co|update] [-P] [-d] [-r RELENG_3] [src|world] > where [] means maybe needed. As you see, the only part I'm sure of is > the "cvs" at the start :-) It used to be so simple, and I could write > an essay on what each bit does, but I'm buggered if I can work out > which bits I need to stick together to get the job done. How will the > CVS stuff that's already in the sources from the other branch affect > this? Should I just delete the whole lot and start again with a fresh > checkout? Is that necessary/safer, or would that just be cheating? > I guess I'd rather know what's the most correct way here. Here's my take (I use CVS for lots of other things than FreeBSD src/ports/etc as well). - ~/.cvsrc: [21:27:04] mortis:~ (ttyp4):{162}% cat .cvsrc diff -u update -d -P checkout -P So I can't forget flags ;> - When changing branches, just whack your src tree and cvs co clean. It's not THAT slow (cvs co of ports takes ~10 minutes, src may be closer to a half hour.) We have machines running HEAD (-current), RELENG_3, and RELENG_2_2, so I'm constantly whack/co'ing back and forth (hint: newfs is much faster than rm -rf ;) - So with a clean /usr/src, set your CVSROOT to wherever your CVS repo is (/home/ncvs seems to be the preference, I use /usr/cvs (also a seperate partition) ) Then something along the lines of (cd /usr && cvs co src) And run it under time(1) while you're at it, so you can put how long it took on your webpage! :) As far as the actual updating, I think the 'right' way is something like: * Update to latest RELENG_2_2 (build/installworld) * Update to 3.1-RELEASE (make update I think is preferred) * Update to latest RELENG_3 At least, that's the way I'd do it if I had to now. Slower, lots of steps, but at least they're small ones. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 2:26: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 7569F15715 for ; Thu, 1 Jul 1999 02:25:58 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id EAA00640; Thu, 1 Jul 1999 04:25:21 -0500 (CDT) Date: Thu, 1 Jul 1999 04:25:21 -0500 From: "Matthew D. Fuller" To: Sue Blake Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrading - one more time please Message-ID: <19990701042521.O26878@futuresouth.com> References: <19990627191626.53465@welearn.com.au> <19990701174424.31398@welearn.com.au> <19990701042031.L26878@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990701042031.L26878@futuresouth.com>; from Matthew D. Fuller on Thu, Jul 01, 1999 at 04:20:31AM -0500 X-OS: FreeBSD Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 04:20:31AM -0500, a little birdie told me that Matthew D. Fuller remarked > Then something along the lines of (cd /usr && cvs co src) Note that this should of course be 'cvs co -r src'. Sleep. Need sleeeeee... zzz. -- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller MF4839 http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 6:36:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (Postfix) with ESMTP id F0DD114BF2 for ; Thu, 1 Jul 1999 06:36:14 -0700 (PDT) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.8.6 (PHNE_14041)/8.7.1) id PAA05628; Thu, 1 Jul 1999 15:36:12 +0200 (MESZ) To: freebsd-stable@freebsd.org Subject: Q: rpc.lockd (*broken!*) ?? Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=NIL From: Marko Schuetz Date: 01 Jul 1999 15:36:11 +0200 Message-ID: <869090sd9w.fsf@king.ki.informatik.uni-frankfurt.de> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG in /etc/defaults/rc.conf it says rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. so is this still true? I have an NFS server running 3.1-stable which has a repository for aegis supposed to be accessed from HP/UX clients. When I do aenpr example -dir /tmp/aegis/example on the server itself it works, but on one of the NFS clients I get 15:35 marko@king% aenpr example -dir /opt/tmp/example aegis: fcntl("/usr1/users/ki/com/aegis/lockfile", F_SETLKW, &{type = F_WRLCK, whence = SEEK_SET, start = 0, len = 1, pid = 0}): No locks available Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 6:48:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 72E0314E8F for ; Thu, 1 Jul 1999 06:48:04 -0700 (PDT) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.8.6 (PHNE_14041)/8.7.1) id PAA05634; Thu, 1 Jul 1999 15:48:02 +0200 (MESZ) To: freebsd-stable@freebsd.org Subject: Re: Q: rpc.lockd (*broken!*) ?? References: <869090sd9w.fsf@king.ki.informatik.uni-frankfurt.de> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=NIL From: Marko Schuetz Date: 01 Jul 1999 15:48:02 +0200 In-Reply-To: Marko Schuetz's message of "01 Jul 1999 15:36:11 +0200" Message-ID: <866744scq5.fsf@king.ki.informatik.uni-frankfurt.de> Lines: 23 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Marko" == Marko Schuetz writes: Marko> in /etc/defaults/rc.conf it says Marko> rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. Marko> so is this still true? Marko> I have an NFS server running 3.1-stable which has a repository for Marko> aegis supposed to be accessed from HP/UX clients. Marko> When I do Marko> aenpr example -dir /tmp/aegis/example Marko> on the server itself it works, but on one of the NFS clients I get Marko> 15:35 marko@king% aenpr example -dir /opt/tmp/example Marko> aegis: fcntl("/usr1/users/ki/com/aegis/lockfile", F_SETLKW, &{type = F_WRLCK, Marko> whence = SEEK_SET, start = 0, len = 1, pid = 0}): No locks available Forgot to say: it does *seem* to work when rpc.lockd is running. Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 7: 4:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id DB45314BCD for ; Thu, 1 Jul 1999 07:04:02 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 1 Jul 1999 15:03:53 +0100 (BST) Date: Thu, 1 Jul 1999 15:03:53 +0100 From: David Malone To: Marko Schuetz Cc: freebsd-stable@freebsd.org Subject: Re: Q: rpc.lockd (*broken!*) ?? Message-ID: <19990701150352.A9794@walton.maths.tcd.ie> References: <869090sd9w.fsf@king.ki.informatik.uni-frankfurt.de> <866744scq5.fsf@king.ki.informatik.uni-frankfurt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <866744scq5.fsf@king.ki.informatik.uni-frankfurt.de>; from Marko Schuetz on Thu, Jul 01, 1999 at 03:48:02PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 01, 1999 at 03:48:02PM +0200, Marko Schuetz wrote: > Forgot to say: it does *seem* to work when rpc.lockd is running. It works in the sense that it always says "Here - have a lock", even if someone else thinks they have one. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 11:47:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from juice.fusebox.com (juice.fusebox.com [205.230.104.35]) by hub.freebsd.org (Postfix) with SMTP id 883471507A for ; Thu, 1 Jul 1999 11:47:20 -0700 (PDT) (envelope-from basem@fusebox.com) Received: from jimmy.fusebox.com (jimmy.fusebox.com [205.230.104.7]) by juice.fusebox.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via SMTP id OAA03766 for ; Thu, 1 Jul 1999 14:39:24 -0700 Date: Thu, 1 Jul 1999 14:39:22 -0700 (PDT) From: Basem Moussa To: freebsd-stable@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 17:10:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 97E7114F29; Thu, 1 Jul 1999 17:10:47 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-148.dialup.rdu.ipass.net [209.170.132.148]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id UAA18505; Thu, 1 Jul 1999 20:10:41 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id UAA05908; Thu, 1 Jul 1999 20:12:36 -0400 (EDT) (envelope-from rhh) Date: Thu, 1 Jul 1999 20:12:36 -0400 From: Randall Hopper To: Frode Vatvedt Fjeld , "Daniel J. O'Connor" , Geff Hanoian Cc: freebsd-stable@freebsd.org, multimedia@freebsd.org Subject: Re: MMX Message-ID: <19990701201236.A5532@ipass.net> References: <199906300229.TAA06545@kusanagi.boing.com> <2hwvwnqh7g.fsf@dslab7.cs.uit.no> <2hwvwnqh7g.fsf@dslab7.cs.uit.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <2hwvwnqh7g.fsf@dslab7.cs.uit.no>; from Frode Vatvedt Fjeld on Tue, Jun 29, 1999 at 03:17:23PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frode Vatvedt Fjeld: |What is the preferred way for my application to determine if the CPU |is MMX-capable? Daniel J. O'Connor: |Use some MMX instructions and see if you catch a SIGILL or not? :) Geff Hanoian: | __asm __volatile( | ".byte 0x0f, 0xa2;" Seems like this would be perfect for the sysctl MIB. We have a few CPU-related ones already: > sysctl -a | grep -i cpu kern.ccpu: 1948 hw.ncpu: 1 What about: hw.cpu.has_mmx: 1 hw.cpu.has_3dnow: 1 hw.cpu.has_sse: 0 In leiu of that, I believe I recall reading that the SIGILL approach works on FreeBSD. Seems like Roger Hardiman uses/used MMX on FreeBSD for some of his signal processing work. You might chat with him. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Jul 1 17:29:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 53C7214F5A; Thu, 1 Jul 1999 17:29:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02255; Thu, 1 Jul 1999 17:23:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907020023.RAA02255@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Randall Hopper Cc: Frode Vatvedt Fjeld , "Daniel J. O'Connor" , Geff Hanoian , freebsd-stable@freebsd.org, multimedia@freebsd.org Subject: Re: MMX In-reply-to: Your message of "Thu, 01 Jul 1999 20:12:36 EDT." <19990701201236.A5532@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 01 Jul 1999 17:23:48 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Seems like this would be perfect for the sysctl MIB. We have a few > CPU-related ones already: > > > sysctl -a | grep -i cpu > kern.ccpu: 1948 > hw.ncpu: 1 > > What about: > > hw.cpu.has_mmx: 1 > hw.cpu.has_3dnow: 1 > hw.cpu.has_sse: 0 > > In leiu of that, I believe I recall reading that the SIGILL approach works > on FreeBSD. Seems like Roger Hardiman uses/used MMX on FreeBSD for some of > his signal processing work. You might chat with him. I would recommend hw.cpu.feature: MMX,CPUID,MTRR etc. This is probably more extensible. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 2: 5: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27]) by hub.freebsd.org (Postfix) with ESMTP id 46A8314CF3 for ; Fri, 2 Jul 1999 02:05:01 -0700 (PDT) (envelope-from frodef@dslab7.cs.uit.no) Received: (from frodef@localhost) by dslab7.cs.uit.no (8.9.3/8.9.1) id LAA09275; Fri, 2 Jul 1999 11:02:49 +0200 (CEST) (envelope-from frodef) To: freebsd-stable@freebsd.org Subject: Re: MMX References: <199907020023.RAA02255@dingo.cdrom.com> From: Frode Vatvedt Fjeld Date: 02 Jul 1999 11:02:48 +0200 In-Reply-To: Mike Smith's message of "Thu, 01 Jul 1999 17:23:48 -0700" Message-ID: <2hemirwhjb.fsf@dslab7.cs.uit.no> Lines: 18 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, in summary: * I can try some MMX and catch SIGILL if non-MMX CPU. Works (?), but is ugly and clumsy. * I can use CPUID, but I guess then I should be prepared to catch SIGILL on old CPUs so I don't gain much from the above. * I could look in dmesg, but this is really ugly since this is a ring-buffer, and the particular boot-up message is not guaranteed to be in the buffer at all. * There _should_ be some sysctl for this. Can someone please do this? Or point me to how I'd go about doing it myself? -- Frode Vatvedt Fjeld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 2:12: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from muffin.highwire.local (pool-1-p34.innotts.co.uk [212.56.33.34]) by hub.freebsd.org (Postfix) with ESMTP id 74D7714F0B for ; Fri, 2 Jul 1999 02:11:55 -0700 (PDT) (envelope-from robmel@nadt.org.uk) Received: from [172.16.17.20] (robsmac.highwire.local [172.16.17.20]) by muffin.highwire.local (8.9.3/8.9.3) with ESMTP id KAA29995; Fri, 2 Jul 1999 10:10:44 +0100 (BST) (envelope-from robmel@nadt.org.uk) Mime-Version: 1.0 X-Sender: robmel@wrcmail (Unverified) Message-Id: In-Reply-To: References: Date: Fri, 2 Jul 1999 10:11:34 +0100 To: Chris Dillon From: Robin Melville Subject: Re: Linux emulation Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:28 pm -0500 30/6/99, Chris Dillon wrote: >I've already modified the installation script to detect FreeBSD and >DTRT for the most part, and if I ever get this to work under >emulation, I think I'll make a port out of it (ala the StarOffice and >WP ports), and possibly even submit the installation script patches to >TrippLite, while at the same time pushing them for a native FreeBSD >version. :-) I, for one, would really appreciate you doing that :) Cheers Robin. ---------------------------------------------------------------------- Robin Melville, Addiction Information Service Nottingham Alcohol & Drug Team Tel: +44 (0)115 952 9478 Fax: +44 (0)115 952 9421 work: robmel@nadt.org.uk Pages: http://www.innotts.co.uk/nadt ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 2:22:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id E28AB14F42; Fri, 2 Jul 1999 02:22:39 -0700 (PDT) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (scary.dmem.strath.ac.uk [130.159.202.5]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id KAA03488 Fri, 2 Jul 1999 10:21:27 +0100 (BST) Message-ID: <377C84BF.33E147F2@cs.strath.ac.uk> Date: Fri, 02 Jul 1999 10:22:07 +0100 From: Roger Hardiman Organization: Strathclyde University X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Randall Hopper Cc: Frode Vatvedt Fjeld , "Daniel J. O'Connor" , Geff Hanoian , freebsd-stable@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: MMX References: <199906300229.TAA06545@kusanagi.boing.com> <2hwvwnqh7g.fsf@dslab7.cs.uit.no> <2hwvwnqh7g.fsf@dslab7.cs.uit.no> <19990701201236.A5532@ipass.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Frode Vatvedt Fjeld: > |What is the preferred way for my application to determine if the CPU > |is MMX-capable? > > In leiu of that, I believe I recall reading that the SIGILL approach works > on FreeBSD. Seems like Roger Hardiman uses/used MMX on FreeBSD for some of > his signal processing work. You might chat with him. Indeed, I do write MMX code. The proper way, if you want your code to be portable to other OSs (like NetBSD/OpenBSD/Linux/ etc), is to ask the CPU what it can do. Here is the almost proper way to determine if a CPU has MMX support. I say _alomost_ because it uses the CPU-ID instruction. This instruction is not on 386 machines or some early 486 machines. There is another test you should do first to determine if there was a CPU-ID instruction. I'll dig that up shortly. // mmx.c // Detect MMX Instruction set // Roger Hardiman // University of Strathclyde // August 1997 // Test for the Presence of an MMX Instruction Set // Returns TRUE if MMX CPU, FALSE if plain CPU. int test_mmx() { int result; __asm __volatile( "movl $1,%%eax\n" "cpuid\n" "andl $0x800000,%%edx\n" "shrl $23,%%edx\n" : "=d" (result) :: "ax", "dx"); if (result) printf("MMX detected\n"); else printf("No MMX.\n"); return result; } My program is then full of if (mmx_detected) { MMX code else old C code Bye Roger -- Roger Hardiman Strathclyde Uni Telepresence Research Group, Glasgow, Scotland. http://telepresence.dmem.strath.ac.uk 0141 548 2897 roger@cs.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 4:47:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id B13FF14F0F for ; Fri, 2 Jul 1999 04:47:10 -0700 (PDT) (envelope-from freebsd-stable@scc.nl) Received: from scones.sup.scc.nl (i359.ztm.euronet.nl [194.134.67.120]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id NAA07049 from for ; Fri, 2 Jul 1999 13:47:08 +0200 (MET DST) Received: (from daemon@localhost) by scones.sup.scc.nl (8.9.3/8.9.3) id NAA26831 for stable@FreeBSD.ORG; Fri, 2 Jul 1999 13:28:44 +0200 (CEST) (envelope-from freebsd-stable@scc.nl) Received: from GATEWAY by scones.sup.scc.nl with netnews for stable@FreeBSD.ORG (stable@FreeBSD.ORG) To: stable@FreeBSD.ORG Date: Fri, 02 Jul 1999 13:28:39 +0200 From: Marcel Moolenaar Message-ID: <377CA267.7F64B97@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: Subject: Re: Linux emulation Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrij Korud wrote: > > Hi. > While trying to run PowerAlert plus for Linux on FreeBSD 3.2-STABLE box I > got a message: > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > Any ideas? Can you apply the following patch and tell me if it solves your problem without creating new problems? :-) Index: linux_ioctl.c =================================================================== RCS file: /home/ncvs/src/sys/i386/linux/linux_ioctl.c,v retrieving revision 1.33 diff -r1.33 linux_ioctl.c 599a600,612 > case LINUX_TIOCMGET: > args->cmd = TIOCMGET; > return ioctl(p, (struct ioctl_args *)args); > case LINUX_TIOCMBIS: > args->cmd = TIOCMBIS; > return ioctl(p, (struct ioctl_args *)args); > case LINUX_TIOCMBIC: > args->cmd = TIOCMBIC; > return ioctl(p, (struct ioctl_args *)args); > case LINUX_TIOCMSET: > args->cmd = TIOCMSET; > return ioctl(p, (struct ioctl_args *)args); > -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 6:44:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.equilibrate.net (ns2.equilibrate.net [193.173.72.3]) by hub.freebsd.org (Postfix) with ESMTP id 3914314D5D for ; Fri, 2 Jul 1999 06:44:52 -0700 (PDT) (envelope-from jascha@equilibrate.net) Received: from equilibrate.net (jascha@linux.equilibrate.net [193.173.72.25]) by smtp1.equilibrate.net (8.9.2/8.9.2/EQ_1.1) with ESMTP id PAA17347 for ; Fri, 2 Jul 1999 15:44:50 +0200 (CEST) Message-ID: <377CC24B.B95F60C3@equilibrate.net> Date: Fri, 02 Jul 1999 15:44:44 +0200 From: Jascha Hoogenraad Organization: Equilibrate Networking X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i686) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 6:52:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 5C7F114D5D for ; Fri, 2 Jul 1999 06:52:09 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id PAA18814; Fri, 2 Jul 1999 15:52:02 +0200 (CEST) (envelope-from des) To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: 3.2-RELEASE Feedback References: <19990626184311.A5290@ipass.net> From: Dag-Erling Smorgrav Date: 02 Jul 1999 15:52:01 +0200 In-Reply-To: Randall Hopper's message of "Sat, 26 Jun 1999 18:43:11 -0400" Message-ID: Lines: 108 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper writes: > 1) The graphical console screen saver is very nice! I'll pretend I'm not proud :) > 2) Where's the tcpdump port/package -- missing? Tcpdump is in the base system. No need to install a port or package. > 3) If I switch the console to 43 or 60 line mode with vidcontrol, "man" and > other full-screen progs don't automatically pick up the correct number > of lines like they did in 3.0-RELEASE. They assume 25-line mode. > > vidcontrol < /dev/ttyv0 -f 8x8 cp866-8x8 > vidcontrol < /dev/ttyv0 132x43 > vidcontrol < /dev/ttyv1 132x43 > vidcontrol < /dev/ttyv2 132x43 > > I have to fiddle with "stty rows" and hand the console the right number. No, no; just set your TERM variable rigth (cons43 or cons60). You can do this in /etc/ttys (replace cons25 with e.g. cons60) if you set these videomodes at boot time (with allscreen_flags). > 4) Arrrg! The Afterstep package has Penguin icons for xterms. > Where's Chuck?! (see attached) Contact the maintainer (cd /usr/ports/x11-wm/afterstep && grep MAINTAINER Makefile) > 6) I didn't find a man page for ld.so, despite what man page for ldd says > (this may be an artifact of the missing ld.so in compat22 on the German > FreeBSD CD I downloaded). Methinks this is a known bug that was fixed before the final release (the one that went to the CD press). > 7) wcd0 became acd0 in the kernel config file, but we still mount wcd0c. (?) > Is this an oversight? It's in the default fstab for example. No, it's called acd in the config file to avoid name conflicts, but it uses the same ol' major/minor. > 8) (Nit) Boot-up probes spelling error: > "bt_isa_probe: Probe failled for card at 0x330" I think that's been fixed. > 9) rc.firewall - if firewall_type is a file, it feeds each line in it to > ipfw. Yes, that's what it's meant to do. If you want to use a home-grown script, set firewall_script to something else than /etc/rc.firewall. > 10) There was no ports_update package in the packages dir when I downloaded. > I found a reference to this in DejaNews, and grabbed the /usr/ports/Mk > tree from ftp.freebsd.org. It worked, but what should users really be > doing? Cvsup the ports tree, perhaps? > 11) When copying directory trees between two IDE drives on the PCI > bus, the system really dogs down -- emacs takes 15 seconds to come up > when normally it takes 1 -- didn't do that on 3.0-RELEASE. Hmm, are you sure (that it didn't do that before)? Non-DMA IDE drives are CPU pigs. > 12) Why do we see lpt0 probes twice: > > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > > My kernel config for the new ppbus scheme: > device ppc0 at isa? port "0x3BC" tty irq 7 > device ppc1 at isa? port "0x378" tty > controller ppbus0 > device lpt0 at ppbus? > device lpt1 at ppbus? Why do you have two lpt lines? I think the lpt driver is autocloning. Remember that lpt isn't a real hardware device driver any more, just one of several ways of talking to the ppc device. > 13) 3.2-RELEASE still locks the system hard when a file system is mismounted, > just as 3.0-RELEASE did: Only for FAT filesystems. FAT sucks. > 15) /opt/bin/xanim.2.70.1 +Ze +B +CF4 +Av10 -geometry +100+100 fox.mov > ld.so failed: Can't find shared library "libgnumalloc.so.2.0" > > Something missing from the compat libs. I pulled it off my 3.0-R > partition on another disk. I don't think gnumalloc is meant to be in compat. It should have been installed when you installed xanim. > 16) So, how do I try a splash screen? Nothing in the FAQ or handbook > on the CD, and only "pseudo-device splash" in LINT. I've got it > in my kernel config, but no splash. Did you try 'man splash'? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 7:26:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.ucb.crimea.ua (relay.ucb.crimea.ua [212.110.138.1]) by hub.freebsd.org (Postfix) with ESMTP id F0FBA15234; Fri, 2 Jul 1999 07:24:59 -0700 (PDT) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id RAA77408; Fri, 2 Jul 1999 17:21:14 +0300 (EEST) (envelope-from ru) Date: Fri, 2 Jul 1999 17:21:14 +0300 From: Ruslan Ermilov To: Dag-Erling Smorgrav , "Jordan K. Hubbard" Cc: Randall Hopper , stable@freebsd.org Subject: Re: 3.2-RELEASE Feedback Message-ID: <19990702172114.A71410@relay.ucb.crimea.ua> Mail-Followup-To: Dag-Erling Smorgrav , "Jordan K. Hubbard" , Randall Hopper , stable@FreeBSD.ORG References: <19990626184311.A5290@ipass.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=nFreZHaLTZJo0R7j X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Jul 02, 1999 at 03:52:01PM +0200 X-Operating-System: FreeBSD 3.2-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii On Fri, Jul 02, 1999 at 03:52:01PM +0200, Dag-Erling Smorgrav wrote: > Randall Hopper writes: [...] > > 6) I didn't find a man page for ld.so, despite what man page for ldd says > > (this may be an artifact of the missing ld.so in compat22 on the German > > FreeBSD CD I downloaded). > > Methinks this is a known bug that was fixed before the final release > (the one that went to the CD press). > Hmm, src/libexec/rtld-elf/Makefile says "NOMAN=true" as of today. > > 7) wcd0 became acd0 in the kernel config file, but we still mount wcd0c. (?) > > Is this an oversight? It's in the default fstab for example. > > No, it's called acd in the config file to avoid name conflicts, but it > uses the same ol' major/minor. > It's sysinstall that puts `wcd' string into /etc/fstab. `wcd' devices are symlinked to `acd'. Patch is attached. Jordan? -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: devices.c =================================================================== RCS file: /usr/FreeBSD-CVS/src/release/sysinstall/devices.c,v retrieving revision 1.93 diff -u -r1.93 devices.c --- devices.c 1999/06/17 19:04:53 1.93 +++ devices.c 1999/07/02 14:12:19 @@ -66,7 +66,7 @@ { DEVICE_TYPE_CDROM, "mcd%da", "Mitsumi (old model) CDROM drive", 7, 0, 8, 4, 'b' }, { DEVICE_TYPE_CDROM, "scd%da", "Sony CDROM drive - CDU31/33A type", 16, 0, 8, 4, 'b' }, { DEVICE_TYPE_CDROM, "matcd%da", "Matsushita CDROM ('sound blaster' type)", 17, 0, 8, 4, 'b' }, - { DEVICE_TYPE_CDROM, "wcd%dc", "ATAPI IDE CDROM", 19, 2, 8, 4, 'b' }, + { DEVICE_TYPE_CDROM, "acd%dc", "ATAPI IDE CDROM", 19, 2, 8, 4, 'b' }, { DEVICE_TYPE_TAPE, "rsa%d", "SCSI tape drive", 14, 0, 16, 4, 'c' }, { DEVICE_TYPE_TAPE, "rwt%d", "Wangtek tape drive", 10, 0, 1, 4, 'c' }, { DEVICE_TYPE_DISK, "da%d", "SCSI disk device", 4, 65538, 8, 16, 'b' }, --nFreZHaLTZJo0R7j-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 9:32:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2]) by hub.freebsd.org (Postfix) with ESMTP id 6801514D8E for ; Fri, 2 Jul 1999 09:32:12 -0700 (PDT) (envelope-from jooji@webnology.com) Received: from localhost (jooji@localhost) by mercury.webnology.com (8.9.2/8.9.2) with SMTP id KAA05481 for ; Fri, 2 Jul 1999 10:34:08 -0500 (CDT) Date: Fri, 2 Jul 1999 10:34:07 -0500 (CDT) From: "Jasper O'Malley" To: stable@freebsd.org Subject: ARP Problem? Need confirmation... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone else confirm or refute the existence of the bug I reported in bin/12448? I can't publish ARP entries for Proxy ARP, and this has killed my FreeBSD 3.2-STABLE firewall box (cvsupped again on Tuesday, June 29). If anyone with a recently make worlded 3.2-STABLE box has a free second, please try to do the following: arp -s ip_address auto pub where ip_address is a free (currently unused) IP address on a subnet to which you have an Ethernet interface attached. What this *should* do is "publish" the IP address for Proxy ARP. What it does for me is print the error message: using interface ed1 for proxy with address 0:e0:29:32:21:ee arp: writing to routing socket: File exists It worked with 3.2-RELEASE code, and I'm probably going to downgrade the box today as a result, but it would be helpful if anyone has a clue what might have changed to cause the error, or even just to know if it's a problem with my box or with the 3.2-STABLE code. Cheers, Mick The Reverend Jasper P. O'Malley dotdot:jooji@webnology.com Systems Administrator ringring:asktheadmiral Webnology, LLC woowoo:http://www.webnology.com/~jooji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 14: 7: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id BD40D14E32 for ; Fri, 2 Jul 1999 14:07:02 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-5-183.dialup.rdu.ipass.net [209.170.134.183]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id RAA03567; Fri, 2 Jul 1999 17:06:58 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id RAA03841; Fri, 2 Jul 1999 17:08:54 -0400 (EDT) (envelope-from rhh) Date: Fri, 2 Jul 1999 17:08:54 -0400 From: Randall Hopper To: Dag-Erling Smorgrav Cc: stable@FreeBSD.ORG Subject: Re: 3.2-RELEASE Feedback Message-ID: <19990702170854.A2009@ipass.net> References: <19990626184311.A5290@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Dag-Erling Smorgrav on Fri, Jul 02, 1999 at 03:52:01PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |> 3) If I switch the console to 43 or 60 line mode with vidcontrol, "man" and |> other full-screen progs don't automatically pick up the correct number |> of lines like they did in 3.0-RELEASE. They assume 25-line mode. |> |> vidcontrol < /dev/ttyv0 -f 8x8 cp866-8x8 |> vidcontrol < /dev/ttyv0 132x43 |> vidcontrol < /dev/ttyv1 132x43 |> vidcontrol < /dev/ttyv2 132x43 |> |> I have to fiddle with "stty rows" and hand the console the right number. | |No, no; just set your TERM variable rigth (cons43 or cons60). You can |do this in /etc/ttys (replace cons25 with e.g. cons60) if you set |these videomodes at boot time (with allscreen_flags). I didn't want to have to do this -- as I didn't have to do it on 3.0-RELEASE. The terminal was smart enough to figure it out. Kazutaka YOKOTA committed a patch for this last week that fixed it up (in response to my kern/12420 PR). |> 11) When copying directory trees between two IDE drives on the PCI |> bus, the system really dogs down -- emacs takes 15 seconds to come up |> when normally it takes 1 -- didn't do that on 3.0-RELEASE. | |Hmm, are you sure (that it didn't do that before)? Non-DMA IDE drives |are CPU pigs. Yes, I'm sure. Oh, these are all DMA IDE drives. I've had them set up that way since 3.0-971208-SNAP. |> 12) Why do we see lpt0 probes twice: |> |> lpt0: on ppbus 0 |> lpt0: Interrupt-driven port |> lpt0: on ppbus 0 |> lpt0: Interrupt-driven port |> |> My kernel config for the new ppbus scheme: |> device ppc0 at isa? port "0x3BC" tty irq 7 |> device ppc1 at isa? port "0x378" tty |> controller ppbus0 |> device lpt0 at ppbus? |> device lpt1 at ppbus? | |Why do you have two lpt lines? On occasion, I've had two parallel ports in one machine. |I think the lpt driver is autocloning. Remember that lpt isn't a real |hardware device driver any more, just one of several ways of talking to |the ppc device. Hmm. I'm confused. /dev/lpt# is the physical device I point /etc/printcap printer entries too. So if I hook up two printers, one is lpt0 and the other is lpt1 AFAIK. Something is odd, because right now I only have one hardware parallel port installed. |> 13) 3.2-RELEASE still locks the system hard when a file system is |>mismounted, just as 3.0-RELEASE did: | |Only for FAT filesystems. FAT sucks. True, FAT isn't great, but this fatal FreeBSD bug has nothing to do with FAT sucking. |> 15) /opt/bin/xanim.2.70.1 +Ze +B +CF4 +Av10 -geometry +100+100 fox.mov |> ld.so failed: Can't find shared library "libgnumalloc.so.2.0" |> |> Something missing from the compat libs. I pulled it off my 3.0-R |> partition on another disk. | |I don't think gnumalloc is meant to be in compat. It should have been |installed when you installed xanim. Hmmm. It was on the 3.0-RELEASE CD: > cat bin.?? | tar -tzf - | grep gnumalloc.so.2 usr/lib/compat/aout/libgnumalloc.so.2.0 So I would have thought it should have been in bindist or a "compat30" binary distribution on the 3.2-RELEASE CD (since 3.x compatibility seems more important than 2.x). However, it's not there: > cat bin.?? | tar -tzf - | grep gnumalloc |> 16) So, how do I try a splash screen? Nothing in the FAQ or handbook |> on the CD, and only "pseudo-device splash" in LINT. I've got it |> in my kernel config, but no splash. | |Did you try 'man splash'? No, I didn't think it'd be that easy :-) Even after reading it though, I didn't get it going. It says you can run this from the loader prompt: load kernel load -t splash_image_data chuck.bmp load splash_bmp You can't (or I couldn't at least). "load kernel" goes off and does just that, never returning to the loader prompt. So thinking about patching loader.rc, I followed splash(4)'s directions and tried to consult the loader.rc(5) man page (to learn what to add where, what not to change, etc.). But there is no loader.rc man page. /boot/* sounds low-enough level that I didn't want to risk modifying it without knowing exactly what I was doing and the potential consequences (i.e. how much trouble was it going to be to recover from an error). I still didn't know enough at this point, so I never did get the splash screen going. Any tips? Thanks for the reply, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 16: 6:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from the.oneinsane.net (the.oneinsane.net [207.113.133.228]) by hub.freebsd.org (Postfix) with ESMTP id 8F90614E67; Fri, 2 Jul 1999 16:06:00 -0700 (PDT) (envelope-from insane@lunatic.oneinsane.net) Received: from lunatic.oneinsane.net (insane@lunatic.oneinsane.net [207.113.133.231]) by the.oneinsane.net (8.9.3/8.9.3) with ESMTP id QAA14853; Fri, 2 Jul 1999 16:05:59 -0700 (PDT) Received: (from insane@localhost) by lunatic.oneinsane.net (8.9.3/8.9.3) id QAA67212; Fri, 2 Jul 1999 16:05:58 -0700 (PDT) (envelope-from insane) Date: Fri, 2 Jul 1999 16:05:58 -0700 From: "Ron 'The InSaNe One' Rosson" To: Joao Carlos Cc: freebsd-ipfw@freebsd.org, freebsd-stable@freebsd.org Subject: Re: NATD/VPN using -pptpalias Message-ID: <19990702160558.A66717@lunatic.oneinsane.net> Reply-To: Ron Rosson References: <19990701164347.B22149@lunatic.oneinsane.net> <000901bec4d8$1f12fa30$0400a8c0@bahianet.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <000901bec4d8$1f12fa30$0400a8c0@bahianet.com.br>; from Joao Carlos on Fri, Jul 02, 1999 at 07:13:31PM -0300 X-Operating-System: FreeBSD lunatic.oneinsane.net 3.2-STABLE X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane-pgp5i.txt X-Uptime: 4:04PM up 1 day, 16:01, 4 users, load averages: 0.03, 0.05, 0.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Still no solution that works. I am still seeing if anyone else has any ideas. I have not given up. I am lucky to have an understandable client. TIA On Fri, 02 Jul 1999, Joao Carlos was heard blurting out: > Hi, io have the same problem as you and would like to know if you have > solved this. If yes, how did you do that??? > > Thanks in advance > > Joao Carlos > jcarlos@bahianet.com.br > > > > ----- Original Message ----- > From: Ron 'The InSaNe One' Rosson > To: > Cc: > Sent: Thursday, July 01, 1999 8:43 PM > Subject: NATD/VPN using -pptpalias > > > > I am tring to get a FreeBSD 3.2-STABLE as of Last week to pass a VPN > connection > > from a client behind the NATD box to a Server out on the internet. At this > time > > I am getting erro, timeout exceeded while waiting for reply. > > > > excerpt from rc.conf > > natd_enable="YES" > > natd_interface="ed0" > > natd_flags="-pptpalias 192.168.2.7" > > > > excerpt from rc.firewall > > if [ "X${natd_enable}" = X"YES" -a "X${natd_interface}" != X"" ]; then > > $fwcmd add divert natd all from any to any via ${natd_interface} > > fi > > > > edo is the line out to my cable modem and ed1 goes for my private network > using > > addresses <192.168.x.x> > > > > If someone has this working I would be greatful to see how you did it. -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was null and void ------------------------------------------------------------------- Stress is waking up screaming and you realize you haven't fallen asleep yet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 17:29:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from yamuna.dalai-nor.de (yamuna.dalai-nor.de [194.231.227.71]) by hub.freebsd.org (Postfix) with ESMTP id 75EAD14D37 for ; Fri, 2 Jul 1999 17:29:44 -0700 (PDT) (envelope-from pruess@yamuna.dalai-nor.de) Received: (from pruess@localhost) by yamuna.dalai-nor.de (8.8.7/8.8.5) id CAA21227; Sat, 3 Jul 1999 02:29:43 +0200 (CEST) Message-Id: <199907030029.CAA21227@yamuna.dalai-nor.de> Subject: double fault in 3.[12]-RELEASE and 19990630-STABLE To: freebsd-stable@freebsd.org Date: Sat, 3 Jul 1999 02:29:43 +0200 (CEST) Cc: pruess@yamuna.dalai-nor.de (G P) From: "G.P." Reply-To: G.P@chatcity.de X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'm using the following system: P2BLS 450-PII 512 MB ECC-RAM Adaptec 2940 UW AGP Hercules In 3.2-RELEASE and also in 19990630-SNAP I am able to produce a panic: double fault using the kernel from the GENERIC-conffile with maxusers set to 512 and trying to fork() as much processes as possible. As far as I know, this panic kills the stacks and thus it is no wonder, that I could never get any helpfull information from dumps. Maybe I am not sufficiently familiar with (k)gdb. In 3.1-RELEASE I had to change Makfile.i386, kernel.script and pmap.h to ask the kernel to use the whole memory. The behavior (panic) keeps the same. Any suggestions? Thanks in advance, Gunnar -- ###################################################### # # # "5.6 Die Grenzen meiner Sprache bedeuten die # # Grenzen meiner Welt." # # # # -- Ludwig Wittgenstein # ###################################################### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 20:30:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id B61B514F26 for ; Fri, 2 Jul 1999 20:30:30 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id WAA57312; Fri, 2 Jul 1999 22:30:23 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 2 Jul 1999 22:30:23 -0500 (CDT) From: Chris Dillon To: Marcel Moolenaar Cc: stable@FreeBSD.ORG Subject: Re: Linux emulation In-Reply-To: <377CA267.7F64B97@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 2 Jul 1999, Marcel Moolenaar wrote: > Andrij Korud wrote: > > > > Hi. > > While trying to run PowerAlert plus for Linux on FreeBSD 3.2-STABLE box I > > got a message: > > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > > Any ideas? > > Can you apply the following patch and tell me if it solves your problem > without creating new problems? :-) > > Index: linux_ioctl.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/linux/linux_ioctl.c,v > retrieving revision 1.33 > diff -r1.33 linux_ioctl.c > 599a600,612 > > case LINUX_TIOCMGET: > > args->cmd = TIOCMGET; > > return ioctl(p, (struct ioctl_args *)args); > > case LINUX_TIOCMBIS: > > args->cmd = TIOCMBIS; > > return ioctl(p, (struct ioctl_args *)args); > > case LINUX_TIOCMBIC: > > args->cmd = TIOCMBIC; > > return ioctl(p, (struct ioctl_args *)args); > > case LINUX_TIOCMSET: > > args->cmd = TIOCMSET; > > return ioctl(p, (struct ioctl_args *)args); > > I just tried this patch on my server and it does the job, almost. There is no "unsupported ioctl" error message, but the daemon can't communicate with the UPS _unless_ I frob the port with tip(1) while the daemon is running. The exact moment that I tip the serial port, the daemon comes alive and tells me UPS communications were established and its happy. tip(1) isn't able to actually talk to the UPS, though it doesn't give me any errors of any kind, and I just ~. to exit out. This would be acceptable if I could find an automated way of frobbing the serial port so that the daemon works. :-) BTW, I haven't tested to see if this breaks Linux emulation in any other way, since that is the only thing I'm using it for on that machine. I may take PowerAlert home and play with it there and see if the X client works under emulation, too. Here are the patches I have so far to make it install and work fairly cleanly under FreeBSD. Yes, the patches are quite "hackey", but that's all you're gonna get without a rewrite of all the scripts to be more portable or just plain BSD-aware (there are only provisions for SysV-style startup scripts). The one bit where I changed a "no_nl_echo" to a printf was purely cosmetic so that things looked right on system startup. --- pap_inst.orig Tue Jun 29 15:27:23 1999 +++ pap_inst Fri Jul 2 20:55:30 1999 @@ -268,6 +268,7 @@ echo " 7) Silicon Graphics IRIX" echo " 8) Digital UNIX" echo " 9) Linux" + echo " 10) FreeBSD/i386 [uses Linux binaries under emulation]" echo @@ -314,6 +315,10 @@ break ;; + 10) TARGET_SYSTEM=FREEBSD_I386 + break + ;; + *) echo echo "Please respond with a number corresponding to the above selections" echo @@ -379,6 +384,14 @@ TARGET_SYSTEM=LINUX ;; +FreeBSD) + case "`uname -m`" in + i386) + TARGET_SYSTEM=FREEBSD_I386 + ;; + esac + ;; + esac @@ -429,6 +442,10 @@ echo "Your system appears to be running Linux." ;; + FREEBSD_I386) + echo "Your system appears to be running FreeBSD/i386." + ;; + esac echo @@ -603,6 +620,37 @@ FILES_THAT_SHOULD_BE_REMOVED="$RC0_K_FILE $RC2_S_FILE $RC2_K_FILE $RC3_S_FILE $RC3_K_FILE $RC5_S_FILE $RC5_K_FILE $PAPLUS_CMD_DIR/pap" ;; + +FREEBSD_I386) + + SYSTEM="FreeBSD/i386" + + PAP_OS="FREEBSD_I386" + + RC2_DIR="/usr/local/etc/rc.d" + + RC2_S_FILE="$RC2_DIR/paplus.sh" + + PAPLUS_CMD_DIR="/usr/local/sbin" + + DEFAULT_UPS_COMM_PORT="/dev/cuaa0" + + DEFAULT_INSTALLATION_DIR="/usr/local/paplus" + + DEFAULT_LOGGING_DIR="/var/log/paplus" + + PAPLUS_INPUT_FILE_LOWER="$CDROM_DIR/linux.pap" + PAPLUS_INPUT_FILE_LOWER_EXT="$CDROM_DIR/linux.pap;1" + PAPLUS_INPUT_FILE_UPPER="$CDROM_DIR/LINUX.PAP" + PAPLUS_INPUT_FILE_UPPER_EXT="$CDROM_DIR/LINUX.PAP;1" + + CPIO_FLAGS="icdumB" + + BROADCAST_COMMAND="/usr/bin/wall" + + FILES_THAT_SHOULD_BE_REMOVED="$RC0_K_FILE $RC2_S_FILE $RC2_K_FILE $RC3_S_FILE $RC3_K_FILE $RC5_S_FILE $RC5_K_FILE $PAPLUS_CMD_DIR/pap" + ;; + DEC_UNIX) --- pap.orig Fri Jul 2 21:19:53 1999 +++ pap Fri Jul 2 21:20:43 1999 @@ -59,7 +59,7 @@ fi # Linux uses modified bsd ps command line args, but no '-' -if [ $TRIPPLITE_PAP_OS = LINUX ] +if [ $TRIPPLITE_PAP_OS = LINUX -o $TRIPPLITE_PAP_OS = FREEBSD_I386 ] then PS="ps ax " else @@ -102,7 +102,7 @@ fi done - no_nl_echo "PowerAlert Plus startup: " + printf "\nPowerAlert Plus startup: " if [ -x "$PAP_HOME/bin/pap_upsd" ] then --- /usr/local/paplus/bin/pap_shutdown Wed Mar 24 11:07:13 1999 +++ pap_shutdown Fri Jul 2 20:51:35 1999 @@ -40,7 +40,7 @@ exec shutdown -g0 -y ;; -LINUX) +LINUX|FREEBSD_I386) exec shutdown -h now ;; esac -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 21:46:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id EE0A915060 for ; Fri, 2 Jul 1999 21:45:31 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (422 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Fri, 2 Jul 1999 21:45:31 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Fri, 2 Jul 1999 21:45:31 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: Mail not inserting From: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -STABLE of two days ago. any clues why /usr/bin/Mail would not be inserting a From: line? very similar system has no problem in -CURRENT. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 21:57:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (Postfix) with ESMTP id 0AF0D14BB8; Fri, 2 Jul 1999 21:57:28 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.3/8.9.3) with ESMTP id IAA19340; Sat, 3 Jul 1999 08:57:25 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (minas-tirith.pol.ru [127.0.0.1]) by shuttle.svib.ru (8.9.3/8.8.8) with ESMTP id JAA31071; Sat, 3 Jul 1999 09:01:15 +0400 (MSD) (envelope-from tarkhil@shuttle.svib.ru) Message-Id: <199907030501.JAA31071@shuttle.svib.ru> X-Mailer: exmh version 2.0.3 To: John Polstra Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Soft-updates feedback In-reply-to: Your message "Wed, 30 Jun 1999 18:54:23 PDT." Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Jul 1999 09:01:14 +0400 From: Alex Povolotsky Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG About a week ago, I've posted a message here and didn't got positive replies. The problem is: when I use soft-updates on IDE disks (disk on primary master, disk on secondary master, CD on primary slave), any active disk-using program (starting Netscape, starting EXMH) causes all other programs literally to stop for several seconds (well, 20-30 seconds is quite often!). Turning soft-updates off causes this nastiness to disappear, but also slows down disk-active processess. Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 22:25:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9389A14C7F; Fri, 2 Jul 1999 22:25:21 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA01914; Fri, 2 Jul 1999 22:25:11 -0700 Date: Fri, 2 Jul 1999 22:24:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alex Povolotsky Cc: John Polstra , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: Soft-updates feedback In-Reply-To: <199907030501.JAA31071@shuttle.svib.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while this is happening, what does 'iostat 1' and 'vmstat 1' tell you? On Sat, 3 Jul 1999, Alex Povolotsky wrote: > About a week ago, I've posted a message here and didn't got positive replies. > > The problem is: > > when I use soft-updates on IDE disks (disk on primary master, disk on > secondary master, CD on primary slave), any active disk-using program > (starting Netscape, starting EXMH) causes all other programs literally to stop > for several seconds (well, 20-30 seconds is quite often!). Turning > soft-updates off causes this nastiness to disappear, but also slows down > disk-active processess. > > Alex. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 22:28:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0053414C7F; Fri, 2 Jul 1999 22:28:26 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id WAA19233; Fri, 2 Jul 1999 22:28:18 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id WAA00889; Fri, 2 Jul 1999 22:28:18 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 02 Jul 1999 22:28:18 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Matthew Jacob Subject: Re: Soft-updates feedback Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG, Alex Povolotsky Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know why I'm on the cc for this thread, but please remove me. And it shouldn't be cross-posted to 2 lists. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Jul 2 23:40: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 0832F14C03 for ; Fri, 2 Jul 1999 23:39:55 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from scones.sup.scc.nl (i459.ztm.euronet.nl [194.134.67.180]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id IAA14177; Sat, 3 Jul 1999 08:39:53 +0200 (MET DST) Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id IAA69472; Sat, 3 Jul 1999 08:39:50 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <377DB035.7EE9AF75@scc.nl> Date: Sat, 03 Jul 1999 08:39:49 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Chris Dillon Cc: stable@FreeBSD.ORG Subject: Re: Linux emulation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] > > Andrij Korud wrote: > > > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" [snip] > I wrote: > > Can you apply the following patch and tell me if it solves your problem > > without creating new problems? :-) [snip] Chris Dillon wrote: > I just tried this patch on my server and it does the job, almost. > There is no "unsupported ioctl" error message, but the daemon can't > communicate with the UPS _unless_ I frob the port with tip(1) while > the daemon is running. The exact moment that I tip the serial port, > the daemon comes alive and tells me UPS communications were > established and its happy. tip(1) isn't able to actually talk to the > UPS, though it doesn't give me any errors of any kind, and I just ~. > to exit out. This would be acceptable if I could find an automated > way of frobbing the serial port so that the daemon works. :-) I figured something like that would do the trick. A ktrace showed that read(2) on the com-port returns -1 with errno set to -11. Everything else seemed to work. Can you tell us what kind of frobbing you did? Maybe there's a bug somewhere in the TCGETS/TCSETS iotcls (these are used right after the TIOCMBIC ioctl). In the mean time I prepare the patch for being committed. As for automated frobbing :-) Maybe it helps to initialize the device at boot-time. See /etc/rc.serial > BTW, I haven't tested to see if this breaks Linux emulation in any > other way, since that is the only thing I'm using it for on that > machine. I may take PowerAlert home and play with it there and see if > the X client works under emulation, too. The only breakage I expect is when using one of the ioctls. So you don't have to worry about any other kind of breakage. > Here are the patches I have so far to make it install and work fairly > cleanly under FreeBSD. Yes, the patches are quite "hackey", but > that's all you're gonna get without a rewrite of all the scripts to be > more portable or just plain BSD-aware (there are only provisions for > SysV-style startup scripts). The one bit where I changed a > "no_nl_echo" to a printf was purely cosmetic so that things looked > right on system startup. [snip] I have my uname patch applied by default, which means that uname returns "Linux" by default. When you run the pap_inst script in a Linux sh, it all works out of the box. Changing the defaults and directories in the script to match a FreeBSD environment is something which would be nice in case of a real port though (hint :-) Thanks for the feedback! -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 0:14:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34]) by hub.freebsd.org (Postfix) with ESMTP id DCCCD1507B for ; Sat, 3 Jul 1999 00:14:00 -0700 (PDT) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.8.7/8.8.7) id RAA32275 for ; Sat, 3 Jul 1999 17:17:07 +1000 Received: from tar-56k-208.tpgi.com.au(203.26.26.208), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpda32184; Sat Jul 3 17:16:53 1999 Message-ID: <377DB824.AC6F1C54@tpgi.com.au> Date: Sat, 03 Jul 1999 17:13:40 +1000 From: Eddie Irvine X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: Re: 3.2-RELEASE Feedback References: <19990626184311.A5290@ipass.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just installed 3.2 on a couple of workstations from the CD-Roms, and I noticed that the default router in /etc/rc.conf was set to "NO". However, I doubt that I'd make the same mistake twice. I do have a default router on my network, and I did type it's IP address in. If I had half a day to spare I'd reinstall the whole thing and make certain. Anyone else noticed this? BTW - the TCP extensions line in /etc/rc.conf is perplexing. I presume I *should* have the extensions on in most cases, so this should be set to "YES" ? -- Eddie http://www1.tpgi.com.au/users/eirvine/index.html ________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 2:28:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C22CE14C81 for ; Sat, 3 Jul 1999 02:28:09 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA47695; Sat, 3 Jul 1999 11:28:05 +0200 (CEST) (envelope-from des) To: Randall Hopper Cc: Dag-Erling Smorgrav , stable@FreeBSD.ORG Subject: Re: 3.2-RELEASE Feedback References: <19990626184311.A5290@ipass.net> <19990702170854.A2009@ipass.net> From: Dag-Erling Smorgrav Date: 03 Jul 1999 11:28:04 +0200 In-Reply-To: Randall Hopper's message of "Fri, 2 Jul 1999 17:08:54 -0400" Message-ID: Lines: 40 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper writes: > Even after reading it though, I didn't get it going. It says you can run > this from the loader prompt: > > load kernel > load -t splash_image_data chuck.bmp > load splash_bmp > > You can't (or I couldn't at least). "load kernel" goes off and does just > that, never returning to the loader prompt. So thinking about patching > loader.rc, I followed splash(4)'s directions and tried to consult the > loader.rc(5) man page (to learn what to add where, what not to change, > etc.). But there is no loader.rc man page. There is a loader(8) man page. 'load kernel' loads the kernel in memory. It does not boot the kernel. 'boot' and 'autoboot' do that. > /boot/* sounds low-enough level that I didn't want to risk modifying it > without knowing exactly what I was doing and the potential consequences > (i.e. how much trouble was it going to be to recover from an error). I > still didn't know enough at this point, so I never did get the splash > screen going. > > Any tips? Put the following in /etc/loader.rc: load kernel load -t splash_image_data chuck.bmp load splash_bmp autoboot 5 (If you want to use a PCX image instead of BMP, just replace splash_bmp with splash_pcx. It has a smaller footprint.) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 8:22: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tranq1.tranquility.net (tranq1.tranquility.net [206.156.230.1]) by hub.freebsd.org (Postfix) with ESMTP id 3D67E14D92 for ; Sat, 3 Jul 1999 08:21:53 -0700 (PDT) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu (stephen.tranquility.net [206.156.230.78]) by tranq1.tranquility.net (8.9.2/8.9.2) with ESMTP id KAA22096 for ; Sat, 3 Jul 1999 10:21:50 -0500 (CDT) Message-ID: <377E2A8D.38A9F7EC@math.missouri.edu> Date: Sat, 03 Jul 1999 10:21:49 -0500 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.2-STABLE i386) MIME-Version: 1.0 To: stable@freebsd.org Subject: make -DCLOBBER installworld References: <19990626184311.A5290@ipass.net> <19990702170854.A2009@ipass.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was having problems with makig the port of super, and it turned out to be that I had old include files left over from earlier versions of FreeBSD (in particular /usr/include/prot.h). At the advice of the maintainer of super, I added -DCLOBBER when I did my next make world. Actually I did it with make installworld, as I always do it in two stages. But it didn't remove the old include files. Any ideas? -- Stephen Montgomery-Smith stephen@math.missouri.edu 307 Math Science Building stephen@showme.missouri.edu Department of Mathematics stephen@missouri.edu University of Missouri-Columbia Columbia, MO 65211 USA Phone (573) 882 4540 Fax (573) 882 1869 http://math.missouri.edu/~stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 9:33: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.freegaypix.com (www.freegaypix.com [216.65.3.226]) by hub.freebsd.org (Postfix) with ESMTP id 1802B14BE4 for ; Sat, 3 Jul 1999 09:32:58 -0700 (PDT) (envelope-from webmaster@jmsinternet.com) Received: from jason-s-pc (we-24-30-100-131.we.mediaone.net [24.30.100.131]) by jason.freegaypix.com (8.9.2/8.9.2) with SMTP id JAA83639 for ; Sat, 3 Jul 1999 09:35:20 -0700 (PDT) (envelope-from webmaster@jmsinternet.com) Message-Id: <4.1.19990703093016.00ceb180@mail.sirius.com> X-Sender: jms@mail.jmsinternet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 03 Jul 1999 09:30:55 -0700 To: freebsd-stable@FreeBSD.ORG From: JMS Internet Subject: Server Slowdown Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been experiencing slow download times with my co-located server... After changing out my HD, network card, and adding memory I have not seen much improvement at all. But, after adjusting different Apache settings (max users, max keep alives, etc.) I have noticed a change of approximately 600kbps of transfer higher then my original settings. What I would like to know is if anyone has experienced these types of problems, or if anyone is willing to give me advice on httpd.conf fine tuning. My server currently transfers approximately 30 gigs a day, and is only using approximately 30% of it's allocated line. Any help or advice is greatly appreciated... I have no idea where to turn at this point.. Thanks guys... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 9:46:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 3CA1A14C02 for ; Sat, 3 Jul 1999 09:46:45 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA16491; Sat, 3 Jul 1999 12:51:50 -0400 (EDT) Date: Sat, 3 Jul 1999 11:51:48 -0500 (EST) From: Alfred Perlstein To: JMS Internet Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Server Slowdown In-Reply-To: <4.1.19990703093016.00ceb180@mail.sirius.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, JMS Internet wrote: > I have been experiencing slow download times with my co-located server... > After changing out my HD, network card, and adding memory I have not seen much > improvement at all. But, after adjusting different Apache settings (max > users, max keep > alives, etc.) I have noticed a change of approximately 600kbps of transfer > higher then > my original settings. What I would like to know is if anyone has > experienced these types > of problems, or if anyone is willing to give me advice on httpd.conf fine > tuning. My server > currently transfers approximately 30 gigs a day, and is only using > approximately 30% of > it's allocated line. Any help or advice is greatly appreciated... I have > no idea where to turn > at this point.. 30 gigs a day is pretty nice, but i'm sure we can do better. :) More helpful would be : the exact configuration (ram, netcard, cpu, disks) a snapshot or two from "top" and "systat -vmstat" what is your current peak transfer rate? are you sure there is more than 30gigs/day demanded? -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] systems administrator and programmer Win Telecom - http://www.wintelcom.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 9:53:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 4B4D614EF6 for ; Sat, 3 Jul 1999 09:53:36 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id JAA04310; Sat, 3 Jul 1999 09:53:32 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <377E400B.C9205B83@gorean.org> Date: Sat, 03 Jul 1999 09:53:31 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Stephen Montgomery-Smith Cc: stable@freebsd.org Subject: Re: make -DCLOBBER installworld References: <19990626184311.A5290@ipass.net> <19990702170854.A2009@ipass.net> <377E2A8D.38A9F7EC@math.missouri.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen Montgomery-Smith wrote: > > I was having problems with makig the port of super, and it turned > out to be that I had old include files left over from earlier versions > of FreeBSD (in particular /usr/include/prot.h). > > At the advice of the maintainer of super, I added -DCLOBBER when I did > my next make world. Actually I did it with make installworld, as I > always do it in two stages. > > But it didn't remove the old include files. > > Any ideas? That confused me for a long time too. The -DCLOBBER isn't taken into account when you do make world. You have to do 'make -DCLOBBER includes' to get it to do what you want. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 9:57:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.freegaypix.com (www.freegaypix.com [216.65.3.226]) by hub.freebsd.org (Postfix) with ESMTP id 5AF8B14EF6 for ; Sat, 3 Jul 1999 09:55:13 -0700 (PDT) (envelope-from webmaster@jmsinternet.com) Received: from jason-s-pc (we-24-30-100-131.we.mediaone.net [24.30.100.131]) by jason.freegaypix.com (8.9.2/8.9.2) with SMTP id JAA90112; Sat, 3 Jul 1999 09:57:36 -0700 (PDT) (envelope-from webmaster@jmsinternet.com) Message-Id: <4.1.19990703094749.00abc430@mail.sirius.com> X-Sender: jms@mail.jmsinternet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 03 Jul 1999 09:53:09 -0700 To: Alfred Perlstein From: JMS Internet Subject: Re: Server Slowdown Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: References: <4.1.19990703093016.00ceb180@mail.sirius.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is some more information about my system: Intel PII 350, 384 Megs of RAM, 2 Multi-Gig hard drives (neither at capacity). My co-location company and myself know that there is more transfer trying to get through because we see it hitting a "roof" on it's transfer at about 3200kbps, and it won't go past that, and there is no steady up and downs, it's flat lining at that type of transfer, so we know something is wrong, and speed for transfers is VERY slow... I ran a test at netmechanic.com, and it rated it as "poor". A site to look at for yourself would be www.sitepalace.com. Thanks for your help... Here is the information requested below: FROM TOP: last pid: 89067; load averages: 0.62, 0.81, 0.75 up 3+21:40:19 09:53:38 279 processes: 1 running, 272 sleeping, 6 zombie CPU states: 7.8% user, 0.0% nice, 8.2% system, 6.2% interrupt, 77.8% idle Mem: 77M Active, 239M Inact, 45M Wired, 12M Cache, 8346K Buf, 1292K Free Swap: 522M Total, 13M Used, 508M Free, 3% Inuse FROM SYSTAT: 1 users Load 0.76 0.86 0.76 Sat Jul 3 09:52 Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER Tot Share Tot Share Free in out in out Act 60648 724 141864 860 16868 count All 382964 1784 3282820 2264 pages 145 cow Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt 73 zfod 1389 total 3 241 171 346 2554 1389 71 340 46028 wire 100 clk0 irq0 76484 act 128 rtc0 irq8 7.1%Sys 13.7%Intr 4.2%User 0.0%Nice 75.0%Idl 243456 inact 343 pci irq11 | | | | | | | | | | 15360 cache fdc0 irq6 ====++++++>>- 1508 free 818 wdc0 irq14 daefr wdc1 irq15 Namei Name-cache Dir-cache prcfr atkbd0 irq Calls hits % hits % react 14218 14183 100 6 0 pdwake pdpgs Discs fd0 wd0 wd1 intrn KB/t 0.00 8.94 0.00 8348 buf tps 0 46 0 29649 desiredvnodes MB/s 0.00 0.40 0.00 20442 numvnodes 4759 freevnodes At 11:51 AM 7/3/99 -0500, Alfred Perlstein wrote: >On Sat, 3 Jul 1999, JMS Internet wrote: > >> I have been experiencing slow download times with my co-located server... >> After changing out my HD, network card, and adding memory I have not seen >much >> improvement at all. But, after adjusting different Apache settings (max >> users, max keep >> alives, etc.) I have noticed a change of approximately 600kbps of transfer >> higher then >> my original settings. What I would like to know is if anyone has >> experienced these types >> of problems, or if anyone is willing to give me advice on httpd.conf fine >> tuning. My server >> currently transfers approximately 30 gigs a day, and is only using >> approximately 30% of >> it's allocated line. Any help or advice is greatly appreciated... I have >> no idea where to turn >> at this point.. > >30 gigs a day is pretty nice, but i'm sure we can do better. :) > >More helpful would be : > >the exact configuration (ram, netcard, cpu, disks) >a snapshot or two from "top" and "systat -vmstat" >what is your current peak transfer rate? >are you sure there is more than 30gigs/day demanded? > >-Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] >systems administrator and programmer > Win Telecom - http://www.wintelcom.net/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 10:20:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 026E614E43 for ; Sat, 3 Jul 1999 10:20:39 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-117.dialup.rdu.ipass.net [209.170.132.117]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id NAA26443; Sat, 3 Jul 1999 13:20:35 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id NAA01294; Sat, 3 Jul 1999 13:22:32 -0400 (EDT) (envelope-from rhh) Date: Sat, 3 Jul 1999 13:22:32 -0400 From: Randall Hopper To: Dag-Erling Smorgrav Cc: Jim Mock , stable@FreeBSD.ORG Subject: Splash Screens (was Re: 3.2-RELEASE Feedback) Message-ID: <19990703132232.A862@ipass.net> References: <19990626184311.A5290@ipass.net> <19990702170854.A2009@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Dag-Erling Smorgrav on Sat, Jul 03, 1999 at 11:28:04AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I didn't know what to do with: include /boot/loader.4th start which were already in this file, so I commented them out. I was lucky. It works just fine, even with VESA mode. So I went splash shopping. The pics on: http://advocacy.freebsd.org/ammunition/splash.html are nice, but I found I preferred the logo at the top of the page the best. Just snipped "The" and "ADVOCACY PROJECT", added a white background, and it's a perfect VESA splash. Thanks to Jim Mock who cooked this pic. One more question. The VESA module: what mode does it decide to switch to? Does it pick the first 8bpp palettized VESA mode registered which is bigger than the pic? Will it switch up to modes like 1280x1024, if registered with VESA? Just curious. Thanks for your help, Randall Dag-Erling Smorgrav: | |Put the following in /etc/loader.rc: | |load kernel |load -t splash_image_data chuck.bmp |load splash_bmp |autoboot 5 | |(If you want to use a PCX image instead of BMP, just replace |splash_bmp with splash_pcx. It has a smaller footprint.) | |Randall Hopper writes: |> Even after reading it though, I didn't get it going. It says you can run |> this from the loader prompt: |> |> load kernel |> load -t splash_image_data chuck.bmp |> load splash_bmp |> |> You can't (or I couldn't at least). "load kernel" goes off and does just |> that, never returning to the loader prompt. So thinking about patching |> loader.rc, I followed splash(4)'s directions and tried to consult the |> loader.rc(5) man page (to learn what to add where, what not to change, |> etc.). But there is no loader.rc man page. | |There is a loader(8) man page. | |'load kernel' loads the kernel in memory. It does not boot the kernel. |'boot' and 'autoboot' do that. | |> /boot/* sounds low-enough level that I didn't want to risk modifying it |> without knowing exactly what I was doing and the potential consequences |> (i.e. how much trouble was it going to be to recover from an error). I |> still didn't know enough at this point, so I never did get the splash |> screen going. |> |> Any tips? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 10:59: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 3647D1509D for ; Sat, 3 Jul 1999 10:58:51 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id TAA58933; Sat, 3 Jul 1999 19:58:47 +0200 (CEST) (envelope-from des) To: Randall Hopper Cc: Dag-Erling Smorgrav , Jim Mock , stable@FreeBSD.ORG Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback) References: <19990626184311.A5290@ipass.net> <19990702170854.A2009@ipass.net> <19990703132232.A862@ipass.net> From: Dag-Erling Smorgrav Date: 03 Jul 1999 19:58:47 +0200 In-Reply-To: Randall Hopper's message of "Sat, 3 Jul 1999 13:22:32 -0400" Message-ID: Lines: 38 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper writes: > Ok, I didn't know what to do with: > > include /boot/loader.4th > start > > which were already in this file, so I commented them out. I was lucky. They're not much use unless you want to use loader.conf (loader.4th reads loader.conf and does magic stuff as directed by variables defined there, much like /etc/rc does magic stuff as directed by /etc/rc.conf) > So I went splash shopping. I use the Saturn pics myself, though for some mysterious reason they're not on the advocacy site. They're by far the best splash screens I've seen, as they were designed specifically for that purpose (rather than just being *adapted* to that purpose). I think they're on John Baldwin's site (there's a link from the advocacy page), but I can't get through to it right now so I can't check. > One more question. The VESA module: what mode does it decide to switch to? > Does it pick the first 8bpp palettized VESA mode registered which is bigger > than the pic? Will it switch up to modes like 1280x1024, if registered > with VESA? Just curious. The VESA module doesn't switch to anything or make any decisions. The splash decoders behave slightly differently: the BMP decoder picks the largest available mode (1024x768, 800x600, 640x480, 320x200) while the PCX decoder picks the smallest available mode which is large enough to accomodate the picture. (I want the BMP decoder to go away, but it seems to be too well-anchored for that right now, though it suffers from slight bitrot because I don't maintain it actively) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 11:16:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id A4AFA150F3 for ; Sat, 3 Jul 1999 11:16:15 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-234.dialup.rdu.ipass.net [209.170.132.234]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id OAA01535; Sat, 3 Jul 1999 14:16:10 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id OAA02215; Sat, 3 Jul 1999 14:18:08 -0400 (EDT) (envelope-from rhh) Date: Sat, 3 Jul 1999 14:18:08 -0400 From: Randall Hopper To: Dag-Erling Smorgrav Cc: stable@FreeBSD.ORG Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback) Message-ID: <19990703141808.A2060@ipass.net> References: <19990626184311.A5290@ipass.net> <19990702170854.A2009@ipass.net> <19990703132232.A862@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Dag-Erling Smorgrav on Sat, Jul 03, 1999 at 07:58:47PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav: |> So I went splash shopping. | |I use the Saturn pics myself, though for some mysterious reason |they're not on the advocacy site. They're by far the best splash |screens I've seen, as they were designed specifically for that purpose |(rather than just being *adapted* to that purpose). I think they're on |John Baldwin's site (there's a link from the advocacy page), but I |can't get through to it right now so I can't check. Good to know. I'd tried it earlier but wrote it off when I couldn't connect: http://www.baldwin.cx/splash/ But based on your input, I'll keep checking it. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 12:22:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lazlo.internal.steam.com (lazlo.steam.com [199.108.84.37]) by hub.freebsd.org (Postfix) with ESMTP id C972314FA8 for ; Sat, 3 Jul 1999 12:22:38 -0700 (PDT) (envelope-from cliff@steam.com) Received: from lazlo.internal.steam.com (cliff@lazlo.internal.steam.com [192.168.32.2]) by lazlo.internal.steam.com (8.9.3/8.9.3) with ESMTP id MAA23316; Sat, 3 Jul 1999 12:24:06 -0700 (PDT) Date: Sat, 3 Jul 1999 12:24:06 -0700 (PDT) From: Cliff Skolnick X-Sender: cliff@lazlo.internal.steam.com To: JMS Internet Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Server Slowdown In-Reply-To: <4.1.19990703093016.00ceb180@mail.sirius.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG http://www.apache.org/docs/misc/perf-tuning.html -and- http://www.apache.org/docs/misc/perf.html are good resources. I am just wondering if your maxclient setting is too high. It is the most common performance problem I see. People think more is better, when really you want to avoid having httpd's start the system paging all on their own. Look at the RSS of the child, divide size of memory minus like 16M or so by that number. Start there and tune away. Cliff On Sat, 3 Jul 1999, JMS Internet wrote: > I have been experiencing slow download times with my co-located server... > After changing out my HD, network card, and adding memory I have not seen much > improvement at all. But, after adjusting different Apache settings (max > users, max keep > alives, etc.) I have noticed a change of approximately 600kbps of transfer > higher then > my original settings. What I would like to know is if anyone has > experienced these types > of problems, or if anyone is willing to give me advice on httpd.conf fine > tuning. My server > currently transfers approximately 30 gigs a day, and is only using > approximately 30% of > it's allocated line. Any help or advice is greatly appreciated... I have > no idea where to turn > at this point.. > > > Thanks guys... > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Cliff Skolnick | "They that can give up essential liberty to obtain Steam Tunnel Operations | a little temporary safety deserve neither liberty cliff@steam.com | nor safety." http://www.steam.com/ | -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 12:26: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles534.castles.com [208.214.165.98]) by hub.freebsd.org (Postfix) with ESMTP id 968A9150D9 for ; Sat, 3 Jul 1999 12:25:55 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA01152; Sat, 3 Jul 1999 12:22:17 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907031922.MAA01152@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dag-Erling Smorgrav Cc: Randall Hopper , Jim Mock , stable@FreeBSD.ORG Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback) In-reply-to: Your message of "03 Jul 1999 19:58:47 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Jul 1999 12:22:16 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Randall Hopper writes: > > Ok, I didn't know what to do with: > > > > include /boot/loader.4th > > start > > > > which were already in this file, so I commented them out. I was lucky. > > They're not much use unless you want to use loader.conf (loader.4th > reads loader.conf and does magic stuff as directed by variables > defined there, much like /etc/rc does magic stuff as directed by > /etc/rc.conf) Yeah, including useful things like loading splash images and kernel configuration files. You should use loader.conf, not loader.rc, to load splash data, etc. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 14: 7:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 3E56714D24 for ; Sat, 3 Jul 1999 14:07:27 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id RAA07240; Sat, 3 Jul 1999 17:12:26 -0400 (EDT) Date: Sat, 3 Jul 1999 16:12:24 -0500 (EST) From: Alfred Perlstein To: JMS Internet Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Server Slowdown In-Reply-To: <4.1.19990703094749.00abc430@mail.sirius.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, JMS Internet wrote: > Here is some more information about my system: > Intel PII 350, 384 Megs of RAM, 2 Multi-Gig hard drives (neither at capacity). > My co-location company and myself know that there is more transfer trying > to get through because we see it hitting a "roof" on it's transfer at about > 3200kbps, > and it won't go past that, and there is no steady up and downs, it's flat > lining > at that type of transfer, so we know something is wrong, and speed for > transfers > is VERY slow... I ran a test at netmechanic.com, and it rated it as "poor". A > site to look at for yourself would be www.sitepalace.com. Thanks for your > help... > Here is the information requested below: everything below looks sort of "happy". some other questions: 1) what kind of network card installed? 2) are you plugged into a switch or hub? 3) try toggling the "duplex" of the cards operation, try flipping it using the ifconfig program and checking the network card's man page to explain how to select the operation mode. I have an fxp card, I can change it to full duplex like so: ifconfig fxp0 -mediaopt full-duplex 4) how are local transfers? like ftp to something on the same 100mbit network? -Alfred > FROM TOP: > last pid: 89067; load averages: 0.62, 0.81, 0.75 up 3+21:40:19 09:53:38 > 279 processes: 1 running, 272 sleeping, 6 zombie > CPU states: 7.8% user, 0.0% nice, 8.2% system, 6.2% interrupt, 77.8% idle > Mem: 77M Active, 239M Inact, 45M Wired, 12M Cache, 8346K Buf, 1292K Free > Swap: 522M Total, 13M Used, 508M Free, 3% Inuse > > FROM SYSTAT: > 1 users Load 0.76 0.86 0.76 Sat Jul 3 09:52 > > Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER > Tot Share Tot Share Free in out in out > Act 60648 724 141864 860 16868 count > All 382964 1784 3282820 2264 pages > 145 cow Interrupts > Proc:r p d s w Csw Trp Sys Int Sof Flt 73 zfod 1389 total > 3 241 171 346 2554 1389 71 340 46028 wire 100 clk0 irq0 > 76484 act 128 rtc0 irq8 > 7.1%Sys 13.7%Intr 4.2%User 0.0%Nice 75.0%Idl 243456 inact 343 pci irq11 > | | | | | | | | | | 15360 cache fdc0 irq6 > ====++++++>>- 1508 free 818 wdc0 > irq14 > daefr wdc1 > irq15 > Namei Name-cache Dir-cache prcfr > atkbd0 irq > Calls hits % hits % react > 14218 14183 100 6 0 pdwake > pdpgs > Discs fd0 wd0 wd1 intrn > KB/t 0.00 8.94 0.00 8348 buf > tps 0 46 0 29649 desiredvnodes > MB/s 0.00 0.40 0.00 20442 numvnodes > 4759 freevnodes > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 14:37:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 65A1615137 for ; Sat, 3 Jul 1999 14:37:14 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-3-15.dialup.rdu.ipass.net [209.170.134.15]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id RAA20064; Sat, 3 Jul 1999 17:37:09 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id RAA01251; Sat, 3 Jul 1999 17:39:06 -0400 (EDT) (envelope-from rhh) Date: Sat, 3 Jul 1999 17:39:06 -0400 From: Randall Hopper To: Mike Smith Cc: Dag-Erling Smorgrav , stable@FreeBSD.ORG Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback) Message-ID: <19990703173906.A1098@ipass.net> References: <199907031922.MAA01152@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199907031922.MAA01152@dingo.cdrom.com>; from Mike Smith on Sat, Jul 03, 1999 at 12:22:16PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith: |> Randall Hopper writes: |> > include /boot/loader.4th |> > start |> |> They're not much use unless you want to use loader.conf (loader.4th |> reads loader.conf and does magic stuff as directed by variables |> defined there, much like /etc/rc does magic stuff as directed by |> /etc/rc.conf) | |Yeah, including useful things like loading splash images and kernel |configuration files. | |You should use loader.conf, not loader.rc, to load splash data, etc. Thanks for the pointer. I converted over and certainly prefer the loader.conf form (more sh-like). I expect most users would. Perhaps splash(4) should point folks there instead of loader.rc?... Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 15: 6:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 59F8515185; Sat, 3 Jul 1999 15:06:11 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA24522; Sat, 3 Jul 1999 15:06:10 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA06152; Sat, 3 Jul 1999 15:06:10 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 03 Jul 1999 15:06:10 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: HEADS UP: Soft-updates sources have been moved Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just finished moving the soft-updates sources to "src/sys/contrib/softupdates", as announced a few days ago. All users of soft-updates will need to update their symbolic links in "src/sys/ufs/ffs" before configuring and building a new kernel. This change affects the main branch (-current), the RELENG_3 branch (-stable), and Warner's RELENG_3_2_PAO branch. I've updated the comments in LINT and README.softupdates accordingly. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 17:57:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 2827D1503F for ; Sat, 3 Jul 1999 17:57:47 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id TAA63496; Sat, 3 Jul 1999 19:57:34 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Sat, 3 Jul 1999 19:57:33 -0500 (CDT) From: Chris Dillon To: Marcel Moolenaar Cc: stable@FreeBSD.ORG Subject: Re: Linux emulation In-Reply-To: <377DB035.7EE9AF75@scc.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 3 Jul 1999, Marcel Moolenaar wrote: > [snip] > > > > Andrij Korud wrote: > > > > "LINUX: 'ioctl' fd=0, typ=0x54(T), num=0x17 not implemented" > > [snip] > > > I wrote: > > > Can you apply the following patch and tell me if it solves your problem > > > without creating new problems? :-) > > [snip] > > Chris Dillon wrote: > > I just tried this patch on my server and it does the job, almost. > > There is no "unsupported ioctl" error message, but the daemon can't > > communicate with the UPS _unless_ I frob the port with tip(1) while > > the daemon is running. The exact moment that I tip the serial port, > > the daemon comes alive and tells me UPS communications were > > established and its happy. tip(1) isn't able to actually talk to the > > UPS, though it doesn't give me any errors of any kind, and I just ~. > > to exit out. This would be acceptable if I could find an automated > > way of frobbing the serial port so that the daemon works. :-) > > I figured something like that would do the trick. A ktrace showed that > read(2) on the com-port returns -1 with errno set to -11. Everything else > seemed to work. > > Can you tell us what kind of frobbing you did? Maybe there's a bug > somewhere in the TCGETS/TCSETS iotcls (these are used right after the > TIOCMBIC ioctl). In /etc/remote: smartups:dv=/dev/cuaa1:br#2400:pa=none: Then simply 'tip smartups' and immediately exit with ~. or kill it. > In the mean time I prepare the patch for being committed. > > As for automated frobbing :-) Maybe it helps to initialize the device at > boot-time. See /etc/rc.serial I'm not sure that /etc/rc.serial would help, but I'll play with it later and see. ... > I have my uname patch applied by default, which means that uname returns > "Linux" by default. When you run the pap_inst script in a Linux sh, it all > works out of the box. Changing the defaults and directories in the script > to match a FreeBSD environment is something which would be nice in case of > a real port though (hint :-) That's exactly what I did, and I will do a port as soon as I can get it working without needing to touch the serial port first. :-) In the event that messing with /etc/rc.serial does the trick, does anyone know of any ports that modify anything in /etc to use as an example? I'm not so sure that is an acceptable thing for a port to do, but if it is, it would make things a lot easier. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 18: 1:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles534.castles.com [208.214.165.98]) by hub.freebsd.org (Postfix) with ESMTP id AAF2314CAF for ; Sat, 3 Jul 1999 18:01:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02543; Sat, 3 Jul 1999 17:57:31 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907040057.RAA02543@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chris Dillon Cc: Marcel Moolenaar , stable@FreeBSD.ORG Subject: Re: Linux emulation In-reply-to: Your message of "Sat, 03 Jul 1999 19:57:33 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Jul 1999 17:57:30 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > In the event that messing with /etc/rc.serial does the trick, does > anyone know of any ports that modify anything in /etc to use as an > example? I'm not so sure that is an acceptable thing for a port to > do, but if it is, it would make things a lot easier. Don't. You're writing a daemon, so you'll have a shellscript in /usr/local/etc/rc.d. Everything that rc.serial does can be done by your shellscript... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 20:32:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netrinsics.com (unknown [210.74.175.1]) by hub.freebsd.org (Postfix) with ESMTP id CD1D014DD4 for ; Sat, 3 Jul 1999 20:32:20 -0700 (PDT) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id LAA02964 for freebsd-stable@freebsd.org; Sun, 4 Jul 1999 11:31:50 +0800 (CST) (envelope-from robinson) Date: Sun, 4 Jul 1999 11:31:50 +0800 (CST) From: Michael Robinson Message-Id: <199907040331.LAA02964@netrinsics.com> To: freebsd-stable@freebsd.org Subject: Multi-byte locales Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a -STABLE system (3.2-PAO kernel), every call to setlocale(LC_CTYPE, "") returns with an error, where is one of: ja_JP.EUC ja_JP.SJIS ko_KR.EUC zh_CN.EUC zh_TW.BIG5 All single-byte locales work fine. I didn't see anything like this in the mailing list archives or PR database, so I'd thought I'd check if anyone can confirm or refute this before I submit a PR. Thanks. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 22: 5: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 6158814C30 for ; Sat, 3 Jul 1999 22:05:00 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt4-208-166-127-207.dialup.HiWAAY.net [208.166.127.207]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id AAA13752; Sun, 4 Jul 1999 00:04:58 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id AAA29436; Sun, 4 Jul 1999 00:00:50 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199907040500.AAA29436@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: JMS Internet Cc: freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: Server Slowdown In-reply-to: Message from JMS Internet of "Sat, 03 Jul 1999 09:53:09 PDT." <4.1.19990703094749.00abc430@mail.sirius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Jul 1999 00:00:50 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG JMS Internet writes: > Here is some more information about my system: > Intel PII 350, 384 Megs of RAM, 2 Multi-Gig hard drives (neither at capacity). [...] > FROM SYSTAT: > 1 users Load 0.76 0.86 0.76 Sat Jul 3 09:52 > > Mem:KB REAL VIRTUAL VN PAGER SWAP PAGER > Tot Share Tot Share Free in out in out > Act 60648 724 141864 860 16868 count > All 382964 1784 3282820 2264 pages > 145 cow Interrupts > Proc:r p d s w Csw Trp Sys Int Sof Flt 73 zfod 1389 total > 3 241 171 346 2554 1389 71 340 46028 wire 100 clk0 irq0 > 76484 act 128 rtc0 irq8 > 7.1%Sys 13.7%Intr 4.2%User 0.0%Nice 75.0%Idl 243456 inact 343 pci irq11 > | | | | | | | | | | 15360 cache fdc0 irq6 > ====++++++>>- 1508 free 818 wdc0 > irq14 > daefr wdc1 > irq15 > Namei Name-cache Dir-cache prcfr > atkbd0 irq > Calls hits % hits % react > 14218 14183 100 6 0 pdwake > pdpgs > Discs fd0 wd0 wd1 intrn > KB/t 0.00 8.94 0.00 8348 buf > tps 0 46 0 29649 desiredvnodes > MB/s 0.00 0.40 0.00 20442 numvnodes A likely culprit is your IDE HD's. Altho I wouldn't think the above example is demonstrating a system starved for I/O. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 22:56:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id 1372E14C01 for ; Sat, 3 Jul 1999 22:56:20 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from scones.sup.scc.nl (i004.ztm.euronet.nl [194.134.112.5]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id HAA07416; Sun, 4 Jul 1999 07:56:13 +0200 (MET DST) Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id HAA57677; Sun, 4 Jul 1999 07:56:10 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <377EF77A.D6FBF364@scc.nl> Date: Sun, 04 Jul 1999 07:56:10 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Chris Dillon Cc: stable@FreeBSD.ORG Subject: Re: Linux emulation References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Dillon wrote: > > [snip] > > > > Can you tell us what kind of frobbing you did? Maybe there's a bug > > somewhere in the TCGETS/TCSETS iotcls (these are used right after the > > TIOCMBIC ioctl). > > In /etc/remote: > smartups:dv=/dev/cuaa1:br#2400:pa=none: > > Then simply 'tip smartups' and immediately exit with ~. or kill it. You'd expect an upsd to be able to initialize a serial port. I try to figure out who or what's the problem. Thanks. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 23:12:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 661EC14C59 for ; Sat, 3 Jul 1999 23:12:06 -0700 (PDT) (envelope-from tom@embt.com) Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id BAA04104 for ; Sun, 4 Jul 1999 01:12:34 -0500 (CDT) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990704021204.00728fb0@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sun, 04 Jul 1999 02:12:04 -0400 To: freebsd-stable@freebsd.org From: Tom Embt Subject: PNIC problems: duplex contradiction & dropped packets Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running a Kingston KNE110TX (82c169) card under FreeBSD 3.2-BETA connected to an Asante 8+2 switch. I have been having two (almost certainly related) problems: 1) The switch always seems to think the card is in half-duplex mode. The only way to get the switch's LEDs to show FDX is to use 'autoselect' but even then if I power cycle the switch it will show half duplex again. The LEDs on the card always show FDX, unless of course I manually set it to half. 2) When the BSD box is on a 100MB segment, anything more than minimal traffic will cause loss of data. For example, I can telnet into it OK, but upon running 'lptest' I will get dumped. Also I could FTP into it, but getting a large directory listing will cause the client to hang. I can do more testing and provide more information, but first I thought I'd see if this is a known problem. I've tried a few different cables, but not many. Anyone know what I'm looking at here? funky drivers.. bad hardware.. losing my mind??? later, Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jul 3 23:57:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 4C65A14CC7 for ; Sat, 3 Jul 1999 23:57:09 -0700 (PDT) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 110gD6-0001oY-00 for freebsd-stable@freebsd.org; Sun, 04 Jul 1999 02:57:08 -0400 Date: Sun, 4 Jul 1999 02:57:07 -0400 From: Peter Radcliffe To: freebsd-stable@freebsd.org Subject: Re: PNIC problems: duplex contradiction & dropped packets Message-ID: <19990704025707.B2631@pir.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <3.0.3.32.19990704021204.00728fb0@mail.embt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3.0.3.32.19990704021204.00728fb0@mail.embt.com>; from Tom Embt on Sun, Jul 04, 1999 at 02:12:04AM -0400 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom Embt probably said: > I am running a Kingston KNE110TX (82c169) card under FreeBSD 3.2-BETA > connected to an Asante 8+2 switch. I have been having two (almost > certainly related) problems: I'm using BSD boxes (2.2.8-R and 3.2-S) with intel pro100b net cards and an Asante 8+2 switch. They negotiate full duplex fine, but I can't get them to do 100bT even if I force both ends ... Not much help, but a datapoint. I _do_ like the pro100b cards, thats the only problem I've had with them they usually Just Work. P. -- pir pir@pir.net pir@shore.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message