Re: Make installworld failure
On Thursday 11 September 2003 07:04 am, Elliott Perrin wrote: > Please cc me, I am not on either list > > I tried the RELENG_4_8 as a workaround with the exact same error as > before. > > vm/vnode_pager.h -> vm/vnode_pager.ph > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/utils/h2ph. > *** Error code 1 > > and a bunch of other error code 1's back up the directory tree. These aren't the error message. The error 1's are telling you that you have an error. If you can't see it, you need to redirect stdout and stderr from your installworld to a file. Since it is dying in 2 different tags, and no one else is having problems, the first assumption is that you have something wrong in your setup. For example, are you cvsuping src-all? Do you have anything in /etc/make.conf? Are you running the installworld from single user mode and etc. Kent > > [EMAIL PROTECTED] > > on 9/9/03 6:18 PM, Alex de Kruijff at [EMAIL PROTECTED] wrote: > > On Tue, Sep 09, 2003 at 04:36:12PM -0400, Elliott Perrin wrote: > >> Good Day, > >> > >> Please cc me ( [EMAIL PROTECTED] ) on responses to this, I am not > >> on either mailing list anymore. > >> > >> I cvsup'ed on the STABLE branch today (September 9th) at around > >> 2:30PM EDT. No problems with buildworld or kernel build, but I am > >> getting failures during installworld > > > > You could try the RELENG_4_8 tag instead of STABLE as a work > > around. > > _______ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pcm0 freezes computer with recent -STABLE
On Wednesday 24 September 2003 02:32 pm, Kent Stewart wrote: > On Wednesday 24 September 2003 07:42 am, M. Warner Losh wrote: > > In message: <[EMAIL PROTECTED]> > > > > Patrick C <[EMAIL PROTECTED]> writes: > > : On September 22, 2003 06:37 pm, you wrote: > > : > In message: <[EMAIL PROTECTED]> > > : > > > : > Michael Sierchio <[EMAIL PROTECTED]> writes: > > : > : Patrick C wrote: > > : > : > I just cvsup'd Sept 21, installed everything today... > > : > : > kernel freezes when detecting pcm0 during boot. After > > : > : > removing my soundcard, I'm able to boot no problem. Any > > : > : > major changes to pcm0 in -STABLE lately? > > : > : > > : > : This happened intermittently to my Dell Inspiron -- there is > > : > : a bug in the pcibus.c device probe, actually. See if the > > : > : following cures it. Warner supposedly had a more correct > > : > : revision, but I don't think it's been mfc'd. > > : > > > : > Yes. I'm pretty sure it has been MFC'd. Checking just now > > : > shows that it has been MFC'd. > > : > > > : > Warner > > : > > : Nope. cvsup'd today after reading this, built and installed > > : kernel/world again... same problem. FWIW, switching BIOS to PnP > > : seems to fix that, but then my NIC doesn't work (yes, I realize > > : it can be configured to work) > > > > this isn't the pci scanning changes then. There's some other > > problem at work here. the pci scanning issue is known to only > > impact weird CPUs found currently in Soekris boxes... > > When I did the RELENG_4 update with the security patch in it to this > system (topaz) with USB on it, the boot died with the latest > 4.9-prefelease. It also completely hung my kvm switch. That happens > occasionally but had never been caused by topaz before. My gateway > computer is not having any problems with the same code. > > I will go back when it is quiet and see where the boot stops. > The section of the dmesg and the location where the boot freezes. ohci0: mem 0xcffce000-0xcffcefff irq 10 at device 2.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered The boot hangs at this point. It also freezes the kvm switch. It was cvsup'ed at 1822 PDT ( 0122 UTC). I am back to running the kernel from 30 August. Kent uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.10/1.10, addr 2 uhub1: 4 ports with 4 removable, self powered uhid0: Microsoft SideWinder Game Voice, rev 1.10/1.01, addr 3, iclass 3/0 ohci1: mem 0xcffcf000-0xcffc irq 10 at device 2.3 on pci0 -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB hangs during boot of 4.9
On Monday 22 September 2003 10:53 am, regis rampnoux wrote: > On 22-Sep-2003 Paul Horechuk wrote: > > Did I miss any USB alerts? > > As a workaround, you can disconnect your USB devices and reconnect > them after booting (at least after the usb tests). I have also an usb > mouse. I have disconnected my hub but Olivier reports that without > the webcam it can boot. (read posts with subject "USB Problem"). My system is also hanging during the boot. The only usb changes made from the system that works and the one that hangs are the following: # Edit file src/sys/dev/usb/usbdevs * Update to 1.11.2.48 (at 2003-09-02 14:35:17 by joe) # Edit file src/sys/dev/usb/usbdevs.h * Update to 1.32.2.45 (at 2003-09-02 14:35:57 by joe) # Edit file src/sys/dev/usb/usbdevs_data.h * Update to 1.32.2.45 (at 2003-09-02 14:35:57 by joe) # Edit file src/sys/dev/usb/uvisor.c * Update to 1.7.2.6 (at 2003-09-02 14:35:17 by joe) I haven't tried disconnecting it. My system hangs during the boot to single user mode to do the installworld. I don't see any point in completing the boot and doing the installworld. The only thing plugged into the hub is a MS Sidewinder Precision 2 Joystick and a MS Sidewinder game voice. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9 Boot Hang when USB Devices Attached
On Friday 26 September 2003 12:06 pm, Joe Kelsey wrote: > Brandon Fosdick wrote: > > Joe Kelsey wrote: > >> When I upgraded to fix the OpenSSH problems, the system started > >> hanging at boot time right after the USB/OHCI messages whenever I > >> had devices plugged into the USB ports (mainly a USB mouse). Now, > >> in order to boot, I have to unplug the mouse and wait for the > >> system to pass the USB part of boot before replugging. > > > > There are several threads discussing this ATM. If you have an > > nforce2 board search for the thread with the subject > > "fix/workaround for usb probe lockups on nForce2 mbs". Andrew > > Atrens posted a patch that worked for me. In the same thread Ian > > Dowse has offered a few other ideas to try. I haven't tried them > > yet. > > I have an ASUS A7S333 which does *not* have an nforce2 chipset. > Mine doesn't either and the fact it dies in the boot -s phase of updating the system is a verification of the reason to boot to single user mode. I have tried unplugging the USB devices and it will finish the boot. I won't, however, finish the installworld. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Patch for boot-time USB hangs in 4.9-PRERELEASE
On Saturday 27 September 2003 06:05 am, Ian Dowse wrote: > Could people who are experiencing boot-time hangs in 4.9-PRERELEASE > try the following patch to see if it helps? I've had one positive > report so far, but it would be helpful to get more feedback to > determine if this is the right fix to be committed. > It also works for me. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld stops at etc/sendmail (was: can't install 'bin/sh')
On Sunday 16 November 2003 03:29 pm, Jeroen wrote: > lo, > > same problem here. discovered an entry in my (default) cvsup refuse > file with `src/etc/sendmail/freebsd.mc`. bit weird though? why put that > in the default refuse file? > It was an example. You were supposed to change it to what you needed. To many people didn't and it has been removed from the current example. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup2
On Thursday 22 January 2004 01:34 pm, Kris Kennaway wrote: > On Thu, Jan 22, 2004 at 01:45:53PM -0500, Mike Jakubik wrote: > > Thanks for the info. Cvsup2 was my fastest link :) > > You can use the fastest_cvsup port to find a replacement in the > meantime. But fastest in the fastest_cvsup sense doesn't accurately represent the shortest cvsup session. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Error compiling XFree86-4-clients
On Thursday 13 May 2004 11:34 am, Thomas Schweikle wrote: > Hi! > > I can't compile XFree86-4-clients. Here is what is given back: > > cc -o bdftopcf -O -pipe -ansi -Dasm=__asm \ >-Wall -Wpointer-arith -Wundef \ >-L/home/ports/x11/XFree86-4-clients/work/xc/exports/lib \ > bdftopcf.o -lXfont -lfntstubs -L/usr/X11R6/lib \ >-lz -lm -Wl,-rpath,/usr/X11R6/lib > /usr/libexec/elf/ld: cannot find -lXfont > *** Error code 1 > > Stop in /home/ports/x11/XFree86-4-clients/work/xc/programs/bdftopcf. > *** Error code 1 > > Stop in /home/ports/x11/XFree86-4-clients/work/xc/programs. > *** Error code 1 > > Stop in /home/ports/x11/XFree86-4-clients. > > Any idea what I can do? Yes, you need to reinstall -libraries. You have missed the transition from Xfonts being in -server to -libraries and when you updated -sever it deleted Xfonts. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to build world
On Wednesday 16 June 2004 09:55 pm, Roger Merritt wrote: > I hadn't updated my world for quite a while, so I ran cvsup to make > sure I had the latest modifications to the code and then tried to run > "make buildworld". Failed. Tried again, failed. Went to the file > where the build failed, didn't see any problem. Deleted the whole > /usr/src directory and > Since it is trying to use a file from /usr/obj, have your rm'ed it. > ran cvsup to retrieve the whole body of code again. Still failed. I get: > >===> games/robots > >cc -O -pipe -march=pentium -DMAX_PER_UID=5-c > >/usr/home/src/games/robots/extern.c > >cc -O -pipe -march=pentium -DMAX_PER_UID=5-c > >/usr/home/src/games/robots/init_field.c > >cc -O -pipe -march=pentium -DMAX_PER_UID=5-c > >/usr/home/src/games/robots/main.c > >In file included from /usr/home/src/games/robots/robots.h:36, > > from /usr/home/src/games/robots/main.c:48: > >/usr/obj/usr/home/src/i386/usr/include/curses.h:1281: undefined or > > invalid # directive > >*** Error code 1 > > > >Stop in /usr/home/src/games/robots. > >*** Error code 1 > > > >Stop in /usr/home/src/games. > >*** Error code 1 > > > >Stop in /usr/home/src. > >*** Error code 1 > > > >Stop in /usr/home/src. > >*** Error code 1 > > > >Stop in /usr/home/src. > > Incidentally, for space reasons I had to put the source tree in the > "home" directory (a separate slice on my hard drive) with a syslink > as /usr/src, but I've built world many times (at least several times) > since I did that and never had a problem before. The only time I have run into a problem with this is if I try to NFS mount /usr/src or /usr/obj. The build process remembers the real path and used it. It was not the same on the machine doing the mounting. When I setup a system to be NFS mountable, I put /usr/src and /usr/obj on their own partitions. Then, build process uses the same path on the machine doing the mounting. Kent > > uname -v gives me: FreeBSD 4.8-STABLE #0: Tue May 6 18:29:38 ICT > 2003, my last cvsup completed successfully last night at about 2230 > hours local time. > > Is it possible I need to upgrade "make" or something like that? I > recall that was a problem once before. But what's with this weird > path /usr/obj/usr/home/src/i386/usr/include/curses.h?? vi opens the > file, and line 1281 is "#define BUTTON_SHIFT > 0002L", which doesn't look like an "undefined or invalid # > directive" to me. -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -STABLE build appears broken after ipfilter 3.4.35 MFC
On Sunday 04 July 2004 09:55 am, Ruslan Ermilov wrote: > On Sun, Jul 04, 2004 at 07:07:47AM -0700, David Wolfskill wrote: > > [I sent a copy of this information under separate cover to Darren > > Reed a little while ago. dhw] Darren's 1741 UTC to ip_fil.h fix lets it build on my test system. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Old version of bison
On Tuesday 04 January 2005 03:27 am, Godwin Stewart wrote:
> Ports cvsup'ed yesterday,
>
> $ cat /usr/ports/devel/bison/Makefile
> {snip}
> PORTNAME= bison
> PORTVERSION=1.75
> PORTREVISION= 2
> {snip}
>
> Is there any particular reason why ports are sticking with this
> version when 1.875 was released 2 years ago almost to the day?
If you have an uptodate port system you will find
Port: bison-1.875_4
Path: /usr/ports/devel/bison1875
Kent
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Old version of bison
On Tuesday 04 January 2005 04:13 am, Godwin Stewart wrote: > On Tue, 4 Jan 2005 03:55:42 -0800, Kent Stewart <[EMAIL PROTECTED]> wrote: > > If you have an uptodate port system you will find > > > > Port: bison-1.875_4 > > Path: /usr/ports/devel/bison1875 > > Indeed. > > That'll teach me to hit [tab] twice after typing > /usr/ports/devel/bison > What I find handy is a perl script called portsearch. It is located in ports/Tools/scripts/ I moved it into a directory in my path. Then, I added an alias search'portsearch -n $1' You can do interesting things like search ^bison Where the port name begins with bison. There are a number of other interesting options. They are covered in a README. Make search does something similar but the output from portsearch is cleaner. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building snapshot CDs
On Friday 18 March 2005 10:02 am, Michael Butler wrote:
> When I tried to build a local snapshot from a fresh cvsup today, it
> failed with "touch not found", so I patched /usr/src/Makefile.inc1 as
> follows:
>
> *** Makefile.inc1~ Wed Mar 2 08:22:57 2005
> --- Makefile.inc1 Fri Mar 18 12:11:15 2005
> ***
> *** 558,564
> ~for prog in [ awk cap_mkdb cat chflags chmod chown \
> ~date echo egrep find grep \
> ~ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
> ! test true uname wc zic; do \
> ~cp `which $$prog` ${INSTALLTMP}; \
> ~done
> ~${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}
> --- 558,564
> ~for prog in [ awk cap_mkdb cat chflags chmod chown \
> ~date echo egrep find grep \
> ~ln make mkdir mtree mv pwd_mkdb rm sed sh sysctl \
> ! test touch true uname wc zic; do \
> ~cp `which $$prog` ${INSTALLTMP}; \
> ~done
> ~${_+_}cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//}
>
> Did I miss something?
>
Having touch show up in a post buildworld is frequently a sign of a
system clock running behind time. It creates a file but the file is
older than the files you cvsuped. Make thinks it needs to remake the
file it created and away you go.
Kent
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5 broken?
On Thursday 14 April 2005 09:23 pm, Joel wrote: (B> On Thu, 14 Apr 2005 11:20:54 -0700 (B> Nate Lawson <[EMAIL PROTECTED]> wrote (B> (B> > Jon Noack wrote: (B> > > On 4/14/2005 8:28 AM, David Wolfskill wrote: (B> > >> On Thu, Apr 14, 2005 at 01:26:17PM +0200, Jose M Rodriguez wrote: (B> > >>> Anyone seen this? (B> > >> (B> > >> [... (B> > >> /usr/src/sys/kern/subr_bus.c:1082: warning: no previous (B> > >> prototype for 'devclass_get_drivers' (B> > >> *** Error code 1 (B> > >> ... (B> > >> ] (B> > >> (B> > >> Yup; just a few minutes ago, with sys/kern/subr_bus.c rev. (B> > >> 1.156.2.6. (B> > >> (B> > >> Perhaps something was overlooked in the MFC from 2005-04-14 (B> > >> 04:54:15 UTC? (B> > > (B> > > Yeah, we also need to MFC rev. 1.68 of src/sys/sys/bus.h. (B> > (B> > I've committed the prototype, much apologies for the breakage. I (B> > compiled the patch in my RELENG_5 tree just fine, but it appears (B> > the kernel build may be referencing /sys for includes instead of (B> > ../../../sys or whatever. Thus build-testing MFC patches on a (B> > -current box is not a good test. (B> (B> Okay, I started a build makeworld in /usr/src last night, and then (B> build make kernel hits this. (B> (B> What do we do next? Is it okay to go back to cvsup, and will that (B> pick up the changes? (B> (B (BJoel, (B (BCan I give you a bad time. We were always told that if you follow (Bx-stable, you were to follow cvs-all. Then, you would have seen his fix (Bcommitted around 1811 UTC. (B (BFWIW, you are just in time anyway because they added a security notice (Band if you cvsup now, you will also get that fix. (B (BKent (B (B-- (BKent Stewart (BRichland, WA (B (Bhttp://users.owt.com/kstewart/index.html (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5 broken?
On Thursday 14 April 2005 10:49 pm, Joel wrote: (B> On Thu, 14 Apr 2005 22:32:42 -0700 (B> Kent Stewart <[EMAIL PROTECTED]> wrote (B> (B> > On Thursday 14 April 2005 09:23 pm, Joel wrote: (B> > > On Thu, 14 Apr 2005 11:20:54 -0700 (B> > > Nate Lawson <[EMAIL PROTECTED]> wrote (B> > > (B> > > > Jon Noack wrote: (B> > > > > On 4/14/2005 8:28 AM, David Wolfskill wrote: (B> > > > >> On Thu, Apr 14, 2005 at 01:26:17PM +0200, Jose M Rodriguez (Bwrote: (B> > > > >>> Anyone seen this? (B> > > > >> (B> > > > >> [... (B> > > > >> /usr/src/sys/kern/subr_bus.c:1082: warning: no previous (B> > > > >> prototype for 'devclass_get_drivers' (B> > > > >> *** Error code 1 (B> > > > >> ... (B> > > > >> ] (B> > > > >> (B> > > > >> Yup; just a few minutes ago, with sys/kern/subr_bus.c rev. (B> > > > >> 1.156.2.6. (B> > > > >> (B> > > > >> Perhaps something was overlooked in the MFC from 2005-04-14 (B> > > > >> 04:54:15 UTC? (B> > > > > (B> > > > > Yeah, we also need to MFC rev. 1.68 of src/sys/sys/bus.h. (B> > > > (B> > > > I've committed the prototype, much apologies for the breakage. (B> > > > I compiled the patch in my RELENG_5 tree just fine, but it (B> > > > appears the kernel build may be referencing /sys for includes (B> > > > instead of ../../../sys or whatever. Thus build-testing MFC (B> > > > patches on a -current box is not a good test. (B> > > (B> > > Okay, I started a build makeworld in /usr/src last night, and (B> > > then build make kernel hits this. (B> > > (B> > > What do we do next? Is it okay to go back to cvsup, and will that (B> > > pick up the changes? (B> > (B> > Joel, (B> > (B> > Can I give you a bad time. (B> (B> Of course. My kids would say I deserve it, too, since I'm such a (B> tease around the house. (B> (B> > We were always told that if you follow (B> > x-stable, you were to follow cvs-all. (B> (B> ... as in editing the example to set the default host to (B> cvsup3.jp.freebsd.org, and doing (B> (B> sudo cvsup -g -L 2 stable-supfile (B> (B> right before the make buildworld? (B> (B> > Then, you would have seen his fix (B> > committed around 1811 UTC. (B> (B> I think I was in bed by then. (UTC+9 here.) (B> (B> > FWIW, you are just in time anyway because they added a security (B> > notice and if you cvsup now, you will also get that fix. (B> (B> So the system is not in an unstable situation such that repeating the (B> cvsup would have me trying to build from inconsistent libraries or (B> anything like that? (B (BWhen you do the buildworld, you get a new world and then the kernel will (Bbuild. This is one of the reasons to buildworld, buildkernel, and (Binstall kernel. Since the buildkernel died, your libraries haven't been (Bupdated. You wouldn't do that until after you have booted the new (Bkernel in single user mode. The sequence may be awkward at times but it (Bsaves you from the little disasters :). (B (B> (B> What the heck, I'll take a backup and give it a spin. (B (BJust remember you build and install the world and the kernel. I just got (Bthrough upgrading to get the ifconf fix. No, problem. (B (BKent (B (B> (B> Thanks. (B> (B> -- (B> Joel Rees <[EMAIL PROTECTED]> (B> digitcom, inc. $B3t<02q Kobe, Japan +81-78-672-8800 (B> ** <http://www.ddcom.co.jp> ** (B> (B> ___ (B> freebsd-stable@freebsd.org mailing list (B> http://lists.freebsd.org/mailman/listinfo/freebsd-stable (B> To unsubscribe, send any mail to (B> "[EMAIL PROTECTED]" (B (B-- (BKent Stewart (BRichland, WA (B (Bhttp://users.owt.com/kstewart/index.html (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Tuesday 19 April 2005 01:39 pm, Dan Nelson wrote: > In the last episode (Apr 19), Bill Moran said: > > Chuck Swiger <[EMAIL PROTECTED]> wrote: > > > Bill Moran wrote: > > > > The system can not replace programs that are in use, > > > > > > This is generally not the case. Unix lets you continue to access > > > a file after it has been deleted, so long as the process hangs on > > > to a file descriptor. This lets you replace programs in use, > > > without running into the same problems that platforms like > > > Windows have. > > > > What you say?: > > > > bash-2.05b$ su > > Password: > > bolivia# cp /usr/sbin/cron /home/wmoran/. > > bolivia# cp /home/wmoran/cron /usr/sbin/. > > cp: /usr/sbin/./cron: Text file busy > > bolivia# > > > > Notice that /usr/sbin/cron is in use (because my system is running > > normally) I can copy _from_ that file, but I can not overwrite it. > > What you can do, however, is: create the new file under a temporary > name, delete the original, and rename the temp file to the orignal's > name, which is what /usr/bin/install does. I've done many > installworlds on running systems without problems. You are forgetting that one of the real purposes of the boot -s is to test your new kernel. If you have never been bitten by a kernel that would only panic, you have no problems. If you have, you know that you can boot the old kernel and continue without any problems until some one solves the panic. You will not most likely hit that situation on a security based version but this is freebsd-stable and it can happen at any time. My attitude is that if you don't boot -s, you are simply playing Russian-roulette with your system. Some day, it will bite you. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Acroread 7 port broken?
On Tuesday 17 May 2005 11:21 am, ya hoo wrote: > I just tried to install acroread 7 from the ports that I cvsup'd last > night. It tells me that it is marked broekn. > > I assume it is broken, but does anyone know when it will be fixed? > > There must be something else going on. I just cvsuped and had no problem building acroreader. It was broken a while back but the current version isn't broken. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fixes for build problems with SMP-stable
Cliff Skolnick wrote: > > FreeBSD.org - Document not found Mike must have flipped a bit when he was copying that URL :). Try http://www.freebsd.org/~msmith/smp-stable.diff. BTW, you can find it the way I did by looking at http://www.freebsd.org/~msmith/ Kent > > On Wed, 1 Sep 1999, Mike Smith wrote: > > > > > Ok; now I have a working -stable SMP system I can actually test this. > > What _was_ I smoking before? > > > > Can anyone with a -stable SMP system please apply the patches at > > http://www.freebsd.org/~msmith/stable-smp.diff and let me know whether > > these result in a buildable and runnable kernel? We need to get this > > into -stable ASAP for obvious reasons. > > > > > > -- > > \\ The mind's the standard \\ Mike Smith > > \\ of the man. \\ [EMAIL PROTECTED] > > \\-- Joseph Merrick \\ [EMAIL PROTECTED] > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- >| Cliff Skolnick | "They that can give up essential liberty to | >| Steam Tunnel Operations | obtain a little temporary safety deserve | >| [EMAIL PROTECTED] | neither liberty nor safety." | >| http://www.steam.com/ | -- Benjamin Franklin, 1759 | > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Cvsup to 3.3-RC Failure
I recently cvsup'ed from 3.2-stable to 3.3-RC. During the process I ended up with an incomplete set of /dev's. I had ttyv0-3 and when I rebooted, I ended up with a screen filled with Sep 6 15:04:14 ruby getty[256]: open /dev/ttyv4: No such file or directory Sep 6 15:04:14 ruby getty[257]: open /dev/ttyv5: No such file or directory Sep 6 15:04:14 ruby getty[258]: open /dev/ttyv6: No such file or directory Sep 6 15:04:14 ruby getty[259]: open /dev/ttyv7: No such file or directory I had combined the old and new with Mergemaster-1.25. A simple fix was a MAKDEV all. -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Cvsup to 3.3-RC Failure
"Jeffrey J. Libman" wrote: > > if you look at the CVSUP tutorial, it tells you that one of the things you > have to do is re-make your devices. The problem was that I thought that Mergemaster did that for me. Kent > > cheers, > jeff > > | > |\+--+ > Jeffrey J. Libman, ops. mgr.| \ | Wantabe Internet Services | > Wantabe, Inc. |__\ +--+ > [EMAIL PROTECTED]<-|--> | access web cgi ftp news mail | > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +--+ > > On Thu, 9 Sep 1999, Kent Stewart wrote: > > > I recently cvsup'ed from 3.2-stable to 3.3-RC. During the process I > > ended up with an incomplete set of /dev's. I had ttyv0-3 and when I > > rebooted, I ended up with a screen filled with > > > > Sep 6 15:04:14 ruby getty[256]: open /dev/ttyv4: No such file or > > directory > > Sep 6 15:04:14 ruby getty[257]: open /dev/ttyv5: No such file or > > directory > > Sep 6 15:04:14 ruby getty[258]: open /dev/ttyv6: No such file or > > directory > > Sep 6 15:04:14 ruby getty[259]: open /dev/ttyv7: No such file or > > directory > > > > I had combined the old and new with Mergemaster-1.25. A simple fix was > > a MAKDEV all. > > -- > > Kent Stewart > > Richland, WA > > > > mailto:[EMAIL PROTECTED] > > http://www.3-cities.com/~kstewart/index.html > > > > SETI (Search for Extraterrestrial Intelligence) @ Home > > http://setiathome.ssl.berkeley.edu/ > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Power Pack at CompUSA
"Chad R. Larson" wrote: > > I visited my closest CompUSA last night, and asked someone there to > look up the Power Pack on their inventory computer. He said it was > a standard item, catagory A01. Which means (the A part) each > store is supposed to stock it and (the 01 part) the minimum quantity > is one. Price $49.95. > > I asked if they had one. Nope, sold out. Did any of the stores > here in Phoenix have one. More nope. How about nation wide? About > 20 stores showed inventory. The item went into the computer in > June. He said every store should have had at least one at that > time. I can only guess (and hope) that they all sold out like hotcakes, > and someone in purchasing will notice and up the mininum stock count. > > In the meantime I asked them to order me one (which meant, order > two). I've already got the toolkit, and I subscribe to the release, > so this was to update my copy of the book, and to throw some money > at the project, and to encourage CompUSA in carrying FreeBSD > products. I think getting FreeBSD into distribution is the next big > step in advicocy. Do you have a URL for CompUSA? I tried doing a search and ended up with what seemed like 200,000 people with gripe's. I agree on the advocacy point. I can go into my local Costco Wholesale place and purchase Win 98 and Red Hat Linux. They have shipping pallets of them. A series of books that you can purchase in any book store is also mandatory. Kent > > -crl > -- > Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] > DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: speaking of 3.4...
Doug White wrote: > > On Tue, 23 Nov 1999, jack wrote: > > > Today Jordan K. Hubbard wrote: > > > > > > Our release QA is horrible. Look at what Apple does -- they sit on the > > > > release candidate for a *month*, with *no changes at all*, before putting > > > > > > The problem is that Apple also gets people to LOOK at the release > > > candidate for that month. > > > > Apple also has a much better idea of what hardware it will be > > installed on, and doesn't have to contend with the multitude of > > (non)standards for PC hardware. It would probably take years to > > test every possible need of various services (heavy HTTP server, > > ftp, etc.) against all the permutations of available hardware. > > I'm not worried about hardware interactions; I'm worried about plain dumb > bugs, like the whole lo0 fiasco with 3.3. That should _NOT_ have > happened. Yes, but that wasn't the only one. The CDROM's were only bootable on certain devices. There have been boot configuration problems for several releases. There was also something on 3.2 that killed some of us. I really didn't shut us down but impared operation was a functional description. As always, a cvsup a week later for 3.2-Stable worked just fine. There has been something strange broken on the last two releases. Code would be locked down but you may not see and identify the problem for a couple of days and by the time you identify that it wasn't a dumb user error, the gold CDROMs have been shipped to the production facility. The problem was identified too late again. More stuff for the errata file and real newbie gotcha's. The lo0 was a much more severe problem because it shut people down and made them scramble to find a machine to dial to the Internet and get an answer. Kent > > Doug White| FreeBSD: The Power to Serve > [EMAIL PROTECTED] | www.FreeBSD.org > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.3-STABLE Question
Adidas Boy wrote: > > I am thinking about upgrading my FreeBSD 3.3-RELEASE machine which i'm going > to turn into a firewall to the 3.3-STABLE. I have decided that I want to use > the program IP Filter with the firewall for the packet filtering and I heard > from somewhere that 3.3-STABLE comes already with IP Filter precompiled with > the OS? I just need to know if this is true or not? Just remember that if you cvsup to RELENG_3, you are going to get 3.4-Stable. Kent > > Brian > __ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: codecrusader and ntp
Walter posted this earlier and it works. Try it and you will end up with /usr/local/bin/jcc If you tried the port, you already have the distfiles in /usr/ports/distfiles. Kent > > -- Forwarded Message -- > Subject: Re: C++ IDE > Date: Sun, 30 Jan 2000 09:34:35 -0600 > From: "Burke Gallagher" <[EMAIL PROTECTED]> > > The Code Crusader Home page http://www.newplanetsoftware.com/jcc/ > > download the sources from ftp.its.caltech.edu /pub/jafl/programs/jcc/ > you need code_crusader, JX, JTooolBar, and JTree > > untar the source files into /usr/local (or somewhere else convient) > cd /usr/local/JX-1.5.3 > JX_INSTALL_ROOT=/usr/local/bin; export JX_INSTALL_ROOT > ln -s /usr/X11R6/include/X11 /usr/include/X11 > ln -s /usr/local/man /usr/man > gmake freebsd3.x > > good luck this is my favorite unix development system., > burke Charles Cox wrote: > > Yes, I have noticed this as well. In fact, after looking at the source > archive on the FreeBSD web site, the last check-in comment for the Makefile, > in particular. I found out that this port is *not* currently working. I > have been trying to fix this myself so that I can submit a fix, but I > haven't really had enough time lately. Sorry for not posting these results > earlier. > > Perhaps we can all continue working toward a solution, and we will come up > with something. At this point, I am pretty sure that the problem lies > somewhere in the make structure, but I am not sure exactly where. If you do > a make, and grep for 'warning', this gives a number of results, and may be > our best starting point. > > Chuck > > - Original Message - > From: Mike Muir <[EMAIL PROTECTED]> > To: Walter Brameld <[EMAIL PROTECTED]> > Cc: Harlan Stenn <[EMAIL PROTECTED]>; Charles Cox <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Sunday, March 05, 2000 11:15 AM > Subject: Re: codecrusader and ntp > > > Walter Brameld wrote: > > > > > And the name of the executable for code crusader is jcc, which of > > > course ou were supposed to know 8-P. On my system it's in > > > /usr/local/bin. Go here for more information: > > > > > > http://www.newplanetsoftware.com/jcc/ > > > > Hrm for some reason, I am unable to find the 'jcc' executable either.. > > > > [rock] [~/.wmstock] > pkg_info -L code_crusader-2.1.4 > > Information for code_crusader-2.1.4: > > > > Files: > > /usr/local/bin/class_map > > /usr/local/bin/jcc > > ... > > and > > ... > > [rock] [/usr/local/bin] # find /usr -name "jcc" > > [rock] [/usr/local/bin] # find /home/ -name "jcc" > > [rock] [/usr/local/bin] # find /usr1 -name "jcc" > > [rock] [/usr/local/bin] # > > > > It just doesnt seem to be there, every other part of the package is, > > except the main program! note: /usr1 is where my ports are and the > > codecrusader port hasnt been cleaned up yet so everything that was built > > is still there, and find failed to find jcc within this.. After > > inspection of the work/JX-1.5.3/programs/code_crusader tree, i cant seem > > to find any trace of 'jcc'. > > > > Mike. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Weirdest crash I ever saw...
"Jim C. Nasby" wrote: > > Brad Knowles wrote: > > > > At 4:09 PM -0600 2000/3/13, Jim C. Nasby wrote: > > > > > Speaking as a BSEE, the 240V 'leak' is either due to the building wiring or > > > due to very poor design (or both). If possible, try plugging both > > >the computer > > > and the RAID array into the same outlet (I don't know if your in the US or > > > not, so I don't know if your standard voltage is 120V or 240V). > > > > I'm in Belgium, so standard is 240VAC @ 50Hz. > > > > > In any case, I would very strongly suggest you find the problem and fix it, > > > as it could prove to be fatal. > > > > Fatal to me, or fatal to the equipment? I've already had a > Yes, and yes. > > > number of unpleasant shocks, but so far nothing has been more than > > unpleasant. Interestingly, there was a small amount of leakage even > What is currently (no pun intended) no more than unpleasant could easily > turn lethal depending on what's going on. > > > when both systems were turned off and I touched both the case of the > > Comparex D1400 (Hitachi DF400) and a grounding pin on the same power > > strip that the drive array is plugged into, which I have to assume > > comes from the internal batteries in the array. > Batteries or no, you shouldn't have been able to feel anything that way. > Sounds like there's something wrong with the equipment. I still wouldn't > rule out the building wiring either. It is also possible that what ever has messed up the ground could also be causing cause the crash. Kent > > > If we're talking about fatal to the equipment, that's a much more > > serious issue. ;-) > > > > -- > >These are my opinions -- not to be taken as official Skynet policy > > == > > Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV > > Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 > > Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels > > http://www.skynet.be || Belgium > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- > Jim C. Nasby (aka Decibel!) /^\ > [EMAIL PROTECTED] /___\ > Freelance lighting designer and database developer / | \ > Member: Triangle Fraternity, Sports Car Club of America /___|___\ > > Give your computer some brain candy! www.distributed.net Team #1828 > Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: "dangerously dedicated"
Doug Barton wrote: > > Warner Losh wrote: > > > I didn't say that using da0a is stupid. I said using dangerously > > dedicated mode is stupid. Based on the number of times I've shot > > myself in the foot trying to use dangaerously dedicated devices over > > the years, I'll never use them again. > > I'm curious, what kind of problems have you had, and how is using the > compatability slice an improvement? I've always used "dangerously > dedicated" on my freebsd-only disks, and I've never had a problem. When I first started using FreeBSD back in Feb 99, I tried to use DD disks and the system would not begin the boot process. It would count memory and hang. We are talking about three different drives and the boot would fail if any were DD. It was like the bios queried the HDs and the HD would not respond and the bios just sat there waiting for the response. The second I "fdisk /mbr" the drives the system would boot. The drives that I had these problems with were all Western Digital. Two of them died, one was in warranty and was replaced but while it was in the mail I, replaced it with a Maxtor UDMA 33. It is on the shelf because I can't see replacing a UDMA33 drive with one that only does PIO4. Kent > > Not disagreeing, just curious, > > Doug > -- > "So, the cows were part of a dream that dreamed itself into > existence, > is that possible?" asked the student incredulously. > The master simply replied, "Mu." > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: slow connections over ethernet
Tony Byrne wrote: > > On Sun, 9 Apr 2000 00:05:16 -0700 (PDT), you wrote: > > >I'm running a 10Mb ethernet and recently it has started taking a very logn > >time to connect and log into one system from another. These systems are > >all FreeBSD 4.0 of various dates, most recently April 6. I have an Ftp > >login, from the most recent system to a slightly older system that just > >got logged in. It took about 30 seconds to connect and ask for > >UID/passwd, it took about 2 minutes or mopre to get logged in. Once > >logged in, every thing seems fine. > > > >Any thoughts, things I should look at? > > Sounds like a reverse DNS problem to me. I've seen similar long > delays in getting a connection going. Once logged in then everything > seems fine. In each case, I've traced the problem down to the server > not being able to reverse resolve the client's hostname. The delay > I've seen is the amount of time it takes for the DNS lookup to timeout > so that the connection can proceed. I had another one. I was getting 8-9KB/s but when I added tun0 to my version 4.0-S network_interfaces, the rate jumped to MB/s. Kent > > Regards, > > Tony. > > -- > == > Tony Byrne <[EMAIL PROTECTED]>, Swords, Co. Dublin, Ireland. > MP3 Musician http://www.mp3.com/tony_byrne > Get your copy of the Winamp MP3 player: http://www.winamp.com > ========== > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1 date?
"Thomas T. Veldhouse" wrote: > > > > > I'm running it happily on an all SCSI machine (I wanted the SBLive > > support), but it's by no means clean and by no means ready for > > full production use, IMO. This is a .0 release and lots of people > > are waiting for the .1 release before using it in production. > > > > I didn't see Sound Blaster Live (emu10k1) support under 4.0. I did see it > on 5.0 current though. People have downloaded the emul0k1 code and made it work under 4.0. Search the archive on -questions for "SBLive! on FreeBSD 4.0 HOWTO". Kent > > Tom Veldhouse > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0-STABLE reboots on high CPU use?
Brook wrote: > > I've seen a few messages on spontaneous reboots due to the new ata > drivers (which I am using) but my problem doesn't seem to be disk related. > > If I run dnetc (the distributed.net client) then my system will simply > reset after a while. Last night I ran dnetc for the first time in a week > or more and it reset after 6 hours, then after 2, and the last time in > under 30 minutes. > > dnetc does very little disk io, so I assume it has something to do with > the strain on the CPU? I just did a make world with no problems, although > the first time I did this in 4.0-RELEASE (a couple weeks ago) it took > several tries before the entire process completed without a reset. > > included my dmesg if it will be of any use, thanks for any help or > references. You might try running "netstat -m" while this is going on and see if you are running out of mbufs. If you are, you need to increase you NMBCLUSTERS in the kernel. Kent > > Cheers, > Brook > > +--- > | Brook Miles <[EMAIL PROTECTED]> > | A spec of cosmic dust... with attitude. > +-- > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-STABLE #2: Sun Apr 30 00:13:32 PDT 2000 > [EMAIL PROTECTED]:/usr/src/sys/compile/FORGE > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium/P55C (199.90-MHz 586-class CPU) > Origin = "GenuineIntel" Id = 0x544 Stepping = 4 > Features=0x8001bf > real memory = 67108864 (65536K bytes) > config> q > avail memory = 62234624 (60776K bytes) > Preloaded elf kernel "kernel" at 0xc02f9000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc02f909c. > Intel Pentium detected, installing workaround for F00F bug > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > dc0: port 0x6100-0x61ff mem 0xe100-0xe1ff >irq 11 at device 13.0 on pci0 > dc0: Ethernet address: 00:a0:cc:32:bf:3a > miibus0: on dc0 > dcphy0: on miibus0 > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > dc0: supplying EUI64: 00:a0:cc:ff:fe:32:bf:3a > pci0: at 15.0 irq 10 > pci0: (vendor=0x1274, dev=0x5000) at 17.0 irq 12 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1: configured irq 3 not in bitmap of probed irqs 0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > plip0: on ppbus0 > ed0 at port 0x240-0x25f iomem 0xd8000 irq 9 on isa0 > ed0: address 00:40:05:45:0f:fa, type NE2000 (16 bit) > IP packet filtering initialized, divert enabled, rule-based forwarding enabled, >default to deny, logging limited to 32 packets/entry by default > ad0: 3020MB [6136/16/63] at ata0-master using WDMA2 > acd0: CD-RW at ata1-master using PIO3 > acd1: CDROM at ata1-slave using PIO3 > Mounting root from ufs:/dev/ad0s2a > WARNING: / was not properly dismounted > dc0: starting DAD for fe80:0001::02a0:ccff:fe32:bf3a > ed0: starting DAD for fe80:0003::0240:05ff:fe45:0ffa > dc0: DAD complete for fe80:0001::02a0:ccff:fe32:bf3a - no duplicates found > ed0: DAD complete for fe80:0003::0240:05ff:fe45:0ffa - no duplicates found > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Linux Wordperfect on 4.0-STABLE (specific issue)
Check the archives. WP8/Linux starts in about 2 seconds when you have everything right. There are conflicts when you have ports closed and it hangs trying to connect to a service or something. There was a comment by Grog and a follow up by the person with a similar problem. It had to be here on stable in the last week or so. FWIW, I installed the commercial release on 4.0-Stable in the last week. Kent Matt Heckaman wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Has anyone had any luck with Linux WordPerfect 8.0 on FreeBSD 4.0-STABLE? > It was working fine for me under 3.4, but refuses to work at all under > 4.0. I should note that all other Linux apps I run (acroread, linux > netscape, real player 7, mpegtv, etc) all work perfectly. > > What happens when you launch xwp is a rather long 5 minute delay, then the > Corel splash logo comes up, shortly thereafter a window with the title bar > of "Wordperfect" is started (rather small) and there is nothing in the > window by grey. I'm not quite sure what this could be, any ideas? I know > that I did get star office working, so I don't see why WP8 wouldn't work > when it did on 3.4.. Ideas appreciated. > > Matt Heckaman > [EMAIL PROTECTED] > http://www.lucida.qc.ca > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.1 (FreeBSD) > Comment: http://www.lucida.qc.ca/pgp > > iD8DBQE5HMRodMMtMcA1U5ARAjDOAKDr+0IFCWAFwVi/XdMWpr3ZWhIyfQCguazN > 8DSMBvQC9EMEv5oWzdOBztw= > =pe+s > -END PGP SIGNATURE- > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Problems after cvsup
Sasha Nazarenko wrote: > > On Sun, 14 May 2000, Sean-Paul Rees wrote: > > > Date: Sun, 14 May 2000 08:39:53 -0700 > > From: Sean-Paul Rees <[EMAIL PROTECTED]> > > To: Sasha Nazarenko <[EMAIL PROTECTED]> > > Subject: Re: Problems after cvsup > > > > On Sun, May 14, 2000 at 06:32:12PM +0300, Sasha Nazarenko wrote: > > > After today's cvsup from 4.0-S to 4.0-S have some problems: > > > > > > bash-2.03# top > > > top: nlist failed > > > bash-2.03# vmstat > > > vmstat: undefined symbols: > > > _cp_time _kmemstatistics _bucket _zlist > > > > It sounds as if you built a new kernel without rebuilding the world. A no-no. :) > > > > > > Don't know how it sounds, but first was build/install world then > build/install kernel.So this mistake i have on up-to-date kernel/system.. I had a similar problem with top and nlist. There was a patch floating around that solved it on my system. See http://www.geocrawler.com/mail/thread.php3?subject=top%2C+systat+%29-%3A+%28all+rebuilt%21%29&list=152 Follow the thread. The patch worked on my system. Kent > > -- > > Alexander > RIPE: AN-RIPE, Internic: ANI116 > E-mail: [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ad0 drivers revisited
Grigoriy Strokin wrote: > > On Mon, May 22, 2000 at 07:26:50PM -0400, Jim Weeks wrote: > > > > On Mon, 22 May 2000, Peter Radcliffe wrote: > > > > > > Define "it doesn't work" ? > > > > ad0: 4884MB [10585/15/63] at ata0-master using BIOSDMA > > ata1-slave: simplex device, DMA on primary only > > acd0: CDROM at ata1-slave using BIOSPIO > > Mounting root from ufs:/dev/ad0s1a > In my case, I see the message 'dma,dma -> pio,pio' > at this point. Maybe try /sbin/sysctl instead > of just sysctl? Have you all done a "man sysctl.conf" Kent > > > ad0: READ command timeout - resetting > > ata0: resetting devices .. done > > ad0: READ command timeout - resetting > > ata0: resetting devices .. done > > ad0: READ command timeout - resetting > > ata0: resetting devices .. done > > ad0: READ command timeout - resetting > > ata0-master: timeout waiting to give command=ef s=eb e=eb > > ad0: trying fallback to PIO mode > > ata0: resetting devices .. done > > > > > > > > It doesn't switch to pio mode or doesn't stop timeouts ? > > > > There is no change in the timeouts with or without adding the line to > > rc. At least it does eventually fall back to PIO. I understand from some > > of the posts that not every case is so. > > > > > If there was a fix known, for it to be scheduled, it would probably > > > already be in the tree. > > > > I was actually hoping that someone with a fix in the works would > > respond ;-) > > > > I do appreciate your response though. My late Father always said that two > > heads were better than one, even if one is a punkin head. Of course that > > one would be mine ;_) > > > > Jim Weeks > > A mind is a terrible thing to lose! How I miss mine.. > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- > === Grigoriy Strokin, Lomonosov University (MGU), Moscow === > === contact info: http://isabase.philol.msu.ru/~grg/ === > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make buildworld failing on libssh
Kris Kennaway wrote: > > On Thu, 25 May 2000, Adam Mackler wrote: > > > now, the only mystery left is how did it work for so long? > > Until recently the 5.0 crypto code hadnt diverged from 4.0 very much (and > would have worked fine) It is still broken right now any way. It doesn't know how to make twe.4. Kent > > Kris > > > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SB16 doens't work in 4.0-STABLE
Simo Kaartinen wrote: > > Hey, > > I installed 4.0-RELEASE, upgraded it to STABLE and my SB16 still > doesn't work. This problem has been the same from the beginning. > > I have tried pcm and sbc in kernel config, which from sbc has output in > dmesg (all > settings correct). I have also done all the necessary device nodes. > > Kernel compiles without any problems. Everything seems to be ok, but no > sound. > > line in kernel config: > device sbc0at isa? port 0x220 irq 5 drq 1 flags 0x15 > > dmesg output: > sbc0: at port 0x220-0x22f irq 5 drq 1 flags 0x15 on > isa0 > sbc0: setting card to irq 5, drq 1, 5 > > i think this is ok too (all the snd-devices has similar rights): > lrwxr-xr-x 1 root wheel 4 May 28 19:26 /dev/dsp -> dsp0 > crw-rw-rw- 1 root wheel 30, 3 May 28 19:02 /dev/dsp0 > > I have also tried dsp1 with similar rights but it has the same output: > > with mpg123: > Can't open /dev/dsp! > with xmixer: > /dev/mixer: Device not configured > with x11amp: > Unable to open the audio device > > I can't think of anything I should do differently. The soundcard works > proberly in > w9x so it isn't physically broken. > > If anyone has any idea what I should try, please let me know. You need to cd /dev ./MAKEDEV snd0 Then check to see if you have a mixer. The make device links things such as the mixer. Kent > > -- > Simo Kaartinen > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: SB16 doens't work in 4.0-STABLE
Simo Kaartinen wrote: > > On Thu, 01 Jun 2000 12:55:33 Kent Stewart wrote: > > On my SB-16 system > > > > My kernel has > > > > # pcm Sound Device Driver > > device pcm > > No other ideas. > > > > Kent > > I lacked the pcm0 from my kernel configuration. What was I thinking. > Thank you > very much, now my SB16 works just fine. When it works on someone else's machine as easy as this does, it has to be something simple. Finding it may not be :). If you use KDE, make sure you change the kscd device from /dev/mtacd0c to /dev/acd0c. You also have to set cddb to us.cddb.com. The default www.cddb.com doesn't work. Once you do an update, you have a number of cddb servers. Have fun, Kent > > -- > Simo Kaartinen > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: todays kernel not compiling.
Lauri Laupmaa wrote: > > Hi > > I get: > > ../../i386/i386/in_cksum.c: In function `in_cksum': > ../../i386/i386/in_cksum.c:238: `__func__' undeclared (first use this > function) > ../../i386/i386/in_cksum.c:238: (Each undeclared identifier is > reported only once > ../../i386/i386/in_cksum.c:238: for each function it appears in.) > ../../i386/i386/in_cksum.c: In function `in_cksum_skip': > ../../i386/i386/in_cksum.c:426: `__func__' undeclared (first use this > function) > *** Error code 1 Did you cvsup and retry it. I cvsup'ed today and didn't have any problems doing a make world and kernel. Kent > > TIA > > L. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make world fails : file exists
Dan Langille wrote: > > In my continuing 4-day saga to get 4.0-stable compiled, I encountered > the following error during make world: > > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl - > I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 - > I/usr/obj/usr/src/i386/usr/include -c > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c -o toke.o > mkdir: build: File exists > *** Error code 1 > > Stop in /usr/src/gnu/usr.bin/perl/libperl. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. Hi Dan, Did you remove the files from /usr/obj/*? I've done 3 cvsups and builds in the last two days on 3 different machines and haven't had any problems. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make world fails : file exists
Dan Langille wrote: > > On 5 Jul 2000, at 12:17, Kent Stewart wrote: > > > Dan Langille wrote: > > > > > > In my continuing 4-day saga to get 4.0-stable compiled, I encountered the > > > following error during make world: > > > > > > cc -O -pipe -I/usr/obj/usr/src/gnu/usr.bin/perl/libperl - > > > I/usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5 - > > > I/usr/obj/usr/src/i386/usr/include -c > > > /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/toke.c -o > > > toke.o mkdir: build: File exists *** Error code 1 > > > > > > Stop in /usr/src/gnu/usr.bin/perl/libperl. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > > Hi Dan, > > > > Did you remove the files from /usr/obj/*? > > > > I've done 3 cvsups and builds in the last two days on 3 different > > machines and haven't had any problems. > > Yep. I did this: > > chflags -R noschg /usr/obj/; > rm -rf /usr/obj/*; > rm -rf /usr/tmp/*; That takes care of original files with permission problems. I don't do make world's. I read where that was a good way to ruin your universe and started doing buildworlds, creating and installing the kernel, rebooting to single user mode to do the installworld. The way it was explained to me was that left you with your original world via /kernel.old in case something happened. Since I'm not having any problems and don't have any ideas at this point, are your just updating your 4.0-Stable or are you moving from 4.0R to 4.0S? Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: buildkernel failure: netinet6/esp_core.c
Lars Eggert wrote: > > Building a kernel (config file attached) on a freshly updated -stable > system fails with: > > cc -c -O3 -pipe -funroll-loops -fomit-frame-pointer -fno-builtin -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include > -DXBONEHACK -DMAX_GIF_NEST=2147483647 -D_KERNEL -include opt_global.h -elf > -mpreferred-stack-boundary=2 ../../netinet6/esp_core.c > ../../netinet6/esp_core.c: In function `esp_descbc_decrypt': > ../../netinet6/esp_core.c:319: void value not ignored as it ought to be > ../../netinet6/esp_core.c:238: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_descbc_encrypt': > ../../netinet6/esp_core.c:440: void value not ignored as it ought to be > ../../netinet6/esp_core.c:345: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_decrypt': > ../../netinet6/esp_core.c:571: void value not ignored as it ought to be > ../../netinet6/esp_core.c:519: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_blowfish_cbc_encrypt': > ../../netinet6/esp_core.c:649: void value not ignored as it ought to be > ../../netinet6/esp_core.c:598: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_cast128cbc_decrypt': > ../../netinet6/esp_core.c:743: void value not ignored as it ought to be > ../../netinet6/esp_core.c:687: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_cast128cbc_encrypt': > ../../netinet6/esp_core.c:818: void value not ignored as it ought to be > ../../netinet6/esp_core.c:765: warning: `error' might be used uninitialized > in this function > ../../netinet6/esp_core.c: In function `esp_rc5cbc_decrypt': > ../../netinet6/esp_core.c:1064: void value not ignored as it ought to be > ../../netinet6/esp_core.c:1014: warning: `error' might be used > uninitialized in this function > ../../netinet6/esp_core.c: In function `esp_rc5cbc_encrypt': > ../../netinet6/esp_core.c:1134: void value not ignored as it ought to be > ../../netinet6/esp_core.c:1085: warning: `error' might be used > uninitialized in this function > *** Error code 1 I just finish cvsup'ing and have completed a buildworld and buildkernel without any problems. Did you cvsup'ed such that you have the crypto files since they are part of src-all now days. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: bioscall.s
Richard Stanaford wrote: > > --- Kent Stewart <[EMAIL PROTECTED]> wrote: > > > Just to make sure that from /usr/src you are doing a > > > > make installkernel KERNEL=NOVA > > I may have used .. > > make buildkernel KERNEL="NOVA" The quotes are evil. One my first kernel I left if buildkernel kernel=NOVA and it didn't work just like yours did. That was part of the reason I needed 15 minutes for my first good build on 7/7. > > If the quotes are evil I would have expected it to make more than just 'as' > mad. I'm going to CVSup, buildworld, and buildkernel again tonight *without* > the quotes to ensure I did it right. > > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty. Recently or before 7 July. My first build was on a P-II 400 and it is only slightly faster than my server, which is a Celeron 433. Kent > > -Richard > > __ > Do You Yahoo!? > Get Yahoo! Mail Free email you can access from anywhere! > http://mail.yahoo.com/ -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: bioscall.s
Richard Stanaford wrote: > > --- Kent Stewart <[EMAIL PROTECTED]> wrote: > > > > I am doing this on a 336MHz Celeron. I did a clean upgrade to STABLE from > > > 4.0-RELEASE on my DX4/100 box and I did use the quotes without difficulty. > > > > Recently or before 7 July. My first build was on a P-II 400 and it is > > only slightly faster than my server, which is a Celeron 433. > > Recently. > > I did a successful upgrade from 4.0-RELEASE to STABLE on the DX4/100 just last > week. The changes to binutils had been committed for some time I believe. They were just in when I made my system on late 7 July. The other thing is that the kernel it makes will be called NOVA and you either have to setup /boot/loader.conf to use it or do the chflags sequence to mv NOVA kernel. I've been doing the mv sequence. I like being able to build/install-kernel KERNEL=GENERIC. Otherwise kernel.GENERIC goes back to your original release. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://www.3-cities.com/~kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upgrading from 4.0release to 4.0stable
Justin wrote: > > Does nayone know a current or updated DOC or LINK to this info, or is it > as simple as a 3.4 release to 3.4 stable procedure? If anyone has any tips > please send them my way @ [EMAIL PROTECTED] > > I am not yet subscribed to the mailing list. > > Thanks for any assistance you can provide me! You have to cvsup and then read /usr/src/UPDATING. You can cvsup now but I don't if it will build. It was broken all day and I'm in the middle of a buildworld. Someone else may have finished their buildworld. Will try the "make buildkernel KERNEL=" next. Kent > > Justin > > -- > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.x stable compile error (Kernel)
Mark Ovens wrote: > > On Thu, Jul 20, 2000 at 09:26:53PM +0200, Johan Mulder wrote: > > On Thu, Jul 20, 2000 at 01:36:22PM -0400, Forrest Aldrich wrote: > > > I've done a 'make clean' in /usr/src, and this error keeps coming up. Looks >like a bug... is this known? > > > > > > A CVSUP was just performed, so the archive is up-to-date. > > > > > > ===> agp > > > make: don't know how to make agp_if.c. Stop > > > *** Error code 2 > > *snip* > > > > I've got that too on a box which was just installed today. > > Is there any solution for this? > > > > Re-cvsup I think. I just cvsup'd at 18:30 BST and it built OK. Did you do a config or a buildkernel sequence. I just got through upgrading 3 systems without any problems. I followed the instructions in /usr/src/UPDATING where you use a make buildkernel/installkernel. Kent > > > -- > > Johan "RTFM" Mulder > > Vuurwerk System Administration > > > > "Why do we have to hide from the police, Daddy?" > > "Because we use vi, son. They use emacs." > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- > If I buy a copy of WinDelete, and it doesn't delete Windows, > am I entitled to my money back? > > FreeBSD - The Power To Serve http://www.freebsd.org > My Webpage http://ukug.uk.freebsd.org/~mark/ > mailto:[EMAIL PROTECTED] http://www.radan.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: nlist - REHASH
Tom wrote: > > On Sat, 22 Jul 2000, Richard Stanaford wrote: > > > All, > > > > I have been carousing the mailing lists, both -stable and -questions, and I > > have not found a definitive answer for this problem... > > > > PROBLEM : top (among others) is broken after going to STABLE. > > > > I know this is a FAQ. What is the preferred method for fixing this? Should I > > implement the patches referred to by : > > > > http://www.geocrawler.com/archives/3/152/2000/5/0/3727446/ > > > > or should I fix the loader? What is exactly wrong with the loader and how is > > it fixed? > > The usual problem is that you install a new kernel, but not the rest of > the world. If that is indead what you've done, fix that first before > worrying about anythig else. Not in this case. If you boot to single user mode and exit, top doesn't work. If you shutdown now to single user mode and exit, top works. There is obviously something broken in the way the loader deals with single user mode. Kent > > Tom > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: README.TXT and RELNOTES.TXT not updated before release tag?
"Jordan K. Hubbard" wrote:
>
> Argh! I knew I'd forgotten something, but at 4:30am I just couldn't
> remember what.. :-)
>
> I've also just recently moved machines and I couldn't find my TODO
> list from 4.0, so what's long been on my checklist of things to verify
> just didn't get checked. Not a crisis in any case since I'd still not
> actually rolled the release (that's happening now) so I had the
> chance, after reading your mail, to fix things up. Thanks for the
> much-needed reminder!
I have all 3 of my machines running builds of 4.1-stable and
everything seems to be cool.
One thing I haven't seen is how or what do you do with ports. Do you
rebuild in general or what?
Kent
>
> - Jordan
>
> > --==_Exmh_481686077P
> > Content-Type: text/plain; charset=us-ascii
> >
> > Hi all--
> >
> > I just cvsup-ed my sources this morning, and it looks to me like the
> > versions of README.TXT and {i386,alpha}/RELNOTES.TXT that got tagged for
> > RELENG_4_1_0_RELEASE still say "4.0-STABLE" rather than "4.1-RELEASE"
> > (at the tops of the files). Is it just me, or does someone need to do an
> > edit->slidetags->reroll on these?
> >
> > Clue-by-four cheerfully accepted if it's just me.
> >
> > Bruce "nitpicker of RELNOTES.TXT" Mah.
> >
> >
> >
> >
> > --==_Exmh_481686077P
> > Content-Type: application/pgp-signature
> >
> > -BEGIN PGP SIGNATURE-
> > Version: PGPfreeware 5.0i for non-commercial use
> > MessageID: 3drolqidq6jWwz0G917HheAOOLeEbcVS
> >
> > iQA/AwUBOX8do9jKMXFboFLDEQKipACg3HVvk7GUig1/Zy3HzzTn4up9DTMAnja9
> > GAz+Tn5YZOIHOhF/fI0gCWoI
> > =soMD
> > -END PGP SIGNATURE-
> >
> > --==_Exmh_481686077P--
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-stable" in the body of the message
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
--
Kent Stewart
Richland, WA
mailto:[EMAIL PROTECTED]
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/
Bomber dropping fire retardant in front of Hanford Wild fire.
http://kstewart.urx.com/kstewart/bomber.jpg
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: src code freeze is over for RELENG_4
Nik Clayton wrote: > > On Thu, Jul 27, 2000 at 11:08:19AM -0400, Robert Watson wrote: > > > > On Thu, 27 Jul 2000, Jordan K. Hubbard wrote: > > > > > You may now go back to whacking on the RELENG_4 branch with the usual > > > degree of -stable discretion. Good release, guys. Next stop is > > > 4.2-RELEASE in mid-November 2000! > > > > And post-RSA Patent :-). Time to integrate the crypto code into the base > > distribution (src-base), I guess. > > Is it worth doing a (non-CD) 4.1.5 release the day after the patent expires? Aren't there 3 or 4 countries out there that we still can't deal with. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Suggestion for change of /usr/src/UPDATING (was: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels)
Mark Ovens wrote: > > On Wed, Aug 02, 2000 at 10:49:12AM -0700, John Reynolds~ wrote: > > > > [ On Wednesday, August 2, Warner Losh wrote: ] > > > : I am not in favour of putting *that* in UPDATING. Either suggest an > > > : appropriate entry in /boot/loader.conf: > > > > > > Actually, make installkernel was fixed so that you don't need to do > > > this. > > > > > > > It was? Did I miss a "HEADS UP" somewhere along the line? I knew that this was > > the behavior in -current and it was going to be "MFC"ed ``at some point'' but > > when did it occur? > > > > Seems like this would screw people like me who edited their /boot/loader.conf > > file unless we change it back to look for /kernel. > > > > Thanks for the notice ... I'll make sure to look at stuff and edit > > /boot/loader.conf appropriately before I type "reboot" the next time :) > > > > If you add > > makeoptions KERNEL=kernel #Build kernel "foo" and install "/foo" > > to your kernel config file it will install it as /kernel without this > change; and back up your old one as /kernel.old. I would expect this > line in the config file will be harmless (albeit redundant) when the > change is MFC'd so you won't have to edit /boot/loader.conf. I have to make a point here and that is I like the current arrangement. I would much rather have installkernel make a file called MYKERNEL than have it make all kernel's as "kernel". I think that as we follow Stable or Current, we need to create a GENERIC that goes along with them. When you don't have a clue, boot GENERIC. It may not solve anything but it is a data point. I don't like having all of my kernels called kernel because of this. I would much rather mv RUBY to kernel than mv kernel to kernel.GENERIC or GENERIC and re-installkernel for RUBY. I follow upgrades with my general setup and only at significant places do I create a GENERIC. I have a shell script that moves RUBY, for example, to kernel and I don't touch GENERIC. Kent > > HTH > > > -Jr > > > > -- > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > | John Reynolds WCCG, CCE, Higher Levels of Abstraction | > > | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | > > | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- > If I buy a copy of WinDelete, and it doesn't delete Windows, > am I entitled to my money back? > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > mailto:[EMAIL PROTECTED]http://www.radan.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 3.x -> 4.x and disklabel
Andrey Lakhno wrote: > > Hi ! > > I'v just cvsupped from 3.X-Stable to 4.1-Stable. > make world was successful. > > Need I change my disk label using /sbin/disklabel ? > if 'yes' what command issue ? What I remember is seeing the boot info replaced automatically. You didn't say anything about doing an appropriate buildkernel and installkernel. If you make it through that sequence in /usr/src/UPDATING, I think you will find everything has been updated. Kent > > -- > Best regards, > Andrey > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ Bomber dropping fire retardant in front of Hanford Wild fire. http://kstewart.urx.com/kstewart/bomber.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: mouse question....
Gary Kline wrote: > > Hi, Y'all, > > This is a long shot, but here goes. --On my other FBSD system > which is as 4.0, the mouse won't work. A friend just checked > the hardware ports, switched the mouse from COM1 to COM2. (COM2 > or, in the case of my modem, /dev/cuaa1, is working.) Zip; > nothing. He tried the mouse on this system on the other. Again, > nothinng. He thinks that in my upgrading to 4.0, part of my > mouse software may have been hosed. > > Any suggestions how I can diagnose the software side of this? I have always use the configure option of sysinstall to figure my mice out. Kent > > I'm stumped. > > thanks, > > gary > > -- >Gary D. Kline [EMAIL PROTECTED] Public service Unix > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Can't mount 4.1 CDROM's
Vivek Khera wrote: > > >>>>> "KS" == Kent Stewart <[EMAIL PROTECTED]> writes: > > KS> The only way I can get the CD out of the cdrom drive has been to reboot. > > If you type "eject -f acd0" you can manually eject the disk, but it > still is unable to finish the mount or umount operations, and your > mount point will look like an executable file rather than a directory, > and have a date in 1969. I saw that /cdrom had changed to cdrom* when I ran my ll alias. The eject will get me around rebooting the computer. That was the most irritating part. I couldn't eject and the device was permanently busy at that point. I was having problems building bluefish port and had to ftp the package from my Win 2000 Server. That was the only non-FreeBSD system that could read the CDROM. > > Several other people have reported this in reply to my query over the > last few days on this list. No fix has been forthcoming. > > My workaround is to run the 4.1-R kernel.GENERIC that was provided > when I did my 4.1-R installation. I rebuilt my kernel.GENERIC last night on my server. That didn't help and that is when I added my message to the queue. I had a suggestion from Sean to use cvsweb to back out the change to atapi-cd.[ch]. Thanks, Kent > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Vivek Khera, Ph.D.Khera Communications, Inc. > Internet: [EMAIL PROTECTED] Rockville, MD +1-301-545-6996 > GPG & MIME spoken herehttp://www.khera.org/~vivek/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ATAPI CD-ROM fails to mount on 4.1-STABLE
Wobbly wrote: > > Had a perfect system until yesterday, running 4.1-STABLE. > > cvsup -g -L 2 stable-supfile (previous cvsup was around a month ago) > > No changes required to kernel config file. > > make buildworld > make buildkernel KERNEL=* > make installkernel KERNEL=* You only have to go back to 20 August. The changes that broke atapi-cd.[ch] were made by SOS on 22 Aug 2000. The cvs log shows $FreeBSD: src/sys/dev/ata/atapi-cd.c,v 1.63 $FreeBSD: src/sys/dev/ata/atapi-cd.h,v 1.19 This was after the date of my kernel.old and my cvsup and rebuild last night. Kent > > single user > > make installworld > mergemaster > reboot > > CDROM's won't mount. > > The mount directory /cd0 as allocated in /etc/fstab... > > /dev/acd0c /cd0cd9660 ro,noauto > > ...has turned itself into a FILE! Please explain? > > -r-xr-xr-x 1 root wheel 0 Jan 1 1970 cd0 > > Check the date out!! > > If I go try & mount my other cdrom drive, /cd1, it returns zero but > won't list anything within the directory. cd /cd1 then umount /cd1 > predictably returns device in use error, so it seems to function but > obviously not well enough to access it. > > So I must reboot. Things revert to normal... > > drwxr-xr-x 2 root wheel 512 Jun 21 08:57 cd0 > drwxr-xr-x 2 root wheel 512 Jun 21 08:57 cd1 -- (I'm GMT +10) > > This time I try mounting /cd1 first with a Windows 2000 CD. Zero result > but still won't list the contents. umount /cd1, bung FreeBSD 4.0 RELEASE > in the drawer then mount /cd1. Zero result but when I... > > bash-2.03# ls /cd1 > /cd1 > Aug 25 23:02:27 /kernel: RRIP without PX field? > Aug 25 23:02:27 /kernel: RRIP without PX field? > > bash-2.03# mount /cd1 > mount /cd1: not a directory > > bash-2.03# umount /cd1 > umount: umount of /cd1 failed: Invalid argument > > bash-2.03# ls -l /cd* > -r-xr-xr-x 1 root wheel 0 Jan 1 1970 /cd1 > > /cd0: > > Once again, the directory has become a file stamped with a date from > the dark ages. > > Sorry team - this is not my idea of STABLE. > > Rosco. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: mounting ATAPI cdroms
Allan Strand wrote: > > Have the problems with mounting ATAPI CDROMs been resolved in the > stable branch? > > I did a fresh cvsup last night (9/3/00), made world and a new kernel > this morning, and I am still unable to mount my CDRW drive. > Potentially this is a problem with my hardware, although the drive is > able to write CDROMs and play music CDs. If mounting CDROMS is > working for everyone else, then I'll suspect my hardware. >From http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ata/atapi-cd.c it was fixed on 25 August 2000. The mounting error made it look like an audio cd was being mounted. The messages were > : > : RRIP without PX field? > : > : Aug 25 03:59:15 jade /kernel: RRIP without PX field? > : > : Aug 25 03:59:15 jade /kernel: RRIP without PX field? If you are still seeing these, then you didn't install your kernel :). Kent > > a. > > -- > Allan Strand, Biologyhttp://linum.cofc.edu > College of Charleston Ph. (843) 953-8085 > Charleston, SC 29424 Fax (843) 953-5453 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: problems with make world (Sunday)
Nikita Proskourine wrote: > > Hi all, > > I am a newbie to FreeBSD development, so please bear with me. I am > currently using FreeBSD-4.0 RELEASE. I did a fresh cvsup (using RELENG_4 > tag, that would get me a stable branch, right?) and "make world" on Sunday > and the build failed somewhere in objc contribs for gcc. > > I made logs of the build and will send them later today. In the meantime, I > was wondering if this is a known problem and whether there are workarounds > for this. You didn't read /usr/src/UPDATING. It tells you that you can try a "make world" but if it fails don't complain until you have tried the buildworld, build[install}kernel, installworld sequence. A lot changed between 4.0 and 4.1. For example, a kernel build using the config is not supported after a cvsup. It may work but there can be changes that the buildkernel mode will process. Your kernel config file can be different. You need to compare what you have against GENERIC. It has been 4 or 5 days since I did a cvsup and all of the builds and installs. Kent > > Nikita. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1 STABLE broken since today!
[EMAIL PROTECTED] wrote:
>
> >
> > As commented on freebsd-current, this seems to have hit the -CURRENT
> > kernel at the same time. Someone should *not* have MFC'd some change
> > immediately. Not clear who yet. I'm suspicious of the sbappend() changes
> > that have been going in recently.
>
> 1. The value of diff in chgsbsize was always positive
> (unsigned - unsigned results in an unsigned value).
> This causes bogus values in ui_sbsize.
>
> 2. chgsbsize was not called as when the 3-way tcp handshake
> for incoming connection completed (in interrupt context).
> This results in sb_lowat being 0, causing infinite loop in
> kernel when attempting to write.
>
> sb_lowat should probably be set to 1 when sb_hiwat is 0
>
> The following patch works for me.
I added these changes to my system and they work for me too.
Kent
>
> Index: sys/kern/kern_proc.c
> ===
> RCS file: /home/ncvs/src/sys/kern/kern_proc.c,v
> retrieving revision 1.72
> diff -u -r1.72 kern_proc.c
> --- sys/kern/kern_proc.c2000/08/30 04:49:07 1.72
> +++ sys/kern/kern_proc.c2000/08/31 03:56:30
> @@ -210,7 +211,7 @@
> if (uip == NULL)
> uip = uicreate(uid);
> s = splnet();
> - diff = to - *hiwat;
> + diff = (rlim_t) to - (rlim_t) *hiwat;
> /* don't allow them to exceed max, but allow subtraction */
> if (diff > 0 && uip->ui_sbsize + diff > max) {
> (void)uifree(uip);
> Index: sys/kern/uipc_socket2.c
> ===
> RCS file: /home/ncvs/src/sys/kern/uipc_socket2.c,v
> retrieving revision 1.63
> diff -u -r1.63 uipc_socket2.c
> --- sys/kern/uipc_socket2.c 2000/08/30 00:09:57 1.63
> +++ sys/kern/uipc_socket2.c 2000/08/31 03:54:33
> @@ -431,6 +431,14 @@
> p->p_rlimit[RLIMIT_SBSIZE].rlim_cur)) {
> return (0);
> }
> + /* XXX: Incoming tcp setup handshake completes in software interrupt.
> +* Normally the hash table has an uidinfo structure for the
> +* relevant uid (unless setuid() was called after listen()).
> +*/
> + if (p == NULL && !chgsbsize(so->so_cred->cr_uid, &sb->sb_hiwat, cc,
> + RLIM_INFINITY)) {
> + return 0;
> + }
> sb->sb_mbmax = min(cc * sb_efficiency, sb_max);
> if (sb->sb_lowat > sb->sb_hiwat)
> sb->sb_lowat = sb->sb_hiwat;
>
> - Tor Egge
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
--
Kent Stewart
Richland, WA
mailto:[EMAIL PROTECTED]
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Stop error in make world
Bill Moran wrote: > > John Reynolds~ wrote: > > > Well, I just cvsup'ed 1 hour ago and built world. No problems. That segfault > > you got when building perl looks really odd. Other people have said that > > segfaults during buildworld are generally hardware problems. Most likely > > memory. > > I'd be surprised ... considering I did a successful `make world' about a > month ago with no problems, and I've done many compilations (Apache, > MySQL, php, ssh) on this machine with no problems prior to this. Still, > it's a possibility, things do wear out/break/etc. > > > Any chance of you swapping out the memory in the machine? > > That's pretty much a last resort ... my goal is to fix this without > having to drive 3.5 hours to the location where it exists. If nothing > else works, I'll do that. > > > Anyway, just reporting "no errors" here with a fresh tree. > > Well, that's good news, it means I've botched something. I think the > mistake is that I accidentally got a 3.X-STABLE tree over top the 4.X > tree and the version of perl from 3.X (whatever version that is) isn't > up to doing some of the chores that are required for a 4.X make world. > My plan of attack at this point is: > make -k buildworld > make installworld > make buildworld I think if you really loaded a 3.5 tree on top, you will need to follow the cvsup upgrade path for 3.5 to 4.1 in /usr/src/UPDATING. You could also upgrade the binaries to 4.1-R and then rebuild userland and the kernel. There were such massive changes to /etc and all of the /binutils. I thought my "i" key was going to wear out running mergemaster :). Kent > > If at that point I have no errors, I'm home free to rebuild a current > kernel and make installworld again. > > If I'm still having trouble. I'm going to try cvsdowning to 4.0-STABLE > (which is what the machine was before this all started) and see if I can > get it working. > If that doesn't work and I can still get ssh access to the machine, I'll > get really desperate and try getting a 3.5.1 machine on here. > If that doesn't work, I'm driving 3.5 hours to do a clean installation > (please no) > > If anyone has any better attack plans, I'm interested to hear them. > > Thanks for all the help so far. > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1-STABLE fails to 'buildkernel'?
"Crist J . Clark" wrote: > > On Tue, Sep 12, 2000 at 01:31:44AM -0300, The Hermit Hacker wrote: > > On Mon, 11 Sep 2000, Francisco Reyes wrote: > > > > > On Mon, 11 Sep 2000 11:25:26 -0700, Gregory Sutter wrote: > > > > > > >I have the same problem. I also desperately need to build some > > > >-STABLE systems for my new job. Anyone know what's causing the > > > >breakage? > > > > > > Why don't you cvsup to a prior date? > > > > doesn't it defeat the point of calling it -STABLE if it can't compile? :) > > Not compiling is not a problem. If it is _really_ broken (and not > pilot error), just wait for it to get fixed and try again. You still > have your old system purring along just fine. > > What SUCKS is when you manage to get through a make-world without an > error, but the running system is broken. /That/ is something to whine > about. (And you just want to slug that first one that says, "Just use > the backups you made before the make-world." I do backup first, but > restoring is still a non-trivial pain in the *ss. And if you didn't > backup, especially a production system, you asked for it, bub.) This is all part of the reason why I do a buildworld, build[install]kernel, and finally do my installworld. When something like this happens, my kernel.old and my user land are still in sync. Kent > -- > Crist J. Clark [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.1-STABLE fails to 'buildkernel'?
Mike Nowlin wrote: > > > > What SUCKS is when you manage to get through a make-world without an > > > error, but the running system is broken. /That/ is something to whine > > > about. (And you just want to slug that first one that says, "Just use > > > the backups you made before the make-world." I do backup first, but > > > restoring is still a non-trivial pain in the *ss. And if you didn't > > > backup, especially a production system, you asked for it, bub.) > > > > This is all part of the reason why I do a buildworld, > > build[install]kernel, and finally do my installworld. When something > > like this happens, my kernel.old and my user land are still in sync. > > > > I kept my mouth shut at the time, since I knew it would be fixed in a > couple of days and the machine I was upgrading wasn't anything really > important, but the problem a couple weeks ago where telnetting into a > system or starting X on it caused it to blow up didn't exactly strike me > as "stable". kernel.old didn't work since the userland had changed enough > to make ps, top, etc. to stop working -- un-cvsup it and rebuild... > > This problem shows up more often when you update sources weekly or > so. Daily doesn't seem to be a big problem - kernel.old is usually > good; going from 4.0-RELEASE to 4.1-STABLE can cause headaches. I have 3 machines that are running builds within 2 or 3 weeks of each other. The two that can go down are built much more often. When everything works and there are changes I want, I cvsup and build my server. The other two can be down for a short while but the server isn't upgraded unless the other two are working. Things change and so it can't be too far behind. I will upgrade one of them if it appears something is broken. I haven't done it right now because I have some seti wu's that are getting too old. > > Just goes to show you that completely trusting > [build|install][world|kernel] and friends isn't completely > goof-proof. Creating a program that compiles flawlessly but still doesn't > work doesn't require much cranial activity. That is very true but you don't get hit by errors like that as frequent as you are by builds that won't finish. The changes are supposed to be tested before they are MFC'ed to stable from current. The telnet/ping problem existed in current and those changes probably shouldn't have been MFC'ed until they were fixed. With the common breakage, if you haven't installed anything, you haven't damaged anything and can wait for the "Maytag repairmen" to fix things :). Kent > > (BTW: Thanks, guys, for fixing that problem! Got my shiny new Toshiba > 4360ZDVD laptop running -STABLE now - X, sound, pcmcia, > everything! Although the S3 Savage-IX patch for XFree-3.3.6 has some > problems (with work-arounds), it's kicking along nicely!) > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > Understated/funny man-page sentence of the current time period: > > >From route(4) on FreeBSD-3.4, DESCRIPTION section: > "FreeBSD provides some packet routing facilities." > ...duh... > > Mike Nowlin, N8NVW [EMAIL PROTECTED] http://www.viewsnet.com -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: installworld on recent cvsup RELENG_4 fails
"B. Scott Michel" wrote: > > This has surfaced for me a few times over the last couple of days -- > installworld dies during perl install attempting to rebuild the SDBM_File > libsdbm.a library. Not really worth sending the output, since installworld > appears to be attempting to reconstitute libsdbm.a in the source and not > in the object directory. > > It's possible to hack around this with a 'make NOPERL=true installworld', > but it is annoying. I tried a couple of things when this first hit me. You can make the installworld work if you add chmod to Makefile.inc1 line 312. I added it in front of the chown. You probably could locate it, cd, and "chmod 755 libsdbm.a". That is what it is trying to do but chmod isn't on the list, which is being created at 312. It handled it properly during the next buildworld. Kent > > -scooter > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Installworld failed in /usr/src/share/timedef
Brian McDonald wrote: > > All, > > An installworld of -stable from fresh sources (about 6:00PM EDT) today dies > with the following: > > [hand copy] > > install: /usr/share/locale/tr_TR.ISO_8859-9/LC_TIME: No such file or > directory > *** Error code 71 > > /usr/src/share/timedef/tr_TR.ISO_8859-9.src is present, with the > corresponding .out file in /usr/obj/usr/src/share/timedef/. > /usr/share/local/tr_TR.ISO_8859-9 was missing. > > Reverting /usr/src/share/timedef/Makefile to version 1.11 allows > installworld to complete without error. 1.12 added the info for > tr_TR.ISO_8859-9, but I'm not sure what was missed. The commit message for > HEAD is included below. It was MFCd right afterwards. It looks like ache added that path around 6:26 EDT your time. I would try recvsuping. Kent > > Brian > -- > Brian McDonald > Microsoft Certified Professional > Columbus, Ohio > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Andrey A. Chernov > Sent: Saturday, September 16, 2000 2:07 PM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: cvs commit: src/share/timedef tr_TR.ISO_8859-9.src Makefile > > ache2000/09/16 11:06:30 PDT > > Modified files: > share/timedefMakefile > Added files: > share/timedeftr_TR.ISO_8859-9.src > Log: > Add tr_TR timedef > > Submitted by: Evren Yurtesen <[EMAIL PROTECTED]> > > Revision ChangesPath > 1.12 +2 -1 src/share/timedef/Makefile > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe cvs-all" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Makeworld is dying...
"Paul A. Howes" wrote: > > All- > > When I attempt a buildworld on a brand new FreeBSD system (IBM/Cyrix-166+, > 64MB memory, 20GB Maxtor drive), it dies while building the ncurses library. > This happen whether it's the version of the source code on the 4.1 CD-Rom > disc, or the latest and greatest 4-STABLE code from a cvsup. Any help would > be appreciated. The tail of the trace log is included below. Signal 11's during a buildworld are usually caused by memory and a few things such as cpu cooling. I finished a buildworld at 1:30 PDT (about 2 hours before your message arrived) and I didn't have any problems. Do you have another 64MB of memory that you could switch as a test of your memory. Kent > > Thanks! > > -- > Paul A. Howes > [EMAIL PROTECTED] > > cc -fpic -DPIC -O -pipe -I. -I/usr/src/lib/libncurses - > /usr/src/lib/libncurses/../../contrib/ncurses/ncurses -I/usr/src/lib/libncur > ses/../../contrib/ncurses/include -Wall -DFREEBSD_NATIVE -DNDEBUG -DHAVE_CON > FIG_H -DTERMIOS -I/usr/obj/usr/src/i386/usr/include -c > /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/alloc_entry.c -o > alloc_entry.So > > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 > > Stop in /usr/src/lib/libncurses. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: UDMA write errors on stable and release
David Uhring wrote: > > On Wed, 20 Sep 2000, Kent Stewart wrote: > > Charlie Root wrote: > > > Hi, > > > > > > I am not sure if this is the right forum to ask, but since it concerns > > > 4.1 stable I might as well try. > > > > > > Since switching to a new motherboard I get the following errors: > > > > > > Sep 14 22:37:27 oblomow /kernel.GENERIC: ad0: UDMA ICRC WRITE ERROR blk# > > > 2523344 retrying Sep 14 22:37:27 oblomow /kernel.GENERIC: ad0: UDMA ICRC > > > WRITE ERROR blk# 2535904 retrying > > > > > > Not only with this installation ( 4.1 Release ) but also with 4.1 stable > > > (see attached messages file) > > > > > > I changed from an Abit AX5 motherboard with a K6 to an Abit KT7 with a > > > Duron 600 (Via chipset). > > > Eventually these errors disappear because the system decides to switch to > > > PIO4 mode for disk access. I have gone through the mailing list archive > > > and found several more reports about this, but no solution there. > > > > > > The cable used to attach these UDMA33/66 capable drives is new and not > > > too long and should be capable of handling these speeds. The disks that > > > worked are 2 * WDC AC34300L. I also tried a new IBM GXP 30 GB with the > > > same result. > > > > > > Suggestions anyone? > > > > Do a "man ata" and learn how to use sysctl to turn off UDMA33+ on your > > motherboard. The Via chips and the ata driver seem to be very > > sensitive to some UDMA drive combinations. You can corrupt your data > > in really bad situations, which occured at 4.0-Release, and degrading > > to PIO 4 or using SCSI HD's seems to be the only solution at this > > point. The sysctl commands go into /etc/sysctl.conf > > > > Kent > > > > > Marc Albers > > > > > > /var/log/messages: > - - snipped - - > > I had the identical problem with 4.0-R on a FIC-VA503A MB using the VIA MVP4 > chipset. Do you mean that the VIA KT133 chipset for the Athlon/Duron in > UDMA66 mode is unsupported by FreeBSD, also? If so, this is really a shame > because the UDMA66 chipset improves Bonnie benchmarks by 25-30% with OpenBSD > and Linux. BTW, on a FIC PA2013 MB with the MVP3 chipset, FreeBSD fully > supports UDMA33 mode, at least for the HD. If you go back to the archives and look at the trouble, most of the UDMA problems have been associated with the Via chips (in general) and UDMA. Some combinations of HD's and MB's are worse than others. There are people with UDMA drives that aren't having problems. There are people with UDMA drives that were being trashed during the boot. There are people that replaced the 80-pin UDMA cables with 40-pin cables to get around the problem. I have 4 UDMA66 drives hooked up to 440bx boards that don't have problems unless I try to boot them dirty and I get the message on one system. As soon as I fsck the drives, the problem went away. I don't think that 4.1-Stable has as many problems as 4.0-Release did. I don't know any more than this. They transfer data significantly faster in UDMA mode. Kent > > Dave -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Odd log entries...an attempted breakin?
Kris Kennaway wrote: > > On Wed, Sep 20, 2000 at 10:09:16AM -0400, Brandon Fosdick wrote: > > For the last week or so I've been seeing the following entries in > > /var/log/messages: > > > > Sep 17 01:17:11 nbf-27 rpc.statd: Invalid hostname to sm_mon: > > ^D÷ÿ¿^D÷ÿ¿^E÷ÿ¿^E÷ÿ¿^F÷ÿ¿^F÷ÿ¿^G÷ÿ¿^G÷ÿ¿%08x %08x %08x %08x %08x %08x > > %08x %08x > > Someone is trying to exploit a root hole in the Linux rpc.statd. > ou don't have anything to worry about running FreeBSD here :-) Is that what the Tribal Flood people are doing or is this something different? Kent > > However, firewalling is always a good idea. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Correct sequence for keeping a 4.1 system stable.
Jon Paterson wrote: > > If these seem like trivial questions please do not flame me, I have never > attempted to do this before and do not want to damage a working system! > > As far as I have researched I need to perform the following actions: > > 1 get the up to date source (using one of the cvs tools) > > 2. make buildworld > > 3. make installworld > > 4. run mergemaster. > > 5. rebuild kernel ??? > > 6. reboot (and pray!) You need to read /usr/src/UPDATING. It will let you run an installworld before you do a buildkernel but the section on updating 4.x to 4.x-stable suggests the sequence make buildkernel KERNEL=YOUR_KERNEL make installkernel KERNEL=YOUR_KERNEL in between the buildworld and the installworld. YOUR_KERNEL is your kernel config file. I don't have to boot to single user mode before I run my installworld. That isn't always the case. Kent > > is this correct or have I missed something out? I assume that the src from > the updates are for the system only, and not any changes to any of the > ports. Do I / can I keep the ports up to date also? or is this a bad idea? > > do I need to "clean" after the install to clear all the temporary files? > > thankyou for any advice you can offer. > > regards, > > Jon Paterson. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Bug report /contrib/gcc/function.c
Henk Wevers wrote: > > Hi, > > When i try to make my machine stable i get the following errors. > > /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/function.c: In > function `assign_stack_local': > /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/function.c:772: syntax > error before ``' > *** Error code 1 How did you do to set this up? You are only showing us the last line of a multi-line output. I just cvsup'ed RELENG_4 and did a buildworld. My buildworld had no problem compiling function.c. Kent > > Stop in /usr/src/gnu/usr.bin/cc/cc_int. > *** Error code 1 > > This is with FreeBSD 4.1.1 on a PIII 733 with 512 MB RAM > CPU: Pentium III/Pentium III Xeon/Celeron (736.46-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > real memory = 536788992 (524208K bytes) > > And two hd's > ad0: 39083MB [79408/16/63] at ata0-master using UDMA66 > ad1: 39083MB [79408/16/63] at ata0-slave using UDMA66 > > Henk Wevers > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: breakage with two ed network devices - ATA stepping on it!
John Reynolds~ wrote: > > [ On Friday, October 6, Warner Losh wrote: ] > > > > They aren't reserved. > > OK. > > > Maybe that's where we should look. Does the ata probe for the slave > > somehow fail to release irq 15? > > Hm. I've got verbose output from a 4.1.1 kernel lying around ... let me > login to my machine at home ... > > Aha ... I didn't see this before, but wasn't looking: > > ata1: at 0x170 irq 15 on atapci0 > > then later on: > > ed0 failed to probe at port 0x2c0-0x2df iomem 0xd8000 irq 15 on isa0 > > DUH. Makes sense if the IRQ is already snagged by something. I have 1 ATA > device in this machine. A single disk sitting on ad0: > > ad0: 9765MB [19841/16/63] at ata0-master using UDMA33 > > and it's using the IDE channels from the BX chipset (the HighPoint controller > on this board just gave me way too many problems when I tried to use it). > > Here's more of the boot message: > > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 > ata0: mask=03 status0=50 status1=00 > ata0: mask=03 status0=50 status1=00 > ata0: devices = 0x1 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008 > ata1: mask=03 status0=2c status1=2c > ata1: mask=03 status0=1c status1=1c > ata1: devices = 0x0 > ata1: at 0x170 irq 15 on atapci0 > > I assume blindly that "devices = 0x1" on ata0 means it found 1 thing connected > on the first channel. This is correct. By the same token I assume "devices = > 0x0" on the ata1 line means it found nothing on my second channel. And that's > also correct! I have nothing on the second channel! I don't even have anything > on the slave of ata0. > > So yes Warner, it appears you are correct. The ATA code appears to be setting > up ata1 for my second IDE channel when I'm not even using it! > > I do not have "boot -v" output sitting around for my working 4.1-RELEASE > kernel but my 'normal' dmesg output says absolutely nothing about 'ata1'. > > > IRQ 9 is fine. Nothing wrong with it. It isn't shared at all. It > > used to be irq 2, but that's now used for chaining. > > Oh goodie. I was hoping somebody would say that. I'm glad somebody knows this > crap :) > > Now I just have to figure out how to get the ATA code to relinquish IRQ15 > and not attach ata1 since I'm not using it. Ideas? Theories? Places to go look > in the code? I'd like to have a general idea of how to fix it before sending > in a PR (since PRs with patches generally get fixed before "it's broken" > gripes do). Do you have the secondary channel disabled in your bios? Kent > > Thanks to all that have helped track this down so far! Thanks Warner! > > -Jr > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > | John Reynolds WCCG, CCE, Higher Levels of Abstraction | > | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | > | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make buildworld failing
Simon J Mudd wrote: > > I successfully cvsup'ed the source to stable on 17/09/00 and decided > to upgrade to the latest version of -STABLE with cvsup. > > The cvsup command works fine, but make buildworld fails at the same place > with the same error message: I would remove /usr/obj/* before I try again. You will have to cd /usr/obj chflags -R noschg * rm -rf * There won't be anything left to have a file exist. Kent > > - SNIP - > ===> gnu/libexec/uucp/uupick > /usr/obj/usr/src/gnu/libexec/uucp/uupick created for /usr/src/gnu/libexec/uucp/uupick > ===> gnu/libexec/uucp/uusched > /usr/obj/usr/src/gnu/libexec/uucp/uusched created for >/usr/src/gnu/libexec/uucp/uusched > ===> gnu/libexec/uucp/uustat > mkdir: /usr/obj/usr/src/gnu/libexec/uucp/uustat: File exists > *** Error code 1 > > Stop in /usr/src/gnu/libexec/uucp/uustat. > *** Error code 1 > > Stop in /usr/src/gnu/libexec/uucp. > *** Error code 1 > > Stop in /usr/src/gnu/libexec. > *** Error code 1 > > Stop in /usr/src/gnu. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > unicorn# > - END - > > Have I missed something obvious with what's goind wrong? > > Regards, > > Simon > -- > Simon J Mudd, Madrid SPAINTel: +34-91-408 4878email: [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Correct sequence for keeping a 4.1 system stable.
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Scott >Dodson writes: > : Hmm, I don't know why. Those problems were going from 4.0 -> 4.1.1 and > : going from 4.1 -> 4.1.1 on another machine. If it happened on just one > : machine i wouldn't rase a question. But his is happening on both, however > : of course I'm the one that's done both the machines. But i don't think > : i've screwd anything else up. > > OK. I'll setup a system and give it a try. I thought that I had no > problems when I had done it. But maybe there's some autopilot effects > going on here. I am following a 4.0-release system that is being upgraded to 4.1.1 stable. It is a training exercise and I'm doing a tail -f and following the upgrade output, which is being redirected to a text file, remotely. The only upgrade problems I've seen lately are those occasional strange ones with perl, i.e., the chmod of libdbsm.a. The upgrade I'm following won't be finished until they get off from work tonight at the earliest. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall fails to access cdrom
Ralf Meyer wrote: > > Hej all, > > after rebuilding world and kernel /stand/sysinstall fails to access my > CDROM device with the following console messages: > > ata0-slave: too many segments in DMA table > acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=02 > > If I mount the device manually everything works. The old install (4.0-STABLE, > 25. May 2000) did not show this problem. The devices are recognized in the > dmesg-output as: > > atapci0: port 0x2020-0x202f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ad0: 6194MB [13424/15/63] at ata0-master using UDMA33 > acd0: CDROM at ata0-slave using WDMA2 > > Has anybody else this problem? Did you cd /usr/src/release/sysinstall and make all and make install it? It isn't built when you did the world and your kernel. Kent > > TIA > > Ralf > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: /dev/dsp problem
j mckitrick wrote: > > On Sun, Dec 24, 2000 at 01:41:30PM -0800, Kent Stewart wrote: > | > | > | j mckitrick wrote: > | > > | > I am running 4.2 stable, and I am having a problem I wonder if you have > | > seen. When I rebuild the kernel, the dsp device quits working and reports > | > 'invalid device' when accessed. It seems I have to run install world to fix > | > it. But this has only worked once. I try running makedev, but that doesn't > | > fix it. Any idea what I am doing wrong? > | > | Did you try doing a ./MAKEDEV snd[01] to upgrade your sound /dev > | link's. > > Yes, that was the command I tried twice. But it didn't work. Ok, I wasn't sure what device you were making. I follow 4-stable and have never had the problem. I have also done a "./MAKEDEV all" everytime new devices were added and mergemaster told me to update all. Kent -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
Soren Schmidt wrote: > > It seems Justin W. Pauler wrote: > > I've heard tell that there are problems with the VIA chipset and UDMA on > > FreeBSD. Is this true, and if so, what is the problem with? > > Hmm, there are no open problems as far as I'm aware... > > > FreeBSD 4.2-STABLE #0: Fri Dec 8 01:52:44 EST 2000 > > CPU: Pentium III/Pentium III Xeon/Celeron (601.37-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x683 Stepping = 3 > > atapci0: port 0xe000-0xe00f at device 7.1 on > > pci0 > > ata0: at 0x1f0 irq 14 on atapci0 > > ata1: at 0x170 irq 15 on atapci0 > > ad0: 19546MB [39714/16/63] at ata0-master UDMA66 > > > > The drive has enough space and I have 512MB RAM. If I hit the system hard, > > lets say, rm -rf /usr/ports, the system locks up. It doesn't just stop > > responding for a little bit. It locks up tight. It kills all network > > connections, doesn't respond to the console and doesn't respond to any > > network activity. A hard reboot is the only thing that can bring it back to > > life. > > > > One time, someone was able to see the console when this happened, and they > > said something about a page fault. Trying to solve this, we ordered two brand > > new 256MB modules and installed them. It is still happening. > > > > This is a production environment type of server. I've had no other problems > > with FreeBSD 4.2-S, and i'm hoping maybe this is something that has been > > fixed. > > Hmm, my main devbox is based on the VIA '686 although with an athlon > CPU, and there is no problems at all with it. I also dont belive that > this is the disk drivers fault, as in almost all cases you would get > error messages en-masse from the ATA driver I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is running in PIO mode and that makes it less than half fast doing a system build. The first install of FreeBSD resulted in a trashed Win98se primary partition. There were timing issues in the bios that were supposed to fix the ATA100 Maxtor drives. The bios was flashed to include those fixes. I used sysctl and turned UDMA back on last night and it didn't help the ata-disk. It went back to PIO mode in a hurry. Kent > > -Søren > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HDD Problem
"David W. Chapman Jr." wrote: > > I have a KT7 with an athlon 1.1, no problems with ATA66, don't have a 100 > drive though. Works fine, does make worlds in a little over an hour with > 384mb of pc133, but I do have to downclock the pc133 to 100 because these > via chips have some problem with agp and pc133 at the moment. I'm also running the slow end on the bios memory setting. The wz beta bios is supposed to deal with some memory timing questions. I have downloaded wz but haven't flashed the bios yet. I am running uz, which became w? (their www server is overloaded and can't see what they called the uz when it was released). Abit is also up to KT7a and 686B. I have both Maxtor's (30 GB and 40 GB - ATA100's) set to do only UDMA 33 using Maxtor's udmaupdt.exe program. That didn't help FreeBSD. Windows 2000 didn't have any problems at the UDMA66 setting and just slowed down a little bit at the UDMA33 setting. I have three other systems based on the bx chipset that don't have problems doing UDMA33. If I time my upworld script, I see user times of 18xx seconds and 1.5-1.8 hours wall clock. I figure the difference between doing an update (cvsup of RELENG_4 to installworld) in 40 minutes wall-clock and what I have now is disk transfer speed related. Setiathome runs at ~40% cpu in the background (niced to 19). Because it is only using available cpu time, killing setiathome before I started the builds didn't change the build time significantly. I have a Promise ATA66 card that I am going to try but will have to move one of the HD's and CDROM before the 80-pin cable will reach. The main drive is all by itself on the ide1 controller. Kent > > > > I have an Abit KT7 with PC-133 memory and an Athlon 900 that doesn't > > like FreeBSD 4.2-stable and Maxtor ATA100 drives. Right now, it is > > running in PIO mode and that makes it less than half fast doing a > > system build. The first install of FreeBSD resulted in a trashed > > Win98se primary partition. There were timing issues in the bios that > > were supposed to fix the ATA100 Maxtor drives. The bios was flashed to > > include those fixes. I used sysctl and turned UDMA back on last night > > and it didn't help the ata-disk. It went back to PIO mode in a hurry. > > > > Kent > > > > > > > > -Søren > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:[EMAIL PROTECTED] > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Mergemaster
whisky wrote: > > How does one use mergemaster correctly after a make installworld of 4.2-R to > 4.x-S Very, very carefully. It will try to change all of the configuration files that have been updated. If you have added local mods, they disappear. I don't let it touch my firewall rules, ppp.conf, passwd, or groups. It will also try to change files root uses but I don't let it. I check when it changes my dot."*" files. If I have added local aliases or paths, I don't want them removed. The choices provided by mergemaster on them is always i(nstall new), d(elete new), or m(erge). On the special files, I usually press the enter key, which is none of the above and do them individually. Then, I go through after everything is done and merged what was important out of the files in /var/tmp/temproot/etc. If you include the header information at the top, it ignore that file in the future until the it is modified by the maintainer. The rest of the files I usually add the new mods. It is really convient to do this all from a second computer. Being able to do that depends on your system. You could also do it from x-windows but that really uses a lot of memory that would usually be more beneficial to the compilers. I just happen to set my system up such that I can do an installworld in multi-user mode. Not everyone can do this. It is discussed in /usr/src/UPDATING. The advantage is that it lets me telnet or ssh in and do everything from several sessions. When I get through, I reboot from the console. Kent > > Help is much appreciated > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Mergemaster
"Bruce A. Mah" wrote: > > If memory serves me right, Kent Stewart wrote: > > > whisky wrote: > > > > > > How does one use mergemaster correctly after a make installworld of 4.2-R t > > o > > > 4.x-S > > > > Very, very carefully. > > That applies to pretty much any system administration task. > > > It will try to change all of the configuration > > files that have been updated. If you have added local mods, they > > disappear. > > Say again?!? Your "local mods" only disappear if you let mergemaster > overwrite them. It never does anything without telling you. That was my point. You have to recognize what you have modified and don't let mergemaster delete your changes unless they need to be. The addition of .../defaults solved most of my early problems. > > > I don't let it touch my firewall rules, ppp.conf, passwd, > > or groups. It will also try to change files root uses but I don't let > > it. I check when it changes my dot."*" files. If I have added local > > aliases or paths, I don't want them removed. The choices provided by > > mergemaster on them is always i(nstall new), d(elete new), or m(erge). > > Have you actually tried the last of the three options? I've found that > it works pretty well for merging in a set of local changes with a new > version of a file. You need to pay attention when doing the merge, > obviously. Yes, I have several times. On most of my files the merge option was ok but then I found a couple of files such as rc.firewall or ppp.conf where mergemaster was looking at such a small part of the picture that it was confusing. A poor choice and your access to the world suddenly disappears and you have to grab the backup and start over. I used its diff as a basis even when I did it manually. I also need to go back an try it on something other than the command line and I have more width available. Kent > > My advise: Run mergemaster after an installworld. Read the diffs it > produces. The first time you run it (on a system updated from > 4.2-RELEASE) you'll probably see a lot of changes. In general, if you > know you didn't modify a file, you can probably just let it install the > new version. Learn how sdiff works for handling merges of files, to > handle the case where you made a local modification and the original, > base file was also updated. The first few times you do this, make sure > to have a backup of /etc so you can bail yourself out if necessary. > > Bruce. > > -- >Part 1.2Type: application/pgp-signature -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Compile failure against RELENG_4
Dennis Glatting wrote: > > Updated my sources yesterday. There were no changes to the tree today. > So, I guess this must be a problem. Well, I updated my sources last night and didn't have a problem doing the usual buildworld, buildkernel, installkernel, and installworld. What version did you start with? Are you trying to build a release because I don't have a disk-1 directory. Kent > > cd /disk-1/src/gnu/lib/libgcc; make depend; make all; make install > echo '#include '> config.h > echo '#include ' >> config.h > echo '#include "gansidecl.h"' > tconfig.h > echo '#include "i386/xm-i386.h"'>> tconfig.h > echo '#include "i386/i386.h"' > tm.h > echo '#include "i386/att.h"'>> tm.h > echo '#include "svr4.h"'>> tm.h > echo '#include ' >> tm.h > echo '#include "i386/freebsd.h"'>> tm.h > echo '#include "i386/perform.h"'>> tm.h > rm -f .depend > mkdep -f .depend -a > -I/disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/config > -I/disk-1/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC > -D_PTHREADS -DGTHREAD_USE_WEAK -I/usr/obj/disk-1/src/i386/usr/include > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > mkdep -f .depend -a -nostdinc++ > -I/disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/inc > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo.cc > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo2.cc > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/new.cc > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:33: > gansidecl.h: No > such file or directory > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:34: > eh-common.h: No > such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /disk-1/src/gnu/lib/libgcc. > *** Error code 1 > > Stop in /disk-1/src. > *** Error code 1 > > Stop in /disk-1/src. > *** Error code 1 > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: installworld anomoly
"Corey G." wrote: > > I was just going to report the same issue. It happened last night and > at 11:00AM Central time with a stable cvsup. Don't use ssh to do the installworld. If you telnet, you don't have any problem. Kent > > install -c -o root -g wheel -m 444 sshd.8.gz /usr/share/man/man8 > ===> etc > ===> etc/sendmail > > -- > >>> Rebuilding man page indices > -- > cd /usr/src/share/man; make makedb > makewhatis /usr/share/man > > gzcat: stdout: Broken pipe > > gzcat: stdout: Broken pipe > > gzcat: stdout: Broken pipe > > gzcat: stdout: Broken pipe > > gzcat: stdout: Broken pipe > > gzcat: stdout: Broken pipe > > On Sat, Feb 03, 2001 at 03:43:44PM -0500, Brian Dean wrote: > > My last several -stable installworlds have completed with the > > messages: > > > > [...] > > > > -- > > >>> Rebuilding man page indices > > -- > > cd /usr/src/share/man; make makedb > > makewhatis /usr/share/man > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > [... message repeated many times ] > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > makewhatis /usr/share/perl/man > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > > > gzcat: stdout: Broken pipe > > rm -rf /tmp/install.85245 > > > > > > Is anyone else seeing this? > > > > Thanks, > > -Brian > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > ---end quoted text--- > > -- > Best Regards, > Corey > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Compile failure against RELENG_4
Dennis Glatting wrote: > > On Saturday 03 February 2001 12:51 pm, Kent Stewart wrote: > > Dennis Glatting wrote: > > > Updated my sources yesterday. There were no changes to the tree > > > today. So, I guess this must be a problem. > > > > Well, I updated my sources last night and didn't have a problem doing > > the usual buildworld, buildkernel, installkernel, and installworld. > > > > What version did you start with? Are you trying to build a release > > because I don't have a disk-1 directory. > > > > I feed several local machines from a CVS tree that I keep up to date > from cvsup8.freebsd.org. The source in question has checked out against > the RELENG_4 tag several times since 4.2. /usr/src is a symlink into > /disk-1 on this machine. The last time I built RELENG_4 was January 10, > 2001. When I compiler all I say is "make buildworld." I also use cvsup8 and have a number of successful cvsup's and build's since 26 Jan. Four of them have been run since 1 Feb. I don't have any idea what is wrong at your site. I don't have any symlinks but do mount /usr/src and /usr/obj on different HD's. Kent > > > Kent > > > > > cd /disk-1/src/gnu/lib/libgcc; make depend; make all; make > > > install echo '#include '> config.h > > > echo '#include ' >> config.h > > > echo '#include "gansidecl.h"' > tconfig.h > > > echo '#include "i386/xm-i386.h"'>> tconfig.h > > > echo '#include "i386/i386.h"' > tm.h > > > echo '#include "i386/att.h"'>> tm.h > > > echo '#include "svr4.h"'>> tm.h > > > echo '#include ' >> tm.h > > > echo '#include "i386/freebsd.h"'>> tm.h > > > echo '#include "i386/perform.h"'>> tm.h > > > rm -f .depend > > > mkdep -f .depend -a > > > -I/disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/config > > > -I/disk-1/src/gnu/lib/libgcc/../../../contrib/gcc -I. -DIN_GCC > > > -D_PTHREADS -DGTHREAD_USE_WEAK > > > -I/usr/obj/disk-1/src/i386/usr/include > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/frame.c > > > mkdep -f .depend -a -nostdinc++ > > > -I/disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/inc > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo.cc > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/tinfo2.cc > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/new.cc > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc > > > > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:33: > > > gansidecl.h: No > > > such file or directory > > > /disk-1/src/gnu/lib/libgcc/../../../contrib/gcc/cp/exception.cc:34: > > > eh-common.h: No > > > such file or directory > > > mkdep: compile failed > > > *** Error code 1 > > > > > > Stop in /disk-1/src/gnu/lib/libgcc. > > > *** Error code 1 > > > > > > Stop in /disk-1/src. > > > *** Error code 1 > > > > > > Stop in /disk-1/src. > > > *** Error code 1 > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.0 Release -> 4.2-Stable should be ok ? via cvsup ?
Warner Losh wrote: > > In message <[EMAIL PROTECTED]> Andrew >Gordon writes: > : I hope that's _late_ Feb 4th sources if your firewall uses ipfw: ipfw was > : substantially broken from 2001/02/01 20:25:09 to 2001/02/04 05:48:59 > : (/sys/netinet/ip_fw.c rev 1.131.2.13 is the bad version). > : > : We were upgrading our firewall around that time and were dismayed to find > : it wide-open after the upgrade! > > Yes. Since I'm on the security-officer's list still, I had planned > the upgrade for a day earlier, but put things off until the fixes were > committed. Thanks for this thread because of it, I found that I could telnet in from the outside world. Something that was supposed to be completely turned off. I was still logging the activity but was really kind of shocked. Kent > > Warner > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-STABLE (20/02/2001): Reproducable kernel panic.
Cameron Grant wrote: > > > > Looking at that, I'm wondering if the sound card isn't the difference > > > here. I would assume that the Ensoniq has its own driver seperate from > the > > > SB series.. I wish I understand much about kernel internals. :P > > > > I have an older SB and a newer Es-1371. I can play it on the Ensoniq > > but it panics the SBc system. I can play it on the SB, if I use Kaiman > > from KDE-2. > > this should now be resolved with sys/dev/sound/pcm/buffer.c revision 1.1.2.2 It did fix the panic problem on the computer that was panicing when I had tested wavplay before. Kent > > -cg > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: KDE
Kris Kennaway wrote: > > On Tue, Feb 27, 2001 at 09:52:25AM +, Antony T Curtis wrote: > > > > Just wondering if KDE 2.x would make an appearence in the FreeBSD 4.3 > > release? > > Since 2.1 was already committed earlier today, the answer to the question > I think you meant to ask is yes. I tried to install 2.1 but it died doing koffice. The mirror's were really busy for awhile. Kent > > KDE 2.x has been in the ports collection for ages. > > Kris > > -- > In God we Trust -- all others must submit an X.509 certificate. > -- Charles Forsythe <[EMAIL PROTECTED]> > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: more strange problem with broken pipes and ssh
Mike Tancsa wrote: > > At 06:32 AM 3/2/01 -0800, Cy Schubert - ITSD Open Systems Group wrote: > >In message <[EMAIL PROTECTED]>, Mike > >Tancsa wr > >ites: > > > > > > OK, here is another strange problem with SSH and pipes. When connecting > > > via some means other than ssh, the commands > > > > > > grep reject /var/log/maillog | less > > > > > > displays data as expected. However, when connected via ssh, hitting q to > > > exit from less, I get a whole mess of > > > > > > grep: writing output: Broken pipe > > > grep: writing output: Broken pipe > > > grep: writing output: Broken pipe > > > grep: writing output: Broken pipe > > > > > > This is with stable as of today and the problem showed up since the last > > > ssh commits. The amount of broken pipes seems to scale with the amount of > > > data less has, and it seems you need at least more than a screen full. > > > >I'm using -stable as of Feb 27 04:15 PST. No problems here. Is there > >something in your ssh config that might either cause this bug to > >manifest itself? > > If I recall you never had the problem with the makewhatis script and ssh as > well due to some special config of your ssh (Kerberos?) ? This is with > > 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Feb 26 > > Like the problem with the makewhatis broken pipes (and certain ports), the > problem does not show itself when connecting to the machine via telnet or > rlogin. I had some broken pipe messages when I tried to upgrade to kde-2.1. I backed up and telneted in and finished the install. Kent > > ---Mike > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: KERNCONF instead of KERNEL?
Nik Clayton wrote: > > On Fri, Mar 02, 2001 at 11:34:19PM +0900, Daniel C. Sobral wrote: > > Here is the order suggested and the why: > > > > 1) make buildworld -- because the new kernel may depend on new tools > > (config(8) is a common example, but no the only one). > > 2) make buildkernel -- some programs may depend on new syscalls, so > > build the kernel before installing the world. > > 3) make installkernel -- install a new kernel (the copy of the old one > > is preserved) > > 4) reboot single user -- make sure the new kernel works > > 5) mount filesystems, make installworld -- install the rest of the world > > 6) mergemaster -- update /etc -- the new userland tools may require new > > /etc scripts and configuration files. > > I think the attached diff to the Handbook brings it up to date with > reality. I've also attached the generated HTML file, for those of you > that don't want to build the docs. Comments? Yes, there are several things that I think are basically wrong. On the -j4 option, what was -current is now 4.0-release or later. On a fast uniprocessor system, using -j4 on the make actually causes the buildworld to run 10% or more longer by the clock. Your user and system time may be shorter but the build takes forever. You are adding overhead to access I/O that the HD's can't provide and the cpu is left in an idle state waiting for I/O. This becomes especially true on large single HD's. Turning on softupdates helps. I have a AMD Thunderbird 900 with 256MB of PC-133 memory that I tried various combinations on. I added ATA-100 HD's until I had reasonable build times. I eventually ended up with 3 and had each on its own controller. I haven't tried fast scsi yet but I think the majority of the new users are building systems around IDE drives and you can see the slowdown when you use -jx with x >= 2. It isn't bad for people running setiathome because it will continue to use 40% or more of the cpu and doesn't interfere. When the percentage reported by time goes over 100%, which it can for multiprocessor systems, setiathome didn't get much time. That data also wasn't included in my table. The only system that can use -j4 is a dual headed system (2-P-III 866's with 256MB of PC-133) with the source on a 2-HD HPT-370 raid-0 array. The system has 3-30GB Maxtor ATA-100 HD's all on different controllers. The variation in build time ran from 1:21 to 34 minutes with softupdates and /usr/src on the raid-0 array. If I tee the output from the build to a file, it only slows the build down to 35:xx minutes. Some entries from my build times log are: buildworld, softupdates, 1-HD 1597.238u 629.123s 47:52.34 77.5% 1227+1393k 42713+11617io 1575pf+0w raid-0 for /usr/obj but no softupdates. 1599.347u 628.302s 1:21:36.28 45.4% 1230+1395k 44554+138574io 1828pf+0w raid-0 (64k) for /usr/src, -j4, and softupdates for everything but / 1655.441u 730.090s 34:16.34 116.0% 1210+1380k 47507+3918io 1881pf+0w make buildworld with tee'ed logging and current setup from above 1665.892u 702.004s 35:14.42 111.9% 1211+1387k 51575+4140io 1918pf+0 The chflag noschg isn't needed on 4.2. I don't know when that was changed but you don't have to use it to rm -rf * files in /usr/obj. Of course, if you have a kern_secure level set in 4.2, you can't noschg anything from multi-user mode and the installkernel will die trying to mv the kernel's around. You have to be running in single user mode to get around the kern_secure level setting. Kent > > N > -- > FreeBSD: The Power to Serve http://www.freebsd.org/ > FreeBSD Documentation Project http://www.freebsd.org/docproj/ > > --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- > > -- > Name: makeworld.html >makeworld.htmlType: Hypertext Markup Language (text/html) > Encoding: quoted-printable > > Name: mw.diff >mw.diffType: Plain Text (text/plain) > Encoding: quoted-printable > >Part 1.2Type: application/pgp-signature -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XF86 4 on 4.3-RELEASE?
Gordon Tetlow wrote: > > On Fri, 9 Mar 2001, Jordan Hubbard wrote: > > > Nope. When XFree86 4.x: > > > >a) Supports a reasonable superset of all cards supported by 3.3.6 > > > >b) Doesn't halve OpenGL performance on cards like Matrox and nVidia > > (3dfx sucks so much on both that it's not an issue). > > > >c) Doesn't have a configuration tool which confuses new users > > even more than the old configuration tool did. > > You forgot one (that happens for me) > d) Doesn't take half the CPU while sitting idle. > > But then again, I suspect it has something to do with the fact I'm running > a dual head. I had to chuckle at this point. I'm running 3.3.6 and KDE-2.1 on a dual 866 coppermine system. On it, kicker has 95% of the second cpu full time. I wonder what is taking half of your system/ Kent > > -gordon > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: New KERNCONF option
Francisco Reyes wrote: > > On Tue, 13 Mar 2001, Torben Baecker wrote: > > > make buildworld > > make kernel KERNCONF=JUPITER > > So this new procedure replaces the old? > Can one put the KERNCONF variable on /etc/rc.conf and just do "make > kernel" > > Where is this explained in /usr/src/UPDATIN? You have to read the source but it is easier to see the changes at http://www.freebsd.org/cgi/cvsweb.cgi/src/Makefile.inc1 It is all documented starting around 22 Jan. Kent > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: BETA induced nervousness
Jim Mock wrote: > > On Fri, 16 Mar 2001 at 21:42:10 +0100, Steve O'Hara-Smith wrote: > > Hi, > > > > Picking a recent example: > > > > Saverio Perugini <[EMAIL PROTECTED]> writes: > > > What is a BETA system? Is it similiar to CURRENT? > > > > We get a lot of this sort of thing every time a release rolls, > > an idea crossed my mind, perhaps if during BETA and RC phases > > /etc/motd were to carry a big message like > > > > -- > > DO NOT PANIC - BETA is a normal phase that STABLE goes through prior > > to the rolling of a release. If anything it is *MORE* stable than > > usual during BETA as all changes are monitered by the release > > engineer. > > -- > > > > Changing BETA to RC as appropriate. It *might* reduce the > > effect, worth a try ? > > This would be wonderful. It should cut down dramatically on the 3.7 > million "MY FBSD IZ BORKEN CUZ IT SAYZ -BETA N I WANT -STABLE FIX IT NOW > K PLZ THX" (I think I hung out with Alfred too much :-) emails to this > list and -questions. > > Perhaps even pointing something towards the FAQ entry on this would > help. > > The only problem is see doing this is that: > >1) Not everyone will run mergemaster afterwards. It doesn't matter > whether they should or not, many just won't. > >2) Not everyone who does run mergemaster will update their /etc/motd > (like me). > > So, the question is.. how can we get something like this to the most > people without printing that section of the FAQ and stapling it to their > foreheads? LOL, this struck me funny because it would have to be reverse printed. Sort of like Ambulance spelled backwards on the front of one. Since Mergemaster is the suggested way of updating /etc, why not add a "don't forget to run mergemaster message" at the end of installworld. Then add the Beta message at the very front of motd. The ones that use a script will never see it but then they probably don't need to. It might even be added using a #if define of some sort. I don't have any idea if that kind of logic is possible. Just an idea that popped into my mind. In several places, it is suggested that they follow stable for several weeks before they try upgrading to stable and that is being ignored. There is a sufficient number that will still drop a "whot hoppnd" message onto the stable list. I think people focus on spots of interest and ignore the rest. Their method of dealing with the number of messages. Kent > > - jim > > -- > - jim mock <[EMAIL PROTECTED]> - O|S|D|N - open source development network - > - http://www.freebsdzine.org/ - [EMAIL PROTECTED] - [EMAIL PROTECTED] - > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.3-BETA crash on 'mount /dev/acd0c /mnt'
Nate Dannenberg wrote: > > On Thu, 22 Mar 2001, David Taylor wrote: > > > (using: 4.3-BETA FreeBSD 4.3-BETA #3: Tue Mar 6 18:39:44 GMT 2001) > > > > mount -t cd9660 /dev/acd0c /mnt #works ok > > > > OTOH, > > > > mount /dev/acd0c /mnt > > > > causes the following panic: > > I've also experienced problems mounting CD-ROM discs, to the extent that > if the bus is busy on one disc, the system will not error out and return a > "device busy" message or something else more appropriate. Instead the > command and it's controlling console/terminal/shell/whatever hangs until > the other device is finished. > > I have yet to panic the kernel doing this, though. I just tried it and it didn't work. The mount complained about incorrect super block. I had /dev/acd0c defined in my fstab as mounting /cdrom. I tried mount /cdrom and it worked. Kent > > > panicstr: vm_fault: fault on nofault entry, addr: c7c11000 > > (not to downplay this...but isn't that like masking an NMI? :-) > > -- > /~~~___~\ > | [EMAIL PROTECTED] //Z@|___ | > | http://home.kscable.com/natedac |'(__ [_< | > \_C64/C128_-_What's_*YOUR*_hobby?__\___|/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: upgrading to bind-8.2.3
Rich Morin wrote: > > I just received a security notice about a really nasty worm that is > using a hole in bind to infect Linux boxes. > > >Late last night, the SANS Institute (through its Global Incident > >Analysis Center) uncovered a dangerous new worm that appears to be > >spreading rapidly across the Internet. It scans the Internet looking > >for Linux computers with a known vulnerability. It infects the > >vulnerable machines, steals the password file (sending it to a > >China.com site), installs other hacking tools, and forces the newly > >infected machine to begin scanning the Internet looking for other > >victims. > > > >Several experts from the security community worked through the night to > >decompose the worm's code and engineer a utility to help you discover > >if the Lion worm has affected your organization. > > > >Updates to this announcement will be posted at the SANS web site, > >http://www.sans.org > >... > > So, it seems like a Good Idea to upgrade my copy of bind (:-). I > pulled down the port for bind-8.2.3-REL and it seems to build just > fine. Before I install it, however, I thought I'd ask if anyone > has run into installation and/or configuration issues. I thought that was what is already built into 4-stable right now. I did a named -v and 8.2.3-REL pops up. Kent > > -r > -- > http://www.cfcl.com/rdm - home page, resume, etc. > http://www.cfcl.com/Meta/md_fb.html - The FreeBSD Browser > email: [EMAIL PROTECTED]; phone: +1 650-873-7841 > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: how to make my sound card work
[EMAIL PROTECTED] wrote: > > i am a newbie to freebsd.i think it is more difficult to configure my sound card in >freebsd > than configure it in linux.maybe this is a reason why freebsd is more fit for >server.:) > nobody need to listen music on a server,isn't it? > i will read chapter 14 in the Handbook carefully. > thanks I have sound on all but my P-200. I have one that I had to add the sbc device but the rest all worked with nothing more than "device pcm". Sound is much easier on 4.x because it is consistent there. You have to worry about pcm0 or pcm1 on 3.x. When you get the kernel made, installed, and reboot. The device shows up in dmesg. You make a device for /dev/snd? where the "? is the digit on the end of your pcm? device from your boot. I had to do a ./MAKEDEV snd0. When I finished I had sound. Kent > > [EMAIL PROTECTED] wrote: > > > > who can tell me whether i need to download 2CD to install 4.3 RC? > > In the releases section ftp://ftp.FreeBSD.org/pub/FreeBSD/, there are an > iso's for each cpu type. There is only one 4.3-rc cd in > releases/i386/ISO-IMAGES. It is called 4.3rc2-install.iso. > > You will find your sound card probably works on it as a "device pcm". > See chapter 14 in the Handbook for details. > > Kent > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: em watchdog timeout on UP, 6-stable
On Friday 08 September 2006 10:25, Gleb Smirnoff wrote: > Barney, > > On Tue, Sep 05, 2006 at 02:33:52PM -0400, Barney Wolff wrote: > B> Updated my Athlon-xp 6-stable system last night, got an em > watchdog B> timeout for the first time a few hours later, during a > fairly B> high-traffic period. System is UP but does have device > apic in B> the config. Any chance this is the recent race condition? > B> Workaround? ifconfig em0 down, ifconfig em0 up seemed to cure it, > B> at least for the moment. > > Not clear from your mail whether interface was working after the > event occured. In my system, you get the timeout, then the state is downed and then uped. Your transfer session is basically dead at that point. On Tuesday, Klop had an email with a copy of what you see in the message log. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em watchdog timeout on UP, 6-stable
On Friday 08 September 2006 11:17, Kent Stewart wrote: > On Friday 08 September 2006 10:25, Gleb Smirnoff wrote: > > Barney, > > > > On Tue, Sep 05, 2006 at 02:33:52PM -0400, Barney Wolff wrote: > > B> Updated my Athlon-xp 6-stable system last night, got an em > > watchdog B> timeout for the first time a few hours later, during a > > fairly B> high-traffic period. System is UP but does have device > > apic in B> the config. Any chance this is the recent race > > condition? B> Workaround? ifconfig em0 down, ifconfig em0 up > > seemed to cure it, B> at least for the moment. > > > > Not clear from your mail whether interface was working after the > > event occured. > > In my system, you get the timeout, then the state is downed and then > uped. Your transfer session is basically dead at that point. On > Tuesday, Klop had an email with a copy of what you see in the message > log. > Ignore part of what I said. I am getting the same errors on re0. All I have to do to force the error is ftp a GB or 2 to the destination machine using 1000baseT NICs. My host machine is XP and I use the destination machine as a backup for photos and mp3 files. A photo session is usually on the order of 1-2 GBs. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bge watchdog timeouts still happening
On Friday 15 September 2006 09:28, Herve Boulouis wrote: > Le 15/09/2006 18:05, Gleb Smirnoff a écrit: > > H> bge0: mem > > 0xfeb0-0xfeb0 irq 17 at device 8.0 on pci1 H> miibus0: > bus> on bge0 > > H> brgphy0: on miibus0 > > H> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, > > 1000baseTX, 1000baseTX-FDX, auto H> bge0: Ethernet address: > > 00:06:5b:1a:7f:4a > > > > Is it integrated or not? I've got exactly the same NIC and I can > > try to reproduce the problem if you describe the workload. > > Yes, it's the onboard bge. Workload is 10-25 Mbit/s of web hosting. It seems to be at the top of the tree somewhere because people are also seeing the watchdog timeouts on em and I get them on the gigabit re's. I got them downloading the kde-3.5.4 distfiles on a 768kb DSL line. I had setiathome running, which keeps the cpu useage close to 100%. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6 does not compile
On Thursday 21 September 2006 18:20, Joerg Pernfuss wrote: > On Fri, 22 Sep 2006 02:59:53 +0200 > > martinko <[EMAIL PROTECTED]> wrote: > > >> internal compiler error: Segmentation fault: 11 > > >> Please submit a full bug report, > > >> with preprocessed source if appropriate. > > >> See http://gcc.gnu.org/bugs.html> for instructions. > > >> *** Error code 1 > > > > > > Chances are you have failing hardware. > > > > > > Kris > > > > you must be kidding! :-o > > no, really, this is a laptop and i hope it's not going to die or > > something. :-/ > > well, it would actually be better now before the warranty is over. > > ;-) anyway, how did you come to your conclusion pls ?? > > SegFault 11 is normally a strong indicator of dying RAM. > But in a laptop it could be related to heat such as a clogged heatsink or the equivalent. In one of my AMD desktop, I blew the dust out of the heat sink and the cpu temp dropped 5oC. There is a list of causes in the FAQ and they can all be the cause. Kent > Joerg -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and "make -j# buildworld" usability
On Friday 13 October 2006 07:31, Buki wrote: > Hi, > > I searched the archives and web a little but found many different > opinions on stability/usability of using make -j# with buildworld > (and buildkernel). > > So I am asking if it is a good idea to use make -j on production > boxes. > I tested buildworlds with different values for -j. On single processors, using a script that basically looked like time make -j? ... yielded fastest builds when I didn't specify a value for -j. On dual cpu's a value around -j8 yielded the fastest build. I am not interested in system and user time. To me the fastest build is the one that produced the smallest wallclock time or elapsed time, which is the 3rd field in the output of time. The fastest build also yielded the highest cpu utilization, which is the 4th field. I figure specifying a value for -j on single cpu system is simply thrashing the cpu by forcing it to save the environment to work on a different section of the build. I also found that mounting /usr/src and /usr/obj on different controller/HDs from the system reduced the build time. I was using ata-133 HDs and a good scsi would be change the results. It is too easy to test in your environment to see what produces the fastest buildworld. I am going to have to upgrade at some point and an AMD X2 should be interesting. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and "make -j# buildworld" usability
On Monday 16 October 2006 15:33, Garance A Drosehn wrote: > At 1:47 PM -0700 10/13/06, Kent Stewart wrote: > >On Friday 13 October 2006 07:31, Buki wrote: > >> Hi, > >> > >> I searched the archives and web a little but found many different > >> opinions on stability/usability of using make -j# with buildworld > >> (and buildkernel). > >> > >> So I am asking if it is a good idea to use make -j on production > >> boxes. > > > >I tested buildworlds with different values for -j. On single > > processors, using a script that basically looked like > > > >time make -j? ... > > > >yielded fastest builds when I didn't specify a value for -j. On dual > >cpu's a value around -j8 yielded the fastest build. > > You might want to repeat those performance tests. The results will > change over time, as various system changes are made. I used to see > results somewhat similar to yours, but the last time I checked I > seemed to get the best results from a dual-cpu system when using -j3 > . > > I believe that change in performance is due to some improvements > made to the `make' command itself, which solved some delays that > happened when -j was used. However, I do not remember the details. > > Performance comparisons like this will also depend on all the > hardware on the system, and not just the dual-CPU. It can change > depending on much memory the machine has, for instance, or how fast > the disks are compared to the CPU's. That was why I commented about making your own tests. I had ata-133 or 100 HDs on individual controllers. Comparing an ata based system with a scsi isn't a real comparison. My tests are at http://users.owt.com/kstewart/freebsd/urban_legends.html and I see I got the shortest elapsed time with -j4 and -j8. It has been too long to remember what I did to improve the -j8. They were run on FreeBSD 4.3 and I no longer have a dual cpu system. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD and "make -j# buildworld" usability
On Monday 16 October 2006 12:46, Nikolas Britton wrote: > On 10/13/06, Kent Stewart <[EMAIL PROTECTED]> wrote: > > On Friday 13 October 2006 07:31, Buki wrote: > > > Hi, > > > > > > I searched the archives and web a little but found many different > > > opinions on stability/usability of using make -j# with buildworld > > > (and buildkernel). > > > > > > So I am asking if it is a good idea to use make -j on production > > > boxes. > > > > I tested buildworlds with different values for -j. On single > > processors, using a script that basically looked like > > > > time make -j? ... > > > > yielded fastest builds when I didn't specify a value for -j. On > > dual cpu's a value around -j8 yielded the fastest build. > > That's odd, your results don't jive with this: > http://people.freebsd.org/~fsmp/SMP/akgraph-a/graph1.html His results are too old to use as a reference. My system was the next step up and is also too old to consider current. His cpus were Intel Pentium pro 200MHZ and the bus speed alone (66MHz) would make a big difference. Only having 64MB of memory may also skew the results. My system was 2 Intel pIII 866's and had 256-512MB of SDRAM or DDR memory. Kent > > Although that report is quite old... My general rule of thumb for -j > is n +1, where n equals the total number of cpu cores. This is > generally enough to keep to processor(s) occupied without over > stressing the system. Maybe n * 2 is more appropriate, can you post > the results from your test? -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with portupgrade
On Saturday 03 March 2007 10:07, [EMAIL PROTECTED] wrote: > > On 2007-Mar-03 10:12:53 +1100, Phillip Ledger > > > > <[EMAIL PROTECTED]> wrote: > > >Even after a complete reinstall of the toll and rebuildig the > > >database its still giving the same error. anyumore ideas? > > > > Exactly what have you re-installed? > > What versions of ruby* and portupgrade do you have? > > Have you compared your /usr/local/etc/pkgtools.conf with the sample > > version? > > I have the exact same problem. I rebuilt INDEX-6, rebuilt INDEX-6.db > and rebuilt portupgrade, to the latest version. I have ruby 1.8.4. > > I have published my pkgtools.conf to > http://www.vistua.com/public/pkgtools.conf the only changes I made > from default, was to ignore language categories I do not speak. And > to instruct that packages only be used for Openoffice. These messages usually popup when you have a problem with ruby and the database setup. Something is inconsistant with that setup. Also, I don't know if your pkgtools.conf ignore will affect the building of the INDEX-*. If you ignore anything, you usually have to fetch an INDEX-* because you can't build a proper INDEX. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Various problems with re(4) on a PCIe 8168/8111B onboard NIC
On Sunday 29 July 2007, Michael Nottebrock wrote: > After recently updating the windows drivers (I dual-boot Windows XP > on the machine the NIC is in), I hit this problem: > http://gentoo-wiki.com/HARDWARE_RTL8168#Troubleshooting which affects > re(4) like it does the Linux drivers described in the above link. > > I already wrote the Realtek technical support about it since their > "own" FreeBSD driver (a hacked rl(4) that does not support any of the > chip's advanced features) does not manage to power up the PHY on its > own either - neither does the motherboard's BIOS when trying to > netboot. > > The other problem is that I have at least two applications > misbehaving when rxcsum/txcsum is enabled: > > - The Linux Second Life client (yes, yes, I know, but it is nice for > showing off GLX and it is really really good at generating network > traffic) will cease to receive data after about a minute or so - > turning off rcxsum/txcsum will mend it on the spot. > > - A Fedora Core 4 running in Qemu, networked with bridge(4) and > tap(4), cannot receive an ip address via DHCP. Interestingly, this > even occurs if rxcsum/txcsum was already turned off before launching > Qemu - to make it work, I have to cycle rxcsum/txcsum once. Might be > related to promiscuous mode. > > I realise that both of these make awful test cases, but so far they > are the only applications I found to expose those problems. > > This is on FreeBSD kiste 6.2-STABLE FreeBSD 6.2-STABLE #4: Sat Jul 28 > 14:11:23 CEST 2007 root@:/usr/obj/usr/src/sys/KISTE-SMP i386. > The kernel sources are up to date as of 2007-07-27. > > The NIC is re0: port > 0xd800-0xd8ff mem 0xfbfff000-0xfbff irq 36 at device 0.0 on pci3 > / [EMAIL PROTECTED]:0:0: class=0x02 card=0x81681849 chip=0x816810ec > rev=0x01 hdr=0x00. Have you looked at /var/log/messages? I would be surprised if you have not had a number of Jul 27 00:55:32 ruby kernel: re0: watchdog timeout Jul 27 00:55:32 ruby kernel: re0: link state changed to DOWN Jul 27 00:55:35 ruby kernel: re0: link state changed to UP People have complained a long time ago and basically given up on getting it fixed. Kent -- Kent Stewart Richland, WA http://www.soyandina.com/ "I am Andean project". http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X.Org/xdm 'frozen' after installworld (7-stable)
On Tuesday 03 February 2009 09:29:05 am Steve Franks wrote: > This is a new weird one I've never had before. Consoles work fine, > but the mouse and keyboard won't move/type when xdm pops up. > ctrl-alt-F2 takes you right to a working console, and the mouse works > fine in the console...ctrl-alt-backspace no longer kills X either... > The option that I found the easiest was to add Option "AutoAddDevices" "off" To the ServerFlags section. I was told in the ports list that you can add it to the ServerLayout section but I could never make that work. Kent ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Invalid path for portupgrade ftp.FreeBSD.orgpub
On Monday 16 February 2009 12:56:25 am Gianni Doe wrote: > I'm upgrading a system from 6.4 to 7.1 and rebuilding all the ports. > I'd rather use packages where present to speed things up a bit so I'm > using: > # portupgrade -faP > > The problem is that it never finds the packages as the URL is invalid, > there seems to be a missing slash between in ftp.FreeBSD.orgpub > > fetch: > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/djbdns-1. >05_12.tbz > > : No address record > > ** The command returned a non-zero exit status: 1 > ** Failed to fetch > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/djbdns-1. >05_12.tbz fetch: > ftp://ftp.FreeBSD.orgpub/FreeBSD/ports/i386/packages-7-stable/All/djbdns-1. >05_12.tgz > > : No address record > > I've got the latest portupgrade. > portupgrade-2.4.6,2 > > Is there somewhere I can specify/fix this path? The handbook shows the usage of PACKAGESITE to specify the path. The main difference is that is shows the path to .../Latest/ instead of .../All/ Kent -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Old /etc files back, or cvs error?
On Monday 23 February 2009 10:11:45 pm Warren Block wrote: > Lately I've installed a couple of test systems from 7.1-RELEASE CDs, > then csupped to RELENG_7 from cvsup9: > > *default host=cvsup9.FreeBSD.org > *default base=/var/db > *default prefix=/usr > *default release=cvs tag=RELENG_7 > *default delete use-rel-suffix > > mergemaster adds a *lot* of old files in /etc that were not there in > 7.1-RELEASE. (Remember the rc.d rework? Like that.) For example, a > bunch of bluetooth files and /etc/isdn/*. > > The version numbers and dates in mergemaster look wrong. For example, > /etc/bluetooth/hcsecd.conf: > > # $Id: hcsecd.conf,v 1.1 2003/05/26 22:50:47 max Exp $ > # $FreeBSD: src/etc/bluetooth/hcsecd.conf,v 1.3 2006/05/18 17:53:49 emax > Exp $ > > Shouldn't that be 1.3.6.1 from Tue Nov 25 02:59:29 2008? > > The latest entries for files in /etc/isdn are 9 months old, and were > removals. > > This looks like an error, but maybe I'm missing something. And other > cvsup mirrors seem to agree with cvsup9. You are looking at the version for the 7.1 release version. The RELENG_7 version is Revision 1.3: download - view: text, markup, annotated - select for diffs Thu May 18 17:53:49 2006 UTC (2 years, 9 months ago) by emax Branches: MAIN CVS tags: RELENG_7_BP, RELENG_7_1_BP, RELENG_7_0_BP, RELENG_7_0_0_RELEASE, RELENG_7_0, RELENG_7, HEAD Branch point for: RELENG_7_1 Diff to: previous 1.2: preferred, colored Changes since revision 1.2: +1 -1 lines Go to http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/bluetooth/hcsecd.conf and you can see the versions and the tags. Kent -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Xorg unbuildable - where to get: x11-xcb?
On Saturday 28 March 2009 09:04:25 pm Chris H wrote: > Greetings, > A fresh install of 7 followed by a cvsup to 7.2-PRE on the 26th > results in an inability to build Xorg on the system. A cvsup only > an hour ago provides no solution. > > An attempt at the following: > > cd /usr/ports/x11/xorg-minimal > make > > produces the following error: > ... > checking pkg-config files for X11 are available... yes > checking for LIBDRM... yes > checking for DRI2PROTO... yes > checking for DRIGL... gnome-config: not found > configure: error: Package requirements (x11 xext xxf86vm xdamage xfixes > x11-xcb > xcb-glx) were not met: > > No package 'x11-xcb' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > ... > > I was able to install /usr/ports/x11/xcb with no issue. But have > no idea where to find x11-xcb. Where can I get it? > > thank you for all your time and consideration in this matter. You didn't really say that your cvsup updated everything but if you didn't you have to do a cvsup of ports-all for ports to be built. Kent -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
