From owner-freebsd-stable Sun Nov 17 1:21:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74B8C37B401 for ; Sun, 17 Nov 2002 01:21:16 -0800 (PST) Received: from mail.svzserv.kemerovo.su (mail.svzserv.kemerovo.su [213.184.65.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C018943E3B for ; Sun, 17 Nov 2002 01:21:14 -0800 (PST) (envelope-from sa@main.svzserv.kemerovo.su) Received: from main.svzserv.kemerovo.su (root@main.svzserv.kemerovo.su [213.184.65.87]) by mail.svzserv.kemerovo.su (8.12.6/8.12.5) with ESMTP id gAH9LAPJ018409 for ; Sun, 17 Nov 2002 16:21:10 +0700 (NKZ) (envelope-from sa@main.svzserv.kemerovo.su) Received: from main.svzserv.kemerovo.su (smmsp@localhost [127.0.0.1]) by main.svzserv.kemerovo.su (8.12.6/8.12.5) with ESMTP id gAH9L8DE025126 for ; Sun, 17 Nov 2002 16:21:08 +0700 (NKZ) (envelope-from sa@main.svzserv.kemerovo.su) Received: (from root@localhost) by main.svzserv.kemerovo.su (8.12.6/8.12.6/Submit) id gAH9L7uJ025122 for stable@freebsd.org; Sun, 17 Nov 2002 16:21:07 +0700 (NKZ) Date: Sun, 17 Nov 2002 16:21:07 +0700 From: Eugene Grosbein To: stable@freebsd.org Subject: make release fails Message-ID: <20021117162107.A19974@main.svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! I'm trying to setup a box for building releases of RELENG_4. This box already has cvsup-mirror and local mirror of the Repo and has been used as local CVSup mirror for a while with success. My goal is to build releases in a way that doesn't touch this system's own /usr/src, /usr/sup and /usr/obj. So I'm trying to have another copy of src, sup and obj using extra supfile and building script: #!/bin/sh -ex export CVSROOT=/home/ncvs # Here is the Repo export KERNEL_FLAGS="-j4 CPUTYPE=i386" # I have CPUTYPE=i686 in /etc/make.conf # and that's SMP system export WORLD_FLAGS="$KERNEL_FLAGS" SUPFILENAME=stable-supfile # has custom host, base and prefix: SRC=/mnt/.1/release/src # /mnt/.1/release mkdir -p $SRC # Here sources must live /usr/local/bin/cvsup -g -L 2 `dirname $0`/$SUPFILENAME # update sources cd $SRC/release nice -17 make -j4 release \ VNDEVICE=vn1 \ RELEASETAG=RELENG_4 \ CHROOTDIR=/mnt/.1/release/chroot 2>&1 | tee /mnt/.1/release/log My problem is that it doesn't work. What am I doing wrong? Here is a log. rm -rf /mnt/.1/release/chroot 2>/dev/null chflags -R noschg /mnt/.1/release/chroot/. rm -rf /mnt/.1/release/chroot mkdir -p /mnt/.1/release/chroot >>> make release for i386 started on Sun Nov 17 09:14:12 GMT 2002 cd /mnt/.1/release/src/release/.. && make TARGET_ARCH=i386 TARGET=i386 -DNOGAMES -DNOHTML -DNOINFO -DNOMAN -DNOPROFILE installworld DESTDIR=/mnt/.1/release/chroot mkdir -p /tmp/install.22943 for prog in [ awk cat chflags chmod chown date echo egrep find grep ln make makewhatis mtree mv perl pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.22943; done cd /mnt/.1/release/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 OBJFORMAT_PATH=/usr/obj/mnt/.1/release/src/i386/usr/libexec PERL5LIB=/usr/obj/mnt/.1/release/src/i386/usr/libdata/perl/5.00503 GROFF_BIN_PATH=/usr/obj/mnt/.1/release/src/i386/usr/bin GROFF_FONT_PATH=/usr/obj/mnt/.1/release/src/i386/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/mnt/.1/release/src/i386/usr/share/tmac PATH=/usr/obj/mnt/.1/release/src/i386/usr/sbin:/usr/obj/mnt/.1/release/src/i386/usr/bin:/usr/obj/mnt/.1/release/src/i386/usr/games:/tmp/install.22943 make -f Makefile.inc1 reinstall -------------------------------------------------------------- >>> Making hierarchy -------------------------------------------------------------- cd /mnt/.1/release/src; make -f Makefile.inc1 hierarchy cd /mnt/.1/release/src/etc; make distrib-dirs `grep "^[a-zA-Z]" /mnt/.1/release/src/etc/locale.deprecated`; while [ $# -gt 0 ] ; do for dir in /usr/share/locale /usr/share/nls /usr/local/share/nls; do test -d /mnt/.1/release/chroot/${dir} && cd /mnt/.1/release/chroot/${dir}; test -L "$2" && rm -rf "$2"; test \! -L "$1" && test -d "$1" && mv "$1" "$2"; done; shift; shift; done mtree -deU -f /mnt/.1/release/src/etc/mtree/BSD.root.dist -p /mnt/.1/release/chroot/ [skip lot's of mtree's output] mtree -deU -f /mnt/.1/release/src/etc/mtree/BSD.sendmail.dist -p /mnt/.1/release/chroot/ ./var/spool/clientmqueue missing (created) cd /mnt/.1/release/chroot/; rm -f /mnt/.1/release/chroot/sys; ln -s usr/src/sys sys cd /mnt/.1/release/chroot/usr/share/man/en.ISO8859-1; ln -sf ../man* . cd /mnt/.1/release/chroot/usr/share/man; `grep "^[a-zA-Z]" /mnt/.1/release/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done -------------------------------------------------------------- >>> Installing everything.. -------------------------------------------------------------- cd /mnt/.1/release/src; make -f Makefile.inc1 install ===> share/info install -o root -g wheel -m 444 dir-tmpl /mnt/.1/release/chroot/usr/share/info/dir install: not found *** Error code 127 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 4:54:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDDBC37B401 for ; Sun, 17 Nov 2002 04:54:55 -0800 (PST) Received: from fubar.adept.org (fubar.adept.org [63.147.172.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8916A43E42 for ; Sun, 17 Nov 2002 04:54:55 -0800 (PST) (envelope-from mike@adept.org) Received: by fubar.adept.org (Postfix, from userid 1001) id 5EA161527E; Sun, 17 Nov 2002 04:54:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by fubar.adept.org (Postfix) with ESMTP id 5C77115247 for ; Sun, 17 Nov 2002 04:54:07 -0800 (PST) Date: Sun, 17 Nov 2002 04:54:07 -0800 (PST) From: Mike Hoskins To: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD: Server or Desktop OS? In-Reply-To: <3DD73B47.6000105@tenebras.com> Message-ID: <20021117044229.Q29719-100000@fubar.adept.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 16 Nov 2002, Michael Sierchio wrote: > Lefteris Tsintjelis wrote: > > It sure is misleading. Why is it called -stable then? You would expect > > to stand up to its name. > Cf. Humpty Dumpty, I'm afraid. -STABLE doesn't mean stable at all. Please don't start this adolescant flamefest again. Any newbie who reads the handbook should understand the meaning of "stable". (It's all spelled out in black and white.) Any non-newbie who's actually been involved with software products should understand the typical use of a -STABLE branch. I'm not sure if the earlier post claiming -stable use since '94 or so is accurate, but if it is, as another pointed out, you should have seen similar periods in -STABLE before now and been better prepared to avoid these types of situations. Anything but -RELEASE is a development branch, that's typically how software projects go. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 5:29:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD4E037B401; Sun, 17 Nov 2002 05:29:35 -0800 (PST) Received: from majordomo.vol.cz (smtp4.vol.cz [195.250.128.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEF6143E77; Sun, 17 Nov 2002 05:29:33 -0800 (PST) (envelope-from dan@obluda.cz) Received: from obluda.cz (xkulesh.vol.cz [195.250.154.106]) by majordomo.vol.cz (8.12.6/8.12.6) with ESMTP id gAHDTPeG027581; Sun, 17 Nov 2002 14:29:26 +0100 (CET) (envelope-from dan@obluda.cz) Message-ID: <3DD62BA4.5040702@obluda.cz> Date: Sat, 16 Nov 2002 12:27:32 +0100 From: Dan Lukes User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021106 X-Accept-Language: en, cs MIME-Version: 1.0 To: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: if_ef doesn't work with if_fxp? References: <200211131926.gADJQMFo011478_zibbi.icomtek.csir.co.za@ns.sol.net> <20021114101959.E72890-100000_hub.org@ns.sol.net> In-Reply-To: <200211131926.gADJQMFo011478_zibbi.icomtek.csir.co.za@ns.sol.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG scrappy@hub.org wrote, On 11/14/02 15:26: > I checked with our network/netware guy, and he's told me that we're > running "0 interface with an Ethernet_II frame", so I've got fxp0f0 > configured with our network number, which he's given me as 0x83a2c800 Yust for fun - 0x83a2c800=131.162.200.0, so your try to hide real IP by "xx"ing it has failed. > Our network is a B-Class, with from x.x.128.x up being divided into > subnets of 8 C-classes each ... so subnet 128, 136, 144, etc ... > > our netware server is on subnet 200, which is the 83a2c800 that he's given Well - we must diferentiate what we are speaking about. If you are trying to set up IPX network, then the informations about IP network topology is irelevant. You need to know the IPX network topology, IPX network numbers and so on. I don't know what the 0x83A2C800 number is - it seems to be IP not IPX network number, but I'm not sure. You should ask your Netware server administrator. > me ... the computer I'm working on is a laptop, so will be on several > different subnets, but never on subnet 200 ... is 83a2c800 the netnum The correct IPX network number must be set to the same number as the IPX network number assigned to network avaiable on cable you are connected in. Under Windows seems to be possible set the IPX network to 0x000000 requesting autodetection of the correct value. As you know, there must be a properly configured IPX router between you and server unless your IPX adress is from the same IPX NET as server's (it is similar law as for IP) Dan -- Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206 root of FIONet, KolejNET, webmaster of www.freebsd.cz AKA: dan@obluda.cz, dan@freebsd.cz,dan@kolej.mff.cuni.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 5:29:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E81EC37B404 for ; Sun, 17 Nov 2002 05:29:39 -0800 (PST) Received: from majordomo.vol.cz (smtp4.vol.cz [195.250.128.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8F8D43E8A for ; Sun, 17 Nov 2002 05:29:38 -0800 (PST) (envelope-from dan@obluda.cz) Received: from obluda.cz (xkulesh.vol.cz [195.250.154.106]) by majordomo.vol.cz (8.12.6/8.12.6) with ESMTP id gAHDTYeG027592; Sun, 17 Nov 2002 14:29:35 +0100 (CET) (envelope-from dan@obluda.cz) Message-ID: <3DD772E8.2070809@obluda.cz> Date: Sun, 17 Nov 2002 11:43:52 +0100 From: Dan Lukes User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021106 X-Accept-Language: en, cs MIME-Version: 1.0 To: freebsd-stable@freebsd.org Cc: plusik@pohoda.cz Subject: Re: cannot compile stable [LONG !] References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tomas Pluskal wrote, On 11/15/02 17:29: > [root@eddie getconf]# make > awk '/^[_A-Z]/ { print; }' confstr.gperf | sed -e 's/,$//' >confstr.names > awk '/^[_A-Z]/ { print; }' limits.gperf | sed -e 's/,$//' >limits.names > awk '/^[_A-Z]/ { print; }' sysconf.gperf | sed -e 's/,$//' >sysconf.names > cat confstr.names limits.names sysconf.names >conflicting.names > sort -u conflicting.names >unique.names > Name conflicts found! > *** Error code 1 Well, so we must locate the point of problem. After my last cvsup of stable, the files in question have following versions: confstr.gperf: * $FreeBSD: src/usr.bin/getconf/confstr.gperf,v 1.4.2.1 2002/10/27 04:18:40 wollman Exp $ limits.gperf: * $FreeBSD: src/usr.bin/getconf/limits.gperf,v 1.1.2.1 2002/10/27 04:18:40 wollman Exp $ sysconf.gperf: * $FreeBSD: src/usr.bin/getconf/sysconf.gperf,v 1.4.2.1 2002/10/27 04:18:40 wollman Exp $ Makefile * $FreeBSD: src/usr.bin/getconf/Makefile,v 1.3.2.1 2002/10/27 04:18:40 wollman Exp $ If you have other version, it is problem with cvsup. The result of running awk '/^[_A-Z]/ { print; }' $FILENAME: ----------- confstr.gperf ---------------- PATH, _CS_PATH POSIX_V6_ILP32_OFF32_CFLAGS, _CS_POSIX_V6_ILP32_OFF32_CFLAGS POSIX_V6_ILP32_OFF32_LDFLAGS, _CS_POSIX_V6_ILP32_OFF32_LDFLAGS POSIX_V6_ILP32_OFF32_LIBS, _CS_POSIX_V6_ILP32_OFF32_LIBS POSIX_V6_ILP32_OFFBIG_CFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_CFLAGS POSIX_V6_ILP32_OFFBIG_LDFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_LDFLAGS POSIX_V6_ILP32_OFFBIG_LIBS, _CS_POSIX_V6_ILP32_OFFBIG_LIBS POSIX_V6_LP64_OFF64_CFLAGS, _CS_POSIX_V6_LP64_OFF64_CFLAGS POSIX_V6_LP64_OFF64_LDFLAGS, _CS_POSIX_V6_LP64_OFF64_LDFLAGS POSIX_V6_LP64_OFF64_LIBS, _CS_POSIX_V6_LP64_OFF64_LIBS POSIX_V6_LPBIG_OFFBIG_CFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_CFLAGS POSIX_V6_LPBIG_OFFBIG_LDFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_LDFLAGS POSIX_V6_LPBIG_OFFBIG_LIBS, _CS_POSIX_V6_LPBIG_OFFBIG_LIBS POSIX_V6_WIDTH_RESTRICTED_ENVS, _CS_POSIX_V6_WIDTH_RESTRICTED_ENVS _POSIX_V6_ILP32_OFF32_CFLAGS, _CS_POSIX_V6_ILP32_OFF32_CFLAGS _POSIX_V6_ILP32_OFF32_LDFLAGS, _CS_POSIX_V6_ILP32_OFF32_LDFLAGS _POSIX_V6_ILP32_OFF32_LIBS, _CS_POSIX_V6_ILP32_OFF32_LIBS _POSIX_V6_ILP32_OFFBIG_CFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_CFLAGS _POSIX_V6_ILP32_OFFBIG_LDFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_LDFLAGS _POSIX_V6_ILP32_OFFBIG_LIBS, _CS_POSIX_V6_ILP32_OFFBIG_LIBS _POSIX_V6_LP64_OFF64_CFLAGS, _CS_POSIX_V6_LP64_OFF64_CFLAGS _POSIX_V6_LP64_OFF64_LDFLAGS, _CS_POSIX_V6_LP64_OFF64_LDFLAGS _POSIX_V6_LP64_OFF64_LIBS, _CS_POSIX_V6_LP64_OFF64_LIBS _POSIX_V6_LPBIG_OFFBIG_CFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_CFLAGS _POSIX_V6_LPBIG_OFFBIG_LDFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_LDFLAGS _POSIX_V6_LPBIG_OFFBIG_LIBS, _CS_POSIX_V6_LPBIG_OFFBIG_LIBS _POSIX_V6_WIDTH_RESTRICTED_ENVS, _CS_POSIX_V6_WIDTH_RESTRICTED_ENVS ----------- limits.gperf ---------------- _POSIX_CLOCKRES_MIN, _POSIX_CLOCKRES_MIN _POSIX_AIO_LISTIO_MAX, _POSIX_AIO_LISTIO_MAX _POSIX_AIO_MAX, _POSIX_AIO_MAX _POSIX_ARG_MAX, _POSIX_ARG_MAX _POSIX_CHILD_MAX, _POSIX_CHILD_MAX _POSIX_DELAYTIMER_MAX, _POSIX_DELAYTIMER_MAX _POSIX_HOST_NAME_MAX, _POSIX_HOST_NAME_MAX _POSIX_LINK_MAX, _POSIX_LINK_MAX _POSIX_LOGIN_NAME_MAX, _POSIX_LOGIN_NAME_MAX _POSIX_MAX_CANON, _POSIX_MAX_CANON _POSIX_MAX_INPUT, _POSIX_MAX_INPUT _POSIX_MQ_OPEN_MAX, _POSIX_MQ_OPEN_MAX _POSIX_MQ_PRIO_MAX, _POSIX_MQ_PRIO_MAX _POSIX_NAME_MAX, _POSIX_NAME_MAX _POSIX_NGROUPS_MAX, _POSIX_NGROUPS_MAX _POSIX_OPEN_MAX, _POSIX_OPEN_MAX _POSIX_PATH_MAX, _POSIX_PATH_MAX _POSIX_PIPE_BUF, __POSIX_PIPE_BUF _POSIX_RE_DUP_MAX, _POSIX_RE_DUP_MAX _POSIX_RTSIG_MAX, _POSIX_RTSIG_MAX _POSIX_SEM_NSEMS_MAX, _POSIX_SEM_NSEMS_MAX _POSIX_SEM_VALUE_MAX, _POSIX_SEM_VALUE_MAX _POSIX_SIGQUEUE_MAX, _POSIX_SIGQUEUE_MAX _POSIX_SSIZE_MAX, _POSIX_SSIZE_MAX _POSIX_STREAM_MAX, _POSIX_STREAM_MAX _POSIX_SS_REPL_MAX, _POSIX_SS_REPL_MAX _POSIX_SYMLINK_MAX, _POSIX_SYMLINK_MAX _POSIX_SYMLOOP_MAX, _POSIX_SYMLOOP_MAX _POSIX_THREAD_DESTRUCTOR_ITERATIONS, _POSIX_THREAD_DESTRUCTOR_ITERATIONS _POSIX_THREAD_KEYS_MAX, _POSIX_THREAD_KEYS_MAX _POSIX_THREAD_THREADS_MAX, _POSIX_THREAD_THREADS_MAX _POSIX_TIMER_MAX, _POSIX_TIMER_MAX _POSIX_TRACE_EVENT_NAME_MAX, _POSIX_TRACE_EVENT_NAME_MAX _POSIX_TRACE_NAME_MAX, _POSIX_TRACE_NAME_MAX _POSIX_TRACE_SYS_MAX, _POSIX_TRACE_SYS_MAX _POSIX_TRACE_USER_EVENT_MAX, _POSIX_TRACE_USER_EVENT_MAX _POSIX_TTY_NAME_MAX, _POSIX_TTY_NAME_MAX _POSIX_TZNAME_MAX, _POSIX_TZNAME_MAX _POSIX2_BC_BASE_MAX, _POSIX2_BC_BASE_MAX _POSIX2_BC_DIM_MAX, _POSIX2_BC_DIM_MAX _POSIX2_BC_SCALE_MAX, _POSIX2_BC_SCALE_MAX _POSIX2_BC_STRING_MAX, _POSIX2_BC_STRING_MAX _POSIX2_CHARCLASS_NAME_MAX, _POSIX2_CHARCLASS_NAME_MAX _POSIX2_COLL_WEIGHTS_MAX, _POSIX2_COLL_WEIGHTS_MAX _POSIX2_EXPR_NEXT_MAX, _POSIX2_EXPR_NEST_MAX _POSIX2_LINE_MAX, _POSIX2_LINE_MAX _POSIX2_RE_DUP_MAX, _POSIX2_RE_DUP_MAX _XOPEN_IOV_MAX, _XOPEN_IOV_MAX _XOPEN_NAME_MAX, _XOPEN_NAME_MAX _XOPEN_PATH_MAX, _XOPEN_PATH_MAX CHAR_BIT, CHAR_BIT CHAR_MAX, CHAR_MAX CHAR_MIN, CHAR_MIN INT_MAX, INT_MAX INT_MIN, INT_MIN LLONG_MIN, LLONG_MIN LLONG_MAX, LLONG_MAX LONG_BIT, LONG_BIT LONG_MAX, LONG_MAX LONG_MIN, LONG_MIN MB_LEN_MAX, MB_LEN_MAX SCHAR_MAX, SCHAR_MAX SCHAR_MIN, SCHAR_MIN SHRT_MAX, SHRT_MAX SHRT_MIN, SHRT_MIN SSIZE_MAX, SSIZE_MAX UCHAR_MAX, UCHAR_MAX UINT_MAX, UINT_MAX ULLONG_MAX, ULLONG_MAX ULONG_MAX, ULONG_MAX USHRT_MAX, USHRT_MAX WORD_BIT, WORD_BIT CHARCLASS_NAME_MAX, CHARCLASS_NAME_MAX NL_ARGMAX, NL_ARGMAX ML_LANGMAX, NL_LANGMAX NL_MSGMAX, NL_MSGMAX NL_NMAX, NL_NMAX NL_SETMAX, NL_SETMAX NL_TEXTMAX, NL_TEXTMAX NZERO, NZERO ----------- sysconf.gperf ---------------- AIO_LISTIO_MAX, _SC_AIO_LISTIO_MAX AIO_MAX, _SC_AIO_MAX AIO_PRIO_DELTA_MAX, _SC_AIO_PRIO_DELTA_MAX ARG_MAX, _SC_ARG_MAX ATEXIT_MAX, _SC_ATEXIT_MAX BC_BASE_MAX, _SC_BC_BASE_MAX BC_DIM_MAX, _SC_BC_DIM_MAX BC_SCALE_MAX, _SC_BC_SCALE_MAX BC_STRING_MAX, _SC_BC_STRING_MAX CHILD_MAX, _SC_CHILD_MAX CLK_TCK, _SC_CLK_TCK COLL_WEIGHTS_MAX, _SC_COLL_WEIGHTS_MAX DELAYTIMER_MAX, _SC_DELAYTIMER_MAX EXPR_NEST_MAX, _SC_EXPR_NEST_MAX GETGR_R_SIZE_MAX, _SC_GETGR_R_SIZE_MAX GETPW_R_SIZE_MAX, _SC_GETPW_R_SIZE_MAX HOST_NAME_MAX, _SC_HOST_NAME_MAX IOV_MAX, _SC_IOV_MAX LINE_MAX, _SC_LINE_MAX LOGIN_NAME_MAX, _SC_LOGIN_NAME_MAX MQ_OPEN_MAX, _SC_MQ_OPEN_MAX MQ_PRIO_MAX, _SC_MQ_PRIO_MAX NGROUPS_MAX, _SC_NGROUPS_MAX NPROCESSORS_CONF, _SC_NPROCESSORS_CONF NPROCESSORS_ONLN, _SC_NPROCESSORS_ONLN OPEN_MAX, _SC_OPEN_MAX PAGESIZE, _SC_PAGESIZE PAGE_SIZE, _SC_PAGESIZE PASS_MAX, _SC_PASS_MAX PTHREAD_DESTRUCTOR_ITERATIONS, _SC_THREAD_DESTRUCTOR_ITERATIONS PTHREAD_KEYS_MAX, _SC_THREAD_KEYS_MAX PTHREAD_STACK_MIN, _SC_THREAD_STACK_MIN PTHREAD_THREADS_MAX, _SC_THREAD_THREADS_MAX RE_DUP_MAX, _SC_RE_DUP_MAX RTSIG_MAX, _SC_RTSIG_MAX SEM_NSEMS_MAX, _SC_SEM_NSEMS_MAX SEM_VALUE_MAX, _SC_SEM_VALUE_MAX SIGQUEUE_MAX, _SC_SIGQUEUE_MAX STREAM_MAX, _SC_STREAM_MAX SYMLOOP_MAX, _SC_SYMLOOP_MAX TIMER_MAX, _SC_TIMER_MAX TTY_NAME_MAX, _SC_TTY_NAME_MAX TZNAME_MAX, _SC_TZNAME_MAX _POSIX2_CHAR_TERM, _SC_2_CHAR_TERM _POSIX2_C_BIND, _SC_2_C_BIND _POSIX2_C_DEV, _SC_2_C_DEV _POSIX2_C_VERSION, _SC_2_C_VERSION _POSIX2_FORT_DEV, _SC_2_FORT_DEV _POSIX2_FORT_RUN, _SC_2_FORT_RUN _POSIX2_LOCALEDEF, _SC_2_LOCALEDEF _POSIX2_SW_DEV, _SC_2_SW_DEV _POSIX2_UPE, _SC_2_UPE _POSIX2_VERSION, _SC_2_VERSION _POSIX_ASYNCHRONOUS_IO, _SC_ASYNCHRONOUS_IO _POSIX_BARRIERS, _SC_BARRIERS _POSIX_CLOCK_SELECTION, _SC_CLOCK_SELECTION _POSIX_CPUTIME, _SC_CPUTIME _POSIX_FILE_LOCKING, _SC_FILE_LOCKING _POSIX_FSYNC, _SC_FSYNC _POSIX_IPV6, _SC_IPV6 _POSIX_JOB_CONTROL, _SC_JOB_CONTROL _POSIX_MAPPED_FILES, _SC_MAPPED_FILES _POSIX_MEMLOCK, _SC_MEMLOCK _POSIX_MEMLOCK_RANGE, _SC_MEMLOCK_RANGE _POSIX_MEMORY_PROTECTION, _SC_MEMORY_PROTECTION _POSIX_MESSAGE_PASSING, _SC_MESSAGE_PASSING _POSIX_MONOTONIC_CLOCK, _SC_MONOTONIC_CLOCK _POSIX_PRIORITIZED_IO, _SC_PRIORITIZED_IO _POSIX_PRIORITY_SCHEDULING, _SC_PRIORITY_SCHEDULING _POSIX_READER_WRITER_LOCKS, _SC_READER_WRITER_LOCKS _POSIX_REALTIME_SIGNALS, _SC_REALTIME_SIGNALS _POSIX_REGEXP, _SC_REGEXP _POSIX_SAVED_IDS, _SC_SAVED_IDS _POSIX_SEMAPHORES, _SC_SEMAPHORES _POSIX_SHARED_MEMORY_OBJECTS, _SC_SHARED_MEMORY_OBJECTS _POSIX_SHELL, _SC_SHELL _POSIX_SPAWN, _SC_SPAWN _POSIX_SPIN_LOCKS, _SC_SPIN_LOCKS _POSIX_SPORADIC_SERVER, _SC_SPORADIC_SERVER _POSIX_SYNCHRONIZED_IO, _SC_SYNCHRONIZED_IO _POSIX_THREADS, _SC_THREADS _POSIX_THREAD_ATTR_STACKADDR, _SC_THREAD_ATTR_STACKADDR _POSIX_THREAD_ATTR_STACKSIZE, _SC_THREAD_ATTR_STACKSIZE _POSIX_THREAD_CPUTIME, _SC_THREAD_CPUTIME _POSIX_THREAD_PRIORITY_SCHEDULING, _SC_THREAD_PRIORITY_SCHEDULING _POSIX_THREAD_PRIO_INHERIT, _SC_THREAD_PRIO_INHERIT _POSIX_THREAD_PRIO_PROTECT, _SC_THREAD_PRIO_PROTECT _POSIX_THREAD_PROCESS_SHARED, _SC_THREAD_PROCESS_SHARED _POSIX_THREAD_SAFE_FUNCTIONS, _SC_THREAD_SAFE_FUNCTIONS _POSIX_THREAD_SPORADIC_SERVER, _SC_THREAD_SPORADIC_SERVER _POSIX_TIMEOUTS, _SC_TIMEOUTS _POSIX_TRACE, _SC_TRACE _POSIX_TRACE_EVENT_FILTER, _SC_TRACE_EVENT_FILTER _POSIX_TRACE_INHERIT, _SC_TRACE_INHERIT _POSIX_TRACE_LOG, _SC_TRACE_LOG _POSIX_TIMERS, _SC_TIMERS _POSIX_TYPED_MEMORY_OBJECTS, _SC_TYPED_MEMORY_OBJECTS _POSIX_VERSION, _SC_VERSION _POSIX_V6_ILP32_OFF32, _SC_V6_ILP32_OFF32 _POSIX_V6_ILP32_OFFBIG, _SC_V6_ILP32_OFFBIG _POSIX_V6_LP64_OFF64, _SC_V6_LP64_OFF64 _POSIX_V6_LP64_OFFBIG, _SC_V6_LP64_OFFBIG _XOPEN_CRYPT, _SC_XOPEN_CRYPT _XOPEN_ENH_I18N, _SC_XOPEN_ENH_I18N _XOPEN_LEGACY, _SC_XOPEN_LEGACY _XOPEN_REALTIME, _SC_XOPEN_REALTIME _XOPEN_REALTIME_THREADS, _SC_XOPEN_REALTIME_THREADS _XOPEN_SHM, _SC_XOPEN_SHM _XOPEN_UNIX, _SC_XOPEN_UNIX _XOPEN_VERSION, _SC_XOPEN_VERSION _XOPEN_XCU_VERSION, _SC_XCU_VERSION ----------------------------------------------------------------------------------- If got other results, you may have problem with awk. 'sed' did nothing, so content of *.names should be the same as above. If got other results, you may have problem with sed. Next, the concatenation to conflicting.names. I trust the 'cat', so ve check the number of lines only: wc -l confstr.names limits.names sysconf.names 27 confstr.names 80 limits.names 111 sysconf.names 218 total wc -l conflicting.names 218 conflicting.names Then, sort -u conflicting.names creates the unique.names: ----------- unique.names ----------------AIO_LISTIO_MAX, _SC_AIO_LISTIO_MAX AIO_MAX, _SC_AIO_MAX AIO_PRIO_DELTA_MAX, _SC_AIO_PRIO_DELTA_MAX ARG_MAX, _SC_ARG_MAX ATEXIT_MAX, _SC_ATEXIT_MAX BC_BASE_MAX, _SC_BC_BASE_MAX BC_DIM_MAX, _SC_BC_DIM_MAX BC_SCALE_MAX, _SC_BC_SCALE_MAX BC_STRING_MAX, _SC_BC_STRING_MAX CHARCLASS_NAME_MAX, CHARCLASS_NAME_MAX CHAR_BIT, CHAR_BIT CHAR_MAX, CHAR_MAX CHAR_MIN, CHAR_MIN CHILD_MAX, _SC_CHILD_MAX CLK_TCK, _SC_CLK_TCK COLL_WEIGHTS_MAX, _SC_COLL_WEIGHTS_MAX DELAYTIMER_MAX, _SC_DELAYTIMER_MAX EXPR_NEST_MAX, _SC_EXPR_NEST_MAX GETGR_R_SIZE_MAX, _SC_GETGR_R_SIZE_MAX GETPW_R_SIZE_MAX, _SC_GETPW_R_SIZE_MAX HOST_NAME_MAX, _SC_HOST_NAME_MAX INT_MAX, INT_MAX INT_MIN, INT_MIN IOV_MAX, _SC_IOV_MAX LINE_MAX, _SC_LINE_MAX LLONG_MAX, LLONG_MAX LLONG_MIN, LLONG_MIN LOGIN_NAME_MAX, _SC_LOGIN_NAME_MAX LONG_BIT, LONG_BIT LONG_MAX, LONG_MAX LONG_MIN, LONG_MIN MB_LEN_MAX, MB_LEN_MAX ML_LANGMAX, NL_LANGMAX MQ_OPEN_MAX, _SC_MQ_OPEN_MAX MQ_PRIO_MAX, _SC_MQ_PRIO_MAX NGROUPS_MAX, _SC_NGROUPS_MAX NL_ARGMAX, NL_ARGMAX NL_MSGMAX, NL_MSGMAX NL_NMAX, NL_NMAX NL_SETMAX, NL_SETMAX NL_TEXTMAX, NL_TEXTMAX NPROCESSORS_CONF, _SC_NPROCESSORS_CONF NPROCESSORS_ONLN, _SC_NPROCESSORS_ONLN NZERO, NZERO OPEN_MAX, _SC_OPEN_MAX PAGESIZE, _SC_PAGESIZE PAGE_SIZE, _SC_PAGESIZE PASS_MAX, _SC_PASS_MAX PATH, _CS_PATH POSIX_V6_ILP32_OFF32_CFLAGS, _CS_POSIX_V6_ILP32_OFF32_CFLAGS POSIX_V6_ILP32_OFF32_LDFLAGS, _CS_POSIX_V6_ILP32_OFF32_LDFLAGS POSIX_V6_ILP32_OFF32_LIBS, _CS_POSIX_V6_ILP32_OFF32_LIBS POSIX_V6_ILP32_OFFBIG_CFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_CFLAGS POSIX_V6_ILP32_OFFBIG_LDFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_LDFLAGS POSIX_V6_ILP32_OFFBIG_LIBS, _CS_POSIX_V6_ILP32_OFFBIG_LIBS POSIX_V6_LP64_OFF64_CFLAGS, _CS_POSIX_V6_LP64_OFF64_CFLAGS POSIX_V6_LP64_OFF64_LDFLAGS, _CS_POSIX_V6_LP64_OFF64_LDFLAGS POSIX_V6_LP64_OFF64_LIBS, _CS_POSIX_V6_LP64_OFF64_LIBS POSIX_V6_LPBIG_OFFBIG_CFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_CFLAGS POSIX_V6_LPBIG_OFFBIG_LDFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_LDFLAGS POSIX_V6_LPBIG_OFFBIG_LIBS, _CS_POSIX_V6_LPBIG_OFFBIG_LIBS POSIX_V6_WIDTH_RESTRICTED_ENVS, _CS_POSIX_V6_WIDTH_RESTRICTED_ENVS PTHREAD_DESTRUCTOR_ITERATIONS, _SC_THREAD_DESTRUCTOR_ITERATIONS PTHREAD_KEYS_MAX, _SC_THREAD_KEYS_MAX PTHREAD_STACK_MIN, _SC_THREAD_STACK_MIN PTHREAD_THREADS_MAX, _SC_THREAD_THREADS_MAX RE_DUP_MAX, _SC_RE_DUP_MAX RTSIG_MAX, _SC_RTSIG_MAX SCHAR_MAX, SCHAR_MAX SCHAR_MIN, SCHAR_MIN SEM_NSEMS_MAX, _SC_SEM_NSEMS_MAX SEM_VALUE_MAX, _SC_SEM_VALUE_MAX SHRT_MAX, SHRT_MAX SHRT_MIN, SHRT_MIN SIGQUEUE_MAX, _SC_SIGQUEUE_MAX SSIZE_MAX, SSIZE_MAX STREAM_MAX, _SC_STREAM_MAX SYMLOOP_MAX, _SC_SYMLOOP_MAX TIMER_MAX, _SC_TIMER_MAX TTY_NAME_MAX, _SC_TTY_NAME_MAX TZNAME_MAX, _SC_TZNAME_MAX UCHAR_MAX, UCHAR_MAX UINT_MAX, UINT_MAX ULLONG_MAX, ULLONG_MAX ULONG_MAX, ULONG_MAX USHRT_MAX, USHRT_MAX WORD_BIT, WORD_BIT _POSIX2_BC_BASE_MAX, _POSIX2_BC_BASE_MAX _POSIX2_BC_DIM_MAX, _POSIX2_BC_DIM_MAX _POSIX2_BC_SCALE_MAX, _POSIX2_BC_SCALE_MAX _POSIX2_BC_STRING_MAX, _POSIX2_BC_STRING_MAX _POSIX2_CHARCLASS_NAME_MAX, _POSIX2_CHARCLASS_NAME_MAX _POSIX2_CHAR_TERM, _SC_2_CHAR_TERM _POSIX2_COLL_WEIGHTS_MAX, _POSIX2_COLL_WEIGHTS_MAX _POSIX2_C_BIND, _SC_2_C_BIND _POSIX2_C_DEV, _SC_2_C_DEV _POSIX2_C_VERSION, _SC_2_C_VERSION _POSIX2_EXPR_NEXT_MAX, _POSIX2_EXPR_NEST_MAX _POSIX2_FORT_DEV, _SC_2_FORT_DEV _POSIX2_FORT_RUN, _SC_2_FORT_RUN _POSIX2_LINE_MAX, _POSIX2_LINE_MAX _POSIX2_LOCALEDEF, _SC_2_LOCALEDEF _POSIX2_RE_DUP_MAX, _POSIX2_RE_DUP_MAX _POSIX2_SW_DEV, _SC_2_SW_DEV _POSIX2_UPE, _SC_2_UPE _POSIX2_VERSION, _SC_2_VERSION _POSIX_AIO_LISTIO_MAX, _POSIX_AIO_LISTIO_MAX _POSIX_AIO_MAX, _POSIX_AIO_MAX _POSIX_ARG_MAX, _POSIX_ARG_MAX _POSIX_ASYNCHRONOUS_IO, _SC_ASYNCHRONOUS_IO _POSIX_BARRIERS, _SC_BARRIERS _POSIX_CHILD_MAX, _POSIX_CHILD_MAX _POSIX_CLOCKRES_MIN, _POSIX_CLOCKRES_MIN _POSIX_CLOCK_SELECTION, _SC_CLOCK_SELECTION_POSIX_CPUTIME, _SC_CPUTIME _POSIX_DELAYTIMER_MAX, _POSIX_DELAYTIMER_MAX _POSIX_FILE_LOCKING, _SC_FILE_LOCKING _POSIX_FSYNC, _SC_FSYNC _POSIX_HOST_NAME_MAX, _POSIX_HOST_NAME_MAX _POSIX_IPV6, _SC_IPV6 _POSIX_JOB_CONTROL, _SC_JOB_CONTROL _POSIX_LINK_MAX, _POSIX_LINK_MAX _POSIX_LOGIN_NAME_MAX, _POSIX_LOGIN_NAME_MAX _POSIX_MAPPED_FILES, _SC_MAPPED_FILES _POSIX_MAX_CANON, _POSIX_MAX_CANON _POSIX_MAX_INPUT, _POSIX_MAX_INPUT _POSIX_MEMLOCK, _SC_MEMLOCK _POSIX_MEMLOCK_RANGE, _SC_MEMLOCK_RANGE _POSIX_MEMORY_PROTECTION, _SC_MEMORY_PROTECTION _POSIX_MESSAGE_PASSING, _SC_MESSAGE_PASSING _POSIX_MONOTONIC_CLOCK, _SC_MONOTONIC_CLOCK _POSIX_MQ_OPEN_MAX, _POSIX_MQ_OPEN_MAX _POSIX_MQ_PRIO_MAX, _POSIX_MQ_PRIO_MAX _POSIX_NAME_MAX, _POSIX_NAME_MAX _POSIX_NGROUPS_MAX, _POSIX_NGROUPS_MAX _POSIX_OPEN_MAX, _POSIX_OPEN_MAX _POSIX_PATH_MAX, _POSIX_PATH_MAX _POSIX_PIPE_BUF, __POSIX_PIPE_BUF _POSIX_PRIORITIZED_IO, _SC_PRIORITIZED_IO _POSIX_PRIORITY_SCHEDULING, _SC_PRIORITY_SCHEDULING _POSIX_READER_WRITER_LOCKS, _SC_READER_WRITER_LOCKS _POSIX_REALTIME_SIGNALS, _SC_REALTIME_SIGNALS _POSIX_REGEXP, _SC_REGEXP _POSIX_RE_DUP_MAX, _POSIX_RE_DUP_MAX _POSIX_RTSIG_MAX, _POSIX_RTSIG_MAX _POSIX_SAVED_IDS, _SC_SAVED_IDS _POSIX_SEMAPHORES, _SC_SEMAPHORES _POSIX_SEM_NSEMS_MAX, _POSIX_SEM_NSEMS_MAX _POSIX_SEM_VALUE_MAX, _POSIX_SEM_VALUE_MAX _POSIX_SHARED_MEMORY_OBJECTS, _SC_SHARED_MEMORY_OBJECTS _POSIX_SHELL, _SC_SHELL _POSIX_SIGQUEUE_MAX, _POSIX_SIGQUEUE_MAX _POSIX_SPAWN, _SC_SPAWN _POSIX_SPIN_LOCKS, _SC_SPIN_LOCKS _POSIX_SPORADIC_SERVER, _SC_SPORADIC_SERVER _POSIX_SSIZE_MAX, _POSIX_SSIZE_MAX _POSIX_SS_REPL_MAX, _POSIX_SS_REPL_MAX _POSIX_STREAM_MAX, _POSIX_STREAM_MAX _POSIX_SYMLINK_MAX, _POSIX_SYMLINK_MAX _POSIX_SYMLOOP_MAX, _POSIX_SYMLOOP_MAX _POSIX_SYNCHRONIZED_IO, _SC_SYNCHRONIZED_IO _POSIX_THREADS, _SC_THREADS _POSIX_THREAD_ATTR_STACKADDR, _SC_THREAD_ATTR_STACKADDR _POSIX_THREAD_ATTR_STACKSIZE, _SC_THREAD_ATTR_STACKSIZE _POSIX_THREAD_CPUTIME, _SC_THREAD_CPUTIME _POSIX_THREAD_DESTRUCTOR_ITERATIONS, _POSIX_THREAD_DESTRUCTOR_ITERATIONS _POSIX_THREAD_KEYS_MAX, _POSIX_THREAD_KEYS_MAX _POSIX_THREAD_PRIORITY_SCHEDULING, _SC_THREAD_PRIORITY_SCHEDULING _POSIX_THREAD_PRIO_INHERIT, _SC_THREAD_PRIO_INHERIT _POSIX_THREAD_PRIO_PROTECT, _SC_THREAD_PRIO_PROTECT _POSIX_THREAD_PROCESS_SHARED, _SC_THREAD_PROCESS_SHARED _POSIX_THREAD_SAFE_FUNCTIONS, _SC_THREAD_SAFE_FUNCTIONS _POSIX_THREAD_SPORADIC_SERVER, _SC_THREAD_SPORADIC_SERVER _POSIX_THREAD_THREADS_MAX, _POSIX_THREAD_THREADS_MAX _POSIX_TIMEOUTS, _SC_TIMEOUTS _POSIX_TIMERS, _SC_TIMERS _POSIX_TIMER_MAX, _POSIX_TIMER_MAX _POSIX_TRACE, _SC_TRACE _POSIX_TRACE_EVENT_FILTER, _SC_TRACE_EVENT_FILTER _POSIX_TRACE_EVENT_NAME_MAX, _POSIX_TRACE_EVENT_NAME_MAX _POSIX_TRACE_INHERIT, _SC_TRACE_INHERIT _POSIX_TRACE_LOG, _SC_TRACE_LOG _POSIX_TRACE_NAME_MAX, _POSIX_TRACE_NAME_MAX _POSIX_TRACE_SYS_MAX, _POSIX_TRACE_SYS_MAX _POSIX_TRACE_USER_EVENT_MAX, _POSIX_TRACE_USER_EVENT_MAX _POSIX_TTY_NAME_MAX, _POSIX_TTY_NAME_MAX _POSIX_TYPED_MEMORY_OBJECTS, _SC_TYPED_MEMORY_OBJECTS _POSIX_TZNAME_MAX, _POSIX_TZNAME_MAX _POSIX_V6_ILP32_OFF32, _SC_V6_ILP32_OFF32 _POSIX_V6_ILP32_OFF32_CFLAGS, _CS_POSIX_V6_ILP32_OFF32_CFLAGS _POSIX_V6_ILP32_OFF32_LDFLAGS, _CS_POSIX_V6_ILP32_OFF32_LDFLAGS _POSIX_V6_ILP32_OFF32_LIBS, _CS_POSIX_V6_ILP32_OFF32_LIBS _POSIX_V6_ILP32_OFFBIG, _SC_V6_ILP32_OFFBIG _POSIX_V6_ILP32_OFFBIG_CFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_CFLAGS _POSIX_V6_ILP32_OFFBIG_LDFLAGS, _CS_POSIX_V6_ILP32_OFFBIG_LDFLAGS _POSIX_V6_ILP32_OFFBIG_LIBS, _CS_POSIX_V6_ILP32_OFFBIG_LIBS _POSIX_V6_LP64_OFF64, _SC_V6_LP64_OFF64 _POSIX_V6_LP64_OFF64_CFLAGS, _CS_POSIX_V6_LP64_OFF64_CFLAGS _POSIX_V6_LP64_OFF64_LDFLAGS, _CS_POSIX_V6_LP64_OFF64_LDFLAGS _POSIX_V6_LP64_OFF64_LIBS, _CS_POSIX_V6_LP64_OFF64_LIBS _POSIX_V6_LP64_OFFBIG, _SC_V6_LP64_OFFBIG _POSIX_V6_LPBIG_OFFBIG_CFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_CFLAGS _POSIX_V6_LPBIG_OFFBIG_LDFLAGS, _CS_POSIX_V6_LPBIG_OFFBIG_LDFLAGS _POSIX_V6_LPBIG_OFFBIG_LIBS, _CS_POSIX_V6_LPBIG_OFFBIG_LIBS _POSIX_V6_WIDTH_RESTRICTED_ENVS, _CS_POSIX_V6_WIDTH_RESTRICTED_ENVS _POSIX_VERSION, _SC_VERSION _XOPEN_CRYPT, _SC_XOPEN_CRYPT _XOPEN_ENH_I18N, _SC_XOPEN_ENH_I18N _XOPEN_IOV_MAX, _XOPEN_IOV_MAX _XOPEN_LEGACY, _SC_XOPEN_LEGACY _XOPEN_NAME_MAX, _XOPEN_NAME_MAX _XOPEN_PATH_MAX, _XOPEN_PATH_MAX _XOPEN_REALTIME, _SC_XOPEN_REALTIME _XOPEN_REALTIME_THREADS, _SC_XOPEN_REALTIME_THREADS _XOPEN_SHM, _SC_XOPEN_SHM _XOPEN_UNIX, _SC_XOPEN_UNIX _XOPEN_VERSION, _SC_XOPEN_VERSION _XOPEN_XCU_VERSION, _SC_XCU_VERSION --------------------------------------------------------------------------------------------------- The number of lines should be 218, e.g. equal to number of lines in conflicting.names. If got other results, you may have problem with sort. The show ends with checking for the equality mentioned above. Run "make conflicts". If you got the error, run 'make -n conflicts' - it print command used for comparing. Run 'set -x' then call the displayed command (note, if you are using bash, you must quote every '!' by backslash or you get '! event not found' error). If you don't see something like 'test 218 != 218' then problem may be shell command expansion. If you see it, but also got 'Name conflict found' the point of problem is 'test' command or 'if' construct. After you locate the right point of problem, we may continue. Hope it help. Cheers Dan -- Dan Lukes tel: +420 2 21914205, fax: +420 2 21914206 root of FIONet, KolejNET, webmaster of www.freebsd.cz AKA: dan@obluda.cz, dan@freebsd.cz,dan@kolej.mff.cuni.cz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 7: 7: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4548A37B401; Sun, 17 Nov 2002 07:07:08 -0800 (PST) Received: from smtp1.home.se (smtp1.home.se [195.66.35.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64AF443E9E; Sun, 17 Nov 2002 07:07:07 -0800 (PST) (envelope-from vidor@home.se) Received: from amd1800 vidor@home.se [217.210.92.52] by smtp1.home.se with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare; Sun, 17 Nov 2002 15:59:45 +0100 Message-ID: <003d01c28e4a$fe295180$0200a8c0@amd1800> From: "Vidor Demeter" To: Cc: Subject: Power off problem Date: Sun, 17 Nov 2002 16:07:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi all, I used to be a SuSE user but I've decided to install FreeBSD instead, which I do not regret. I had some great surprises compared to Linux, and I've decided to stay with FreeBSD! :-) So I'm quite new to FreeBSD and I will have some questions until I get the system run after my whishes. The first problem is that I can not manage to configure the system shutdown with power off option. I've compiled the kernel with the apm option and I changed the rc.conf file as well, with ' apm_enable="YES" ', but no luck. After the shutdown I have to power off the system with the Power Off button! :-( I can not find any further help on this but what I described here. Did I missed something? I have an AMD 1800+ XP CPU, with 256MB RAM and 40GB HD, Asus mobo. Can somebody help me ? TIA Vidor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 7:15: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7436937B401 for ; Sun, 17 Nov 2002 07:15:00 -0800 (PST) Received: from hotmail.com (f32.sea2.hotmail.com [207.68.165.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B19E43E75 for ; Sun, 17 Nov 2002 07:14:52 -0800 (PST) (envelope-from kmays2000@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 17 Nov 2002 07:14:52 -0800 Received: from 68.114.30.180 by sea2fd.sea2.hotmail.msn.com with HTTP; Sun, 17 Nov 2002 15:14:51 GMT X-Originating-IP: [68.114.30.180] From: "Kenneth Mays" To: scrappy@hub.org Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD: Server or Desktop OS? Date: Sun, 17 Nov 2002 10:14:51 -0500 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 17 Nov 2002 15:14:52.0092 (UTC) FILETIME=[13D107C0:01C28E4C] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Your question brings up an issue that was talked about several times, and it was addressed in the docs and the newsgroup. -STABLE is an engineering development branch that is 'more stable' than -CURRENT, but not more stable than -RELEASE. -STABLE is NOT for end users/customers for official production use (i.e. do so at your own risk). Some development companies call these 'interim builds' in relation to the 'alpha->beta->RC1->interim builds and more RCs->FR->RTM' type of cycle. The RELEASE maintainers have some docs talking about 'CURRENT->STABLE->RELEASE' and how it all works. As some people commented, -RELEASE is the main starting point for 'loaded' production servers. Implement small changes that only resolve a problem your having that wasn't fixed in -RELEASE which makes it easier for some people to find the problem (easier said than done). Read the entire section 19.2 (especially section 19.2.2.2) in the FreeBSD Handbook. '19.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT first for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users.' In other words, expect -STABLE not to be as stable as -RELEASE and that -STABLE may or may not crash. As a customer, I'd worry more if -RELEASE was crashing within less than 30 days on a properly configured system. -Ken _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 7:52:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F40C37B401 for ; Sun, 17 Nov 2002 07:52:11 -0800 (PST) Received: from grosbein.pp.ru (www2.svzserv.kemerovo.su [213.184.65.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6A1B43E6E for ; Sun, 17 Nov 2002 07:52:04 -0800 (PST) (envelope-from eugen@grosbein.pp.ru) Received: from grosbein.pp.ru (smmsp@localhost [127.0.0.1]) by grosbein.pp.ru (8.12.6/8.12.5) with ESMTP id gAHFpsT6000921; Sun, 17 Nov 2002 22:51:54 +0700 (KRAT) (envelope-from eugen@grosbein.pp.ru) Received: (from eugen@localhost) by grosbein.pp.ru (8.12.6/8.12.6/Submit) id gAHFnjLE000878; Sun, 17 Nov 2002 22:49:45 +0700 (KRAT) Date: Sun, 17 Nov 2002 22:49:45 +0700 From: Eugene Grosbein To: Kenneth Mays Cc: scrappy@hub.org, freebsd-stable@FreeBSD.ORG Subject: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) Message-ID: <20021117224945.A806@grosbein.pp.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kmays2000@hotmail.com on Sun, Nov 17, 2002 at 10:14:51AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 17, 2002 at 10:14:51AM -0500, Kenneth Mays wrote: > Your question brings up an issue that was talked about several times, and it > was addressed in the docs and the newsgroup. -STABLE is an engineering > development branch that is 'more stable' than -CURRENT, but not more stable > than -RELEASE. -STABLE is NOT for end users/customers for official > production use (i.e. do so at your own risk). I wonder why no one says that -STABLE really WAS stable and WAS intended for end users less than 2 years ago. Moreover, Hanbook said you need -STABLE if you are using FreeBSD in production environment and you need stability, Handbook said it even 15 months ago. And it has been assetring so for long time, that's where the name of this branch came from. Anyone can see that in CVS. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 8:23:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B11237B401 for ; Sun, 17 Nov 2002 08:23:29 -0800 (PST) Received: from wrzx35.rz.uni-wuerzburg.de (wrzx35.rz.uni-wuerzburg.de [132.187.3.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA40443E75 for ; Sun, 17 Nov 2002 08:23:21 -0800 (PST) (envelope-from q@uni.de) Received: from wrzx34.rz.uni-wuerzburg.de (wrzx34.rz.uni-wuerzburg.de [132.187.3.34]) by wrzx35.rz.uni-wuerzburg.de (8.8.8/8.8.8/uniwue-MM-1.05) with ESMTP id RAA17145 for ; Sun, 17 Nov 2002 17:23:19 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by virusscan.rz.uni-wuerzburg.de (Postfix) with ESMTP id 74651C25 for ; Sun, 17 Nov 2002 17:23:18 +0100 (CET) Received: from wrzx37.rz.uni-wuerzburg.de (wrzx37.rz.uni-wuerzburg.de [132.187.3.37]) by wrzx34.rz.uni-wuerzburg.de (Postfix) with ESMTP id 460EBC22 for ; Sun, 17 Nov 2002 17:23:18 +0100 (CET) Received: from frodo.galgenberg.net (galgenberg.net [132.187.222.250]) by wrzx37.rz.uni-wuerzburg.de (Postfix) with SMTP id 1F102A1AB for ; Sun, 17 Nov 2002 17:23:18 +0100 (CET) Received: (qmail 63736 invoked from network); 17 Nov 2002 16:23:17 -0000 Received: from gb-007.galgenberg.net (HELO roadrunner) (132.187.222.7) by galgenberg.net with SMTP; 17 Nov 2002 16:23:17 -0000 From: "Ulrich 'Q' Spoerlein" To: "Vidor Demeter" Cc: , Subject: Re: Power off problem Date: Sun, 17 Nov 2002 17:23:22 +0100 Organization: Hier koennte Ihre Werbung stehen! Message-ID: References: <003d01c28e4a$fe295180$0200a8c0@amd1800> In-Reply-To: <003d01c28e4a$fe295180$0200a8c0@amd1800> X-Mailer: Forte Agent 1.91/32.564 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS snapshot-20020422 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Nov 2002 16:07:04 +0100, you wrote: >The first problem is that I can not manage to configure the system >shutdown with power off option. I've compiled the kernel with the apm >option and I changed the rc.conf file as well, with ' apm_enable="YES" ', >but no luck. After the shutdown I have to power off the system with the >Power Off button! :-( halt -p or shutdown -p now it's in the manpage :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 9: 5:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EE6037B401 for ; Sun, 17 Nov 2002 09:05:13 -0800 (PST) Received: from pohoda.cz (pohoda.pohoda.cz [194.228.111.151]) by mx1.FreeBSD.org (Postfix) with SMTP id B0E7B43E77 for ; Sun, 17 Nov 2002 09:05:11 -0800 (PST) (envelope-from plusik@pohoda.cz) Received: (qmail 1655 invoked from network); 17 Nov 2002 17:05:14 -0000 Received: from plusik@pohoda.cz by pohoda.cz by uid 500 with qmail-scanner-1.15 ( Clear:. Processed in 0.051476 secs); 17 lis 2002 17:05:14 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Nov 2002 17:05:13 -0000 Date: Sun, 17 Nov 2002 18:05:13 +0100 (CET) From: Tomas Pluskal To: Dan Lukes Cc: Subject: Re: cannot compile stable In-Reply-To: <20021117174552.P587-100000@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Well, so we must locate the point of problem. After my last cvsup of > stable, the files in question have following versions: ... > If you have other version, it is problem with cvsup. Versions are OK. > The result of running awk '/^[_A-Z]/ { print; }' $FILENAME: > ----------- confstr.gperf ---------------- ... > > If got other results, you may have problem with awk. This seems to be the problem, because in my awk result, there are lines that start with lovercase letters (eg. "int"), but not in yours. As I've read in the awk manpage, it should in default be case sensitive, so my awk is behaving abnormally. This seems to be because of my locale settings - it is set to cs_CZ.ISO8859-2 and when I unset it, awk becomes case sensitive. Now I know why compilation crashed, but I don't understand why awk is case insensitive with Czech locales set. My awk is: GNU Awk 3.0.6 (from 4.6 release) > After you locate the right point of problem, we may continue. Thank you very much for your "investigation", it was really helpful. Tomas Pluskal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 9:15:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 234B337B404; Sun, 17 Nov 2002 09:15:10 -0800 (PST) Received: from ene.asda.gr (ene.asda.gr [193.92.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5111343E42; Sun, 17 Nov 2002 09:15:09 -0800 (PST) (envelope-from lefty@ene.asda.gr) Received: from ene.asda.gr (lefty.ene.asda.gr [193.92.118.162]) by ene.asda.gr (Postfix) with ESMTP id C59804119; Sun, 17 Nov 2002 19:15:06 +0200 (EET) Message-ID: <3DD7CEB0.F2A9C2F8@ene.asda.gr> Date: Sun, 17 Nov 2002 19:15:28 +0200 From: Lefteris Tsintjelis Organization: ASDA X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en,el MIME-Version: 1.0 To: Eugene Grosbein Cc: Kenneth Mays , scrappy@hub.org, freebsd-stable@FreeBSD.ORG, freebsd-chat@FreeBSD.ORG Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) References: <20021117224945.A806@grosbein.pp.ru> Content-Type: text/plain; charset=iso-8859-7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene Grosbein wrote: > > On Sun, Nov 17, 2002 at 10:14:51AM -0500, Kenneth Mays wrote: > > > Your question brings up an issue that was talked about several times, and it > > was addressed in the docs and the newsgroup. -STABLE is an engineering > > development branch that is 'more stable' than -CURRENT, but not more stable > > than -RELEASE. -STABLE is NOT for end users/customers for official > > production use (i.e. do so at your own risk). > > I wonder why no one says that -STABLE really WAS stable and WAS intended > for end users less than 2 years ago. Moreover, Hanbook said you > need -STABLE if you are using FreeBSD in production environment > and you need stability, Handbook said it even 15 months ago. > And it has been assetring so for long time, that's where the name > of this branch came from. Anyone can see that in CVS. > > Eugene Grosbein NOW THAT was making a lot of sense two years ago. Well, MY answer is that I am very new to FreeBSD so I wouldn't really know the branch name history but I couldn't agree any more with the old terminology you are referring too. PS: I think that this should be a chat thread though. LEfteris Tsintjelis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 10:11:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EED937B401 for ; Sun, 17 Nov 2002 10:11:53 -0800 (PST) Received: from mail.bobj.org (cpe-gan-68-101-90-216-cmcpe.ncf.coxexpress.com [68.101.90.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77BD043E3B for ; Sun, 17 Nov 2002 10:11:52 -0800 (PST) (envelope-from stest033@garbonzo.hos.ufl.edu) Received: from bobj.dyndns.org (dhcp6.wb4jcm.org [192.168.132.167]) by neti.bobj.org with esmtp; Sun, 17 Nov 2002 13:06:32 -0500 From: Bob Johnson To: Lefteris Tsintjelis Subject: Re: FreeBSD: Server or Desktop OS? Date: Sun, 17 Nov 2002 13:06:31 -0500 X-Mailer: KMail [version 1.4] Cc: freebsd-stable@FreeBSD.ORG References: <20021117115616.T301-100000@extortion.peterh.dropbear.id.au> <3DD6EEA0.AD524CA2@ene.asda.gr> In-Reply-To: <3DD6EEA0.AD524CA2@ene.asda.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-7 Content-Transfer-Encoding: 7bit Message-Id: <200211171306.31020.stest033@garbonzo.hos.ufl.edu> X-Mime-Autoconverted: from 8bit to 7bit by courier 0.39 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Saturday 16 November 2002 08:19 pm, Lefteris Tsintjelis wrote: > It sure is misleading. Why is it called -stable then? You would expect > to stand up to its name. It is called -stable because once upon a time it was intended to BE stable. Commits to -stable were only supposed to happen after they had been well tested in -current. The FreeBSD documentation specifically recommended running -stable in a production environment. In those days (not terribly long ago), and -current was the beta test environment for stuff that had been alpha tested by those who applied patches on their own. Once code proved stable in -current, it was moved to -stable. Real effort was put in to keeping -stable suitable for production environments. It may be that -stable is no longer stable because it was allowed (for valid reasons) to diverge considerably from -current. -current and -stable are almost two separate projects. Or perhaps the idea has taken hold that -current is the alpha branch, and -stable is the beta branch because of assumptions carried into FreeBSD from other projects that various committers have worked on. Or perhaps the rapid pace of development has made the old model obsolete. Or maybe the old model was never really a good one, but it was at least a goal that strived for. As things stand now, it appears that -current is the alpha branch, -stable is the not-so-stable beta branch, and RELENG_4_7 is the stable branch. But it also helps to remember the original (although widely forgotten) definition of "beta" testing: it is the final testing phase of a design that is believed to be ready for production, and thus should be intended to be as stable as a production system, and not as an experimental testbed for new features. Perhaps by that definition, -stable always WAS "beta", and it is the definition of "beta" that has changed. - Bob > > Regards, > Lefteris Tsintjelis > > Peter Hoskin wrote: > > STABLE is still a development branch. The name is misleading. If I were > > you, I'd install & run release. > > > > On Sat, 16 Nov 2002, Marc G. Fournier wrote: > > > On Sat, 16 Nov 2002, Hununu wrote: > > > > On 16 Nov 2002 at 13:47, Geoffrey C. Speicher wrote: > > > > > > Am I expecting too much from FreeBSD-STABLE? Would I fair better > > > > > > if I moved down into RELENG_4_7 and avoided -STABLE altogether? > > > > > > > > > > I think you're expecting too much from -stable. -stable is kind of > > > > > a misnomer; read the Handbook section 21.2.2.1 ("What Is > > > > > FreeBSD-STABLE?") for more. Your conclusion above is addressed > > > > > there (spoiler: don't use -stable in production unless your test > > > > > environment convinces you that it will work). > > > > > > > > Exactly. I have some boxes that run -stable. Though, I cvsup and > > > > install world & kernel on one box I can afford to fail. If it works > > > > ok, then I slowly move it to others.. -STABLE is not meant to be rock > > > > solid, and running it on production servers can be time-consuming for > > > > various reasons. > > > > > > The thing is, I run -STABLE on about a dozen desktops and servers at my > > > day job, and have never had a problem ... but they don't carry near as > > > much load as venus/jupiter do ... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 10:26: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D87837B401; Sun, 17 Nov 2002 10:25:59 -0800 (PST) Received: from mail.nsu.ru (mx.nsu.ru [193.124.215.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 379AF43E77; Sun, 17 Nov 2002 10:25:58 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from drweb by mail.nsu.ru with drweb-scanned (Exim 3.20 #1) id 18DU77-0003G1-00; Mon, 18 Nov 2002 00:25:45 +0600 Received: from iclub.nsu.ru ([193.124.215.97] ident=root) by mail.nsu.ru with esmtp (Exim 3.20 #1) id 18DU77-0003FZ-00; Mon, 18 Nov 2002 00:25:45 +0600 Received: from iclub.nsu.ru (fjoe@localhost [127.0.0.1]) by iclub.nsu.ru (8.12.6/8.12.6) with ESMTP id gAHIPWiP080489; Mon, 18 Nov 2002 00:25:34 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Received: (from fjoe@localhost) by iclub.nsu.ru (8.12.6/8.12.6/Submit) id gAHIPOlp080484; Mon, 18 Nov 2002 00:25:24 +0600 (NS) Date: Mon, 18 Nov 2002 00:25:23 +0600 From: Max Khon To: Mike Tancsa Cc: Lauri Laupmaa , ports@freebsd.org, stable@freebsd.org Subject: Re: uvscan & __stderrp Message-ID: <20021118002523.B80255@iclub.nsu.ru> References: <3DD4F95D.4948.5AB48BC@localhost> <5.1.0.14.0.20021115201514.0637b5a8@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.0.20021115201514.0637b5a8@192.168.0.12>; from mike@sentex.net on Fri, Nov 15, 2002 at 08:18:36PM -0500 X-Spam-Status: No, hits=-3.3 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02, USER_AGENT,USER_AGENT_MUTT version=2.43 X-Envelope-To: mike@sentex.net, mauri@andineeme.ee, ports@freebsd.org, stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, there! On Fri, Nov 15, 2002 at 08:18:36PM -0500, Mike Tancsa wrote: > .... You just beat me to the send button. Same deal here on my home > firewall. Could this be anything to do with the commits to > lib/compat/compat3x.i386 ? the commits to compat3x.i386 are the fix for the problem you have. you need not to re-build wordld (after cvsup) again. just do cd /usr/src/lib/compat/compat3x.i386 && make obj && make && make install /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 10:28:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADC5C37B401 for ; Sun, 17 Nov 2002 10:28:13 -0800 (PST) Received: from MX2.estpak.ee (mta1.mail.neti.ee [194.126.101.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA34643E77 for ; Sun, 17 Nov 2002 10:28:11 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from tiiu.internal (80-235-33-106-dsl.mus.estpak.ee [80.235.33.106]) by MX2.estpak.ee (Postfix) with ESMTP id 22E5F73562; Sun, 17 Nov 2002 20:27:07 +0200 (EET) Received: from tiiu.internal (localhost [127.0.0.1]) by tiiu.internal (8.12.6/8.12.6) with ESMTP id gAHIS38G001715; Sun, 17 Nov 2002 20:28:03 +0200 (EET) (envelope-from vallo@tiiu.internal) Received: (from vallo@localhost) by tiiu.internal (8.12.6/8.12.6/Submit) id gAHIS2BF001714; Sun, 17 Nov 2002 20:28:02 +0200 (EET) (envelope-from vallo) Date: Sun, 17 Nov 2002 20:28:01 +0200 From: Vallo Kallaste To: Eugene Grosbein Cc: Kenneth Mays , scrappy@hub.org, freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) Message-ID: <20021117182801.GB1131@tiiu.internal> Reply-To: kalts@estpak.ee References: <20021117224945.A806@grosbein.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021117224945.A806@grosbein.pp.ru> User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 17, 2002 at 10:49:45PM +0700, Eugene Grosbein wrote: > > Your question brings up an issue that was talked about several > > times, and it was addressed in the docs and the newsgroup. > > -STABLE is an engineering development branch that is 'more > > stable' than -CURRENT, but not more stable than -RELEASE. > > -STABLE is NOT for end users/customers for official production > > use (i.e. do so at your own risk). > I wonder why no one says that -STABLE really WAS stable and WAS intended > for end users less than 2 years ago. Moreover, Hanbook said you > need -STABLE if you are using FreeBSD in production environment > and you need stability, Handbook said it even 15 months ago. > And it has been assetring so for long time, that's where the name > of this branch came from. Anyone can see that in CVS. Exactly my point. The stability of FreeBSD is slowly but definitely deteriorating. The more the OS is gaining complexity, more bugs will be introduced or old bugs surface. As I understand it's very hard to support ever changing hardware, growing needs of userbase and hold the OS quality (in this context stability) on the track. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 10:33:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6389A37B401; Sun, 17 Nov 2002 10:33:42 -0800 (PST) Received: from meitner.wh.uni-dortmund.de (meitner.wh.Uni-Dortmund.DE [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id C70F143E75; Sun, 17 Nov 2002 10:33:40 -0800 (PST) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org ([10.3.12.105]) by meitner.wh.uni-dortmund.de (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id gAHHsic18115; Sun, 17 Nov 2002 18:54:45 +0100 X-Authentication-Warning: meitner.wh.uni-dortmund.de: Host [10.3.12.105] claimed to be lofi.dyndns.org Received: from gmx.net (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.6/8.12.6) with ESMTP id gAHIXVds035848 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 17 Nov 2002 19:33:32 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <3DD7E0FA.2080808@gmx.net> Date: Sun, 17 Nov 2002 19:33:30 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ulrich 'Q' Spoerlein" Cc: freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Power off problem References: <003d01c28e4a$fe295180$0200a8c0@amd1800> X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ulrich 'Q' Spoerlein wrote: > halt -p or > shutdown -p now ... does indeed not work on a lot of modern systems. All my athlon boxes here will only poweroff with 5-CURRENT, thanks to acpi-support there. -- Michael Nottebrock "And the reasons? There are no reasons." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 10:42:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C972D37B401 for ; Sun, 17 Nov 2002 10:42:08 -0800 (PST) Received: from vortex.wa4phy.net (user-24-214-14-65.knology.net [24.214.14.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC7CB43E77 for ; Sun, 17 Nov 2002 10:42:07 -0800 (PST) (envelope-from sam@wa4phy.net) Received: from vortex.wa4phy.net (localhost.wa4phy.net [127.0.0.1]) by vortex.wa4phy.net (8.12.6/8.12.6) with ESMTP id gAHIfna4042988; Sun, 17 Nov 2002 13:41:49 -0500 (EST) (envelope-from sam@wa4phy.net) Message-ID: <3DD7E2EC.5050805@vortex.wa4phy.net> Date: Sun, 17 Nov 2002 13:41:48 -0500 From: Sam Drinkard Organization: You Gotta Be Kiddin! User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:1.2b) Gecko/20021016 X-Accept-Language: en, ja MIME-Version: 1.0 To: kalts@estpak.ee Cc: Eugene Grosbein , Kenneth Mays , scrappy@hub.org, freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) References: <20021117224945.A806@grosbein.pp.ru> <20021117182801.GB1131@tiiu.internal> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been using -stable for about 2 years now, and I can tell you this much. -Stable, at least for me, IS stable. Of course, I'm not running any heavy load on the machine, but in all of my rebuilds, I've never (knock on wood) had any problems that weren't caused by my own lack of knowledge. When I first moved to the -stable branch (4.2 I believe) from a 3.2-R system, I had a few problems crop up, but as the updates came out, the problems went away. I don't have to have the "latest and greatest" every few days or months.. sometimes I'll go a year before I'll decide to upgrade, then it's primarily due to security considerations, and not any specific fix. The one thing I can say to everyone involved in the building of FreeBSD is thank you for such good documentation. I unfortunately have to have a linux machine running due to specific software that will not run on *bsd, and from my very limited exposure to linux, I can say the documentation stinks. At some point, I will most likely go back to a -Release, but the thoughts of reworking and re-installing from scratch 10 years worth of software, files, and configurations really scares me, even with good, valid backups. When you progressivley move from a version of 1 to a version of 4.7 over 10 years, you learn a bit about what works and what doesn't. Sam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 11:21: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0624E37B401 for ; Sun, 17 Nov 2002 11:21:08 -0800 (PST) Received: from MX3.estpak.ee (mta1.mail.neti.ee [194.126.101.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC86E43E6E for ; Sun, 17 Nov 2002 11:21:06 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from tiiu.internal (80-235-33-106-dsl.mus.estpak.ee [80.235.33.106]) by MX3.estpak.ee (Postfix) with ESMTP id DDD3D8800E; Sun, 17 Nov 2002 21:21:04 +0200 (EET) Received: from tiiu.internal (localhost [127.0.0.1]) by tiiu.internal (8.12.6/8.12.6) with ESMTP id gAHJL48G002028; Sun, 17 Nov 2002 21:21:04 +0200 (EET) (envelope-from vallo@tiiu.internal) Received: (from vallo@localhost) by tiiu.internal (8.12.6/8.12.6/Submit) id gAHJL3Q3002027; Sun, 17 Nov 2002 21:21:03 +0200 (EET) (envelope-from vallo) Date: Sun, 17 Nov 2002 21:21:03 +0200 From: Vallo Kallaste To: Sam Drinkard Cc: Eugene Grosbein , Kenneth Mays , scrappy@hub.org, freebsd-stable@FreeBSD.ORG Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) Message-ID: <20021117192103.GB1909@tiiu.internal> Reply-To: kalts@estpak.ee References: <20021117224945.A806@grosbein.pp.ru> <20021117182801.GB1131@tiiu.internal> <3DD7E2EC.5050805@vortex.wa4phy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DD7E2EC.5050805@vortex.wa4phy.net> User-Agent: Mutt/1.5.1i-ja.1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 17, 2002 at 01:41:48PM -0500, Sam Drinkard wrote: > I've been using -stable for about 2 years now, and I can tell you this > much. -Stable, at least for me, IS stable. Of course, I'm not running > any heavy load on the machine, but in all of my rebuilds, I've never > (knock on wood) had any problems that weren't caused by my own lack of > knowledge. When I first moved to the -stable branch (4.2 I believe) > from a 3.2-R system, I had a few problems crop up, but as the updates > came out, the problems went away. I don't have to have the "latest and > greatest" every few days or months.. sometimes I'll go a year before > I'll decide to upgrade, then it's primarily due to security > considerations, and not any specific fix. The one thing I can say to > everyone involved in the building of FreeBSD is thank you for such good > documentation. I unfortunately have to have a linux machine running due > to specific software that will not run on *bsd, and from my very limited > exposure to linux, I can say the documentation stinks. At some point, I > will most likely go back to a -Release, but the thoughts of reworking > and re-installing from scratch 10 years worth of software, files, and > configurations really scares me, even with good, valid backups. When > you progressivley move from a version of 1 to a version of 4.7 over 10 > years, you learn a bit about what works and what doesn't. Well, I don't have any hard facts to guard my words unfortunately, because all the memories are under the dust of time. This all can go down to the simple fact that when I first jumped over to FreeBSD from Linux on 2.2.1 days I was a greenhorn and my needs were very simple. But I remember the fact that I were switching because of Linux unstability. Still, my overall feeling is that stability has gotten worse over time. IMO. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 11:39:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BC4B37B401; Sun, 17 Nov 2002 11:39:10 -0800 (PST) Received: from english-breakfast.cloud9.net (english-breakfast.cloud9.net [168.100.1.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id B616943E42; Sun, 17 Nov 2002 11:39:04 -0800 (PST) (envelope-from Hostmaster@Video2Video.Com) Received: from localhost (localhost [127.0.0.1]) by english-breakfast.cloud9.net (Postfix) with ESMTP id 1953C26F42; Sun, 17 Nov 2002 14:38:59 -0500 (EST) Received: from english-breakfast.cloud9.net (localhost [127.0.0.1]) by localhost (VaMailArmor-2.0.1.7) id 37517-7BBE7724; Sun, 17 Nov 2002 14:38:59 -0500 Received: from earl-grey.cloud9.net (earl-grey.cloud9.net [168.100.1.1]) by english-breakfast.cloud9.net (Postfix) with ESMTP id BD24926F1E; Sun, 17 Nov 2002 14:38:58 -0500 (EST) Date: Sun, 17 Nov 2002 14:38:58 -0500 (EST) From: Peter Leftwich X-X-Sender: pete@earl-grey.cloud9.net To: Michael Nottebrock Cc: Ulrich 'Q' Spoerlein , FreeBSD LIST , Subject: Re: Power off problem In-Reply-To: <3DD7E0FA.2080808@gmx.net> Message-ID: <20021117143635.I80685-100000@earl-grey.cloud9.net> Organization: Video2Video Services - http://Www.Video2Video.Com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.7; VAE: 6.16.0.0; VDF: 6.16.0.17; host: english-breakfast.cloud9.net) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Nov 2002, Michael Nottebrock wrote: > Ulrich 'Q' Spoerlein wrote: > > halt -p or shutdown -p now > ... does indeed not work on a lot of modern systems. All my athlon boxes > here will only poweroff with 5-CURRENT, thanks to acpi-support there. > Michael Nottebrock > "And the reasons? There are no reasons." There was another post about having to recompile the kernel as well as add apmd_enable="YES" to /etc/rc.conf by the way. I am also on Athlon (FreeBSD 4.6.2), on a home-built box with a MicroStar MS-6167 motherboard. Isn't there some important jumper on the board to enable powering off via software rather than having to press the button?? -- Peter Leftwich President & Founder, Video2Video Services Box 13692, La Jolla, CA, 92039 USA http://Www.Video2Video.Com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12: 1:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D67C37B401 for ; Sun, 17 Nov 2002 12:01:22 -0800 (PST) Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8454843E75 for ; Sun, 17 Nov 2002 12:01:21 -0800 (PST) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id LAA51199; Sun, 17 Nov 2002 11:55:50 -0800 (PST) Received: from arch20m.dellroad.org (localhost [127.0.0.1]) by arch20m.dellroad.org (8.12.6/8.12.6) with ESMTP id gAHJtpOS046502; Sun, 17 Nov 2002 11:55:51 -0800 (PST) (envelope-from archie@arch20m.dellroad.org) Received: (from archie@localhost) by arch20m.dellroad.org (8.12.6/8.12.6/Submit) id gAHJtptv046501; Sun, 17 Nov 2002 11:55:51 -0800 (PST) From: Archie Cobbs Message-Id: <200211171955.gAHJtptv046501@arch20m.dellroad.org> Subject: Re: IPsec/gif VPN tunnel packets on wrong NIC in ipfw? In-Reply-To: <2F6DCE1EFAB3BC418B5C324F13934C9601D23C0F@exchange.corp.cre8.com> To: Scott Ullrich Date: Sun, 17 Nov 2002 11:55:50 -0800 (PST) Cc: "'greg.panula@dolaninformation.com'" , David Kelly , FreeBSD-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Scott Ullrich wrote: > I am also having this same problem. If I revert back to 4.7 RELEASE the > problem goes away. > > Anyone have an idea of what changed the default behavior between 4.7 RELEASE > and STABLE or if there is a better workaround other than adding a rule > before the divert statement allowing the internal networks to talk? Try reverting rev. 1.130.2.40 of netinet/ip_input.c (there may be other files in this commit; didn't look (you could do it by time)). This is just a guess because it seems like it might be relevant. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/netinet/ip_input.c?only_with_tag=RELENG_4 -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12: 1:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F03E37B401; Sun, 17 Nov 2002 12:01:41 -0800 (PST) Received: from sv07e.atm-tzs.kmjeuro.com (sv07e.atm-tzs.kmjeuro.com [193.81.94.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8970D43E4A; Sun, 17 Nov 2002 12:01:39 -0800 (PST) (envelope-from k.joch@kmjeuro.com) Received: from WSJK03 (adsl.ooe.kmjeuro.com [193.81.94.78]) (authenticated bits=0) by sv07e.atm-tzs.kmjeuro.com (8.12.6/8.12.6) with ESMTP id gAHK1HrP049323; Sun, 17 Nov 2002 21:01:18 +0100 (CET) (envelope-from k.joch@kmjeuro.com) Message-ID: <022801c28e74$1cadd4e0$0f05a8c0@WSJK03> From: "Karl M. Joch" To: , Subject: Real time server mirroring? Date: Sun, 17 Nov 2002 21:01:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MailScanner: Mail Server protected by CTS Austria www.ctseuro.com Message found to be clean Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, i am working on a very big project thruout our whole country and have the possibility to install freebsd on all servers in this project. i already have solutions for all needed components including the needed ipsec and ssl stuff. there is only one point i havnt found a real solution. i need to real time mirror some servers (4*2) for fault tolerance. the requirements is that these ones never can break down because it is used as a medical net. best would be mirror over locations. the servers are running: postgres, mysql sendmail and cyrus imap samba any idea how to have mirrored servers in real time with freebsd? thanks a lot. -- Best regards / Mit freundlichen Gruessen, Karl M. Joch http://www.freebsd.at - Das Power Betriebssystem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:10:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7BAB37B401 for ; Sun, 17 Nov 2002 12:10:55 -0800 (PST) Received: from genius.tao.org.uk (genius.tao.org.uk [212.135.162.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4477F43E4A for ; Sun, 17 Nov 2002 12:10:55 -0800 (PST) (envelope-from joe@genius.tao.org.uk) Received: by genius.tao.org.uk (Postfix, from userid 100) id EC5A94436; Sun, 17 Nov 2002 20:10:11 +0000 (GMT) Date: Sun, 17 Nov 2002 20:10:11 +0000 From: Josef Karthauser To: freebsd-stable@freebsd.org Subject: Call to test ulpt patch pre-commit. Message-ID: <20021117201011.GC35633@genius.tao.org.uk> Mail-Followup-To: Josef Karthauser , freebsd-stable@freebsd.org References: <20021012210204.GA484@raggedclown.net> <20021012211715.GA667@raggedclown.net> <20021113195205.GA10896@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7gGkHNMELEOhSGF6" Content-Disposition: inline In-Reply-To: <20021113195205.GA10896@genius.tao.org.uk> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --7gGkHNMELEOhSGF6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I mailed here a few days ago but didn't get much response. I've prepared a patch to the USB printer driver (ulpt) which adds additional support that's in -current but not yet in -stable. I don't have a usb printer myself and so am loathed to commit it until I've had some feedback from usb users in -stable saying that I didn't break anything. I'd be interested to hear whether this patch makes broken printers work without breaking working ones. http://www.josef-k.net/freebsd/releng4_usb_ulpt.patch Thanks, Joe --=20 Josef Karthauser (joe@tao.org.uk) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an= d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --7gGkHNMELEOhSGF6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iEYEARECAAYFAj3X96MACgkQXVIcjOaxUBbNkgCfa4f/q0AQ+MywKi42fr9a9wYz Y8IAniX27At69Xu80vkfjnW3mljA21wt =iq2e -----END PGP SIGNATURE----- --7gGkHNMELEOhSGF6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:31:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C829B37B401; Sun, 17 Nov 2002 12:31:51 -0800 (PST) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C97943E4A; Sun, 17 Nov 2002 12:31:51 -0800 (PST) (envelope-from stefan@fafoe.dyndns.org) Received: by frog.fafoe (Postfix, from userid 1001) id B00312A7; Sun, 17 Nov 2002 21:31:44 +0100 (CET) Date: Sun, 17 Nov 2002 21:31:44 +0100 From: Stefan Farfeleder To: Michael Nottebrock Cc: Ulrich 'Q' Spoerlein , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Power off problem Message-ID: <20021117203144.GC265@frog.fafoe> References: <003d01c28e4a$fe295180$0200a8c0@amd1800> <3DD7E0FA.2080808@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DD7E0FA.2080808@gmx.net> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 17, 2002 at 07:33:30PM +0100, Michael Nottebrock wrote: > Ulrich 'Q' Spoerlein wrote: > > >halt -p or > >shutdown -p now > > ... does indeed not work on a lot of modern systems. All my athlon boxes > here will only poweroff with 5-CURRENT, thanks to acpi-support there. jhb has a patch that gives some basic acpi functionality to RELENG_4 (http://people.freebsd.org/~jhb/patches/acpi_4x.patch). With it I'm able to do halt -p on stable. Regards, Stefan Farfeleder To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:33:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66F4237B401 for ; Sun, 17 Nov 2002 12:33:54 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27F5B43E4A for ; Sun, 17 Nov 2002 12:33:54 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id E74F38A1AF4; Sun, 17 Nov 2002 16:33:51 -0400 (AST) Date: Sun, 17 Nov 2002 16:33:51 -0400 (AST) From: "Marc G. Fournier" To: Mike Hoskins Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD: Server or Desktop OS? In-Reply-To: <20021117044229.Q29719-100000@fubar.adept.org> Message-ID: <20021117161953.M23359-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Nov 2002, Mike Hoskins wrote: > I'm not sure if the earlier post claiming -stable use since '94 or so is > accurate, but if it is, as another pointed out, you should have seen > similar periods in -STABLE before now and been better prepared to avoid > these types of situations. '92 was Linux ... '92 moved to BSDi since Linux was lucky to run for more then an hour once connected to the Internet ... '94 (or '95) moved to FreeBSD since BSDi changed their pricing structuremaking it near impossible to afford for 'the little man' ... As for 'similar periods' ... you know, I've been running -STABLE on desktops and low end servers over the past 5 years at the Univesrity, slowly replacing Solaris as the applications they run permit ... so far, in 5 years, I've *yet* to be burnt, but none of these are running near as heavy load ... so no, other then on venus/jupiter, I haven' tnot seen similar periods of instability ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:38:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80D6D37B401; Sun, 17 Nov 2002 12:38:32 -0800 (PST) Received: from mail3.sea.registeredsite.com (mail3.sea.registeredsite.com [66.111.73.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB9C343E6E; Sun, 17 Nov 2002 12:38:26 -0800 (PST) (envelope-from WD@US-Webmasters.com) Received: from us-webmasters.com (us-webmasters.com [207.159.139.240]) by mail3.sea.registeredsite.com (8.12.5/8.12.5) with ESMTP id gAHKcIaQ011835; Sun, 17 Nov 2002 15:38:19 -0500 Received: from xyz.netins.net (desm-05-095.dialup.netins.net [167.142.12.96]) by us-webmasters.com (8.9.3/8.9.3) with ESMTP id MAA04111; Sun, 17 Nov 2002 12:38:16 -0800 (PST) Message-Id: <5.1.0.14.2.20021117143716.061d59b0@us-webmasters.com> X-Sender: wd@us-webmasters.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 17 Nov 2002 14:38:06 -0600 To: From: "W. D." Subject: Re: Real time server mirroring? Cc: , "Karl M. Joch" In-Reply-To: <022801c28e74$1cadd4e0$0f05a8c0@WSJK03> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 14:01 11/17/2002, Karl M. Joch wrote: >postgres, mysql >sendmail and cyrus imap >samba > >any idea how to have mirrored servers in real time with freebsd? Here are some ideas: http://www.Google.com/search?q=3Drsync+mirror+freebsd Start Here to Find It Fast!=A9 -> http://www.US-Webmasters.com/best-start-pa= ge/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:45:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 134CD37B404 for ; Sun, 17 Nov 2002 12:45:24 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id B988C43E8A for ; Sun, 17 Nov 2002 12:45:23 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id 580228A19C8; Sun, 17 Nov 2002 16:45:21 -0400 (AST) Date: Sun, 17 Nov 2002 16:45:21 -0400 (AST) From: "Marc G. Fournier" To: Vallo Kallaste Cc: Eugene Grosbein , Kenneth Mays , Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) In-Reply-To: <20021117182801.GB1131@tiiu.internal> Message-ID: <20021117163832.T23359-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Nov 2002, Vallo Kallaste wrote: > On Sun, Nov 17, 2002 at 10:49:45PM +0700, Eugene Grosbein > wrote: > > > > Your question brings up an issue that was talked about several > > > times, and it was addressed in the docs and the newsgroup. > > > -STABLE is an engineering development branch that is 'more > > > stable' than -CURRENT, but not more stable than -RELEASE. > > > -STABLE is NOT for end users/customers for official production > > > use (i.e. do so at your own risk). > > > I wonder why no one says that -STABLE really WAS stable and WAS intended > > for end users less than 2 years ago. Moreover, Hanbook said you > > need -STABLE if you are using FreeBSD in production environment > > and you need stability, Handbook said it even 15 months ago. > > And it has been assetring so for long time, that's where the name > > of this branch came from. Anyone can see that in CVS. > > Exactly my point. The stability of FreeBSD is slowly but definitely > deteriorating. The more the OS is gaining complexity, more bugs will > be introduced or old bugs surface. As I understand it's very hard to > support ever changing hardware, growing needs of userbase and hold > the OS quality (in this context stability) on the track. I think the main thing that is bothering me is the priority that is being attributed to bug reports on the -STABLE branch ... when one of my servers crashes, it takes ~1hr or so for it to dump core, since it has to use netdump to dump it to another server (I don't have 4+ gig of continuous swap space) and then there is the extra time required to fsck 100gig of disk space ... If someone could jump onto, and fix, why it crashed in an "exceptional" environment, think of how much less chance there would be of someone else's computer crashing ... Using -STABLE, I upgrade my desktops and servers once every ~30days ... I'd be happy to get 30 days uptime on my loaded servers before having to upgrade, but if it crashes, my first steps have always been to report a crash dump (if I can) and then upgrade to the next -STABLE, since it might be somethign that is already fixed ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:51:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D139F37B401 for ; Sun, 17 Nov 2002 12:51:50 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55D0643E6E for ; Sun, 17 Nov 2002 12:51:50 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id 0645C8A1A97; Sun, 17 Nov 2002 16:51:48 -0400 (AST) Date: Sun, 17 Nov 2002 16:51:47 -0400 (AST) From: "Marc G. Fournier" To: Bill Moran Cc: kalts@estpak.ee, Eugene Grosbein , Kenneth Mays , Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) In-Reply-To: <3DD7E3D9.1040902@potentialtech.com> Message-ID: <20021117164707.T23359-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 17 Nov 2002, Bill Moran wrote: > Vallo Kallaste wrote: > > On Sun, Nov 17, 2002 at 10:49:45PM +0700, Eugene Grosbein > > wrote: > > > > > >>>Your question brings up an issue that was talked about several > >>>times, and it was addressed in the docs and the newsgroup. > >>>-STABLE is an engineering development branch that is 'more > >>>stable' than -CURRENT, but not more stable than -RELEASE. > >>>-STABLE is NOT for end users/customers for official production > >>>use (i.e. do so at your own risk). > >> > >>I wonder why no one says that -STABLE really WAS stable and WAS intended > >>for end users less than 2 years ago. Moreover, Hanbook said you > >>need -STABLE if you are using FreeBSD in production environment > >>and you need stability, Handbook said it even 15 months ago. > >>And it has been assetring so for long time, that's where the name > >>of this branch came from. Anyone can see that in CVS. > > > > Exactly my point. The stability of FreeBSD is slowly but definitely > > deteriorating. The more the OS is gaining complexity, more bugs will > > be introduced or old bugs surface. As I understand it's very hard to > > support ever changing hardware, growing needs of userbase and hold > > the OS quality (in this context stability) on the track. > > I disagree. > I think the impression of what could be done with -STABLE (in the > developers eyes) has changed because of the RELENG_4_7 branches. > Since anyone interested in production stability should track that > branch instead. What's to track? Nothing happens on that branch ... I just CVSup'd RELEASE, followed by RELENG_4_7 and the only changes were pretty much related to the latest BIND vulnerabilities ... Here's all that has changed in 4_7: Updating collection src-all/cvs Edit src/Makefile.inc1 Edit src/UPDATING Edit src/contrib/bind/CHANGES Edit src/contrib/bind/bin/named/db_defs.h Edit src/contrib/bind/bin/named/db_sec.c Edit src/contrib/bind/bin/named/ns_defs.h Edit src/contrib/bind/bin/named/ns_ncache.c Edit src/contrib/bind/bin/named/ns_req.c Edit src/contrib/bind/bin/named/ns_resp.c Edit src/contrib/bind/lib/nameser/ns_name.c Edit src/contrib/bind/lib/nameser/ns_samedomain.c Edit src/contrib/tar/src/extract.c Edit src/contrib/tar/src/misc.c Edit src/crypto/heimdal/kadmin/version4.c Edit src/crypto/kerberosIV/kadmin/kadm_ser_wrap.c Edit src/kerberos5/include/version.h Edit src/kerberosIV/include/version.h Edit src/lib/libc/net/gethostbydns.c Edit src/lib/libc/net/getnetbydns.c Edit src/release/doc/de_DE.ISO8859-1/errata/article.sgml Edit src/release/doc/de_DE.ISO8859-1/hardware/alpha/article.sgml Edit src/release/doc/de_DE.ISO8859-1/hardware/alpha/proc-alpha.sgml Edit src/release/doc/de_DE.ISO8859-1/hardware/common/dev.sgml Edit src/release/doc/de_DE.ISO8859-1/hardware/i386/article.sgml Edit src/release/doc/de_DE.ISO8859-1/hardware/i386/proc-i386.sgml Edit src/release/doc/de_DE.ISO8859-1/installation/alpha/article.sgml Edit src/release/doc/de_DE.ISO8859-1/installation/i386/article.sgml Edit src/release/doc/de_DE.ISO8859-1/readme/article.sgml Edit src/release/doc/de_DE.ISO8859-1/relnotes/alpha/article.sgml Edit src/release/doc/de_DE.ISO8859-1/relnotes/common/new.sgml Edit src/release/doc/de_DE.ISO8859-1/relnotes/i386/article.sgml Edit src/release/doc/de_DE.ISO8859-1/share/sgml/catalog Edit src/release/doc/de_DE.ISO8859-1/share/sgml/release.dsl Delete src/release/doc/de_DE.ISO8859-1/share/sgml/release.ent Edit src/share/examples/cvsup/standard-supfile Edit src/sys/conf/newvers.sh Finished successfully 20021113: p2 FreeBSD-SA-02:43.bind Correct name server vulnerabilities. 20021023: p1 FreeBSD-SA-02:40.kadmind Correct bug in the tar(1) contains_dot_dot function allowing files to be extracted outside the intended directory tree. Correct kadmind buffer overflow. 20021010: FreeBSD 4.7-RELEASE. Purely security vulnerabilities ... no 'critical patches' ... I would consider most anything related to the VM subsystem to be 'critical', at the very least ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 12:53:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A9E537B404; Sun, 17 Nov 2002 12:53:51 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEAF243E75; Sun, 17 Nov 2002 12:53:49 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id gAHKrlYM017915; Sun, 17 Nov 2002 21:53:47 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id gAHKrldW017914; Sun, 17 Nov 2002 21:53:47 +0100 (CET) Date: Sun, 17 Nov 2002 21:53:47 +0100 From: Wilko Bulte To: Stefan Farfeleder Cc: Michael Nottebrock , "Ulrich 'Q' Spoerlein" , freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Power off problem Message-ID: <20021117215347.A17757@freebie.xs4all.nl> References: <003d01c28e4a$fe295180$0200a8c0@amd1800> <3DD7E0FA.2080808@gmx.net> <20021117203144.GC265@frog.fafoe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021117203144.GC265@frog.fafoe>; from e0026813@stud3.tuwien.ac.at on Sun, Nov 17, 2002 at 09:31:44PM +0100 X-OS: FreeBSD 4.7-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Nov 17, 2002 at 09:31:44PM +0100, Stefan Farfeleder wrote: > On Sun, Nov 17, 2002 at 07:33:30PM +0100, Michael Nottebrock wrote: > > Ulrich 'Q' Spoerlein wrote: > > > > >halt -p or > > >shutdown -p now > > > > ... does indeed not work on a lot of modern systems. All my athlon boxes > > here will only poweroff with 5-CURRENT, thanks to acpi-support there. > > jhb has a patch that gives some basic acpi functionality to RELENG_4 > (http://people.freebsd.org/~jhb/patches/acpi_4x.patch). With it I'm able > to do halt -p on stable. Be careful that on multiple systems ACPI events give rise to panics using this patch. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 13: 7:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3055C37B401 for ; Sun, 17 Nov 2002 13:07:52 -0800 (PST) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47EBE43E4A for ; Sun, 17 Nov 2002 13:07:51 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id PAA28656; Sun, 17 Nov 2002 15:07:10 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from mke-24-167-197-76.wi.rr.com(24.167.197.76) by peak.mountin.net via smap (V1.3) id sma028623; Sun Nov 17 15:06:39 2002 Message-Id: <4.3.2.7.2.20021117142506.00e60dc0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 17 Nov 2002 15:05:13 -0600 To: kalts@estpak.ee, Sam Drinkard From: "Jeffrey J. Mountin" Subject: Re: -STABLE was stable for long time (Re: FreeBSD: Server or Desktop OS?) Cc: stable@FreeBSD.ORG In-Reply-To: <20021117192103.GB1909@tiiu.internal> References: <3DD7E2EC.5050805@vortex.wa4phy.net> <20021117224945.A806@grosbein.pp.ru> <20021117182801.GB1131@tiiu.internal> <3DD7E2EC.5050805@vortex.wa4phy.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 09:21 PM 11/17/02 +0200, Vallo Kallaste wrote: >Well, I don't have any hard facts to guard my words unfortunately, >because all the memories are under the dust of time. This all can go >down to the simple fact that when I first jumped over to FreeBSD >from Linux on 2.2.1 days I was a greenhorn and my needs were very >simple. But I remember the fact that I were switching because of >Linux unstability. Still, my overall feeling is that stability has >gotten worse over time. IMO. I'd have to say just the opposite for the same period of time (2.1.5 really), then I manage to miss stepping on most of the bugs that creep in or wonder why others are having issues with various sub-systems. What I do know if there are more using -stable and many that *should not* or should being doing far more reading than they do, which makes it a matter of perception. Frankly build errors shouldn't factor in, as most are pilot error. Myself have only run into 2 build problems in 7 years. Then I do bother to read before building (and thus avoid the few *true* issues) and even might wait a day or 3 after pulling source to actually build and install. Need we even mention the number of users with questionable hardware. Does seem a bit more quite on the front than it used to be compared to say last year. Not to pick on anyone, but for as long as I can recall Marc (scrappy@hub.org) has run afoul of many problems and it's either due to taking risks or just shit luck and stepping on every odd and rare bug there is. Not that it's any fun being the exception. 8-/ Also don't recall the handbook ever saying -stable for production environments and think Eugene is spewing FUD or whoever put that in the handbook was smoking crack. Besides, the security branches came about for those with production systems or those less willing to gamble on new features. As for -stable and -current diverging. Well, that happens and can mean less developer time spent on -stable. I hardly think that an issue (it was concern at one point and there was a need for more working on -current for 5.0) considering the commits to keep gratuitous changes from creeping in and work that is done on the -stable brank or even the few MFS's seen from time to time. Not for me to say that this time around there are a more differences between them than ever before for a major branch, but doubt it isn't the case and those going to track RELENG_5 when it spins off... My guess is the -stable list will be rather busy and many running "the latest and greatest" won't bother to do their homework. Only thing in support of being a bit unstable is that it has appeared a bit more bumpy than usual after 4.7R. Then some things *could* affect systems under my control, so I tend to turn a bit more conservative. Perception again and yet anyone that has been around should know that before and after releases is when breakage is more likely. Not to mention it is after a release that new features and major changes are committed and "buyer beware" should be the rule. Otherwise business as usual, IMO. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 13: 8:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D93237B401; Sun, 17 Nov 2002 13:08:11 -0800 (PST) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 582C243E3B; Sun, 17 Nov 2002 13:08:10 -0800 (PST) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id <42S9WJ1C>; Sun, 17 Nov 2002 16:08:08 -0500 Message-ID: From: Don Bowman To: "'k.joch@kmjeuro.com'" , "'freebsd-questions@freebsd.org '" , "'freebsd-stable@freebsd.org '" Subject: RE: Real time server mirroring? Date: Sun, 17 Nov 2002 16:08:07 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >From: Karl M. Joch >there is only one point i havnt found a real solution. i need to >real time mirror some servers (4*2) for fault tolerance. >the requirements is that these ones never can break down >because it is used as a medical net. best >would be mirror over locations. the servers are running: http://www.bsdshell.net/ may provide some assistance (it is the high-uptime bsd project, HUT). This provides some of the components. For the individual services, see e.g. postgresql replication (there are several different mechanisms to achieve for postgres). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 17 13:18: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61CE937B401; Sun, 17 Nov 2002 13:18:00 -0800 (PST) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0298F43E4A; Sun, 17 Nov 2002 13:17:58 -0800 (PST) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.12.6/8.11.6) with ESMTP id gAHLHE0g043377; Sun, 17 Nov 2002 23:17:15 +0200 (EET) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost.vega.com [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id gAHLH96A006949; Sun, 17 Nov 2002 23:17:09 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id gAHLGsto006948; Sun, 17 Nov 2002 23:16:54 +0200 (EET) Date: Sun, 17 Nov 2002 23:16:54 +0200 From: Maxim Sobolev To: stable@FreeBSD.org Cc: marks@ripe.net, tlambert2@mindspring.com, bmilekic@unixdaemons.com, dl-freebsd@catspoiler.org, stranger@sberbank.sibnet.ru, vova@sw.ru, sos@freebsd.dk, udo.schweigert@siemens.com, ktsin@acm.org, hackers@FreeBSD.org Subject: Memory corruption in -STABLE on P4/2GHz Message-ID: <20021117211654.GE6115@vega.vega.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Hi there, I'm observing very strange memory corruption problems with 2GHz P4 system running 4.7 (security branch as of today). Under the load (make -j20 buildworld) the compiler or make(1) often die with signal 11. I found in mailing lists that there is similarly looking problem with -current, any chances that -stable is affected as well? Adding `options DISABLE_PSE', as suggested, reduced the likelyhood of the problem, but didn't eliminate it completely (-j20 fails with sig11 from time to time, but much less frequently than without the said option. Any ideas? -Maxim --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE-p2 #0: Sun Nov 17 05:12:06 PST 2002 root@install.portaone.com:/usr/src/sys/compile/INSTALL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium 4 (1990.24-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff,ACC> real memory = 503250944 (491456K bytes) config> en apm0 config> q avail memory = 484413440 (473060K bytes) Preloaded elf kernel "kernel" at 0xc050d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc050d09c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 5 entries at 0xc00fdec0 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 ohci0: mem 0xec100000-0xec100fff irq 11 at device 8.0 on pci0 usb0: OHCI version 1.0 usb0: on ohci0 usb0: USB revision 1.0 uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xec101000-0xec101fff irq 5 at device 8.1 on pci0 usb1: OHCI version 1.0 usb1: on ohci1 usb1: USB revision 1.0 uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at 8.2 irq 10 rl0: port 0xd000-0xd0ff mem 0xec103000-0xec1030ff irq 10 at device 10.0 on pci0 rl0: Ethernet address: 00:e0:4c:77:20:ce miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0xd400-0xd40f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: (vendor=0x1106, dev=0x3059) at 17.5 irq 10 orm0: Here Skan-Line Sports Airsoft News --boundary42-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12: 9:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70F6B37B404 for ; Sat, 23 Nov 2002 12:09:41 -0800 (PST) Received: from mailsvr1.mn1.fasturl.net (mailsvr1.mn1.fasturl.net [209.32.216.129]) by mx1.FreeBSD.org (Postfix) with SMTP id BEBB043E9C for ; Sat, 23 Nov 2002 12:09:40 -0800 (PST) (envelope-from skanline@websvr4.mn1.fasturl.net) Received: (qmail 38993 invoked from network); 23 Nov 2002 20:09:40 -0000 Received: from unknown (HELO websvr4.mn1.fasturl.net) (204.73.200.37) by mailsvr1.mn1.fasturl.net with SMTP; 23 Nov 2002 20:09:40 -0000 Received: (from skanline@localhost) by websvr4.mn1.fasturl.net (8.9.3/8.9.3) id UAA13082; Sat, 23 Nov 2002 20:09:40 GMT (envelope-from skanline@websvr4.mn1.fasturl.net) Date: Sat, 23 Nov 2002 20:09:40 GMT Message-Id: <200211232009.UAA13082@websvr4.mn1.fasturl.net> To: stable@FreeBSD.org From: Skan-Line Sports Airsoft News Reply-To: Skan-Line Sports Airsoft News Subject: You've Been Added! MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=boundary42 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --boundary42 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit This message is to confirm the addition of your email address: stable@FreeBSD.org to the Skan-Line Sports Airsoft News mailing list. If you feel you have received this notice in error, please visit the Skan-Line Sports Airsoft News mailing list at our website: http://www.skanline.com to remove yourself automatically, or click the link below: http://www.skanline.com/cgi-world/cgiwrap-skanline/skanline/cgi-bin/smpro/s.pl?r=1&l=3&e=stable=:FreeBSD.org Thank you, Skan-Line Sports Airsoft News --boundary42-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12: 9:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B528137B401 for ; Sat, 23 Nov 2002 12:09:53 -0800 (PST) Received: from ene.asda.gr (ene.asda.gr [193.92.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 339D843E91 for ; Sat, 23 Nov 2002 12:09:53 -0800 (PST) (envelope-from lefty@ene.asda.gr) Received: from ene.asda.gr (lefty.ene.asda.gr [193.92.118.162]) by ene.asda.gr (Postfix) with ESMTP id C2C604308; Sat, 23 Nov 2002 22:09:50 +0200 (EET) Message-ID: <3DDFE0AC.57BF260E@ene.asda.gr> Date: Sat, 23 Nov 2002 22:10:20 +0200 From: Lefteris Tsintjelis Organization: ASDA X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en,el MIME-Version: 1.0 To: Kent Stewart Cc: a , stable@FreeBSD.ORG Subject: Re: Port INDEX dependency list incompletes References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> Content-Type: text/plain; charset=iso-8859-7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent Stewart wrote: > > cd /usr/ports > make index > portsdb -u I get almost always "dependency list incompletes" with portsdb -Uu. Would it be a good idea to always use the above instead? Lefteris > Kent > > -- > Kent Stewart > Richland, WA > > http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12:28:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 937B037B401 for ; Sat, 23 Nov 2002 12:28:11 -0800 (PST) Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 038C043E4A for ; Sat, 23 Nov 2002 12:28:11 -0800 (PST) (envelope-from kstewart@owt.com) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id MAA28124; Sat, 23 Nov 2002 12:28:06 -0800 Message-ID: <3DDFE4D6.5090901@owt.com> Date: Sat, 23 Nov 2002 12:28:06 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, es-mx MIME-Version: 1.0 To: Lefteris Tsintjelis Cc: a , stable@FreeBSD.ORG Subject: Re: Port INDEX dependency list incompletes References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> <3DDFE0AC.57BF260E@ene.asda.gr> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Lefteris Tsintjelis wrote: > Kent Stewart wrote: > >>cd /usr/ports >>make index >>portsdb -u > > > I get almost always "dependency list incompletes" with portsdb -Uu. > Would it be a good idea to always use the above instead? No, because portsdb -U uses much less computer time to rebuild INDEX than make index does. On my AMD 2000+ XP, which is designed to do 20 minute buildworlds, a portsdb -U requires ~7 minutes and a make index requires ~11 minutes. If you are going to work on your ports, the extra time is time you just sit there. I find people go into their own version of an idle-loop after 2 minutes. We just have to wait for knu to fix it. KEnt -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12:29:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00F6637B401 for ; Sat, 23 Nov 2002 12:29:17 -0800 (PST) Received: from luftpost.plosh.net (luftpost.plosh.net [204.152.186.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id A44D443E91 for ; Sat, 23 Nov 2002 12:29:16 -0800 (PST) (envelope-from plosher+freebsd.org@plosh.net) Received: from zorin.isc.org (tardis-nat.plosh.net [64.139.14.228]) by luftpost.plosh.net (Postfix) with ESMTP id 473873261E for ; Sat, 23 Nov 2002 12:29:08 -0800 (PST) (envelope-from plosher+freebsd.org@plosh.net) Content-Type: text/plain; charset="iso-8859-1" From: Peter Losher To: FreeBSD Stable Subject: Re: Opera for FreeBSD Date: Sat, 23 Nov 2002 12:28:40 -0800 User-Agent: KMail/1.4.3 References: <1036191053.15279.0.camel@lerlaptop.iadfw.net> <20021104142546.GA77857@sr.se> <200211041403.51714.phaedrus@alltel.net> In-Reply-To: <200211041403.51714.phaedrus@alltel.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200211231228.40573.plosher+freebsd.org@plosh.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (Apologies for the late response, but I wanted to get this answer in the archives, and I am now catching up on my -stable mail...) On Monday 04 November 2002 12:03 pm, Dave Cantrell wrote: > Yeah, but if you *bought* the linux license to run under emulation, you > still have to *buy* the FreeBSD license, now that they finally got it > native. For me, I'm switching to konqui (KDE). A clarification, like you I have a Linux license (as well as a Windows; I really do like Opera) What I did is "upgrade" the license for US$15 to convert my Linux license to FreeBSD. Since I have had my Linux license for over a year, paying $15 for letting Opera know I use FreeBSD and will support Opera natively on FreeBSD is good value for money, IMO. Hopefully soon there will be a opera-sharedqt port, since I use KDE, I can take advantage of the AA support I have compiled into my QT install, and makes Opera look just as good as the rest of my KDE setup :) (I still use Konq for my IPv6 web browsing, so it still has a use) ;) Best Wishes - Peter -- plosher@plosh.net - [ http://www.plosh.net/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12:40: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F95A37B401 for ; Sat, 23 Nov 2002 12:40:08 -0800 (PST) Received: from quartz.bos.dyndns.org (quartz.bos.dyndns.org [66.37.215.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A97243E6E for ; Sat, 23 Nov 2002 12:40:07 -0800 (PST) (envelope-from twilde@dyndns.org) Received: from quartz.bos.dyndns.org (twilde@localhost [127.0.0.1]) by quartz.bos.dyndns.org (8.12.2/8.12.2) with ESMTP id gANKe6kL027747; Sat, 23 Nov 2002 15:40:06 -0500 (EST) Received: from localhost (twilde@localhost) by quartz.bos.dyndns.org (8.12.2/8.12.2/Submit) with ESMTP id gANKe6Qe027722; Sat, 23 Nov 2002 15:40:06 -0500 (EST) X-Authentication-Warning: quartz.bos.dyndns.org: twilde owned process doing -bs Date: Sat, 23 Nov 2002 15:40:06 -0500 (EST) From: Tim Wilde X-X-Sender: twilde@quartz.bos.dyndns.org To: Thomas Seck Cc: stable@FreeBSD.ORG Subject: Re: named.root In-Reply-To: <20021122162336.GA480@laurel.tmseck.homedns.org> Message-ID: References: <20021121204315.707455D04@ptavv.es.net> <3DDDD74D.F4BC206F@softweyr.com> <20021122162336.GA480@laurel.tmseck.homedns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 22 Nov 2002, Thomas Seck wrote: > No one is kept from modifying his or her local copy of FreeBSD to suit > his resp. her needs. I do not think that Network Solutions will assign > 198.41.0.10 tomorrow to $evil_person for $most_evil_purpose but YMMV. They have explicitly stated, in fact, that it will continue providing root DNS service for at least 5 years. Tim Wilde -- Tim Wilde twilde@dyndns.org Systems Administrator Dynamic DNS Network Services http://www.dyndns.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12:53:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0484937B401 for ; Sat, 23 Nov 2002 12:53:48 -0800 (PST) Received: from ene.asda.gr (ene.asda.gr [193.92.118.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73DDB43E91 for ; Sat, 23 Nov 2002 12:53:47 -0800 (PST) (envelope-from lefty@ene.asda.gr) Received: from ene.asda.gr (lefty.ene.asda.gr [193.92.118.162]) by ene.asda.gr (Postfix) with ESMTP id 440114308; Sat, 23 Nov 2002 22:53:44 +0200 (EET) Message-ID: <3DDFEAF6.3F3D4D40@ene.asda.gr> Date: Sat, 23 Nov 2002 22:54:14 +0200 From: Lefteris Tsintjelis Organization: ASDA X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en,el MIME-Version: 1.0 To: Kent Stewart Cc: a , stable@FreeBSD.ORG Subject: Re: Port INDEX dependency list incompletes References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> <3DDFE0AC.57BF260E@ene.asda.gr> <3DDFE4D6.5090901@owt.com> Content-Type: text/plain; charset=iso-8859-7 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent Stewart wrote: > > a portsdb -U requires ~7 minutes and a make index > requires ~11 minutes. If 4 min is the only real difference, ~7 min here, then I guess its a good time for a hot cup of coffee break). Cheers, Lefteris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 12:55:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2D5B37B401 for ; Sat, 23 Nov 2002 12:55:26 -0800 (PST) Received: from smtp.netcologne.de (smtp.netcologne.de [194.8.194.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3A0443E3B for ; Sat, 23 Nov 2002 12:55:25 -0800 (PST) (envelope-from tmseck-lists@netcologne.de) Received: from mail.tmseck.homedns.org (xdsl-213-168-118-202.netcologne.de [213.168.118.202]) by smtp.netcologne.de (Postfix) with ESMTP id 5B016867E3 for ; Sat, 23 Nov 2002 21:55:22 +0100 (MET) Received: by mail.tmseck.homedns.org (Postfix, from userid 1001) id 1DD5F285B0; Sat, 23 Nov 2002 21:55:17 +0100 (CET) Date: Sat, 23 Nov 2002 21:55:17 +0100 From: Thomas Seck To: stable@freebsd.org Subject: Re: Port INDEX dependency list incompletes Message-ID: <20021123205517.GA411@laurel.tmseck.homedns.org> Reply-To: stable@freebsd.org Mail-Followup-To: stable@freebsd.org References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> <3DDFE0AC.57BF260E@ene.asda.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DDFE0AC.57BF260E@ene.asda.gr> User-Agent: Mutt/1.4i Organization: private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 X-Attribution: tms Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Lefteris Tsintjelis (lefty@ene.asda.gr): > Kent Stewart wrote: > > > > cd /usr/ports > > make index > > portsdb -u > > I get almost always "dependency list incompletes" with portsdb -Uu. > Would it be a good idea to always use the above instead? Obviously one cannot get error messages from "make index" when one does not run it. Please read portsdb(1) for what these options do. On the other hand, the verbose output from "make index" is - as far as I can tell - nothing to worry about. --Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 13:27:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2CFB37B401 for ; Sat, 23 Nov 2002 13:27:24 -0800 (PST) Received: from hotmail.com (f59.law8.hotmail.com [216.33.241.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A8FA43E3B for ; Sat, 23 Nov 2002 13:27:24 -0800 (PST) (envelope-from luckywolf19@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 23 Nov 2002 13:27:24 -0800 Received: from 216.27.227.3 by lw8fd.law8.hotmail.msn.com with HTTP; Sat, 23 Nov 2002 21:27:24 GMT X-Originating-IP: [216.27.227.3] From: "Not Going to Tell You" To: stable@freebsd.org Subject: Help in removing from list Date: Sat, 23 Nov 2002 21:27:24 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Nov 2002 21:27:24.0430 (UTC) FILETIME=[1D53A2E0:01C29337] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have sent several request to be removed from all the FreeBSD lists, but I do not get the reply confirmation email. I am getting tired of trying and would like some help from the admin of these list. Regards, LuckyWolf19@hotmail.com _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 13:32:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C450937B401 for ; Sat, 23 Nov 2002 13:32:21 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8159F43EA3 for ; Sat, 23 Nov 2002 13:32:21 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id AF0B68A4CFB; Sat, 23 Nov 2002 17:32:20 -0400 (AST) Date: Sat, 23 Nov 2002 17:32:20 -0400 (AST) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Cc: "Moore, Eric Dean" Subject: Upgrade MegaRAID firmware and SMP no longer works ... ? Message-ID: <20021123164528.Q22758-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Okay, this one is strange one, but I've tried everything that I can think of and its all failing ... On Friday night, I got Rackspace ot upgrade the firmware on my AMI MegaRAID controller to the C170 Firmware, as reported by the OS: amr0: mem 0xfc5f0000-0xfc5fffff irq 10 at device 2.0 on pci1 amr0: Firmware C170, BIOS 3.13, 32MB RAM in the hopes that i could get past the Oct 28th -STABLE kernel, after the changes were made to the AMR driver ... unfortunately, this is made the situtation worse ... no I can't boot into *any* SMP kernel, even the one that was running prior to the firmware upgrade on Friday :( Now, I did a boot -v (through /boot.config) and just noticed this: IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 bios32: Found BIOS32 Service Directory header at 0xc00fdb90 bios32: Entry = 0xfdba0 (c00fdba0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xdbc1 pnpbios: Found PnP BIOS data at 0xc00f4c50 pnpbios: Entry = f0000:3954 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 I'm missing a CPU here ... it was there the other day ... other then taking the CPU out, is there anything on the FreeBSD/software side of things that would cause a CPU to go un-detected? Thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 15:14:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 924D837B401 for ; Sat, 23 Nov 2002 15:14:49 -0800 (PST) Received: from nemesis.systems.pipex.net (nemesis.systems.pipex.net [62.241.160.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAB4843E4A for ; Sat, 23 Nov 2002 15:14:48 -0800 (PST) (envelope-from stacey@vickiandstacey.com) Received: from [192.168.1.8] (81-86-129-77.dsl.pipex.com [81.86.129.77]) by nemesis.systems.pipex.net (Postfix) with ESMTP id 23D2516007FC0; Sat, 23 Nov 2002 23:14:40 +0000 (GMT) Subject: Re: Port INDEX dependency list incompletes From: Stacey Roberts Reply-To: stacey@vickiandstacey.com To: Kent Stewart Cc: Lefteris Tsintjelis , a , stable@FreeBSD.ORG In-Reply-To: <3DDFE4D6.5090901@owt.com> References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> <3DDFE0AC.57BF260E@ene.asda.gr> <3DDFE4D6.5090901@owt.com> Content-Type: text/plain Organization: Message-Id: <1038093287.43256.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 23 Nov 2002 23:14:47 +0000 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Kent, I wanted to square with you that this is as one would expect from "make index" and "portsdb -u" at the end of cvsup of ports tree: # make index Generating INDEX - please wait..Warning: Duplicate INDEX entry: freeciv-imlib-1.13.0 Done. #portsdb -u [Updating the portsdb in /usr/ports ... - 7860 port entries found .........1000.........2000.........3000.........4000.........5000.........6000.........7000........ ..... done] # Is the one warning there about freeciv-imlib-1.13.0 being duplicated okay? I ask as this is usually the last entry in my regular portsdb -Uu after cvsup'ing ports tree. Regards, Stacey On Sat, 2002-11-23 at 20:28, Kent Stewart wrote: > Lefteris Tsintjelis wrote: > > Kent Stewart wrote: > > > >>cd /usr/ports > >>make index > >>portsdb -u > > > > > > I get almost always "dependency list incompletes" with portsdb -Uu. > > Would it be a good idea to always use the above instead? > > No, because portsdb -U uses much less computer time to rebuild INDEX > than make index does. On my AMD 2000+ XP, which is designed to do 20 > minute buildworlds, a portsdb -U requires ~7 minutes and a make index > requires ~11 minutes. If you are going to work on your ports, the > extra time is time you just sit there. I find people go into their own > version of an idle-loop after 2 minutes. > > We just have to wait for knu to fix it. > > KEnt -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 16:14:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6950437B401 for ; Sat, 23 Nov 2002 16:14:11 -0800 (PST) Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E546043E3B for ; Sat, 23 Nov 2002 16:14:10 -0800 (PST) (envelope-from jtm63@enteract.com) Received: from jamestown.21stcentury.net (24-148-18-147.na.21stcentury.net [24.148.18.147]) by smtp-2.enteract.com (Postfix) with ESMTP id 4E9B45F71; Sat, 23 Nov 2002 18:14:05 -0600 (CST) Received: from jamestown.21stcentury.net (localhost [127.0.0.1]) by jamestown.21stcentury.net (8.12.5/8.12.5) with ESMTP id gAO0E083015674; Sat, 23 Nov 2002 18:14:02 -0600 (CST) (envelope-from jtm@jamestown.21stcentury.net) Received: (from jtm@localhost) by jamestown.21stcentury.net (8.12.5/8.12.5/Submit) id gAO0DwPW015671; Sat, 23 Nov 2002 18:13:59 -0600 (CST) To: "Not Going to Tell You" Cc: stable@freebsd.org Subject: Re: Help in removing from list References: From: James McNaughton Date: 23 Nov 2002 18:13:55 -0600 In-Reply-To: Message-ID: <864ra7ygcc.fsf@jamestown.21stcentury.net> Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Not Going to Tell You" writes: > Hi, > I have sent several request to be removed from all the FreeBSD lists, > but I do not get the reply confirmation email. I am getting tired of > trying and would like some help from the admin of these list. Have you sent the requests to majordomo@freebsd.org with "unsubscribe ${listname}" in the body? -and- Do you have any funky anti-spam strategy in your headers? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 16:50:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F6BD37B401 for ; Sat, 23 Nov 2002 16:50:08 -0800 (PST) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36EFD43E6E for ; Sat, 23 Nov 2002 16:50:08 -0800 (PST) (envelope-from ps@yogurt.yahoo.com) Received: from yogurt.yahoo.com (yogurt.yahoo.com [216.145.52.186]) by mrout1.yahoo.com (8.11.6/8.11.6/y.out) with ESMTP id gAO0nbC91113; Sat, 23 Nov 2002 16:49:37 -0800 (PST) Received: (from ps@localhost) by yogurt.yahoo.com (8.11.6/8.11.6) id gAO0lOh24209; Sat, 23 Nov 2002 16:47:24 -0800 (PST) (envelope-from ps) Date: Sat, 23 Nov 2002 16:47:24 -0800 From: Paul Saab To: Pete French Cc: stable@FreeBSD.ORG Subject: Re: RAID performance problems Message-ID: <20021124004724.GA24189@yahoo-inc.com> Reply-To: ps@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Are you sure the Battery module is installed? If it isn't, then the read/write cache would not be enabled. Pete French (pfrench@firstcallgroup.co.uk) wrote: > I wonder if anyone can shed any light on the following, as I am > starting to come to the conclusion that its possibly some BSD driver > issue. > > I have been testing the performance of the various drives on my system > using bonnie, just out of curiosity. The system has 3 different drives on > it: > > 1) a 15k RPM drive attached directly to an Adaptec SCSI controller > 2) a RAID-1 mirrored pair of 10k RPS drives > 3) a RAID-5 set of 5 7200 RPM drives > > All SCSI buses are 40MB/sec. Both the RAID drives are being run from the > same Compaq 4200 RAID controller. Both the RAID controller and the Adaptec > SCSI card are on the same PCI bus. > > So, what I expected was that the driect drive would be fastest, followed by > the RAID-1, then the RAID-5 (at least as far as write performance goes) > > The actual results are that both the RAID drives have identical performance! > The direct drive is 4 times faster than these. > > This was a bit of a shock to me. Especially ater all the effort of utting > in thr 10k RPM drives to try and speed that disc up. The obvious conclusion > is that somewhere there is some component common to both RAID drives which is > limiting the performance. > > The bottleneck cannot be the PCI bus to the card as the direct drive is > shifting 4 times the data on the same bus. It also cannot be the SCSI > bus to the drives by my reasoning - even assuming that the controller > aggregates the writes so that RAID-5 and RAID-1 are taking the same bandwidth > on the bus (which is necessary if they are to perform the same with the bus > being the bottleneck right?) then the bus is operating 4x slower than the > direct bus. The Compaq card supports 40MB/s bus speeds according to > the documentation - plus the bus is terminated correctly as plugging the array > into the SCSI card shows all the drives up as 40MB/s > > So I'm left with one of two conclusions > > a) This is a limitation in the processing power of the RAID card. This seems > very unlikely - the work needed to be done by the controller for RAID-1 > is far less than that which needs to be done for RAID-5 (it would take a > complete muppet to design a controller where this wasnt the case wouldnt > it ?) and this is one of Compaq's meatier controllers afer all. > > b) This is some strange limitation in the speed at which FreeBSD's device > driver for Compaq controllers can talk to the actual device. > > Its the fact that I have arrived at conclusion b) as a possibility that makes > me ask on here. Does anyone have any comments or thoughts on this ? I know > there are people around who can argue at great length about RAID performance > after all :-) > > -pcf. [puzzled] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:29:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42FA437B401 for ; Sat, 23 Nov 2002 17:29:08 -0800 (PST) Received: from web13205.mail.yahoo.com (web13205.mail.yahoo.com [216.136.174.190]) by mx1.FreeBSD.org (Postfix) with SMTP id DC61A43E6E for ; Sat, 23 Nov 2002 17:29:07 -0800 (PST) (envelope-from bsd_kb@yahoo.com) Message-ID: <20021124012907.40052.qmail@web13205.mail.yahoo.com> Received: from [12.211.5.196] by web13205.mail.yahoo.com via HTTP; Sat, 23 Nov 2002 17:29:07 PST Date: Sat, 23 Nov 2002 17:29:07 -0800 (PST) From: Yuri K Subject: Portupgrade: persistant libgtop failure To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, this has been a pain for me for a while preventing to get other packages udgraded, here is a chunk of output: guile-names.c:1560: warning: `glibtop_guile_descriptions_mem' defined but not used cpp0: output pipe has been closed gmake[4]: *** [guile-names.lo] Error 1 gmake[4]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13/sysdeps/guile/names' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13/sysdeps/guile' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13/sysdeps' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Stop in /usr/ports/devel/libgtop. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade39904.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! devel/libgtop (libgtop-1.0.13) (compiler error) the same expanded: In file included from guile-names.c:1671: /usr/include/stdio.h:221: arguments given to macro `getchar' In file included from /usr/include/sys/types.h:126, from /usr/include/sys/time.h:40, from ../../../include/glibtop/global.h:67, from ../../../glibtop.h:27, from guile-names.c:4, from guile-names.c:1671: /usr/include/machine/endian.h: In function `glibtop_boot_guile_names': /usr/include/machine/endian.h:63: syntax error before `__extension__' /usr/include/machine/endian.h:63: `__X' undeclared (first use in this function) /usr/include/machine/endian.h:63: (Each undeclared identifier is reported only once /usr/include/machine/endian.h:63: for each function it appears in.) /usr/include/machine/endian.h: At top level: /usr/include/machine/endian.h:63: syntax error before `)' guile-names.c:12: warning: `glibtop_guile_names_proc_args' defined but not used guile-names.c:29: warning: `glibtop_guile_types_proc_args' defined but not used guile-names.c:40: warning: `glibtop_guile_labels_proc_args' defined but not used guile-names.c:57: warning: `glibtop_guile_descriptions_proc_args' defined but not used guile-names.c:74: warning: `glibtop_guile_names_proc_time' defined but not used guile-names.c:91: warning: `glibtop_guile_types_proc_time' defined but not used guile-names.c:116: warning: `glibtop_guile_labels_proc_time' defined but not used guile-names.c:133: warning: `glibtop_guile_descriptions_proc_time' defined but not used guile-names.c:150: warning: `glibtop_guile_names_proc_segment' defined but not used guile-names.c:167: warning: `glibtop_guile_types_proc_segment' defined but not used guile-names.c:185: warning: `glibtop_guile_labels_proc_segment' defined but not used guile-names.c:202: warning: `glibtop_guile_descriptions_proc_segment' defined but not used guile-names.c:219: warning: `glibtop_guile_names_netload' defined but not used guile-names.c:236: warning: `glibtop_guile_types_netload' defined but not used guile-names.c:260: warning: `glibtop_guile_labels_netload' defined but not used guile-names.c:277: warning: `glibtop_guile_descriptions_netload' defined but not used guile-names.c:294: warning: `glibtop_guile_names_cpu' defined but not used guile-names.c:311: warning: `glibtop_guile_types_cpu' defined but not used guile-names.c:342: warning: `glibtop_guile_labels_cpu' defined but not used guile-names.c:359: warning: `glibtop_guile_descriptions_cpu' defined but not used guile-names.c:376: warning: `glibtop_guile_names_sysdeps' defined but not used guile-names.c:393: warning: `glibtop_guile_types_sysdeps' defined but not used guile-names.c:403: warning: `glibtop_guile_labels_sysdeps' defined but not used guile-names.c:420: warning: `glibtop_guile_descriptions_sysdeps' defined but not used guile-names.c:437: warning: `glibtop_guile_names_fsusage' defined but not used guile-names.c:454: warning: `glibtop_guile_types_fsusage' defined but not used guile-names.c:469: warning: `glibtop_guile_labels_fsusage' defined but not used guile-names.c:486: warning: `glibtop_guile_descriptions_fsusage' defined but not used guile-names.c:503: warning: `glibtop_guile_names_mountlist' defined but not used guile-names.c:520: warning: `glibtop_guile_types_mountlist' defined but not used guile-names.c:533: warning: `glibtop_guile_labels_mountlist' defined but not used guile-names.c:550: warning: `glibtop_guile_descriptions_mountlist' defined but not used guile-names.c:567: warning: `glibtop_guile_names_ppp' defined but not used guile-names.c:584: warning: `glibtop_guile_types_ppp' defined but not used guile-names.c:597: warning: `glibtop_guile_labels_ppp' defined but not used guile-names.c:614: warning: `glibtop_guile_descriptions_ppp' defined but not used guile-names.c:631: warning: `glibtop_guile_names_proclist' defined but not used guile-names.c:648: warning: `glibtop_guile_types_proclist' defined but not used guile-names.c:661: warning: `glibtop_guile_labels_proclist' defined but not used guile-names.c:678: warning: `glibtop_guile_descriptions_proclist' defined but not used guile-names.c:695: warning: `glibtop_guile_names_proc_signal' defined but not used guile-names.c:712: warning: `glibtop_guile_types_proc_signal' defined but not used guile-names.c:734: warning: `glibtop_guile_labels_proc_signal' defined but not used guile-names.c:751: warning: `glibtop_guile_descriptions_proc_signal' defined but not used guile-names.c:768: warning: `glibtop_guile_names_proc_map' defined but not used guile-names.c:785: warning: `glibtop_guile_types_proc_map' defined but not used guile-names.c:798: warning: `glibtop_guile_labels_proc_map' defined but not used guile-names.c:815: warning: `glibtop_guile_descriptions_proc_map' defined but not used guile-names.c:832: warning: `glibtop_guile_names_proc_mem' defined but not used guile-names.c:849: warning: `glibtop_guile_types_proc_mem' defined but not used guile-names.c:865: warning: `glibtop_guile_labels_proc_mem' defined but not used guile-names.c:882: warning: `glibtop_guile_descriptions_proc_mem' defined but not used guile-names.c:899: warning: `glibtop_guile_names_uptime' defined but not used guile-names.c:916: warning: `glibtop_guile_types_uptime' defined but not used guile-names.c:928: warning: `glibtop_guile_labels_uptime' defined but not used guile-names.c:945: warning: `glibtop_guile_descriptions_uptime' defined but not used guile-names.c:962: warning: `glibtop_guile_names_proc_state' defined but not used guile-names.c:979: warning: `glibtop_guile_types_proc_state' defined but not used guile-names.c:993: warning: `glibtop_guile_labels_proc_state' defined but not used guile-names.c:1010: warning: `glibtop_guile_descriptions_proc_state' defined but not used guile-names.c:1027: warning: `glibtop_guile_names_proc_kernel' defined but not used guile-names.c:1044: warning: `glibtop_guile_types_proc_kernel' defined but not used guile-names.c:1063: warning: `glibtop_guile_labels_proc_kernel' defined but not used guile-names.c:1080: warning: `glibtop_guile_descriptions_proc_kernel' defined but not used guile-names.c:1097: warning: `glibtop_guile_names_proc_uid' defined but not used guile-names.c:1114: warning: `glibtop_guile_types_proc_uid' defined but not used guile-names.c:1136: warning: `glibtop_guile_labels_proc_uid' defined but not used guile-names.c:1153: warning: `glibtop_guile_descriptions_proc_uid' defined but not used guile-names.c:1170: warning: `glibtop_guile_names_sem_limits' defined but not used guile-names.c:1187: warning: `glibtop_guile_types_sem_limits' defined but not used guile-names.c:1207: warning: `glibtop_guile_labels_sem_limits' defined but not used guile-names.c:1224: warning: `glibtop_guile_descriptions_sem_limits' defined but not used guile-names.c:1241: warning: `glibtop_guile_names_msg_limits' defined but not used guile-names.c:1258: warning: `glibtop_guile_types_msg_limits' defined but not used guile-names.c:1275: warning: `glibtop_guile_labels_msg_limits' defined but not used guile-names.c:1292: warning: `glibtop_guile_descriptions_msg_limits' defined but not used guile-names.c:1309: warning: `glibtop_guile_names_shm_limits' defined but not used guile-names.c:1326: warning: `glibtop_guile_types_shm_limits' defined but not used guile-names.c:1341: warning: `glibtop_guile_labels_shm_limits' defined but not used guile-names.c:1358: warning: `glibtop_guile_descriptions_shm_limits' defined but not used guile-names.c:1375: warning: `glibtop_guile_names_swap' defined but not used guile-names.c:1392: warning: `glibtop_guile_types_swap' defined but not used guile-names.c:1407: warning: `glibtop_guile_labels_swap' defined but not used guile-names.c:1424: warning: `glibtop_guile_descriptions_swap' defined but not used guile-names.c:1441: warning: `glibtop_guile_names_loadavg' defined but not used guile-names.c:1458: warning: `glibtop_guile_types_loadavg' defined but not used guile-names.c:1474: warning: `glibtop_guile_labels_loadavg' defined but not used guile-names.c:1491: warning: `glibtop_guile_descriptions_loadavg' defined but not used guile-names.c:1508: warning: `glibtop_guile_names_mem' defined but not used guile-names.c:1525: warning: `glibtop_guile_types_mem' defined but not used guile-names.c:1543: warning: `glibtop_guile_labels_mem' defined but not used guile-names.c:1560: warning: `glibtop_guile_descriptions_mem' defined but not used cpp0: output pipe has been closed gmake[4]: *** [guile-names.lo] Error 1 gmake[4]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13/sysdeps/guile/names' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13/sysdeps/guile' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13/sysdeps' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/devel/libgtop/work/libgtop-1.0.13' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Stop in /usr/ports/devel/libgtop. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade39904.0 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! devel/libgtop (libgtop-1.0.13) (compiler error) __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus – Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:38:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2106837B401 for ; Sat, 23 Nov 2002 17:38:14 -0800 (PST) Received: from mail.gbronline.com (mail.gbronline.com [12.145.226.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 655B143E6E for ; Sat, 23 Nov 2002 17:38:13 -0800 (PST) (envelope-from kdk@daleco.biz) Received: from DaleCoportable [207.191.248.38] by mail.gbronline.com (SMTPD32-7.13) id ACF948C00108; Sat, 23 Nov 2002 19:35:53 -0600 Message-ID: <098601c29359$c1393740$faec910c@DaleCoportable> From: "Kevin D. Kinsey, DaleCo, S.P." To: Subject: Installworld: boot2: no such file --- anyone remember, or new bork? Date: Sat, 23 Nov 2002 19:35:17 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Seems like I saw this issue not too long ago on this list, but I've not seen it in the archives of October or November... make installworld failed here, twice: ++++++++++++++++++++++++++++++++++++ install -o root -g wheel -m 444 mbr /boot ===> sys/boot/i386/boot0 install -o root -g wheel -m 444 boot0 /boot ===> sys/boot/i386/btx ===> sys/boot/i386/btx/btx ===> sys/boot/i386/btx/btxldr ===> sys/boot/i386/btx/lib ===> sys/boot/i386/boot2 install -o root -g wheel -m 444 boot1 /boot/boot1 install -o root -g wheel -m 444 boot2 /boot/boot2 install: boot2: No such file or directory *** Error code 71 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. +++++++++++++++++++++++++++++ Something's borked, did I do it, or just cvs at the wrong time? Thx, Kevin Kinsey DaleCo, S.P. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:45: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF5F037B401 for ; Sat, 23 Nov 2002 17:45:02 -0800 (PST) Received: from softweyr.com (softweyr.com [209.63.227.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CB6943E6E for ; Sat, 23 Nov 2002 17:45:02 -0800 (PST) (envelope-from wes@softweyr.com) Received: from homer.softweyr.com ([204.68.178.39] helo=softweyr.com) by softweyr.com with esmtp (Exim 3.35 #1) id 18Flp8-0006Em-00; Sat, 23 Nov 2002 18:44:38 -0700 Message-ID: <3DE02EFC.AB671666@softweyr.com> Date: Sat, 23 Nov 2002 17:44:28 -0800 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Tim Wilde Cc: Thomas Seck , stable@FreeBSD.ORG Subject: Re: named.root References: <20021121204315.707455D04@ptavv.es.net> <3DDDD74D.F4BC206F@softweyr.com> <20021122162336.GA480@laurel.tmseck.homedns.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tim Wilde wrote: > > On Fri, 22 Nov 2002, Thomas Seck wrote: > > > No one is kept from modifying his or her local copy of FreeBSD to suit > > his resp. her needs. I do not think that Network Solutions will assign > > 198.41.0.10 tomorrow to $evil_person for $most_evil_purpose but YMMV. > > They have explicitly stated, in fact, that it will continue providing root > DNS service for at least 5 years. They are, of course, assuming they will be around to insure that for at least 5 years. I'm not sure I agree with that assumption either. This update certainly didn't harm RELENG_4_7 in any way, why in hell are you two still carping about it? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:46:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40AA237B406 for ; Sat, 23 Nov 2002 17:46:51 -0800 (PST) Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97EFF43E91 for ; Sat, 23 Nov 2002 17:46:50 -0800 (PST) (envelope-from kstewart@owt.com) Received: from owt.com (owt-207-41-94-232.owt.com [207.41.94.232]) by rutger.owt.com (8.9.3/8.9.3) with ESMTP id RAA09024; Sat, 23 Nov 2002 17:46:43 -0800 Message-ID: <3DE02F83.6050407@owt.com> Date: Sat, 23 Nov 2002 17:46:43 -0800 From: Kent Stewart User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, es-mx MIME-Version: 1.0 To: stacey@vickiandstacey.com Cc: Lefteris Tsintjelis , a , stable@FreeBSD.ORG Subject: Re: Port INDEX dependency list incompletes References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> <3DDFE0AC.57BF260E@ene.asda.gr> <3DDFE4D6.5090901@owt.com> <1038093287.43256.12.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Stacey Roberts wrote: > Hi Kent, > I wanted to square with you that this is as one would expect from > "make index" and "portsdb -u" at the end of cvsup of ports tree: > # make index > Generating INDEX - please wait..Warning: Duplicate INDEX entry: > freeciv-imlib-1.13.0 > Done. > #portsdb -u > [Updating the portsdb in /usr/ports ... - 7860 port > entries found > .........1000.........2000.........3000.........4000.........5000.........6000.........7000........ ..... done] > # > > Is the one warning there about freeciv-imlib-1.13.0 being duplicated > okay? I ask as this is usually the last entry in my regular portsdb -Uu > after cvsup'ing ports tree. Kris told me that it was because I had imlib installed, which I did. I also figured that one message about a port I didn't use was much better than screens of messages about ports I did use :). Kent > > Regards, > > Stacey > > On Sat, 2002-11-23 at 20:28, Kent Stewart wrote: > >>Lefteris Tsintjelis wrote: >> >>>Kent Stewart wrote: >>> >>> >>>>cd /usr/ports >>>>make index >>>>portsdb -u >>> >>> >>>I get almost always "dependency list incompletes" with portsdb -Uu. >>>Would it be a good idea to always use the above instead? >> >>No, because portsdb -U uses much less computer time to rebuild INDEX >>than make index does. On my AMD 2000+ XP, which is designed to do 20 >>minute buildworlds, a portsdb -U requires ~7 minutes and a make index >>requires ~11 minutes. If you are going to work on your ports, the >>extra time is time you just sit there. I find people go into their own >>version of an idle-loop after 2 minutes. >> >>We just have to wait for knu to fix it. >> >>KEnt > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:48:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7FA037B401 for ; Sat, 23 Nov 2002 17:48:51 -0800 (PST) Received: from buffoon.automagic.org (buffoon.automagic.org [208.185.30.208]) by mx1.FreeBSD.org (Postfix) with SMTP id 26EEF43E91 for ; Sat, 23 Nov 2002 17:48:51 -0800 (PST) (envelope-from jabley@buffoon.automagic.org) Received: (qmail 91638 invoked by uid 1000); 24 Nov 2002 01:48:50 -0000 Date: Sat, 23 Nov 2002 20:48:50 -0500 From: Joe Abley To: Wes Peters Cc: Tim Wilde , Thomas Seck , stable@FreeBSD.ORG Subject: Re: named.root Message-ID: <20021124014850.GF90840@buffoon.automagic.org> References: <20021121204315.707455D04@ptavv.es.net> <3DDDD74D.F4BC206F@softweyr.com> <20021122162336.GA480@laurel.tmseck.homedns.org> <3DE02EFC.AB671666@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DE02EFC.AB671666@softweyr.com> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Nov 23, 2002 at 05:44:28PM -0800, Wes Peters wrote: > They are, of course, assuming they will be around to insure that for at > least 5 years. I'm not sure I agree with that assumption either. Both the old and the new addresses for J are located within swamp /24s which can be readily advertised from one or more places anywhere on the network without much risk of being filtered. Whether or not one of those /24s happens to still be operated by Verisign in five years time is not all that important. Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:58:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11D9237B401 for ; Sat, 23 Nov 2002 17:58:26 -0800 (PST) Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 419B243E9C for ; Sat, 23 Nov 2002 17:58:25 -0800 (PST) (envelope-from andrew@ugh.net.au) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id E4EB2A804; Sun, 24 Nov 2002 12:58:16 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id B4E70542D; Sun, 24 Nov 2002 12:58:16 +1100 (EST) Date: Sun, 24 Nov 2002 12:58:16 +1100 (EST) From: Andrew To: Antony Mawer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make release broken (touch: not found) In-Reply-To: <3DDFB54F.4080401@optusnet.com.au> Message-ID: <20021124125739.R39653-100000@starbug.ugh.net.au> X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 24 Nov 2002, Antony Mawer wrote: > Have you done a cd /usr/src && make buildworld first? I ran into this > about 24hrs ago, as it seems 'make release' expects a 'make buildworld' > to have been executed prior to execution. It then installs into the > chroot'd directory and starts its work from there! I had but doing it again may have fixed it (something did). Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 17:59:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19C4337B404 for ; Sat, 23 Nov 2002 17:59:49 -0800 (PST) Received: from colossus.systems.pipex.net (colossus.systems.pipex.net [62.241.160.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D98E43E88 for ; Sat, 23 Nov 2002 17:59:44 -0800 (PST) (envelope-from stacey@vickiandstacey.com) Received: from [192.168.1.8] (81-86-129-77.dsl.pipex.com [81.86.129.77]) by colossus.systems.pipex.net (Postfix) with ESMTP id D15781600028E; Sun, 24 Nov 2002 01:59:39 +0000 (GMT) Subject: Re: Port INDEX dependency list incompletes From: Stacey Roberts Reply-To: stacey@vickiandstacey.com To: Kent Stewart Cc: Lefteris Tsintjelis , a , stable@FreeBSD.ORG In-Reply-To: <3DE02F83.6050407@owt.com> References: <3DDF911D.5FF8F512@ene.asda.gr> <3DDF9EFC.E3B42B5D@ene.asda.gr> <20021123170312.3af58fdd.a@grunix.com> <3DDFA761.D459E000@ene.asda.gr> <3DDFCA8A.40104@owt.com> <3DDFE0AC.57BF260E@ene.asda.gr> <3DDFE4D6.5090901@owt.com> <1038093287.43256.12.camel@localhost> <3DE02F83.6050407@owt.com> Content-Type: text/plain Organization: Message-Id: <1038103185.43256.78.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 24 Nov 2002 01:59:46 +0000 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Kent, Thanks for that.., I'll keep looking out for some update from the maintainers on some progress to the issues with portsdb -U Regards, Stacey On Sun, 2002-11-24 at 01:46, Kent Stewart wrote: > Stacey Roberts wrote: > > Hi Kent, > > I wanted to square with you that this is as one would expect from > > "make index" and "portsdb -u" at the end of cvsup of ports tree: > > # make index > > Generating INDEX - please wait..Warning: Duplicate INDEX entry: > > freeciv-imlib-1.13.0 > > Done. > > #portsdb -u > > [Updating the portsdb in /usr/ports ... - 7860 port > > entries found > > .........1000.........2000.........3000.........4000.........5000.........6000.........7000........ ..... done] > > # > > > > Is the one warning there about freeciv-imlib-1.13.0 being duplicated > > okay? I ask as this is usually the last entry in my regular portsdb -Uu > > after cvsup'ing ports tree. > > Kris told me that it was because I had imlib installed, which I did. > > I also figured that one message about a port I didn't use was much > better than screens of messages about ports I did use :). > > Kent > > > > > Regards, > > > > Stacey > > > > On Sat, 2002-11-23 at 20:28, Kent Stewart wrote: > > > >>Lefteris Tsintjelis wrote: > >> > >>>Kent Stewart wrote: > >>> > >>> > >>>>cd /usr/ports > >>>>make index > >>>>portsdb -u > >>> > >>> > >>>I get almost always "dependency list incompletes" with portsdb -Uu. > >>>Would it be a good idea to always use the above instead? > >> > >>No, because portsdb -U uses much less computer time to rebuild INDEX > >>than make index does. On my AMD 2000+ XP, which is designed to do 20 > >>minute buildworlds, a portsdb -U requires ~7 minutes and a make index > >>requires ~11 minutes. If you are going to work on your ports, the > >>extra time is time you just sit there. I find people go into their own > >>version of an idle-loop after 2 minutes. > >> > >>We just have to wait for knu to fix it. > >> > >>KEnt > > -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 18:22:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA13737B401 for ; Sat, 23 Nov 2002 18:22:57 -0800 (PST) Received: from smtp0.adl1.internode.on.net (smtp0.adl1.internode.on.net [203.16.214.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6465043E91 for ; Sat, 23 Nov 2002 18:22:56 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from midget.dons.net.au (ppp1561.sa.padsl.internode.on.net [150.101.252.24]) by smtp0.adl1.internode.on.net (8.12.4/8.12.4) with ESMTP id gAO2Mmp5071755; Sun, 24 Nov 2002 12:52:49 +1030 (CST) Received: from guppy.dons.net.au (guppy.dons.net.au [10.0.2.9]) by midget.dons.net.au (8.12.2/8.12.2) with ESMTP id gAO2NAeQ072085; Sun, 24 Nov 2002 12:53:11 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Received: from guppy.dons.net.au (localhost [127.0.0.1]) by guppy.dons.net.au (8.12.6/8.12.6) with ESMTP id gAO2MoDf001240; Sun, 24 Nov 2002 12:52:51 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Content-Type: text/plain; charset="iso-8859-1" From: "Daniel O'Connor" To: Martin Gumucio Subject: Re: nvidia tv-out Date: Sun, 24 Nov 2002 12:52:50 +1030 User-Agent: KMail/1.4.3 Cc: freebsd-stable@FreeBSD.ORG References: <20021121164650.421c9b9a.martin@gumucio.com> <1037919023.4656.0.camel@chowder.gsoft.com.au> <20021123184614.056e237d.martin@gumucio.com> In-Reply-To: <20021123184614.056e237d.martin@gumucio.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200211241252.50107.doconnor@gsoft.com.au> X-Spam-Score: -3.4 () IN_REP_TO X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 24 Nov 2002 04:16 am, Martin Gumucio wrote: > I guess the horz sync freq's are wrong, but "30-50", (from the nvidia docs) > is about the only thing that works even a little. What freq's work for you? I haven't tried TV out yet :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 19:22: 0 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDA3B37B404 for ; Sat, 23 Nov 2002 19:21:58 -0800 (PST) Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net [204.127.131.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A8EC43E6E for ; Sat, 23 Nov 2002 19:21:53 -0800 (PST) (envelope-from cswiger@mac.com) Received: from prime ([12.88.86.18]) by mtiwmhc12.worldnet.att.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with SMTP id <20021124032125.CLK13909.mtiwmhc12.worldnet.att.net@prime> for ; Sun, 24 Nov 2002 03:21:25 +0000 Message-ID: <01de01c29368$a2893ca0$0301a8c0@prime> From: "Charles Swiger" To: References: Subject: Re: RAID performance problems Date: Sat, 23 Nov 2002 22:21:52 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Pete French wrote: [ ... ] > 1) a 15k RPM drive attached directly to an Adaptec SCSI controller > 2) a RAID-1 mirrored pair of 10k RPS drives > 3) a RAID-5 set of 5 7200 RPM drives > > All SCSI buses are 40MB/sec. Both the RAID drives are being run from > the same Compaq 4200 RAID controller. Both the RAID controller and > the Adaptec SCSI card are on the same PCI bus. > > So, what I expected was that the driect drive would be fastest, > followed by the RAID-1, then the RAID-5 (at least as far as write > performance goes) You're not going to be able to derive firm conclusions from changing two variables at a time, unless you fill in the other missing pieces. Try comparing one of the five 7200 RPM drives via direct I/O versus two 7200 RPM drives in a RAID-1 mirror, versus the RAID-5 case. If you're using hardware RAID, then FreeBSD will be treating it like a single (larger) device, not going through vinum or some other OS-level software RAID. I agree that your results are somewhat surprising.... -Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 19:34: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E20637B401; Sat, 23 Nov 2002 19:34:02 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C58843E6E; Sat, 23 Nov 2002 19:34:02 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id 5E55A8A4D5C; Sat, 23 Nov 2002 23:34:00 -0400 (AST) Date: Sat, 23 Nov 2002 23:34:00 -0400 (AST) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Cc: freebsd-hardware@freebsd.org, "Moore, Eric Dean" Subject: CPU not detected after firmware upgrade ... Message-ID: <20021123222059.N16724-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Over the past couple of weeks, I've been experiencing a problem where -STABLE after Oct 28th would hang on booting. The only change that appeared to be on the 29th was the amr driver changes that Eric committed, and he suggested upgrading the firmware on my MegaRAID controller to 'correct' the issue. Last night, Rackspace performed that upgrade for us, and powered up using the same kernel (RELENG_4_7) we had installed ... it hung on reboot. They could boot off of the GENERIC kernel that I still had on that machine, but not the kernel that I had running several hours previous ... after playing with the kernel config for a period of time, I finally figured out that as long as I didn't enable SMP, the kernel would boot. Not good, but better then nothing ... Today, after getting some rest, I dove back into things again, finally thinking to setup /boot.config to enable -v on boot, figuring that was hte only way I was going to more detailed information ... After looking through /var/run/dmesg.boot after trying to boot an SMP kernel, I noticed that the kernel isn't detecting the second CPU in the machine: IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 bios32: Found BIOS32 Service Directory header at 0xc00fdb90 bios32: Entry = 0xfdba0 (c00fdba0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xdbc1 pnpbios: Found PnP BIOS data at 0xc00f4c50 pnpbios: Entry = f0000:3954 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 whereas my other server, same motherboard and BIOS level, shows: FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 4, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 5, version: 0x000f0011, at 0xfec01000 Now, I've had Rackspace check to make sure that the second CPU is, in fact, in the machine, and they went to the extent of swap out the CPUs and put new ones in ... the CPUs are detected by the BIOs itself, its only once it gets to the OS level that it seems to "lose" the second CPU ... The kernel config I'm trying to boot is quite basic, and included at the bottom of this ... What would cause a CPU to "disappear" as far as the operating system is concerned? And how could a firmware upgrade (and/or driver upgrade) cause this? This is a totally new one for me, and I haven't got a clue what direction to go at next ... ___machine i386 ___cpu I686_CPU ___ident kernel ___maxusers 0 ___makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols ___options INET #InterNETworking ___options FFS #Berkeley Fast Filesystem ___options FFS_ROOT #FFS usable as root device [keep this!] ___options SOFTUPDATES #Enable FFS soft updates support ___options UFS_DIRHASH #Improve performance on big directories ___options PROCFS #Process filesystem ___options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] ___options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI ___options KTRACE #ktrace(1) support ___options SYSVSHM ___options SHMMAXPGS=199608 ___options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) ___options SYSVSEM ___options SEMMNI=4096 ___options SEMMNS=8192 ___options SYSVMSG #SYSV-style message queues ___options IPFIREWALL #firewall ___options IPFIREWALL_FORWARD #enable transparent proxy support ___options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default ___options P1003_1B #Posix P1003_1B real-time extensions ___options _KPOSIX_PRIORITY_SCHEDULING ___options ICMP_BANDLIM #Rate limit bad replies ___options KBD_INSTALL_CDEV # install a CDEV entry in /dev ___# To make an SMP kernel, the next two are needed ___options SMP # Symmetric MultiProcessor Kernel ___options APIC_IO # Symmetric (APIC) I/O ___device isa ___device pci ___device sym # NCR/Symbios Logic (newer chipsets) ___device scbus # SCSI bus (required) ___device da # Direct Access (disks) ___device sa # Sequential Access (tape etc) ___device pass # Passthrough device (direct SCSI access) ___device amr # AMI MegaRAID ___device atkbdc0 at isa? port IO_KBD ___device atkbd0 at atkbdc? irq 1 flags 0x1 ___device psm0 at atkbdc? irq 12 ___device vga0 at isa? ___pseudo-device splash ___device sc0 at isa? flags 0x100 ___device npx0 at nexus? port IO_NPX irq 13 ___device miibus # MII bus support ___device fxp # Intel EtherExpress PRO/100B (82557, 82558) ___pseudo-device loop # Network loopback ___pseudo-device ether # Ethernet support ___pseudo-device pty 256 # Pseudo-ttys (telnet etc) ___pseudo-device bpf #Berkeley packet filter ___options DDB ___options DDB_UNATTENDED ___options INCLUDE_CONFIG_FILE # Include this file in kernel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 23 22:25: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C949937B401 for ; Sat, 23 Nov 2002 22:25:05 -0800 (PST) Received: from iscan1.intra.oki.co.jp (okigate.oki.co.jp [202.226.91.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8382843E4A for ; Sat, 23 Nov 2002 22:25:03 -0800 (PST) (envelope-from yamamoto436@oki.com) Received: from aoi.okilab.oki.co.jp (IDENT:root@localhost.localdomain [127.0.0.1]) by iscan1.intra.oki.co.jp (8.9.3/8.9.3) with SMTP id PAA09990 for ; Sun, 24 Nov 2002 15:24:56 +0900 Received: (qmail 29300 invoked from network); 24 Nov 2002 15:24:55 +0900 Received: from tulip.okilab.oki.co.jp (172.24.23.187) by aoi.okilab.oki.co.jp with SMTP; 24 Nov 2002 15:24:55 +0900 Received: from localhost (tulip [172.24.23.187]) by tulip.okilab.oki.co.jp (8.11.6/8.11.6) with ESMTP id gAO6Otr28880 for ; Sun, 24 Nov 2002 15:24:56 +0900 (JST) (envelope-from yamamoto436@oki.com) Date: Sun, 24 Nov 2002 15:24:55 +0900 (JST) Message-Id: <20021124.152455.74736548.yamamoto436@oki.com> To: freebsd-stable@FreeBSD.ORG Subject: Apache 2 compile error From: Hideki Yamamoto X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have met a compile problem of Apache 2.0.47 as follows. It seems that ssl.h and x509v3.h in openssl headerfile directory occures the problem, but I don't know how to solve the problem. Please give me information on this problem. Thanks in advance. ==================================================== # cd /usr/ports/www/apache2 # ls -l Makefile -rw-r--r-- 1 root wheel 4637 Nov 16 10:58 Makefile # make . . . Building shared: mod_ssl.la /bin/sh /usr/ports/www/apache2/work/httpd-2.0.43/srclib/apr/libtool --silent --m ode=compile cc -pipe -DNO_IDEA -D_REENTRANT -D_THREAD_SAFE -DAP_HAVE_DESIGNA TED_INITIALIZER -I/usr/ports/www/apache2/work/httpd-2.0.43/srclib/apr/include -I/usr/ports/www/apache2/work/httpd-2.0.43/srclib/apr-util/include -I/usr/local/ include -I. -I/usr/ports/www/apache2/work/httpd-2.0.43/os/unix -I/usr/ports/www/ apache2/work/httpd-2.0.43/server/mpm/prefork -I/usr/ports/www/apache2/work/httpd -2.0.43/modules/http -I/usr/ports/www/apache2/work/httpd-2.0.43/modules/filters -I/usr/ports/www/apache2/work/httpd-2.0.43/modules/proxy -I/usr/ports/www/apache 2/work/httpd-2.0.43/include -I/usr/include/openssl -I/usr/ports/www/apache2/work /httpd-2.0.43/modules/dav/main -c mod_ssl.c && touch mod_ssl.slo In file included from mod_ssl.h:111, from mod_ssl.c:60: /usr/include/openssl/ssl.h:1222: syntax error before `CRYPTO_EX_new' /usr/include/openssl/ssl.h:1227: syntax error before `CRYPTO_EX_new' /usr/include/openssl/ssl.h:1232: syntax error before `CRYPTO_EX_new' In file included from mod_ssl.h:125, from mod_ssl.c:60: /usr/include/openssl/x509v3.h:141: syntax error before `ENUMERATED_NAMES' /usr/include/openssl/x509v3.h:141: warning: data definition has no type or stora ge class /usr/include/openssl/x509v3.h:232: syntax error before `STACK_ASN1_INTEGER' *** Error code 1 Stop in /usr/ports/www/apache2/work/httpd-2.0.43/modules/ssl. *** Error code 1 Stop in /usr/ports/www/apache2/work/httpd-2.0.43/modules/ssl. *** Error code 1 Stop in /usr/ports/www/apache2/work/httpd-2.0.43/modules. *** Error code 1 Stop in /usr/ports/www/apache2/work/httpd-2.0.43. *** Error code 1 Stop in /usr/ports/www/apache2/work/httpd-2.0.43. *** Error code 1 Stop in /usr/ports/www/apache2. -------------------------------------------------------------- hikarigaoka# ls -l /usr/include/openssl/ssl.h -r--r--r-- 1 root wheel 64484 Sep 1 12:13 /usr/include/openssl/ssl.h hikarigaoka# ls -l /usr/include/openssl/x509v3.h -r--r--r-- 1 root wheel 23612 Sep 1 12:13 /usr/include/openssl/x509v3.h ----------------------------------------------------------------- Hideki YAMAMOTO | Broadband Media Solutions Department | E-mail: yamamoto436@oki.com Broadband Media Company | Tel: +81-3-3455-0870 Oki Electric Industry Co., Ltd. | FAX: +81-3-3798-7670 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message