From owner-freebsd-hackers Sun Oct 25 00:19:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14365 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 00:19:13 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14359 for ; Sun, 25 Oct 1998 00:19:11 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id CAA00332; Sun, 25 Oct 1998 02:18:24 -0500 (EST) Date: Sun, 25 Oct 1998 02:18:23 -0500 (EST) From: "Matthew N. Dodd" To: Greg Lehey cc: freebsd-hackers@FreeBSD.ORG Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: <19981025122928.B16609@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Oct 1998, Greg Lehey wrote: > > Talk about context switch out the ass... > > Have you tried it? I don't have any problems. I was being silly. (Though I do run systems that are slow enough to prohibit local apps; these I just X-kernel. Mind you these aren't FreeBSD boxes. (Not that my FreeBSD play boxes are any faster.)) On a sufficiently fast system, the speed loss from running local apps isn't measureable. On a DECstation 3100 it is. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 03:41:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04150 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 03:41:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04138 for ; Sun, 25 Oct 1998 03:41:17 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id DAA04210; Sun, 25 Oct 1998 03:40:45 -0800 (PST) Message-ID: <19981025034045.D21744@Alameda.net> Date: Sun, 25 Oct 1998 03:40:45 -0800 From: Ulf Zimmermann To: hackers@FreeBSD.ORG Subject: more questions Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I finaly getting somewhere. I can now read single blocks from the Mylex DAC960 PCI Raid controller. But only single blocks at a time. Can someone please point me how I tell the kernel that I can more then 1 block a time. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 05:48:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14050 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 05:48:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14045 for ; Sun, 25 Oct 1998 05:48:07 -0800 (PST) (envelope-from freebsd@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zXQW5-000IAPC; Sun, 25 Oct 1998 08:47:33 -0500 (EST) Message-Id: From: freebsd@tomqnx.com (Tom Torrance) Subject: Broken Source Tree To: hackers@FreeBSD.ORG Date: Sun, 25 Oct 1998 08:47:32 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM909323252-555-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ELM909323252-555-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I believe that I have discovered a serious problem with the source tree for 2.2.7-RELEASE and later. Someone that really understands the make world process should check me out on this - I don't pretend to understand it perfectly! Problem Summary: Changes to the /usr/share/mk makefiles are not being made, and about 20 'leaf nodes' on the source tree are not being installed properly as a result of the make world process. To list them: grep afterinstall `find /usr/src -name Makefile -print` | grep -v /lkm/ ISSUE #1: Because the 'afterinstall' target gets broken, and 'make world' etc. is forced to operate from the /usr/share/mk set of files rather that the /usr/src/share/mk set, new versions of the mk files never get installed. Proposed Solution: Remove the conditional test in /usr/src/Makefile to ensure that 'make world' 'make buildworld' and 'make installworld' use the updated mk files provided under /usr/src/share/mk. ISSUE #2: the makefiles bsd.prog.mk and bsd.lib.mk presently corrupt the target 'afterinstall' if it was previously set before those files were called. Proposed Solution: Bracket the lines that modify the 'afterinstall' target with: .if !target(afterinstall) ........... .endif in both bsd.prog.mk and bsd.lib.mk. Please copy any responses directly to my e-mail address as I am not presently receiving hackers. Thank you! Tom --ELM909323252-555-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=Makefile Content-Description: Modified /usr/src/Makefile Content-Transfer-Encoding: 7bit # # $Id: Makefile,v 1.109.2.35 1998/09/07 19:05:21 jkh Exp $ # # Make command line options: # -DCLOBBER will remove /usr/include # -DMAKE_KERBEROS4 to build KerberosIV # # -DNOCLEANDIR run ${MAKE} clean, instead of ${MAKE} cleandir # -DNOCLEAN do not clean at all # -DNOTOOLS do not rebuild any tools first # -DNOCRYPT will prevent building of crypt versions # -DNOLKM do not build loadable kernel modules # -DNOOBJDIR do not run ``${MAKE} obj'' # -DNOPROFILE do not build profiled libraries # -DNOSECURE do not go into secure subdir # -DNOGAMES do not go into games subdir # -DNOSHARE do not go into share subdir # -DNOINFO do not make or install info files # -DNOLIBC_R do not build libc_r. # -DNOPERL do not make or install perl # LOCAL_DIRS="list of dirs" to add additional dirs to the SUBDIR list # # The intended user-driven targets are: # buildworld - rebuild *everything*, including glue to help do upgrades # installworld- install everything built by "buildworld" # world - buildworld + installworld # update - convenient way to update your source tree (eg: sup/cvs) # most - build user commands, no libraries or include files # installmost - install user commands, no libraries or include files # # Standard targets (not defined here) are documented in the makefiles in # /usr/share/mk. These include: # obj depend all install clean cleandepend cleanobj #.if (!make(world)) && (!make(buildworld)) && (!make(installworld)) .MAKEFLAGS:= ${.MAKEFLAGS} -m ${.CURDIR}/share/mk #.endif # Put initial settings here. SUBDIR= # We must do share/info early so that installation of info `dir' # entries works correctly. Do it first since it is less likely to # grow dependencies on include and lib than vice versa. .if exists(share/info) SUBDIR+= share/info .endif # We must do include and lib first so that the perl *.ph generation # works correctly as it uses the header files installed by this. .if exists(include) SUBDIR+= include .endif .if exists(lib) SUBDIR+= lib .endif .if exists(bin) SUBDIR+= bin .endif .if exists(games) && !defined(NOGAMES) SUBDIR+= games .endif .if exists(gnu) SUBDIR+= gnu .endif .if exists(kerberosIV) && exists(crypto) && !defined(NOCRYPT) && defined(MAKE_KERBEROS4) SUBDIR+= kerberosIV .endif .if exists(libexec) SUBDIR+= libexec .endif .if exists(sbin) SUBDIR+= sbin .endif .if exists(share) && !defined(NOSHARE) SUBDIR+= share .endif .if exists(sys) SUBDIR+= sys .endif .if exists(usr.bin) SUBDIR+= usr.bin .endif .if exists(usr.sbin) SUBDIR+= usr.sbin .endif .if exists(secure) && !defined(NOCRYPT) && !defined(NOSECURE) SUBDIR+= secure .endif .if exists(lkm) && !defined(NOLKM) SUBDIR+= lkm .endif # etc must be last for "distribute" to work .if exists(etc) && make(distribute) SUBDIR+= etc .endif # These are last, since it is nice to at least get the base system # rebuilt before you do them. .if defined(LOCAL_DIRS) .for _DIR in ${LOCAL_DIRS} .if exists(${_DIR}) & exists(${_DIR}/Makefile) SUBDIR+= ${_DIR} .endif .endfor .endif # Handle -DNOOBJDIR, -DNOCLEAN and -DNOCLEANDIR .if defined(NOOBJDIR) OBJDIR= .else OBJDIR= obj .endif .if defined(NOCLEAN) CLEANDIR= .else .if defined(NOCLEANDIR) CLEANDIR= clean .else CLEANDIR= cleandir .endif .endif SUP?= cvsup SUPFLAGS?= -g -L 2 -P - # # While building tools for bootstrapping, we dont need to waste time on # profiled libraries or man pages. This speeds things up somewhat. # MK_FLAGS= -DNOINFO -DNOMAN -DNOPROFILE # # world # # Attempt to rebuild and reinstall *everything*, with reasonable chance of # success, regardless of how old your existing system is. # # >> Beware, it overwrites the local build environment! << # world: @echo "--------------------------------------------------------------" @echo "make world started on `LC_TIME=C date`" @echo "--------------------------------------------------------------" .if target(pre-world) @echo @echo "--------------------------------------------------------------" @echo " Making 'pre-world' target" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${MAKE} pre-world .endif cd ${.CURDIR} && ${MAKE} buildworld cd ${.CURDIR} && ${MAKE} -B installworld .if target(post-world) @echo @echo "--------------------------------------------------------------" @echo " Making 'post-world' target" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${MAKE} post-world .endif @echo @echo "--------------------------------------------------------------" @echo "make world completed on `LC_TIME=C date`" @echo "--------------------------------------------------------------" .if defined(MAKEOBJDIRPREFIX) WORLDTMP= ${MAKEOBJDIRPREFIX}${.CURDIR}/tmp .else WORLDTMP= /usr/obj${.CURDIR}/tmp .endif STRICTTMPPATH= ${WORLDTMP}/sbin:${WORLDTMP}/usr/sbin:${WORLDTMP}/bin:${WORLDTMP}/usr/bin TMPPATH= ${STRICTTMPPATH}:${PATH} # XXX COMPILER_PATH is needed for finding cc1, ld and as # XXX GCC_EXEC_PREFIX is for *crt.o. It is probably unnecssary now # tbat LIBRARY_PATH is set. We still can't use -nostdlib, since gcc # wouldn't link *crt.o or libgcc if it were used. # XXX LD_LIBRARY_PATH is for ld.so. It is also used by ld, although we don't # want that - all compile-time library paths should be resolved by gcc. # It fails for set[ug]id executables (are any used?). COMPILER_ENV= BISON_SIMPLE=${WORLDTMP}/usr/share/misc/bison.simple \ COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \ GCC_EXEC_PREFIX=${WORLDTMP}/usr/lib/ \ LD_LIBRARY_PATH=${WORLDTMP}${SHLIBDIR} \ LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib BMAKEENV= PATH=${TMPPATH} ${COMPILER_ENV} NOEXTRADEPEND=t XMAKEENV= PATH=${STRICTTMPPATH} ${COMPILER_ENV} \ CC='cc -nostdinc' # XXX -nostdlib # used to compile and install 'make' in temporary build tree IBMAKE= ${BMAKEENV} ${MAKE} DESTDIR=${WORLDTMP} # bootstrap make BMAKE= ${BMAKEENV} ${WORLDTMP}/usr/bin/${MAKE} DESTDIR=${WORLDTMP} # cross make used for compilation XMAKE= ${XMAKEENV} ${WORLDTMP}/usr/bin/${MAKE} DESTDIR=${WORLDTMP} # cross make used for final installation IXMAKE= ${XMAKEENV} ${WORLDTMP}/usr/bin/${MAKE} # # buildworld # # Attempt to rebuild the entire system, with reasonable chance of # success, regardless of how old your existing system is. # buildworld: .if !defined(NOCLEAN) @echo @echo "--------------------------------------------------------------" @echo " Cleaning up the temporary build tree" @echo "--------------------------------------------------------------" mkdir -p ${WORLDTMP} chflags -R noschg ${WORLDTMP}/ rm -rf ${WORLDTMP} .endif .if !defined(NOTOOLS) @echo @echo "--------------------------------------------------------------" @echo " Making make" @echo "--------------------------------------------------------------" mkdir -p ${WORLDTMP}/usr/bin .if !defined(NOCLEAN) || !defined(NOOBJDIR) cd ${.CURDIR}/usr.bin/make && \ ${IBMAKE} -I${.CURDIR}/share/mk ${CLEANDIR} ${OBJDIR} .endif cd ${.CURDIR}/usr.bin/make && \ ${IBMAKE} -I${.CURDIR}/share/mk depend && \ ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} all && \ ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} install && \ ${IBMAKE} -I${.CURDIR}/share/mk ${MK_FLAGS} clean cleandepend .endif @echo @echo "--------------------------------------------------------------" @echo " Making hierarchy" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} hierarchy .if !defined(NOCLEAN) @echo @echo "--------------------------------------------------------------" @echo " Cleaning up the obj tree" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} par-${CLEANDIR} .endif .if !defined(NOOBJDIR) @echo @echo "--------------------------------------------------------------" @echo " Rebuilding the obj tree" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} par-obj .endif .if !defined(NOTOOLS) @echo @echo "--------------------------------------------------------------" @echo " Rebuilding bootstrap tools" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} bootstrap @echo @echo "--------------------------------------------------------------" @echo " Rebuilding tools necessary to build the include files" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} include-tools .endif @echo @echo "--------------------------------------------------------------" @echo " Rebuilding /usr/include" @echo "--------------------------------------------------------------" cd ${.CURDIR} && SHARED=symlinks ${BMAKE} includes .if !defined(NOTOOLS) @echo @echo "--------------------------------------------------------------" @echo " Rebuilding tools needed to build the libraries" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} lib-tools .endif @echo @echo "--------------------------------------------------------------" @echo " Rebuilding /usr/lib" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} libraries .if !defined(NOTOOLS) @echo @echo "--------------------------------------------------------------" @echo " Rebuilding all other tools needed to build the world" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${BMAKE} build-tools .endif @echo @echo "--------------------------------------------------------------" @echo " Rebuilding dependencies" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${XMAKE} ${.MAKEFLAGS} par-depend @echo @echo "--------------------------------------------------------------" @echo " Building everything.." @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${XMAKE} all # # installworld # # Installs everything compiled by a 'buildworld'. # installworld: cd ${.CURDIR} && ${IXMAKE} reinstall # # reinstall # # If you have a build server, you can NFS mount the source and obj directories # and do a 'make reinstall' on the *client* to install new binaries from the # most recent server build. # reinstall: @echo "--------------------------------------------------------------" @echo " Making hierarchy" @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${MAKE} hierarchy @echo @echo "--------------------------------------------------------------" @echo " Installing everything.." @echo "--------------------------------------------------------------" cd ${.CURDIR} && ${MAKE} install @echo @echo "--------------------------------------------------------------" @echo " Re-scanning the shared libraries.." @echo "--------------------------------------------------------------" cd ${.CURDIR} && ldconfig -R @echo @echo "--------------------------------------------------------------" @echo " Rebuilding man page indexes" @echo "--------------------------------------------------------------" cd ${.CURDIR}/share/man && ${MAKE} makedb # # update # # Update the source tree, by running sup and/or running cvs to update to the # latest copy. # update: .if defined(SUP_UPDATE) @echo "--------------------------------------------------------------" @echo "Running ${SUP}" @echo "--------------------------------------------------------------" @${SUP} ${SUPFLAGS} ${SUPFILE} .if defined(SUPFILE1) @${SUP} ${SUPFLAGS} ${SUPFILE1} .endif .if defined(SUPFILE2) @${SUP} ${SUPFLAGS} ${SUPFILE2} .endif .endif .if defined(CVS_UPDATE) @echo "--------------------------------------------------------------" @echo "Updating /usr/src from cvs repository" ${CVSROOT} @echo "--------------------------------------------------------------" cd ${.CURDIR} && cvs -q update -P -d -r RELENG_2_2 .endif # # most # # Build most of the user binaries on the existing system libs and includes. # most: @echo "--------------------------------------------------------------" @echo " Building programs only" @echo "--------------------------------------------------------------" cd ${.CURDIR}/bin && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/sbin && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/libexec && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/usr.bin && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/usr.sbin && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/gnu/libexec && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/gnu/usr.bin && ${MAKE} ${.MAKEFLAGS} all cd ${.CURDIR}/gnu/usr.sbin && ${MAKE} ${.MAKEFLAGS} all #.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) # cd ${.CURDIR}/kerberosIV && ${MAKE} ${.MAKEFLAGS} most #.endif #.if !defined(NOSECURE) && !defined(NOCRYPT) # cd ${.CURDIR}/secure && ${MAKE} ${.MAKEFLAGS} most #.endif # # installmost # # Install the binaries built by the 'most' target. This does not include # libraries or include files. # installmost: @echo "--------------------------------------------------------------" @echo " Installing programs only" @echo "--------------------------------------------------------------" cd ${.CURDIR}/bin && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/sbin && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/libexec && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/usr.bin && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/usr.sbin && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/gnu/libexec && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/gnu/usr.bin && ${MAKE} ${.MAKEFLAGS} install cd ${.CURDIR}/gnu/usr.sbin && ${MAKE} ${.MAKEFLAGS} install #.if defined(MAKE_KERBEROS4) && !defined(NOCRYPT) # cd ${.CURDIR}/kerberos4 && ${MAKE} ${.MAKEFLAGS} installmost #.endif #.if !defined(NOSECURE) && !defined(NOCRYPT) # cd ${.CURDIR}/secure && ${MAKE} ${.MAKEFLAGS} installmost #.endif # # ------------------------------------------------------------------------ # # From here onwards are utility targets used by the 'make world' and # related targets. If your 'world' breaks, you may like to try to fix # the problem and manually run the following targets to attempt to # complete the build. Beware, this is *not* guaranteed to work, you # need to have a pretty good grip on the current state of the system # to attempt to manually finish it. If in doubt, 'make world' again. # # # heirarchy - ensure that all the needed directories are present # hierarchy: cd ${.CURDIR}/etc && ${MAKE} distrib-dirs # # bootstrap - [re]build tools needed to run the actual build, this includes # tools needed by 'make depend', as some tools are needed to generate source # for the dependency information to be gathered from. # bootstrap: .if defined(DESTDIR) rm -f ${DESTDIR}/usr/src/sys ln -s ${.CURDIR}/sys ${DESTDIR}/usr/src cd ${.CURDIR}/include && find -dx . | cpio -dump ${DESTDIR}/usr/include cd ${.CURDIR}/include && make symlinks .endif cd ${.CURDIR}/usr.bin/make && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/xinstall && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} cd ${.CURDIR}/usr.bin/lex && ${MAKE} bootstrap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} -DNOLIB all && \ ${MAKE} ${MK_FLAGS} -DNOLIB -B install ${CLEANDIR} .if !defined(NOOBJDIR) cd ${.CURDIR}/usr.bin/lex && ${MAKE} obj .endif # # include-tools - generally the same as 'bootstrap', except that it's for # things that are specifically needed to generate include files. # # XXX should be merged with bootstrap, it's not worth keeeping them separate. # Well, maybe it is now. We force 'cleandepend' here to avoid dependencies # on cleaned away headers in ${WORLDTMP}. # include-tools: cd ${.CURDIR}/usr.bin/rpcgen && ${MAKE} -B cleandepend depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} # # includes - possibly generate and install the include files. # includes: .if defined(CLOBBER) rm -rf ${DESTDIR}/usr/include/* mtree -deU -f ${.CURDIR}/etc/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/include .endif cd ${.CURDIR}/include && ${MAKE} -B all install cd ${.CURDIR}/gnu/include && ${MAKE} install cd ${.CURDIR}/gnu/lib/libreadline && ${MAKE} beforeinstall cd ${.CURDIR}/gnu/lib/libregex && ${MAKE} beforeinstall cd ${.CURDIR}/gnu/lib/libstdc++ && ${MAKE} beforeinstall cd ${.CURDIR}/gnu/lib/libg++ && ${MAKE} beforeinstall cd ${.CURDIR}/gnu/lib/libdialog && ${MAKE} beforeinstall .if exists(kerberosIV) && !defined(NOCRYPT) && defined(MAKE_KERBEROS4) cd ${.CURDIR}/kerberosIV/lib/libacl && ${MAKE} beforeinstall cd ${.CURDIR}/kerberosIV/lib/libkadm && ${MAKE} beforeinstall cd ${.CURDIR}/kerberosIV/lib/libkafs && ${MAKE} beforeinstall cd ${.CURDIR}/kerberosIV/lib/libkdb && ${MAKE} beforeinstall cd ${.CURDIR}/kerberosIV/lib/libkrb && ${MAKE} beforeinstall cd ${.CURDIR}/kerberosIV/lib/libtelnet && ${MAKE} beforeinstall .else cd ${.CURDIR}/lib/libtelnet && ${MAKE} beforeinstall .endif cd ${.CURDIR}/lib/csu/i386 && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libalias && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libc && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libcurses && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libedit && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libftpio && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libmd && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libmytinfo && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libncurses && ${MAKE} beforeinstall .if !defined(WANT_CSRG_LIBM) cd ${.CURDIR}/lib/msun && ${MAKE} beforeinstall .endif cd ${.CURDIR}/lib/libpcap && ${MAKE} beforeinstall cd ${.CURDIR}/lib/librpcsvc && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libskey && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libtermcap && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libcom_err && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libss && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libscsi && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libutil && ${MAKE} beforeinstall cd ${.CURDIR}/lib/libz && ${MAKE} beforeinstall # # lib-tools - build tools to compile and install the libraries. # # XXX gperf is required for cc # XXX a new ld and tsort is required for cc lib-tools: .for d in \ gnu/usr.bin/gperf \ gnu/usr.bin/ld \ usr.bin/tsort \ gnu/usr.bin/as \ gnu/usr.bin/bison \ gnu/usr.bin/awk \ usr.bin/ar \ usr.bin/compile_et \ usr.bin/lex/lib \ usr.bin/mk_cmds \ usr.bin/nm \ usr.bin/ranlib \ usr.bin/uudecode \ gnu/usr.bin/cc cd ${.CURDIR}/$d && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endfor # # libraries - build and install the libraries # libraries: .if exists(lib/csu/i386) cd ${.CURDIR}/lib/csu/i386 && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libcompat) cd ${.CURDIR}/lib/libcompat && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libc) cd ${.CURDIR}/lib/libc && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libmytinfo) cd ${.CURDIR}/lib/libmytinfo && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libncurses) cd ${.CURDIR}/lib/libncurses && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib/libtermcap) cd ${.CURDIR}/lib/libtermcap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(gnu) cd ${.CURDIR}/gnu/lib && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(secure) && !defined(NOCRYPT) && !defined(NOSECURE) cd ${.CURDIR}/secure/lib && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(lib) cd ${.CURDIR}/lib && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(usr.bin/lex/lib) cd ${.CURDIR}/usr.bin/lex/lib && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(kerberosIV) && exists(crypto) && !defined(NOCRYPT) && defined(MAKE_KERBEROS4) cd ${.CURDIR}/kerberosIV/lib && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif .if exists(usr.sbin/pcvt/keycap) cd ${.CURDIR}/usr.sbin/pcvt/keycap && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endif # Exclude perl from the build-tools if NOPERL is defined. .if defined(NOPERL) _perl= .else _perl= gnu/usr.bin/perl/perl .endif # # build-tools - build and install any other tools needed to complete the # compile and install. # ifdef stale # bc and cpp are required to build groff. Otherwise, the order here is # mostly historical, i.e., bogus. # chmod is used to build gcc's tmpmultilib[2] at obscure times. # endif stale # XXX uname is a bug - the target should not depend on the host. # build-tools: .for d in \ bin/cat \ bin/chmod \ bin/cp \ bin/date \ bin/dd \ bin/echo \ usr.bin/yacc \ bin/expr \ bin/hostname \ bin/ln \ bin/ls \ bin/mkdir \ bin/mv \ bin/rm \ bin/test \ gnu/usr.bin/bc \ gnu/usr.bin/grep \ gnu/usr.bin/groff \ gnu/usr.bin/gzip \ gnu/usr.bin/man/makewhatis \ gnu/usr.bin/patch \ ${_perl} \ gnu/usr.bin/sort \ gnu/usr.bin/texinfo \ usr.bin/basename \ usr.bin/cap_mkdb \ usr.bin/chflags \ usr.bin/cmp \ usr.bin/col \ usr.bin/cpp \ usr.bin/expand \ usr.bin/file2c \ usr.bin/find \ usr.bin/gencat \ usr.bin/id \ usr.bin/lorder \ usr.bin/m4 \ usr.bin/mkdep \ usr.bin/paste \ usr.bin/sed \ usr.bin/size \ usr.bin/soelim \ usr.bin/strip \ usr.bin/symorder \ usr.bin/touch \ usr.bin/tr \ usr.bin/true \ usr.bin/uname \ usr.bin/uuencode \ usr.bin/vgrind \ usr.bin/vi \ usr.bin/wc \ usr.sbin/chown \ usr.sbin/mtree \ usr.sbin/zic \ bin/sh cd ${.CURDIR}/$d && ${MAKE} depend && \ ${MAKE} ${MK_FLAGS} all && \ ${MAKE} ${MK_FLAGS} -B install ${CLEANDIR} ${OBJDIR} .endfor .for __target in clean cleandir obj depend .for entry in ${SUBDIR} ${entry}.${__target}__D: .PHONY if test -d ${.CURDIR}/${entry}.${MACHINE}; then \ ${ECHODIR} "===> ${DIRPRFX}${entry}.${MACHINE}"; \ edir=${entry}.${MACHINE}; \ cd ${.CURDIR}/$${edir}; \ else \ ${ECHODIR} "===> ${DIRPRFX}${entry}"; \ edir=${entry}; \ cd ${.CURDIR}/$${edir}; \ fi; \ ${MAKE} ${__target} DIRPRFX=${DIRPRFX}$${edir}/ .endfor par-${__target}: ${SUBDIR:S/$/.${__target}__D/} .endfor .include --ELM909323252-555-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=bsd.prog.mk Content-Description: Modified /usr/src/share/mk/bsd.prog.mk Content-Transfer-Encoding: 7bit # from: @(#)bsd.prog.mk 5.26 (Berkeley) 6/25/91 # $Id: bsd.prog.mk,v 1.41.2.7 1998/06/14 16:10:49 steve Exp $ .if exists(${.CURDIR}/../Makefile.inc) .include "${.CURDIR}/../Makefile.inc" .endif .SUFFIXES: .out .o .c .cc .cpp .cxx .C .y .l .s .S CFLAGS+=${COPTS} ${DEBUG_FLAGS} .if defined(DESTDIR) CFLAGS+= -I${DESTDIR}/usr/include CXXINCLUDES+= -I${DESTDIR}/usr/include/g++ .endif .if !defined(DEBUG_FLAGS) STRIP?= -s .endif .if defined(NOSHARED) && ( ${NOSHARED} != "no" && ${NOSHARED} != "NO" ) LDFLAGS+= -static .endif .include .if defined(PROG) .if defined(SRCS) DPSRCS+= ${SRCS:M*.h} .if !defined(NOOBJ) OBJS+= ${SRCS:N*.h:R:S/$/.o/g} .endif .if defined(LDONLY) ${PROG}: ${LIBCRT0} ${LIBC} ${DPSRCS} ${OBJS} ${DPADD} ${LD} ${LDFLAGS} -o ${.TARGET} ${LIBCRT0} ${OBJS} ${LIBC} ${LDDESTDIR} \ ${LDADD} .else defined(LDONLY) ${PROG}: ${DPSRCS} ${OBJS} ${LIBC} ${DPADD} ${CC} ${CFLAGS} ${LDFLAGS} -o ${.TARGET} ${OBJS} ${LDDESTDIR} ${LDADD} .endif .else !defined(SRCS) SRCS= ${PROG}.c .if 0 ${PROG}: ${DPSRCS} ${SRCS} ${LIBC} ${DPADD} ${CC} ${LDFLAGS} ${CFLAGS} -o ${.TARGET} ${.CURDIR}/${SRCS} \ ${LDDESTDIR} ${LDADD} MKDEP= -p .else # Always make an intermediate object file because: # - it saves time rebuilding when only the library has changed # - the name of the object gets put into the executable symbol table instead of # the name of a variable temporary object. # - it's useful to keep objects around for crunching. OBJS= ${PROG}.o ${PROG}: ${DPSRCS} ${OBJS} ${LIBC} ${DPADD} ${CC} ${CFLAGS} ${LDFLAGS} -o ${.TARGET} ${OBJS} ${LDDESTDIR} ${LDADD} .endif .endif .if !defined(MAN1) && !defined(MAN2) && !defined(MAN3) && \ !defined(MAN4) && !defined(MAN5) && !defined(MAN6) && \ !defined(MAN7) && !defined(MAN8) && !defined(NOMAN) MAN1= ${PROG}.1 .endif .endif # XXX I think MANDEPEND is only used for groff. It should be named more # generally and perhaps not be in the maninstall dependencies now it is # here (or does maninstall always work when nothing is made?), .MAIN: all all: objwarn ${PROG} all-man _SUBDIR .if !target(clean) clean: _SUBDIR rm -f a.out Errs errs mklog ${PROG} ${OBJS} ${CLEANFILES} .if defined(CLEANDIRS) && !empty(CLEANDIRS) rm -rf ${CLEANDIRS} .endif .endif .if !target(install) .if !target(beforeinstall) beforeinstall: .endif realinstall: beforeinstall .if defined(PROG) ${INSTALL} ${COPY} ${STRIP} -o ${BINOWN} -g ${BINGRP} -m ${BINMODE} \ ${INSTALLFLAGS} ${PROG} ${DESTDIR}${BINDIR} .endif .if defined(HIDEGAME) (cd ${DESTDIR}/usr/games; rm -f ${PROG}; ln -s dm ${PROG}; \ chown games:bin ${PROG}) .endif .if defined(LINKS) && !empty(LINKS) @set ${LINKS}; \ while test $$# -ge 2; do \ l=${DESTDIR}$$1; \ shift; \ t=${DESTDIR}$$1; \ shift; \ ${ECHO} $$t -\> $$l; \ rm -f $$t; \ ln ${LN_FLAGS} $$l $$t; \ done; true .endif install: afterinstall _SUBDIR .if !target(afterinstall) .if !defined(NOMAN) afterinstall: realinstall maninstall .else afterinstall: realinstall .endif .endif .endif DISTRIBUTION?= bin .if !target(distribute) distribute: _SUBDIR .for dist in ${DISTRIBUTION} cd ${.CURDIR} ; $(MAKE) install DESTDIR=${DISTDIR}/${dist} SHARED=copies .endfor .endif .if !target(lint) lint: ${SRCS} _SUBDIR .if defined(PROG) @${LINT} ${LINTFLAGS} ${CFLAGS} ${.ALLSRC} | more 2>&1 .endif .endif .if defined(NOTAGS) tags: .endif .if !target(tags) tags: ${SRCS} _SUBDIR .if defined(PROG) @cd ${.CURDIR} && gtags ${GTAGSFLAGS} .if defined(HTML) @cd ${.CURDIR} && htags ${HTAGSFLAGS} .endif .endif .endif .if !defined(NOMAN) .include .elif !target(maninstall) maninstall: all-man: .endif .include .include --ELM909323252-555-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=bsd.lib.mk Content-Description: Modified /usr/src/share/mk/bsd.lib.mk Content-Transfer-Encoding: 7bit # from: @(#)bsd.lib.mk 5.26 (Berkeley) 5/2/91 # $Id: bsd.lib.mk,v 1.46.2.9 1998/06/14 16:10:48 steve Exp $ # .if exists(${.CURDIR}/../Makefile.inc) .include "${.CURDIR}/../Makefile.inc" .endif .if exists(${.CURDIR}/shlib_version) SHLIB_MAJOR != . ${.CURDIR}/shlib_version ; echo $$major SHLIB_MINOR != . ${.CURDIR}/shlib_version ; echo $$minor .endif .if defined(DESTDIR) CFLAGS+= -I${DESTDIR}/usr/include CXXINCLUDES+= -I${DESTDIR}/usr/include/g++ .endif .if defined(DEBUG_FLAGS) CFLAGS+= ${DEBUG_FLAGS} .endif .if !defined(DEBUG_FLAGS) STRIP?= -s .endif .include .MAIN: all # prefer .s to a .c, add .po, remove stuff not used in the BSD libraries # .so used for PIC object files .SUFFIXES: .SUFFIXES: .out .o .po .so .s .S .c .cc .cpp .cxx .m .C .f .y .l .c.o: ${CC} ${CFLAGS} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .c.po: ${CC} -pg ${CFLAGS} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -X -r ${.TARGET} .c.so: ${CC} ${PICFLAG} -DPIC ${CFLAGS} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .cc.o .C.o .cpp.o .cxx.o: ${CXX} ${CXXFLAGS} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .cc.po .C.po .cpp.po .cxx.po: ${CXX} -pg ${CXXFLAGS} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -X -r ${.TARGET} .cc.so .C.so .cpp.so .cxx.so: ${CXX} ${PICFLAG} -DPIC ${CXXFLAGS} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .f.o: ${FC} ${FFLAGS} -o ${.TARGET} -c ${.IMPSRC} @${LD} -O ${.TARGET} -x -r ${.TARGET} .f.po: ${FC} -pg ${FFLAGS} -o ${.TARGET} -c ${.IMPSRC} @${LD} -O ${.TARGET} -X -r ${.TARGET} .f.so: ${FC} ${PICFLAG} -DPIC ${FFLAGS} -o ${.TARGET} -c ${.IMPSRC} @${LD} -O ${.TARGET} -x -r ${.TARGET} .s.o: ${CC} -x assembler-with-cpp ${CFLAGS:M-[BID]*} ${AINC} -c \ ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .s.po: ${CC} -x assembler-with-cpp -DPROF ${CFLAGS:M-[BID]*} ${AINC} -c \ ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -X -r ${.TARGET} .s.so: ${CC} -x assembler-with-cpp -fpic -DPIC ${CFLAGS:M-[BID]*} ${AINC} -c \ ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .S.o: ${CC} ${CFLAGS:M-[BID]*} ${AINC} -c ${.IMPSRC} -o ${.TARGET} .S.po: ${CC} -DPROF ${CFLAGS:M-[BID]*} ${AINC} -c ${.IMPSRC} -o ${.TARGET} .S.so: ${CC} -fpic -DPIC ${CFLAGS:M-[BID]*} ${AINC} -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -x -r ${.TARGET} .m.po: ${CC} ${CFLAGS} -fgnu-runtime -pg -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -X -r ${.TARGET} .m.o: ${CC} ${CFLAGS} -fgnu-runtime -c ${.IMPSRC} -o ${.TARGET} @${LD} -O ${.TARGET} -X -r ${.TARGET} .if !defined(INTERNALLIB) || defined(INTERNALSTATICLIB) .if !defined(NOPROFILE) && !defined(INTERNALLIB) _LIBS=lib${LIB}.a lib${LIB}_p.a .else _LIBS=lib${LIB}.a .endif .endif .if !defined(NOPIC) .if defined(SHLIB_MAJOR) && defined(SHLIB_MINOR) _LIBS+=lib${LIB}.so.${SHLIB_MAJOR}.${SHLIB_MINOR} .endif .if defined(INSTALL_PIC_ARCHIVE) _LIBS+=lib${LIB}_pic.a .endif .endif .if !defined(PICFLAG) PICFLAG=-fpic .endif all: objwarn ${_LIBS} all-man _SUBDIR # llib-l${LIB}.ln OBJS+= ${SRCS:N*.h:R:S/$/.o/g} lib${LIB}.a:: ${OBJS} @${ECHO} building standard ${LIB} library @rm -f lib${LIB}.a @${AR} cq lib${LIB}.a `lorder ${OBJS} | tsort -q` ${ARADD} ${RANLIB} lib${LIB}.a .if !defined(NOPROFILE) POBJS+= ${OBJS:.o=.po} lib${LIB}_p.a:: ${POBJS} @${ECHO} building profiled ${LIB} library @rm -f lib${LIB}_p.a @${AR} cq lib${LIB}_p.a `lorder ${POBJS} | tsort -q` ${ARADD} ${RANLIB} lib${LIB}_p.a .endif .if defined(DESTDIR) LDDESTDIRENV?= LIBRARY_PATH=${DESTDIR}${SHLIBDIR}:${DESTDIR}/usr/lib .endif .if !defined(NOPIC) SOBJS+= ${OBJS:.o=.so} lib${LIB}.so.${SHLIB_MAJOR}.${SHLIB_MINOR}: ${SOBJS} @${ECHO} building shared ${LIB} library \(version ${SHLIB_MAJOR}.${SHLIB_MINOR}\) @rm -f lib${LIB}.so.${SHLIB_MAJOR}.${SHLIB_MINOR} @${LDDESTDIRENV} ${CC} -shared -Wl,-x \ -o lib${LIB}.so.${SHLIB_MAJOR}.${SHLIB_MINOR} \ `lorder ${SOBJS} | tsort -q` ${LDDESTDIR} ${LDADD} lib${LIB}_pic.a:: ${SOBJS} @${ECHO} building special pic ${LIB} library @rm -f lib${LIB}_pic.a @${AR} cq lib${LIB}_pic.a ${SOBJS} ${ARADD} ${RANLIB} lib${LIB}_pic.a .endif llib-l${LIB}.ln: ${SRCS} ${LINT} -C${LIB} ${CFLAGS} ${.ALLSRC:M*.c} .if !target(clean) clean: _SUBDIR rm -f a.out Errs errs mklog ${CLEANFILES} ${OBJS} rm -f lib${LIB}.a llib-l${LIB}.ln rm -f ${POBJS} profiled/*.o lib${LIB}_p.a rm -f ${SOBJS} shared/*.o rm -f lib${LIB}.so.*.* lib${LIB}_pic.a .if defined(CLEANDIRS) && !empty(CLEANDIRS) rm -rf ${CLEANDIRS} .endif .endif .if defined(SRCS) afterdepend: @(TMP=_depend$$$$; \ sed -e 's/^\([^\.]*\).o[ ]*:/\1.o \1.po \1.so:/' < .depend > $$TMP; \ mv $$TMP .depend) .endif .if !target(install) .if !target(beforeinstall) beforeinstall: .endif .if defined(PRECIOUSLIB) SHLINSTALLFLAGS+= -fschg .endif realinstall: beforeinstall .if !defined(INTERNALLIB) ${INSTALL} ${COPY} -o ${LIBOWN} -g ${LIBGRP} -m ${LIBMODE} \ ${INSTALLFLAGS} lib${LIB}.a ${DESTDIR}${LIBDIR} .if !defined(NOPROFILE) ${INSTALL} ${COPY} -o ${LIBOWN} -g ${LIBGRP} -m ${LIBMODE} \ ${INSTALLFLAGS} lib${LIB}_p.a ${DESTDIR}${LIBDIR} .endif .endif .if !defined(NOPIC) .if defined(SHLIB_MAJOR) && defined(SHLIB_MINOR) ${INSTALL} ${COPY} -o ${LIBOWN} -g ${LIBGRP} -m ${LIBMODE} \ ${INSTALLFLAGS} ${SHLINSTALLFLAGS} \ lib${LIB}.so.${SHLIB_MAJOR}.${SHLIB_MINOR} \ ${DESTDIR}${SHLIBDIR} .endif .if defined(INSTALL_PIC_ARCHIVE) ${INSTALL} ${COPY} -o ${LIBOWN} -g ${LIBGRP} -m ${LIBMODE} \ ${INSTALLFLAGS} lib${LIB}_pic.a ${DESTDIR}${LIBDIR} .endif .endif .if defined(LINKS) && !empty(LINKS) @set ${LINKS}; \ while test $$# -ge 2; do \ l=${DESTDIR}$$1; \ shift; \ t=${DESTDIR}$$1; \ shift; \ ${ECHO} $$t -\> $$l; \ rm -f $$t; \ ln ${LN_FLAGS} $$l $$t; \ done; true .endif install: afterinstall _SUBDIR .if !target(afterinstall) .if !defined(NOMAN) afterinstall: realinstall maninstall .else afterinstall: realinstall .endif .endif .endif DISTRIBUTION?= bin .if !target(distribute) distribute: _SUBDIR .for dist in ${DISTRIBUTION} cd ${.CURDIR} ; $(MAKE) install DESTDIR=${DISTDIR}/${dist} SHARED=copies .endfor .endif .if !target(lint) lint: .endif .if defined(NOTAGS) tags: .endif .if !target(tags) tags: ${SRCS} _SUBDIR @cd ${.CURDIR} && gtags ${GTAGSFLAGS} .if defined(HTML) @cd ${.CURDIR} && htags ${HTAGSFLAGS} .endif .endif .if !defined(NOMAN) .include .elif !target(maninstall) maninstall: all-man: .endif .include .include --ELM909323252-555-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 07:42:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21982 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 07:42:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21963 for ; Sun, 25 Oct 1998 07:42:08 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id QAA06975 for ; Sun, 25 Oct 1998 16:30:22 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1b4) id kwa06973; Sun Oct 25 16:30:07 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id QAA00420 for ; Sun, 25 Oct 1998 16:38:53 +0100 Original: Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id QAA06431 for freebsd-hackers@freebsd.org; Sun, 25 Oct 1998 16:42:32 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199810251542.QAA06431@borg.kryptokom.de> Subject: fxp 10/100 and device timeouts To: freebsd-hackers@FreeBSD.ORG Date: Sun, 25 Oct 1998 16:42:32 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ... I am doing some througput tests and I'm running into some problems with the Intel ether express 10/100B cards. I am using ttcp with udp packets and using different packet sizes. The connections are 100MB full-duplex connections with x-over cables. The setup is as follows. PII400(fxp) ------ PII400(2x fxp) ------- PII300(fxp) I am using the PII400 in the middle as a bridge (drawbridge code) and it's running 2.2.7-STABLE ... the version of the fxp driver is 1.21.2.14 ... The following seems to happen .... When transmitting data from both sides through the machine in the middle and using packet sizes less than 256 bytes, I start to get device timeout messages. When doing the same transmit from only the one side ... there is no problems. Sometimes I get up to 4 device timeouts when transferring 32MB of data with these small packets. The error occurs on both the fxp devices (fxp0 and fxp1). I also tried to use a 2.2.6-RELEASE installation, but the same thing happens. Any ideas ? Thanx Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 08:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25076 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 08:37:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25071 for ; Sun, 25 Oct 1998 08:37:17 -0800 (PST) (envelope-from Reinier.Bezuidenhout@KryptoKom.DE) Received: (from mail@localhost) by Thingol.KryptoKom.DE (8.8.7/8.8.4) id RAA07016 for ; Sun, 25 Oct 1998 17:25:32 +0100 Received: from cirdan.kryptokom.de by via smtpp (Version 1.1.1b4) id kwa07014; Sun Oct 25 17:25:11 1998 Received: by Cirdan.KryptoKom.DE (8.8.5/8.8.5) with ESMTP id RAA00453 for ; Sun, 25 Oct 1998 17:33:58 +0100 Original: Received: (from bez@localhost) by borg.kryptokom.de (8.8.8/8.8.8) id RAA06512 for freebsd-hackers@freebsd.org; Sun, 25 Oct 1998 17:37:38 +0100 (CET) (envelope-from bez) From: Reinier Bezuidenhout Message-Id: <199810251637.RAA06512@borg.kryptokom.de> Subject: fxp 10/100B timeout - more info To: freebsd-hackers@FreeBSD.ORG Date: Sun, 25 Oct 1998 17:37:37 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have tried the same test with two DLINK cards (de) and did not get the deive timeouts ... the resulting throughput is also almost double that of the fxp with 128 byte packets. There is also no interface queue fulls being counted by the drawbridge software with the DLINK 3C905 cards while the interface queue fulls are very high with the fxp cards Bye Reinier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 08:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25929 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 08:50:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25924 for ; Sun, 25 Oct 1998 08:50:48 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA21849; Sun, 25 Oct 1998 08:51:09 -0800 (PST) Message-Id: <199810251651.IAA21849@implode.root.com> To: Reinier Bezuidenhout cc: freebsd-hackers@FreeBSD.ORG Subject: Re: fxp 10/100 and device timeouts In-reply-to: Your message of "Sun, 25 Oct 1998 16:42:32 +0100." <199810251542.QAA06431@borg.kryptokom.de> From: David Greenman Reply-To: dg@root.com Date: Sun, 25 Oct 1998 08:51:09 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I am doing some througput tests and I'm running into some problems >with the Intel ether express 10/100B cards. > >I am using ttcp with udp packets and using different packet sizes. The >connections are 100MB full-duplex connections with x-over cables. The >setup is as follows. Don't use cross-over cables. This was a known problem early on and Intel's official response when I asked them about it was "cross-over cables aren't supported with the Pro/100B cards". I suspect there is some bit of PHY programming that needs to be done that isn't happening, but that's just a guess. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 09:32:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28649 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 09:32:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA28644 for ; Sun, 25 Oct 1998 09:32:42 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 21375 invoked by uid 1001); 25 Oct 1998 17:32:07 +0000 (GMT) To: dg@root.com Cc: Reinier.Bezuidenhout@KryptoKom.DE, freebsd-hackers@FreeBSD.ORG Subject: Re: fxp 10/100 and device timeouts In-Reply-To: Your message of "Sun, 25 Oct 1998 08:51:09 -0800" References: <199810251651.IAA21849@implode.root.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 25 Oct 1998 18:32:07 +0100 Message-ID: <21371.909336727@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Don't use cross-over cables. This was a known problem early on and Intel's > official response when I asked them about it was "cross-over cables aren't > supported with the Pro/100B cards". On the other hand, a cross-over cable works just fine between a Pro/100B and a 21140 based card. Different PHYs, of course. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 11:04:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05621 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 11:04:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05616 for ; Sun, 25 Oct 1998 11:04:47 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id LAA15821 for ; Sun, 25 Oct 1998 11:04:13 -0800 (PST) (envelope-from jdp) Message-Id: <199810251904.LAA15821@austin.polstra.com> To: hackers@FreeBSD.ORG Subject: Re: Best upgrade path to 3.0 In-Reply-To: <199810242128.OAA03190@dingo.cdrom.com> References: <199810242128.OAA03190@dingo.cdrom.com> Organization: Polstra & Co., Seattle, WA Date: Sun, 25 Oct 1998 11:04:13 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > All release tags have the form RELENG_x_x_x_RELEASE, where the x's are > the three version digits. There is no tag for 2.2.8 as it hasn't > happened yet. You can follow the tree up to (and past) 2.2.8 using the > RELENG_2_2 branch tag. Also, for reference, there's a list of commonly used tags in the CVSup tutorial in the FreeBSD Handbook. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 15:35:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28477 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 15:35:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28464 for ; Sun, 25 Oct 1998 15:35:30 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id RAA27043; Sun, 25 Oct 1998 17:55:23 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id RAA01596; Sun, 25 Oct 1998 17:55:31 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810251755.RAA01596@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Keith Stevenson cc: Brian Somers , freebsd-hackers@FreeBSD.ORG Subject: Re: Ppp improvements for dynamic IPs In-reply-to: Your message of "Sat, 24 Oct 1998 14:47:53 EDT." <19981024144753.A24415@homer.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Oct 1998 17:55:31 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the report. I have no plans to put it into -stable. The stuff in -stable is from before the ppp rewrite, and we're not supposed to add new features to the -stable branch. Anyone that wants the latest ppp can get it from my web site anyway :-) > I just installed the new code and everything seems to work as advertised. The > "first-connection" problem is gone and no new bugs appear to have been > introduced. I tested connecting both with my FreeBSD console and from the > Windows boxen on the private network behind it. > > Thanks for the fix! Any idea when/if it will be committed to Stable? > > Regards, > --Keith Stevenson-- > > -- > Keith Stevenson > System Programmer - Data Center Services - University of Louisville > k.stevenson@louisville.edu > PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 > > On Thu, Oct 22, 1998 at 01:32:48PM +0100, Brian Somers wrote: > > Ppp has just been updated with some code that should work around the > > ``first connection'' problem for people running in -auto -alias mode > > with dynamic IPs. > > > > Previously, the program that caused the dial up would never connect > > although programs started after the dialup is complete would. Now, > > everything should ``just work''. > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 18:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14911 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 18:53:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hydrogen.fircrest.net (metriclient-5.uoregon.edu [128.223.172.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14904 for ; Sun, 25 Oct 1998 18:53:33 -0800 (PST) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by hydrogen.fircrest.net (8.9.1/8.8.7) id SAA01403; Sun, 25 Oct 1998 18:52:56 -0800 (PST) Message-ID: <19981025185256.50775@hydrogen.nike.efn.org> Date: Sun, 25 Oct 1998 18:52:56 -0800 From: John-Mark Gurney To: FreeBSD Hackers Subject: clock running slowly (3.0-R) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well, I have a machine w/ 3.0-R and the clock is running VERY slowly.. # telnet h daytime; date; sleep 1; date; telnet h daytime Trying 192.168.0.1... Connected to hydrogen.fircrest.net. Escape character is '^]'. Sun Oct 25 18:47:40 1998 Connection closed by foreign host. Sun Oct 25 18:47:09 PST 1998 Sun Oct 25 18:47:10 PST 1998 Trying 192.168.0.1... Connected to hydrogen.fircrest.net. Escape character is '^]'. Sun Oct 25 18:49:31 1998 Connection closed by foreign host. and yes, the clock on hydrogen is running perfectly fine... I have xntpd syncing to two stratum 2 servers... the clock runs perfectly fine under win95... and I am using fbsdboot to boot freebsd, but other than that, a pretty much standard setup... here is the dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Sun Oct 25 16:01:47 PST 1998 jmg@hydrogen.fircrest.net:/a/home/johng/FreeBSD-checkout/30r/sys/compile/lead.snd Timecounter "i8254" frequency 1193182 Hz cost 4252 ns Timecounter "TSC" frequency 90205130 Hz cost 386 ns CPU: AMD K5 model 0 (90.21-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x501 Stepping=1 Features=0x3bf real memory = 50331648 (49152K bytes) avail memory = 46882816 (45784K bytes) Probing for devices on PCI bus 0: chip0: rev 0x10 on pci0.0.0 chip1: rev 0x02 on pci0.7.0 ide_pci0: rev 0x02 on pci0.7.1 vga0: rev 0x00 int a irq 12 on pci0.8.0 bktr0: rev 0x11 int a irq 7 on pci0.10.0 STB TV/PCI, Temic NTSC tuner, dbx stereo. Probing for PnP devices: CSN 1 Vendor ID: CSC4237 [0x3742630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] mss_attach 1 at 0x530 irq 5 dma 1:3 flags 0x13 pcm1 (CS423x/Yamaha sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 flags 0x13 on isa Probing for devices on the ISA bus: video#0: WARNING: video mode switching is not fully supported on this adapter sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:80:ad:19:5e:8b, type NE2000 (16 bit) pcm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: configured irq 5 not in bitmap of probed irqs 0 sio2 not found at 0x3e8 sio3: configured irq 9 not in bitmap of probed irqs 0 sio3 not found at 0x2e8 lpt0 not found lpt1 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 520MB (1065456 sectors), 1057 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): , 32-bit, multi-block-16 wd1: 1243MB (2546208 sectors), 2526 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 1 (wd3): <\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^? @\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?> wd3: 95MB (196607 sectors), 65535 cyls, 65535 heads, 65535 S/T, 512 B/S wdc1: unit 0 (atapi): <400_02/3 FX>, removable, intr wcd0: 689Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked npx0 on motherboard npx0: INT 16 interface changing root device to wd0s1a WARNING: / was not properly dismounted Start pid=2 Start pid=3 Start pid=4 any ideas? -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 Live in Peace, destroy Micro$oft, support free software, run FreeBSD Don't trust anyone you don't have the source for To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 20:18:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23493 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 20:18:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from tokyonet-entrance.astec.co.jp (tokyonet-entrance.astec.co.jp [202.239.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23488 for ; Sun, 25 Oct 1998 20:18:05 -0800 (PST) (envelope-from junichi@astec.co.jp) Received: from amont.astec.co.jp (amont.astec.co.jp [172.20.10.1]) by tokyonet-entrance.astec.co.jp (8.9.1+3.0W/3.7W-astecMX2.3) with ESMTP id NAA06812 for ; Mon, 26 Oct 1998 13:17:29 +0900 (JST) Received: from localhost (sakura.astec.co.jp [172.20.10.61]) by amont.astec.co.jp (8.7.6/3.6W-astecMX2.4) with ESMTP id NAA20662 for ; Mon, 26 Oct 1998 13:17:28 +0900 (JST) To: freebsd-hackers@FreeBSD.ORG Subject: libdisk problem X-Mailer: Mew version 1.93pre1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_Oct_26_13:17:23_1998_595)--" Content-Transfer-Encoding: 7bit Message-Id: <19981026131728H.junichi@astec.co.jp> Date: Mon, 26 Oct 1998 13:17:28 +0900 From: Satoh Junichi X-Dispatcher: imput version 980815 Lines: 65 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Mon_Oct_26_13:17:23_1998_595)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit I found the Write_Disk() in libdisk doesn't support any length of device name. It supports only two characters. So, I can not create slices on the 'wfd' using /stand/sysinstall which links the libdisk. I made a patch against /usr/src/lib/libdisk/write_disk.c of -current to support any device names. Can anyone commit it? --- Junichi ----Next_Part(Mon_Oct_26_13:17:23_1998_595)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=write_disk.diff *** write_disk.c.org Tue Oct 6 20:57:08 1998 --- write_disk.c Thu Oct 22 21:46:09 1998 *************** *** 64,73 **** for(c2=c1->part;c2;c2=c2->next) { if (c2->type == unused) continue; if (!strcmp(c2->name,"X")) continue; ! j = c2->name[5] - 'a'; if (j < 0 || j >= MAXPARTITIONS || j == RAW_PART) { #ifdef DEBUG ! warn("Weird parititon letter %c",c2->name[5]); #endif continue; } --- 64,73 ---- for(c2=c1->part;c2;c2=c2->next) { if (c2->type == unused) continue; if (!strcmp(c2->name,"X")) continue; ! j = c2->name[strlen(new->name) + 2] - 'a'; if (j < 0 || j >= MAXPARTITIONS || j == RAW_PART) { #ifdef DEBUG ! warn("Weird parititon letter %c",c2->name[strlen(new->name) + 2]); #endif continue; } *************** *** 172,178 **** for (c1=d1->chunks->part; c1 ; c1 = c1->next) { if (c1->type == unused) continue; if (!strcmp(c1->name,"X")) continue; ! j = c1->name[4] - '1'; if (j < 0 || j > 3) continue; s[j]++; --- 172,178 ---- for (c1=d1->chunks->part; c1 ; c1 = c1->next) { if (c1->type == unused) continue; if (!strcmp(c1->name,"X")) continue; ! j = c1->name[strlen(d1->name) + 1] - '1'; if (j < 0 || j > 3) continue; s[j]++; ----Next_Part(Mon_Oct_26_13:17:23_1998_595)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Oct 25 21:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03778 for freebsd-hackers-outgoing; Sun, 25 Oct 1998 21:59:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from chickenbean.ais-gwd.com (chickenbean.com [205.160.97.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03574; Sun, 25 Oct 1998 21:57:41 -0800 (PST) (envelope-from charlespeters@chickenbean.com) Received: from ci1000971-d.sptnbrg1.sc.home.com (ci1000971-d.sptnbrg1.sc.home.com [24.4.115.200]) by chickenbean.ais-gwd.com (8.8.8/8.8.8) with SMTP id BAA02260; Mon, 26 Oct 1998 01:09:12 -0500 (EST) (envelope-from charlespeters@chickenbean.com) Reply-To: From: "Charles A. Peters" To: , , , , , , , , , , , , , , , , Date: Mon, 26 Oct 1998 00:51:11 -0500 Message-ID: <000001be00a5$5e2d8d40$c8730418@ci1000971-d.sptnbrg1.sc.home.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 00:13:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15667 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 00:13:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from proxy.unpar.ac.id ([167.205.206.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15653 for ; Mon, 26 Oct 1998 00:13:27 -0800 (PST) (envelope-from 1193016@student.unpar.ac.id) Received: from student.unpar.ac.id (1193016@student.unpar.ac.id [10.210.1.3]) by proxy.unpar.ac.id (8.8.5/8.8.5) with ESMTP id KAA02175 for ; Thu, 26 Oct 1995 10:32:31 +0700 (JAVT) Received: from localhost (1193016@localhost) by student.unpar.ac.id (8.9.1/8.9.0) with ESMTP id PAA18541 for ; Mon, 26 Oct 1998 15:17:03 +0700 (JAVT) Date: Mon, 26 Oct 1998 15:17:03 +0700 (JAVT) From: Thomas Wahyudi <1193016@student.unpar.ac.id> To: freebsd-hackers@FreeBSD.ORG Subject: dup! (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have two NC, ed0 and vx0 if I ping from internal network, the result is normal but if I ping from outside network, the result get DUP! what could be wrong ? fyi this machine running gated Best regard, from #### # Thomas Wahyudi UIN:535778 # # # # 1193016@student.unpar.ac.id # ## ## http://student.unpar.ac.id/~1193016 -=-=-=-=-=PARAHYANGAN UNIVERSITY=-=-=-=-=-=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 00:57:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19038 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 00:57:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA19033 for ; Mon, 26 Oct 1998 00:57:47 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA26339; Mon, 26 Oct 1998 09:57:05 +0100 (MET) Date: Mon, 26 Oct 1998 09:57:02 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Terry Lambert cc: FreeBSD hackers mailing list Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: <199810232051.NAA01614@usr07.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > being in italy i can speak about that.. cameras and scanners are > > more and more available in stores on USB nowadays (actually it is becoming > > difficult to find non-USB scanners and especially cameras in some > > places). I haven't seen many keyboards/mice on USB though. > > They don't sell iMac hardware in Italy? You always have to order. Italian shops tend to have things not in stock when you ask for them. Especially when it is something 'new'. > The iMac keyboard and mouse are USB. Apple at the steering wheel of USB is a Good Thing (tm). They are at least good in keeping their suppliers in line with standards. Nick -- STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 05:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13086 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 05:57:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from att.com (cagw1.att.com [192.128.52.89]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA13078 for ; Mon, 26 Oct 1998 05:57:17 -0800 (PST) (envelope-from sbabkin@dcn.att.com) From: sbabkin@dcn.att.com Received: from caig1.fw.att.com by cagw1.att.com (AT&T/IPNS/UPAS-1.0) for freebsd.org!freebsd-hackers sender dcn.att.com!sbabkin (dcn.att.com!sbabkin); Mon Oct 26 08:43 EST 1998 Received: from dcn71.dcn.att.com ([135.44.192.112]) by caig1.fw.att.com (AT&T/IPNS/GW-1.0) with ESMTP id IAA07891 for ; Mon, 26 Oct 1998 08:52:11 -0500 (EST) Received: by dcn71.dcn.att.com with Internet Mail Service (5.0.1458.49) id ; Mon, 26 Oct 1998 09:00:43 -0500 Message-ID: To: dg@root.com, Reinier.Bezuidenhout@KryptoKom.DE Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: fxp 10/100 and device timeouts Date: Mon, 26 Oct 1998 09:00:41 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: David Greenman [SMTP:dg@root.com] > > >I am doing some througput tests and I'm running into some problems > >with the Intel ether express 10/100B cards. > > > >I am using ttcp with udp packets and using different packet sizes. > The > >connections are 100MB full-duplex connections with x-over cables. > The > >setup is as follows. > > Don't use cross-over cables. This was a known problem early on and > Intel's > official response when I asked them about it was "cross-over cables > aren't > supported with the Pro/100B cards". > I suspect there is some bit of PHY programming that needs to be > done that > isn't happening, but that's just a guess. > I have used two Pro/100B cards connected without a hub, back-to-back with a crossover cable, without any problems. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 06:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14444 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 06:08:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14439 for ; Mon, 26 Oct 1998 06:08:21 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id OAA18785; Mon, 26 Oct 1998 14:07:21 GMT Message-ID: <36348217.12C37E19@tdx.co.uk> Date: Mon, 26 Oct 1998 14:07:19 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: sbabkin@dcn.att.com CC: dg@root.com, Reinier.Bezuidenhout@KryptoKom.DE, freebsd-hackers@FreeBSD.ORG Subject: Re: fxp 10/100 and device timeouts References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sbabkin@dcn.att.com wrote: > > I suspect there is some bit of PHY programming that needs to be > > done that > > isn't happening, but that's just a guess. > > > I have used two Pro/100B cards connected without > a hub, back-to-back with a crossover cable, without > any problems. I'm using a number of these in cross-over situations, but it didn't happen first time... Some do, some don't (infact the ones I'm using at the moment do - but only if I leave them in the machines, if I swap the cards over within the same group of machines - they don't (and even then they only "don't" one-way... - If you get what I mean). Summary: Your mileage may vary... I had a lot of cards and cables to swap around with, and I was lucky to find some that work... ;-) (and a lot that didn't)... David Greenman at the time got involved a bit - but between us we couldn't come up with anything definitive... Cables? Cards? Timing? - Timing and Cables? Who knows... (The only interesting thing I did find is that a sequence of 'FFFF-FFFF's repeated would screw the card up one-way only for one of the configurations I cooked together... Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 07:09:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19929 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 07:09:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net (gw.sparks.net [209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA19923 for ; Mon, 26 Oct 1998 07:09:36 -0800 (PST) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0zXoGN-0004FL-00; Mon, 26 Oct 1998 10:08:55 -0500 Date: Mon, 26 Oct 1998 10:08:54 -0500 (EST) From: To: freebsd-hackers@FreeBSD.ORG Subject: Time syncing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone used a system on FreeBSD, any version, which could sync the system clock from an external source other than via xntpd/timed? I need to sync to the clock at a cable headend for insertion of digital video programming. For non-relevent reasons I can't just drop a time card with drivers into the NT box doing the actual playback. I *can* get a version of ntp for NT, but would rather have a nice bsd box doing time syncs than pay MS more $$ for another NT license. The specific hardware involved is from W Clark & Associates. My choices are an ISA card (TCR 500) and an RS-232 (TCI 232) box from which you can read the time/date. Once I got the time into a FreeBSD box I could xntpd serve off it. More info available at http://www.masterclock.com. Thanks in advance for any pointers:) --- David Miller ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 07:13:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20244 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 07:13:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ms13.url.com.tw (gemini.accton.com.tw [210.68.148.7]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA20237 for ; Mon, 26 Oct 1998 07:13:13 -0800 (PST) (envelope-from willer@ms13.url.com.tw) Date: Mon, 26 Oct 1998 07:13:13 -0800 (PST) Received: from willer ([202.145.254.42]) by AccSMTP/NT 2.5 (210.68.148.49) [210.68.148.49]; Mon, 26 Oct 1998 21:49:58 +0800 Message-ID: <007501be00e7$a55fffd0$8eab91ca@willer.willer.net> To: From: "willer" Subject: =?big5?B?sXqkQKl3rW6lzsD0q0+lUrlxuXGmwA==?= MIME-Version: 1.0 Content-Type: text/plain; charset="big5" X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.freebsd.org id HAA20240 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ¥DÃD ·R¥xÆW ±z¤@©w­n¥ÎÀô«O¥R¹q¹q¦À ¦U Ãþ ¤T¸¹¹q¦À¤ñ¸û ¹q¦À¯S©Ê Àô«OÆP©Ê¹q¦À ´¶³q¹q¦À ÂìÂð¹q¦À Àô«O Âì ²B¹q¦À ¥i¥R¹q¦¸¼Æ ¹s¦¸ ¹s¦¸ ¬ù¤@¨Õ¦¸ ¤j©ó¤­¨Õ¦¸ §t­«ª÷ÄݦìV·½ µL µL §tÂ𭫪÷ÄÝ µL °ª¯Ó¹q¨Ï¥Î ¾A¦X ¤£¾A¦X ¾A¦X ¾A¦X °ª«ù¤[©Ê ¬O §_ §_ ¬O ¥R¹q°O¾Ð©Ê -- -- ¦³ ¦³ ¦pªG±z·R¥xÆW³o¶ô¤j¦a ½Ð±z¨Ï¥ÎµL¦¾¬VÂì²BÀô«O¥R¹q¹q¦À ¦³¥R¹q°O¾Ð©Êªº¹q¦À ¸ûµLªkµo´§¹q¤O ¥²»Ý§¹¥þ©ñ¹q«á¤~¯à¥R¹q ´ö²L¤T¸¹©Î ¥|¸¹µL¦¾¬VÂì²BÀô«O¥R¹q¹q¦À ºô¸ô°â»ù 99 ¤¸ YUASA NiMH AA or AAA type, NTD 99 Each ´ö²L ª¾¼z«¬¥R¹q¾¹ ? ºô¸ô°â»ù 399 ¤¸ YUASA Recharger of NiMH, NTD 399 Tel: (03)3278012 BBC: 060224189-099 Mobile: 0933926100 Miss Eileen Lin ªL¤p©j To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 08:05:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24035 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 08:05:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from borderware.com (ns.borderware.com [209.226.34.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24030 for ; Mon, 26 Oct 1998 08:05:41 -0800 (PST) (envelope-from dchapes@borderware.com) Received: by gateway.borderware.com id <115594>; Mon, 26 Oct 1998 11:01:14 -0500 Message-Id: <98Oct26.110114est.115594@gateway.borderware.com> Date: Mon, 26 Oct 1998 10:44:05 -0500 From: Dave Chapeskie To: Drew Baxter Cc: hackers@FreeBSD.ORG Subject: Re: XL0 References: <4.1.0.67.19981022124020.00ad2100@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.0.67.19981022124020.00ad2100@genesis.ispace.com>; from Drew Baxter on Thu, Oct 22, 1998 at 12:43:17PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 22, 1998 at 12:43:17PM -0400, Drew Baxter wrote: > Got my dmesg output for the day.. (this is probably my 2nd day of using my > XL card instead of a EP0'd 3c509), and i see this.. Anyone able to shed > some light on it? It runs fine otherwise, not sure if this is killing > performance when we have this happen or not. > > > xl0: transmission error: 82 [repeats] > > --- > Drew "Droobie" Baxter > Network Admin/Professional Computer Nerd(TM) > OneEX: The OneNetwork Exchange 207-942-0275 > http://www.droo.orland.me.us > My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 I had the exact same thing and this is the response I got from the author of the xl0 driver: > > a) What does transmission error 82 mean? > > The 2 part in this case indicates the error which, according to the > manual is: > > #define XL_TXSTATUS_RECLAIM 0x02 /* 3c905B only */ > > The manual says that this error happens because "the packet experienced > a collision after the front of the packet had been reclaimed to the > FIFO free space." In other words, the chip had sent the packet and had > already erased part of it from its internal FIFO RAM when it detected > a collision. The driver detects this error and, if the packet is still > in the driver's outbound queue, it will attempt to retransmit it. If > it isn't in the queue, the driver just acknowledges the TX error interrupt > and continues. I don't think there should be any traffic interruptions. > > The 80 part means the transmission is complete: > > #define XL_TXSTATUS_COMPLETE 0x80 > > > b) Is it something I should be concerned about? > > Not really. If the error message annoys you, you can hide it under an > #ifdef DIAGNOSTIC/#endif pair. The driver recovers from the condition > correctly, so it's really just an informational message. (There was a > bug in older versions of the driver where the error handler failed to > check if there really was a packet in the outbound queue and could panic > when it tried to dereference the NULL queue head pointer, but I fixed > that.) > > > c) Is it a potential problem with my cabling or hub? > > Mmm... possibly. I would expect to see this on a busy shared ethernet > with lots of collisions, but there might be other causes. In my test > environment I use an ethernet switch and don't ever see these errors. > > -Bill > > -- > ============================================================================= > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ============================================================================= Hope this helps. -- Dave Chapeskie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 10:08:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05231 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 10:08:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05221; Mon, 26 Oct 1998 10:08:19 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id SAA11606 Mon, 26 Oct 1998 18:07:31 GMT Message-ID: <3634BA43.94BC672C@cs.strath.ac.uk> Date: Mon, 26 Oct 1998 18:06:59 +0000 From: Roger Hardiman Organization: Strathclyde Uni X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: PCIC_IRQ - disabling PCMCIA IRQ allocation Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, One of the things PAO hase which the 3.0-RELEASE PCMCIA code does not have is the PCIC_IRQ kernel configuration. With it, it is possible to tell the PCMCIA card controller NOT to reserve itself an IRQ. This means no hot swapping of cards, but for my application (embedded systems) I cannot hot swap and I do not want an IRQ wasted by the card chipset. The patch for 3.0-RELEASE is trivial to include the PCIC_IRQ code (basically it forces a value in the pcic.c code). Is someone willing to commit this to -current if I supply the diff. It will then complete all my PCMCIA needs without needing the full PAO package. Bye Roger Hardiman Strathclyde University Telepresence Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 10:58:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08769 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 10:58:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08764 for ; Mon, 26 Oct 1998 10:58:17 -0800 (PST) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id LAA18793; Mon, 26 Oct 1998 11:57:29 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd018704; Mon Oct 26 11:57:24 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA13957; Mon, 26 Oct 1998 11:57:09 -0700 (MST) From: Terry Lambert Message-Id: <199810261857.LAA13957@usr04.primenet.com> Subject: Re: Oracle8 Release 8.0.5 for LINUX 2.0.34 To: chuckr@mat.net (Chuck Robey) Date: Mon, 26 Oct 1998 18:57:09 +0000 (GMT) Cc: tlambert@primenet.com, mike@smith.net.au, selvaraj@sri.lanka.net, hackers@FreeBSD.ORG In-Reply-To: from "Chuck Robey" at Oct 24, 98 08:13:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Oracle will not run on FreeBSD at this stage. It is likely that it > > > will not be supported on the 2.2.x family at all. > > > > Unless you get the version of Oracle that Oracle sells on their > > FreeBSD-running NC server, in which case it runs great on 2.2.6 > > and above. > > > > This would incidently make it a FreeBSD issue instead of a Linux > > emulation issue, killing two birds with one stone. 8-). > > Last time I heard from John Dyson on this list about that, the FreeBSD > version wasn't a publicly available thing. Love to have it, I'm doing a > Oracle class project now, and it sure would be lovely to have (drool!) You don't get if you don't ask. In other words, ask them for it. The difference between an internal and a public release is whether there is a perceived market for the thing or not. It's not like they have additional porting effort, and it's not like they don't already have to support it internally, so it's almost zero work for them to do a release -- if there's a market. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 11:56:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14997 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 11:56:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ime.net (ime.net [209.90.192.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14989 for ; Mon, 26 Oct 1998 11:56:05 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4014.ime.net [209.90.195.24]) by ime.net (8.8.7/8.8.7) with SMTP id OAA05715; Mon, 26 Oct 1998 14:55:20 -0500 (EST) Message-Id: <4.1.19981026145333.00b06100@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 26 Oct 1998 14:54:04 -0500 To: Dave Chapeskie From: Drew Baxter Subject: Re: XL0 Cc: hackers@FreeBSD.ORG In-Reply-To: <98Oct26.110114est.115594@gateway.borderware.com> References: <4.1.0.67.19981022124020.00ad2100@genesis.ispace.com> <4.1.0.67.19981022124020.00ad2100@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well at least it isn't "Card has caught on fire, contact local fire prevention immediately".. That must be Error 28, I always get those mixed up :) At 10:44 AM 10/26/98 -0500, Dave Chapeskie wrote: >On Thu, Oct 22, 1998 at 12:43:17PM -0400, Drew Baxter wrote: >> Got my dmesg output for the day.. (this is probably my 2nd day of using my >> XL card instead of a EP0'd 3c509), and i see this.. Anyone able to shed >> some light on it? It runs fine otherwise, not sure if this is killing >> performance when we have this happen or not. >> >> > xl0: transmission error: 82 >[repeats] >> >> --- >> Drew "Droobie" Baxter >> Network Admin/Professional Computer Nerd(TM) >> OneEX: The OneNetwork Exchange 207-942-0275 >> http://www.droo.orland.me.us >> My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT >1998 > >I had the exact same thing and this is the response I got from the >author of the xl0 driver: > >> > a) What does transmission error 82 mean? >> >> The 2 part in this case indicates the error which, according to the >> manual is: >> >> #define XL_TXSTATUS_RECLAIM 0x02 /* 3c905B only */ >> >> The manual says that this error happens because "the packet experienced >> a collision after the front of the packet had been reclaimed to the >> FIFO free space." In other words, the chip had sent the packet and had >> already erased part of it from its internal FIFO RAM when it detected >> a collision. The driver detects this error and, if the packet is still >> in the driver's outbound queue, it will attempt to retransmit it. If >> it isn't in the queue, the driver just acknowledges the TX error interrupt >> and continues. I don't think there should be any traffic interruptions. >> >> The 80 part means the transmission is complete: >> >> #define XL_TXSTATUS_COMPLETE 0x80 >> >> > b) Is it something I should be concerned about? >> >> Not really. If the error message annoys you, you can hide it under an >> #ifdef DIAGNOSTIC/#endif pair. The driver recovers from the condition >> correctly, so it's really just an informational message. (There was a >> bug in older versions of the driver where the error handler failed to >> check if there really was a packet in the outbound queue and could panic >> when it tried to dereference the NULL queue head pointer, but I fixed >> that.) >> >> > c) Is it a potential problem with my cabling or hub? >> >> Mmm... possibly. I would expect to see this on a busy shared ethernet >> with lots of collisions, but there might be other causes. In my test >> environment I use an ethernet switch and don't ever see these errors. >> >> -Bill >> >> -- >> ============================================================================= >> -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu >> Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research >> Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City >> ============================================================================= >> "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" >> ============================================================================= > >Hope this helps. >-- >Dave Chapeskie --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 14:32:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01334 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 14:32:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01328 for ; Mon, 26 Oct 1998 14:32:28 -0800 (PST) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com (ppp142.dialin.bonn-online.com [194.162.223.142]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id XAA19751 for ; Mon, 26 Oct 1998 23:31:38 +0100 Message-ID: <3634F865.9755D2E7@bonn-online.com> Date: Mon, 26 Oct 1998 23:32:05 +0100 From: Sebastian Lederer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Patch for src/sys/i386/isa/wd.c Content-Type: multipart/mixed; boundary="------------8F9E5C4B973502E5736EE3E7" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------8F9E5C4B973502E5736EE3E7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, How about the following patch to src/sys/i386/isa/wd.c ? It fills in the disk model name (and disk type) when reading the in-core disk label via the DIOCGDINFO ioctl(), if it has not already been set. Tested and working on a couple of machines. It's just a simple way for userland programs to identify IDE disks by name (which is what I need for a FreeBSD installation program). Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com --------------8F9E5C4B973502E5736EE3E7 Content-Type: text/plain; charset=us-ascii; name="wd.c.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="wd.c.diff" *** sys/i386/isa/wd.c.orig Mon Oct 26 21:49:04 1998 --- sys/i386/isa/wd.c Mon Oct 26 23:03:57 1998 *************** *** 1984,1989 **** --- 1984,2003 ---- wdsleep(du->dk_ctrlr, "wdioct"); error = dsioctl("wd", dev, cmd, addr, flags, &du->dk_slices, wdstrategy1, (ds_setgeom_t *)NULL); + + + if (!error && cmd == DIOCGDINFO) { + if (!strncmp(((struct disklabel *) addr)->d_packname, + "fictitious", + sizeof(((struct disklabel *) addr)->d_packname))) { + + ((struct disklabel *) addr)->d_type = DTYPE_ESDI; + bcopy(du->dk_params.wdp_model, + ((struct disklabel *) addr)->d_packname, + sizeof(((struct disklabel *) addr)->d_packname)); + } + } + if (error != ENOIOCTL) return (error); switch (cmd) { --------------8F9E5C4B973502E5736EE3E7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 16:25:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA13873 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 16:25:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA13853; Mon, 26 Oct 1998 16:25:40 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (root@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id AAA27526; Tue, 27 Oct 1998 00:25:01 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id AAA10745; Tue, 27 Oct 1998 00:25:06 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810270025.AAA10745@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Roger Hardiman cc: mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: PCIC_IRQ - disabling PCMCIA IRQ allocation In-reply-to: Your message of "Mon, 26 Oct 1998 18:06:59 GMT." <3634BA43.94BC672C@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 00:25:04 +0000 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > One of the things PAO hase which the 3.0-RELEASE PCMCIA code does not > have is the > PCIC_IRQ kernel configuration. > > With it, it is possible to tell the PCMCIA card controller NOT to > reserve itself an IRQ. > This means no hot swapping of cards, but for my application (embedded > systems) I cannot hot > swap and I do not want an IRQ wasted by the card chipset. > > The patch for 3.0-RELEASE is trivial to include the PCIC_IRQ code > (basically it forces a value in the > pcic.c code). > > Is someone willing to commit this to -current if I supply the diff. > > It will then complete all my PCMCIA needs without needing the full PAO > package. I'm willing to if 1. You can also specify the IRQ that the controller should use. 2. Either Nate or Mike OKs it (I'll pass it to them for review first - they're our resident laptop people). > Bye > Roger Hardiman > Strathclyde University Telepresence Group Cheers. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 16:29:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14291 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 16:29:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from yonge.cs.toronto.edu (yonge.cs.toronto.edu [128.100.1.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA14278 for ; Mon, 26 Oct 1998 16:29:26 -0800 (PST) (envelope-from dholland@cs.toronto.edu) Received: from qew.cs.toronto.edu ([128.100.1.13]) by yonge.cs.toronto.edu with SMTP id <86461-6609>; Mon, 26 Oct 1998 19:28:42 -0500 Received: by qew.cs.toronto.edu id <37768-3361>; Mon, 26 Oct 1998 19:28:29 -0500 Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE? From: David Holland To: garbanzo@hooked.net (Alex Zepeda) Date: Mon, 26 Oct 1998 19:28:19 -0500 Cc: jdp@polstra.com, jin@george.lbl.gov, hackers@FreeBSD.ORG In-Reply-To: from "Alex Zepeda" at Oct 23, 98 05:56:29 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <98Oct26.192829edt.37768-3361@qew.cs.toronto.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On that note one thing I've noticed is that the ELF ld refuses to > recognize shared libs unless they end in .so. What would the chances be > of having it check for libfoo.so.x where x is the greatest value (assuming > libfoo.so doesn't exist)? This is rather annoying, as the a.out ld > doesn't do this, and the Linux ld apparently doesn't do this, and that > covers quite a lot of software one might want to compile. mico is a prime > example. The Linux ld (has has been noted already) is the same as the freebsd one. It also requires that you have a *.so filename present. The reason is that ELF does not enforce any semantics on the SONAME of a library, so it's perfectly legitimate to have a libfoo.so.5-pizza-6. Now, if you have libfoo.so.5-pizza-6 and libfoo.so.5-sushi-3, how is ld supposed to guess which one is the "greatest" value? -- - David A. Holland | (please continue to send non-list mail to dholland@cs.utoronto.ca | dholland@hcs.harvard.edu. yes, I moved.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 16:37:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14977 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 16:37:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14969; Mon, 26 Oct 1998 16:37:55 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA28499; Mon, 26 Oct 1998 17:37:09 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA28919; Mon, 26 Oct 1998 17:37:08 -0700 Date: Mon, 26 Oct 1998 17:37:08 -0700 Message-Id: <199810270037.RAA28919@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Brian Somers Cc: Roger Hardiman , mobile@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: PCIC_IRQ - disabling PCMCIA IRQ allocation In-Reply-To: <199810270025.AAA10745@woof.lan.awfulhak.org> References: <3634BA43.94BC672C@cs.strath.ac.uk> <199810270025.AAA10745@woof.lan.awfulhak.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One of the things PAO hase which the 3.0-RELEASE PCMCIA code does not > > have is the > > PCIC_IRQ kernel configuration. > > > > With it, it is possible to tell the PCMCIA card controller NOT to > > reserve itself an IRQ. > > This means no hot swapping of cards, but for my application (embedded > > systems) I cannot hot > > swap and I do not want an IRQ wasted by the card chipset. > > > > The patch for 3.0-RELEASE is trivial to include the PCIC_IRQ code > > (basically it forces a value in the > > pcic.c code). > > > > Is someone willing to commit this to -current if I supply the diff. > > > > It will then complete all my PCMCIA needs without needing the full PAO > > package. > > I'm willing to if > > 1. You can also specify the IRQ that the controller should use. > 2. Either Nate or Mike OKs it (I'll pass it to them for review first > - they're our resident laptop people). I'm out of the picture, but I'd like to see it done 'correctly'. Using OPTIONS is IMO the 'wrong' way of doing it. PAO already has about 3 dozen different options, and that's about 3 dozen too many when in fact each option is generally specific to one file. There's got to be a better way of configuring a single-file that is better than using options. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 16:48:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16074 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 16:48:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16035 for ; Mon, 26 Oct 1998 16:47:56 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id QAA00714; Mon, 26 Oct 1998 16:47:11 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <3635180F.BA6C6F92@gorean.org> Date: Mon, 26 Oct 1998 16:47:11 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1026 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sebastian Lederer CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: <3634F865.9755D2E7@bonn-online.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sebastian Lederer wrote: > > Hi, > > How about the following patch to src/sys/i386/isa/wd.c ? It fills in the > disk model name (and disk type) when reading the in-core disk label via > the DIOCGDINFO ioctl(), if it has not already been set. Tested and > working on a couple of machines. It's just a simple way for userland > programs to identify IDE disks by name (which is what I need for a > FreeBSD installation program). This compiles and runs fine on -stable, any chance you could supply code that would show me the label? I think this is a fine idea, and I'd even like to see it in the boot message. More information provided to the user is always a good thing. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 17:34:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20664 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 17:34:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20659 for ; Mon, 26 Oct 1998 17:34:48 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0zXy1P-000I0NC; Mon, 26 Oct 1998 20:34:07 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Weird 'make' trivia To: hackers@FreeBSD.ORG Date: Mon, 26 Oct 1998 20:34:07 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you ever do a 'make world' and mkdep fails in libgroff, unable to find a bunch of existing includes for *.cc files, you somehow had CXXFLAGS instantiated with a value before issuing the 'make world'. Unset it. On the other hand, it is a good idea to set CFLAGS permanently to your preferred optimization values (I use -O2 -m486 -pipe). This is because 'configure' scripts test to see if there are pre-existing values in CFLAGS, and ensure they are used in any subsequent compiles. Otherwise the default -O will probably be used. Tom PS. It was fun finding that one! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 17:40:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21367 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 17:40:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-16.ppp.wenet.net [206.15.85.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21358 for ; Mon, 26 Oct 1998 17:40:24 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id RAA00698; Mon, 26 Oct 1998 17:41:15 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Mon, 26 Oct 1998 17:41:15 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: David Holland cc: jdp@polstra.com, jin@george.lbl.gov, hackers@FreeBSD.ORG Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE? In-Reply-To: <98Oct26.192829edt.37768-3361@qew.cs.toronto.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Oct 1998, David Holland wrote: > The Linux ld (has has been noted already) is the same as the freebsd > one. It also requires that you have a *.so filename present. The > reason is that ELF does not enforce any semantics on the SONAME of a > library, so it's perfectly legitimate to have a libfoo.so.5-pizza-6. If this was true, then mico's configure script wouldn't properly detect shared libs. But it does, except on FreeBSD/ELF. > Now, if you have libfoo.so.5-pizza-6 and libfoo.so.5-sushi-3, how is > ld supposed to guess which one is the "greatest" value? I'm sure the a.out ld has code for this type of thing. Why not emulate its behavior? - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Oct 26 20:02:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05483 for freebsd-hackers-outgoing; Mon, 26 Oct 1998 20:02:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05473 for ; Mon, 26 Oct 1998 20:02:45 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id XAA09134; Mon, 26 Oct 1998 23:02:08 -0500 (EST) Message-ID: <19981026230208.A8159@netmonger.net> Date: Mon, 26 Oct 1998 23:02:08 -0500 From: Christopher Masto To: hackers@FreeBSD.ORG Subject: Some curiosity about syscons Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The end of daylight time upon us, I have just finished writing my second Timex DataLink watch downloader. The first one was for X, 'cause I thought it was necessary, but it quickly became a pain to configure a second X session for the correct scanrate. Then I realized that VGA_80x30 is 60hz, and as luck would have it, nothing more than plain old text mode and IBM line-drawing characters is needed. Anyway.. I wasn't quite sure what the best approach would be, so I decided to see if I would just luck out and need no more than stdio and some cheating. It turns out, of course, that syscons doesn't simply put what you send it on the screen; it puts it into a buffer which is copied to the screen periodically, so I couldn't trivially make it work. Rather than back up and start over with a different approach, I added a tiny ioctl to syscons to call scrn_update(). With that and some fudging, I actually have the damned thing working. If anyone is still following this, and particularly if you Know From Experience, perhaps you can comment on some of these architectural issues. I need a 60Hz vertical refresh rate, and I need to be able to display 18 lines of text every frame. This needs to happen during the vertical retrace interval, as a single glitched frame will cause a failure. Ideally I would like the cursor not to be present, but it isn't actually a problem if I can make sure it is always at the top or bottom of the screen. The questions I'm considering are, more or less.. should this go in the kernel? Should I try to interact with syscons, or should I do whatever X does to get a console of my own? If I do that, do I need to program the VGA controller at a low level? It's tempting to just add a few flags to syscons so that I can say "don't touch this VC anymore, and let me write directly to it". I would like to have the freedom a screen saver has, without having to be a screen saver. What I have right now is a gross hack, although it's very small one. It sufficed to set my watch, and I may just ignore it for another six months, but then I'll want to rewrite it again. :-) Tomorrow I'll put the code somewhere, though I doubt many people want to patch their kernel for it. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ There won't be anything we won't say to people to try and convince them that our way is the way to go. - BILL GATES To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 00:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA25754 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 00:30:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA25749 for ; Tue, 27 Oct 1998 00:30:14 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA03642; Tue, 27 Oct 1998 07:25:27 +0100 From: Luigi Rizzo Message-Id: <199810270625.HAA03642@labinfo.iet.unipi.it> Subject: Potential problem with network drivers in promisc mode To: hackers@FreeBSD.ORG Date: Tue, 27 Oct 1998 07:25:26 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just after my yesterday patch to if_ed.c i realised that there might be a severe problem with many network drivers. The problem is as follows: when the interface goes in promisc mode (e.g. because one is using bpf), certain drivers (I have not cheched how many, but for sure the "ed" driver does this) are configured to accept also RUNT pkts and those with bad CRCs. This means that very short packets may make it up to the point where the card prepares for ether_input(), and the usual action there is something like ms->m_pkthdr.len -= sizeof(struct ether_header); etc.. If m_pkthdr.len < 14, this results in a very large value going into m_pkthdr.len (u_short), with all sort of interesting consequences. Before you comment that packets are checked for a matching ether dst address, remember that multicast packets are passed up unconditionally, and because the multicast bit is the first one in the packet, they are more at risk than others. Possible countermeasures: * disable RUNT reception when in promisc mode (I am not sure if this is a standard bpf option, or just happens to be implemented in the "ed" driver for convenience); * use m_adj() to remove the ethernet header from packet buffers, because it does the appropriate length checks; * implement more accurate checks in all drivers before removing the packet headers. If it is allowed, i'd probably go for the first approach, because the code paths between bpf_mtap() and ether_input() can be a bit convoluted. I will try to come up with a more precise report on critical drivers on -stable and -current. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 00:45:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA27243 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 00:45:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA27238 for ; Tue, 27 Oct 1998 00:45:23 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA09535; Tue, 27 Oct 1998 00:45:00 -0800 (PST) Message-Id: <199810270845.AAA09535@implode.root.com> To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: Potential problem with network drivers in promisc mode In-reply-to: Your message of "Tue, 27 Oct 1998 07:25:26 +0100." <199810270625.HAA03642@labinfo.iet.unipi.it> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 00:44:59 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >accept also RUNT pkts and those with bad CRCs. This means that very >short packets may make it up to the point where the card prepares for >ether_input(), and the usual action there is something like > > ms->m_pkthdr.len -= sizeof(struct ether_header); > >etc.. If m_pkthdr.len < 14, this results in a very large value going >into m_pkthdr.len (u_short), with all sort of interesting consequences. ... > * disable RUNT reception when in promisc mode (I am not sure if this > is a standard bpf option, or just happens to be implemented in the > "ed" driver for convenience); I haven't verified this with the NIC spec, but I don't think it will ever pass packets that are smaller than 14 bytes since the packets must still conform to the 802.3 spec. Still, I think it would be best to check the length and drop the packet if it is less than 14 bytes. I don't think it is wise to always believe what the hardware tells you. I do the check in the fxp driver, but I see that this is an exception for FreeBSD drivers. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 06:01:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20000 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 06:01:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19995 for ; Tue, 27 Oct 1998 06:01:39 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA19539 Tue, 27 Oct 1998 09:00:59 -0500 (EST) Message-ID: <3635D21B.961D038@ics.com> Date: Tue, 27 Oct 1998 09:00:59 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE? References: <98Oct26.192829edt.37768-3361@qew.cs.toronto.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Holland wrote: > > > On that note one thing I've noticed is that the ELF ld refuses to > > recognize shared libs unless they end in .so. What would the chances be > > of having it check for libfoo.so.x where x is the greatest value (assuming > > libfoo.so doesn't exist)? This is rather annoying, as the a.out ld > > doesn't do this, and the Linux ld apparently doesn't do this, and that > > covers quite a lot of software one might want to compile. mico is a prime > > example. By definition, with ELF, ld always links with the .so. ld uses the SO_NAME in the .so if it's available, otherwise it uses the real name of the library, i.e. libmumble.so.mumble, and stores that as a NEEDED in the program file. At runtime ld.so loads all the NEEDED libraries using the libmumble.so.mumble name. (Note that libmumble.so need not be a symlink to libmumble.so.mumble, in which case ld.so just loads libmumble.so.) > The Linux ld (has has been noted already) is the same as the freebsd > one. It also requires that you have a *.so filename present. The > reason is that ELF does not enforce any semantics on the SONAME of a > library, so it's perfectly legitimate to have a libfoo.so.5-pizza-6. > > Now, if you have libfoo.so.5-pizza-6 and libfoo.so.5-sushi-3, how is > ld supposed to guess which one is the "greatest" value? It doesn't. With ELF, ld.so loads the precise library that was recorded as NEEDED by ld. There is no automatic runtime linking with newer versions as there is with SunOS and *BSD-style shared libraries. If you don't want N copies of a particular library sitting in your /usr/lib then you use (sym)links using the older names to the newest library. -- Kaleb S. KEITHLEY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 06:06:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20536 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 06:06:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ics.com (ics.com [140.186.40.192]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20531 for ; Tue, 27 Oct 1998 06:06:48 -0800 (PST) (envelope-from kaleb@ics.com) Received: from ics.com (sunoco.ics.com [140.186.40.142]) by ics.com (8.9.0.Beta5/8.9.0.Beta5) with ESMTP id JAA19742 Tue, 27 Oct 1998 09:06:11 -0500 (EST) Message-ID: <3635D352.A2E6E2A6@ics.com> Date: Tue, 27 Oct 1998 09:06:10 -0500 From: "Kaleb S. KEITHLEY" Organization: Integrated Computer Solutions X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote: > > > so it's perfectly legitimate to have a libfoo.so.5-pizza-6. > > If this was true, then mico's configure script wouldn't properly detect > shared libs. But it does, except on FreeBSD/ELF. > > > Now, if you have libfoo.so.5-pizza-6 and libfoo.so.5-sushi-3, how is > > ld supposed to guess which one is the "greatest" value? > > I'm sure the a.out ld has code for this type of thing. Why not emulate > its behavior? That's not the ELF way. Lacking the availability of a more architecture neutral reference, I suggest a trip through the System V Application Binary Interface (i.e. SVR4, SVR4.2 ABI) for a good overview of ELF semantics. Unix Press, ISBN 0-13-100439-5. Intel and SPARC supplements are also available, but I don't have the ISBN numbers for them. -- Kaleb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 06:24:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA22211 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 06:24:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA22200 for ; Tue, 27 Oct 1998 06:24:24 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id NAA03999; Tue, 27 Oct 1998 13:19:28 +0100 From: Luigi Rizzo Message-Id: <199810271219.NAA03999@labinfo.iet.unipi.it> Subject: Re: Potential problem with network drivers in promisc mode To: dg@root.com Date: Tue, 27 Oct 1998 13:19:28 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <199810270845.AAA09535@implode.root.com> from "David Greenman" at Oct 27, 98 00:44:40 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > * disable RUNT reception when in promisc mode (I am not sure if this > > is a standard bpf option, or just happens to be implemented in the > > "ed" driver for convenience); > > I haven't verified this with the NIC spec, but I don't think it will ever > pass packets that are smaller than 14 bytes since the packets must still > conform to the 802.3 spec. it does... i am seeing 4, 5, 7 byte-packets (including CRC) all the time here after the fix for packet-lenght computation in the "ed" driver (i am not sure why i never saw less then 4, but perhaps the NIC at least wants enough to have a CRC to compare to.) And for the records, both the lenght in the NIC packet header and the length computed by considering the pointer to the next packet are consistent. > Still, I think it would be best to check the length and drop the packet > if it is less than 14 bytes. I don't think it is wise to always believe what > the hardware tells you. I do the check in the fxp driver, but I see that > this is an exception for FreeBSD drivers. the question is what to do with packets between 14 and 60 bytes: do you think the higher level code will check for short pkts or assumes that a packet with type 0x800 will have for sure an IP header ? The problem is particularly bad because the various length fields are unsigned all over the place and the tests for short packets generally fail because these counters will wrap to large values. if you don't have objections i would do the following: * if it is less than 14 bytes (excluding CRC) drop pkt * between 14 and 59 pass it to bpf if any, but not to ether_input * pkts >= 60 bytes go both to bpf and ether_input (but don't have strong preferences, so for me it's ok to pass up to ether_input() also short packets, although i am a bit uncertain how safe it is.) cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 06:36:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23026 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 06:36:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23021 for ; Tue, 27 Oct 1998 06:36:47 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id GAA12629; Tue, 27 Oct 1998 06:36:43 -0800 (PST) Message-Id: <199810271436.GAA12629@implode.root.com> To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: Potential problem with network drivers in promisc mode In-reply-to: Your message of "Tue, 27 Oct 1998 13:19:28 +0100." <199810271219.NAA03999@labinfo.iet.unipi.it> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 06:36:43 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > * disable RUNT reception when in promisc mode (I am not sure if this >> > is a standard bpf option, or just happens to be implemented in the >> > "ed" driver for convenience); >> >> I haven't verified this with the NIC spec, but I don't think it will ever >> pass packets that are smaller than 14 bytes since the packets must still >> conform to the 802.3 spec. > >it does... i am seeing 4, 5, 7 byte-packets (including CRC) all >the time here after the fix for packet-lenght computation in the >"ed" driver (i am not sure why i never saw less then 4, but perhaps the >NIC at least wants enough to have a CRC to compare to.) >And for the records, both the lenght in the NIC packet header and >the length computed by considering the pointer to the next packet >are consistent. > >> Still, I think it would be best to check the length and drop the packet >> if it is less than 14 bytes. I don't think it is wise to always believe what >> the hardware tells you. I do the check in the fxp driver, but I see that >> this is an exception for FreeBSD drivers. > >the question is what to do with packets between 14 and 60 bytes: >do you think the higher level code will check for short pkts or assumes >that a packet with type 0x800 will have for sure an IP header ? ip_input() is smart about doing consistency checks. It checks the length and many other things, so this will not be a problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 07:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27678 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 07:35:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA27673 for ; Tue, 27 Oct 1998 07:35:00 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id KAA07355; Tue, 27 Oct 1998 10:34:21 -0500 Date: Tue, 27 Oct 1998 10:34:21 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: hackers@FreeBSD.ORG Subject: dropping to single user mode on a telnet connection Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Interesting idea passed to me by john degood, who used to work at hp. On hpux, when you drop to single user via a telnet connection, it leaves the connection open. Result: you don't have to mess around in single user via a local keyboard. This would be heaven on a cluster. I am sure it is hard, but it is something to think about. Ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 07:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28335 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 07:43:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28329 for ; Tue, 27 Oct 1998 07:43:41 -0800 (PST) (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.9.1/8.9.1) with ESMTP id JAA04150 for ; Tue, 27 Oct 1998 09:42:46 -0600 (CST) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199810271542.JAA04150@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG From: Glenn Johnson Subject: cpp error with POSIX defines Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 09:42:46 -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone help me decode this output: from file mdfork.F, line 10: #include cpp: line 90, Error: misplaced constant in #if (_POSIX_VERSION >= 199309L && defined(_POSIX_C_SOURCE) && \ from file /usr/include/sys/unistd.h, line 40: #include from file /usr/include/unistd.h, line 41: #include from file mdfork.F, line 11: #include cpp: line 90, Warning: Unexpected text in #control line ignored (_POSIX_VERSION >= 199309L && defined(_POSIX_C_SOURCE) && \ from file /usr/include/sys/unistd.h, line 40: #include from file /usr/include/unistd.h, line 41: #include from file mdfork.F, line 11: #include 1 error in preprocessor gmake: *** [mdfork.o] Error 1 I seem to be having trouble with Thanks in advance. -- Glenn Johnson Technician USDA, ARS, SRRC New Orleans, LA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 07:44:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28521 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 07:44:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28510 for ; Tue, 27 Oct 1998 07:44:39 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JLJJTEBK; Tue, 27 Oct 98 15:43:56 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981027164356.0090a7c0@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 27 Oct 1998 16:43:56 +0100 To: "Ron G. Minnich" , hackers@FreeBSD.ORG From: Marius Bendiksen Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Interesting idea passed to me by john degood, who used to work at hp. Indeed. This is a quite interesting idea. >On hpux, when you drop to single user via a telnet connection, it leaves >the connection open. Result: you don't have to mess around in single user >via a local keyboard. This would be heaven on a cluster. I am sure it is >hard, but it is something to think about. One possible solution might be setting up a script which is run after the drop to single-user mode. The script could use netcat or telnet, perhaps combined with some tails and then plugged into a shell. This would give you a log of the session, as well as a fairly(?) simple solution. The telnet/netcat would connect back to you, or open a listening session. This is not quite the same, but not that far off, is it? --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 07:54:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29083 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 07:54:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29076 for ; Tue, 27 Oct 1998 07:54:53 -0800 (PST) (envelope-from cmascott@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id KAA10442; Tue, 27 Oct 1998 10:54:12 -0500 (EST) Received: from europa.local (world-f.std.com) by world.std.com (TheWorld/Spike-2.0) id AA25313; Tue, 27 Oct 1998 10:54:10 -0500 Received: (from cmascott@localhost) by europa.local (8.8.8/8.8.8) id KAA00341 for hackers@freebsd.org; Tue, 27 Oct 1998 10:53:38 -0500 (EST) (envelope-from cmascott) Date: Tue, 27 Oct 1998 10:53:38 -0500 (EST) From: Carl Mascott Message-Id: <199810271553.KAA00341@europa.local> To: hackers@FreeBSD.ORG Subject: Seeking volunteer to commit fixes to -stable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the release of 2.2.8 approaching (still mid-November?) I'm looking for a volunteer to commit some fixes to -stable: PR DATE SYNOPSIS --------- -------- -------- bin/7757 08/27/98 xlint/gcc: "warning: integral constant too large" misc/7759 08/27/98 proflibs installation error, libcrypt_p.a kern/8383 10/20/98 msdosfs wipes out NT VFAT lower case flags See the PRs for details, but here are brief comments: bin/7757: Priority: low Fix has been in CVS repository for a long time, but only in -current. A file needs to be migrated to -stable (tag change). misc/7759: Priority: low Probably applies to -current also. 5 lines of tested code need to be added to a shell script. kern/8383: Priority: medium Probably applies to -current also. PR has a patch for several files. I've been running it successfully since 10/13/98. If no one is willing to do the work then I'm volunteering to do it. Note, though, that I'm not in a position to do anything to -current: I have only one machine, and it runs 2.2.7-R. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 07:58:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29231 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 07:58:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29225 for ; Tue, 27 Oct 1998 07:58:13 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id LAA03755; Tue, 27 Oct 1998 11:00:06 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Tue, 27 Oct 1998 11:00:06 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Marius Bendiksen cc: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: <3.0.5.32.19981027164356.0090a7c0@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Marius Bendiksen wrote: > >Interesting idea passed to me by john degood, who used to work at hp. > > Indeed. This is a quite interesting idea. > > >On hpux, when you drop to single user via a telnet connection, it leaves > >the connection open. Result: you don't have to mess around in single user > >via a local keyboard. This would be heaven on a cluster. I am sure it is > >hard, but it is something to think about. > > One possible solution might be setting up a script which is run after the > drop to single-user mode. The script could use netcat or telnet, perhaps > combined with some tails and then plugged into a shell. This would give you > a log of the session, as well as a fairly(?) simple solution. The > telnet/netcat would connect back to you, or open a listening session. > > This is not quite the same, but not that far off, is it? doesn't sound too difficult, you could have init catch the shutdown signal see who it came from, notice thier controlling terminal and not send signals to that process group. or perhaps that could be the behaviour expected if a different signal was sent to init so as not to break non-standard shutdown(ing) programs. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 08:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29656 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 08:05:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA29643 for ; Tue, 27 Oct 1998 08:05:02 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id LAA07537; Tue, 27 Oct 1998 11:04:19 -0500 Date: Tue, 27 Oct 1998 11:04:19 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: Marius Bendiksen cc: hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: <3.0.5.32.19981027164356.0090a7c0@mail.scancall.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It would be even nicer if it could work under ssh. Can some sort of netcat-based idea work for that too? ron Ron Minnich |"Using Windows NT, which is known to have some rminnich@sarnoff.com | failure modes, on a warship is similar to hoping (609)-734-3120 | that luck will be in our favor"- A. Digiorgio ftp://ftp.sarnoff.com/pub/mnfs/www/docs/cluster.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 08:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01730 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 08:29:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gambit.Msk.SU (gambit.msk.su [194.190.206.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01722 for ; Tue, 27 Oct 1998 08:29:12 -0800 (PST) (envelope-from laskavy@Gambit.Msk.SU) Received: (from laskavy@localhost) by Gambit.Msk.SU (8.0/8.9.1) id TAA20361; Tue, 27 Oct 1998 19:28:10 +0300 (MSK) Message-ID: <19981027192809.A20305@gambit.msk.su> Date: Tue, 27 Oct 1998 19:28:09 +0300 From: Sergei Laskavy To: "Ron G. Minnich" , hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection Mail-Followup-To: "Ron G. Minnich" , hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Ron G. Minnich on Tue, Oct 27, 1998 at 10:34:21AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 27, 1998 at 10:34:21AM -0500, Ron G. Minnich wrote: > On hpux, when you drop to single user via a telnet connection, it > leaves the connection open. Result: you don't have to mess around in > single user via a local keyboard. This would be heaven on a cluster. I > am sure it is hard, but it is something to think about. And what about system immutable, undeletable, append-only flags in this mode? -- FreeBSD Project: http://FreeBSD.org/docproj/ Vim: http://www.vim.org/ $_='$6C86:P$^P|2D<2GJPl=2D<2GJp82>3:E^>D<^DFn';tr#P-~\x20-O#\x20-~#;print To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 08:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03354 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 08:47:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03349 for ; Tue, 27 Oct 1998 08:47:01 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id IAA17351; Tue, 27 Oct 1998 08:45:07 -0800 (PST) Message-Id: <199810271645.IAA17351@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: "Kaleb S. KEITHLEY" Cc: hackers@FreeBSD.ORG Subject: Re: ld for loading dynamic library changed in 3.0-RELEASE? Reply-To: Jason Thorpe From: Jason Thorpe Date: Tue, 27 Oct 1998 08:45:06 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998 09:06:10 -0500 "Kaleb S. KEITHLEY" wrote: > Lacking the availability of a more architecture neutral reference, I > suggest a trip through the System V Application Binary Interface (i.e. > SVR4, SVR4.2 ABI) for a good overview of ELF semantics. > Unix Press, ISBN 0-13-100439-5. Intel and SPARC supplements are also > available, but I don't have the ISBN numbers for them. Architecture neutral? That's what the base SVR4.2 ABI spec is. If you mean OS neutral, well, ELF _is_ an SVR4 invention :-) Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 08:47:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03513 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 08:47:45 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03482; Tue, 27 Oct 1998 08:47:20 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id RAA24586; Tue, 27 Oct 1998 17:46:36 +0100 (MET) Date: Tue, 27 Oct 1998 17:46:31 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Doug Rabson cc: FreeBSD hackers mailing list Subject: sys/kern/subr_bus.c ? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has the options file been updated? I can't find opt_bus in i386/conf/ or /sys/conf of 27. Cheers, Nick -- STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy ---------- Forwarded message ---------- Date: Tue, 27 Oct 1998 10:51:33 -0500 From: Alfred Perlstein To: current@FreeBSD.ORG Subject: sys/kern/subr_bus.c ? sys/kern/subr_bus.c line 37: #include "opt_bus.h" This makes "make depend" fail on my kernel, I can't find this file anywhere on my machine, this leaked in sometime last night as I was able to get a kernel to compile however MFS was broken, cvsup'd some changes in this morning noting fixes to mfs/vfs but now this has crept in. Simply commenting this line out seems to have worked (no warnings whatsoever), I'm gonna reboot with this kernel and see what's up. I still have my kernel from about 2 weeks ago which was amazingly stable, i just wanted to have the anti-nestea patches. thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 09:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07409 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 09:38:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07400 for ; Tue, 27 Oct 1998 09:38:31 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id RAA15708 Tue, 27 Oct 1998 17:37:47 GMT Message-ID: <363604EB.15FB@cs.strath.ac.uk> Date: Tue, 27 Oct 1998 17:37:47 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Need help with PCMCIA code changes. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have spoken with Nate about a code change to the PCMCIA code in -current. The current PCMCIA code in -current automatically scans some base addresses and automatically searches for a free IRQ to allocate to the PCMCIA controller chip. (see /sysd/pccard/pcic.c) I want to define my own IRQ in the kernel config. eg to manually specify IRQ 9, with the card at address 0x380 controller card0 device pcic0 at card? port=0x380 irq=9 The code in /sys/pccard/pcic.c would somehow need to query the system for the irq (and/or base address) which has been defined and to skip the 'free irq' probe. But the pcic device is on the 'card0' controller and not the 'isa?' controller. So, how does the pcic device retrieve this information. Thanks Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://telepresence.dmem.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 09:45:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07844 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 09:45:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07837 for ; Tue, 27 Oct 1998 09:45:01 -0800 (PST) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com ([194.162.223.162]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id SAA32369; Tue, 27 Oct 1998 18:44:04 +0100 Message-ID: <3636067E.7C2249A3@bonn-online.com> Date: Tue, 27 Oct 1998 18:44:30 +0100 From: Sebastian Lederer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Studded , freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: <3634F865.9755D2E7@bonn-online.com> <3635180F.BA6C6F92@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded wrote: > Sebastian Lederer wrote: > > > > Hi, > > > > How about the following patch to src/sys/i386/isa/wd.c ? It fills in the > > disk model name (and disk type) when reading the in-core disk label via > > the DIOCGDINFO ioctl(), if it has not already been set. Tested and > > working on a couple of machines. It's just a simple way for userland > > programs to identify IDE disks by name (which is what I need for a > > FreeBSD installation program). > > This compiles and runs fine on -stable, any chance you could supply > code that would show me the label? I think this is a fine idea, and I'd You can use disklabel(8) on the raw disk device, e.g. "disklabel /dev/rwd0", or maybe"disklabel /dev/rwd0 | grep label". > even like to see it in the boot message. More information provided to > the user is always a good thing. Why in the boot message? The kernel already prints the model name when probing the disks, if that's what you mean? Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 09:55:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08703 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 09:55:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08695 for ; Tue, 27 Oct 1998 09:55:36 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id SAA26499 for ; Tue, 27 Oct 1998 18:54:57 +0100 (MET) Date: Tue, 27 Oct 1998 18:54:53 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD hackers mailing list Subject: Re: missing opt_bus.h In-Reply-To: <199810271749.JAA02471@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id JAA08697 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you are in a hurry, do a for i in /sys/compile/*; do touch opt_bus.h done That does it. It makes the compiler ignore any debugging in opt_usb.h. Nick > According to Markus Döhr: > > > make depend > > > > > > ../../kern/subr_bus.c:37: opt_bus.h: No such file or directory > > > mkdep: compile failed > > > *** Error code 1 > > > > Had similar error > > > > try to delete the whole TROUTMASK subtree and build again with config > > TROUTMASK. It should run properly. > > > > Been there. > > Seems to be an incomplete commit to recent changes in > sys/kern/subr_bus.c > > $ Id: subr_bus.c,v 1.8 1998/10/27 09:21:43 dfr Exp $ > -- > Steve > > finger kargl@troutmask.apl.washington.edu > http://troutmask.apl.washington.edu/~clesceri/kargl.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 10:49:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13059 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 10:49:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ms13.url.com.tw (gemini.accton.com.tw [210.68.148.7]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA13020 for ; Tue, 27 Oct 1998 10:49:11 -0800 (PST) (envelope-from willer@ms13.url.com.tw) Date: Tue, 27 Oct 1998 10:49:11 -0800 (PST) Received: from willer ([202.145.254.42]) by AccSMTP/NT 2.5 (210.68.148.49) [210.68.148.49]; Wed, 28 Oct 1998 02:11:50 +0800 Message-ID: <00de01be01d5$6056b6b0$8eab91ca@willer.willer.net> To: From: "willer" Subject: =?big5?B?sXqkQKl3rW6lzsD0q0+lUrlxuXGmwA==?= MIME-Version: 1.0 Content-Type: text/plain; charset="big5" X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.freebsd.org id KAA13052 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ¥DÃD ·R¥xÆW ±z¤@©w­n¥ÎÀô«O¥R¹q¹q¦À ¦U Ãþ ¤T¸¹¹q¦À¤ñ¸û ¹q¦À¯S©Ê Àô«OÆP©Ê¹q¦À ´¶³q¹q¦À ÂìÂð¹q¦À Àô«O Âì ²B¹q¦À ¥i¥R¹q¦¸¼Æ ¹s¦¸ ¹s¦¸ ¬ù¤@¨Õ¦¸ ¤j©ó¤­¨Õ¦¸ §t­«ª÷ÄݦìV·½ µL µL §tÂ𭫪÷ÄÝ µL °ª¯Ó¹q¨Ï¥Î ¾A¦X ¤£¾A¦X ¾A¦X ¾A¦X °ª«ù¤[©Ê ¬O §_ §_ ¬O ¥R¹q°O¾Ð©Ê -- -- ¦³ ¦³ ¦pªG±z·R¥xÆW³o¶ô¤j¦a ½Ð±z¨Ï¥ÎµL¦¾¬VÂì²BÀô«O¥R¹q¹q¦À ¦³¥R¹q°O¾Ð©Êªº¹q¦À ¸ûµLªkµo´§¹q¤O ¥²»Ý§¹¥þ©ñ¹q«á¤~¯à¥R¹q ´ö²L¤T¸¹©Î ¥|¸¹µL¦¾¬VÂì²BÀô«O¥R¹q¹q¦À ºô¸ô°â»ù 99 ¤¸ YUASA NiMH AA or AAA type, NTD 99 Each ´ö²L ª¾¼z«¬¥R¹q¾¹ ? ºô¸ô°â»ù 399 ¤¸ YUASA Recharger of NiMH, NTD 399 Tel: (03)3278012 BBC: 060224189-099 Mobile: 0933926100 Miss Eileen Lin ªL¤p©j To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 11:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16660 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 11:34:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16655 for ; Tue, 27 Oct 1998 11:34:29 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA09120; Tue, 27 Oct 1998 11:33:38 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <36362011.1235F2E1@gorean.org> Date: Tue, 27 Oct 1998 11:33:37 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1026 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sebastian Lederer CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: <3634F865.9755D2E7@bonn-online.com> <3635180F.BA6C6F92@gorean.org> <3636067E.7C2249A3@bonn-online.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sebastian Lederer wrote: > > Studded wrote: > > > Sebastian Lederer wrote: > > > > > > Hi, > > > > > > How about the following patch to src/sys/i386/isa/wd.c ? It fills in the > > > disk model name (and disk type) when reading the in-core disk label via > > > the DIOCGDINFO ioctl(), if it has not already been set. Tested and > > > working on a couple of machines. It's just a simple way for userland > > > programs to identify IDE disks by name (which is what I need for a > > > FreeBSD installation program). > > > > This compiles and runs fine on -stable, any chance you could supply > > code that would show me the label? I think this is a fine idea, and I'd > > You can use disklabel(8) on the raw disk device, e.g. "disklabel /dev/rwd0", > or maybe"disklabel /dev/rwd0 | grep label". Ok, tried that and the "label: " slot is blank. I have a WD Caviar 1.6G EIDE drive that's about 2 years old if that helps you any. > > even like to see it in the boot message. More information provided to > > the user is always a good thing. > > Why in the boot message? The kernel already prints the model name when probing > the disks, > if that's what you mean? Mine prints out: wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S As opposed to: (ahc0:0:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4134MB (8467200 512 byte sectors) For my scsi disk. Users like to see information in the boot probes, and providing something they recognize adds a level of comfort to the complex and confusing boot probes. It's just an idea. :) Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 11:42:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17251 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 11:42:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17246 for ; Tue, 27 Oct 1998 11:42:05 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA24928; Tue, 27 Oct 1998 14:41:23 -0500 (EST) Message-ID: <19981027144123.A24749@netmonger.net> Date: Tue, 27 Oct 1998 14:41:23 -0500 From: Christopher Masto To: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <3634F865.9755D2E7@bonn-online.com> <3635180F.BA6C6F92@gorean.org> <3636067E.7C2249A3@bonn-online.com> <36362011.1235F2E1@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36362011.1235F2E1@gorean.org>; from Studded on Tue, Oct 27, 1998 at 11:33:37AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 27, 1998 at 11:33:37AM -0800, Studded wrote: > > > even like to see it in the boot message. More information provided to > > > the user is always a good thing. > > > > Why in the boot message? The kernel already prints the model name > > when probing the disks, if that's what you mean? > > Mine prints out: wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, > 63 S/T, 512 B/S > As opposed to: > (ahc0:0:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 4134MB (8467200 512 byte sectors) wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, accel, dma, iordis If you're not getting that information during boot, and you're not getting it with the disklabel patch, perhaps your drive doesn't supply it. -- Christopher Masto Director of Operations S NetMonger Communications chris@netmonger.net info@netmonger.net SSS http://www.netmonger.net \_/ In a manner that would have left the robber barons of the late 19th century gaping in absolute awe, Microsoft is approaching something unprecedented: a monopoly that could well own the choke points of tomorrow's commerce and communications. - DAN GILLMOR, San Jose Mercury News Computing Editor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 11:45:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17619 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 11:45:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17613 for ; Tue, 27 Oct 1998 11:45:25 -0800 (PST) (envelope-from jobaldwi@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id OAA08643; Tue, 27 Oct 1998 14:44:44 -0500 (EST) Received: from john.baldwinfamily.org (jobaldwi.campus.vt.edu [198.82.67.63]) by sable.cc.vt.edu (8.8.8/8.8.8) with ESMTP id OAA31814; Tue, 27 Oct 1998 14:44:43 -0500 (EST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <36362011.1235F2E1@gorean.org> Date: Tue, 27 Oct 1998 14:44:42 -0500 (EST) Reply-To: jobaldwi@vt.edu Organization: Virginia Tech From: John Baldwin To: Studded Subject: Re: Patch for src/sys/i386/isa/wd.c Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- On 27-Oct-98 Studded wrote: > > Mine prints out: wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, > 63 S/T, 512 B/S > As opposed to: > (ahc0:0:0): "IBM DCAS-34330W S65A" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 4134MB (8467200 512 byte sectors) > > For my scsi disk. Users like to see information in the boot probes, and > providing something they recognize adds a level of comfort to the > complex and confusing boot probes. It's just an idea. :) Hmmm... my kernel (without the patch: 2.2.7-Stable as of 21 October 98) displays the following: ... wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 6485MB (13281408 sectors), 13176 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 1625MB (3329424 sectors), 3303 cyls, 16 heads, 63 S/T, 512 B/S ... Which displays the name as you can see. Your WD drive should have a model, such as "WDC AC21600" or something remotely similar that you should see in your dmesg. - --- John Baldwin -- http://members.freedomnet.com/~jbaldwin/ PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc Of course I'm sane. The voices said so. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNjYinojYza302vYpAQG2lAL/Tp/1sdaKOMX1jeLkZ2cIuHHZjbqu6yJI fdEf/xtcDH3DcrQhY5pfQofa3OiKbF7cWDTq3DNZJmQBL84BAerNHfwvwpb82wwf SjBq8WWBuoBeQKXsw1GYCjqxyqMpOvZU =uB1I -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 12:09:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19745 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 12:09:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19740 for ; Tue, 27 Oct 1998 12:08:59 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id MAA09524; Tue, 27 Oct 1998 12:08:16 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <3636282F.42DA5C54@gorean.org> Date: Tue, 27 Oct 1998 12:08:15 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1026 i386) X-Accept-Language: en MIME-Version: 1.0 To: jobaldwi@vt.edu CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > Your WD drive should have a model, > such as "WDC AC21600" or something remotely similar that you should see in your > dmesg. D'oh! wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S Since it said "WDC" I assumed it was talking about the controller. :) It would be nicer if it said, "Wester Digital Caviar" but I'll stop now while I'm behind. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 12:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19876 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 12:11:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19870 for ; Tue, 27 Oct 1998 12:11:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00912; Tue, 27 Oct 1998 12:09:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810272009.MAA00912@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto cc: hackers@FreeBSD.ORG Subject: Re: Some curiosity about syscons In-reply-to: Your message of "Mon, 26 Oct 1998 23:02:08 EST." <19981026230208.A8159@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 12:09:58 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyway.. I wasn't quite sure what the best approach would be, so I > decided to see if I would just luck out and need no more than stdio > and some cheating. It turns out, of course, that syscons doesn't > simply put what you send it on the screen; it puts it into a buffer > which is copied to the screen periodically, so I couldn't trivially > make it work. > > Rather than back up and start over with a different approach, I added > a tiny ioctl to syscons to call scrn_update(). With that and some > fudging, I actually have the damned thing working. You could just have memory-mapped the display buffer, of course. 8) > If anyone is still following this, and particularly if you Know From > Experience, perhaps you can comment on some of these architectural > issues. I need a 60Hz vertical refresh rate, and I need to be able to > display 18 lines of text every frame. This needs to happen during the > vertical retrace interval, as a single glitched frame will cause a > failure. Ideally I would like the cursor not to be present, but it > isn't actually a problem if I can make sure it is always at the top or > bottom of the screen. This *definitely* wants to be done inside the kernel. Use the screensaver interface, add a couple of ioctls (pass data to saver, activate saver) and you're done. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 12:13:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20074 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 12:13:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20069 for ; Tue, 27 Oct 1998 12:13:27 -0800 (PST) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com ([194.162.223.187]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id VAA01782; Tue, 27 Oct 1998 21:12:29 +0100 Message-ID: <36362945.81950EC7@bonn-online.com> Date: Tue, 27 Oct 1998 21:12:53 +0100 From: Sebastian Lederer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Studded , freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: <3634F865.9755D2E7@bonn-online.com> <3635180F.BA6C6F92@gorean.org> <3636067E.7C2249A3@bonn-online.com> <36362011.1235F2E1@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Studded wrote: > > > > You can use disklabel(8) on the raw disk device, e.g. "disklabel /dev/rwd0", > > or maybe"disklabel /dev/rwd0 | grep label". > > Ok, tried that and the "label: " slot is blank. I have a WD Caviar 1.6G > EIDE drive that's about 2 years old if that helps you any. > Do you use 2.2-stable or 3.0-RELEASE ? The generic diskslice code in 2.2.x leaves the packname in the disklabel blank, while in 3.0 it puts "fictitious" in. My patch checks only for the 3.0 case. > > > even like to see it in the boot message. More information provided to > > > the user is always a good thing. > > > > Why in the boot message? The kernel already prints the model name when probing > > the disks, > > if that's what you mean? > > Mine prints out: wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, > 63 S/T, 512 B/S > That's strange, I usually see something like this on IDE probes: wdc0: unit 0 (wd0): wd0: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S and in particular on a machine with a 2GB WD Caviar drive: wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 13:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23805 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 13:01:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23791 for ; Tue, 27 Oct 1998 13:01:24 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id NAA00280; Tue, 27 Oct 1998 13:00:47 -0800 (PST) Message-ID: <19981027130042.B26513@Alameda.net> Date: Tue, 27 Oct 1998 13:00:46 -0800 From: Ulf Zimmermann To: Studded , jobaldwi@vt.edu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c Reply-To: ulf@Alameda.net References: <3636282F.42DA5C54@gorean.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <3636282F.42DA5C54@gorean.org>; from Studded on Tue, Oct 27, 1998 at 12:08:15PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Oct 27, 1998 at 12:08:15PM -0800, Studded wrote: > John Baldwin wrote: > > > Your WD drive should have a model, > > such as "WDC AC21600" or something remotely similar that you should see in your > > dmesg. > > D'oh! > > wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa > wdc0: unit 0 (wd0): , 32-bit, multi-block-16 > wd0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S > > Since it said "WDC" I assumed it was talking about the controller. :) > It would be nicer if it said, "Wester Digital Caviar" but I'll stop now > while I'm behind. WDC stands for "Western Digital Corporation", not for "Caviar". > > Doug > -- > *** Chief Operations Officer, DALnet IRC network *** > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 15:20:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10080 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 15:20:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10065 for ; Tue, 27 Oct 1998 15:20:52 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id XAA17820; Tue, 27 Oct 1998 23:20:12 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 27 Oct 1998 23:13:28 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <3.0.5.32.19981027164356.0090a7c0@mail.scancall.no> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 27 Oct 1998 23:13:26 +0000 To: Alfred Perlstein From: Bob Bishop Subject: Re: dropping to single user mode on a telnet connection Cc: Marius Bendiksen , "Ron G. Minnich" , hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 11:00 am -0500 27/10/98, Alfred Perlstein wrote: >On Tue, 27 Oct 1998, Marius Bendiksen wrote: > >> >Interesting idea passed to me by john degood, who used to work at hp. >> >> Indeed. This is a quite interesting idea. >> >> >On hpux, when you drop to single user via a telnet connection, it leaves >> >the connection open.[etc] The classical way to do this (SysVr2 IIRC) is to have console output go to /dev/syscon, which gets (hard) linked to whichever device is appropriate when the music stops (often /dev/console). This means that kernel internals have to access the console by name not via maj/min 0/0. Care is required: you don't want the console attached to a vty or pty en route for a reboot, for instance. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 15:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10619 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 15:25:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dt053nb4.san.rr.com (dt053nb4.san.rr.com [204.210.34.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10601 for ; Tue, 27 Oct 1998 15:24:59 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053nb4.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA13345; Tue, 27 Oct 1998 15:23:47 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <36365603.3FCA1C60@gorean.org> Date: Tue, 27 Oct 1998 15:23:47 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1026 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sebastian Lederer CC: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: <3634F865.9755D2E7@bonn-online.com> <3635180F.BA6C6F92@gorean.org> <3636067E.7C2249A3@bonn-online.com> <36362011.1235F2E1@gorean.org> <36362945.81950EC7@bonn-online.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sebastian Lederer wrote: > Do you use 2.2-stable or 3.0-RELEASE ? -Stable. Sorry if I wasn't clear. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 15:25:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10738 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 15:25:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10733 for ; Tue, 27 Oct 1998 15:25:36 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA29109; Tue, 27 Oct 1998 15:24:57 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma029103; Tue Oct 27 15:24:28 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA13877; Tue, 27 Oct 1998 15:24:28 -0800 (PST) From: Archie Cobbs Message-Id: <199810272324.PAA13877@bubba.whistle.com> Subject: Re: mounting multiple /proc's In-Reply-To: from Ryan Ziegler at "Oct 23, 98 12:42:59 pm" To: ziggy@wopr.inetu.net (Ryan Ziegler) Date: Tue, 27 Oct 1998 15:24:27 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ryan Ziegler writes: > Is it possible, safe, and atleast mildly efficient to mount /proc, say, 25 > times? I have tried mounting it twice on 2.2.5, and every program that > uses /proc became out-of-synch. However, I cannot confirm that the cause > was the multiple /proc mountings because I was also playing around with > other possibly-damaging things. I will try this again in the next few days > when I have a spare machine. Suggestions, comments, caveats? What exactly does "out-of-synch" mean? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 16:04:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17280 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 16:04:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17273 for ; Tue, 27 Oct 1998 16:04:29 -0800 (PST) (envelope-from syang@directhit.com) Received: from moe.directhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id TAA13737 for ; Tue, 27 Oct 1998 19:03:50 -0500 (EST) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Tue, 27 Oct 1998 19:03:14 -0500 Message-ID: <839A86AB6CE4D111A52200104B938D4308081A@MOE> From: Steven Yang To: "'freebsd-hackers@freebsd.org'" Subject: FW: Can't get rid of my mbufs. Date: Tue, 27 Oct 1998 19:03:12 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I posted this to freebsd-questions, but nobody responded. Can anybody on this list help me? Thanks, Steven > -----Original Message----- > From: Steven Yang > Sent: Tuesday, October 20, 1998 11:04 AM > To: 'freebsd-questions@freebsd.org' > Subject: Can't get rid of my mbufs. > > Hi, we are running a test on FreeBSD 2.2.6, using Apache 1.2.4 with > FastCGI. We are performing about 100 requests per second over a > high-speed switch. On average, each request returns about 20,000 > bytes, so we are transferring about 2MB/sec. The problem is, our > machine ends up rebooting itself after a couple hours. > Here are some sample outputs after pounding on our machine for over 1 > hour: > # netstat -m > 4449 mbufs in use: > 4437 mbufs allocated to data > 1 mbufs allocated to packet headers > 7 mbufs allocated to protocol control blocks > 4 mbufs allocated to socket names and addresses > 4263/4314 mbuf clusters in use > 9184 Kbytes allocated to network (98% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > #netstat -r > Routing tables > > Internet: > Destination Gateway Flags Refs Use > Netif Expire > default 10.4.18.1 UGSc 1 0 > fxp0 > 10.4.18/24 link#1 UC 0 0 > 10.4.18.1 0:10:7b:a6:a6:e8 UHLW 2 0 > fxp0 684 > moe 0:10:4b:93:8d:43 UHLW 0 43 > fxp0 1186 > 10.4.18.198 0:10:4b:99:c5:e2 UHLW 1 9215795 > fxp0 972 > localhost localhost UH 0 0 > lo0 > > Symptoms: I can sit around for a long time with no network activity, > and the mbufs won't decrease. If I exceed 10,000 mbuf clusters, I'm > in danger of hitting a server reboot. I can kill Apache, but that > doesn't help. My memory usage increases linearly with increasing mbuf > clusters. mbuf clusters only seem to increase under heavy load. > Basically, once an mbuf is allocated, it's never deallocated, and we > don't have memory leaks. > How do I solve this problem? > > Thanks, > Steven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 16:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19584 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 16:23:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ms13.url.com.tw (gemini.accton.com.tw [210.68.148.7]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA19574 for ; Tue, 27 Oct 1998 16:22:57 -0800 (PST) (envelope-from willer@ms13.url.com.tw) Date: Tue, 27 Oct 1998 16:22:57 -0800 (PST) Received: from willer ([202.145.254.42]) by AccSMTP/NT 2.5 (210.68.148.49) [210.68.148.49]; Wed, 28 Oct 1998 04:57:56 +0800 Message-ID: <015e01be01ec$948079f0$8eab91ca@willer.willer.net> From: "willer" To: Subject: =?big5?B?pKOlaaSjqr65RA==?= MIME-Version: 1.0 Content-Type: text/plain; charset="big5" X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by hub.freebsd.org id QAA19578 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ¥D¦®:±z¥i¥H¤£¶R§Ú­Ìªº°Ó«~¡A¦ý¤£¥i¤£ª¾¹D³o­Ó¨Æ¹ê¡H±zª¾¹D¶Ü¡H¦æ°Ê¹q¸Ü·|¾É­P¸£Àù ¦æ°Ê¹q¸Ü·|¾É­P¸£Àù¶Ü?±zª¾¹D¤@¯ë¥«­±¤W¨¾ºÏ¶K¥¬¥\®Ä¤Î¼Æ¾ÚÅã¥Ü¡A½Ð±z¬Ý¥H¤U³ø¾É ¥»°Ó«~¥u·Q±À¼sµ¹·Q¹w¨¾¦æ°Ê¹q¸Ü·|¾É­P¸£Àùµo¥Íªº¤H ­ì»ù$1399¨¾ºÏ¶K¥¬ ªÀ·|³d¥ô½æ:$399¤¸ www.willer.net/eric/index.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 16:23:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19723 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 16:23:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from elektra.ultra.net (elektra.ultra.net [199.232.56.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19712 for ; Tue, 27 Oct 1998 16:23:36 -0800 (PST) (envelope-from syang@directhit.com) Received: from moe.directhit.com ([10.4.18.2]) by elektra.ultra.net (8.8.8/ult.n14767) with ESMTP id TAA13414; Tue, 27 Oct 1998 19:22:27 -0500 (EST) Received: by MOE with Internet Mail Service (5.0.1459.74) id ; Tue, 27 Oct 1998 19:21:47 -0500 Message-ID: <839A86AB6CE4D111A52200104B938D4308081B@MOE> From: Steven Yang To: "'Open Systems Networking'" Cc: "'freebsd-hackers@freebsd.org'" Subject: RE: FW: Can't get rid of my mbufs. Date: Tue, 27 Oct 1998 19:21:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1459.74) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the info. One question remains. Suppose netstat -m tells me that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the important processes and let the machine stay idle for 2 hours. Why does netstat -m still tell me that 7900/8050 mbuf clusters are in use? Basically, I'd wish it would say something like 99/8050 mbuf clusters in use instead. I already have MAXUSERS set to 512. Thanks, Steven > -----Original Message----- > From: Open Systems Networking [SMTP:opsys@mail.webspan.net] > Sent: Tuesday, October 27, 1998 7:17 PM > To: Steven Yang > Subject: Re: FW: Can't get rid of my mbufs. > > > Steven, > > MBUF's do not de-allocate. Once there allocated there allocated, You > only > generate more mbufs when the system needs them if enough have not > already > been allocated. What you need to do is increase maxusers in your > kernel > config to something higher than what it is like 512 or 1024. > > netstat -m shows mbuf useage as im sure your aware of. > You can also add the kernel config option: > options NMBCLUSTERS=10000 > > or something very high. This will give you more room and longer > periods of > time to run your tests. You will just have to keep increasing > nmbclusters > or maxusers until you find the right ammount that lets you perform > your > tests. > > Hope this helps you some. > > Chris > > -- > > "You both seem to be ignoring the fact that the networking market is > driven by so-called 'IT professionals' these days, most of whom can't > tell the difference between an ARP and a carp." --Wes Peters > > ===================================| Open Systems FreeBSD Consulting. > FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # > 20016186 > -----------------------------------| 3335 N. 103 Plaza, Omaha, NE > 68134 > FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net > http://www.freebsd.org | Consulting, Network Engineering, > Security > ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 16:54:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24817 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 16:54:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24808 for ; Tue, 27 Oct 1998 16:54:31 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA05118; Tue, 27 Oct 1998 16:54:57 -0800 (PST) Message-Id: <199810280054.QAA05118@implode.root.com> To: Steven Yang cc: "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 19:03:12 EST." <839A86AB6CE4D111A52200104B938D4308081A@MOE> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 16:54:57 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, I posted this to freebsd-questions, but nobody responded. Can >anybody on this list help me? Since it takes 60 seconds for a connection to go away after it has been closed, 100 requests/second will create an average of 6000 TIME_WAIT connections in addition to your downloads. It's no surprise that you are occasionally hitting your 10000 mbuf clusters configuration limit. The only real solution to this is to further increase the configured mbuf clusters so that you can handle the peaks. Ideally, you want 50% more configured than you expect to use. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 17:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25910 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 17:02:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (host-e186.tidalwave.net [208.213.203.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25839; Tue, 27 Oct 1998 17:02:16 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id UAA00981; Tue, 27 Oct 1998 20:01:32 -0500 (EST) (envelope-from lee) Message-ID: <19981027200132.A977@tidalwave.net> Date: Tue, 27 Oct 1998 20:01:32 -0500 From: Lee Cremeans To: hackers@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Call for help on UDMA on Acer chipsets... Reply-To: lcremean@tidalwave.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got myself a shiny new Seagate Medalist Pro 9140 9GB UDMA drive yesterday, and I noticed as I was setting it up last night, that if I enabled DMA on it, it got the dreaded interrupt timeout spasms people have seen. I think I know why...my motherboard, an Amptron 9600, uses an Acer chipset, which isn't explicitly covered in ide_pci.c...so I've had to do what all those others have had to do, and turn off _all_ IDE DMA support on this drive. :( The purpose of this message is to get some help in fixing this--I can be helpful myself, with coding, testing, etc, but I need someone who has an Acer Aladdin IV+ or Aladdin V chipset, runs 3.0-CURRENT, and can get access to the Acer M1543 data sheet (which is available on the web at acerlabs.com, but it's behind a Username/Password box and I don't know how to register). I think it's a real shame to have to run my drive in PIO mode just because of this. Also, a workaround I can think of for other non-supported chipsets (like SiS) would be to put the drive in Multiword DMA mode 2 instead of UDMA--but I'm not sure if this is possible without stepping on any timing toes, I'll see. -- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 17:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29879 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 17:39:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA29855; Tue, 27 Oct 1998 17:39:30 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA11413; Tue, 27 Oct 1998 20:44:04 -0500 From: Bill Paul Message-Id: <199810280144.UAA11413@skynet.ctr.columbia.edu> Subject: Call for testers for Winbond W89C840F driver To: hackers@FreeBSD.ORG, hardware@FreeBSD.ORG Date: Tue, 27 Oct 1998 20:44:02 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a call for testers for the Winbond W89C840F fast ethernet driver. The Winbond 840F is a tulip clone with a couple of wrinkles: the registers are spaced 4 bytes apart instead of 8 and the receive filter is programmed by writing directly to registers instead of loading a setup frame via the transmit DMA engine. The receive filter also has only one perfect address and a 64-bit multicast hash filter instead of a 16 entry perfect filter ans a 512-bit hash table. The driver source is available from the following locations: http://www.freebsd.org/~wpaul/Winbond/3.0 source for FreeBSD 3.0 http://www.freebsd.org/~wpaul/Winbond/2.2 source for FreeBSD 2.2.x To add the driver to an existing system, do the following: - Download the correct version of if_wb.c and if_wbreg.h for your version of FreeBSD. - Copy if_wb.c and if_wbreg.h to /sys/pci. - Edit /sys/conf/files and add a line that says: pci/if_wb.c optional wb device-driver - Edit your kernel config file (e.g. /sys/i386/conf/GENERIC) and add a line that says: device wb0 - Configure a and compile a new kernel and boot it. So far, the only card I've found that uses the Winbond chip is the Trendware TE100-PCIE (www.trendware.com). Trendware also makes DEC tulip and PNIC adapters. I believe Winbond may make their own cards with this chip as well. Note: - This is the W89C940F is _NOT_ The same as the W89C840F. The 940 is a 10Mbps only NE2000 clone. - The wb driver uses the same 'kludge descriptor' hack as the PNIC driver. I get the idea that the behavior I noticed with the PNIC is par for the course with tulip and tulip-like devices. I think reloading the transmit list base address register is only possible when the transmitter is in the 'stopped' state. Now I defy anybody to tell me how to put the transmitter in the 'stopped' state other than by resetting the chip. As usual, please report successes or failures to wpaul@skynet.ctr.columbia.edu. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 17:44:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00631 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 17:44:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA00626 for ; Tue, 27 Oct 1998 17:44:01 -0800 (PST) (envelope-from rabtter@aye.net) Received: (qmail 14611 invoked by uid 2784); 28 Oct 1998 01:42:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Oct 1998 01:42:06 -0000 Date: Tue, 27 Oct 1998 20:42:06 -0500 (EST) From: Barrett Richardson To: Steven Yang cc: "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-Reply-To: <839A86AB6CE4D111A52200104B938D4308081A@MOE> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you really think your server in production is going to be that heavily loaded search the archives for "large scale server" info (look for blurbs about wcarchive and postings by David Greenman). On Tue, 27 Oct 1998, Steven Yang wrote: > Hi, I posted this to freebsd-questions, but nobody responded. Can > anybody on this list help me? > > Thanks, > Steven > > > -----Original Message----- > > From: Steven Yang > > Sent: Tuesday, October 20, 1998 11:04 AM > > To: 'freebsd-questions@freebsd.org' > > Subject: Can't get rid of my mbufs. > > > > Hi, we are running a test on FreeBSD 2.2.6, using Apache 1.2.4 with > > FastCGI. We are performing about 100 requests per second over a > > high-speed switch. On average, each request returns about 20,000 > > bytes, so we are transferring about 2MB/sec. The problem is, our > > machine ends up rebooting itself after a couple hours. > > Here are some sample outputs after pounding on our machine for over 1 > > hour: > > # netstat -m > > 4449 mbufs in use: > > 4437 mbufs allocated to data > > 1 mbufs allocated to packet headers > > 7 mbufs allocated to protocol control blocks > > 4 mbufs allocated to socket names and addresses > > 4263/4314 mbuf clusters in use > > 9184 Kbytes allocated to network (98% in use) > > 0 requests for memory denied > > 0 requests for memory delayed > > 0 calls to protocol drain routines > > > > #netstat -r > > Routing tables > > > > Internet: > > Destination Gateway Flags Refs Use > > Netif Expire > > default 10.4.18.1 UGSc 1 0 > > fxp0 > > 10.4.18/24 link#1 UC 0 0 > > 10.4.18.1 0:10:7b:a6:a6:e8 UHLW 2 0 > > fxp0 684 > > moe 0:10:4b:93:8d:43 UHLW 0 43 > > fxp0 1186 > > 10.4.18.198 0:10:4b:99:c5:e2 UHLW 1 9215795 > > fxp0 972 > > localhost localhost UH 0 0 > > lo0 > > > > Symptoms: I can sit around for a long time with no network activity, > > and the mbufs won't decrease. If I exceed 10,000 mbuf clusters, I'm > > in danger of hitting a server reboot. I can kill Apache, but that > > doesn't help. My memory usage increases linearly with increasing mbuf > > clusters. mbuf clusters only seem to increase under heavy load. > > Basically, once an mbuf is allocated, it's never deallocated, and we > > don't have memory leaks. > > How do I solve this problem? > > > > Thanks, > > Steven > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 17:59:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02698 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 17:59:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02693 for ; Tue, 27 Oct 1998 17:59:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02572; Tue, 27 Oct 1998 17:58:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280158.RAA02572@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Steven Yang cc: "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 19:21:46 EST." <839A86AB6CE4D111A52200104B938D4308081B@MOE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 17:58:14 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for the info. One question remains. Suppose netstat -m tells me > that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the > important processes and let the machine stay idle for 2 hours. Why does > netstat -m still tell me that 7900/8050 mbuf clusters are in use? > Basically, I'd wish it would say something like 99/8050 mbuf clusters in > use instead. I already have MAXUSERS set to 512. You have an mbuf leak somewhere, where mbufs are being allocated to contain data but never being freed. I'm not aware of any known mbuf leaks in 2.2.7, however you might consider installing the 3.0 release and evaluating it under the same test load. This is something that will typically require a kernel developer to help you with. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 18:29:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06247 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 18:29:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06240 for ; Tue, 27 Oct 1998 18:29:54 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA06105; Tue, 27 Oct 1998 18:30:27 -0800 (PST) Message-Id: <199810280230.SAA06105@implode.root.com> To: Steven Yang cc: "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 19:21:46 EST." <839A86AB6CE4D111A52200104B938D4308081B@MOE> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 18:30:27 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Thanks for the info. One question remains. Suppose netstat -m tells me >that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the >important processes and let the machine stay idle for 2 hours. Why does >netstat -m still tell me that 7900/8050 mbuf clusters are in use? >Basically, I'd wish it would say something like 99/8050 mbuf clusters in >use instead. I already have MAXUSERS set to 512. What does "netstat -n" show? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 18:55:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09019 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 18:55:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09011 for ; Tue, 27 Oct 1998 18:55:17 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA06432; Tue, 27 Oct 1998 18:55:36 -0800 (PST) Message-Id: <199810280255.SAA06432@implode.root.com> To: Mike Smith cc: Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 17:58:14 PST." <199810280158.RAA02572@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 18:55:36 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Thanks for the info. One question remains. Suppose netstat -m tells me >> that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the >> important processes and let the machine stay idle for 2 hours. Why does >> netstat -m still tell me that 7900/8050 mbuf clusters are in use? >> Basically, I'd wish it would say something like 99/8050 mbuf clusters in >> use instead. I already have MAXUSERS set to 512. > >You have an mbuf leak somewhere, where mbufs are being allocated to >contain data but never being freed. We need more info before it can be detemined that there is a "leak". The machine is trying to do more than 8 million connections/day, and there are special considerations when trying to do that. 10000 mbuf clusters almost certainly will not be enough. He may not be able to configure enough, in fact, without changing the kernel VM layout. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 20:24:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16998 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 20:24:54 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16980; Tue, 27 Oct 1998 20:24:51 -0800 (PST) (envelope-from soren@soekris.dk) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) with SMTP id UAA20773; Tue, 27 Oct 1998 20:24:05 -0800 (PST) X-SMTP: helo soren.soekris from soren@soekris.dk server @207.90.187.212 ip 207.90.187.212 Message-ID: <36369C62.1F92@soekris.dk> Date: Tue, 27 Oct 1998 20:24:02 -0800 From: Soren Kristensen Reply-To: soren@soekris.dk Organization: Soekris Engineering X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: lcremean@tidalwave.net CC: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Call for help on UDMA on Acer chipsets... References: <19981027200132.A977@tidalwave.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Lee, I would be happy to help you with a UDMA driver for the Acer Aladdin chipsets, not only to be nice, but also because I'm working on a hardware project using the Aladdin IV+, which eventually are going to run freebsd on UDMA drives :-) First, If you haven't got the datasheets, you can get them on my server: http://www.soekris.dk/ds1543v125.pdf -- M1543 http://www.soekris.dk/ds1543cv08.pdf -- M1543C Note that there is both a M1543 and M1543C, but I think that the UDMA programming is the same, even as the M1543C has a slightly larger IDE buffer. Right now I've got a standard motherboard using the Aladdin IV chipset, and although I'm not a freeBSD programmer, I would be able to do testing, and might be helpful on the really low level stuff. And I will probably have prototypes of my own hardware in 6-8 weeks. Best Regards, Soren Kristensen Soekris Engineering Alameda, CA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 20:25:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17035 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 20:25:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sparks.net (gw.sparks.net [209.222.120.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA17029 for ; Tue, 27 Oct 1998 20:25:19 -0800 (PST) (envelope-from david@sparks.net) Received: from david by sparks.net with smtp (Exim 1.62 #5) id 0zYN8g-0006Cw-00; Tue, 27 Oct 1998 23:23:18 -0500 Date: Tue, 27 Oct 1998 23:23:17 -0500 (EST) From: To: Joe Greco cc: hackers@FreeBSD.ORG, mlnn4@oaks.com.au Subject: Re: Multi-terabyte disk farm In-Reply-To: <199810221747.MAA26363@aurora.sol.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998, Joe Greco wrote: > If you do the raid5 thing, I would recommend clustering drives in a four- > plus-one pattern that gives you three filesystems of 72 or 168GB each per > SCSI chain. This effectively limits the amount of data you need to fsck, > and the amount of potential loss in case of catastrophic failure. It > does drive the price up a bit. Why four + 1? Maybe performance isn't an issue, but don't you stand a real chance of lots of superblocks being on a single drive? 7 + 1 would be a nice number with most rack mount chassis which hold 8 drives. Something I did when hooking up something like this at a previous job was a four + 1 setup (the mylex raid controllers had 5 channels, I didn't have any choice:) where each of the five channels was an independent channel on an external RAID controller. Each channel went to a seperate rack mount chassis, so even if I lost a chassis cable/power supply the thing was still running OK. In that installation performance was an issue, so I hooked 20 drives each up to two raid controllers on two seperate wide scsi busses. However, there's no reason why 40 drives couldn't be connected to a single raid controller (2,500-4,000 or so), for a total of 576 effective GB. With CCD they could even be configured as a single disk drive. Or maybe not, any ufs experts around? > You may not want to start out using vinum, which is relatively new and > untested. I love watching the development, but it's a little new for me to bet *my* job on it:) Besides, external RAID is easily cost justified in a project like this. Hope this helps someone:) --- David Miller ---------------------------------------------------------------------------- It's *amazing* what one can accomplish when one doesn't know what one can't do! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 20:55:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19140 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 20:55:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19096 for ; Tue, 27 Oct 1998 20:55:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00348; Tue, 27 Oct 1998 20:54:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280454.UAA00348@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com cc: Mike Smith , Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 18:55:36 PST." <199810280255.SAA06432@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 20:54:01 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Thanks for the info. One question remains. Suppose netstat -m tells me > >> that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the > >> important processes and let the machine stay idle for 2 hours. Why does > >> netstat -m still tell me that 7900/8050 mbuf clusters are in use? > >> Basically, I'd wish it would say something like 99/8050 mbuf clusters in > >> use instead. I already have MAXUSERS set to 512. > > > >You have an mbuf leak somewhere, where mbufs are being allocated to > >contain data but never being freed. > > We need more info before it can be detemined that there is a "leak". The > machine is trying to do more than 8 million connections/day, and there are > special considerations when trying to do that. 10000 mbuf clusters almost > certainly will not be enough. He may not be able to configure enough, in > fact, without changing the kernel VM layout. If the machine is left idle for 2 hours, and presumably from this we would expect that all open connections were closed, there is nothing that I can think of that could account for nearly eight thousand mbufs allocated for data other than a pile in the bottom of the bit bucket. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 21:01:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19521 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 21:01:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19511 for ; Tue, 27 Oct 1998 21:01:20 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id XAA10438; Tue, 27 Oct 1998 23:00:28 -0600 (CST) From: Joe Greco Message-Id: <199810280500.XAA10438@aurora.sol.net> Subject: Re: Multi-terabyte disk farm In-Reply-To: from "david@sparks.net" at "Oct 27, 98 11:23:17 pm" To: david@sparks.net Date: Tue, 27 Oct 1998 23:00:28 -0600 (CST) Cc: hackers@FreeBSD.ORG, mlnn4@oaks.com.au X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 22 Oct 1998, Joe Greco wrote: > > > If you do the raid5 thing, I would recommend clustering drives in a four- > > plus-one pattern that gives you three filesystems of 72 or 168GB each per > > SCSI chain. This effectively limits the amount of data you need to fsck, > > and the amount of potential loss in case of catastrophic failure. It > > does drive the price up a bit. > > Why four + 1? Maybe performance isn't an issue, but don't you stand a > real chance of lots of superblocks being on a single drive? > > 7 + 1 would be a nice number with most rack mount chassis which hold 8 > drives. A F/W SCSI bus handles 15 devices. 7+1 means that you could have 1 and 7/8 RAID filesystems on a single chain. 4+1 means that you could have 3 RAID filesystems on a single chain. It is usually easier for humans to interpret easy patterns such as that. A 4+1 RAID gets you a 72GB filesystem that will take a long time to fsck. Adding almost double the capacity to the RAID will double the fsck time. Writing to a RAID involves a performance penalty where all drives have to participate in the write process. Involving only five drives instead of eight implies that the other three can be doing something else. If speed is not an issue, and horrible write performance is OK, then the best other option would be to do 14+1 RAID5. There's really very little reason to have any middle ground. The aesthetics of being able to use an eight-wide rack mount chassis is of no concern to me, it is simply a trivial exercise in cabling. Those units are always a problem, anyways, since the only way you can put 8 drives in them without a cabling issue is to run a F/W SCSI bus to each chassis and forget about the other 7 drives that the F/W SCSI would allow you. Since we were explicitly discussing an _inexpensive_ storage solution, it stands to reason that you would want to maximize the number of SCSI busses and also the number of SCSI devices per bus, to minimize the number of disk fileservers that you had. Does this adequately answer your question? > Something I did when hooking up something like this at a previous job was > a four + 1 setup (the mylex raid controllers had 5 channels, I didn't have > any choice:) where each of the five channels was an independent channel on > an external RAID controller. Each channel went to a seperate rack mount > chassis, so even if I lost a chassis cable/power supply the thing was > still running OK. > > In that installation performance was an issue, so I hooked 20 drives each > up to two raid controllers on two seperate wide scsi busses. However, > there's no reason why 40 drives couldn't be connected to a single raid > controller (2,500-4,000 or so), for a total of 576 effective GB. With CCD > they could even be configured as a single disk drive. Or maybe not, any > ufs experts around? > > > You may not want to start out using vinum, which is relatively new and > > untested. > > I love watching the development, but it's a little new for me to bet *my* > job on it:) > > Besides, external RAID is easily cost justified in a project like this. You clearly didn't read the design requirements. To be cost-competitive with a _tape_array_, it is necessary to go for the least expensive storage option. Even the RAID thing is questionable, because it will add to the overall cost. To get 4-8 terabytes of storage with hard drives at this point, with 18GB drives running about $1000, would cost $222K-$444K _just_ for the hard drives without any RAID, any servers, any anything else. They can get an 8 TB tape robot for $100K. The only way to beat that is to bank on the fact that hard drive prices are dropping rapidly (and maybe that they did not factor in the cost of tapes?) Besides, if they were willing to settle for tape, and are able to restore crashed drives from backup tapes, it is quite likely that external RAID is NOT justifiable, particularly on a cost basis. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 21:08:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20009 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 21:08:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20004 for ; Tue, 27 Oct 1998 21:08:46 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA07267; Tue, 27 Oct 1998 21:09:14 -0800 (PST) Message-Id: <199810280509.VAA07267@implode.root.com> To: Mike Smith cc: Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 20:54:01 PST." <199810280454.UAA00348@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 21:09:13 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If the machine is left idle for 2 hours, and presumably from this we >would expect that all open connections were closed That would be presuming too much. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 21:28:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21208 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 21:28:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21201 for ; Tue, 27 Oct 1998 21:28:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00546; Tue, 27 Oct 1998 21:27:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280527.VAA00546@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: dg@root.com cc: Mike Smith , Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 21:09:13 PST." <199810280509.VAA07267@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 21:27:27 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >If the machine is left idle for 2 hours, and presumably from this we > >would expect that all open connections were closed > > That would be presuming too much. How about we ask the tester? Were there still a pile of open connections? I didn't read the refcounts from the routing table, or the other numbers in the 'netstat -m' output as indicative of anything significant in this area. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 21:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21530 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 21:36:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21523 for ; Tue, 27 Oct 1998 21:36:43 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA07503; Tue, 27 Oct 1998 21:37:06 -0800 (PST) Message-Id: <199810280537.VAA07503@implode.root.com> To: Mike Smith cc: Steven Yang , "'Open Systems Networking'" , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 21:27:27 PST." <199810280527.VAA00546@dingo.cdrom.com> From: David Greenman Reply-To: dg@root.com Date: Tue, 27 Oct 1998 21:37:06 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >If the machine is left idle for 2 hours, and presumably from this we >> >would expect that all open connections were closed >> >> That would be presuming too much. > >How about we ask the tester? I already did several messages back. I said "What does netstat -n show?" Note that I'm not asking for -m. I'm interested in the state of the (apparantly still open) connections, not in the memory summaries. -n simply because doing reverse DNS for 6000+ connections might take a very long time. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 22:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24299 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 22:25:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24282; Tue, 27 Oct 1998 22:25:18 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id BAA01457; Wed, 28 Oct 1998 01:27:18 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Wed, 28 Oct 1998 01:27:18 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: lcremean@tidalwave.net cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Call for help on UDMA on Acer chipsets... In-Reply-To: <19981027200132.A977@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From personal experiances with Acer i'd avoid them like the f'ing plague Took 2 tech support people over a week of daily contact before i bit the bullet and manually guessed as to what jumpers where what on a motherboard. One other time i needed jumper info, it only took 3 days of emailing back and forth to get the sheets. After asking why it's not on thier site i was told "it's not something we want the customer to mess with." Anyone familiar with the legal ramifications of having a site up that has anti-testimonials about companies, I have quite a few on my sh*tlist and email corrispondance with these companies to show why. I'm quite sure stuff like that falls under "fair use" no? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Tue, 27 Oct 1998, Lee Cremeans wrote: > I just got myself a shiny new Seagate Medalist Pro 9140 9GB UDMA drive > yesterday, and I noticed as I was setting it up last night, that if I > enabled DMA on it, it got the dreaded interrupt timeout spasms people have > seen. I think I know why...my motherboard, an Amptron 9600, uses an Acer > chipset, which isn't explicitly covered in ide_pci.c...so I've had to do > what all those others have had to do, and turn off _all_ IDE DMA support on > this drive. :( > > The purpose of this message is to get some help in fixing this--I can be > helpful myself, with coding, testing, etc, but I need someone who has an > Acer Aladdin IV+ or Aladdin V chipset, runs 3.0-CURRENT, and can get access > to the Acer M1543 data sheet (which is available on the web at acerlabs.com, > but it's behind a Username/Password box and I don't know how to register). I > think it's a real shame to have to run my drive in PIO mode just because of > this. Also, a workaround I can think of for other non-supported chipsets > (like SiS) would be to put the drive in Multiword DMA mode 2 instead of > UDMA--but I'm not sure if this is possible without stepping on any timing > toes, I'll see. > > > -- > Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) > A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did > $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net > http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 22:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24671 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 22:31:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24666 for ; Tue, 27 Oct 1998 22:30:58 -0800 (PST) (envelope-from marcs@znep.com) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.9.1a/8.9.1) with UUCP id XAA03830; Tue, 27 Oct 1998 23:29:35 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with ESMTP id WAA04556; Tue, 27 Oct 1998 22:30:23 -0800 (PST) Date: Tue, 27 Oct 1998 22:30:23 -0800 (PST) From: Marc Slemko To: Mike Smith cc: Steven Yang , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-Reply-To: <199810280158.RAA02572@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Mike Smith wrote: > > Thanks for the info. One question remains. Suppose netstat -m tells me > > that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the > > important processes and let the machine stay idle for 2 hours. Why does > > netstat -m still tell me that 7900/8050 mbuf clusters are in use? > > Basically, I'd wish it would say something like 99/8050 mbuf clusters in > > use instead. I already have MAXUSERS set to 512. > > You have an mbuf leak somewhere, where mbufs are being allocated to > contain data but never being freed. > > I'm not aware of any known mbuf leaks in 2.2.7, however you might He isn't using 2.2.7, he is using 2.2.6 plus an old verison of Apache. My first recommendation would be to upgrade both. I don't really see that the sort of volume being moved is that huge (it is trivial to do 100 hits/sec on a 20k file on my little p166 using well under 500 mbuf clusters), but a _lot_ can depend on the exact benchmark setup. eg. 5000 simultaneous clients will use a heck of a lot more mbufs than 5 simultaneous clients will, yet both could get similar throughput. SUre, the FastCGI stuff is probably doing something more complex than static files and it does double the total transfered (from fastcgi to the server, from the server to the client), but still... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 22:36:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24943 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 22:36:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24937 for ; Tue, 27 Oct 1998 22:36:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00967; Tue, 27 Oct 1998 22:35:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280635.WAA00967@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Marc Slemko cc: Mike Smith , Steven Yang , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Tue, 27 Oct 1998 22:30:23 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 22:35:20 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > SUre, the FastCGI stuff is probably doing something more complex than > static files and it does double the total transfered (from fastcgi to the > server, from the server to the client), but still... Hmm, I wasn't aware that the fastcgi reference implied a second server. How does it communicate with the server proper? INET domain connection(s)? Local domain connections? Named pipes? Shared memory? It sounds like there might be room there for many mbufs to be legitimately consumed, effectively leaked by the application interaction. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 22:43:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25512 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 22:43:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25505 for ; Tue, 27 Oct 1998 22:43:53 -0800 (PST) (envelope-from marcs@znep.com) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.9.1a/8.9.1) with UUCP id XAA03972; Tue, 27 Oct 1998 23:42:59 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with ESMTP id WAA04817; Tue, 27 Oct 1998 22:43:47 -0800 (PST) Date: Tue, 27 Oct 1998 22:43:47 -0800 (PST) From: Marc Slemko To: Mike Smith cc: Steven Yang , "'freebsd-hackers@freebsd.org'" Subject: Re: FW: Can't get rid of my mbufs. In-Reply-To: <199810280635.WAA00967@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Mike Smith wrote: > > SUre, the FastCGI stuff is probably doing something more complex than > > static files and it does double the total transfered (from fastcgi to the > > server, from the server to the client), but still... > > Hmm, I wasn't aware that the fastcgi reference implied a second server. > How does it communicate with the server proper? INET domain > connection(s)? Local domain connections? Named pipes? Shared memory? TCP connection. Well, ok, I guess that isn't true. It can use a pipe and probably would for local connections. OTOH, I have no idea what version is being used or how it is configured, and I'm no FastCGI expert anyway. > It sounds like there might be room there for many mbufs to be > legitimately consumed, effectively leaked by the application > interaction. Possibly. I would recommend simplifying the test case to just Apache serving a 20k static file and see if that changes things. And, of course, the netstat -n output that dg asked for to see if there is anything legit. If it hasn't been tried already, killing all the Apache and fastcgi processes and anything related and seeing if use drops down would be another possible idea. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 23:23:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28770 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 23:23:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28763 for ; Tue, 27 Oct 1998 23:23:47 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id BAA18457; Wed, 28 Oct 1998 01:21:43 -0600 (CST) Date: Wed, 28 Oct 1998 01:21:42 -0600 From: Dan Nelson To: Joe Greco , david@sparks.net Cc: hackers@FreeBSD.ORG, mlnn4@oaks.com.au Subject: Re: Multi-terabyte disk farm Message-ID: <19981028012142.A18128@emsphone.com> References: <199810280500.XAA10438@aurora.sol.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199810280500.XAA10438@aurora.sol.net>; from "Joe Greco" on Tue Oct 27 23:00:28 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 27), Joe Greco said: > Writing to a RAID involves a performance penalty where all drives > have to participate in the write process. Involving only five drives > instead of eight implies that the other three can be doing something > else. That doesn't make much sense. Writing to a RAID should only involve two drives; the data drive and the drive the parity is on. You read the original parity, read the original data, XOR it out of the parity area, XOR the new data back in, and write the updated data and parity (so 2r + 2w for every write the OS makes). Writes larger than the stripe size should access the multiple data+parity drives all in parallel. You pay a constant penalty for writes when going to RAID5, but the number of drives involved in the array doesn't affect it. You only have to read every drive when one fails and you have to recalculate a drive's contents from the parity data. We have four 27+1 x 9GB external RAID5 boxes that take over 4 hours to recalc when a drive fails. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 23:36:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00290 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 23:36:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from storm.typhoon.co.jp (storm.typhoon.co.jp [202.33.21.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00283 for ; Tue, 27 Oct 1998 23:36:18 -0800 (PST) (envelope-from fbsd@typhoon.co.jp) Received: from typhoon.co.jp (waterfall.typhoon.co.jp [202.33.21.60]) by storm.typhoon.co.jp (8.9.1a/8.9.1/TIS-MX) with ESMTP id QAA05550; Wed, 28 Oct 1998 16:35:35 +0900 (JST) Message-ID: <3636C944.EDBFF71A@typhoon.co.jp> Date: Wed, 28 Oct 1998 16:35:32 +0900 From: FreeBSD4Me X-Mailer: Mozilla 4.07 [en] (Win98; I) MIME-Version: 1.0 To: Terry Lambert CC: hackers@FreeBSD.ORG Subject: Re: Oracle8 Release 8.0.5 for LINUX 2.0.34 References: <199810261857.LAA13957@usr04.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > > Oracle will not run on FreeBSD at this stage. It is likely that it > > > > will not be supported on the 2.2.x family at all. > > > > > > Unless you get the version of Oracle that Oracle sells on their > > > FreeBSD-running NC server, in which case it runs great on 2.2.6 > > > and above. > > > > > > This would incidently make it a FreeBSD issue instead of a Linux > > > emulation issue, killing two birds with one stone. 8-). > > > > Last time I heard from John Dyson on this list about that, the FreeBSD > > version wasn't a publicly available thing. Love to have it, I'm doing a > > Oracle class project now, and it sure would be lovely to have (drool!) > > You don't get if you don't ask. > > In other words, ask them for it. The difference between an internal > and a public release is whether there is a perceived market for the > thing or not. > Any suggestions on how to ask? I've asked via http://www.oracle.com/siteadmin/html/contactus.html whether they have plans to release ANY of their products for FreeBSD. This was a few days ago and I have yet to hear from them. exit(); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 27 23:39:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00543 for freebsd-hackers-outgoing; Tue, 27 Oct 1998 23:39:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00538 for ; Tue, 27 Oct 1998 23:39:05 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id BAA10774 for hackers@freebsd.org; Wed, 28 Oct 1998 01:38:26 -0600 (CST) From: Joe Greco Message-Id: <199810280738.BAA10774@aurora.sol.net> Subject: Re: Multi-terabyte disk farm In-Reply-To: <3.0.3.32.19981028011701.0070082c@bugs.us.dell.com> from Tony Overfield at "Oct 28, 98 01:17:01 am" To: hackers@FreeBSD.ORG Date: Wed, 28 Oct 1998 01:38:26 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 11:00 PM 10/27/98 -0600, you wrote: > >Writing to a RAID involves a performance penalty where all drives have to > >participate in the write process. Involving only five drives instead of > >eight implies that the other three can be doing something else. > > Why would you ever need to write to _all_ of the drives, unless you are > writing an entire data-stripe's worth of data, in which case you'll be > writing to at least that many drives anyway? Never mind, I was thinking of parity regeneration. Too much other stuff going on in my head right now. I was thinking of the specific case where you need to read the other drives in order to calculate the parity. Assuming an initialized RAID, that's an invalid assumption, although you still have to read/write two blocks in that case. There's something else that's nagging at my memory... (I'm spending my day moving 8 million files, so disks are certainly the only thing on my mind right now) ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 00:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05803 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 00:40:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05798; Wed, 28 Oct 1998 00:40:35 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA25063; Wed, 28 Oct 1998 08:41:58 GMT Date: Wed, 28 Oct 1998 08:41:58 +0000 (GMT) From: Doug Rabson To: Nick Hibma cc: Doug Rabson , FreeBSD hackers mailing list Subject: Re: sys/kern/subr_bus.c ? (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Nick Hibma wrote: > > Has the options file been updated? > > I can't find opt_bus in i386/conf/ or /sys/conf of 27. I forgot to commit sys/conf/options. Thanks for pointing it out. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 01:35:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09328 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 01:35:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09323 for ; Wed, 28 Oct 1998 01:35:26 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id DAA05514; Wed, 28 Oct 1998 03:34:24 -0600 (CST) From: Kevin Day Message-Id: <199810280934.DAA05514@home.dragondata.com> Subject: Re: FW: Can't get rid of my mbufs. In-Reply-To: <199810280230.SAA06105@implode.root.com> from David Greenman at "Oct 27, 98 06:30:27 pm" To: dg@root.com Date: Wed, 28 Oct 1998 03:34:24 -0600 (CST) Cc: syang@directhit.com, opsys@mail.webspan.net, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Thanks for the info. One question remains. Suppose netstat -m tells me > >that 7900/8050 mbuf clusters are in use. Now suppose I stop all of the > >important processes and let the machine stay idle for 2 hours. Why does > >netstat -m still tell me that 7900/8050 mbuf clusters are in use? > >Basically, I'd wish it would say something like 99/8050 mbuf clusters in > >use instead. I already have MAXUSERS set to 512. > > What does "netstat -n" show? > For what it's worth.... I've got something similar.... Kevin su-2.00# uname -a FreeBSD home.dragondata.com 2.2.5-STABLE FreeBSD 2.2.5-STABLE #0: Fri Feb 20 04:51:48 CST 1998 toasty@home.dragondata.com:/usr/src/sys/compile/HOME i386 su-2.00# uptime 3:32AM up 45 days, 23:10, 7 users, load averages: 0.62, 0.55, 0.37 su-2.00# netstat -m 20655 mbufs in use: 20552 mbufs allocated to data 93 mbufs allocated to packet headers 9 mbufs allocated to protocol control blocks 1 mbufs allocated to socket names and addresses 2514/3778 mbuf clusters in use 10137 Kbytes allocated to network (75% in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines su-2.00# netstat -n Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 204.137.237.2.80 195.100.148.119.1637 SYN_RCVD tcp 0 0 204.137.237.2.80 205.188.154.69.13376 TIME_WAIT tcp 0 0 204.137.237.2.80 194.39.131.69.39055 TIME_WAIT tcp 0 0 204.137.237.2.80 205.188.154.1.3246 TIME_WAIT tcp 0 0 204.137.237.2.80 152.163.213.74.54125 TIME_WAIT tcp 0 0 204.137.237.2.110 208.149.230.5.62917 TIME_WAIT tcp 0 15728 204.137.237.2.80 139.142.128.201.1733 ESTABLISHED tcp 0 0 204.137.237.2.80 203.237.104.38.1876 ESTABLISHED tcp 0 6070 204.137.237.2.80 152.170.245.110.1252 FIN_WAIT_1 tcp 0 17520 204.137.237.2.80 152.170.245.110.1251 ESTABLISHED tcp 0 16060 204.137.237.2.80 152.170.245.110.1250 ESTABLISHED tcp 0 0 204.137.237.2.80 193.190.148.4.2347 TIME_WAIT tcp 0 16535 204.137.237.2.80 209.48.17.56.1628 ESTABLISHED tcp 0 0 204.137.237.2.80 203.237.104.38.1871 ESTABLISHED tcp 0 0 204.137.237.2.80 205.188.154.130.58346 TIME_WAIT tcp 0 12778 204.137.237.2.80 206.169.228.16.1105 ESTABLISHED tcp 0 0 204.137.237.2.80 129.94.6.30.1772 TIME_WAIT tcp 0 0 204.137.237.2.80 129.94.6.30.1736 TIME_WAIT tcp 0 0 204.137.237.2.80 205.186.214.192.3379 ESTABLISHED tcp 0 0 204.137.237.2.80 193.159.122.38.1627 FIN_WAIT_2 tcp 0 4905 204.137.237.2.80 193.159.122.38.1626 ESTABLISHED tcp 0 0 204.137.237.2.80 193.159.122.38.1625 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 199.35.98.187.1185 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 199.35.98.187.1184 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 206.130.189.78.1451 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 193.159.122.38.1622 ESTABLISHED tcp 0 1126 204.137.237.2.80 202.96.183.110.1566 FIN_WAIT_1 tcp 0 0 204.137.237.2.80 195.122.206.23.1359 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 209.240.200.31.38372 TIME_WAIT tcp 0 0 204.137.237.2.80 209.240.200.31.38371 TIME_WAIT tcp 0 0 204.137.237.2.80 209.240.200.38.55954 TIME_WAIT tcp 0 0 204.137.237.2.80 204.250.57.2.54349 TIME_WAIT tcp 0 0 204.137.237.2.80 204.250.57.2.54344 TIME_WAIT tcp 0 0 204.137.237.2.80 194.39.131.69.37724 TIME_WAIT tcp 0 0 204.137.237.2.80 199.35.98.187.1183 TIME_WAIT tcp 0 0 204.137.237.103.80 168.191.215.149.2269 ESTABLISHED tcp 0 15497 204.137.237.103.80 168.191.215.149.2268 ESTABLISHED tcp 0 0 204.137.237.2.80 199.35.98.187.1182 TIME_WAIT tcp 0 0 204.137.237.225.80 166.72.180.37.4742 FIN_WAIT_2 tcp 0 231 204.137.237.2.80 202.96.183.110.1555 FIN_WAIT_1 tcp 0 0 204.137.237.2.80 193.193.157.119.1224 ESTABLISHED tcp 0 15605 204.137.237.101.80 196.6.178.123.1156 ESTABLISHED tcp 0 17520 204.137.237.2.80 194.39.131.69.35745 ESTABLISHED tcp 0 0 204.137.237.225.80 166.72.180.37.4740 FIN_WAIT_2 tcp 0 0 204.137.237.225.80 166.72.180.37.4738 FIN_WAIT_2 tcp 0 0 204.137.237.225.80 166.72.180.37.4737 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 212.10.18.31.61145 FIN_WAIT_2 tcp 0 16616 204.137.237.2.80 204.112.115.46.1157 ESTABLISHED tcp 0 16616 204.137.237.2.80 204.112.115.46.1156 ESTABLISHED tcp 0 0 204.137.237.2.80 194.168.100.162.1185 FIN_WAIT_2 tcp 0 15544 204.137.237.2.80 204.112.115.46.1155 ESTABLISHED tcp 0 15008 204.137.237.2.80 204.112.115.46.1154 ESTABLISHED tcp 0 0 204.137.237.21.80 192.117.131.80.1506 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 209.130.161.79.1782 FIN_WAIT_2 tcp 0 0 204.137.237.21.80 192.117.131.80.1505 FIN_WAIT_2 tcp 0 0 204.137.237.21.80 192.117.131.80.1504 FIN_WAIT_2 tcp 0 8180 204.137.237.21.80 132.70.1.6.38157 CLOSING tcp 0 17520 204.137.237.21.80 132.70.1.6.38156 LAST_ACK tcp 0 83 204.137.237.21.80 132.70.1.6.38149 CLOSING tcp 0 8504 204.137.237.21.80 132.70.1.6.38145 CLOSING tcp 0 2863 204.137.237.21.80 132.70.1.6.38076 LAST_ACK tcp 0 10844 204.137.237.21.80 132.70.1.6.38075 LAST_ACK tcp 0 5091 204.137.237.21.80 132.70.1.6.38074 LAST_ACK tcp 0 17520 204.137.237.101.80 196.6.178.123.1148 ESTABLISHED tcp 0 0 204.137.237.21.80 192.117.131.80.1495 FIN_WAIT_2 tcp 0 16060 204.137.237.103.80 136.159.201.200.1143 ESTABLISHED tcp 0 0 204.137.237.2.80 212.211.29.108.1798 FIN_WAIT_2 tcp 0 0 204.137.237.21.80 195.165.173.96.1261 FIN_WAIT_2 tcp 0 0 204.137.237.21.80 195.165.173.96.1259 FIN_WAIT_2 tcp 0 0 204.137.237.21.80 195.165.173.96.1258 FIN_WAIT_2 tcp 0 0 204.137.237.2.80 160.135.100.249.1364 FIN_WAIT_2 tcp 0 17520 204.137.237.103.80 206.105.172.86.1488 ESTABLISHED tcp 0 0 127.0.0.1.53 *.* LISTEN tcp 0 0 10.0.0.2.53 *.* LISTEN tcp 0 0 204.137.237.148.53 *.* LISTEN tcp 0 0 204.137.237.147.53 *.* LISTEN tcp 0 0 204.137.237.146.53 *.* LISTEN tcp 0 0 204.137.237.145.53 *.* LISTEN tcp 0 0 204.137.237.144.53 *.* LISTEN tcp 0 0 204.137.237.143.53 *.* LISTEN tcp 0 0 204.137.237.142.53 *.* LISTEN tcp 0 0 204.137.237.141.53 *.* LISTEN tcp 0 0 204.137.237.138.53 *.* LISTEN tcp 0 0 204.137.237.140.53 *.* LISTEN tcp 0 0 204.137.237.137.53 *.* LISTEN tcp 0 0 204.137.237.135.53 *.* LISTEN tcp 0 0 204.137.237.136.53 *.* LISTEN tcp 0 0 204.137.237.134.53 *.* LISTEN tcp 0 0 204.137.237.133.53 *.* LISTEN tcp 0 0 205.253.12.2.53 *.* LISTEN tcp 0 0 204.137.237.131.53 *.* LISTEN tcp 0 0 204.137.237.130.53 *.* LISTEN tcp 0 0 204.137.237.129.53 *.* LISTEN tcp 0 0 204.137.237.125.53 *.* LISTEN tcp 0 0 204.137.237.128.53 *.* LISTEN tcp 0 0 204.137.237.127.53 *.* LISTEN tcp 0 0 204.137.237.126.53 *.* LISTEN tcp 0 0 204.137.237.124.53 *.* LISTEN tcp 0 0 204.137.237.120.53 *.* LISTEN tcp 0 0 204.137.237.221.53 *.* LISTEN tcp 0 0 204.137.237.229.53 *.* LISTEN tcp 0 0 204.137.237.227.53 *.* LISTEN tcp 0 0 204.137.237.226.53 *.* LISTEN tcp 0 0 204.137.237.225.53 *.* LISTEN tcp 0 0 204.137.237.224.53 *.* LISTEN tcp 0 0 204.137.237.220.53 *.* LISTEN tcp 0 0 204.137.237.119.53 *.* LISTEN tcp 0 0 204.137.237.115.53 *.* LISTEN tcp 0 0 204.137.237.114.53 *.* LISTEN tcp 0 0 204.137.237.16.53 *.* LISTEN tcp 0 0 204.137.237.17.53 *.* LISTEN tcp 0 0 204.137.237.15.53 *.* LISTEN tcp 0 0 204.137.237.113.53 *.* LISTEN tcp 0 0 204.137.237.112.53 *.* LISTEN tcp 0 0 204.137.237.111.53 *.* LISTEN tcp 0 0 204.137.237.23.53 *.* LISTEN tcp 0 0 204.137.237.109.53 *.* LISTEN tcp 0 0 204.137.237.107.53 *.* LISTEN tcp 0 0 204.137.237.106.53 *.* LISTEN tcp 0 0 204.137.237.104.53 *.* LISTEN tcp 0 0 204.137.237.103.53 *.* LISTEN tcp 0 0 204.137.237.22.53 *.* LISTEN tcp 0 0 204.137.237.102.53 *.* LISTEN tcp 0 0 204.137.237.101.53 *.* LISTEN tcp 0 0 204.137.237.20.53 *.* LISTEN tcp 0 0 204.137.237.21.53 *.* LISTEN tcp 0 0 204.137.237.14.53 *.* LISTEN tcp 0 0 204.137.237.13.53 *.* LISTEN tcp 0 0 204.137.237.12.53 *.* LISTEN tcp 0 0 204.137.237.11.53 *.* LISTEN tcp 0 0 204.137.237.10.53 *.* LISTEN tcp 0 0 204.137.237.2.53 *.* LISTEN tcp 0 5710 204.137.237.2.80 132.170.27.133.1507 LAST_ACK tcp 0 0 204.137.237.2.23 207.181.71.175.1069 ESTABLISHED tcp 0 3828 204.137.237.2.80 152.203.205.84.7580 LAST_ACK tcp 0 0 204.137.237.2.22 204.137.237.4.2749 ESTABLISHED tcp 0 3300 204.137.237.2.80 136.159.200.155.1732 LAST_ACK tcp 0 6146 204.137.237.2.80 207.164.143.162.3274 LAST_ACK tcp 0 11780 204.137.237.2.80 152.167.48.21.12327 LAST_ACK tcp 0 14091 204.137.237.2.80 152.167.48.21.12285 LAST_ACK tcp 0 0 204.137.237.2.677 204.137.237.8.22 ESTABLISHED tcp 0 5421 204.137.237.2.80 152.171.51.55.11295 LAST_ACK tcp 0 6686 204.137.237.2.80 142.55.240.170.28724 LAST_ACK tcp 0 1461 204.137.237.2.80 152.168.94.64.8528 LAST_ACK tcp 0 5162 204.137.237.2.80 152.202.18.21.7565 LAST_ACK tcp 0 9695 204.137.237.21.80 194.184.0.170.1961 LAST_ACK tcp 0 13140 204.137.237.2.80 195.34.195.111.2349 LAST_ACK tcp 0 6713 204.137.237.101.80 152.202.136.120.15747 LAST_ACK tcp 0 14426 204.137.237.2.80 152.206.106.24.3329 LAST_ACK tcp 0 0 204.137.237.23.1020 204.101.197.114.2664 ESTABLISHED tcp 0 4013 204.137.237.21.80 146.227.15.144.23126 LAST_ACK tcp 0 1388 204.137.237.2.80 152.169.128.239.11130 LAST_ACK tcp 0 0 204.137.237.2.23 204.137.237.254.11007 ESTABLISHED tcp 0 14600 204.137.237.2.80 195.171.232.134.1557 LAST_ACK tcp 0 388 204.137.237.2.80 195.171.232.134.1555 LAST_ACK tcp 0 863 204.137.237.2.80 152.166.18.207.8289 LAST_ACK tcp 0 11008 204.137.237.2.80 209.83.55.4.16313 LAST_ACK tcp 0 12409 204.137.237.2.80 209.83.55.4.16224 LAST_ACK tcp 0 8540 204.137.237.2.80 152.200.242.115.7894 LAST_ACK tcp 0 3662 204.137.237.2.80 146.227.16.134.26501 LAST_ACK tcp 0 8299 204.137.237.103.80 147.197.179.178.8709 LAST_ACK tcp 0 0 204.137.237.2.113 *.* LISTEN tcp 0 0 204.137.237.2.110 *.* LISTEN tcp 0 0 204.137.237.2.23 *.* LISTEN udp 0 0 127.0.0.1.53 *.* udp 0 0 10.0.0.2.53 *.* udp 0 0 204.137.237.148.53 *.* udp 0 0 204.137.237.147.53 *.* udp 0 0 204.137.237.146.53 *.* udp 0 0 204.137.237.145.53 *.* udp 0 0 204.137.237.144.53 *.* udp 0 0 204.137.237.143.53 *.* udp 0 0 204.137.237.142.53 *.* udp 0 0 204.137.237.141.53 *.* udp 0 0 204.137.237.138.53 *.* udp 0 0 204.137.237.140.53 *.* udp 0 0 204.137.237.137.53 *.* udp 0 0 204.137.237.135.53 *.* udp 0 0 204.137.237.136.53 *.* udp 0 0 204.137.237.134.53 *.* udp 0 0 204.137.237.133.53 *.* udp 0 0 205.253.12.2.53 *.* udp 0 0 204.137.237.131.53 *.* udp 0 0 204.137.237.130.53 *.* udp 0 0 204.137.237.129.53 *.* udp 0 0 204.137.237.125.53 *.* udp 0 0 204.137.237.128.53 *.* udp 0 0 204.137.237.127.53 *.* udp 0 0 204.137.237.126.53 *.* udp 0 0 204.137.237.124.53 *.* udp 0 0 204.137.237.120.53 *.* udp 0 0 204.137.237.221.53 *.* udp 0 0 204.137.237.229.53 *.* udp 0 0 204.137.237.227.53 *.* udp 0 0 204.137.237.226.53 *.* udp 0 0 204.137.237.225.53 *.* udp 0 0 204.137.237.224.53 *.* udp 0 0 204.137.237.220.53 *.* udp 0 0 204.137.237.119.53 *.* udp 0 0 204.137.237.115.53 *.* udp 0 0 204.137.237.114.53 *.* udp 0 0 204.137.237.16.53 *.* udp 0 0 204.137.237.17.53 *.* udp 0 0 204.137.237.15.53 *.* udp 0 0 204.137.237.113.53 *.* udp 0 0 204.137.237.112.53 *.* udp 0 0 204.137.237.111.53 *.* udp 0 0 204.137.237.23.53 *.* udp 0 0 204.137.237.109.53 *.* udp 0 0 204.137.237.107.53 *.* udp 0 0 204.137.237.106.53 *.* udp 0 0 204.137.237.104.53 *.* udp 0 0 204.137.237.103.53 *.* udp 0 0 204.137.237.22.53 *.* udp 0 0 204.137.237.102.53 *.* udp 0 0 204.137.237.101.53 *.* udp 0 0 204.137.237.20.53 *.* udp 0 0 204.137.237.21.53 *.* udp 0 0 204.137.237.14.53 *.* udp 0 0 204.137.237.13.53 *.* udp 0 0 204.137.237.12.53 *.* udp 0 0 204.137.237.11.53 *.* udp 0 0 204.137.237.10.53 *.* udp 0 0 204.137.237.2.53 *.* udp 0 0 204.137.237.2.1031 *.* udp 0 0 204.137.237.2.1030 *.* udp 0 0 204.137.237.2.69 *.* Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr f2595400 dgram 0 0 0 f1ec1794 0 f1a0f794 f2b7cf00 dgram 0 0 f258cd00 0 f23b2e94 0 /var/run/log f2ca1400 dgram 0 0 0 f1ec1794 0 f19d6e14 f25ea500 dgram 0 0 0 f1ec1794 0 f2305294 f28e6900 dgram 0 0 0 f1ec1794 0 f21a3394 f260fc00 dgram 0 0 0 f1ec1794 0 0 f25ac600 dgram 0 0 0 0 0 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 01:37:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09498 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 01:37:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TYO203.gate.nec.co.jp (TYO203.gate.nec.co.jp [202.32.8.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09489 for ; Wed, 28 Oct 1998 01:37:30 -0800 (PST) (envelope-from y-nakaga@ccs.mt.nec.co.jp) Received: from mailsv.nec.co.jp (mailsv-le1 [192.168.1.90]) by TYO203.gate.nec.co.jp (8.9.1a/3.7W98092815) with ESMTP id SAA25925; Wed, 28 Oct 1998 18:36:31 +0900 (JST) Received: from gw.ccs.mt.nec.co.jp (gw.ccs.mt.nec.co.jp [133.201.2.2]) by mailsv.nec.co.jp (8.9.1a/3.7W-MAILSV-NEC) with ESMTP id SAA24896; Wed, 28 Oct 1998 18:36:30 +0900 (JST) Received: from mail.ccs.mt.nec.co.jp (mail.ccs.mt.nec.co.jp [133.201.3.22]) by gw.ccs.mt.nec.co.jp (8.8.8+2.7Wbeta7/3.3W9-GW_CCS) with ESMTP id SAA23459; Wed, 28 Oct 1998 18:31:26 +0900 (JST) Received: from spls63.ccs.mt.nec.co.jp (spls63.ccs.mt.nec.co.jp [172.16.5.30]) by mail.ccs.mt.nec.co.jp (8.9.1a/3.6W-CCS_Master) with ESMTP id SAA10239; Wed, 28 Oct 1998 18:36:27 +0900 (JST) Received: from ccs.mt.nec.co.jp by spls63.ccs.mt.nec.co.jp (8.8.8+2.7Wbeta7/6.4J.6-slave-1.0) id SAA06989; Wed, 28 Oct 1998 18:36:27 +0900 (JST) Message-Id: <199810280936.SAA06989@spls63.ccs.mt.nec.co.jp> To: Roger Hardiman Cc: hackers@FreeBSD.ORG Subject: Re: Need help with PCMCIA code changes. In-reply-to: Your message of "Tue, 27 Oct 1998 17:37:47 GMT" References: <363604EB.15FB@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Wed, 28 Oct 1998 18:36:26 +0900 From: Nakagawa Yoshihisa Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | The current PCMCIA code in -current automatically scans some base | addresses and automatically searches for a free IRQ | to allocate to the PCMCIA controller chip. (see /sysd/pccard/pcic.c) In PAO project, already changed these problem. But, PAO for 3.0-RELESE is now under development. See: http://www.jp.freebsd.org/PAO/ -- Internet Engineering Laboratory, Networking Systems Laboratories, NEC Corporation NAKAGAWA, Yoshihisa y-nakaga@ccs.mt.nec.co.jp nakagawa@jp.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 01:39:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09725 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 01:39:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09714 for ; Wed, 28 Oct 1998 01:39:47 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id EAA28238; Wed, 28 Oct 1998 04:38:59 -0500 (EST) Date: Wed, 28 Oct 1998 04:39:05 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: FreeBSD4Me cc: Terry Lambert , hackers@FreeBSD.ORG Subject: Re: Oracle8 Release 8.0.5 for LINUX 2.0.34 In-Reply-To: <3636C944.EDBFF71A@typhoon.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, FreeBSD4Me wrote: > Any suggestions on how to ask? I've asked via > > http://www.oracle.com/siteadmin/html/contactus.html > > whether they have plans to release ANY of their products for FreeBSD. This was > a few days ago and I have yet to hear from them. Same here, a couple of times, it just goes to a black hole. I wrote john once to see if he had a name of a better person to email than some generic contact for oracle as a whole. But no reply so who knows. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 01:40:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09843 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 01:40:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09835 for ; Wed, 28 Oct 1998 01:40:54 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA10250; Wed, 28 Oct 1998 01:41:19 -0800 (PST) Message-Id: <199810280941.BAA10250@implode.root.com> To: Kevin Day cc: syang@directhit.com, opsys@mail.webspan.net, freebsd-hackers@FreeBSD.ORG Subject: Re: FW: Can't get rid of my mbufs. In-reply-to: Your message of "Wed, 28 Oct 1998 03:34:24 CST." <199810280934.DAA05514@home.dragondata.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 28 Oct 1998 01:41:19 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> What does "netstat -n" show? >> > >For what it's worth.... I've got something similar.... Okay, how about "netstat -rna" ? I'm only interested in the number of entries. What type of ethernet card is in that machine? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 02:05:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11847 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 02:05:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11825 for ; Wed, 28 Oct 1998 02:05:35 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40334>; Wed, 28 Oct 1998 21:04:15 +1100 Date: Wed, 28 Oct 1998 21:04:45 +1100 From: Peter Jeremy Subject: Soft Updates To: hackers@FreeBSD.ORG Message-Id: <98Oct28.210415est.40334@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone ported Kirk's softupdate code to 2.2? The code in /usr/src/contrib/sys/softupdates applies to 3.0 only AFAIK. Also, how does the performance on the softupdate code compare with asynchronous mounts? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 02:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14544 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 02:35:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14538 for ; Wed, 28 Oct 1998 02:35:36 -0800 (PST) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (dialup-b1-29.raytrace.com [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id VAA01075 for ; Wed, 28 Oct 1998 21:34:54 +1100 (EST) Message-Id: <199810281034.VAA01075@mail.aussie.org> From: "Hallam Oaks" To: "hackers@FreeBSD.ORG" Date: Wed, 28 Oct 1998 21:27:59 +1100 Reply-To: "Hallam Oaks" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Multi-terabyte disk farm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all the advice. At the moment we're looking at a solution involving Kingston enclosures and hot-swap trays, hooked up to 56 IBM UltraStore 18.2gb HDD's. We'll be running these off two servers using double-ended SCSI controllers in much the same way as the tertiary disk project does. This gives us 1tb in a single rack ; we add new racks each time we need a new terabyte. We're taking a punt on drive prices going down and capacities going up as we stock the farm over a period of two years to its final capacity of 8tb. We won't be using raid because (a) we don't care about speed, and (b) we don't care if a drive dies and takes its data along with it. All data will be backed up on AIT tape (shelved). This is a usable solution to us since the type of data being stored is very static. It comes in one end, sits there for two years, then is deleted. It doesn't change in the meantime, and in fact it's likely that any drive with >6mo data on it will be spun down. If anyone's interested, and we go ahead with it, I'll let -hackers know how much the thing ended up costing and how well it worked. -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 03:24:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18750 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 03:24:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18745 for ; Wed, 28 Oct 1998 03:24:53 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from cs.strath.ac.uk (posh.dmem.strath.ac.uk [130.159.202.3]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with ESMTP id LAA03852 Wed, 28 Oct 1998 11:24:01 GMT Message-ID: <3636FEC2.F836138D@cs.strath.ac.uk> Date: Wed, 28 Oct 1998 11:23:46 +0000 From: Roger Hardiman Organization: Strathclyde Uni X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Kernel config - passing flags to a PCI device Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to pass flags from a kernel config to a PCI device I would like them in the bt848/878 driver. eg, I would like device bktr0 flags 0x0103 to allow the kernel to tell the driver something about the card. eg Make, Tuner Type. Bye Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 04:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25713 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 04:41:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25708 for ; Wed, 28 Oct 1998 04:41:02 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id HAA08152 for ; Wed, 28 Oct 1998 07:39:29 -0500 (EST) Date: Wed, 28 Oct 1998 07:39:29 -0500 (EST) From: Chuck Robey To: freebsd-hackers@FreeBSD.ORG Subject: silo overflows Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since moving the system to elf, I've been plagued with silo overflows, hundreds of them. They're turning into a real nuisance, since they often are the cause of a ppp hangup. Is there anything I can do to bring them down? I have a 2 processor smp system, p6*166, and the uarts are those integrated into the Tyan Titan II board. If needed, I could stick an old sio*2 card that has a couple real 16550a's inside, in the machine. What do I do? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 05:07:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27186 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 05:07:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27175 for ; Wed, 28 Oct 1998 05:07:09 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA15312; Wed, 28 Oct 1998 14:06:25 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA05335; Wed, 28 Oct 1998 14:06:24 +0100 (MET) Message-ID: <19981028140624.48345@follo.net> Date: Wed, 28 Oct 1998 14:06:24 +0100 From: Eivind Eklund To: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: Soft Updates References: <98Oct28.210415est.40334@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <98Oct28.210415est.40334@border.alcanet.com.au>; from Peter Jeremy on Wed, Oct 28, 1998 at 09:04:45PM +1100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 09:04:45PM +1100, Peter Jeremy wrote: > Has anyone ported Kirk's softupdate code to 2.2? The code in > /usr/src/contrib/sys/softupdates applies to 3.0 only AFAIK. Not officially, at least, and I consider it unlikely there is an unofficial port. > Also, how does the performance on the softupdate code compare > with asynchronous mounts? Softupdates are usually a little better. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 05:25:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA00337 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 05:25:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA00331 for ; Wed, 28 Oct 1998 05:25:43 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id IAA12402; Wed, 28 Oct 1998 08:30:02 -0500 From: Bill Paul Message-Id: <199810281330.IAA12402@skynet.ctr.columbia.edu> Subject: Re: XL0 To: dchapes@borderware.com (Dave Chapeskie) Date: Wed, 28 Oct 1998 08:29:59 -0500 (EST) Cc: hackers@FreeBSD.ORG, netmonger@genesis.ispace.com In-Reply-To: <98Oct26.110114est.115594@gateway.borderware.com> from "Dave Chapeskie" at Oct 26, 98 10:44:05 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Dave Chapeskie had to walk into mine and say: > On Thu, Oct 22, 1998 at 12:43:17PM -0400, Drew Baxter wrote: > > Got my dmesg output for the day.. (this is probably my 2nd day of using my > > XL card instead of a EP0'd 3c509), and i see this.. Anyone able to shed > > some light on it? It runs fine otherwise, not sure if this is killing > > performance when we have this happen or not. > > > > > xl0: transmission error: 82 > [repeats] The latest version of the xl driver tries to avoid these by increasing the transmit reclaim threshold. Note however that according to the manual, these errors only appear with the 3c90xB adapters, not the 3c90x adapters. Consequently, the driver only fiddles with the reclaim threshold if it detects that the adapter is a 3c90xB. This leads me to believe you have a 3c905B-TX instead of a 3c905-TX, although you didn't say so. If you do have a 3c900 or 3c905 and still see the error, then the 3Com manual is lying to me. Like the other mail says, these errors indicate that an error was encountered after the chip had already started deleting the packet from its internal memory. I only recently discovered the command to change the transmit reclaim threshold. The change to increase the threshold happened sometime last week. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 08:31:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16033 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 08:31:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16011; Wed, 28 Oct 1998 08:31:37 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id LAA00990; Wed, 28 Oct 1998 11:30:43 -0500 (EST) (envelope-from lee) Message-ID: <19981028113037.A974@tidalwave.net> Date: Wed, 28 Oct 1998 11:30:37 -0500 From: Lee Cremeans To: Alfred Perlstein , lcremean@tidalwave.net, hackers@FreeBSD.ORG Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Call for help on UDMA on Acer chipsets... Reply-To: lcremean@tidalwave.net References: <19981027200132.A977@tidalwave.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Alfred Perlstein on Wed, Oct 28, 1998 at 01:27:18AM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 01:27:18AM -0500, Alfred Perlstein wrote: > > >From personal experiances with Acer i'd avoid them like the f'ing plague > > Took 2 tech support people over a week of daily contact before i bit the > bullet and manually guessed as to what jumpers where what on a > motherboard. > > One other time i needed jumper info, it only took 3 days of emailing > back and forth to get the sheets. > > After asking why it's not on thier site i was told "it's not something we > want the customer to mess with." We've had some bad problems with Acer America tech support here at work...a server we had blew up (it wasn't being used as a server at the time, thank god), and it took like 3 weeks and lots of BS to get it fixed. Acer Labs seems to be just as bad at providing tech specs on their chipsets as Acer Computer is at jumper setting. All the sites I went to either didn't have the sheet for the M1543, or had it locked behind a Username/Password box. It was only after writing to this list that I got the info I needed. As for the UDMA support, all the really dirty stuff (like handling data flow) has been done already, since all IDE DMA controllers are compatible with the Intel PIIX in that respect. I just have to program the chip to use UDMA mode...it should be done this weekend, barring any unforseen stopgaps. --- Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet) A! JW223 YWD+++^ri P&B++ SL+++^i GDF B&M KK--i MD+++i P++ I++++ Did $++ E5/10/70/3c/73ac/95/96 H2 PonPippi Ay77 M | mailto:lcremean@tidalwave.net http://st-lcremean.tidalwave.net | Powered by FreeBSD 3.0-CURRENT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 09:53:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23689 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 09:53:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23678 for ; Wed, 28 Oct 1998 09:53:30 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA08089; Wed, 28 Oct 1998 12:52:14 -0500 (EST) Date: Wed, 28 Oct 1998 12:52:14 -0500 (EST) From: "Matthew N. Dodd" To: "Ron G. Minnich" cc: Marius Bendiksen , hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Oct 1998, Ron G. Minnich wrote: > It would be even nicer if it could work under ssh. Can some sort of > netcat-based idea work for that too? Why not just have done with the hackery and use serial consoles hooked to terminal servers all living on a private network hooked up to a management/monitoring system? -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 09:54:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23771 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 09:54:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles337.castles.com [208.214.167.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23709 for ; Wed, 28 Oct 1998 09:53:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03858; Wed, 28 Oct 1998 09:52:22 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810281752.JAA03858@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Roger Hardiman cc: hackers@FreeBSD.ORG Subject: Re: Kernel config - passing flags to a PCI device In-reply-to: Your message of "Wed, 28 Oct 1998 11:23:46 GMT." <3636FEC2.F836138D@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 09:52:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it possible to pass flags from a kernel config to a PCI device > I would like them in the bt848/878 driver. > > eg, I would like > device bktr0 flags 0x0103 > > to allow the kernel to tell the driver something about the card. eg > Make, Tuner Type. No. You should be detecting this automatically anyway; that's what PCI is for. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 10:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24339 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 10:00:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24328 for ; Wed, 28 Oct 1998 10:00:18 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA08249; Wed, 28 Oct 1998 12:59:02 -0500 (EST) Date: Wed, 28 Oct 1998 12:59:01 -0500 (EST) From: "Matthew N. Dodd" To: Hallam Oaks cc: "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <199810281034.VAA01075@mail.aussie.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you're using the Kingston stuff I have but one bit of advice for you. Do not integrate the drives, enclosures and carriers yourself. Subtle and many are the ways you will shoot yourself in the foot attempting to integrate them yourselves. On Wed, 28 Oct 1998, Hallam Oaks wrote: > Thanks for all the advice. At the moment we're looking at a solution > involving Kingston enclosures and hot-swap trays, hooked up to 56 IBM > UltraStore 18.2gb HDD's. We'll be running these off two servers using > double-ended SCSI controllers in much the same way as the tertiary disk > project does. This gives us 1tb in a single rack ; we add new racks each > time we need a new terabyte. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 10:05:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24726 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 10:05:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24720 for ; Wed, 28 Oct 1998 10:05:21 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id MAA23577; Wed, 28 Oct 1998 12:04:25 -0600 (CST) Message-ID: <19981028120424.A23573@Denninger.Net> Date: Wed, 28 Oct 1998 12:04:24 -0600 From: Karl Denninger To: "Matthew N. Dodd" , Hallam Oaks Cc: "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm References: <199810281034.VAA01075@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew N. Dodd on Wed, Oct 28, 1998 at 12:59:01PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oh balderdash. I do my own drive integration all the time. Its not difficult; you just have to pay attention to the SCSI rules regarding cabling and such. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. On Wed, Oct 28, 1998 at 12:59:01PM -0500, Matthew N. Dodd wrote: > > If you're using the Kingston stuff I have but one bit of advice for you. > > Do not integrate the drives, enclosures and carriers yourself. > > Subtle and many are the ways you will shoot yourself in the foot > attempting to integrate them yourselves. > > On Wed, 28 Oct 1998, Hallam Oaks wrote: > > Thanks for all the advice. At the moment we're looking at a solution > > involving Kingston enclosures and hot-swap trays, hooked up to 56 IBM > > UltraStore 18.2gb HDD's. We'll be running these off two servers using > > double-ended SCSI controllers in much the same way as the tertiary disk > > project does. This gives us 1tb in a single rack ; we add new racks each > > time we need a new terabyte. > > -- > | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | > | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 10:18:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26064 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 10:18:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ascetic.portal.ca (ascetic.portal.ca [206.87.139.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26059 for ; Wed, 28 Oct 1998 10:18:19 -0800 (PST) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by ascetic.portal.ca (8.8.8/8.8.5) with SMTP id KAA27854; Wed, 28 Oct 1998 10:17:25 -0800 (PST) X-Authentication-Warning: ascetic.portal.ca: cjs owned process doing -bs Date: Wed, 28 Oct 1998 10:17:24 -0800 (PST) From: Curt Sampson To: Kris Kirby cc: FreeBSD hackers mailing list Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: <362EAA40.B215D4A9@airnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Oct 1998, Kris Kirby wrote: > Let's not forget the physical limitations of the host machine. I'm pretty sure > that you'd want to use PCI video cards, and how many PCI slots do you have? On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) cjs -- Curt Sampson 604-257-9400 De gustibus, aut bene aut nihil. Any opinions expressed are mine and mine alone. The most widely ported operating system in the world: http://www.netbsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 10:19:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26174 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 10:19:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from circe.bonn-online.com (circe.bonn-online.com [195.52.214.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26169 for ; Wed, 28 Oct 1998 10:19:34 -0800 (PST) (envelope-from lederer@bonn-online.com) Received: from bonn-online.com (ppp136.dialin.bonn-online.com [194.162.223.136]) by circe.bonn-online.com (8.8.5/8.8.5) with ESMTP id TAA14542; Wed, 28 Oct 1998 19:15:23 +0100 Message-ID: <36375F53.DBCC5CF5@bonn-online.com> Date: Wed, 28 Oct 1998 19:15:47 +0100 From: Sebastian Lederer X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Studded , freebsd-hackers@FreeBSD.ORG Subject: Re: Patch for src/sys/i386/isa/wd.c References: <3634F865.9755D2E7@bonn-online.com> <3635180F.BA6C6F92@gorean.org> <3636067E.7C2249A3@bonn-online.com> <36362011.1235F2E1@gorean.org> <36362945.81950EC7@bonn-online.com> <36365603.3FCA1C60@gorean.org> Content-Type: multipart/mixed; boundary="------------1626A96235A1EC8778B655E1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------1626A96235A1EC8778B655E1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Studded wrote: > Sebastian Lederer wrote: > > > Do you use 2.2-stable or 3.0-RELEASE ? > > -Stable. Sorry if I wasn't clear. > Digging around in the source code, I have found that the slice code only fakes a disklabel for the "whole disk slice", not for ordinary slices which have no label (yet). Given that, I rewrote the patch in a different way which is much less of a kludge and which should also work on -stable as on 3.0. Please test it, if you like. Best regards, Sebastian Lederer -- Sebastian Lederer lederer@bonn-online.com --------------1626A96235A1EC8778B655E1 Content-Type: text/plain; charset=us-ascii; name="wd.c.diff-current" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="wd.c.diff-current" *** sys/i386/isa/wd.c.orig Mon Oct 26 21:49:04 1998 --- sys/i386/isa/wd.c Wed Oct 28 18:47:06 1998 *************** *** 1330,1335 **** --- 1330,1341 ---- label.d_ncylinders = du->dk_dd.d_ncylinders; label.d_secpercyl = du->dk_dd.d_secpercyl; label.d_secperunit = du->dk_dd.d_secperunit; + + label.d_type = DTYPE_ESDI; + strcpy(label.d_typename,"fixed"); + bcopy(du->dk_params.wdp_model, label.d_packname, + sizeof(label.d_packname)); + error = dsopen("wd", dev, fmt, 0, &du->dk_slices, &label, wdstrategy1, (ds_setgeom_t *)NULL, &wd_cdevsw); } --------------1626A96235A1EC8778B655E1 Content-Type: text/plain; charset=us-ascii; name="wd.c.diff-stable" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="wd.c.diff-stable" *** wd.c.orig Wed Oct 28 19:09:41 1998 --- wd.c Wed Oct 28 19:05:50 1998 *************** *** 1196,1201 **** --- 1196,1207 ---- label.d_ncylinders = du->dk_dd.d_ncylinders; label.d_secpercyl = du->dk_dd.d_secpercyl; label.d_secperunit = du->dk_dd.d_secperunit; + + label.d_type = DTYPE_ESDI; + strcpy(label.d_typename,"fixed"); + bcopy(du->dk_params.wdp_model, label.d_packname, + sizeof(label.d_packname)); + error = dsopen("wd", dev, fmt, &du->dk_slices, &label, wdstrategy1, (ds_setgeom_t *)NULL, &wd_bdevsw, &wd_cdevsw); } --------------1626A96235A1EC8778B655E1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 10:21:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26427 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 10:21:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26417 for ; Wed, 28 Oct 1998 10:21:28 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4022.ime.net [209.90.195.32]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id NAA03045; Wed, 28 Oct 1998 13:20:14 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981028131749.00b16da0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 13:18:47 -0500 To: Bill Paul , dchapes@borderware.com (Dave Chapeskie) From: Drew Baxter Subject: Re: XL0 Cc: hackers@FreeBSD.ORG In-Reply-To: <199810281330.IAA12402@skynet.ctr.columbia.edu> References: <98Oct26.110114est.115594@gateway.borderware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah it's a B series according to the box. As it was, my packets weren't getting through with the XL0 driver running (screwup in the ifconfig maybe) so I went back to the ep0 device for now. I'll venture back into the other side sometime next week. At 08:29 AM 10/28/98 -0500, Bill Paul wrote: >Of all the gin joints in all the towns in all the world, Dave Chapeskie >had to walk into mine and say: > >> On Thu, Oct 22, 1998 at 12:43:17PM -0400, Drew Baxter wrote: >> > Got my dmesg output for the day.. (this is probably my 2nd day of using my >> > XL card instead of a EP0'd 3c509), and i see this.. Anyone able to shed >> > some light on it? It runs fine otherwise, not sure if this is killing >> > performance when we have this happen or not. >> > >> > > xl0: transmission error: 82 >> [repeats] > >The latest version of the xl driver tries to avoid these by increasing >the transmit reclaim threshold. Note however that according to the >manual, these errors only appear with the 3c90xB adapters, not the >3c90x adapters. Consequently, the driver only fiddles with the reclaim >threshold if it detects that the adapter is a 3c90xB. This leads me to >believe you have a 3c905B-TX instead of a 3c905-TX, although you didn't >say so. If you do have a 3c900 or 3c905 and still see the error, then the >3Com manual is lying to me. > >Like the other mail says, these errors indicate that an error was >encountered after the chip had already started deleting the packet >from its internal memory. I only recently discovered the command to >change the transmit reclaim threshold. The change to increase the >threshold happened sometime last week. > >-Bill > >-- >============================================================================= >-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu >Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research >Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City >============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" >============================================================================= --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 10:47:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29381 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 10:47:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA29372 for ; Wed, 28 Oct 1998 10:47:38 -0800 (PST) (envelope-from rminnich@Sarnoff.COM) Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id NAA13989; Wed, 28 Oct 1998 13:46:14 -0500 Date: Wed, 28 Oct 1998 13:46:14 -0500 (EST) From: "Ron G. Minnich" X-Sender: rminnich@terra To: "Matthew N. Dodd" cc: Marius Bendiksen , hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Matthew N. Dodd wrote: > Why not just have done with the hackery and use serial consoles hooked to > terminal servers all living on a private network hooked up to a > management/monitoring system? 1) because its one more link in the chain, and links break when you get to reasonable numbers 2) because serial consoles are going away on the next round of motherboards ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA00763 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:00:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA00660 for ; Wed, 28 Oct 1998 11:00:00 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id NAA09305; Wed, 28 Oct 1998 13:58:46 -0500 (EST) Date: Wed, 28 Oct 1998 13:58:46 -0500 (EST) From: "Matthew N. Dodd" To: Karl Denninger cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <19981028120424.A23573@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Karl Denninger wrote: > I do my own drive integration all the time. Its not difficult; you just > have to pay attention to the SCSI rules regarding cabling and such. Are you using the Kingston kit? If not then my reply was not for you. I was specifically addressing the Kingston hardware, and in particular, the hotswap receiving frames and disk boxes. Once the disks and frames are integrated into the enclosures you'll only have to worry about the frequent fan failures. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01067 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:02:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01054 for ; Wed, 28 Oct 1998 11:02:46 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA09419; Wed, 28 Oct 1998 14:01:58 -0500 (EST) Date: Wed, 28 Oct 1998 14:01:58 -0500 (EST) From: "Matthew N. Dodd" To: "Ron G. Minnich" cc: Marius Bendiksen , hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Ron G. Minnich wrote: > On Wed, 28 Oct 1998, Matthew N. Dodd wrote: > > Why not just have done with the hackery and use serial consoles hooked to > > terminal servers all living on a private network hooked up to a > > management/monitoring system? > > 1) because its one more link in the chain, and links break > when you get to reasonable numbers >From the standpoing of someone observing the operation of 100s of machines installed world wide I would have to disagree with you. > 2) because serial consoles are going away on the next round of > motherboards Poor design decision? While leaving the telnet/ssh port open on entering single-user might be useful, I argue that a serial console will be less painful in the long run. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01579 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:07:36 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01573 for ; Wed, 28 Oct 1998 11:07:34 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4022.ime.net [209.90.195.32]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id OAA03090; Wed, 28 Oct 1998 14:05:34 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981028140254.00aa12e0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 14:04:01 -0500 To: "Matthew N. Dodd" , Karl Denninger From: Drew Baxter Subject: Re: Multi-terabyte disk farm Cc: Hallam Oaks , "hackers@FreeBSD.ORG" In-Reply-To: References: <19981028120424.A23573@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:58 PM 10/28/98 -0500, Matthew N. Dodd wrote: >On Wed, 28 Oct 1998, Karl Denninger wrote: >> I do my own drive integration all the time. Its not difficult; you just >> have to pay attention to the SCSI rules regarding cabling and such. > >Are you using the Kingston kit? If not then my reply was not for you. > >I was specifically addressing the Kingston hardware, and in particular, >the hotswap receiving frames and disk boxes. > >Once the disks and frames are integrated into the enclosures you'll only >have to worry about the frequent fan failures. > >-- >| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | >| winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | >| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | Frequent Fan Failures? Makes those Digital Storageworks cabinets come into the limelight.. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01808 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:09:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01799 for ; Wed, 28 Oct 1998 11:09:03 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id TAA22735 Wed, 28 Oct 1998 19:07:52 GMT Message-ID: <36376B89.41C6@cs.strath.ac.uk> Date: Wed, 28 Oct 1998 19:07:53 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Mike Smith CC: hackers@FreeBSD.ORG Subject: Re: Kernel config - passing flags to a PCI device References: <199810281752.JAA03858@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roger wrote > > Is it possible to pass flags from a kernel config to a PCI device > > I would like them in the bt848/878 driver. > > eg, device bktr0 flags 0x0103 > > Mike wrote > No. You should be detecting this automatically > anyway; that's what PCI is for. I agree you can read a manufacturer and model number from PCI chips. Very usefull too. In my case, I need the flags for things you cannot discover from the PCI chipset. CASE 1: The bt848 frame grabber opens in NTSC or PAL mode. Opening in the 'wrong mode' can lock up the bt848 chipset and hang the PC. (believe me, it took 2 weeks to trace this hardware 'feature') Currently there is a kernel option, "BROOKTREE_SYSTEM_DEFAULT" which effects all instances of the driver. I need specific flags to each bt848 card. (just like you can specify flags 0x80ff80ff to the IDE controller) CASE 2: On the Bt848 based frame grabbers, all you can get back from the PCI probe is "Manufacturer - Brooktree" and "model - BT848" Each of the different TV cards based on the bt848 use different tuner types. There is no way to probe the card to determine the tuner type or the OEM of the TV card. Currently, there are more kernel options and even some sysctls to specify this to the kernel driver. I would like this to be in a flags setting for each card. So, back to the question. How can I pass flags to a PCI device? Bye Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:27:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03728 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:27:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03706 for ; Wed, 28 Oct 1998 11:27:16 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4022.ime.net [209.90.195.32]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id OAA03130 for ; Wed, 28 Oct 1998 14:26:41 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981028142017.00a66d10@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 14:25:02 -0500 To: freebsd-hackers@FreeBSD.ORG From: Drew Baxter Subject: Re: Opt_Bus.h Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After synching the source tree, I noticed an additional line in the /sys/kern/subr_bus.c. #include "opt_bus.h" Thing is, this file doesn't come in the source distrib, and a find / -name opt_bus.h results in nothing. I've since remarked out the line. I just wanted to make it to someones attention (I even deleted the subr_bus.c file altogether to resync it) in case maybe I missed out on some secret opt_bus.h debut party. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:54:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07381 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:54:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07376 for ; Wed, 28 Oct 1998 11:54:07 -0800 (PST) (envelope-from crb@ChrisBowman.com) Received: from fermion (fermion [10.0.1.2]) by quark.ChrisBowman.com (8.8.8/8.8.8) with SMTP id PAA02748; Wed, 28 Oct 1998 15:57:07 -0500 (EST) (envelope-from crb@ChrisBowman.com) Message-Id: <199810282057.PAA02748@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Wed, 28 Oct 1998 14:52:43 -0500 To: "Hallam Oaks" From: "Christopher R. Bowman" Subject: Re: Multi-terabyte disk farm Cc: "hackers@FreeBSD.ORG" In-Reply-To: <199810281034.VAA01075@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:27 PM 10/28/98 +1100, Hallam Oaks wrote: >Thanks for all the advice. At the moment we're looking at a solution >involving Kingston enclosures and hot-swap trays, hooked up to 56 IBM >UltraStore 18.2gb HDD's. We'll be running these off two servers using >double-ended SCSI controllers in much the same way as the tertiary disk >project does. This gives us 1tb in a single rack ; we add new racks each >time we need a new terabyte. > >We're taking a punt on drive prices going down and capacities going up >as we stock the farm over a period of two years to its final capacity >of 8tb. > >We won't be using raid because (a) we don't care about speed, and (b) we >don't care if a drive dies and takes its data along with it. All data will >be backed up on AIT tape (shelved). This is a usable solution to us since >the type of data being stored is very static. It comes in one end, sits >there for two years, then is deleted. It doesn't change in the meantime, >and in fact it's likely that any drive with >6mo data on it will be spun >down. > >If anyone's interested, and we go ahead with it, I'll let -hackers know >how much the thing ended up costing and how well it worked. > >-- Chris You might want to take just one more data point on this. Yesterday, IBM announced that they will now be making the Ultrastar 36XP a 36 GB 7200 rpm 7.5ms 4Mb cache disk drive along the lines of their other drives. This drive is available in Ultra2, SSA and FCAL interfaces. This would bring you down to 28 drives and at "IBM estimated the list price of $1,575" (http://www.news.com/News/Item/0,4,27995,00.html?st.ne.2.head) and run you about $44100 for just the drives to give you 1TB of storage. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 11:57:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07654 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 11:57:34 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-97.airnet.net [207.242.81.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07644 for ; Wed, 28 Oct 1998 11:57:31 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id NAA12458; Wed, 28 Oct 1998 13:54:21 -0600 (CST) Message-ID: <3637766B.EF38FD48@airnet.net> Date: Wed, 28 Oct 1998 13:54:19 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: Curt Sampson CC: FreeBSD hackers mailing list Subject: Re: multi-user: multiple consoles in FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Curt Sampson wrote: > On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) If I'm not mistaken, I believe FreeBSD has a problem with PCI busses after the bridges. Hence, not many slots. -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 12:06:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10242 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 12:06:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-97.airnet.net [207.242.81.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10229 for ; Wed, 28 Oct 1998 12:06:45 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id OAA12483; Wed, 28 Oct 1998 14:03:24 -0600 (CST) Message-ID: <3637788B.7912F11A@airnet.net> Date: Wed, 28 Oct 1998 14:03:23 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: "Matthew N. Dodd" CC: hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew N. Dodd wrote: > From the standpoing of someone observing the operation of 100s of machines > installed world wide I would have to disagree with you. And you've obviously not read their web page, have you? > > 2) because serial consoles are going away on the next round of > > motherboards > > Poor design decision? On the contrary. They are doing this in a large cluster. -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 12:11:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12506 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 12:11:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12492 for ; Wed, 28 Oct 1998 12:11:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00430; Wed, 28 Oct 1998 12:10:21 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810282010.MAA00430@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kris Kirby cc: Curt Sampson , FreeBSD hackers mailing list Subject: Re: multi-user: multiple consoles in FreeBSD In-reply-to: Your message of "Wed, 28 Oct 1998 13:54:19 CST." <3637766B.EF38FD48@airnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 12:10:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Curt Sampson wrote: > > On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) > > If I'm not mistaken, I believe FreeBSD has a problem with PCI busses after the > bridges. Hence, not many slots. Nope. There's an Intel box just outside my office with either five or six PCI busses in it (three on the base system, two or three cards with bridges on them). It works fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 12:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12677 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 12:12:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ascetic.portal.ca (ascetic.portal.ca [206.87.139.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12668 for ; Wed, 28 Oct 1998 12:12:13 -0800 (PST) (envelope-from cjs@portal.ca) Received: from localhost (localhost [[UNIX: localhost]]) by ascetic.portal.ca (8.8.8/8.8.5) with SMTP id MAA29733; Wed, 28 Oct 1998 12:11:26 -0800 (PST) X-Authentication-Warning: ascetic.portal.ca: cjs owned process doing -bs Date: Wed, 28 Oct 1998 12:11:25 -0800 (PST) From: Curt Sampson To: Kris Kirby cc: FreeBSD hackers mailing list Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: <3637766B.EF38FD48@airnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Kris Kirby wrote: > Curt Sampson wrote: > > On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) > > If I'm not mistaken, I believe FreeBSD has a problem with PCI busses after the > bridges. Hence, not many slots. Really? So simple things like the Zynx 4-port Ethernet card don't work? If this is indeed the case, at any rate, I can't imagine that this is a feature of FreeBSD, rather than a bug that will be squished as soon as somone gets around to it. cjs -- Curt Sampson 604-257-9400 De gustibus, aut bene aut nihil. Any opinions expressed are mine and mine alone. The most widely ported operating system in the world: http://www.netbsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 13:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18413 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 13:04:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18387 for ; Wed, 28 Oct 1998 13:04:51 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id QAA11871; Wed, 28 Oct 1998 16:04:12 -0500 (EST) Date: Wed, 28 Oct 1998 16:04:10 -0500 (EST) From: "Matthew N. Dodd" To: Kris Kirby cc: hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection In-Reply-To: <3637788B.7912F11A@airnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Kris Kirby wrote: > Matthew N. Dodd wrote: > > From the standpoint of someone observing the operation of 100s of machines > > installed world wide I would have to disagree with you. > And you've obviously not read their web page, have you? You've not been following the thread have you. He said "serial consoles add complexity to the system which tends to make it more unstable/less reliable." I asserted that "based on experience, I don't believe this is the case regarding serial consoles." (for other things added complexity may indeed make for less reliable/more unstable operation. We're talking about plain old simple serial consoles so everything outside of serial consoles is moot.) > > > 2) because serial consoles are going away on the next round of > > > motherboards > > > > Poor design decision? > > On the contrary. They are doing this in a large cluster. > He more or less implied that "we're using serial consoles now, but the next rev of the system we won't be." I labeled this choice as "a poor design decision." referring to the lack of serial consoles on the new systems. == I work at a place that uses a client/server console management system based on Vixie's rtty package. (I believe local mods are Kerberos 5 auth and encryption and real client/server support instead of local access.) Basically you type 'console ' from any machine as any user listed in the ACLs and you are connected to the console port of hostname. Multiple users can connect to the same console and all i/o is logged. Quite nice. I'm pretty sure that Ron Minnich desire to perpetuate this hack due to prolonged exposure to typing 'telnet sometermserver xxxx' to get console access. (Or maybe he drags out a laptop/dumbterm). I'm still trying to duplicate the above setup for myself at home but a bit of code is required to match the stated feature list. Since someone is sure to bring up the fact that more hardware (term servers and a console management server) is less stable I'll answer now by saying "less, but to no noticeable degree." I'm fairly certain the only time I've seen 2511 term-servers reboot is when their power cords get tripped over. A lightly loaded console management server isn't likely to be loaded enough to tickle any bugs, even if it was hosted on a SCO box. :) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 13:24:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20901 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 13:24:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA20875 for ; Wed, 28 Oct 1998 13:23:53 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 4143 invoked by uid 1001); 28 Oct 1998 21:21:56 +0000 (GMT) To: cjs@portal.ca Cc: kris@airnet.net, hackers@FreeBSD.ORG Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: Your message of "Wed, 28 Oct 1998 12:11:25 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 28 Oct 1998 22:21:56 +0100 Message-ID: <4141.909609716@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Really? So simple things like the Zynx 4-port Ethernet card don't work? The ZNYX ZX314 4-port 10 Mbps card worked in FreeBSD more than two years ago. So did other Ethernet multiport cards with builtin PCI bridges. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 13:40:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22363 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 13:40:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22353 for ; Wed, 28 Oct 1998 13:40:25 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id WAA15693; Wed, 28 Oct 1998 22:39:44 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA03457 (5.67b/IDA-1.5); Wed, 28 Oct 1998 22:10:23 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA02283; Wed, 28 Oct 1998 21:38:43 +0100 (CET) From: Wilko Bulte Message-Id: <199810282038.VAA02283@yedi.iaf.nl> Subject: Re: Multi-terabyte disk farm In-Reply-To: <4.1.19981028140254.00aa12e0@genesis.ispace.com> from Drew Baxter at "Oct 28, 98 02:04:01 pm" To: netmonger@genesis.ispace.com (Drew Baxter) Date: Wed, 28 Oct 1998 21:38:43 +0100 (CET) Cc: winter@jurai.net, karl@denninger.net, mlnn4@oaks.com.au, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Drew Baxter wrote... > At 01:58 PM 10/28/98 -0500, Matthew N. Dodd wrote: > >On Wed, 28 Oct 1998, Karl Denninger wrote: > >I was specifically addressing the Kingston hardware, and in particular, > >the hotswap receiving frames and disk boxes. > > > >Once the disks and frames are integrated into the enclosures you'll only > >have to worry about the frequent fan failures. > > > >-- > >| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | > Frequent Fan Failures? Makes those Digital Storageworks cabinets come into > the limelight.. ?? I do these things for a living but don't remember any real problems with the fans. Customers are normally pretty quick to point them out ;-) Tell me more.. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 13:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22370 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 13:40:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22350 for ; Wed, 28 Oct 1998 13:40:23 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id WAA15683; Wed, 28 Oct 1998 22:39:41 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA03524 (5.67b/IDA-1.5); Wed, 28 Oct 1998 22:11:03 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA02297; Wed, 28 Oct 1998 21:39:26 +0100 (CET) From: Wilko Bulte Message-Id: <199810282039.VAA02297@yedi.iaf.nl> Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: from Curt Sampson at "Oct 28, 98 10:17:24 am" To: cjs@portal.ca (Curt Sampson) Date: Wed, 28 Oct 1998 21:39:26 +0100 (CET) Cc: kris@airnet.net, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Curt Sampson wrote... > On Thu, 22 Oct 1998, Kris Kirby wrote: > > > Let's not forget the physical limitations of the host machine. I'm pretty sure > > that you'd want to use PCI video cards, and how many PCI slots do you have? > > On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) If I remember correctly the 8400 can have 144 slots max. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 15:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04280 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 15:40:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04190 for ; Wed, 28 Oct 1998 15:40:43 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id AAA03906; Thu, 29 Oct 1998 00:39:53 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA12912 (5.67b/IDA-1.5); Thu, 29 Oct 1998 00:14:15 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id WAA02987; Wed, 28 Oct 1998 22:14:54 +0100 (CET) From: Wilko Bulte Message-Id: <199810282114.WAA02987@yedi.iaf.nl> Subject: Re: multi-user: multiple consoles in FreeBSD In-Reply-To: from Curt Sampson at "Oct 28, 98 12:11:25 pm" To: cjs@portal.ca (Curt Sampson) Date: Wed, 28 Oct 1998 22:14:54 +0100 (CET) Cc: kris@airnet.net, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Curt Sampson wrote... > On Wed, 28 Oct 1998, Kris Kirby wrote: > > > Curt Sampson wrote: > > > On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) > > > > If I'm not mistaken, I believe FreeBSD has a problem with PCI busses after the > > bridges. Hence, not many slots. > > Really? So simple things like the Zynx 4-port Ethernet card don't work? > > If this is indeed the case, at any rate, I can't imagine that this > is a feature of FreeBSD, rather than a bug that will be squished > as soon as somone gets around to it. Hmmm: FreeBSD 2.2.6-RELEASE #0: Sun Oct 25 22:12:25 CET 1998 root@yedi.iaf.nl:/usr/src/sys/compile/YEDI CPU: AMD-K6tm w/ multimedia extensions (261.96-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 96292864 (94036K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 0 int a irq 14 on pci0:10:0 chip3 rev 2 on pci0:12:0 <<<<<<<<------------------------------*********************** Probing for devices on PCI bus 1: ncr0 rev 4 int a irq 14 on pci1:0:0 ncr0 waiting for scsi devices to settle (ncr0:0:0): "DEC RZ29B (C) DEC 0014" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 15) 4091MB (8380080 512 byte sectors) sd0(ncr0:0:0): with 3708 cyls, 20 heads, and an average 113 sectors/track (ncr0:3:0): "TANDBERG TDC 4200 00A1" type 1 removable SCSI 2 Works fine here... Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 17:12:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00960 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 17:12:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00930 for ; Wed, 28 Oct 1998 17:12:01 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA15081; Wed, 28 Oct 1998 16:37:30 -0800 (PST) Message-ID: <19981028163730.A14495@Alameda.net> Date: Wed, 28 Oct 1998 16:37:30 -0800 From: Ulf Zimmermann To: Wilko Bulte , Curt Sampson Cc: kris@airnet.net, hackers@FreeBSD.ORG Subject: Re: multi-user: multiple consoles in FreeBSD Reply-To: ulf@Alameda.net References: <199810282114.WAA02987@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810282114.WAA02987@yedi.iaf.nl>; from Wilko Bulte on Wed, Oct 28, 1998 at 10:14:54PM +0100 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 10:14:54PM +0100, Wilko Bulte wrote: > As Curt Sampson wrote... > > On Wed, 28 Oct 1998, Kris Kirby wrote: > > > > > Curt Sampson wrote: > > > > On a DEC Alpha 8400? Maybe a couple of hundred. Why? :-) > > > > > > If I'm not mistaken, I believe FreeBSD has a problem with PCI busses after the > > > bridges. Hence, not many slots. > > > > Really? So simple things like the Zynx 4-port Ethernet card don't work? > > > > If this is indeed the case, at any rate, I can't imagine that this > > is a feature of FreeBSD, rather than a bug that will be squished > > as soon as somone gets around to it. Have a Znyx 314 and works fine. > > Hmmm: > > FreeBSD 2.2.6-RELEASE #0: Sun Oct 25 22:12:25 CET 1998 > root@yedi.iaf.nl:/usr/src/sys/compile/YEDI > CPU: AMD-K6tm w/ multimedia extensions (261.96-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x562 Stepping=2 > Features=0x8001bf > real memory = 100663296 (98304K bytes) > avail memory = 96292864 (94036K bytes) > Probing for devices on PCI bus 0: > chip0 rev 3 on pci0:0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > vga0 rev 0 int a irq 14 on pci0:10:0 > chip3 rev 2 on > pci0:12:0 <<<<<<<<------------------------------*********************** > Probing for devices on PCI bus 1: > ncr0 rev 4 int a irq 14 on pci1:0:0 > ncr0 waiting for scsi devices to settle > (ncr0:0:0): "DEC RZ29B (C) DEC 0014" type 0 fixed SCSI 2 > sd0(ncr0:0:0): Direct-Access > sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 15) > 4091MB (8380080 512 byte sectors) > sd0(ncr0:0:0): with 3708 cyls, 20 heads, and an average 113 sectors/track > (ncr0:3:0): "TANDBERG TDC 4200 00A1" type 1 removable SCSI 2 > > Works fine here... > > Wilko > _ ______________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl > |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl > ______________________________________________ Powered by FreeBSD __________ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 17:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01530 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 17:15:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01481 for ; Wed, 28 Oct 1998 17:14:53 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4022.ime.net [209.90.195.32]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id TAA03367; Wed, 28 Oct 1998 19:33:31 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981028192730.00af7730@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 19:28:34 -0500 To: Wilko Bulte From: Drew Baxter Subject: Re: Multi-terabyte disk farm Cc: winter@jurai.net, karl@denninger.net, mlnn4@oaks.com.au, hackers@FreeBSD.ORG In-Reply-To: <199810282038.VAA02283@yedi.iaf.nl> References: <4.1.19981028140254.00aa12e0@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:38 PM 10/28/98 +0100, Wilko Bulte wrote: >As Drew Baxter wrote... >> At 01:58 PM 10/28/98 -0500, Matthew N. Dodd wrote: >> >On Wed, 28 Oct 1998, Karl Denninger wrote: > >> >I was specifically addressing the Kingston hardware, and in particular, >> >the hotswap receiving frames and disk boxes. >> > >> >Once the disks and frames are integrated into the enclosures you'll only >> >have to worry about the frequent fan failures. >> > >> >-- >> >| Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | > >> Frequent Fan Failures? Makes those Digital Storageworks cabinets come into >> the limelight.. > >?? I do these things for a living but don't remember any real problems >with the fans. Customers are normally pretty quick to point them out ;-) > >Tell me more.. > >Wilko That'd be Winter's department, i was just questioning it. Never really wanted to buy anything from Kingston. The Digital Storageworks cabinets look intriguing, but I don't have that kinda green to be tossing around. I guess I'll just keep stacking smaller drives, and look into something inane like RAID in the future. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 17:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08614 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 17:54:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08605 for ; Wed, 28 Oct 1998 17:54:04 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id UAA16162; Wed, 28 Oct 1998 20:52:53 -0500 (EST) Date: Wed, 28 Oct 1998 20:52:53 -0500 (EST) From: "Matthew N. Dodd" To: Drew Baxter cc: Wilko Bulte , karl@denninger.net, mlnn4@oaks.com.au, hackers@FreeBSD.ORG Subject: Re: Multi-terabyte disk farm In-Reply-To: <4.1.19981028192730.00af7730@genesis.ispace.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Drew Baxter wrote: > >> Frequent Fan Failures? Makes those Digital Storageworks cabinets come into > >> the limelight.. > > > >?? I do these things for a living but don't remember any real problems > >with the fans. Customers are normally pretty quick to point them out ;-) > > > >Tell me more.. > > That'd be Winter's department, i was just questioning it. Never > really wanted to buy anything from Kingston. The Digital Storageworks > cabinets look intriguing, but I don't have that kinda green to be > tossing around. I guess I'll just keep stacking smaller drives, and > look into something inane like RAID in the future. I read the DSW comment as "you think Kingston's have fan failures. Wait till you see a DSW." The DSWs on the toasters at work appear to be pretty good though I'm not even remotely involved with that hardware. The experiences with the Kingston enclosures I've had indicate that fan failure is somewhat frequent. 2 of the fans are -inside- the enclosure where it is difficult to hot-swap them. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 17:56:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09084 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 17:56:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09075 for ; Wed, 28 Oct 1998 17:56:40 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4022.ime.net [209.90.195.32]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id UAA03432; Wed, 28 Oct 1998 20:56:27 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981028204823.00aefd40@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 28 Oct 1998 20:49:51 -0500 To: "Matthew N. Dodd" From: Drew Baxter Subject: Re: Multi-terabyte disk farm Cc: Wilko Bulte , karl@denninger.net, mlnn4@oaks.com.au, hackers@FreeBSD.ORG In-Reply-To: References: <4.1.19981028192730.00af7730@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:52 PM 10/28/98 -0500, Matthew N. Dodd wrote: >On Wed, 28 Oct 1998, Drew Baxter wrote: >> >> Frequent Fan Failures? Makes those Digital Storageworks cabinets come into >> >> the limelight.. >> > >> >?? I do these things for a living but don't remember any real problems >> >with the fans. Customers are normally pretty quick to point them out ;-) >> > >> >Tell me more.. >> >> That'd be Winter's department, i was just questioning it. Never >> really wanted to buy anything from Kingston. The Digital Storageworks >> cabinets look intriguing, but I don't have that kinda green to be >> tossing around. I guess I'll just keep stacking smaller drives, and >> look into something inane like RAID in the future. > >I read the DSW comment as "you think Kingston's have fan failures. Wait >till you see a DSW." > >The DSWs on the toasters at work appear to be pretty good though I'm not >even remotely involved with that hardware. > >The experiences with the Kingston enclosures I've had indicate that fan >failure is somewhat frequent. > >2 of the fans are -inside- the enclosure where it is difficult to hot-swap >them. > Heh I'll stick with smaller-level devices for the time being.. I think life is easier that way :) --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 18:05:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10409 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 18:05:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-10.airnet.net [207.242.81.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10400 for ; Wed, 28 Oct 1998 18:05:01 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id UAA13493; Wed, 28 Oct 1998 20:02:35 -0600 (CST) Message-ID: <3637CCB9.1E6A32B9@airnet.net> Date: Wed, 28 Oct 1998 20:02:33 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: "Matthew N. Dodd" CC: hackers@FreeBSD.ORG Subject: Re: dropping to single user mode on a telnet connection References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew N. Dodd wrote: > I labeled this choice as "a poor design decision." referring to the lack > of serial consoles on the new systems. I'll sum up my reaction to this and the other comments from above simply: Your viewpoint is much clearer than my mind interpreted it as. I think I need to recompile my OS with some modifications :-) -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 18:09:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11041 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 18:09:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-10.airnet.net [207.242.81.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11026 for ; Wed, 28 Oct 1998 18:09:07 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id UAA13504; Wed, 28 Oct 1998 20:06:34 -0600 (CST) Message-ID: <3637CDA7.6E8CE1CD@airnet.net> Date: Wed, 28 Oct 1998 20:06:31 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: Wilko Bulte CC: Curt Sampson , hackers@FreeBSD.ORG Subject: Re: multi-user: multiple consoles in FreeBSD References: <199810282114.WAA02987@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > > > If I'm not mistaken, I believe FreeBSD has a problem with PCI busses after the > > > bridges. Hence, not many slots. The above point has very obviously been proven wrong. > Probing for devices on PCI bus 0: > chip0 rev 3 on pci0:0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > chip3 rev 2 on pci0:12:0 Seeing this has brought on a case of deja vu. I recall a friends system outputing something similar to the above, but (as you can tell) I ignored it because the machine ran. :-) My reply: "Gee that was stupid of me." -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 18:12:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11738 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 18:12:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11723 for ; Wed, 28 Oct 1998 18:12:45 -0800 (PST) (envelope-from devinecreations@modempool.com) Received: from imail.modempool.com (imail.modempool.com [198.109.197.5]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id SAA01974 for ; Wed, 28 Oct 1998 18:13:18 -0800 (PST) Received: from devinecreations.com (n2-p188.modempool.com [198.109.216.188]) by imail.modempool.com (Netscape Mail Server v2.01) with ESMTP id AAA188 for ; Wed, 28 Oct 1998 21:15:53 -0500 Message-ID: <3637CEA1.1E4DF2F1@devinecreations.com> Date: Wed, 28 Oct 1998 21:10:41 -0500 From: Steve Devine X-Mailer: Mozilla 4.04 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@freefall.cdrom.com Subject: User utility Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello , I am looking for a batch utility that will add users. Do you know of any? Thanx Freebsd 2.2.7 Steve Devine sdevine@jps.k12.mi.us To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 19:44:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22706 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 19:44:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22699 for ; Wed, 28 Oct 1998 19:44:13 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id LAA26559 for ; Thu, 29 Oct 1998 11:44:06 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id LAA02525; Thu, 29 Oct 1998 11:44:06 +0800 Message-Id: <199810290344.LAA02525@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: The new bootloader - how do you set it up? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 11:44:05 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone give me a pointer? I'm still running an a.out kernel on a system that was installed from a 3.0 snapshot CD and has been kept upto date via cvs since. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 20:47:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00186 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 20:47:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles53.castles.com [208.214.165.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00177 for ; Wed, 28 Oct 1998 20:46:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00420; Wed, 28 Oct 1998 20:46:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810290446.UAA00420@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Thu, 29 Oct 1998 11:44:05 +0800." <199810290344.LAA02525@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Oct 1998 20:46:36 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can someone give me a pointer? I'm still running an a.out kernel on a system > that was installed from a 3.0 snapshot CD and has been kept upto date via cvs > since. make world followed by disklabel -B -b /boot/boot1 -s /boot/boot2 will upgrade you completely. The visible parts of the new loader are in /boot/loader, and are updated by 'make world'. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 22:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08232 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 22:07:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08215 for ; Wed, 28 Oct 1998 22:07:08 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id BAA10318; Thu, 29 Oct 1998 01:04:51 -0500 (EST) Date: Thu, 29 Oct 1998 01:04:50 -0500 (EST) From: Chuck Robey To: Mike Smith cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810290446.UAA00420@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Mike Smith wrote: > > Can someone give me a pointer? I'm still running an a.out kernel on a system > > that was installed from a 3.0 snapshot CD and has been kept upto date via cvs > > since. > > make world > > followed by > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > will upgrade you completely. The visible parts of the new loader are > in /boot/loader, and are updated by 'make world'. Excuse me (I'm worried about doing something inordinately dumb), just to verify, if I do that line above, after a buildworld/installworld, and then build a new kernel with KERNFORMAT set to elf, and install it, I should be running ok, right? All my newly regenned lkms will keep on humming fine, same obj files that powered the aout kernel, right? If I get an answer here, I'll go ahead and take the next step (gulp!) ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 22:40:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11163 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 22:40:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11150 for ; Wed, 28 Oct 1998 22:40:08 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id OAA04511; Thu, 29 Oct 1998 14:38:41 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810290638.OAA04511@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: Mike Smith , Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Thu, 29 Oct 1998 01:04:50 EST." Date: Thu, 29 Oct 1998 14:38:40 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > On Wed, 28 Oct 1998, Mike Smith wrote: > > > > Can someone give me a pointer? I'm still running an a.out kernel on a sys tem > > > that was installed from a 3.0 snapshot CD and has been kept upto date via cvs > > > since. > > > > make world > > > > followed by > > > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > > > will upgrade you completely. The visible parts of the new loader are > > in /boot/loader, and are updated by 'make world'. I'll also mention that this is jumping in at the deep end. You can shortcut and do this: echo "/boot/loader" > /boot.config as an intermediate step and test that. This will cause the existing bootblocks to load the 3rd stage boot loader by default instead of /kernel - but you are not yet committed. You still have the old boot: prompt and can load /kernel.aout explicitly. The command that Mike has given puts the new boot *blocks* on the disk which are not strictly necessary to use the /boot/loader boot loader. You can actually test the new bootloader out by explicitly typing in /boot/loader at the existing boot: prompt. > Excuse me (I'm worried about doing something inordinately dumb), just to > verify, if I do that line above, after a buildworld/installworld, and > then build a new kernel with KERNFORMAT set to elf, and install it, I > should be running ok, right? All my newly regenned lkms will keep on > humming fine, same obj files that powered the aout kernel, right? If you build an ELF kernel, you throw out the lkm's. They are a.out only, because it depends on the a.out 'ld' command. Instead you can use the src/ sys/modules stuff with kldload/kldunload and/or loading them at boot time via the /boot/loader command prompt or the /boot/loader.conf script. One of my machines has: peter@overcee[2:34pm]~src-240> cat /boot/boot.conf load kernel load nfs.ko autoboot 10 This makes the boot loader pull in the kernel and the nfs module, then autoboot in 10 seconds unless it's aborted for further adjustments. > If I get an answer here, I'll go ahead and take the next step (gulp!) If you keep an a.out kernel handy, and use the old (existing) bootblocks to activate /boot/loader, you need not commit until you know it all works to your satisfaction. I use it for all of my machines here. If you have got Really Old (tm) bootblocks (eg: 2.1.x or old 2.2.x vintage), you may like to update to the current a.out bootblocks first. The older bootblocks do not understand /boot.config Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 23:34:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15174 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 23:34:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA15169 for ; Wed, 28 Oct 1998 23:34:35 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id FAA07168; Thu, 29 Oct 1998 05:53:45 +0100 From: Luigi Rizzo Message-Id: <199810290453.FAA07168@labinfo.iet.unipi.it> Subject: compiler prototype question... To: hackers@FreeBSD.ORG Date: Thu, 29 Oct 1998 05:53:44 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, can someone tell me why in the following C program: int c1 (int c); int c1 (char c) { return 1 ; } Hi, can someone tell me why in the following C program: int c1 (int c); int c1 (char c) { return 1 ; } int c2 (int c); int c2 (c) char c; { return 1 ; } int c3 (char c); int c3 (c) int c; { return 1 ;} int c4 (char c); int c4 (int c) { return 1 ;} compiled on 2.2.6 produces this output: prova# cc -c -Wall proto.c proto.c:8: conflicting types for `c1' proto.c:7: previous declaration of `c1' proto.c: In function `c3': proto.c:14: argument `c' doesn't match prototype proto.c:13: prototype declaration proto.c: At top level: proto.c:17: conflicting types for `c4' proto.c:16: previous declaration of `c4' To me, c2() seems as bad as the others, and i don't understand why the compiler does not complain. It seems that when the prototype declares an "int" argument, then any signed/unsigned type is accepted for that argument in the non-ansi function body. As you can imagine this defeats the usefulness of prototypes and obfuscates code. Furthermore, with multiple arguments, i could even be suspicious of how the compiler behaves (e.g. does it push a wordsize argument and then tries to read it as multiple 1 or 2 byte items ?). and the reason i am asking on hackers... there is such code in the kernel, e.g. sys/i386/isa/if_ed.c function ed_get_packet() has this problem and i don't know if it a bug or what. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 23:38:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15360 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 23:38:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from storm.typhoon.co.jp (storm.typhoon.co.jp [202.33.21.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15355 for ; Wed, 28 Oct 1998 23:38:07 -0800 (PST) (envelope-from fbsd@typhoon.co.jp) Received: from typhoon.co.jp (waterfall.typhoon.co.jp [202.33.21.60]) by storm.typhoon.co.jp (8.9.1a/8.9.1/TIS-MX) with ESMTP id QAA12746; Thu, 29 Oct 1998 16:37:31 +0900 (JST) Message-ID: <36381B3A.6677B10@typhoon.co.jp> Date: Thu, 29 Oct 1998 16:37:30 +0900 From: FreeBSD4Me X-Mailer: Mozilla 4.07 [en] (Win98; I) MIME-Version: 1.0 To: Mike Smith CC: hackers@FreeBSD.ORG Subject: LOAD_CONFIG_FILE and unattended install Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike, I found your post regarding "unattended install" while digging through the archive: >We have actually supported unattended installs for some time >through sysinstall's scripting support. If there's an >install.cfg file in the boot image MFS, it's run straight away. >This lets you do everything that sysinstall handles, fully >automatically. I'd tried placing a install.cfg in the boot floopy (2.2.7R) but the usual install menu came up:( Also, according to the sysinstall(8) manpage: If sysinstall is compiled with LOAD_CONFIG_FILE set in the envi-ronment (or in the Makefile) to some value, then that value will be used as the filename to automatically look for and load when sysinstall starts up and with no user interaction required. But when I did a "grep LOAD_CONFIG_FILE *" in /usr/src/release/sysinstall I couldn't find any #ifdef LOAD_CONFIG_FILE lines. In fact the only occurance was in systinall.8! Where did I go wrong? TIA for any pointers. ---end--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 28 23:46:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16364 for freebsd-hackers-outgoing; Wed, 28 Oct 1998 23:46:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16359 for ; Wed, 28 Oct 1998 23:46:31 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id JAA16726 for hackers@FreeBSD.ORG; Thu, 29 Oct 1998 09:46:21 +0200 (SAT) From: John Hay Message-Id: <199810290746.JAA16726@zibbi.mikom.csir.co.za> Subject: kld screensavers To: hackers@FreeBSD.ORG (FreeBSD-hackers) Date: Thu, 29 Oct 1998 09:46:21 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like the kld screensavers hasn't been converted from lkm's to kld's yet. It looks like it has just been moved from the lkm directory to sys/modules. I have converted one of them (daemon_saver) and it seems to be working fine. Is this the kind of chnages needed? Is there something more (or less) needed? If this is ok, I will commit it and do the rest of the screensavers... Or is someone else busy with it... Or is there some other plan? One thing that I'm unsure about is in DECLARE_MODULE() if SI_SUB_PSEUDO is the right one to use for the screen savers. John -- John Hay -- John.Hay@mikom.csir.co.za Index: sys/modules/syscons/daemon/daemon_saver.c =================================================================== RCS file: /home/ncvs/src/sys/modules/syscons/daemon/daemon_saver.c,v retrieving revision 1.11 diff -u -r1.11 daemon_saver.c --- daemon_saver.c 1998/09/17 19:40:30 1.11 +++ daemon_saver.c 1998/10/23 10:29:52 @@ -35,6 +35,7 @@ #include #include #include +#include #include #include @@ -48,8 +49,6 @@ #define DAEMON_MAX_WIDTH 32 #define DAEMON_MAX_HEIGHT 19 -MOD_MISC(daemon_saver); - static char *message; static int messagelen; static u_short *window; @@ -335,35 +334,37 @@ } static int -daemon_saver_load(struct lkm_table *lkmtp, int cmd) +daemon_saver_modevent(module_t mod, modeventtype_t type, void *unused) { int err; - messagelen = strlen(hostname) + 3 + strlen(ostype) + 1 + - strlen(osrelease); - message = malloc(messagelen + 1, M_DEVBUF, M_WAITOK); - sprintf(message, "%s - %s %s", hostname, ostype, osrelease); - - err = add_scrn_saver(daemon_saver); - if (err != 0) - free(message, M_DEVBUF); - return err; + err = 0; + switch (type) { + case MOD_LOAD: + messagelen = strlen(hostname) + 3 + strlen(ostype) + 1 + + strlen(osrelease); + message = malloc(messagelen + 1, M_DEVBUF, M_WAITOK); + sprintf(message, "%s - %s %s", hostname, ostype, osrelease); + + err = add_scrn_saver(daemon_saver); + if (err != 0) + free(message, M_DEVBUF); + break; + case MOD_UNLOAD: + err = remove_scrn_saver(daemon_saver); + if (err == 0) + free(message, M_DEVBUF); + break; + default: + printf("daemon_saver module unknown event: 0x%x\n", type); + } + return(err); } - -static int -daemon_saver_unload(struct lkm_table *lkmtp, int cmd) -{ - int err; - err = remove_scrn_saver(daemon_saver); - if (err == 0) - free(message, M_DEVBUF); - return err; -} +moduledata_t daemon_saver_mod = { + "daemon_saver", + daemon_saver_modevent, + 0 +}; -int -daemon_saver_mod(struct lkm_table *lkmtp, int cmd, int ver) -{ - MOD_DISPATCH(daemon_saver, lkmtp, cmd, ver, - daemon_saver_load, daemon_saver_unload, lkm_nullcmd); -} +DECLARE_MODULE(daemon_saver, daemon_saver_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 01:43:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28996 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 01:43:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from TYO203.gate.nec.co.jp (TYO203.gate.nec.co.jp [202.32.8.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28985 for ; Thu, 29 Oct 1998 01:43:29 -0800 (PST) (envelope-from y-nakaga@ccs.mt.nec.co.jp) Received: from mailsv.nec.co.jp (mailsv-le1 [192.168.1.90]) by TYO203.gate.nec.co.jp (8.9.1a/3.7W98092815) with ESMTP id SAA05291; Thu, 29 Oct 1998 18:43:18 +0900 (JST) Received: from gw.ccs.mt.nec.co.jp (gw.ccs.mt.nec.co.jp [133.201.2.2]) by mailsv.nec.co.jp (8.9.1a/3.7W-MAILSV-NEC) with ESMTP id SAA20582; Thu, 29 Oct 1998 18:43:16 +0900 (JST) Received: from mail.ccs.mt.nec.co.jp (mail.ccs.mt.nec.co.jp [133.201.3.22]) by gw.ccs.mt.nec.co.jp (8.8.8+2.7Wbeta7/3.3W9-GW_CCS) with ESMTP id SAA05551; Thu, 29 Oct 1998 18:38:10 +0900 (JST) Received: from spls63.ccs.mt.nec.co.jp (spls63.ccs.mt.nec.co.jp [172.16.5.30]) by mail.ccs.mt.nec.co.jp (8.9.1a/3.6W-CCS_Master) with ESMTP id SAA07771; Thu, 29 Oct 1998 18:43:10 +0900 (JST) Received: from ccs.mt.nec.co.jp by spls63.ccs.mt.nec.co.jp (8.8.8+2.7Wbeta7/6.4J.6-slave-1.0) id SAA08543; Thu, 29 Oct 1998 18:43:09 +0900 (JST) Message-Id: <199810290943.SAA08543@spls63.ccs.mt.nec.co.jp> To: Ted Faber Cc: Daniel Berlin , hackers@FreeBSD.ORG Subject: Re: Our CardBus support In-reply-to: Your message of "Thu, 22 Oct 1998 14:03:19 MST" References: <199810222103.OAA19358@tnt.isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Date: Thu, 29 Oct 1998 18:43:08 +0900 From: Nakagawa Yoshihisa Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | If you're willing to test the TI code I write, I'm happy to try to | write you some. I just plain don't have a box to test on. Although I | may beg off until my 3.0 CDROM shows up in the mail and I successfully | upgrade. See: http://www.jp.freebsd.org/PAO/ PAO-980913 for 2.2.7-RELEASE, support TI chips. (TI PCI1130, 1131, 1250, ...) But, PAO for 3.0-RELESE is now under development. pao227, that is include CardBus test code, also. -- Internet Engineering Laboratory, Networking Systems Laboratories, NEC Corporation NAKAGAWA, Yoshihisa y-nakaga@ccs.mt.nec.co.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 01:49:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29569 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 01:49:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29564 for ; Thu, 29 Oct 1998 01:49:52 -0800 (PST) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (dialup-b1-29.raytrace.com [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id UAA01503 for ; Thu, 29 Oct 1998 20:49:46 +1100 (EST) Message-Id: <199810290949.UAA01503@mail.aussie.org> From: "Hallam Oaks" To: "hackers@FreeBSD.ORG" Date: Thu, 29 Oct 1998 20:49:12 +1100 Reply-To: "Hallam Oaks" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Multi-terabyte disk farm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If anyone wants to suggest alternative enclosures to the Kingstons then I'm all ears. Nothing in that area is set in stone (yet). -- chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 01:50:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29682 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 01:50:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29677 for ; Thu, 29 Oct 1998 01:50:21 -0800 (PST) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (dialup-b1-29.raytrace.com [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id UAA01506; Thu, 29 Oct 1998 20:49:47 +1100 (EST) Message-Id: <199810290949.UAA01506@mail.aussie.org> From: "Hallam Oaks" To: "Christopher R. Bowman" Cc: "hackers@FreeBSD.ORG" Date: Thu, 29 Oct 1998 20:50:08 +1100 Reply-To: "Hallam Oaks" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Multi-terabyte disk farm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yesterday, IBM announced that they will now be making the Ultrastar 36XP a 36 >GB 7200 rpm 7.5ms 4Mb cache disk drive along the lines of their other drives. >This drive is available in Ultra2, SSA and FCAL interfaces. This would bring >you down to 28 drives and at "IBM estimated the list price of $1,575" >(http://www.news.com/News/Item/0,4,27995,00.html?st.ne.2.head) and run you >about $44100 for just the drives to give you 1TB of storage. Thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you thank you ;) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) :) I got this JUST in time to give it to the management finance meeting. It made my day ... as I'd already told them to expect 36 (or so) gb drives from IBM 'soonish'. I just didn't think it would be THIS soon. -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 02:32:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA05329 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 02:32:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA05322 for ; Thu, 29 Oct 1998 02:32:12 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA28773; Thu, 29 Oct 1998 10:33:47 GMT Date: Thu, 29 Oct 1998 10:33:47 +0000 (GMT) From: Doug Rabson To: John Hay cc: FreeBSD-hackers Subject: Re: kld screensavers In-Reply-To: <199810290746.JAA16726@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, John Hay wrote: > It looks like the kld screensavers hasn't been converted from lkm's > to kld's yet. It looks like it has just been moved from the lkm > directory to sys/modules. I have converted one of them (daemon_saver) > and it seems to be working fine. Is this the kind of chnages needed? > Is there something more (or less) needed? If this is ok, I will > commit it and do the rest of the screensavers... Or is someone else > busy with it... Or is there some other plan? > > One thing that I'm unsure about is in DECLARE_MODULE() if SI_SUB_PSEUDO > is the right one to use for the screen savers. It looks about right and SI_SUB_PSEUDO is sufficiently late that it shouldn't disturb anything. Any time after SI_SUB_CONFIGURE should work I think. It would be nice if the add_scrn_saver/remove_scrn_saver goop was factored into a generic module event handler which can be used by all screen savers. Have a look at the CDEV_MODULE #define in sys/conf.h for a possible way of doing this. If the generic module handler chains onto an optional user-supplied handler, then extra initialisation (allocating message in this case) can be done by each saver without repeating the registration code. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 03:36:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA12145 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 03:36:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA12137 for ; Thu, 29 Oct 1998 03:36:40 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id TAA14897; Thu, 29 Oct 1998 19:36:31 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id TAA05338; Thu, 29 Oct 1998 19:36:31 +0800 Message-Id: <199810291136.TAA05338@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Thu, 29 Oct 1998 14:38:40 +0800." <199810290638.OAA04511@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 19:36:31 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eureka - it works! Now for the modules..... > Chuck Robey wrote: > > On Wed, 28 Oct 1998, Mike Smith wrote: > > > > > > Can someone give me a pointer? I'm still running an a.out kernel on a sys > tem > > > > that was installed from a 3.0 snapshot CD and has been kept upto date via > cvs > > > > since. > > > [Deletia] > I'll also mention that this is jumping in at the deep end. You can > shortcut and do this: echo "/boot/loader" > /boot.config > as an intermediate step and test that. This will cause the existing > bootblocks to load the 3rd stage boot loader by default instead of > /kernel - but you are not yet committed. You still have the old boot: > prompt and can load /kernel.aout explicitly. The command that Mike has > given puts the new boot *blocks* on the disk which are not strictly > necessary to use the /boot/loader boot loader. > > You can actually test the new bootloader out by explicitly typing in > /boot/loader at the existing boot: prompt. > > > Excuse me (I'm worried about doing something inordinately dumb), just to > > verify, if I do that line above, after a buildworld/installworld, and > > then build a new kernel with KERNFORMAT set to elf, and install it, I > > should be running ok, right? All my newly regenned lkms will keep on > > humming fine, same obj files that powered the aout kernel, right? > > If you build an ELF kernel, you throw out the lkm's. They are a.out only, > because it depends on the a.out 'ld' command. Instead you can use the src/ > sys/modules stuff with kldload/kldunload and/or loading them at boot time > via the /boot/loader command prompt or the /boot/loader.conf script. > > One of my machines has: > > peter@overcee[2:34pm]~src-240> cat /boot/boot.conf > load kernel > load nfs.ko > autoboot 10 > -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 05:00:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20567 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 05:00:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA20556 for ; Thu, 29 Oct 1998 05:00:24 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id OAA10731; Thu, 29 Oct 1998 14:00:11 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id OAA11230; Thu, 29 Oct 1998 14:00:10 +0100 (MET) Message-ID: <19981029140009.23485@follo.net> Date: Thu, 29 Oct 1998 14:00:09 +0100 From: Eivind Eklund To: Luigi Rizzo , hackers@FreeBSD.ORG Subject: Re: compiler prototype question... References: <199810290453.FAA07168@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199810290453.FAA07168@labinfo.iet.unipi.it>; from Luigi Rizzo on Thu, Oct 29, 1998 at 05:53:44AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 05:53:44AM +0100, Luigi Rizzo wrote: > Hi, > > can someone tell me why in the following C program: > > int c1 (int c); > int c1 (char c) { return 1 ; } > > int c2 (int c); > int c2 (c) char c; { return 1 ; } [...] > To me, c2() seems as bad as the others, and i don't understand why > the compiler does not complain. It seems that when the prototype > declares an "int" argument, then any signed/unsigned type is accepted > for that argument in the non-ansi function body. As you can imagine > this defeats the usefulness of prototypes and obfuscates code. > Furthermore, with multiple arguments, i could even be suspicious of > how the compiler behaves (e.g. does it push a wordsize argument > and then tries to read it as multiple 1 or 2 byte items ?). That char is promoted to an int when the call is made, unless a prototype saying otherwise is in scope. > and the reason i am asking on hackers... > there is such code in the kernel, e.g. sys/i386/isa/if_ed.c > function ed_get_packet() has this problem and i don't know if it > a bug or what. I think it should be changed, but it isn't a bug per se. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 05:17:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22237 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 05:17:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from niobe.ewox.org (ppp041.uio.no [129.240.240.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22207 for ; Thu, 29 Oct 1998 05:16:54 -0800 (PST) (envelope-from finrod@niobe.ewox.org) Received: (from finrod@localhost) by niobe.ewox.org (8.9.1/8.8.8) id OAA03682; Thu, 29 Oct 1998 14:16:39 +0100 (CET) (envelope-from finrod) To: hackers@FreeBSD.ORG Subject: s/bpfilter/bpf/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: finrod@ewox.org (Dag-Erling Coidan Smørgrav) Date: 29 Oct 1998 14:16:38 +0100 Message-ID: <86u30n7bk9.fsf@niobe.ewox.org> Lines: 172 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While in Arnhem, I discussed renaming the bpfilter pseudo-device to bpf. There seemed to be agreement that it would be more consistent (amongst other items, the device nodes are named /dev/bpf*, and the man page is bpf(4)). The only impact this will have on users is that config will no longer recognize bpfilter as a valid pseudo-device name. All kernel config files that have bpf enabled will have to be edited. Other than that, there should be no user-visible changes. No syscalls, ioctls, library functions or header files will be renamed. All bpf consumers will compile and run as previously, and it will not be necessary to recompile any applications to adapt to the change. A patch is enclosed below; if it passes the usual tests and nobody objects, I'll commit it. (as you can see, the only changes are s/bpfilter/bpf/ in the man page, kernel source list, and sample kernel config files) Index: src/release/picobsd/router/conf/PICOBSD =================================================================== RCS file: /home/ncvs/src/release/picobsd/router/conf/PICOBSD,v retrieving revision 1.7 diff -u -r1.7 PICOBSD --- PICOBSD 1998/10/25 15:31:26 1.7 +++ PICOBSD 1998/10/29 12:54:23 @@ -86,7 +86,7 @@ pseudo-device ether #pseudo-device tun 2 #pseudo-device vn -#pseudo-device bpfilter 4 +#pseudo-device bpf 4 pseudo-device ppp 4 pseudo-device pty 16 #pseudo-device gzip # Exec gzipped a.out's Index: src/share/man/man4/bpf.4 =================================================================== RCS file: /home/ncvs/src/share/man/man4/bpf.4,v retrieving revision 1.13 diff -u -r1.13 bpf.4 --- bpf.4 1998/05/25 07:11:41 1.13 +++ bpf.4 1998/10/29 12:56:37 @@ -29,7 +29,7 @@ .Nm bpf .Nd Berkeley Packet Filter .Sh SYNOPSIS -.Cd pseudo-device bpfilter +.Cd pseudo-device bpf .Sh DESCRIPTION The Berkeley Packet Filter provides a raw interface to data link layers in a protocol Index: src/sys/conf/files =================================================================== RCS file: /home/ncvs/src/sys/conf/files,v retrieving revision 1.167 diff -u -r1.167 files --- files 1998/10/25 07:23:32 1.167 +++ files 1998/10/29 12:54:15 @@ -317,8 +317,8 @@ msdosfs/msdosfs_lookup.c optional msdosfs msdosfs/msdosfs_vfsops.c optional msdosfs msdosfs/msdosfs_vnops.c optional msdosfs -net/bpf.c optional bpfilter -net/bpf_filter.c optional bpfilter +net/bpf.c optional bpf +net/bpf_filter.c optional bpf net/bsd_comp.c optional ppp_bsdcomp #net/hostcache.c standard net/if.c standard Index: src/sys/i386/conf/GENERIC =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v retrieving revision 1.128 diff -u -r1.128 GENERIC --- GENERIC 1998/10/22 13:49:51 1.128 +++ GENERIC 1998/10/29 12:53:14 @@ -178,8 +178,8 @@ # options SYSVSHM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter Index: src/sys/i386/conf/LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/LINT,v retrieving revision 1.491 diff -u -r1.491 LINT --- LINT 1998/10/22 13:49:51 1.491 +++ LINT 1998/10/29 12:52:03 @@ -362,7 +362,7 @@ # of synchronous PPP links (like `cx', `ar'). # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. # The `ppp' pseudo-device implements the Point-to-Point Protocol. -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. @@ -381,7 +381,7 @@ pseudo-device fddi #Generic FDDI pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device -pseudo-device bpfilter 4 #Berkeley packet filter +pseudo-device bpf 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver (user process ppp(8)) pseudo-device sl 2 #Serial Line IP Index: src/sys/i386/conf/SMP-GENERIC =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/SMP-GENERIC,v retrieving revision 1.20 diff -u -r1.20 SMP-GENERIC --- SMP-GENERIC 1998/10/22 13:49:51 1.20 +++ SMP-GENERIC 1998/10/29 12:51:48 @@ -195,8 +195,8 @@ # options SYSVSHM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter Index: src/sys/pc98/conf/GENERIC98 =================================================================== RCS file: /home/ncvs/src/sys/pc98/conf/GENERIC98,v retrieving revision 1.54 diff -u -r1.54 GENERIC98 --- GENERIC98 1998/10/22 16:16:02 1.54 +++ GENERIC98 1998/10/29 12:49:19 @@ -171,11 +171,11 @@ # device ed0 at isa? port 0x00d0 net irq 6 -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter device ed1 at isa? port 0x00d8 net irq 6 flags 0x200000 device ed2 at isa? port 0x00d8 net irq 6 flags 0x300000 device ed3 at isa? port 0x00d0 net irq 6 flags 0x400000 Index: src/sys/pc98/conf/SMP-GENERIC98 =================================================================== RCS file: /home/ncvs/src/sys/pc98/conf/SMP-GENERIC98,v retrieving revision 1.9 diff -u -r1.9 SMP-GENERIC98 --- SMP-GENERIC98 1998/10/22 16:16:02 1.9 +++ SMP-GENERIC98 1998/10/29 12:49:11 @@ -235,8 +235,8 @@ # options SYSVSHM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter DES -- Dag-Erling Smørgrav - finrod@ewox.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 06:13:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26483 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 06:13:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nordmail.nordnet.fr (nordmail.nordnet.fr [194.206.126.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26465 for ; Thu, 29 Oct 1998 06:12:55 -0800 (PST) (envelope-from ericd@elabs.fr) Received: from Eric (gate7-167.nordnet.fr [195.146.225.167]) by nordmail.nordnet.fr (8.9.0/8.9.0) with SMTP id PAA22317 for ; Thu, 29 Oct 1998 15:12:43 +0100 Message-ID: <000501bdfc2b$bb1ee7c0$3c0aa8c0@Eric.labo.lan> From: "Eric D'HEM" To: Subject: suscribe Date: Tue, 20 Oct 1998 15:15:38 +0200 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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG suscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 06:38:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29923 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 06:38:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from emu.sourcee.com (emu.sourcee.com [199.201.159.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29911 for ; Thu, 29 Oct 1998 06:38:03 -0800 (PST) (envelope-from nrice@emu.sourcee.com) Received: (from nrice@localhost) by emu.sourcee.com (8.9.1/8.9.1) id JAA08404; Thu, 29 Oct 1998 09:37:46 -0500 (EST) Message-ID: <19981029093745.B8106@emu.sourcee.com> Date: Thu, 29 Oct 1998 09:37:45 -0500 From: "Norman C. Rice" To: =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= , hackers@FreeBSD.ORG Subject: Re: s/bpfilter/bpf/ References: <86u30n7bk9.fsf@niobe.ewox.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.91.1i In-Reply-To: =?iso-8859-1?Q?=3C86u30n7bk9=2Efsf=40niobe=2Eewox=2Eorg=3E=3B_from_Dag-E?= =?iso-8859-1?Q?rling_Coidan_Sm=F8rgrav_on_Thu=2C_Oct_29=2C_1998_at_02:16?= =?iso-8859-1?Q?:38PM_+0100?= Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 02:16:38PM +0100, Dag-Erling Coidan Smørgrav wrote: > While in Arnhem, I discussed renaming the bpfilter pseudo-device to > bpf. There seemed to be agreement that it would be more consistent > (amongst other items, the device nodes are named /dev/bpf*, and the > man page is bpf(4)). What about supporting either syntax to minimize the impact of the change? The pseudo-device bpfilter could be marked as deprecated. -- Regards, Norman C. Rice, Jr. > > The only impact this will have on users is that config will no longer > recognize bpfilter as a valid pseudo-device name. All kernel config > files that have bpf enabled will have to be edited. Other than that, > there should be no user-visible changes. No syscalls, ioctls, library > functions or header files will be renamed. All bpf consumers will > compile and run as previously, and it will not be necessary to > recompile any applications to adapt to the change. A patch is enclosed > below; if it passes the usual tests and nobody objects, I'll commit > it. > > (as you can see, the only changes are s/bpfilter/bpf/ in the man page, > kernel source list, and sample kernel config files) > > Index: src/release/picobsd/router/conf/PICOBSD > =================================================================== > RCS file: /home/ncvs/src/release/picobsd/router/conf/PICOBSD,v > retrieving revision 1.7 > diff -u -r1.7 PICOBSD > --- PICOBSD 1998/10/25 15:31:26 1.7 > +++ PICOBSD 1998/10/29 12:54:23 > @@ -86,7 +86,7 @@ > pseudo-device ether > #pseudo-device tun 2 > #pseudo-device vn > -#pseudo-device bpfilter 4 > +#pseudo-device bpf 4 > pseudo-device ppp 4 > pseudo-device pty 16 > #pseudo-device gzip # Exec gzipped a.out's > Index: src/share/man/man4/bpf.4 > =================================================================== > RCS file: /home/ncvs/src/share/man/man4/bpf.4,v > retrieving revision 1.13 > diff -u -r1.13 bpf.4 > --- bpf.4 1998/05/25 07:11:41 1.13 > +++ bpf.4 1998/10/29 12:56:37 > @@ -29,7 +29,7 @@ > .Nm bpf > .Nd Berkeley Packet Filter > .Sh SYNOPSIS > -.Cd pseudo-device bpfilter > +.Cd pseudo-device bpf > .Sh DESCRIPTION > The Berkeley Packet Filter > provides a raw interface to data link layers in a protocol > Index: src/sys/conf/files > =================================================================== > RCS file: /home/ncvs/src/sys/conf/files,v > retrieving revision 1.167 > diff -u -r1.167 files > --- files 1998/10/25 07:23:32 1.167 > +++ files 1998/10/29 12:54:15 > @@ -317,8 +317,8 @@ > msdosfs/msdosfs_lookup.c optional msdosfs > msdosfs/msdosfs_vfsops.c optional msdosfs > msdosfs/msdosfs_vnops.c optional msdosfs > -net/bpf.c optional bpfilter > -net/bpf_filter.c optional bpfilter > +net/bpf.c optional bpf > +net/bpf_filter.c optional bpf > net/bsd_comp.c optional ppp_bsdcomp > #net/hostcache.c standard > net/if.c standard > Index: src/sys/i386/conf/GENERIC > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v > retrieving revision 1.128 > diff -u -r1.128 GENERIC > --- GENERIC 1998/10/22 13:49:51 1.128 > +++ GENERIC 1998/10/29 12:53:14 > @@ -178,8 +178,8 @@ > # > options SYSVSHM > > -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > -#pseudo-device bpfilter 4 #Berkeley packet filter > +#pseudo-device bpf 4 #Berkeley packet filter > Index: src/sys/i386/conf/LINT > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/LINT,v > retrieving revision 1.491 > diff -u -r1.491 LINT > --- LINT 1998/10/22 13:49:51 1.491 > +++ LINT 1998/10/29 12:52:03 > @@ -362,7 +362,7 @@ > # of synchronous PPP links (like `cx', `ar'). > # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. > # The `ppp' pseudo-device implements the Point-to-Point Protocol. > -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > @@ -381,7 +381,7 @@ > pseudo-device fddi #Generic FDDI > pseudo-device sppp #Generic Synchronous PPP > pseudo-device loop #Network loopback device > -pseudo-device bpfilter 4 #Berkeley packet filter > +pseudo-device bpf 4 #Berkeley packet filter > pseudo-device disc #Discard device > pseudo-device tun 1 #Tunnel driver (user process ppp(8)) > pseudo-device sl 2 #Serial Line IP > Index: src/sys/i386/conf/SMP-GENERIC > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/SMP-GENERIC,v > retrieving revision 1.20 > diff -u -r1.20 SMP-GENERIC > --- SMP-GENERIC 1998/10/22 13:49:51 1.20 > +++ SMP-GENERIC 1998/10/29 12:51:48 > @@ -195,8 +195,8 @@ > # > options SYSVSHM > > -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > -#pseudo-device bpfilter 4 #Berkeley packet filter > +#pseudo-device bpf 4 #Berkeley packet filter > Index: src/sys/pc98/conf/GENERIC98 > =================================================================== > RCS file: /home/ncvs/src/sys/pc98/conf/GENERIC98,v > retrieving revision 1.54 > diff -u -r1.54 GENERIC98 > --- GENERIC98 1998/10/22 16:16:02 1.54 > +++ GENERIC98 1998/10/29 12:49:19 > @@ -171,11 +171,11 @@ > # > device ed0 at isa? port 0x00d0 net irq 6 > > -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > -#pseudo-device bpfilter 4 #Berkeley packet filter > +#pseudo-device bpf 4 #Berkeley packet filter > device ed1 at isa? port 0x00d8 net irq 6 flags 0x200000 > device ed2 at isa? port 0x00d8 net irq 6 flags 0x300000 > device ed3 at isa? port 0x00d0 net irq 6 flags 0x400000 > Index: src/sys/pc98/conf/SMP-GENERIC98 > =================================================================== > RCS file: /home/ncvs/src/sys/pc98/conf/SMP-GENERIC98,v > retrieving revision 1.9 > diff -u -r1.9 SMP-GENERIC98 > --- SMP-GENERIC98 1998/10/22 16:16:02 1.9 > +++ SMP-GENERIC98 1998/10/29 12:49:11 > @@ -235,8 +235,8 @@ > # > options SYSVSHM > > -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be > +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be > # aware of the legal and administrative consequences of enabling this > # option. The number of devices determines the maximum number of > # simultaneous BPF clients programs runnable. > -#pseudo-device bpfilter 4 #Berkeley packet filter > +#pseudo-device bpf 4 #Berkeley packet filter > > DES > -- > Dag-Erling Smørgrav - finrod@ewox.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 06:56:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02623 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 06:56:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02618 for ; Thu, 29 Oct 1998 06:56:49 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:zBtQPuwcNwYnYf1OgO+16oouFzXM+bSL@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id XAA23282; Thu, 29 Oct 1998 23:55:58 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA12116; Thu, 29 Oct 1998 23:57:20 +0900 (JST) Message-Id: <199810291457.XAA12116@zodiac.mech.utsunomiya-u.ac.jp> To: Doug Rabson cc: John Hay , FreeBSD-hackers , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: kld screensavers In-reply-to: Your message of "Thu, 29 Oct 1998 10:33:47 GMT." References: Date: Thu, 29 Oct 1998 23:57:19 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It looks about right and SI_SUB_PSEUDO is sufficiently late that it >shouldn't disturb anything. Any time after SI_SUB_CONFIGURE should work I >think. > >It would be nice if the add_scrn_saver/remove_scrn_saver goop was factored >into a generic module event handler which can be used by all screen >savers. Have a look at the CDEV_MODULE #define in sys/conf.h for a >possible way of doing this. > >If the generic module handler chains onto an optional user-supplied >handler, then extra initialisation (allocating message in this case) can >be done by each saver without repeating the registration code. You mean something like this? 1. Define generic_screen_saver_module_handler() in syscons.c or somewhere. 2. Each screen saver module define its own event handler. It will call the generic handler first and then do its own extra house keeping. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 07:33:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07152 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 07:33:38 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07145 for ; Thu, 29 Oct 1998 07:33:34 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id HAA05164; Thu, 29 Oct 1998 07:33:29 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: finrod@ewox.org (Dag-Erling Coidan Sm rgrav) cc: hackers@FreeBSD.ORG Subject: Re: s/bpfilter/bpf/ In-reply-to: Your message of "29 Oct 1998 14:16:38 +0100." <86u30n7bk9.fsf@niobe.ewox.org> Date: Thu, 29 Oct 1998 07:33:29 -0800 Message-ID: <5159.909675209@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While in Arnhem, I discussed renaming the bpfilter pseudo-device to > bpf. There seemed to be agreement that it would be more consistent > (amongst other items, the device nodes are named /dev/bpf*, and the > man page is bpf(4)). I agree that this change is overdue, but I also wonder whether or not you could do this so that ``pseudo-device bpfilter'' would continue to be a synonym for bpf. It wouldn't appear in any documentation or be suggested, but would at least continue to work for those with old config files. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 07:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08950 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 07:55:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from niobe.ewox.org (ppp027.uio.no [129.240.240.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08934; Thu, 29 Oct 1998 07:55:13 -0800 (PST) (envelope-from finrod@niobe.ewox.org) Received: (from finrod@localhost) by niobe.ewox.org (8.9.1/8.8.8) id QAA04512; Thu, 29 Oct 1998 16:55:07 +0100 (CET) (envelope-from finrod) To: hackers@FreeBSD.ORG, committers@FreeBSD.ORG Subject: sysctl Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit From: finrod@ewox.org (Dag-Erling Coidan Smørgrav) Date: 29 Oct 1998 16:55:07 +0100 Message-ID: <86n26f7484.fsf@niobe.ewox.org> Lines: 16 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While fixing a sysctl-related bug in arp, I noticed that sysctl(3) is kinda fubar. According to the man page, it either returns 0, or returns -1 and sets errno. However, reading src/lib/libc/gen/sysctl.c and src/sys/kern/kern_sysctl.c reveals that the sysctl syscall returns the error code directly, and the sysctl library function does a little of both. The "fix" I did to src/lib/libkvm/kvm_proc.c depends on sysctl(3) acting in accordance to the man page, which it doesn't (it returns ENOMEM instead of setting errno to ENOMEM and returning -1). Should sysctl(3) be fixed to act as documented, or should the man page be fixed to document reality? In both cases, sysctl(3) will neeed to be fixed since it does a little of both. DES -- Dag-Erling Smørgrav - finrod@ewox.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:16:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11804 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:16:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11794 for ; Thu, 29 Oct 1998 08:16:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA27387; Thu, 29 Oct 1998 11:16:01 -0500 (EST) Date: Thu, 29 Oct 1998 11:16:00 -0500 (EST) From: "Matthew N. Dodd" To: Hallam Oaks cc: "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <199810290949.UAA01503@mail.aussie.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Hallam Oaks wrote: > If anyone wants to suggest alternative enclosures to the Kingstons > then I'm all ears. Nothing in that area is set in stone (yet). The Kingstons are fine provided you do not attempt to integrate them yourself. I'm fairly unhappy with most of the RAID products out there at this point. Hitachi looks to have some interesting stuff. Artecon as some really slow, lame stuff. Symbios has some fairly good, but lame interfacing stuff. Call Gary Evans at UniSolutions (713.552.0505). They have an email address as well (unisol@ix.netcom.com) but I remember it not being frequently checked. Gary knows his stuff and will be albe to do disk integration for you, and offer suggestions on RAID solutions as well. They've been doing this stuff for a long time and your project requirements are probably on the small end of the kind of things they do. :) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:25:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12509 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:25:12 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12504 for ; Thu, 29 Oct 1998 08:25:10 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA27545; Thu, 29 Oct 1998 11:24:42 -0500 (EST) Date: Thu, 29 Oct 1998 11:24:42 -0500 (EST) From: "Matthew N. Dodd" To: Hallam Oaks cc: "Christopher R. Bowman" , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <199810290949.UAA01506@mail.aussie.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Hallam Oaks wrote: > I got this JUST in time to give it to the management finance meeting. It made > my day ... as I'd already told them to expect 36 (or so) gb drives from IBM > 'soonish'. I just didn't think it would be THIS soon. I still think the tape robot solution would be a better way to go. Expanding a big library is just a matter of adding more silos. Drives may fail but you can (and should) have spares. Tapes can fail as well, but you can (and should) have dupes. I'm pretty sure that the cost of scaling is cheaper than for online storage. Additionally, you may wish to check out some of the new HP Magneto Optical storage products. Their 1200ex can fit 1237.6 GB across 238 media slots using 5.2g media with 4, 6 or 10 drives. Consider also CD-ROM jukeboxes. With the cost of CDR media you would be limited only by the size of the changer you could find. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:29:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12944 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:29:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12938 for ; Thu, 29 Oct 1998 08:29:07 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id KAA27518; Thu, 29 Oct 1998 10:28:54 -0600 (CST) Message-ID: <19981029102854.A27512@Denninger.Net> Date: Thu, 29 Oct 1998 10:28:54 -0600 From: Karl Denninger To: "Matthew N. Dodd" , Hallam Oaks Cc: "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm References: <199810290949.UAA01503@mail.aussie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew N. Dodd on Thu, Oct 29, 1998 at 11:16:00AM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I love the CMD RAID controllers. There is a local shop here in Chicagoland, CompuElectronics, which can do integration and build-up for you on basically anything. They're not the cheapest, but they do good work, and I've been extremely happy with them in the past. Call 847-679-2667, ask for Rom. They have available some mongo-huge array cases with redundant power and incredible numbers of bays (20+) for this kind of job. That kind of thing is not cheap, but it can be done. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. On Thu, Oct 29, 1998 at 11:16:00AM -0500, Matthew N. Dodd wrote: > On Thu, 29 Oct 1998, Hallam Oaks wrote: > > If anyone wants to suggest alternative enclosures to the Kingstons > > then I'm all ears. Nothing in that area is set in stone (yet). > > The Kingstons are fine provided you do not attempt to integrate them > yourself. > > I'm fairly unhappy with most of the RAID products out there at this point. > > Hitachi looks to have some interesting stuff. > > Artecon as some really slow, lame stuff. > > Symbios has some fairly good, but lame interfacing stuff. > > Call Gary Evans at UniSolutions (713.552.0505). They have an email > address as well (unisol@ix.netcom.com) but I remember it not being > frequently checked. > > Gary knows his stuff and will be albe to do disk integration for you, and > offer suggestions on RAID solutions as well. > > They've been doing this stuff for a long time and your project > requirements are probably on the small end of the kind of things they do. > :) > > > -- > | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | > | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:31:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13145 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:31:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from niobe.ewox.org (ppp027.uio.no [129.240.240.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13129 for ; Thu, 29 Oct 1998 08:30:51 -0800 (PST) (envelope-from finrod@niobe.ewox.org) Received: (from finrod@localhost) by niobe.ewox.org (8.9.1/8.8.8) id RAA04890; Thu, 29 Oct 1998 17:30:49 +0100 (CET) (envelope-from finrod) To: hackers@FreeBSD.ORG Subject: Re: s/bpfilter/bpf/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit References: <5159.909675209@time.cdrom.com> From: finrod@ewox.org (Dag-Erling Coidan Smørgrav) Date: 29 Oct 1998 17:30:49 +0100 Message-ID: <86k91j72km.fsf@niobe.ewox.org> Lines: 158 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a new patch which allows both keywords (bpfilter and bpf): Index: src/release/picobsd/router/conf/PICOBSD =================================================================== RCS file: /home/ncvs/src/release/picobsd/router/conf/PICOBSD,v retrieving revision 1.7 diff -u -r1.7 PICOBSD --- PICOBSD 1998/10/25 15:31:26 1.7 +++ PICOBSD 1998/10/29 12:54:23 @@ -86,7 +86,7 @@ pseudo-device ether #pseudo-device tun 2 #pseudo-device vn -#pseudo-device bpfilter 4 +#pseudo-device bpf 4 pseudo-device ppp 4 pseudo-device pty 16 #pseudo-device gzip # Exec gzipped a.out's Index: src/share/man/man4/bpf.4 =================================================================== RCS file: /home/ncvs/src/share/man/man4/bpf.4,v retrieving revision 1.13 diff -u -r1.13 bpf.4 --- bpf.4 1998/05/25 07:11:41 1.13 +++ bpf.4 1998/10/29 12:56:37 @@ -29,7 +29,7 @@ .Nm bpf .Nd Berkeley Packet Filter .Sh SYNOPSIS -.Cd pseudo-device bpfilter +.Cd pseudo-device bpf .Sh DESCRIPTION The Berkeley Packet Filter provides a raw interface to data link layers in a protocol Index: src/sys/conf/files =================================================================== RCS file: /home/ncvs/src/sys/conf/files,v retrieving revision 1.167 diff -u -r1.167 files --- files 1998/10/25 07:23:32 1.167 +++ files 1998/10/29 16:26:31 @@ -317,8 +317,11 @@ msdosfs/msdosfs_lookup.c optional msdosfs msdosfs/msdosfs_vfsops.c optional msdosfs msdosfs/msdosfs_vnops.c optional msdosfs +# bpfilter is deprecated and will go away soon; use bpf instead. net/bpf.c optional bpfilter net/bpf_filter.c optional bpfilter +net/bpf.c optional bpf +net/bpf_filter.c optional bpf net/bsd_comp.c optional ppp_bsdcomp #net/hostcache.c standard net/if.c standard Index: src/sys/i386/conf/GENERIC =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/GENERIC,v retrieving revision 1.128 diff -u -r1.128 GENERIC --- GENERIC 1998/10/22 13:49:51 1.128 +++ GENERIC 1998/10/29 12:53:14 @@ -178,8 +178,8 @@ # options SYSVSHM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter Index: src/sys/i386/conf/LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/LINT,v retrieving revision 1.491 diff -u -r1.491 LINT --- LINT 1998/10/22 13:49:51 1.491 +++ LINT 1998/10/29 12:52:03 @@ -362,7 +362,7 @@ # of synchronous PPP links (like `cx', `ar'). # The `sl' pseudo-device implements the Serial Line IP (SLIP) service. # The `ppp' pseudo-device implements the Point-to-Point Protocol. -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. @@ -381,7 +381,7 @@ pseudo-device fddi #Generic FDDI pseudo-device sppp #Generic Synchronous PPP pseudo-device loop #Network loopback device -pseudo-device bpfilter 4 #Berkeley packet filter +pseudo-device bpf 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver (user process ppp(8)) pseudo-device sl 2 #Serial Line IP Index: src/sys/i386/conf/SMP-GENERIC =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/SMP-GENERIC,v retrieving revision 1.20 diff -u -r1.20 SMP-GENERIC --- SMP-GENERIC 1998/10/22 13:49:51 1.20 +++ SMP-GENERIC 1998/10/29 12:51:48 @@ -195,8 +195,8 @@ # options SYSVSHM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter Index: src/sys/pc98/conf/GENERIC98 =================================================================== RCS file: /home/ncvs/src/sys/pc98/conf/GENERIC98,v retrieving revision 1.54 diff -u -r1.54 GENERIC98 --- GENERIC98 1998/10/22 16:16:02 1.54 +++ GENERIC98 1998/10/29 12:49:19 @@ -171,11 +171,11 @@ # device ed0 at isa? port 0x00d0 net irq 6 -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter device ed1 at isa? port 0x00d8 net irq 6 flags 0x200000 device ed2 at isa? port 0x00d8 net irq 6 flags 0x300000 device ed3 at isa? port 0x00d0 net irq 6 flags 0x400000 Index: src/sys/pc98/conf/SMP-GENERIC98 =================================================================== RCS file: /home/ncvs/src/sys/pc98/conf/SMP-GENERIC98,v retrieving revision 1.9 diff -u -r1.9 SMP-GENERIC98 --- SMP-GENERIC98 1998/10/22 16:16:02 1.9 +++ SMP-GENERIC98 1998/10/29 12:49:11 @@ -235,8 +235,8 @@ # options SYSVSHM -# The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be +# The `bpf' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. -#pseudo-device bpfilter 4 #Berkeley packet filter +#pseudo-device bpf 4 #Berkeley packet filter DES -- Dag-Erling Smørgrav - finrod@ewox.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:47:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14884 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:47:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14874 for ; Thu, 29 Oct 1998 08:47:01 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA27972; Thu, 29 Oct 1998 11:46:48 -0500 (EST) Date: Thu, 29 Oct 1998 11:46:48 -0500 (EST) From: "Matthew N. Dodd" To: Karl Denninger cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <19981029102854.A27512@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Karl Denninger wrote: > I love the CMD RAID controllers. They do have nice features yes, but David Greenman posted a bit about their limited number of tags (64). Unless CMD has fixed this, these arrays would be fairly useless in a performance system. Granted, they are priced right and if you don't mind not being able to max out your drives, go for it. With fewer tags supported, I'd have no problems putting more drives on each chain, which would make them an even higher density solution. > There is a local shop here in Chicagoland, CompuElectronics, which can do > integration and build-up for you on basically anything. > > They're not the cheapest, but they do good work, and I've been extremely > happy with them in the past. > > Call 847-679-2667, ask for Rom. > > They have available some mongo-huge array cases with redundant power and > incredible numbers of bays (20+) for this kind of job. That kind of thing > is not cheap, but it can be done. > > -- > -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:53:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15647 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:53:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15640 for ; Thu, 29 Oct 1998 08:53:27 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id KAA27633; Thu, 29 Oct 1998 10:53:16 -0600 (CST) Message-ID: <19981029105316.A27621@Denninger.Net> Date: Thu, 29 Oct 1998 10:53:16 -0600 From: Karl Denninger To: "Matthew N. Dodd" Cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm References: <19981029102854.A27512@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew N. Dodd on Thu, Oct 29, 1998 at 11:46:48AM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 11:46:48AM -0500, Matthew N. Dodd wrote: > On Thu, 29 Oct 1998, Karl Denninger wrote: > > I love the CMD RAID controllers. > > They do have nice features yes, but David Greenman posted a bit about > their limited number of tags (64). Unless CMD has fixed this, these > arrays would be fairly useless in a performance system. > > Granted, they are priced right and if you don't mind not being able to max > out your drives, go for it. > > With fewer tags supported, I'd have no problems putting more drives on > each chain, which would make them an even higher density solution. Hmmm... I'll look into this. We haven't gotten tag reduction warnings on any of our NFS fileservers using these, nor on our INN machine (which uses them in RAID 0+1 config). -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:57:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16278 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:57:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16269 for ; Thu, 29 Oct 1998 08:57:47 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA28185; Thu, 29 Oct 1998 11:57:30 -0500 (EST) Date: Thu, 29 Oct 1998 11:57:30 -0500 (EST) From: "Matthew N. Dodd" To: Karl Denninger cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <19981029105316.A27621@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Karl Denninger wrote: > Hmmm... I'll look into this. We haven't gotten tag reduction warnings > on any of our NFS fileservers using these, nor on our INN machine > (which uses them in RAID 0+1 config). You'd proably only see it in RAID5 mode or if you were -really- beating on your array. Still, with that much memory they should make # of tags supported a tunable. I really want to find a cheap CRD-5440 just for kicks. 1 host and 2 disk channels is just right for a small server. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 08:59:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16407 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 08:59:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16401; Thu, 29 Oct 1998 08:59:02 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA22379; Fri, 30 Oct 1998 03:58:58 +1100 Date: Fri, 30 Oct 1998 03:58:58 +1100 From: Bruce Evans Message-Id: <199810291658.DAA22379@godzilla.zeta.org.au> To: committers@FreeBSD.ORG, finrod@ewox.org, hackers@FreeBSD.ORG Subject: Re: sysctl Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >While fixing a sysctl-related bug in arp, I noticed that sysctl(3) is >kinda fubar. According to the man page, it either returns 0, or >returns -1 and sets errno. However, reading src/lib/libc/gen/sysctl.c >and src/sys/kern/kern_sysctl.c reveals that the sysctl syscall returns >the error code directly, and the sysctl library function does a little >of both. The "fix" I did to src/lib/libkvm/kvm_proc.c depends on I think you need to read the code again. All syscall functions in in the kernel (at the level of sysent[]) return the error code directly. Normal return values are returned indirectly in p->p_retval[]. >sysctl(3) acting in accordance to the man page, which it doesn't (it >returns ENOMEM instead of setting errno to ENOMEM and returning -1). > >Should sysctl(3) be fixed to act as documented, or should the man page It already does, at least for the call near your fix in kvm_proc.c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 09:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16613 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 09:00:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16602 for ; Thu, 29 Oct 1998 09:00:09 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id KAA27671; Thu, 29 Oct 1998 10:59:43 -0600 (CST) Message-ID: <19981029105943.A27659@Denninger.Net> Date: Thu, 29 Oct 1998 10:59:43 -0600 From: Karl Denninger To: "Matthew N. Dodd" Cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm References: <19981029105316.A27621@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew N. Dodd on Thu, Oct 29, 1998 at 11:57:30AM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 11:57:30AM -0500, Matthew N. Dodd wrote: > On Thu, 29 Oct 1998, Karl Denninger wrote: > > Hmmm... I'll look into this. We haven't gotten tag reduction warnings > > on any of our NFS fileservers using these, nor on our INN machine > > (which uses them in RAID 0+1 config). > > You'd proably only see it in RAID5 mode or if you were -really- beating on > your array. Still, with that much memory they should make # of tags > supported a tunable. We beat the SHIT out of our arrays, and the big NFS servers run in RAID 5 mode :-) > I really want to find a cheap CRD-5440 just for kicks. 1 host and 2 disk > channels is just right for a small server. Yep. Actually, the 5440 has 4 channels :-) ~$2500 or so. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 09:06:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17326 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 09:06:31 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17312 for ; Thu, 29 Oct 1998 09:06:29 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id MAA28395; Thu, 29 Oct 1998 12:06:16 -0500 (EST) Date: Thu, 29 Oct 1998 12:06:15 -0500 (EST) From: "Matthew N. Dodd" To: Karl Denninger cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <19981029105943.A27659@Denninger.Net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Karl Denninger wrote: > > You'd proably only see it in RAID5 mode or if you were -really- beating on > > your array. Still, with that much memory they should make # of tags > > supported a tunable. > > We beat the SHIT out of our arrays, and the big NFS servers run in RAID 5 > mode :-) But how busy is the controller? 50%? More? David G. would probably have more information on the CMD's low performance modes. (Or rather modes where the limited number of taged commands begins to impose limits on I/O) > > I really want to find a cheap CRD-5440 just for kicks. 1 host and 2 disk > > channels is just right for a small server. > > Yep. Actually, the 5440 has 4 channels :-) ~$2500 or so. Ya, reading skills help. $2500 is still a bit out of my price range for home use. Maybe when I can second hand them in a few years. :) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 09:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18755 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 09:17:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18750 for ; Thu, 29 Oct 1998 09:17:17 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id LAA27750; Thu, 29 Oct 1998 11:16:55 -0600 (CST) Message-ID: <19981029111654.A27715@Denninger.Net> Date: Thu, 29 Oct 1998 11:16:54 -0600 From: Karl Denninger To: "Matthew N. Dodd" Cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm References: <19981029105943.A27659@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew N. Dodd on Thu, Oct 29, 1998 at 12:06:15PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 12:06:15PM -0500, Matthew N. Dodd wrote: > On Thu, 29 Oct 1998, Karl Denninger wrote: > > > You'd proably only see it in RAID5 mode or if you were -really- beating on > > > your array. Still, with that much memory they should make # of tags > > > supported a tunable. > > > > We beat the SHIT out of our arrays, and the big NFS servers run in RAID 5 > > mode :-) > > But how busy is the controller? 50%? More? Yeap. A good percentage of the time anyway. During backups (which are done hot!) it gets pounded even harder. > David G. would probably have more information on the CMD's low performance > modes. (Or rather modes where the limited number of taged commands begins > to impose limits on I/O) Hmmm..... I'd like to see that, actually. > > > I really want to find a cheap CRD-5440 just for kicks. 1 host and 2 disk > > > channels is just right for a small server. > > > > Yep. Actually, the 5440 has 4 channels :-) ~$2500 or so. > > Ya, reading skills help. $2500 is still a bit out of my price range for > home use. Maybe when I can second hand them in a few years. :) Yep. I'd buy one for my home network too, but that's a big pricey. I like having the "best and fastest", but not THAT badly :-) I am nutty enough though to do swappable carriers with temperature control in each (via a sensor, control CPU and dual fans - IN the carrier) :-) The disks run at a near-constant 42 degrees centigrade case temperature ;-) -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 10:00:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23419 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 10:00:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23413 for ; Thu, 29 Oct 1998 10:00:09 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with SMTP id KAA11760 for ; Thu, 29 Oct 1998 10:00:07 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Thu, 29 Oct 1998 10:00:07 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: hackers@FreeBSD.ORG Subject: Re: Multi-terabyte disk farm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Matthew N. Dodd wrote: > Consider also CD-ROM jukeboxes. With the cost of CDR media you would be > limited only by the size of the changer you could find. Bad idea. :) 1 terabyte requires 1539 CD-Rs, and it will take 32 days of continuous operation (assuming one 2x speed burner) to burn them. I don't think anyone makes thousand-disc changers, so one would probably have to buy a robot to handle them. Methinks you'd wear the drives (both readers and burners) out very quickly, too. -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 10:29:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28730 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 10:29:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28723 for ; Thu, 29 Oct 1998 10:29:49 -0800 (PST) (envelope-from moncrg@bt340707.res.ray.com) Received: (mailer@localhost) by gatekeeper.ray.com (8.8.7/8.8.7) id NAA23257 for ; Thu, 29 Oct 1998 13:14:10 -0500 (EST) Received: from bt340707.res.ray.com/138.125.142.35() by gatekeeper.ray.com id sma.909684807.009620; Thu Oct 29 13:13:27 1998 Received: from bt340707.res.ray.com (localhost [127.0.0.1]) by bt340707.res.ray.com (8.8.8/8.8.7) with ESMTP id NAA11096 for ; Thu, 29 Oct 1998 13:13:01 -0500 (EST) (envelope-from moncrg@bt340707.res.ray.com) Message-ID: <3638B02C.F1913CD5@bt340707.res.ray.com> Date: Thu, 29 Oct 1998 13:13:01 -0500 From: "Gregory D. Moncreaff" X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: hackers Subject: help with setting up private cvsup mirror Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to set up a mirror. I have one machine "A" that cvsup'd cvs-all and ports-all from cvsup.freebsd.org. I want another machine "B" to be able to do the same but pointing at "A" instead of cvsup.freebsd.org I checked out distrib/cvsup and placed it in /usr/local/etc/cvsup but when I try to do the private cvsup (using /usr/share/examples/cvsup/cvs-supfile with only a host change) on "A" cvsupd reports: collection "src-all" release "cvs" is not available here collection "ports-all" release "cvs" is not available here and cvsup on "B" reports the same thing "A" cvsupd = 15.4.2 "B" cvsup = 15.4 I'm guessing that there is something missing, and from reading the cvsupd manpage I think it must be the prefix dir. The .../cvsup/sup/README file suggests there might be links, but to what and with what names I can't tell. Is there a "cvsup mirror in N easy steps" page I haven't found yet? I searched the mailing lists, and this was raised back in Feb, but not apparently resolved. JDPs page also doesn't discuss the server side, cvsupd.... -- Greg Moncreaff, Senior Software Engineer, CNS/ATN Raytheon Systems Company, Mailstop 2.2.2507 Raytheon 1001 Boston Post Road East, Marlboro, MA 01752 USA 508.490.2048, 508.490.2086 fax -- Disclaimer: "this is my personal opinion and not that of my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 10:41:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00823 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 10:41:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from scully.tamu.edu (unix.tamu.edu [128.194.103.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00814 for ; Thu, 29 Oct 1998 10:41:42 -0800 (PST) (envelope-from s0k9955@unix.tamu.edu) Received: from localhost by scully.tamu.edu (8.9.0/8.9.0) with SMTP id MAA29235; Thu, 29 Oct 1998 12:41:31 -0600 (CST) Date: Thu, 29 Oct 1998 12:41:31 -0600 (CST) From: Shafia Kausar To: FreeBSD Hackers cc: shafiak@ee.tamu.edu Subject: Timer Granularity Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am new to the FreeBSD OS. I have a few questions for which I could not find answers on the webpages. I am using the FreeBSD version 2.1.5 Relase #2. What is the kernel clock granularity in this version? There are a number of clocks being used in FreeBSD. Which clock is used for real time kernel processing? Is this accessible to the users? Has the timer granularity improved in the releases following this release? In the /sys/kern/kern_clock.c file the variable time_precision has been initialised to 1microsec, but it has been stated that the resolution decreases depending on whether the external clock is working or not. What is the range of the variation in the resolutuion? Any help or pointers are welcome. Thanks -Shafia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04601 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:11:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04596 for ; Thu, 29 Oct 1998 11:11:45 -0800 (PST) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id TAA11313; Thu, 29 Oct 1998 19:11:27 GMT Message-ID: <3638BDDE.69C6C0B9@tdx.co.uk> Date: Thu, 29 Oct 1998 19:11:26 +0000 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: Dag-Erling Coidan Sm rgrav , hackers@FreeBSD.ORG Subject: Re: s/bpfilter/bpf/ References: <5159.909675209@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > While in Arnhem, I discussed renaming the bpfilter pseudo-device to > > bpf. There seemed to be agreement that it would be more consistent > > (amongst other items, the device nodes are named /dev/bpf*, and the > > man page is bpf(4)). > > I agree that this change is overdue, but I also wonder whether or not > you could do this so that ``pseudo-device bpfilter'' would continue to > be a synonym for bpf. It wouldn't appear in any documentation or be > suggested, but would at least continue to work for those with old > config files. Or even better have something at 'config' time that says: "Warning - BPFILTER is being phased out! Please replace 'bpfilter' with 'bpf' in future" (This is coming from somone who knows not a lot how 'config KERNEL' works, but is still impressed when it spots things like un-specified controllers for wired down SCSI devices) ;-) Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:13:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05118 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:13:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05099; Thu, 29 Oct 1998 11:13:23 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA22847; Thu, 29 Oct 1998 11:13:18 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma022843; Thu Oct 29 11:13:15 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA26982; Thu, 29 Oct 1998 11:13:15 -0800 (PST) From: Archie Cobbs Message-Id: <199810291913.LAA26982@bubba.whistle.com> Subject: Re: getpwnam() problem? In-Reply-To: <199810281914.MAA07942@kitsune.swcp.com> from Brendan Conoboy at "Oct 28, 98 12:14:20 pm" To: synk@swcp.com (Brendan Conoboy) Date: Thu, 29 Oct 1998 11:13:15 -0800 (PST) Cc: freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brendan Conoboy writes: > A couple weeks ago I filled out a little bug report with the GNATS > form, but it's received no attention (maybe I should have marked it as > critical?). Anyway, since it may well be security related, I wanted to > point it out here. The condensed version is that if getpwnam() is > given a very large string (say a few thousand characters) it will > sigsegv or sigbus. This is true for 2.2.7-stable (as of a few weeks > ago) and 3.0-release. Perhaps it's nothing, perhaps it's something, > but it certainly doesn't happen on a whole slew of other OSes. The > problem report is at: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=8176 I've located the bug and supplied a patch in a followup... Very simple bug, someone please commit in 2.2 and 3.0. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:17:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05937 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:17:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from galea.com (Odie.Galea.Com [205.237.227.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA05926 for ; Thu, 29 Oct 1998 11:17:27 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from gotlib.galea.com (Gotlib.Galea.Com [205.237.227.60]) by galea.com (8.6.11/8.6.9) with SMTP id OAA15429 for ; Thu, 29 Oct 1998 14:32:24 -0500 Received: from videotron.ca ([205.237.227.166]) by gotlib.galea.com (Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) with SMTP id 852566AC.0069E340; Thu, 29 Oct 1998 14:16:34 -0500 Message-ID: <3638BF40.304CB4F0@videotron.ca> Date: Thu, 29 Oct 1998 14:17:20 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security Inc. X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Hackers@FreeBSD.ORG Subject: FreeBSD arm port Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For a project I have here I need to port FreeBSD to an arm architecture (SA110 processor with a 21285 as pci/memory controller). Is there anyone currently working on this? I remember some discussions about arm support a few weeks ago but I can't quite remember is someone was actively doing it. I'll search the archives later on this afternoon... Before I RTFM and try to learn how to add the support to the FreeBSD gcc compiler to cross-compile from our i386-unknown-freebsd3.0 to arm-unknown-freebsd3.0 I wanted to check if anyone had already done this or was in the process of doing so. I guess it would be easier to do the port using netbsd as host but as the hw is not yet ready we are using an ebsa285 board to do the prototyping and I was told that netBSD doesn't support it natively (though I could be mistaken). Also, some pointers as to what are the main steps for doing such a port (FreeBSD port as a whole) would be greatly appreciated. Comments, pros, cons are welcome :) Regards, Stephane E. Potvin Galea Network Security --- La vie est trop courte pour etre prise au serieux. anonyme P.S.: Sorry if it's on the wrong list. Feel free to follow up at the right place if it's the case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:22:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07107 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:22:43 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07098 for ; Thu, 29 Oct 1998 11:22:37 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id VAA27010; Thu, 29 Oct 1998 21:22:00 +0200 (SAT) From: John Hay Message-Id: <199810291922.VAA27010@zibbi.mikom.csir.co.za> Subject: Re: kld screensavers In-Reply-To: <199810291457.XAA12116@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Oct 29, 98 11:57:19 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 29 Oct 1998 21:22:00 +0200 (SAT) Cc: dfr@nlsystems.com, hackers@FreeBSD.ORG (FreeBSD-hackers) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >It looks about right and SI_SUB_PSEUDO is sufficiently late that it > >shouldn't disturb anything. Any time after SI_SUB_CONFIGURE should work I > >think. > > > >It would be nice if the add_scrn_saver/remove_scrn_saver goop was factored > >into a generic module event handler which can be used by all screen > >savers. Have a look at the CDEV_MODULE #define in sys/conf.h for a > >possible way of doing this. > > > >If the generic module handler chains onto an optional user-supplied > >handler, then extra initialisation (allocating message in this case) can > >be done by each saver without repeating the registration code. > > You mean something like this? > > 1. Define generic_screen_saver_module_handler() in syscons.c or somewhere. > 2. Each screen saver module define its own event handler. It will call > the generic handler first and then do its own extra house keeping. > Is this really usefull? The simplest one is the star_saver and its modevent function will look like this: --------- static int star_saver_modevent(module_t mod, modeventtype_t type, void *unused) { switch (type) { case MOD_LOAD: return add_scrn_saver(star_saver); case MOD_UNLOAD: return remove_scrn_saver(star_saver); default: printf("star_saver module unknown event: 0x%x\n", type); } return 0; } --------- It looks silly to me to put this somewhere generic and call it from each saver. What might be usefull is a macro to define the moduledata_t structure and do the DECLARE_MODULE() thingy like what is done with CDEV_MODULE, but even there I'm not sure if you are saving that much. But maybe I'm missing something. John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07327 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:22:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07137 for ; Thu, 29 Oct 1998 11:22:50 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA22994; Thu, 29 Oct 1998 11:22:48 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma022992; Thu Oct 29 11:22:38 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA27011; Thu, 29 Oct 1998 11:22:38 -0800 (PST) From: Archie Cobbs Message-Id: <199810291922.LAA27011@bubba.whistle.com> Subject: Re: s/bpfilter/bpf/ In-Reply-To: <86u30n7bk9.fsf@niobe.ewox.org> from =?ISO-8859-1?Q?Dag=2DErling_Coidan_Sm=F8rgrav?= at "Oct 29, 98 02:16:38 pm" To: finrod@ewox.org (Dag-Erling Coidan Smørgrav) Date: Thu, 29 Oct 1998 11:22:38 -0800 (PST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by bubba.whistle.com id LAA27011 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA07138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Coidan Smørgrav writes: > While in Arnhem, I discussed renaming the bpfilter pseudo-device to > bpf. There seemed to be agreement that it would be more consistent > (amongst other items, the device nodes are named /dev/bpf*, and the > man page is bpf(4)). While you're at it, could you also fix the /dev/MAKEDEV script so if you say sh MAKEDEV bpf3 it makes bpf0, bpf1, and bpf2 as well? It does this for tunX but not bpfX, for some reason.. why the inconsistency? Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:41:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10666 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:41:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10634 for ; Thu, 29 Oct 1998 11:41:19 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id LAA16928; Thu, 29 Oct 1998 11:40:04 -0800 (PST) Message-Id: <199810291940.LAA16928@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: "Stephane E. Potvin" Cc: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 29 Oct 1998 11:40:03 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 14:17:20 -0500 "Stephane E. Potvin" wrote: > port using netbsd as host but as the hw is not yet ready we are using an > ebsa285 board to do the prototyping and I was told that netBSD doesn't > support it natively (though I could be mistaken). NetBSD-current does indeed run on the EBSA285. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 11:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12498 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 11:52:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12491 for ; Thu, 29 Oct 1998 11:52:20 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA01340; Thu, 29 Oct 1998 14:52:13 -0500 (EST) Date: Thu, 29 Oct 1998 14:52:12 -0500 (EST) From: "Matthew N. Dodd" To: "Brian W. Buchanan" cc: hackers@FreeBSD.ORG Subject: Re: Multi-terabyte disk farm In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Brian W. Buchanan wrote: > Bad idea. :) 1 terabyte requires 1539 CD-Rs, and it will take 32 days > of continuous operation (assuming one 2x speed burner) to burn them. > I don't think anyone makes thousand-disc changers, so one would > probably have to buy a robot to handle them. Methinks you'd wear the > drives (both readers and burners) out very quickly, too. JVC makes a 600 disk changer. You'd only need 3 of them :) I have no idea how expensive they would be though. It could be that a half a dozen such changers would be more effective than any muddling with disks. Once the media is burned it shelf life is fairly long and in an emergency you can manually load from any desktop peecee. Granted, making sure you filled dieks to capacity and had correct indexes would be the difficult part but it is an option, and probably cheaper than DLT when you consider media costs. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 13:03:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22123 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 13:03:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22112 for ; Thu, 29 Oct 1998 13:03:39 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40341>; Fri, 30 Oct 1998 08:02:47 +1100 Date: Fri, 30 Oct 1998 08:03:14 +1100 From: Peter Jeremy Subject: Re: compiler prototype question... To: hackers@FreeBSD.ORG Cc: luigi@labinfo.iet.unipi.it Message-Id: <98Oct30.080247est.40341@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 05:53:44 +0100 (MET), Luigi Rizzo wrote: >can someone tell me why in the following C program: > > int c1 (int c); > int c1 (char c) { return 1 ; } > proto.c:8: conflicting types for `c1' > proto.c:7: previous declaration of `c1' Here, you've specified conflicting prototypes. The declaration states that c1 takes a single `int' argument, whilst the definition states that it takes a single `char' argument. > int c2 (int c); > int c2 (c) char c; { return 1 ; } This is correct. A K&R definition means that the argument will be promoted: {char,short}->int, float->double. The prototype therefore matches the definition. Note that although the argument is passed as an int, it is referenced as a char. The remaining bytes are ignored. > int c3 (char c); > int c3 (c) int c; { return 1 ;} > proto.c: In function `c3': > proto.c:14: argument `c' doesn't match prototype > proto.c:13: prototype declaration Here, you've specified conflicting prototypes. The declaration states that c1 takes a single `char' argument, whilst the definition states that it takes a single `int' argument. > int c4 (char c); > int c4 (int c) { return 1 ;} > proto.c:17: conflicting types for `c4' > proto.c:16: previous declaration of `c4' This is identical to c3. >To me, c2() seems as bad as the others, and i don't understand why >the compiler does not complain. This is according to the ANSI standard rules. > It seems that when the prototype >declares an "int" argument, then any signed/unsigned type is accepted >for that argument in the non-ansi function body. Any char, short or int argument is acceptable. long isn't and I'd need to check on unsigned. > As you can imagine >this defeats the usefulness of prototypes and obfuscates code. Not true. It complies with the K&R C calling conventions. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 13:20:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24380 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 13:20:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from galea.com (Odie.Galea.Com [205.237.227.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24371 for ; Thu, 29 Oct 1998 13:20:03 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from gotlib.galea.com (Gotlib.Galea.Com [205.237.227.60]) by galea.com (8.6.11/8.6.9) with SMTP id QAA15647; Thu, 29 Oct 1998 16:35:09 -0500 Received: from videotron.ca ([205.237.227.166]) by gotlib.galea.com (Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) with SMTP id 852566AC.00752245; Thu, 29 Oct 1998 16:19:24 -0500 Message-ID: <3638DC0A.EE8C80A5@videotron.ca> Date: Thu, 29 Oct 1998 16:20:10 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security Inc. X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Jason Thorpe CC: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port References: <199810291940.LAA16928@lestat.nas.nasa.gov> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Thorpe wrote: > > On Thu, 29 Oct 1998 14:17:20 -0500 > "Stephane E. Potvin" wrote: > > > port using netbsd as host but as the hw is not yet ready we are using an > > ebsa285 board to do the prototyping and I was told that netBSD doesn't > > support it natively (though I could be mistaken). > > NetBSD-current does indeed run on the EBSA285. I was told that it wouldn't work natively because of the lack of BIOS/RTC. Maybe they use the Angel PBL to load the image even if there's no BIOS. I'll check it out later on tonight. Thanks for the tip... Stephane E. Potvin Galea Network Security. --- La vie est trop courte pour etre prise au serieux. anonyme To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 13:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25526 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 13:32:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25521 for ; Thu, 29 Oct 1998 13:32:07 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with SMTP id NAA18297; Thu, 29 Oct 1998 13:30:57 -0800 (PST) Message-Id: <199810292130.NAA18297@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: localhost [127.0.0.1] didn't use HELO protocol To: "Stephane E. Potvin" Cc: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 29 Oct 1998 13:30:56 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998 16:20:10 -0500 "Stephane E. Potvin" wrote: > I was told that it wouldn't work natively because of the lack of > BIOS/RTC. Maybe they use the Angel PBL to load the image even if there's > no BIOS. I'll check it out later on tonight. BIOS? What's that? :-) You have to have console firmware, yes. That which loads the firmware doesn't have enuf smarts to load the kernel. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: +1 408 866 1912 NAS: M/S 258-5 Work: +1 650 604 0935 Moffett Field, CA 94035 Pager: +1 650 940 5942 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 13:56:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28401 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 13:56:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gamma.aei.ca (gamma.aei.ca [206.123.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28396 for ; Thu, 29 Oct 1998 13:56:14 -0800 (PST) (envelope-from malartre@aei.ca) Received: from aei.ca (aeiusrF-22.aei.ca [206.186.205.22]) by gamma.aei.ca (8.8.5/8.8.5) with ESMTP id QAA21782; Thu, 29 Oct 1998 16:56:06 -0500 (EST) Message-ID: <3638E436.C685F828@aei.ca> Date: Thu, 29 Oct 1998 16:55:02 -0500 From: Malartre X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: "Stephane E. Potvin" CC: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port References: <3638BF40.304CB4F0@videotron.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephane E. Potvin wrote: > > For a project I have here I need to port FreeBSD to an arm architecture > (SA110 processor with a 21285 as pci/memory controller). Is there anyone > currently working on this? I remember some discussions about arm support > a few weeks ago but I can't quite remember is someone was actively doing > it. I'll search the archives later on this afternoon... > > Before I RTFM and try to learn how to add the support to the FreeBSD gcc > compiler to cross-compile from our i386-unknown-freebsd3.0 to > arm-unknown-freebsd3.0 I wanted to check if anyone had already done this > or was in the process of doing so. I guess it would be easier to do the > port using netbsd as host but as the hw is not yet ready we are using an > ebsa285 board to do the prototyping and I was told that netBSD doesn't > support it natively (though I could be mistaken). > > Also, some pointers as to what are the main steps for doing such a port > (FreeBSD port as a whole) would be greatly appreciated. > > Comments, pros, cons are welcome :) > > Regards, > > Stephane E. Potvin > Galea Network Security > > --- > La vie est trop courte pour etre prise au serieux. > anonyme > > P.S.: Sorry if it's on the wrong list. Feel free to follow up at the > right place if it's the case. Salut Un autre francophone :-) http://www.aei.ca/~malartre/bsd-fr.html @+ -- [Malartre][malartre@aei.ca][http://www.aei.ca/~malartre/] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01141 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:17:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01127 for ; Thu, 29 Oct 1998 14:17:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id OAA29402; Thu, 29 Oct 1998 14:16:50 -0800 (PST) (envelope-from obrien) Message-ID: <19981029141650.A29353@nuxi.com> Date: Thu, 29 Oct 1998 14:16:50 -0800 From: "David O'Brien" To: Archie Cobbs , =?iso-8859-1?Q?Dag-Erling_Coidan_Sm=F8rgrav?= Cc: hackers@FreeBSD.ORG Subject: Re: s/bpfilter/bpf/ Reply-To: obrien@NUXI.com References: <86u30n7bk9.fsf@niobe.ewox.org> <199810291922.LAA27011@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810291922.LAA27011@bubba.whistle.com>; from Archie Cobbs on Thu, Oct 29, 1998 at 11:22:38AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While you're at it, could you also fix the /dev/MAKEDEV script > so if you say sh MAKEDEV bpf3 it makes bpf0, bpf1, and bpf2 as > well? Done. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:20:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01031 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:16:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA01005 for ; Thu, 29 Oct 1998 14:16:54 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zZ0My-00076G-00; Thu, 29 Oct 1998 15:16:40 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id PAA17442; Thu, 29 Oct 1998 15:16:27 -0700 (MST) Message-Id: <199810292216.PAA17442@harmony.village.org> To: "Stephane E. Potvin" Subject: Re: FreeBSD arm port Cc: Hackers@freebsd.org In-reply-to: Your message of "Thu, 29 Oct 1998 14:17:20 EST." <3638BF40.304CB4F0@videotron.ca> References: <3638BF40.304CB4F0@videotron.ca> Date: Thu, 29 Oct 1998 15:16:26 -0700 From: Warner Losh Sender: owner-freebsd-hackers@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG In message <3638BF40.304CB4F0@videotron.ca> "Stephane E. Potvin" writes: : For a project I have here I need to port FreeBSD to an arm architecture : Before I RTFM and try to learn how to add the support to the FreeBSD gcc : compiler to cross-compile from our i386-unknown-freebsd3.0 to : arm-unknown-freebsd3.0 I wanted to check if anyone had already done this : or was in the process of doing so. I guess it would be easier to do the : port using netbsd as host but as the hw is not yet ready we are using an : ebsa285 board to do the prototyping and I was told that netBSD doesn't : support it natively (though I could be mistaken). The cross compilation may be a bit of a problem. while the binutitls are setup to easily build different targets, the current gcc in the tree isn't setup to do that at all. I'm working on "fixing" that for a target that I'm working on. Once that is done, the cross compiler stuff should be fairly simple and easy. Until that happens, however, your best bet may be to use gcc 2.8.1 or egcs and configure it --target arm-unknown-freebsd3.0. You'll need to write some files to support this, but configure will tell you which ones (if you clone the FreeBSD entry). : Also, some pointers as to what are the main steps for doing such a port : (FreeBSD port as a whole) would be greatly appreciated. Step one, get build tools working. Step two-a, get the kernel working Step two-b, get userland working Step three boot. For kernel breakage, see step two-a, for userland breakage, see step two-b :-) You'll need to have at least some of the kernel files in place before you can build a userland. Trying to build the user land will tell you what is missing :-). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:33:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02785 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:33:24 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.kar.net (n180.cdialup.kar.net [195.178.130.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02766 for ; Thu, 29 Oct 1998 14:33:01 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.1/8.8.8) with ESMTP id AAA01672 for ; Fri, 30 Oct 1998 00:32:49 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Fri, 30 Oct 1998 00:32:48 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810290446.UAA00420@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Oct 1998, Mike Smith wrote: > > Can someone give me a pointer? I'm still running an a.out kernel on a system > > that was installed from a 3.0 snapshot CD and has been kept upto date via cvs > > since. > > make world > > followed by > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > will upgrade you completely. The visible parts of the new loader are > in /boot/loader, and are updated by 'make world'. > Sorry, this is probably stupid question, but all the same. How do I update these boot blocks in a dual-boot situation (wd0s1 - win95, wd0s2 - FreeBSD)? And do I need/can/want to update boot manager to a new boot0 as well (I got a rather oldish BIOS here)? Thanks in advance, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:34:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03104 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:34:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gamma.aei.ca (gamma.aei.ca [206.123.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03063 for ; Thu, 29 Oct 1998 14:33:58 -0800 (PST) (envelope-from malartre@aei.ca) Received: from aei.ca (aeiusrF-22.aei.ca [206.186.205.22]) by gamma.aei.ca (8.8.5/8.8.5) with ESMTP id RAA26869 for ; Thu, 29 Oct 1998 17:33:51 -0500 (EST) Message-ID: <3638ED0E.AEE86EA9@aei.ca> Date: Thu, 29 Oct 1998 17:32:46 -0500 From: Malartre X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port References: <3638BF40.304CB4F0@videotron.ca> <3638E436.C685F828@aei.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Malartre wrote: > > Stephane E. Potvin wrote: > > > > For a project I have here I need to port FreeBSD to an arm architecture > > (SA110 processor with a 21285 as pci/memory controller). Is there anyone > > currently working on this? I remember some discussions about arm support > > a few weeks ago but I can't quite remember is someone was actively doing > > it. I'll search the archives later on this afternoon... > > > > Before I RTFM and try to learn how to add the support to the FreeBSD gcc > > compiler to cross-compile from our i386-unknown-freebsd3.0 to > > arm-unknown-freebsd3.0 I wanted to check if anyone had already done this > > or was in the process of doing so. I guess it would be easier to do the > > port using netbsd as host but as the hw is not yet ready we are using an > > ebsa285 board to do the prototyping and I was told that netBSD doesn't > > support it natively (though I could be mistaken). > > > > Also, some pointers as to what are the main steps for doing such a port > > (FreeBSD port as a whole) would be greatly appreciated. > > > > Comments, pros, cons are welcome :) > > > > Regards, > > > > Stephane E. Potvin > > Galea Network Security > > > > --- > > La vie est trop courte pour etre prise au serieux. > > anonyme > > > > P.S.: Sorry if it's on the wrong list. Feel free to follow up at the > > right place if it's the case. > Salut > Un autre francophone :-) > http://www.aei.ca/~malartre/bsd-fr.html > @+ > -- > [Malartre][malartre@aei.ca][http://www.aei.ca/~malartre/] > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message My error, wasnt supposed to be cc to the hacker list ;-) -- [Malartre][malartre@aei.ca][http://www.aei.ca/~malartre/] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05054 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:45:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05029 for ; Thu, 29 Oct 1998 14:45:43 -0800 (PST) (envelope-from xroot@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id OAA28199; Thu, 29 Oct 1998 14:45:55 -0800 (PST) Message-Id: <199810292245.OAA28199@implode.root.com> To: "Matthew N. Dodd" cc: Karl Denninger , Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-reply-to: Your message of "Thu, 29 Oct 1998 12:06:15 EST." From: David Greenman Reply-To: dg@root.com Date: Thu, 29 Oct 1998 14:45:55 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, 29 Oct 1998, Karl Denninger wrote: >> > You'd proably only see it in RAID5 mode or if you were -really- beating on >> > your array. Still, with that much memory they should make # of tags >> > supported a tunable. >> >> We beat the SHIT out of our arrays, and the big NFS servers run in RAID 5 >> mode :-) > >But how busy is the controller? 50%? More? > >David G. would probably have more information on the CMD's low performance >modes. (Or rather modes where the limited number of taged commands begins >to impose limits on I/O) It's unlikely that you'd be able to get enough concurrency on any "typical" system to see the tag limit. According to the Adaptec person I talked to, the newer CRD-5440's are further limited to just 32 tags. This would totally kill us on wcarchive. For one thing, you'll rarely ever see any seek optimizations - you have to have several tags queued on a drive before it can optimally reorder them. If you've got 36 drives and only 32 tags, well, you have a big problem. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:49:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA05542 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:49:55 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from assurance.rstcorp.com ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA05522 for ; Thu, 29 Oct 1998 14:49:50 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id RAA16822; Thu, 29 Oct 1998 17:48:41 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma016818; Thu, 29 Oct 98 17:48:06 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id RAA17558; Thu, 29 Oct 1998 17:47:52 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id RAA01269; Thu, 29 Oct 1998 17:47:51 -0500 (EST) Date: Thu, 29 Oct 1998 17:47:51 -0500 (EST) Message-Id: <199810292247.RAA01269@jabberwock.rstcorp.com> From: "Viren R. Shah" To: Peter Wemm Cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810290638.OAA04511@spinner.netplex.com.au> References: <199810290638.OAA04511@spinner.netplex.com.au> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "PW" == Peter Wemm writes: >> > disklabel -B -b /boot/boot1 -s /boot/boot2 Here's a pretty naiive question: I installed boot1 and boot2 using the above command. In my case, it was disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/rwd0s3 Prior to this I was using an older version of the bootblocks (circa Oct 1) that loaded /boot/loader. However, everything still looks the same. I still get a boot: prompt (with the help screen above it). Is there any way to find out whether the new boot stages were installed? What should I be seeing with the new boot blocks? [Part of the reason I'm asking this is that I boot FreeBSD using the NT loader, and I'm not entirely certain whether I need to update the NT loader in order to get the new boot blocks running.] PW> Cheers, PW> -Peter Thanks Viren -- Viren R. Shah To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 14:56:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06890 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 14:56:11 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06876 for ; Thu, 29 Oct 1998 14:56:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA00440; Thu, 29 Oct 1998 14:54:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292254.OAA00440@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Hay cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), dfr@nlsystems.com, hackers@FreeBSD.ORG (FreeBSD-hackers) Subject: Re: kld screensavers In-reply-to: Your message of "Sat, 29 Oct 1998 21:22:00 +0200." <199810291922.VAA27010@zibbi.mikom.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 14:54:14 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is this really usefull? The simplest one is the star_saver and its > modevent function will look like this: > > --------- > static int > star_saver_modevent(module_t mod, modeventtype_t type, void *unused) > { > switch (type) { > case MOD_LOAD: > return add_scrn_saver(star_saver); > case MOD_UNLOAD: > return remove_scrn_saver(star_saver); > default: > printf("star_saver module unknown event: 0x%x\n", type); > } > return 0; > } > --------- > > It looks silly to me to put this somewhere generic and call it from each > saver. > > What might be usefull is a macro to define the moduledata_t structure > and do the DECLARE_MODULE() thingy like what is done with CDEV_MODULE, > but even there I'm not sure if you are saving that much. > > But maybe I'm missing something. Actually, I'd put it the other way around and have the screensaver-specific functions call through the module generic handler, so you'd just add extra cases to the switch, and still only have one entrypoint per module. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:06:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08819 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:06:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08806 for ; Thu, 29 Oct 1998 15:06:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00523; Thu, 29 Oct 1998 15:04:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292304.PAA00523@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Vladimir Kushnir cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Fri, 30 Oct 1998 00:32:48 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:04:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > make world > > > > followed by > > > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > > > will upgrade you completely. The visible parts of the new loader are > > in /boot/loader, and are updated by 'make world'. > > > > Sorry, this is probably stupid question, but all the same. How do I update > these boot blocks in a dual-boot situation (wd0s1 - win95, wd0s2 - > FreeBSD)? As above. is the FreeBSD slice. > And do I need/can/want to update boot manager to a new boot0 as > well (I got a rather oldish BIOS here)? You can, but you don't need to. Whether you want to is up to you. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:08:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09561 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:08:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09554 for ; Thu, 29 Oct 1998 15:08:02 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00560; Thu, 29 Oct 1998 15:07:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292307.PAA00560@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephane E. Potvin" cc: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port In-reply-to: Your message of "Thu, 29 Oct 1998 14:17:20 EST." <3638BF40.304CB4F0@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:07:46 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also, some pointers as to what are the main steps for doing such a port > (FreeBSD port as a whole) would be greatly appreciated. Crucial to bringing up any new port is the ability to tighten the build/ debug cycle. If you have an emulator, that's excellent. If you can boot diskless, that's almost as good. Copying kernels onto floppies and lugging them back and forth gets old _really_ quick. You want to start with a skeleton of the new system-specific code, and flesh it out as you go. The first goal is to get enough infrastructure in place to build the kernel. The alpha port is probably a good place to look first, as it's only just starting to put on weight, and has a lot of new architectural stuff in it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:15:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10245 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:15:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10238 for ; Thu, 29 Oct 1998 15:15:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00616; Thu, 29 Oct 1998 15:13:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292313.PAA00616@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Shafia Kausar cc: FreeBSD Hackers , shafiak@ee.tamu.edu Subject: Re: Timer Granularity In-reply-to: Your message of "Thu, 29 Oct 1998 12:41:31 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:13:18 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am new to the FreeBSD OS. I have a few questions for which I could not > find answers on the webpages. > > I am using the FreeBSD version 2.1.5 Relase #2. What is the kernel clock > granularity in this version? 10ms, if I remember correctly. > There are a number of clocks being used in FreeBSD. Which clock is used > for real time kernel processing? Is this accessible to the users? No clocks are "accessible to the users". User applications obtain time values from the system. > Has the timer granularity improved in the releases following this release? Yes. Timer support now offers nanosecond resolution, dependant on the particular clock source(s) in use. > In the /sys/kern/kern_clock.c file the variable time_precision has been > initialised to 1microsec, but it has been stated that the resolution > decreases depending on whether the external clock is working or not. > What is the range of the variation in the resolutuion? It depends on the hardware in use. On some systems the Pentium TSC is available as a time source, in which case time resolution is one CPU cycle. The i8254 timecounter generally has an operating frequency around 1.19MHz, giving a resolution of approximately 1us. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:18:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11013 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:18:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.kar.net (n180.cdialup.kar.net [195.178.130.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10948 for ; Thu, 29 Oct 1998 15:18:25 -0800 (PST) (envelope-from kushn@mail.kar.net) Received: from localhost (volodya@localhost) by mail.kar.net (8.9.1/8.8.8) with ESMTP id BAA02911; Fri, 30 Oct 1998 01:17:40 +0200 (EET) (envelope-from kushn@mail.kar.net) Date: Fri, 30 Oct 1998 01:17:40 +0200 (EET) From: Vladimir Kushnir X-Sender: volodya@kushnir.kiev.ua To: Mike Smith cc: Vladimir Kushnir , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810292304.PAA00523@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Mike Smith wrote: > > Sorry, this is probably stupid question, but all the same. How do I update > > these boot blocks in a dual-boot situation (wd0s1 - win95, wd0s2 - > > FreeBSD)? > > As above. is the FreeBSD slice. > > > And do I need/can/want to update boot manager to a new boot0 as > > well (I got a rather oldish BIOS here)? > > You can, but you don't need to. Whether you want to is up to you. > -- Thanks a lot. So I'm not stuck with the old bootblocks forever (happy smile). What I meant about bootmanager, does it work with the old bios? There were some problems, it seems, and it looks I can't test it from floppy. Thanks again, Vladimir ===========================|======================= Vladimir Kushnir | kushn@mail.kar.net, | Powered by FreeBSD kushnir@ap3.bitp.kiev.ua | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:21:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11555 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:21:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from assurance.rstcorp.com ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11550 for ; Thu, 29 Oct 1998 15:21:45 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id SAA17095; Thu, 29 Oct 1998 18:21:41 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma017093; Thu, 29 Oct 98 18:21:10 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id SAA18031; Thu, 29 Oct 1998 18:21:09 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id SAA00678; Thu, 29 Oct 1998 18:21:07 -0500 (EST) Date: Thu, 29 Oct 1998 18:21:07 -0500 (EST) Message-Id: <199810292321.SAA00678@jabberwock.rstcorp.com> From: "Viren R. Shah" To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810292303.PAA00506@dingo.cdrom.com> References: <199810292247.RAA01269@jabberwock.rstcorp.com> <199810292303.PAA00506@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mike" == Mike Smith writes: >> way to find out whether the new boot stages were installed? What >> should I be seeing with the new boot blocks? Mike> Remove /boot.config. The new loader does its very best to Mike> look-and-feel just like the old one. That definitely changed something. The help screen is no longer shown. So hopefully that means that I'm using the new boot blocks. >> [Part of the reason I'm asking this is that I boot FreeBSD using the >> NT loader, and I'm not entirely certain whether I need to update the >> NT loader in order to get the new boot blocks running.] Mike> No idea. Does the NT loader keep a copy of the first sector of the Mike> partition, or does it just jump there? I checked. It copies it, so I recopied the first sector from the FreeBSD partition. One unexpected side effect of my setup is that when I type in "reboot" at the /boot/loader prompt, I get sent back to the NT loader menu. Thanks for the help. Viren -- Viren R. Shah {viren @ rstcorp . com} "Never hire a ferret to do a weasel's job" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:22:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11694 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:22:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11641 for ; Thu, 29 Oct 1998 15:22:06 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id PAA06088; Thu, 29 Oct 1998 15:21:50 -0800 (PST) (envelope-from jdp) Message-Id: <199810292321.PAA06088@austin.polstra.com> To: moncrg@bt340707.res.ray.com Subject: Re: help with setting up private cvsup mirror In-Reply-To: <3638B02C.F1913CD5@bt340707.res.ray.com> References: <3638B02C.F1913CD5@bt340707.res.ray.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Thu, 29 Oct 1998 15:21:49 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3638B02C.F1913CD5@bt340707.res.ray.com>, Gregory D. Moncreaff wrote: > Is there a "cvsup mirror in N easy steps" page I haven't found yet? Better than that: "ports/net/cvsup-mirror". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:22:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11705 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:22:25 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from login-2.eunet.no (login-2.eunet.no [193.71.71.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11684 for ; Thu, 29 Oct 1998 15:22:15 -0800 (PST) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (mbendiks@login-1.eunet.no [193.71.71.238]) by login-2.eunet.no (8.9.0/8.9.0/GN) with ESMTP id AAA02999 for ; Fri, 30 Oct 1998 00:22:06 +0100 (CET) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.8.8/8.8.8) with SMTP id AAA01825 for ; Fri, 30 Oct 1998 00:22:06 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Fri, 30 Oct 1998 00:22:06 +0100 (CET) From: Marius Bendiksen To: freebsd-hackers@FreeBSD.ORG Subject: Journaling File Systems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking to implement JFS. This would add compatibility with AIX and OS/2, besides which the fs is rock solid and supposedly (at least) comparable to FFS as far as speed is concerned. If I've understood correctly, the journaling technology is not just for stability, but also serves a function similar to softupdates. Needless to say, I'd be a lot more happy about being able to get hold of some specs than I would about having to grab hold of the Eurora Technology Preview and try to hack the filesystem. Reverse-engineering the code is out of the question. --- Marius Bendiksen ... dead girls don't say no ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:22:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10968 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:18:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10950; Thu, 29 Oct 1998 15:18:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00654; Thu, 29 Oct 1998 15:18:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292318.PAA00654@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: synk@swcp.com (Brendan Conoboy), freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: getpwnam() problem? In-reply-to: Your message of "Thu, 29 Oct 1998 11:13:15 PST." <199810291913.LAA26982@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:18:11 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > http://www.freebsd.org/cgi/query-pr.cgi?pr=8176 > > I've located the bug and supplied a patch in a followup... > Very simple bug, someone please commit in 2.2 and 3.0. Done. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:25:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12069 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:25:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12064 for ; Thu, 29 Oct 1998 15:25:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00714; Thu, 29 Oct 1998 15:24:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292324.PAA00714@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Viren R. Shah" cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Thu, 29 Oct 1998 18:21:07 EST." <199810292321.SAA00678@jabberwock.rstcorp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:24:48 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >>>>> "Mike" == Mike Smith writes: > > >> way to find out whether the new boot stages were installed? What > >> should I be seeing with the new boot blocks? > > Mike> Remove /boot.config. The new loader does its very best to > Mike> look-and-feel just like the old one. > > That definitely changed something. The help screen is no longer > shown. So hopefully that means that I'm using the new boot blocks. Yup. With no cues, the new loader will just sit there for a few seconds (you can hit a key at this point and get the boot: prompt and help) and then load /boot/loader. > One unexpected side effect of my setup is that when I type in "reboot" > at the /boot/loader prompt, I get sent back to the NT loader menu. That's correct; 'reboot' actually calls the IPL vector (int19 IIRC), so it's faster than a soft reset. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:28:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12979 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:28:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12974 for ; Thu, 29 Oct 1998 15:28:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00742; Thu, 29 Oct 1998 15:26:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292326.PAA00742@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Vladimir Kushnir cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Fri, 30 Oct 1998 01:17:40 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:26:47 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > And do I need/can/want to update boot manager to a new boot0 as > > > well (I got a rather oldish BIOS here)? > > > > You can, but you don't need to. Whether you want to is up to you. > > Thanks a lot. So I'm not stuck with the old bootblocks forever (happy > smile). What I meant about bootmanager, does it work with the old bios? It *should*. > There were some problems, it seems, and it looks I can't test it from > floppy. That's correct. You can boot from floppy to rescue yourself if you install it though; just type 'wd(0,a)/boot/loader' from the boot: prompt off a floppy. The problematic features are still being studied; what we're looking at at the moment is a set of tests similar to those that the Windows 95 FDISK uses when it asks the "large disk support" question. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:51:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16471 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:51:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16456 for ; Thu, 29 Oct 1998 15:51:42 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4014.ime.net [209.90.195.24]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id SAA04645 for ; Thu, 29 Oct 1998 18:51:46 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981029184825.00b115a0@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 29 Oct 1998 18:50:01 -0500 To: hackers@FreeBSD.ORG From: Drew Baxter Subject: Re: FreeBSD 3.0 AOUT Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Haven't migrated up to an ELF system yet because of some remarks about the boot loader... How much damage am I going to get into by make buildworld/make aout-to-elf from 30 miles away? I can make and install the world fine from here, I just wasn't sure of the logistics of me being locked out of my box.. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:55:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17173 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:55:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17157 for ; Thu, 29 Oct 1998 15:55:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00936; Thu, 29 Oct 1998 15:55:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292355.PAA00936@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Drew Baxter cc: hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.0 AOUT In-reply-to: Your message of "Thu, 29 Oct 1998 18:50:01 EST." <4.1.19981029184825.00b115a0@genesis.ispace.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:55:18 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Haven't migrated up to an ELF system yet because of some remarks about the > boot loader... > > How much damage am I going to get into by make buildworld/make aout-to-elf > from 30 miles away? I can make and install the world fine from here, I > just wasn't sure of the logistics of me being locked out of my box.. Just migrating to ELF still leaves you with an a.out kernel. No risk as long as you update /etc/rc at the same time. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 15:58:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17737 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 15:58:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Loki.orland.u91.k12.me.us (Loki.orland.u91.k12.me.us [169.244.111.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17730 for ; Thu, 29 Oct 1998 15:58:46 -0800 (PST) (envelope-from netmonger@genesis.ispace.com) Received: from Celeris (56k-port4014.ime.net [209.90.195.24]) by Loki.orland.u91.k12.me.us (8.9.1/8.8.8-Loki) with SMTP id SAA04652; Thu, 29 Oct 1998 18:58:39 -0500 (EST) (envelope-from netmonger@genesis.ispace.com) X-Server-ID: Loki.orland.u91.k12.me.us, OCSNet - Orland Maine USA X-Coord-Name: Drew "Droobie" Baxter, OneNetwork Exchange X-Coord-Addr: Droobie@Openlink.orland.me.us X-Coord-Pager: USA: 207-471-2719, http://pagedroo.orland.me.us Message-Id: <4.1.19981029185602.00920f00@genesis.ispace.com> X-Sender: netmonger@genesis.ispace.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 29 Oct 1998 18:56:53 -0500 To: Mike Smith From: Drew Baxter Subject: Re: FreeBSD 3.0 AOUT Cc: hackers@FreeBSD.ORG In-Reply-To: <199810292355.PAA00936@dingo.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:55 PM 10/29/98 -0800, Mike Smith wrote: >> Haven't migrated up to an ELF system yet because of some remarks about the >> boot loader... >> >> How much damage am I going to get into by make buildworld/make aout-to-elf >> from 30 miles away? I can make and install the world fine from here, I >> just wasn't sure of the logistics of me being locked out of my box.. > >Just migrating to ELF still leaves you with an a.out kernel. No risk >as long as you update /etc/rc at the same time. > >-- >\\ Sometimes you're ahead, \\ Mike Smith >\\ sometimes you're behind. \\ mike@smith.net.au >\\ The race is long, and in the \\ msmith@freebsd.org >\\ end it's only with yourself. \\ msmith@cdrom.com > Hmm.. what needs to be changed there? I was thinking OBJFORMAT=... but I thought that was in a different file.. --- Drew "Droobie" Baxter Network Admin/Professional Computer Nerd(TM) OneEX: The OneNetwork Exchange 207-942-0275 http://www.droo.orland.me.us My Latest Kernel: FreeBSD 3.0-CURRENT (ONEEX) #14: Mon Oct 19 22:36:58 EDT 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 16:01:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18216 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 16:01:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18183 for ; Thu, 29 Oct 1998 16:00:55 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00968; Thu, 29 Oct 1998 15:59:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810292359.PAA00968@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Roger Hardiman cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: Kernel config - passing flags to a PCI device In-reply-to: Your message of "Wed, 28 Oct 1998 19:07:53 GMT." <36376B89.41C6@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 15:59:26 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Roger wrote > > > Is it possible to pass flags from a kernel config to a PCI device > > > I would like them in the bt848/878 driver. > > > eg, device bktr0 flags 0x0103 > > > > > Mike wrote > > No. You should be detecting this automatically > > anyway; that's what PCI is for. > > I agree you can read a manufacturer and model number from PCI chips. > Very usefull too. > In my case, I need the flags for things you cannot discover from the > PCI chipset. I'm curious; how does the vendor-supplied software know whether it's talking to the right sort of card? Does it just make assumptions? > CASE 2: On the Bt848 based frame grabbers, all you can get back from > the PCI probe is "Manufacturer - Brooktree" and "model - BT848" Each of > the different TV cards based on the bt848 use different tuner types. > There is no way to probe the card to determine the tuner type or the OEM > of the TV card. Currently, there are more kernel options and even some > sysctls to specify this to the kernel driver. I would like this to be in > a flags setting for each card. Use an ioctl to configure the driver on a per-device basis. Have a control app that reads a configuration file using a user-supplied model name as an index. Don't get sidetracked by a stupid anti-ioctl flameware again. Alternatively, use a sysctl node and instantiate multiple settings groups yourself. This sucks more than it should because of the way that sysctl works at the moment. > So, back to the question. How can I pass flags to a PCI device? You don't. You never will. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 16:09:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19217 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 16:09:17 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19211 for ; Thu, 29 Oct 1998 16:09:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01062 for ; Thu, 29 Oct 1998 16:09:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300009.QAA01062@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: New bootloader, PnP scanning Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 16:09:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quick call to anyone running the new /boot/loader, can you try the 'pnpscan -v' command and make sure that it looks sensible for your system? Ideally you should see a collection of unidentified PNP???? items (motherboard peripherals), any ISA PnP peripherals you have, and any PCI peripherals. I'm particularly interested in knowing if it works properly on systems with embedded ISA PnP devices on the motherboard (or non-ISA PnP stuff, eg. laptops), as well as systems with PCI:PCI bridges. Thanks. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 16:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20792 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 16:25:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.iserver.com (gatekeeper.iserver.com [206.107.170.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20774; Thu, 29 Oct 1998 16:25:10 -0800 (PST) (envelope-from hart@iserver.com) Received: by gatekeeper.iserver.com; Thu, 29 Oct 1998 17:25:05 -0700 (MST) Received: from unknown(192.168.1.109) by gatekeeper.iserver.com via smap (V3.1.1) id xma019844; Thu, 29 Oct 98 17:24:37 -0700 Received: (hart@localhost) by anchovy.orem.iserver.com (8.8.8) id RAA07147; Thu, 29 Oct 1998 17:23:57 -0700 (MST) Date: Thu, 29 Oct 1998 17:23:57 -0700 (MST) From: Paul Hart X-Sender: hart@anchovy.orem.iserver.com To: Archie Cobbs cc: Brendan Conoboy , freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: getpwnam() problem? In-Reply-To: <199810291913.LAA26982@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Archie Cobbs wrote: > Brendan Conoboy writes: > > > A couple weeks ago I filled out a little bug report with the GNATS > > form, but it's received no attention (maybe I should have marked it as > > critical?). Anyway, since it may well be security related, I wanted to > > point it out here. The condensed version is that if getpwnam() is > > given a very large string (say a few thousand characters) it will > > sigsegv or sigbus. This is true for 2.2.7-stable (as of a few weeks > > ago) and 3.0-release. Perhaps it's nothing, perhaps it's something, > > but it certainly doesn't happen on a whole slew of other OSes. The > > problem report is at: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=8176 > > I've located the bug and supplied a patch in a followup... > Very simple bug, someone please commit in 2.2 and 3.0. I'm running 2.2.7-RELEASE and the How-To-Repeat section in the PR above lists: #include #include #include char zeename[] = "AVeryLongStringGoesHere"; struct passwd *gunk; main() { gunk = getpwnam(zeename); } as sample code to exercise the bug in getpwnam(). However, it seems to have no affect. No SIGBUS or SIGSEGV that I can see. The patch in the PR for /usr/src/lib/libc/gen/getpwent.c shows that I have (presumably) vulnerable code at the diff location, but I don't seem to be experiencing problems with it. Has anyone else noticed these symptoms? Paul Hart -- Paul Robert Hart ><8> ><8> ><8> Verio Web Hosting, Inc. hart@iserver.com ><8> ><8> ><8> http://www.iserver.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 16:32:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22292 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 16:32:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22284 for ; Thu, 29 Oct 1998 16:32:55 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id TAA21242 for ; Thu, 29 Oct 1998 19:11:21 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Thu, 29 Oct 1998 19:11:21 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: hackers@FreeBSD.ORG Subject: NFS sysctls and LINT options Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG anyone feel on elaborating on the vfs.nfs.* sysctls and NFS options in the kernel a bit? manpage? comments in LINT? anything? Also, what about large files and NFS, anyone have an idea what's up? thank you, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 16:35:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22522 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 16:35:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from Gatekeeper.Alameda.net (gatekeeper.Alameda.net [207.90.181.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22501 for ; Thu, 29 Oct 1998 16:34:59 -0800 (PST) (envelope-from ulf@Gatekeeper.Alameda.net) Received: by Gatekeeper.Alameda.net (8.8.8/8.8.6) id QAA19695; Thu, 29 Oct 1998 16:34:54 -0800 (PST) Message-ID: <19981029163453.A15208@Alameda.net> Date: Thu, 29 Oct 1998 16:34:54 -0800 From: Ulf Zimmermann To: "Matthew N. Dodd" , Karl Denninger Cc: Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm Reply-To: ulf@Alameda.net References: <19981029105316.A27621@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew N. Dodd on Thu, Oct 29, 1998 at 11:57:30AM -0500 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 2.2.6-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 11:57:30AM -0500, Matthew N. Dodd wrote: > On Thu, 29 Oct 1998, Karl Denninger wrote: > > Hmmm... I'll look into this. We haven't gotten tag reduction warnings > > on any of our NFS fileservers using these, nor on our INN machine > > (which uses them in RAID 0+1 config). > > You'd proably only see it in RAID5 mode or if you were -really- beating on > your array. Still, with that much memory they should make # of tags > supported a tunable. > > I really want to find a cheap CRD-5440 just for kicks. 1 host and 2 disk > channels is just right for a small server. Looking for something like that for a long time. Nothing found below $2k so far, which is far too much from my opinion. > > -- > | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | > | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 17:06:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27032 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 17:06:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27009; Thu, 29 Oct 1998 17:06:01 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id RAA27680; Thu, 29 Oct 1998 17:05:58 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma027677; Thu Oct 29 17:05:48 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id RAA09541; Thu, 29 Oct 1998 17:05:48 -0800 (PST) From: Archie Cobbs Message-Id: <199810300105.RAA09541@bubba.whistle.com> Subject: Re: getpwnam() problem? In-Reply-To: from Paul Hart at "Oct 29, 98 05:23:57 pm" To: hart@iserver.com (Paul Hart) Date: Thu, 29 Oct 1998 17:05:48 -0800 (PST) Cc: archie@whistle.com, synk@swcp.com, freebsd-security@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul Hart writes: > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=8176 > > > > I've located the bug and supplied a patch in a followup... > > Very simple bug, someone please commit in 2.2 and 3.0. > > I'm running 2.2.7-RELEASE and the How-To-Repeat section in the PR above > lists: > > #include > #include > #include > > char zeename[] = "AVeryLongStringGoesHere"; > struct passwd *gunk; > > main() > { > gunk = getpwnam(zeename); > } > > as sample code to exercise the bug in getpwnam(). However, it seems to > have no affect. No SIGBUS or SIGSEGV that I can see. The patch in the PR > for /usr/src/lib/libc/gen/getpwent.c shows that I have (presumably) > vulnerable code at the diff location, but I don't seem to be experiencing > problems with it. Has anyone else noticed these symptoms? The sample program doesn't cause the bug. Try replacing "zeename" with a string of 12000 characters.. then you'll see it. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 17:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28299 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 17:14:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail3.microsoft.com (mail3.microsoft.com [131.107.3.123]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28294 for ; Thu, 29 Oct 1998 17:14:13 -0800 (PST) (envelope-from sgasch@microsoft.com) Received: by mail3.microsoft.com with Internet Mail Service (5.5.2232.9) id ; Thu, 29 Oct 1998 17:14:10 -0800 Message-ID: <61AC5C9A4B9CD11181A200805F57CD540700D8DA@RED-MSG-44> From: Scott Gasch To: "'hackers@freebsd.org'" Subject: Q: Status of CDR support? Date: Thu, 29 Oct 1998 17:14:05 -0800 X-Mailer: Internet Mail Service (5.5.2232.9) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I am curious as to the current support for CDR/CDRW devices. The handbook says only old HP, Philips and Plasmon (whoever they are) are supported. However a search of the mailing list archives seems to suggest a beta IDE/Atapi driver is in the works. The Hardware.txt file in today's snapshot makes no reference to this... Can somone enumerate what drives are known to work, what drives are suspected to work, and what drives may work sometime soon? Thanks, Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 17:43:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02441 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 17:43:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02429 for ; Thu, 29 Oct 1998 17:43:41 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id MAA04153; Fri, 30 Oct 1998 12:13:23 +1030 (CST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <61AC5C9A4B9CD11181A200805F57CD540700D8DA@RED-MSG-44> Date: Fri, 30 Oct 1998 12:13:21 +1030 (CST) From: "Daniel O'Connor" To: Scott Gasch Subject: RE: Q: Status of CDR support? Cc: "hackers@freebsd.org" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Oct-98 Scott Gasch wrote: > a search of the mailing list archives seems to suggest a beta IDE/Atapi > driver is in > Can somone enumerate what drives are known to work, what drives are > suspected > to work, and what drives may work sometime soon? Well, you don't have to use the worm driver, because cdrecord exists and it supports many more drives.. It talks to the cdr directly using SCSI commands. cdrecord doesn't support IDE drives under FreeBSD (I think it does under Linux), but its support of SCSI drives is excellent. --------------------------------------------------------------------- |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-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 18:22:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09420 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 18:22:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from limbo.rtfm.net (limbo.rtfm.net [207.198.222.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09360 for ; Thu, 29 Oct 1998 18:22:38 -0800 (PST) (envelope-from nathan@limbo.rtfm.net) Received: (from nathan@localhost) by limbo.rtfm.net (8.9.1/8.9.1) id VAA00295; Thu, 29 Oct 1998 21:18:42 -0500 (EST) (envelope-from nathan) Message-ID: <19981029211841.A269@rtfm.net> Date: Thu, 29 Oct 1998 21:18:41 -0500 From: Nathan Dorfman To: Scott Gasch , freebsd-hackers@FreeBSD.ORG Subject: Re: Q: Status of CDR support? References: <61AC5C9A4B9CD11181A200805F57CD540700D8DA@RED-MSG-44> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <61AC5C9A4B9CD11181A200805F57CD540700D8DA@RED-MSG-44>; from Scott Gasch on Thu, Oct 29, 1998 at 05:14:05PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 29, 1998 at 05:14:05PM -0800, Scott Gasch wrote: > Hello, > > I am curious as to the current support for CDR/CDRW devices. The handbook > says only old HP, Philips and Plasmon (whoever they are) are supported. > However > a search of the mailing list archives seems to suggest a beta IDE/Atapi > driver is in > the works. The Hardware.txt file in today's snapshot makes no reference to > this... > > Can somone enumerate what drives are known to work, what drives are > suspected > to work, and what drives may work sometime soon? Get a copy of cdrecord (/usr/ports/sysutils/cdrecord; or get the tarball from ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/). This is the de facto Unix CD burning software. It is the recommended way of burning CDs under FreeBSD (since worm0 left when CAM came in, possibly the only practical way). Inside you should see a list of hardware supported, and it is definitely more extensive than what you listed, so don't fret :-) If you don't have a SCSI CD-R drive, I'm pretty sure you're SOL. AFAICS, cdrecord is SCSI at heart. There was discussion here about experimental ATAPI/IDE burner support but I don't know where it went. Just avoid the giant IDE conspiracy altogether and get SCSI if you can. Just say NO to IDE. IDE sucks. And so on :-) > Thanks, > Scott -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 18:56:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14001 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 18:56:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13932 for ; Thu, 29 Oct 1998 18:55:58 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id VAA00323; Thu, 29 Oct 1998 21:58:26 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Thu, 29 Oct 1998 21:58:26 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: New bootloader, PnP scanning In-Reply-To: <199810300009.QAA01062@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG just installed the new bootloader, VERY cool :) urm, where is boot.help for it? anyhow here's that pnp info you wanted: (copied by hand) Probing PnP BIOS Probing ISA BUS Probing PCI BIOS PNP0102 PNP0102 PNP0102 PNP0c01 :System memory PNP0200 PNP0000 PNP0100 PNP0b00 PNP0303 PNP0c04 PNP0800 PNP0903 PNP0f13 PNP0501 PNP0700 PNP0400 YMH0030 :OPL 3-SH Snd System 0x71118086 IDE controller 0x00141011 Ethernet controller 0x905510b7 Ethernet controller (i think i lost a digit here copying might have a leading 0) 0x51b102b Vga display 0x71128086 USB controller it seems to have found everything, like i said VERY cool. i do have 2 ether devices. as well as a windows soundsystem yamaha soundcard... devices on the motherboard: USB, sound and hardrive controller Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Thu, 29 Oct 1998, Mike Smith wrote: > > Just a quick call to anyone running the new /boot/loader, can you try > the 'pnpscan -v' command and make sure that it looks sensible for your > system? Ideally you should see a collection of unidentified PNP???? > items (motherboard peripherals), any ISA PnP peripherals you have, and > any PCI peripherals. > > I'm particularly interested in knowing if it works properly on systems > with embedded ISA PnP devices on the motherboard (or non-ISA PnP stuff, > eg. laptops), as well as systems with PCI:PCI bridges. > > Thanks. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 20:06:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24263 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 20:06:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24257 for ; Thu, 29 Oct 1998 20:06:45 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id XAA10941; Thu, 29 Oct 1998 23:02:11 -0500 (EST) Date: Thu, 29 Oct 1998 23:02:11 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Ulf Zimmermann cc: "Matthew N. Dodd" , Karl Denninger , Hallam Oaks , "hackers@FreeBSD.ORG" Subject: Re: Multi-terabyte disk farm In-Reply-To: <19981029163453.A15208@Alameda.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Ulf Zimmermann wrote: > Looking for something like that for a long time. Nothing found below > $2k so far, which is far too much from my opinion. If anyone is interested, I guess we found a decent supplier :) We're buying the 5440 (4 channel) at about $1900-ish. If there's interest, contact me, and I'll get the info when I'm in the office... Thanks, Charles > > > > > -- > > | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | > > | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | > > | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Regards, Ulf. > > --------------------------------------------------------------------- > Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 > Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 20:14:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA24592 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 20:14:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles148.castles.com [208.214.165.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA24585 for ; Thu, 29 Oct 1998 20:14:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA00437; Thu, 29 Oct 1998 20:14:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300414.UAA00437@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Mike Smith , hackers@FreeBSD.ORG Subject: Re: New bootloader, PnP scanning In-reply-to: Your message of "Thu, 29 Oct 1998 21:58:26 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 20:14:19 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > just installed the new bootloader, VERY cool :) > urm, where is boot.help for it? Syntax is still in flux. Will probably have sectioned help system, but that'll probably be *very* slow off a floppy. Working on it... > PNP0c01 :System memory Interesting that they should put an ID string in for a motherboard device. What motherboard is this? Thanks for the feedback. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 20:54:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28351 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 20:54:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fox.tamu.edu (unix.tamu.edu [128.194.103.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28346 for ; Thu, 29 Oct 1998 20:54:32 -0800 (PST) (envelope-from s0k9955@unix.tamu.edu) Received: from localhost by fox.tamu.edu (8.9.0/8.9.0) with SMTP id WAA04030; Thu, 29 Oct 1998 22:54:08 -0600 (CST) Date: Thu, 29 Oct 1998 22:54:08 -0600 (CST) From: Shafia Kausar To: Mike Smith cc: FreeBSD Hackers , shafiak@ee.tamu.edu Subject: Re: Timer Granularity In-Reply-To: <199810292313.PAA00616@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am confused, On basis of which parameters is the kernel clock granularity defined?? especially when multiple clocks are available. On Thu, 29 Oct 1998, Mike Smith wrote: > > I am new to the FreeBSD OS. I have a few questions for which I could not > > find answers on the webpages. > > > > I am using the FreeBSD version 2.1.5 Relase #2. What is the kernel clock > > granularity in this version? > > 10ms, if I remember correctly. > > > There are a number of clocks being used in FreeBSD. Which clock is used > > for real time kernel processing? Is this accessible to the users? > > No clocks are "accessible to the users". User applications obtain time > values from the system. > > > Has the timer granularity improved in the releases following this release? > > Yes. Timer support now offers nanosecond resolution, dependant on the > particular clock source(s) in use. > > > In the /sys/kern/kern_clock.c file the variable time_precision has been > > initialised to 1microsec, but it has been stated that the resolution > > decreases depending on whether the external clock is working or not. > > What is the range of the variation in the resolutuion? > > It depends on the hardware in use. On some systems the Pentium TSC is > available as a time source, in which case time resolution is one CPU > cycle. The i8254 timecounter generally has an operating frequency > around 1.19MHz, giving a resolution of approximately 1us. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 21:05:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29402 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 21:05:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles148.castles.com [208.214.165.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29212 for ; Thu, 29 Oct 1998 21:05:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00773; Thu, 29 Oct 1998 21:04:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300504.VAA00773@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Shafia Kausar cc: FreeBSD Hackers , shafiak@ee.tamu.edu Subject: Re: Timer Granularity In-reply-to: Your message of "Thu, 29 Oct 1998 22:54:08 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 21:04:46 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am confused, On basis of which parameters is the kernel clock > granularity defined?? especially when multiple clocks are available. At which release level? 2.1.x, 2.2.x or 3.x? As a general rule, the best available clock is used. The techniques used to determine which clock is best, and to ensure accurate counts vary from release to release, with a general trend towards better. > > On Thu, 29 Oct 1998, Mike Smith wrote: > > > > I am new to the FreeBSD OS. I have a few questions for which I could not > > > find answers on the webpages. > > > > > > I am using the FreeBSD version 2.1.5 Relase #2. What is the kernel clock > > > granularity in this version? > > > > 10ms, if I remember correctly. > > > > > > There are a number of clocks being used in FreeBSD. Which clock is used > > > for real time kernel processing? Is this accessible to the users? > > > > No clocks are "accessible to the users". User applications obtain time > > values from the system. > > > > > Has the timer granularity improved in the releases following this release? > > > > Yes. Timer support now offers nanosecond resolution, dependant on the > > particular clock source(s) in use. > > > > > In the /sys/kern/kern_clock.c file the variable time_precision has been > > > initialised to 1microsec, but it has been stated that the resolution > > > decreases depending on whether the external clock is working or not. > > > What is the range of the variation in the resolutuion? > > > > It depends on the hardware in use. On some systems the Pentium TSC is > > available as a time source, in which case time resolution is one CPU > > cycle. The i8254 timecounter generally has an operating frequency > > around 1.19MHz, giving a resolution of approximately 1us. > > > > -- > > \\ Sometimes you're ahead, \\ Mike Smith > > \\ sometimes you're behind. \\ mike@smith.net.au > > \\ The race is long, and in the \\ msmith@freebsd.org > > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 21:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29961 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 21:22:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29953 for ; Thu, 29 Oct 1998 21:22:05 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40365>; Fri, 30 Oct 1998 16:21:23 +1100 Date: Fri, 30 Oct 1998 16:21:51 +1100 From: Peter Jeremy Subject: sync writes with softupdates enabled To: hackers@FreeBSD.ORG Message-Id: <98Oct30.162123est.40365@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just installed 3.0-RELEASE on the machine destined to be our new news server. Whilst testing it with soft updates enabled, I'm seeing a lot of sync writes onto /usr: /dev/wd0s1f on /usr (local, soft-updates, writes: sync 32910 async 4955) With /usr mounted asynchronously rather than soft updates enabled, I also saw lots of synchronous writes. The writes are definitely a result of innd - nothing else much is running and pausing innd makes the I/O stop. I've looked at a ktrace of innd and can't see anything that would obviously cause it to do sync writes (no fsync() or open(O_SYNC) calls). It's inn-1.7.2 as per the ports with the exception that MMAP is enabled for dbz. All I can think of is that the MMAP'd history file is causing the kernel to unnecessarily perform sync writes to try and keep the MMAP and VFS images in sync. Any ideas? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 21:29:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00475 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 21:29:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles148.castles.com [208.214.165.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00470 for ; Thu, 29 Oct 1998 21:29:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00927; Thu, 29 Oct 1998 21:29:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300529.VAA00927@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Jeremy cc: hackers@FreeBSD.ORG Subject: Re: sync writes with softupdates enabled In-reply-to: Your message of "Fri, 30 Oct 1998 16:21:51 +1100." <98Oct30.162123est.40365@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 Oct 1998 21:29:10 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just installed 3.0-RELEASE on the machine destined to be our new > news server. Whilst testing it with soft updates enabled, I'm seeing > a lot of sync writes onto /usr: > > /dev/wd0s1f on /usr (local, soft-updates, writes: sync 32910 async 4955) > > With /usr mounted asynchronously rather than soft updates enabled, > I also saw lots of synchronous writes. > > The writes are definitely a result of innd - nothing else much is > running and pausing innd makes the I/O stop. I've looked at a > ktrace of innd and can't see anything that would obviously cause it > to do sync writes (no fsync() or open(O_SYNC) calls). > > It's inn-1.7.2 as per the ports with the exception that MMAP is > enabled for dbz. > > All I can think of is that the MMAP'd history file is causing the > kernel to unnecessarily perform sync writes to try and keep the > MMAP and VFS images in sync. That's almost certainly correct. Try running without mmap. It used to be faster that way; maybe it is again? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 22:17:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04336 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 22:17:28 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04330 for ; Thu, 29 Oct 1998 22:17:24 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id BAA01820; Fri, 30 Oct 1998 01:17:17 -0500 (EST) (envelope-from luoqi) Date: Fri, 30 Oct 1998 01:17:17 -0500 (EST) From: Luoqi Chen Message-Id: <199810300617.BAA01820@lor.watermarkgroup.com> To: mike@smith.net.au, peter.jeremy@auss2.alcatel.com.au Subject: Re: sync writes with softupdates enabled Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > All I can think of is that the MMAP'd history file is causing the > > kernel to unnecessarily perform sync writes to try and keep the > > MMAP and VFS images in sync. > > That's almost certainly correct. Try running without mmap. It used to > be faster that way; maybe it is again? > It may be related to vfs_msync() not respecting MNT_NOWAIT flags when calling vm_object_page_clean(). -lq > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 29 23:53:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00760 for freebsd-hackers-outgoing; Thu, 29 Oct 1998 23:53:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00755 for ; Thu, 29 Oct 1998 23:53:50 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id IAA03998; Fri, 30 Oct 1998 08:53:37 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199810300753.IAA03998@freebsd.dk> Subject: Re: Q: Status of CDR support? In-Reply-To: <19981029211841.A269@rtfm.net> from Nathan Dorfman at "Oct 29, 1998 9:18:41 pm" To: nathan@rtfm.net (Nathan Dorfman) Date: Fri, 30 Oct 1998 08:53:37 +0100 (CET) Cc: sgasch@microsoft.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nathan Dorfman wrote: > > If you don't have a SCSI CD-R drive, I'm pretty sure you're SOL. AFAICS, > cdrecord is SCSI at heart. There was discussion here about experimental > ATAPI/IDE burner support but I don't know where it went. Just avoid the > giant IDE conspiracy altogether and get SCSI if you can. Just say NO to > IDE. IDE sucks. And so on :-) No, he just needs to run 3.0 or later, there is support for IDE CD-R/RW, and it works with Phillips, HP, BTC and mitsumi drives. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 00:08:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02428 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 00:08:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.aussie.org (hallam.lnk.telstra.net [139.130.54.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02423 for ; Fri, 30 Oct 1998 00:08:48 -0800 (PST) (envelope-from mlnn4@oaks.com.au) Received: from bigbox (dialup-b1-29.raytrace.com [203.29.75.73]) by mail.aussie.org (8.9.0/8.9.0) with SMTP id TAA03591 for ; Fri, 30 Oct 1998 19:08:44 +1100 (EST) Message-Id: <199810300808.TAA03591@mail.aussie.org> From: "Hallam Oaks" To: "hackers@FreeBSD.ORG" Date: Fri, 30 Oct 1998 19:09:02 +1100 Reply-To: "Hallam Oaks" X-Mailer: PMMail 98 Standard (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Fibre channel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm now going to demonstrate my total ignorance of fibre channel ;) Who here can tell me what we need to set up a working fibre channel hard drive system, apart from the controller and drive ? I'm not referring specifically to FC on FreeBSD per se, but the actual hardware. I know I'd (obviously) need some fibre optic cable, but I'm unsure if you also need an external optical transciever. That is, I'm unsure if these are built into the FC hardware, or if the FC devices connect to the transcievers via some sort of standard electrical - rather than optical - interface. If so, does anyone know how much these transcievers tend to cost (low power type) ? What else is needed to have a working system ? (apart from the driver software that is ... at the moment I'm only concerned about hardware.) regards, -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 00:14:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02999 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 00:14:04 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles148.castles.com [208.214.165.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02994 for ; Fri, 30 Oct 1998 00:14:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA01726 for ; Fri, 30 Oct 1998 00:13:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810300813.AAA01726@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG Subject: scanf in the kernel? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 00:13:48 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just wondering what the general feeling would be about having scanf in the kernel? As we move towards more abstract representations of things (eg. device names), it's becoming more important to be able to parse strings inside the kernel. Doing this in hand-rolled code is tedious, error-prone and results in code that can be hard to read and maintain (as everyone does it their own way). If this isn't totally repulsive, I'll roll a somewhat smaller version of the libc vfscanf for general approval. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 00:22:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03972 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 00:22:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA03967 for ; Fri, 30 Oct 1998 00:22:17 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id HAA09223; Fri, 30 Oct 1998 07:18:23 +0100 From: Luigi Rizzo Message-Id: <199810300618.HAA09223@labinfo.iet.unipi.it> Subject: Re: scanf in the kernel? To: mike@smith.net.au (Mike Smith) Date: Fri, 30 Oct 1998 07:18:22 +0100 (MET) Cc: hackers@FreeBSD.ORG In-Reply-To: <199810300813.AAA01726@dingo.cdrom.com> from "Mike Smith" at Oct 30, 98 00:13:29 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If this isn't totally repulsive, I'll roll a somewhat smaller version > of the libc vfscanf for general approval. fully agree. How big would it be ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 01:43:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10770 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 01:43:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10765 for ; Fri, 30 Oct 1998 01:43:07 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA02509; Fri, 30 Oct 1998 09:44:35 GMT Date: Fri, 30 Oct 1998 09:44:35 +0000 (GMT) From: Doug Rabson To: Kazutaka YOKOTA cc: John Hay , FreeBSD-hackers Subject: Re: kld screensavers In-Reply-To: <199810291457.XAA12116@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Kazutaka YOKOTA wrote: > > >It looks about right and SI_SUB_PSEUDO is sufficiently late that it > >shouldn't disturb anything. Any time after SI_SUB_CONFIGURE should work I > >think. > > > >It would be nice if the add_scrn_saver/remove_scrn_saver goop was factored > >into a generic module event handler which can be used by all screen > >savers. Have a look at the CDEV_MODULE #define in sys/conf.h for a > >possible way of doing this. > > > >If the generic module handler chains onto an optional user-supplied > >handler, then extra initialisation (allocating message in this case) can > >be done by each saver without repeating the registration code. > > You mean something like this? > > 1. Define generic_screen_saver_module_handler() in syscons.c or somewhere. > 2. Each screen saver module define its own event handler. It will call > the generic handler first and then do its own extra house keeping. Thats more or less what I was suggesting. Simple screen savers wouldn't even need an event handler. Maybe something like: struct saver_module_data { modeventhand_t chainevh; void* chainarg; void (*saver)(int); }; #defined SAVER_MODULE(name, fn, evh, arg) \ static struct saver_module_data name##_saver_mod = { \ evh, arg, fn \ }; \ \ static moduledata_t name##_mod = { \ #name, \ saver_module_handler, \ &name##_saver_mod \ }; \ DECLARE_MODULE(name, name##_mod, SI_SUB_PSEUDO, SI_ORDER_MIDDLE) static int saver_module_handler(module_t mod, modeventtype_t type, void *arg) { struct saver_module_data *data = arg; switch (type) { case MOD_LOAD: return add_scrn_saver(data->saver); case MOD_UNLOAD: return remove_scrn_saver(data->saver); default: printf("star_saver module unknown event: 0x%x\n", type); } if (data->chainevh) return data->chainevh(mod, what, data->chainarg); else return 0; } -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 02:07:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13276 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 02:07:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13263 for ; Fri, 30 Oct 1998 02:07:48 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40347>; Fri, 30 Oct 1998 21:07:12 +1100 Date: Fri, 30 Oct 1998 21:07:36 +1100 From: Peter Jeremy Subject: Re: sync writes with softupdates enabled To: mike@smith.net.au Cc: hackers@FreeBSD.ORG Message-Id: <98Oct30.210712est.40347@border.alcanet.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > All I can think of is that the MMAP'd history file is causing the > kernel to unnecessarily perform sync writes to try and keep the > MMAP and VFS images in sync. Mike Smith wrote: >That's almost certainly correct. Try running without mmap. It used to >be faster that way; maybe it is again? I tried rebuilding it without DBZ-MMAP and it no longer does any sync writes to /usr. I haven't tried following up Luoqi's suggestion as to the possible cause, but this behaviour would seem undesirable - it would seem to nullify many of the advantages of using mmap(2) [I accept that there's a fair amount of black magic involved in making it work at all without a unified buffer cache]. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 02:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14582 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 02:21:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rgate2.ricochet.net (rgate2.ricochet.net [204.179.143.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14577 for ; Fri, 30 Oct 1998 02:21:36 -0800 (PST) (envelope-from enkhyl@scient.com) Received: from mg130-075.ricochet.net (mg130-075.ricochet.net [204.179.130.75]) by rgate2.ricochet.net (8.8.8/8.8.8) with ESMTP id EAA17364; Fri, 30 Oct 1998 04:21:20 -0600 (CST) Date: Fri, 30 Oct 1998 02:20:30 -0800 (PST) From: Christopher Nielsen X-Sender: enkhyl@ender.sf.scient.com Reply-To: enkhyl@hayseed.net To: Hallam Oaks cc: "hackers@FreeBSD.ORG" Subject: Re: Fibre channel In-Reply-To: <199810300808.TAA03591@mail.aussie.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Hallam Oaks wrote: > I'm now going to demonstrate my total ignorance of fibre channel ;) > > Who here can tell me what we need to set up a working fibre channel hard > drive system, apart from the controller and drive ? I'm not referring > specifically to FC on FreeBSD per se, but the actual hardware. > > I know I'd (obviously) need some fibre optic cable, but I'm unsure if you > also need an external optical transciever. That is, I'm unsure if these are > built into the FC hardware, or if the FC devices connect to the transcievers > via some sort of standard electrical - rather than optical - interface. > > If so, does anyone know how much these transcievers tend to cost (low power > type) ? What else is needed to have a working system ? (apart from the driver > software that is ... at the moment I'm only concerned about hardware.) Check out the following URLs. One of them should have the info you're looking for. http://www.fibrechannel.com/ http://www.seagate.com:80/support/disc/papers/fibfs.shtml http://www.seagate.com:80/support/disc/papers/fibp.shtml http://www.seagate.com:80/support/disc/manuals/67496a.pdf -- Christopher Nielsen Scient: The Art and Science of Electronic Business cnielsen@scient.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 02:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16211 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 02:41:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16205 for ; Fri, 30 Oct 1998 02:41:18 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA02651; Fri, 30 Oct 1998 10:43:04 GMT Date: Fri, 30 Oct 1998 10:43:04 +0000 (GMT) From: Doug Rabson To: Mike Smith cc: "Stephane E. Potvin" , Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port In-Reply-To: <199810292307.PAA00560@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Mike Smith wrote: > > Also, some pointers as to what are the main steps for doing such a port > > (FreeBSD port as a whole) would be greatly appreciated. > > Crucial to bringing up any new port is the ability to tighten the build/ > debug cycle. If you have an emulator, that's excellent. If you can > boot diskless, that's almost as good. Copying kernels onto floppies and > lugging them back and forth gets old _really_ quick. The best debugging environment is definately a simulator (but only if it has good hooks into gdb). Netbooting with serial-line debugging runs a close second. I used the excellent SimOS simulator exclusively in the early stages of the FreeBSD/alpha port and was able to get the thing to boot all the way to single-user mode and run a few commands before I touched a real machine. That really shortened the debug time for the real hardware. The SimOS simulator currently supports various mips and alpha cpus. Future versions will have other cpus but the SimOS folks will be able to give you an idea. > > You want to start with a skeleton of the new system-specific code, and > flesh it out as you go. The first goal is to get enough infrastructure > in place to build the kernel. The alpha port is probably a good place > to look first, as it's only just starting to put on weight, and has a > lot of new architectural stuff in it. I think that cloning the alpha port and hacking it is as good a way to start as any. Make sure you have current source trees for the NetBSD and Linux kernel too for cross reference. You have a steep learning curve ahead - good luck! -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 05:16:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04596 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 05:16:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04587 for ; Fri, 30 Oct 1998 05:16:19 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id VAA11350; Fri, 30 Oct 1998 21:14:12 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810301314.VAA11350@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: Mike Smith , "Stephane E. Potvin" , Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port In-reply-to: Your message of "Fri, 30 Oct 1998 10:43:04 GMT." Date: Fri, 30 Oct 1998 21:14:11 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: [..] > I think that cloning the alpha port and hacking it is as good a way to > start as any. Make sure you have current source trees for the NetBSD and > Linux kernel too for cross reference. You have a steep learning curve > ahead - good luck! But when doing this, make *damn sure* that all the necessary credits are given and copyrights respected. Some people are really touchy about that and have been known to flame if the lines are crossed. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 05:45:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08824 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 05:45:05 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from rnocserv.urc.ac.ru (rnocserv.urc.ac.ru [193.233.85.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA08798 for ; Fri, 30 Oct 1998 05:44:31 -0800 (PST) (envelope-from joy@urc.ac.ru) Received: from urc.ac.ru (y.urc.ac.ru [193.233.85.37]) by rnocserv.urc.ac.ru (8.8.8/8.8.8) with ESMTP id SAA07097 for ; Fri, 30 Oct 1998 18:43:43 +0500 (ES) (envelope-from joy@urc.ac.ru) Message-ID: <3639C28F.467FE675@urc.ac.ru> Date: Fri, 30 Oct 1998 18:43:43 +0500 From: Konstantin Chuguev Organization: Southern Ural Regional Center of FREEnet X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: make installworld over NFS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I'm administering several servers and routers (~10 FreeBSD boxes). The most powerful PC of them is a build server, i.e. I run make buildworld on it. Then I'd prefer just to run "make DESTDIR=/net/${HOST} installworld", assuming all other hosts export their /,/usr,/var to the build server. Besides the simplicity, it is also very secure scheme, as most hosts have no access to the build server themselves. All works fine (conceptually), but there are troubles with chflags [no]schg, which don't work over NFS. I have to run some scripts before and after the installworld, and they are not very reliable, because I cannot test files for the immutable flags, only can change them. So, I once parsed the whole distribution searching "schg" and "PRECIOUSLIB" and made a list of such files. I in no way propose to implement schg working over NFS :-) Maybe we can have some variable for make to disable chflags, and a list (automatically generated?) of the immutable flags? Your opinions? Best regards, -- Konstantin V. Chuguev. System administrator of Southern http://www.urc.ac.ru/~joy/ Ural Regional Center of FREEnet, mailto:joy@urc.ac.ru Chelyabinsk, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 07:17:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20180 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 07:17:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA20163 for ; Fri, 30 Oct 1998 07:16:48 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id OAA09884 for hackers@freebsd.org; Fri, 30 Oct 1998 14:13:37 +0100 From: Luigi Rizzo Message-Id: <199810301313.OAA09884@labinfo.iet.unipi.it> Subject: signal 10 to cc ? To: hackers@FreeBSD.ORG Date: Fri, 30 Oct 1998 14:13:36 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, on my test machine after some strange instability i am now getting signal 10 sent to "cc" while building kernels (on a 3.0 snap): /kernel: pid 1269 (cc1), uid 0: exited on signal 10 (core dumped). should i suspect bad hardware ? I already do, because i am getting strange hangups with previously working kernels. luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 07:49:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22860 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 07:49:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from galea.com (Odie.Galea.Com [205.237.227.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA22850 for ; Fri, 30 Oct 1998 07:49:41 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from gotlib.galea.com (Gotlib.Galea.Com [205.237.227.60]) by galea.com (8.6.11/8.6.9) with SMTP id LAA17290; Fri, 30 Oct 1998 11:03:27 -0500 Received: from videotron.ca ([205.237.227.166]) by gotlib.galea.com (Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) with SMTP id 852566AD.0056C224; Fri, 30 Oct 1998 10:47:38 -0500 Message-ID: <3639DFC8.7C3AE9FB@videotron.ca> Date: Fri, 30 Oct 1998 10:48:24 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security Inc. X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Doug Rabson CC: Mike Smith , Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > > On Thu, 29 Oct 1998, Mike Smith wrote: > > > > Also, some pointers as to what are the main steps for doing such a port > > > (FreeBSD port as a whole) would be greatly appreciated. > > > > Crucial to bringing up any new port is the ability to tighten the build/ > > debug cycle. If you have an emulator, that's excellent. If you can > > boot diskless, that's almost as good. Copying kernels onto floppies and > > lugging them back and forth gets old _really_ quick. > > The best debugging environment is definately a simulator (but only if it > has good hooks into gdb). Netbooting with serial-line debugging runs a > close second. > > I used the excellent SimOS simulator exclusively in the early stages of > the FreeBSD/alpha port and was able to get the thing to boot all the way > to single-user mode and run a few commands before I touched a real > machine. That really shortened the debug time for the real hardware. > > The SimOS simulator currently supports various mips and alpha cpus. > Future versions will have other cpus but the SimOS folks will be able to > give you an idea. > I've just checked with their home page but unfortunately they don't seems to have any support yet for ARM architectures. I guess netbooting with serial debugger will have to do for a start... > > > > You want to start with a skeleton of the new system-specific code, and > > flesh it out as you go. The first goal is to get enough infrastructure > > in place to build the kernel. The alpha port is probably a good place > > to look first, as it's only just starting to put on weight, and has a > > lot of new architectural stuff in it. > > I think that cloning the alpha port and hacking it is as good a way to > start as any. Make sure you have current source trees for the NetBSD and > Linux kernel too for cross reference. You have a steep learning curve > ahead - good luck! Thanks, I'm pretty sure I'll need all I can find :) Stephane E. Potvin Galea Network Security. --- La vie est trop courte pour etre prise au serieux. anonyme To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 07:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23560 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 07:56:52 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from galea.com (Odie.Galea.Com [205.237.227.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA23554 for ; Fri, 30 Oct 1998 07:56:51 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from gotlib.galea.com (Gotlib.Galea.Com [205.237.227.60]) by galea.com (8.6.11/8.6.9) with SMTP id LAA17363 for ; Fri, 30 Oct 1998 11:12:03 -0500 Received: from videotron.ca ([205.237.227.166]) by gotlib.galea.com (Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) with SMTP id 852566AD.00578BD4; Fri, 30 Oct 1998 10:56:14 -0500 Message-ID: <3639E1CC.45D25F60@videotron.ca> Date: Fri, 30 Oct 1998 10:57:00 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security Inc. X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port References: <3638BF40.304CB4F0@videotron.ca> <199810292216.PAA17442@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, thanks for the numerous and helpfull responses. As I was suggested by many I'll try to first get the build tools working on a NetBSD host under arm with egcs (seems to have better arm support from a fast skimming of the source) taking the alpha port as template/example. If that's wanted I'll keep you informed of my progression. Regards, Stephane E. Potvin Galea Network Security. --- La vie est trop courte pour etre prise au serieux. anonyme To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 08:43:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28536 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 08:43:29 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28522 for ; Fri, 30 Oct 1998 08:43:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00451; Fri, 30 Oct 1998 08:42:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301642.IAA00451@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Luigi Rizzo cc: hackers@FreeBSD.ORG Subject: Re: signal 10 to cc ? In-reply-to: Your message of "Fri, 30 Oct 1998 14:13:36 +0100." <199810301313.OAA09884@labinfo.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 08:42:29 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > on my test machine after some strange instability i am now getting > signal 10 sent to "cc" while building kernels (on a 3.0 snap): > > /kernel: pid 1269 (cc1), uid 0: exited on signal 10 (core dumped). > > should i suspect bad hardware ? I already do, because i am getting > strange hangups with previously working kernels. I'm doing a lot of builds on bleeding-edge current at the moment playing with PnP stuff, and I'm not seeing that, so I would certainly be suspicious, yes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 08:44:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28756 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 08:44:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28745 for ; Fri, 30 Oct 1998 08:44:39 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id IAA00468; Fri, 30 Oct 1998 08:44:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810301644.IAA00468@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephane E. Potvin" cc: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port In-reply-to: Your message of "Fri, 30 Oct 1998 10:57:00 EST." <3639E1CC.45D25F60@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 08:44:24 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, thanks for the numerous and helpfull responses. As I was suggested > by many I'll try to first get the build tools working on a NetBSD host > under arm with egcs (seems to have better arm support from a fast > skimming of the source) taking the alpha port as template/example. If > that's wanted I'll keep you informed of my progression. I think you'll find intense interest; certainly from those of us with embedded-systems backgrounds. There are plenty of neat SA-based devices out there that would be even more fun to play with under FreeBSD. What I want *now* is for someone to do a Palm Pilot clone using a processor with a PMMU. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 09:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01707 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 09:10:40 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01701 for ; Fri, 30 Oct 1998 09:10:37 -0800 (PST) (envelope-from urgent@aol.com) From: urgent@aol.com Received: from central.cnet.com (1Cust6.tnt13.nyc3.da.uu.net [153.37.139.6]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id JAA22181 for ; Fri, 30 Oct 1998 09:10:34 -0800 (PST) Date: Fri, 30 Oct 1998 09:10:34 -0800 (PST) To: Message-Id: <989.283923.694682 urgent@aol.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 10/30/98 Y2K Solution! 8 Pine Circle Dr., Silicon Valley, Calif. OTC Company "TCFG" 21 st. Century Frontier Group has through several members of their administrative research department leaked vital information about their companies efforts. Everyone was tight lipped and interviews were refused, and through un-named sources we have learned that the technology and software solution are in the process of being patented! In over 1640 trials, using various data systems the use of the new technology and software solved the Y2K problem 100% of the time. This small publicly traded company "TCFG" which is just 3 years old is through various sources now negotiating with the "Big Boys"! "TCFG" the letters to look for... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 10:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08000 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 10:15:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07995 for ; Fri, 30 Oct 1998 10:15:00 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA05207; Fri, 30 Oct 1998 10:14:58 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma005205; Fri Oct 30 10:14:45 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA16349; Fri, 30 Oct 1998 10:14:45 -0800 (PST) From: Archie Cobbs Message-Id: <199810301814.KAA16349@bubba.whistle.com> Subject: Re: scanf in the kernel? In-Reply-To: <199810300813.AAA01726@dingo.cdrom.com> from Mike Smith at "Oct 30, 98 00:13:48 am" To: mike@smith.net.au (Mike Smith) Date: Fri, 30 Oct 1998 10:14:45 -0800 (PST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: > Just wondering what the general feeling would be about having scanf in > the kernel? As we move towards more abstract representations of things > (eg. device names), it's becoming more important to be able to parse > strings inside the kernel. > > Doing this in hand-rolled code is tedious, error-prone and results in > code that can be hard to read and maintain (as everyone does it their > own way). > > If this isn't totally repulsive, I'll roll a somewhat smaller version > of the libc vfscanf for general approval. I think you may even get a net savings after replacing all the instances where scanf() could be used... we certainly have had to do it manually in some custom drivers here. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 10:39:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10773 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 10:39:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10766 for ; Fri, 30 Oct 1998 10:38:51 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id TAA05192; Fri, 30 Oct 1998 19:44:14 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Fri, 30 Oct 1998 19:44:13 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: New bootloader, PnP scanning In-Reply-To: <199810300414.UAA00437@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Here's how it looks in my case: 1. Intel Dakota DK440LX, 2xPII-233, Phoenix BIOS 4.0 Release 6.0, with on-board Adaptec 7895 UW controller, Fore PCA-200E 155Mbps card, DEC21040-based eth. card. PNP0c02 PNP0c02 PNP0c01 : System Memory PNP0c02 PNP0200 PNP0000 PNP0100 PNP0b00 PNP0303 PNP0c04 PNP0800 PNP0a03 PNP0c02 PNP0c02 PNP0501 PNP0501 PNP0700 PNP0401 PNP0f13 CSC0b35 : CS4236B 0x78959004 : SCSI controller 0x78959004 : SCSI controller 0x71118086 : IDE controller 0x12298086 : Ethernet controller 0x03001127 : ATM controller 0x89015333 : VGA display 0x71128086 : USB controller 2. Oldish Tyan Tomcat II, 2xP-133, Award(?) BIOS, AHA2940AU PNP0000 PNP0200 PNP0100 PNP0b00 PNP0303 PNP0800 PNP0c04 PNP0c01 PNP0a03 PNP0501 PNP0700 PNP0401 PNP0501 0x61789004 : SCSI controller 0x70108086 : IDE controller 0x00141011 : Ethernet controller 0x56315333 : VGA display Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 10:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11172 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 10:42:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11167 for ; Fri, 30 Oct 1998 10:42:56 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id NAA27273 for ; Fri, 30 Oct 1998 13:42:32 GMT Message-Id: <199810301342.NAA27273@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 30 Oct 1998 13:56:07 -0500 To: hackers@FreeBSD.ORG From: Dennis Subject: TTCP for Freebsd Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cant find this in the tree anywhere. Is there a package or port of ttcp somewhere? thanks, Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 10:50:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11982 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 10:50:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11974 for ; Fri, 30 Oct 1998 10:50:50 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA21296; Fri, 30 Oct 1998 10:45:47 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdW21290; Fri Oct 30 18:45:43 1998 Date: Fri, 30 Oct 1998 10:45:23 -0800 (PST) From: Julian Elischer To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-Reply-To: <199810300813.AAA01726@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes we have already seveal places that do this sort of thing.. e.g. matching device/manufacturer strings in teh CAM and SCSI systems. On Fri, 30 Oct 1998, Mike Smith wrote: > > Just wondering what the general feeling would be about having scanf in > the kernel? As we move towards more abstract representations of things > (eg. device names), it's becoming more important to be able to parse > strings inside the kernel. > > Doing this in hand-rolled code is tedious, error-prone and results in > code that can be hard to read and maintain (as everyone does it their > own way). > > If this isn't totally repulsive, I'll roll a somewhat smaller version > of the libc vfscanf for general approval. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 11:07:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13254 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 11:07:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smarter.than.nu (lal-99-91.Reshall.Berkeley.EDU [169.229.99.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13248 for ; Fri, 30 Oct 1998 11:07:44 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.8.8) with SMTP id LAA03515; Fri, 30 Oct 1998 11:07:08 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Fri, 30 Oct 1998 11:07:08 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: <199810301342.NAA27273@etinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Dennis wrote: > > I cant find this in the tree anywhere. Is there a package or port of ttcp > somewhere? T/TCP, last I checked, is in the tree. You need to do: sysctl -W net.inet.tcp.rfc1644=1 to enable it. -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 11:18:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14421 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 11:18:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14413 for ; Fri, 30 Oct 1998 11:18:06 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA105871139; Fri, 30 Oct 1998 10:25:39 -0500 Date: Fri, 30 Oct 1998 10:25:39 -0500 (EST) From: Bill Fumerola To: Mike Smith Cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-Reply-To: <199810300813.AAA01726@dingo.cdrom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > Just wondering what the general feeling would be about having scanf in > the kernel? As we move towards more abstract representations of things > (eg. device names), it's becoming more important to be able to parse > strings inside the kernel. I'm not a kernel-hacking kind of guy, but I know just from personal C experiences that scanf makes things a lot easier to change later on and easier to get a visual representation of. scanf and sprintf have become my friend. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 11:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15580 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 11:27:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from calvin.saturn-tech.com ([207.229.19.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15574 for ; Fri, 30 Oct 1998 11:27:16 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id MAA17417; Fri, 30 Oct 1998 12:24:34 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Fri, 30 Oct 1998 12:24:34 -0700 (MST) From: Doug Russell To: Konstantin Chuguev cc: freebsd-hackers@FreeBSD.ORG Subject: Re: make installworld over NFS In-Reply-To: <3639C28F.467FE675@urc.ac.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Konstantin Chuguev wrote: > Hi. > Then I'd prefer just to run "make DESTDIR=/net/${HOST} installworld", > assuming all other hosts export their /,/usr,/var to the build server. I do it the other way around all the time. NFS mount /usr/obj and /usr/src from the build server on the minibox to be updated, then do a make installworld on the minibox. Works great. I use it to update my bedroom machine all the time. It only has two 420 meg IDEs CCD, so there isn't really enough room to do whole make worlds on the machine itself. Besides, it takes forever on a 486/120. Much faster on one of the K6es. :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 11:39:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17319 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 11:39:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17314 for ; Fri, 30 Oct 1998 11:39:40 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id UAA30867; Fri, 30 Oct 1998 20:39:36 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA24082 (5.67b/IDA-1.5); Fri, 30 Oct 1998 20:21:39 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id TAA01062; Fri, 30 Oct 1998 19:25:11 +0100 (CET) From: Wilko Bulte Message-Id: <199810301825.TAA01062@yedi.iaf.nl> Subject: Re: Fibre channel In-Reply-To: <199810300808.TAA03591@mail.aussie.org> from Hallam Oaks at "Oct 30, 98 07:09:02 pm" To: mlnn4@oaks.com.au Date: Fri, 30 Oct 1998 19:25:11 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Hallam Oaks wrote... > Hi, > > I'm now going to demonstrate my total ignorance of fibre channel ;) > > Who here can tell me what we need to set up a working fibre channel hard > drive system, apart from the controller and drive ? I'm not referring > specifically to FC on FreeBSD per se, but the actual hardware. > > I know I'd (obviously) need some fibre optic cable, but I'm unsure if you Not so obviously as you think: FC also runs on copper wiring. For shorter max distances though. > also need an external optical transciever. That is, I'm unsure if these are > built into the FC hardware, or if the FC devices connect to the transcievers > via some sort of standard electrical - rather than optical - interface. On adapters you normally will find GLM (gigabit link modules). These can be for copper or for multi or single mode fiber. > If so, does anyone know how much these transcievers tend to cost (low power > type) ? What else is needed to have a working system ? (apart from the driver > software that is ... at the moment I'm only concerned about hardware.) FC stuff is currently still pretty expensive. Check www.emulex.com for some sample hardware. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:06:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19743 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:06:37 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freesbee.t.dk (freesbee.t.dk [193.163.159.72]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA19730 for ; Fri, 30 Oct 1998 12:06:34 -0800 (PST) (envelope-from ncbp@freesbee.t.dk) Received: (qmail 29585 invoked by uid 1002); 30 Oct 1998 20:06:31 -0000 Date: Fri, 30 Oct 1998 21:06:31 +0100 From: "Niels Chr. Bank-Pedersen" To: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? Message-ID: <19981030210631.A29433@bank-pedersen.dk> Mail-Followup-To: hackers@FreeBSD.ORG References: <199810290344.LAA02525@ariadne.tensor.pgs.com> <199810290446.UAA00420@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.15i In-Reply-To: <199810290446.UAA00420@dingo.cdrom.com>; from Mike Smith on Wed, Oct 28, 1998 at 08:46:36PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Oct 28, 1998 at 08:46:36PM -0800, Mike Smith wrote: > > make world > > followed by > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > will upgrade you completely. The visible parts of the new loader are > in /boot/loader, and are updated by 'make world'. Is the issue with a "changing" bootdevice during boot solved? I saw some reports on problems when booting from a device that wouldn't become the root-device -- resulting in "root device doesn't match mounted device" when remounting "/". I ask because I am using OS/2 bootloader (installed on wd0) to boot FreeBSD from da0, and I ran into the abovementioned problem. ( - could be because I haven't configured wd-support in my kernel (only M$-stuff there anyway :), but I'd like that to work as well.) /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, Tele Danmark DataNET, IP-section. # rsh -l God universe.all find / -name '*windows*' -exec rm -rf {} \\; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:09:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20006 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:09:59 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20001 for ; Fri, 30 Oct 1998 12:09:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01740; Fri, 30 Oct 1998 12:09:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810302009.MAA01740@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Niels Chr. Bank-Pedersen" cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Fri, 30 Oct 1998 21:06:31 +0100." <19981030210631.A29433@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 12:09:28 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Oct 28, 1998 at 08:46:36PM -0800, Mike Smith wrote: > > > > make world > > > > followed by > > > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > > > will upgrade you completely. The visible parts of the new loader are > > in /boot/loader, and are updated by 'make world'. > > Is the issue with a "changing" bootdevice during boot solved? > I saw some reports on problems when booting from a device that > wouldn't become the root-device -- resulting in "root device > doesn't match mounted device" when remounting "/". > I ask because I am using OS/2 bootloader (installed on wd0) to boot > FreeBSD from da0, and I ran into the abovementioned problem. > ( - could be because I haven't configured wd-support in my kernel (only > M$-stuff there anyway :), but I'd like that to work as well.) You might need to set $rootdev explicitly. You'd have this problem with the old loader too. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:30:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21881 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:30:41 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from samizdat.uucom.com (samizdat.uucom.com [198.202.217.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21873 for ; Fri, 30 Oct 1998 12:30:36 -0800 (PST) (envelope-from cshenton@uucom.com) Received: (from cshenton@localhost) by samizdat.uucom.com (8.9.0/8.9.0) id PAA25566; Fri, 30 Oct 1998 15:30:21 -0500 To: Doug Russell Cc: Konstantin Chuguev , freebsd-hackers@FreeBSD.ORG Subject: Re: make installworld over NFS References: From: Chris Shenton Date: 30 Oct 1998 15:30:21 -0500 In-Reply-To: Doug Russell's message of Fri, 30 Oct 1998 12:24:34 -0700 (MST) Message-ID: <86iuh194iq.fsf@samizdat.uucom.com> Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Russell writes: > I do it the other way around all the time. NFS mount /usr/obj and > /usr/src from the build server on the minibox to be updated, then do a > make installworld on the minibox. > > Works great. I use it to update my bedroom machine all the time. It only > has two 420 meg IDEs CCD, so there isn't really enough room to do whole > make worlds on the machine itself. Besides, it takes forever on a > 486/120. Much faster on one of the K6es. :) My minibox is a lowly 486sx-16 or -33 with only 5MB RAM so building the OS on it is out of the question. It's also at a lights-out ISP site so getting to it physically is difficult. Any suggestions on how to do this when the minibox is a 28.8 POTS line away? Would the NFS be reliable enough? It's currently at 2.2.1-RELEASE and I'd like to bring it up to 2.2-STABLE. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22360 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:33:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22355 for ; Fri, 30 Oct 1998 12:33:32 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id NAA05159; Fri, 30 Oct 1998 13:33:26 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA24629; Fri, 30 Oct 1998 13:33:25 -0700 Date: Fri, 30 Oct 1998 13:33:25 -0700 Message-Id: <199810302033.NAA24629@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Dennis Cc: hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: <199810301342.NAA27273@etinc.com> References: <199810301342.NAA27273@etinc.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I cant find this in the tree anywhere. Is there a package or port of ttcp > somewhere? TTCP is part of the kernel, and enabled via sysctl's. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:36:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22665 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:36:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22659 for ; Fri, 30 Oct 1998 12:36:27 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 2703 invoked by uid 1001); 30 Oct 1998 20:36:20 +0000 (GMT) To: nate@mt.sri.com Cc: dennis@etinc.com, hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: Your message of "Fri, 30 Oct 1998 13:33:25 -0700" References: <199810302033.NAA24629@mt.sri.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 30 Oct 1998 21:36:20 +0100 Message-ID: <2701.909779780@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I cant find this in the tree anywhere. Is there a package or port of ttcp > > somewhere? > > TTCP is part of the kernel, and enabled via sysctl's. He's probably talking about ttcp, not T/TCP. As in: NAME ttcp - test TCP and UDP performance SYNOPSIS ttcp -t [-lbuflen] [-s] [-nnumbufs] [-pport] [-u] [-D] [-L] [-Aalign] [-Ooffset] [-v] host [out] DESCRIPTION Ttcp times the transmission and reception of data between two systems using the UDP or TCP protocols. It differs from common "blast" tests, which tend to measure the remote inetd as much as the network performance, and which usually do not allow measurements at the remote end of a UDP transmission. It's extremely useful. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:38:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22856 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:38:09 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22851 for ; Fri, 30 Oct 1998 12:38:08 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id PAA27801; Fri, 30 Oct 1998 15:37:29 GMT Message-Id: <199810301537.PAA27801@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 30 Oct 1998 15:51:03 -0500 To: Nate Williams From: Dennis Subject: Re: TTCP for Freebsd Cc: hackers@FreeBSD.ORG In-Reply-To: <199810302033.NAA24629@mt.sri.com> References: <199810301342.NAA27273@etinc.com> <199810301342.NAA27273@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:33 PM 10/30/98 -0700, Nate Williams wrote: >> I cant find this in the tree anywhere. Is there a package or port of ttcp >> somewhere? > >TTCP is part of the kernel, and enabled via sysctl's. I was referring to ttcp.c, a tcp throughput generator. Someone has already sent it to me.....thanks. Dennis > > > >Nate > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23524 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:43:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23519 for ; Fri, 30 Oct 1998 12:43:30 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA17415; Fri, 30 Oct 1998 13:42:53 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199810302042.NAA17415@panzer.plutotech.com> Subject: Re: TTCP for Freebsd In-Reply-To: <2701.909779780@verdi.nethelp.no> from "sthaug@nethelp.no" at "Oct 30, 98 09:36:20 pm" To: sthaug@nethelp.no Date: Fri, 30 Oct 1998 13:42:53 -0700 (MST) Cc: nate@mt.sri.com, dennis@etinc.com, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote... > > > I cant find this in the tree anywhere. Is there a package or port of ttcp > > > somewhere? > > > > TTCP is part of the kernel, and enabled via sysctl's. > > He's probably talking about ttcp, not T/TCP. As in: > > NAME > ttcp - test TCP and UDP performance [ ... ] > It's extremely useful. Well then, where do you get it? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 12:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23731 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 12:48:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA23724 for ; Fri, 30 Oct 1998 12:48:05 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 2802 invoked by uid 1001); 30 Oct 1998 20:47:59 +0000 (GMT) To: ken@plutotech.com Cc: hackers@FreeBSD.ORG Subject: Re: TTCP for Freebsd In-Reply-To: Your message of "Fri, 30 Oct 1998 13:42:53 -0700 (MST)" References: <199810302042.NAA17415@panzer.plutotech.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 30 Oct 1998 21:47:59 +0100 Message-ID: <2800.909780479@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ttcp - test TCP and UDP performance > > > It's extremely useful. > > Well then, where do you get it? http://ftpsearch.ntnu.no/ is your friend. The ttcp version I use (an old one) can be picked up from ftp://ftp.ntnu.no/pub/unix/network/ttcp/ There's a newer version available from ftp://ftp.dante.org.uk/pub/software/ttcp/ Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 13:00:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24893 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 13:00:07 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gatekeeper.ray.com (gatekeeper.ray.com [138.125.162.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24856 for ; Fri, 30 Oct 1998 13:00:03 -0800 (PST) (envelope-from moncrg@bt340707.res.ray.com) Received: (mailer@localhost) by gatekeeper.ray.com (8.8.7/8.8.7) id PAA26045 for ; Fri, 30 Oct 1998 15:50:01 -0500 (EST) Received: from bt340707.res.ray.com/138.125.142.35() by gatekeeper.ray.com id sma.909780553.a07465; Fri Oct 30 15:49:13 1998 Received: from bt340707.res.ray.com (localhost [127.0.0.1]) by bt340707.res.ray.com (8.8.8/8.8.7) with ESMTP id PAA29458; Fri, 30 Oct 1998 15:48:44 -0500 (EST) (envelope-from moncrg@bt340707.res.ray.com) Message-ID: <363A262B.C912F17@bt340707.res.ray.com> Date: Fri, 30 Oct 1998 15:48:44 -0500 From: "Gregory D. Moncreaff" X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: John Polstra CC: hackers@FreeBSD.ORG Subject: Re: help with setting up private cvsup mirror References: <3638B02C.F1913CD5@bt340707.res.ray.com> <199810292321.PAA06088@austin.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doh! much better.... btw should cvsupd use SO_REUSEADDR enables local address reuse SO_REUSEPORT enables duplicate address and port bindings in case one restarted it? or does it already [I'm using 2.2.7 release ports still] John Polstra wrote: > Gregory D. Moncreaff wrote: > > Is there a "cvsup mirror in N easy steps" page I haven't found yet? > > Better than that: "ports/net/cvsup-mirror". -- Greg Moncreaff, Senior Software Engineer, CNS/ATN Raytheon Systems Company, Mailstop 2.2.2507 Raytheon 1001 Boston Post Road East, Marlboro, MA 01752 USA 508.490.2048, 508.490.2086 fax -- Disclaimer: "this is my personal opinion and not that of my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 13:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25067 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 13:01:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25061 for ; Fri, 30 Oct 1998 13:01:06 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA07289; Fri, 30 Oct 1998 13:01:03 -0800 (PST) Received: from bubba.whistle.com(207.76.205.7) by whistle.com via smap (V1.3) id sma007287; Fri Oct 30 13:00:58 1998 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA18888; Fri, 30 Oct 1998 13:00:58 -0800 (PST) From: Archie Cobbs Message-Id: <199810302100.NAA18888@bubba.whistle.com> Subject: Re: scanf in the kernel? In-Reply-To: <199810301814.KAA16349@bubba.whistle.com> from Archie Cobbs at "Oct 30, 98 10:14:45 am" To: mike@smith.net.au Date: Fri, 30 Oct 1998 13:00:58 -0800 (PST) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs writes: > > Just wondering what the general feeling would be about having scanf in > > the kernel? As we move towards more abstract representations of things > > (eg. device names), it's becoming more important to be able to parse > > strings inside the kernel. > > > > Doing this in hand-rolled code is tedious, error-prone and results in > > code that can be hard to read and maintain (as everyone does it their > > own way). > > > > If this isn't totally repulsive, I'll roll a somewhat smaller version > > of the libc vfscanf for general approval. Also- Seems like the kernel was missing memmove(), memcpy(), and/or memset() at some point. I like using these better than bcopy()/bzero() because they are more ANSI and portable... And what about snprintf()? Would that be hard to add to the existing printf() functionality? The kernel is definitely one place you don't want to overflow string buffers... -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 13:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25496 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 13:07:02 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25491 for ; Fri, 30 Oct 1998 13:07:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA02040; Fri, 30 Oct 1998 13:06:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810302106.NAA02040@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Archie Cobbs cc: mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Fri, 30 Oct 1998 13:00:58 PST." <199810302100.NAA18888@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 13:06:10 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Archie Cobbs writes: > > > Just wondering what the general feeling would be about having scanf in > > > the kernel? As we move towards more abstract representations of things > > > (eg. device names), it's becoming more important to be able to parse > > > strings inside the kernel. > > > > > > Doing this in hand-rolled code is tedious, error-prone and results in > > > code that can be hard to read and maintain (as everyone does it their > > > own way). > > > > > > If this isn't totally repulsive, I'll roll a somewhat smaller version > > > of the libc vfscanf for general approval. > > Also- > Seems like the kernel was missing memmove(), memcpy(), and/or memset() > at some point. I like using these better than bcopy()/bzero() because > they are more ANSI and portable... I think there'd be some BSD traditionalist sentiment here. But you can fake them up easily enough, so if there's a compelling need this could be done, yes. > And what about snprintf()? Would that be hard to add to the existing > printf() functionality? The kernel is definitely one place you > don't want to overflow string buffers... I don't know. Want to take a quick look and tell us? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 13:39:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28075 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 13:39:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28070 for ; Fri, 30 Oct 1998 13:39:18 -0800 (PST) (envelope-from devet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.8.8/8.8.8) with IAEhv.nl id WAA03571 for hackers@freebsd.org; Fri, 30 Oct 1998 22:39:16 +0100 (MET) (envelope-from devet@adv.iae.nl) Received: (from devet@localhost) by adv.iae.nl (8.8.8/8.8.6) id WAA13889 for hackers@freebsd.org; Fri, 30 Oct 1998 22:39:02 +0100 (CET) From: Arjan de Vet Message-Id: <199810302139.WAA13889@adv.iae.nl> Subject: Possible bug in freopen()? To: hackers@FreeBSD.ORG Date: Fri, 30 Oct 1998 22:39:02 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I may have found a bug in freopen() while testing INN 2.2-stable. Consider the following program: #include #include main () { FILE *f, *g; long i; g = fopen("/tmp/test", "a"); f = freopen("/tmp/test", "a", g); i = ftell(f); printf("%d\n", i); fprintf(f, "test"); i = ftell(f); printf("%d\n", i); close(f); } Start with an empty /tmp/test file and run the program three times consecutively. The results on BSD/OS 3.0, FreeBSD 2.2.7-stable and Solaris 2.6 are: BSDI 3.0 FreeBSD 2.2.7 Solaris ----------------------------------------------------------------------------- 0 0 0 4 4 4 0 0 4 8 4 8 0 0 8 12 4 12 Hmm... Quite different. I think Solaris shows the correct behaviour. In each case /tmp/test contains "testtesttest" after the running the program three times. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 14:16:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02192 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 14:16:35 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com ([207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02185 for ; Fri, 30 Oct 1998 14:16:33 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id OAA13544 for ; Fri, 30 Oct 1998 14:16:30 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id OAA01317 for hackers@freebsd.org; Fri, 30 Oct 1998 14:16:24 -0800 (PST) Message-ID: <19981030141624.A1244@thought.org> Date: Fri, 30 Oct 1998 14:16:24 -0800 From: Gary Kline To: Hackers Mailing List Subject: Memory leak location tool? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm double-checking because the word that I've heard thus far is `No, not really.' But I thought I'd check this worldwide list to confirm:: Are there any free tools to detect likely memory leaks? Tools like Purify aren't quite what I'm looking for. Anybody? gary -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 14:37:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04001 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 14:37:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03995 for ; Fri, 30 Oct 1998 14:36:58 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from lal.cs.utah.edu (lal.cs.utah.edu [155.99.192.110]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id PAA29138; Fri, 30 Oct 1998 15:36:53 -0700 (MST) From: David G Andersen Received: (from danderse@localhost) by lal.cs.utah.edu (8.8.8/8.8.8) id PAA01262; Fri, 30 Oct 1998 15:37:02 -0700 (MST) Message-Id: <199810302237.PAA01262@lal.cs.utah.edu> Subject: nfs/amd hangs / getattr request flood problem To: hackers@FreeBSD.ORG Date: Fri, 30 Oct 1998 15:37:02 -0700 (MST) Cc: sclawson@cs.utah.edu, danderse@cs.utah.edu, mike@fast.cs.utah.edu X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We're in the process of configuring some new machines (for personal and distributed build farm use), and we're seeing some atrocities with amd. The machines are running 3.0-RELEASE (plus the last few days of checked in fixes). They receive AMD maps via NIS and a static map, but disabling NIS doesn't affect things. We've made significant tweaks to the rest of the system configuration (disabling nis, mfs, slowing things down, etc) and tried it on multiple systems, and the problem keeps popping up. This behavior isn't exhibited in 2.2.x. We have AMD looking at /n/{machine}/path, with the actual mounts on /a/{machine}. When compiling with a source tree on /n/machine/path and an object tree on local /z, AMD can use up to 50% of the processor. Ktrace and tcpdump output shows that it's handling around 150 getattr requests per second, on "/n" and "/n/machine", and the ktrace indicates that that's the _only_ thing it's doing. The result of this is some serious slowdowns, and reproducible system freezes (kernel alive and pingable, no userland activity whatsoever). Unfortunately, we don't have a simple way of reproducing the hangs yet - it happens while running the Linux suse Matrox Xserver and the FreeBSD netscape (entering, then leaving, and then re-entering Netscape frequently triggers the hang). There don't seem to be any references to this in gnats or on the lists. We're working on forward-porting the 2.2.x amd to 3.0 to see if the behavior still exists, but in the meantime, if anyone has suggestions / thoughts / knows what's wrong and wants to clue me in, it'd be greatly appreciated. :) -Dave -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah http://www.angio.net/ Department of Computer Science To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 15:16:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07955 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 15:16:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07948 for ; Fri, 30 Oct 1998 15:16:51 -0800 (PST) (envelope-from danderse@cs.utah.edu) Received: from lal.cs.utah.edu (lal.cs.utah.edu [155.99.192.110]) by wrath.cs.utah.edu (8.8.8/8.8.8) with ESMTP id QAA00678; Fri, 30 Oct 1998 16:16:45 -0700 (MST) From: David G Andersen Received: (from danderse@localhost) by lal.cs.utah.edu (8.8.8/8.8.8) id QAA02491; Fri, 30 Oct 1998 16:16:56 -0700 (MST) Message-Id: <199810302316.QAA02491@lal.cs.utah.edu> Subject: Re: FreeBSD arm port To: mike@smith.net.au (Mike Smith) Date: Fri, 30 Oct 1998 16:16:55 -0700 (MST) Cc: sepotvin@videotron.ca, Hackers@FreeBSD.ORG In-Reply-To: <199810301644.IAA00468@dingo.cdrom.com> from "Mike Smith" at Oct 30, 98 08:44:24 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As an aside about this, we (the Flux research group at the University of Utah) have a few DEC DNARDs that we're doing some development work on, and a couple of them spend a fair amount of time idle right now - so we'd be willing to open them up to a _few_ people who are serious about an ARM port and want another platform (the DNARDs are StrongARM based NCs. They netboot like a charm) on which to work. If there's interest, let me know and we can work out the access details. they're on power boxes, have serial consoles you can tip to, etc. The "few" part is that we're still bringing our research DNARD cluster online, so space is a bit limited. :) -Dave Lo and behold, Mike Smith once said: > > > Well, thanks for the numerous and helpfull responses. As I was suggested > > by many I'll try to first get the build tools working on a NetBSD host > > under arm with egcs (seems to have better arm support from a fast > > skimming of the source) taking the alpha port as template/example. If > > that's wanted I'll keep you informed of my progression. > > I think you'll find intense interest; certainly from those of us with > embedded-systems backgrounds. There are plenty of neat SA-based devices > out there that would be even more fun to play with under FreeBSD. > > What I want *now* is for someone to do a Palm Pilot clone using a > processor with a PMMU. 8) > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- work: danderse@cs.utah.edu me: angio@pobox.com University of Utah http://www.angio.net/ Department of Computer Science To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 15:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08676 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 15:25:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from m4.c2.telstra-mm.net.au (m4.c2.telstra-mm.net.au [24.192.3.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08671 for ; Fri, 30 Oct 1998 15:25:11 -0800 (PST) (envelope-from andrew@lake.com.au) Received: from m5.c2.telstra-mm.net.au (m5.c2.telstra-mm.net.au [24.192.3.20]) by m4.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA27542 for ; Sat, 31 Oct 1998 10:25:06 +1100 (EDT) Received: from nsw.bigpond.net.au (UNKNOWN049067.rev.telstra-mm.net.au [24.192.49.67]) by m5.c2.telstra-mm.net.au (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id KAA28444 for ; Sat, 31 Oct 1998 10:25:05 +1100 (EDT) Received: (qmail 1281 invoked by uid 1000); 30 Oct 1998 23:23:40 -0000 From: "Andrew Reilly" Message-ID: <19981031102340.A1127@reilly.home> Date: Sat, 31 Oct 1998 10:23:40 +1100 To: Mike Smith , "Stephane E. Potvin" Cc: Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port References: <3639E1CC.45D25F60@videotron.ca> <199810301644.IAA00468@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810301644.IAA00468@dingo.cdrom.com>; from Mike Smith on Fri, Oct 30, 1998 at 08:44:24AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 30, 1998 at 08:44:24AM -0800, Mike Smith wrote: > What I want *now* is for someone to do a Palm Pilot clone using a > processor with a PMMU. 8) What about the DEC itsy? Not a product yet, but I believe you can get closer to one if you register enough interest. On the subject of ARMs, does anyone know whether the ARM-1500 (that of the relatively huge single precision FLOPS) has made it into any kind of product yet? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 15:31:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09144 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 15:31:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09139 for ; Fri, 30 Oct 1998 15:31:25 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id SAA28485; Fri, 30 Oct 1998 18:30:52 GMT Message-Id: <199810301830.SAA28485@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 30 Oct 1998 18:44:25 -0500 To: Archie Cobbs From: Dennis Subject: Re: scanf in the kernel? Cc: hackers@FreeBSD.ORG In-Reply-To: <199810302100.NAA18888@bubba.whistle.com> References: <199810301814.KAA16349@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:00 PM 10/30/98 -0800, you wrote: >Archie Cobbs writes: >> > Just wondering what the general feeling would be about having scanf in >> > the kernel? As we move towards more abstract representations of things >> > (eg. device names), it's becoming more important to be able to parse >> > strings inside the kernel. >> > >> > Doing this in hand-rolled code is tedious, error-prone and results in >> > code that can be hard to read and maintain (as everyone does it their >> > own way). >> > >> > If this isn't totally repulsive, I'll roll a somewhat smaller version >> > of the libc vfscanf for general approval. > >Also- >Seems like the kernel was missing memmove(), memcpy(), and/or memset() >at some point. I like using these better than bcopy()/bzero() because >they are more ANSI and portable... #define memcpy(d,s,n) bcopy(s,d,n) not exactly rocket science :-) sscanf..you lazy bastard....although I am pleased as punch that printf now supports leading zeros...when did that happen? db Emerging Technologies, Inc. http://www.etinc.com ISA and PCI T1/V35/HSSI Cards for FreeBSD, LINUX and BSD/OS Bandwidth Manager http://www.etinc.com/bwmgr.htm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 16:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12491 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 16:17:44 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ratthing.reef.com (ratthing.REEF.COM [207.212.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12483 for ; Fri, 30 Oct 1998 16:17:42 -0800 (PST) (envelope-from james@reef.com) Received: from reef.com (ratthing.REEF.COM [207.212.49.2]) by ratthing.reef.com (8.9.1/8.9.1) with ESMTP id QAA00526 for ; Fri, 30 Oct 1998 16:17:39 -0800 (PST) Message-ID: <363A5719.AFB449CF@reef.com> Date: Fri, 30 Oct 1998 18:17:29 -0600 From: James Buszard-Welcher Organization: Silicon Reef, Inc. X-Mailer: Mozilla 4.06 [en] (Win95; U) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: fvwm2 package (3.0) is 'kerberized' Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The fvwm2 package under 3.0-current is kerberized. I thought there was something wrong with XFree86 install... reinstalled it twice... -- James Buszard-Welcher | VOX 847.729.8600 | SF 415.241.2800 Silicon Reef, Inc. | FAX 847.729.1560 | PGR 800.418.0016 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 16:18:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12584 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 16:18:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12553 for ; Fri, 30 Oct 1998 16:18:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA02916; Fri, 30 Oct 1998 16:16:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810310016.QAA02916@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrew Reilly" cc: Mike Smith , "Stephane E. Potvin" , Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port In-reply-to: Your message of "Sat, 31 Oct 1998 10:23:40 +1100." <19981031102340.A1127@reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 16:16:25 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Oct 30, 1998 at 08:44:24AM -0800, Mike Smith wrote: > > What I want *now* is for someone to do a Palm Pilot clone using a > > processor with a PMMU. 8) > > What about the DEC itsy? Not a product yet, but I believe you > can get closer to one if you register enough interest. That was more or less what I was referring to. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 16:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12890 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 16:19:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA12885 for ; Fri, 30 Oct 1998 16:19:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA02943; Fri, 30 Oct 1998 16:18:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810310018.QAA02943@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David G Andersen cc: hackers@FreeBSD.ORG, sclawson@cs.utah.edu, mike@fast.cs.utah.edu Subject: Re: nfs/amd hangs / getattr request flood problem In-reply-to: Your message of "Fri, 30 Oct 1998 15:37:02 MST." <199810302237.PAA01262@lal.cs.utah.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 16:18:57 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We're in the process of configuring some new machines (for personal and > distributed build farm use), and we're seeing some atrocities with amd. > The machines are running 3.0-RELEASE (plus the last few days of checked in > fixes). They receive AMD maps via NIS and a static map, but disabling NIS > doesn't affect things. We've made significant tweaks to the rest of the > system configuration (disabling nis, mfs, slowing things down, etc) and > tried it on multiple systems, and the problem keeps popping up. This > behavior isn't exhibited in 2.2.x. > > We have AMD looking at /n/{machine}/path, with the actual mounts on > /a/{machine}. When compiling with a source tree on /n/machine/path and an > object tree on local /z, AMD can use up to 50% of the processor. Ktrace > and tcpdump output shows that it's handling around 150 getattr requests > per second, on "/n" and "/n/machine", and the ktrace indicates that that's > the _only_ thing it's doing. This may be related to a known defect in the BSD NFS code; we don't cache getattr requests nor do we cache access requests. > There don't seem to be any references to this in gnats or on the lists. > We're working on forward-porting the 2.2.x amd to 3.0 to see if the > behavior still exists, but in the meantime, if anyone has suggestions / > thoughts / knows what's wrong and wants to clue me in, it'd be greatly > appreciated. :) 2.2 has the same problems, although it's amd may not suffer the consequences. You can save yourself a lot of effort by resurrecting the 3.0 AMD from the attic (check out the relevant directories a few days before the new AM-utils stuff went in). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 17:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21809 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 17:35:03 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21793 for ; Fri, 30 Oct 1998 17:34:56 -0800 (PST) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-130.camalott.com [208.229.74.130]) by mail.camalott.com (8.8.7/8.8.7) with ESMTP id TAA09598; Fri, 30 Oct 1998 19:35:44 -0600 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id TAA10574; Fri, 30 Oct 1998 19:34:34 -0600 (CST) (envelope-from joelh) To: Gary Kline Cc: Hackers Mailing List Subject: Re: Memory leak location tool? References: <19981030141624.A1244@thought.org> From: Joel Ray Holveck Date: 30 Oct 1998 19:34:29 -0600 In-Reply-To: Gary Kline's message of "Fri, 30 Oct 1998 14:16:24 -0800" Message-ID: <86u30lms4a.fsf@detlev.UUCP> Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Are there any free tools to detect likely memory leaks? Tools > like Purify aren't quite what I'm looking for. > Anybody? "more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the following: * The Boehm-Weiser garbage collecting malloc (boehm-gc) includes a leak detector. * Doug Lea's malloc (libdlmalloc) and libmalloc include hooks to add leak detection. * S-Lang (libslang) says that it includes "a malloc debugging package". I'm not sure whether they mean something to help debug malloc, or a malloc that helps you debug your code. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 18:02:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23887 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 18:02:46 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23879 for ; Fri, 30 Oct 1998 18:02:42 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA01129; Sat, 31 Oct 1998 12:32:37 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA28332; Sat, 31 Oct 1998 12:32:35 +1030 (CST) Message-ID: <19981031123234.A5846@freebie.lemis.com> Date: Sat, 31 Oct 1998 12:32:34 +1030 From: Greg Lehey To: Archie Cobbs , mike@smith.net.au Cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? References: <199810301814.KAA16349@bubba.whistle.com> <199810302100.NAA18888@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199810302100.NAA18888@bubba.whistle.com>; from Archie Cobbs on Fri, Oct 30, 1998 at 01:00:58PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 October 1998 at 13:00:58 -0800, Archie Cobbs wrote: > Archie Cobbs writes: >>> Just wondering what the general feeling would be about having scanf in >>> the kernel? As we move towards more abstract representations of things >>> (eg. device names), it's becoming more important to be able to parse >>> strings inside the kernel. >>> >>> Doing this in hand-rolled code is tedious, error-prone and results in >>> code that can be hard to read and maintain (as everyone does it their >>> own way). >>> >>> If this isn't totally repulsive, I'll roll a somewhat smaller version >>> of the libc vfscanf for general approval. > > Also- > Seems like the kernel was missing memmove(), memcpy(), and/or memset() > at some point. I like using these better than bcopy()/bzero() because > they are more ANSI and portable... I don't see that that's an issue within the kernel. > And what about snprintf()? Would that be hard to add to the existing > printf() functionality? The kernel is definitely one place you > don't want to overflow string buffers... One thing I *could* do with (and will do if people agree) is a %qd modifier for kernel *printf. I need that for vinum, and I currently have a horrible kludge to do it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 18:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25486 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 18:17:58 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25479 for ; Fri, 30 Oct 1998 18:17:54 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id VAA00487; Fri, 30 Oct 1998 21:16:24 -0500 (EST) Date: Fri, 30 Oct 1998 21:16:23 -0500 (EST) From: Chuck Robey To: Peter Wemm cc: Mike Smith , Stephen Hocking-Senior Programmer PGS Tensor Perth , hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810290638.OAA04511@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Oct 1998, Peter Wemm wrote: > > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > > > > > will upgrade you completely. The visible parts of the new loader are > > > in /boot/loader, and are updated by 'make world'. > > I'll also mention that this is jumping in at the deep end. You can > shortcut and do this: echo "/boot/loader" > /boot.config > as an intermediate step and test that. This will cause the existing > bootblocks to load the 3rd stage boot loader by default instead of > /kernel - but you are not yet committed. You still have the old boot: > prompt and can load /kernel.aout explicitly. The command that Mike has > given puts the new boot *blocks* on the disk which are not strictly > necessary to use the /boot/loader boot loader. > > You can actually test the new bootloader out by explicitly typing in > /boot/loader at the existing boot: prompt. Thanks for the excellent summary; I started testing tonight, and things aren't going exactly how I'd guessed ... and I've got at least one new question ... First, the question regarding the move from lkms to kernel modules. I see I now have a /modules directory, but it's empty. I know my /lkm directory is (was, I mean ... ) being updated by the installworld, so that I always had up to date lkms. I always kept lkms and kernel in sync, because I understood that. With the new modules, well, they're *.ko's, right? Where are they? /sys/modules/* ? That looks right, but do I then have to specifically go copy them all into /modules, so that they're available to the elf kernel? And will the elf kernel automatically install those it needs, like the cd9660 fs? 2nd: I tried your suggested procedure, typing /boot/loader, at the boot prompt. Tried it first with an aout kernel, then with an elf kernel. Same thing happens either time, it hangs immediately after printing symbols=[0x0,040,0x0 That's precisely where it stops (hangs). Am I doing something wrong? Last item, which man page (if any) is up-to-date regarding the allowable syntax in boot.config? Thanks a million bucks for giving me a procedure I could test with, because if I'd used that "echo '/boot/loader' >/boot.config" thing, and it'd hung then, I'd be kinda out of touch, I think. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 18:30:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27423 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 18:30:42 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27409 for ; Fri, 30 Oct 1998 18:30:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA03696; Fri, 30 Oct 1998 18:29:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810310229.SAA03696@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Fri, 30 Oct 1998 21:16:23 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 18:29:48 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First, the question regarding the move from lkms to kernel modules. I > see I now have a /modules directory, but it's empty. I know my /lkm > directory is (was, I mean ... ) being updated by the installworld, so > that I always had up to date lkms. I always kept lkms and kernel in > sync, because I understood that. > > With the new modules, well, they're *.ko's, right? Where are they? > /sys/modules/* ? That looks right, but do I then have to specifically > go copy them all into /modules, so that they're available to the elf > kernel? And will the elf kernel automatically install those it needs, > like the cd9660 fs? This is because /sys/modules isn't (yet) in the buildworld path. Go to /sys/modules and try 'make all install'. > 2nd: I tried your suggested procedure, typing /boot/loader, at the boot > prompt. Tried it first with an aout kernel, then with an elf kernel. > Same thing happens either time, it hangs immediately after printing > > symbols=[0x0,040,0x0 > > > That's precisely where it stops (hangs). Am I doing something wrong? The /boot/loader file you have is almost certainly corrupt. It doesn't matter what sort of kernel you have at this point; it's an a.out format ELF executable (don't ask 8). dingo:~>size -aout /boot/loader text data bss dec hex 4096 73728 0 77824 13000 Yours should look something like that. > Last item, which man page (if any) is up-to-date regarding the allowable > syntax in boot.config? /boot.config is still as per boot.8 > Thanks a million bucks for giving me a procedure I could test with, > because if I'd used that "echo '/boot/loader' >/boot.config" thing, and > it'd hung then, I'd be kinda out of touch, I think. No; that just sets the default and you can override it at boot time. You can also always still boot the loader off a floppy. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 18:39:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28473 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 18:39:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28460 for ; Fri, 30 Oct 1998 18:39:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA03769; Fri, 30 Oct 1998 18:39:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810310239.SAA03769@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Chuck Robey cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-reply-to: Your message of "Fri, 30 Oct 1998 18:29:48 PST." <199810310229.SAA03696@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 18:39:03 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 2nd: I tried your suggested procedure, typing /boot/loader, at the boot > > prompt. Tried it first with an aout kernel, then with an elf kernel. > > Same thing happens either time, it hangs immediately after printing > > > > symbols=[0x0,040,0x0 > > > > That's precisely where it stops (hangs). Am I doing something wrong? Whoops, hang on a sec. Does it print the text/data stuff first? Are you *sure* it printed 0x0,040,0x0? It should have printed 0x0,0x4,0x0. If I remember correctly, we saw this with very out-of-date bootblocks. You can update to the most recent "old" bootblocks with simply "disklabel -B '. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 19:06:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01981 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 19:06:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01975 for ; Fri, 30 Oct 1998 19:06:47 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id WAA01673; Fri, 30 Oct 1998 22:05:27 -0500 (EST) Date: Fri, 30 Oct 1998 22:05:26 -0500 (EST) From: Chuck Robey To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: The new bootloader - how do you set it up? In-Reply-To: <199810310239.SAA03769@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Mike Smith wrote: > > > 2nd: I tried your suggested procedure, typing /boot/loader, at the boot > > > prompt. Tried it first with an aout kernel, then with an elf kernel. > > > Same thing happens either time, it hangs immediately after printing > > > > > > symbols=[0x0,040,0x0 > > > > > > That's precisely where it stops (hangs). Am I doing something wrong? > > Whoops, hang on a sec. Does it print the text/data stuff first? > > Are you *sure* it printed 0x0,040,0x0? It should have printed > 0x0,0x4,0x0. I'm sorry, I fatfingered it, it really printed symbols=[0x0,0x4,0x0 and that was after the text/data stuff. It died precisely there, tho, not one extra comma, even. I could go back and handcopy all the data if it's of use ... is it? OK, I went and did the size on /boot/loader, it gave me: ROOT:/boot:129 >env OBJFORMAT=aout size loader text data bss dec hex 4096 73728 0 77824 13000 This seems to indicate to me that my installed /boot/loader is ok, but I'm willing to rebuild/reinstall it. Does it have to be an aout executeable (how shall I set OBJFORMAT for the make clean depend all install in /sys/boot?) Or is there something else I should try, to get a good test of the /boot/loader? Could it be the fact that my /modules are completely empty? > > If I remember correctly, we saw this with very out-of-date bootblocks. > You can update to the most recent "old" bootblocks with simply > "disklabel -B '. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 21:13:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12534 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 21:13:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12529 for ; Fri, 30 Oct 1998 21:13:31 -0800 (PST) (envelope-from satishb@hotmail.com) Received: from hotmail.com (f144.hotmail.com [207.82.251.23]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id VAA19188 for ; Fri, 30 Oct 1998 21:13:32 -0800 (PST) Received: (qmail 24810 invoked by uid 65534); 31 Oct 1998 05:12:58 -0000 Message-ID: <19981031051258.24809.qmail@hotmail.com> Received: from 206.165.50.234 by www.hotmail.com with HTTP; Fri, 30 Oct 1998 21:12:58 PST X-Originating-IP: [206.165.50.234] From: "Satish Basvapatri" To: freebsd-hackers@freefall.cdrom.com Subject: Hi Content-Type: text/plain Date: Sat, 31 Oct 1998 05:12:58 GMT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have one problem with sockets. I have one server and many clients. Server listens at a particular port. The clients themselves acts as servers for other clients and the opeen the connection and never closes them. If the server crashes without closing the socket when I am trying to restart the server I am getting error message "port in user". Can you suggest is there any way to clear up this port? Thanks Satish Basvapatri ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 21:22:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13548 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 21:22:06 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13543 for ; Fri, 30 Oct 1998 21:22:05 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id VAA19433 for ; Fri, 30 Oct 1998 21:22:06 -0800 (PST) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id AAA09430; Sat, 31 Oct 1998 00:24:35 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Sat, 31 Oct 1998 00:24:35 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Satish Basvapatri cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Hi In-Reply-To: <19981031051258.24809.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG a) don't write buggy code :) b) setup a signal handler,(i assume for SIGSEGV) keep track of all sockets and close them in the handler c) the client+servers could then catch the SIGPIPE on writes to themain server as an indication to try to reconnect in "X" amount of time, if the slave servers are performing reads, you should set them up to timeout after some time if no data comes across and take it as a signal to reconnect. i think "a" is the best option though... :) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Sat, 31 Oct 1998, Satish Basvapatri wrote: > Hi, > > I have one problem with sockets. > > I have one server and many clients. Server listens at a particular port. > The clients themselves acts as servers for other clients and the opeen > the connection and never closes them. If the server crashes without > closing the socket when I am trying to restart the server I am getting > error message "port in user". Can you suggest is there any way to clear > up this port? > > Thanks > Satish Basvapatri > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 22:30:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18382 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 22:30:27 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA18375 for ; Fri, 30 Oct 1998 22:30:23 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by freefall.freebsd.org (8.8.8/8.8.5) with ESMTP id WAA21221 for ; Fri, 30 Oct 1998 22:30:23 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id AAA23790; Sat, 31 Oct 1998 00:29:49 -0600 (CST) Date: Sat, 31 Oct 1998 00:29:48 -0600 From: Dan Nelson To: Alfred Perlstein , Satish Basvapatri Cc: freebsd-hackers@freefall.cdrom.com Subject: Re: Hi Message-ID: <19981031002948.A23594@emsphone.com> References: <19981031051258.24809.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: ; from "Alfred Perlstein" on Sat Oct 31 00:24:35 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Oct 31), Alfred Perlstein said: > On Sat, 31 Oct 1998, Satish Basvapatri wrote: > > I have one server and many clients. Server listens at a particular > > port. The clients themselves acts as servers for other clients and > > the opeen the connection and never closes them. If the server > > crashes without closing the socket when I am trying to restart the > > server I am getting error message "port in user". Can you suggest > > is there any way to clear up this port? > > a) don't write buggy code :) > b) setup a signal handler,(i assume for SIGSEGV) keep track of all > sockets and close them in the handler > c) the client+servers could then catch the SIGPIPE on writes to > themain server as an indication to try to reconnect in "X" amount of > time, if the slave servers are performing reads, you should set them > up to timeout after some time if no data comes across and take it as > a signal to reconnect. And the correct answer is of course d) enable the socket option SO_REUSEADDR. See the Sockets FAQ at http://kipper.york.ac.uk/~vic/sock-faq, sections 4.1 and 4.5. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 23:47:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25265 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 23:47:15 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25251 for ; Fri, 30 Oct 1998 23:47:10 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Spinner) with ESMTP id PAA18872; Sat, 31 Oct 1998 15:46:40 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199810310746.PAA18872@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: sync writes with softupdates enabled In-reply-to: Your message of "Thu, 29 Oct 1998 21:29:10 PST." <199810300529.VAA00927@dingo.cdrom.com> Date: Sat, 31 Oct 1998 15:46:39 +0800 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I've just installed 3.0-RELEASE on the machine destined to be our new > > news server. Whilst testing it with soft updates enabled, I'm seeing > > a lot of sync writes onto /usr: > > > > /dev/wd0s1f on /usr (local, soft-updates, writes: sync 32910 async 4955) > > > > With /usr mounted asynchronously rather than soft updates enabled, > > I also saw lots of synchronous writes. > > > > The writes are definitely a result of innd - nothing else much is > > running and pausing innd makes the I/O stop. I've looked at a > > ktrace of innd and can't see anything that would obviously cause it > > to do sync writes (no fsync() or open(O_SYNC) calls). > > > > It's inn-1.7.2 as per the ports with the exception that MMAP is > > enabled for dbz. > > > > All I can think of is that the MMAP'd history file is causing the > > kernel to unnecessarily perform sync writes to try and keep the > > MMAP and VFS images in sync. > > That's almost certainly correct. Try running without mmap. It used to > be faster that way; maybe it is again? Hmm, from vm_object.c: void vm_object_page_clean(object, start, end, flags) pagerflags = (flags & (OBJPC_SYNC | OBJPC_INVAL)) ? VM_PAGER_PUT_SYNC : 0; pagerflags |= (flags & OBJPC_INVAL) ? VM_PAGER_PUT_INVAL : 0; VOP_FSYNC(vp, NULL, (pagerflags & VM_PAGER_PUT_SYNC)?MNT_WAIT:0, curproc); vm_object.h: #define OBJPC_SYNC 0x1 /* sync I/O */ #define OBJPC_INVAL 0x2 /* invalidate */ Yet, we have: vfs_subr.c: vm_object_page_clean(vp->v_object, 0, 0, TRUE); vfs_syscalls.c: vm_object_page_clean(vp->v_object, 0, 0, FALSE); param.h:#define TRUE 1 param.h:#define FALSE 0 The sync_fsync() writes are calling vfs_msync() with MNT_NOWAIT, but vfs_msync() is turning dirty mmap pages into sync writes. This behavior is needed prior to unmount (obviously) but doesn't seem useful for the periodic sync. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 30 23:51:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25851 for freebsd-hackers-outgoing; Fri, 30 Oct 1998 23:51:50 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25844 for ; Fri, 30 Oct 1998 23:51:47 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.9.1/8.8.8) id CAA04396; Sat, 31 Oct 1998 02:51:13 -0500 (EST) (envelope-from toor) Message-Id: <199810310751.CAA04396@dyson.iquest.net> Subject: Re: Oracle8 Release 8.0.5 for LINUX 2.0.34 In-Reply-To: from Open Systems Networking at "Oct 28, 98 04:39:05 am" To: opsys@mail.webspan.net (Open Systems Networking) Date: Sat, 31 Oct 1998 02:51:13 -0500 (EST) Cc: fbsd@typhoon.co.jp, tlambert@primenet.com, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@iquest.net X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Open Systems Networking said: > On Wed, 28 Oct 1998, FreeBSD4Me wrote: > > > Any suggestions on how to ask? I've asked via > > > > http://www.oracle.com/siteadmin/html/contactus.html > > > > whether they have plans to release ANY of their products for FreeBSD. This was > > a few days ago and I have yet to hear from them. > > > Same here, a couple of times, it just goes to a black hole. > I wrote john once to see if he had a name of a better person to email than > some generic contact for oracle as a whole. But no reply so who knows. > I suspect that there will be little to be gained by persuing the issue internally. Oracle is quite aware of FreeBSD, and some of the developers use it regularly. It is an issue of market, and rattling the normal distribution and sales channels is the best approach at this point. It is *amazing* how well respected the free OSes are inside of big companies. It is also interesting to note the high opinion that I hear about (Free,Net)BSD, even with the edge towards FreeBSD much of the time (even though we tend towards NetBSD.) With my involvement in FreeBSD at/near zero, I get more unbiased input from others, still it appears that FreeBSD is well respected. The deal is that the market share and the expected willingness to pay by that market share is probably not high enough. Also, there are issues of credibility in the marketplace. Note that historically in the computer industry, technical excellence is not an indicator of market volume and sucess. It seems that there is some kind of inverse relationship at times in certain circumstances. FreeBSD has inadequate hype, but too much hype "might?" backfire. Since FreeBSD isn't hyped enough (given it's capabilities, reliability and performance), it is far below the level that would cause such backfire. Even with all of FreeBSD's flaws, it isn't that bad (and is in fact very good) for now. The future has to be addressed, and part of the future is associated with marketeering. My guess is that it is desired to keep FreeBSD small enough so that a single entity can keep control of it. It would be a very good idea (if the powers that be at WC) would make a vast marketing and sales pitch of FreeBSD. If WC doesn't want to do it, then someone who is interested in an investment and wants to start a support / distribution / integration business should take it on. FreeBSD seems to be continually running in "slightly starved" mode to keep it frustratingly small. When I need a U**X box, and I don't want to do kernel development on the box, I wouldn't mind spending $200-$400 for a really good and supported OS (maybe with extra commercial packages.) When I was working on FreeBSD, I didn't mind the administrative overhead. Now, I don't even want to think about admin issues, but just want to get work done. (I am not meaning to compare FreeBSD to other OSes, but mean to imply what might be useful to improve FreeBSD for non FreeBSD centric developers.) Sure, FreeBSD is a server OS, but is also a superior desktop, missing only desktop applications. A nice desktop (in the sense of a nice userland development machine config -- not in the sense of "X" desktop) will lower the threshold for developers. I had kept hearing of a FreeBSD-gold, and it is still non-existant... Where is it? Developers do like to have wordprocessing on their machines, and yes, they can buy it today. However, buying it as a pre assembled and installed package makes it much nicer. (If it isn't pre-installed, at least make the default installation perform the OS, Xwindows and commercial application installs automatically.) The project needs to be energized, and IMO, it is important to realize that other projects are not standing still, and are moving fairly quickly. Note that I don't think that other projects are moving as quickly as they are being hyped that they are, but they are moving well. I seem to remember "bogoMips???", it seems that they also have another measure "bogoSeats" :-). The hype might backfire, but I don't think so, simply because they have hit critical mass. This (in a way) tells me that the notion of "backfire" could be imaginary. My guess is that Linux has a couple of years to prove itself as a commercial OS before vendors will loose interest. This means that users will really have to fork over big bucks for the high priced packages. All of the talk needs to solidify into action for Linux. I really don't know if it is going to happen, but Linux's success or failure might be extrapolated to a potential future commercially available port for FreeBSD. It would be best for FreeBSD's emulation to continue to outperform the emulated OS -- this will be wonderful for FreeBSD in situations where a software package actually loads the machine. Unfortuately, such an emulation is likely not going to be supported by the big software vendors -- big DB users are going to often want the support of the vendors. FreeBSD is going to have to take action from it's side if it wants quicker growth and a higher profile. It is going to have to decide *to be* a player, but talking about being a player only begs the question of the true decison and commitment. -- John | Never try to teach a pig to sing, dyson@iquest.net | it makes one look stupid jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 01:27:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02155 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 01:27:13 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA02149 for ; Sat, 31 Oct 1998 01:27:10 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 17884 invoked by uid 1001); 31 Oct 1998 09:27:06 +0000 (GMT) To: Arjan.deVet@adv.iae.nl Cc: hackers@FreeBSD.ORG Subject: Re: Possible bug in freopen()? In-Reply-To: Your message of "Fri, 30 Oct 1998 22:39:02 +0100 (CET)" References: <199810302139.WAA13889@adv.iae.nl> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 31 Oct 1998 10:27:06 +0100 Message-ID: <17882.909826026@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I may have found a bug in freopen() while testing INN 2.2-stable. > > Consider the following program: > > #include > #include > > main () { > FILE *f, *g; > long i; > > g = fopen("/tmp/test", "a"); > f = freopen("/tmp/test", "a", g); > i = ftell(f); > printf("%d\n", i); > fprintf(f, "test"); > i = ftell(f); > printf("%d\n", i); > close(f); > } Your program needs to fclose() the FILE :-) Aside from that, I believe you definitely have a point. The FreeBSD freopen() behavior may actually be correct according to the standards. My copy of POSIX 1003.1 (First edition, 1990-12-07) says the following about ftell(): 8.2.3.10 ftell() The underlying function is lseek(). ... If the stream is opened in append mode or if the O_APPEND flag is set as a consequence of dealing with other handles on the file, the result of ftell() on that stream is unspecified. So freopen() behaving differently than fopen() may be allowed by the standards - but it certainly violates POLA, and probably also the FreeBSD manual page, which says: The freopen() function opens the file whose name is the string pointed to by path and associates the stream pointed to by stream with it. The original stream (if it exists) is closed. The mode argument is used just as in the fopen() function. Since it says "just as in the fopen() function", I would expect the effect on file position to be the same also. Here is a proposed patch - it simply consists of the relevant part of the fopen() function, inserted at the appropriate place in freopen(). Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- *** lib/libc/stdio/freopen.c.orig Tue May 30 07:41:43 1995 --- lib/libc/stdio/freopen.c Sat Oct 31 10:06:08 1998 *************** *** 151,155 **** --- 151,166 ---- fp->_write = __swrite; fp->_seek = __sseek; fp->_close = __sclose; + + /* + * When opening in append mode, even though we use O_APPEND, + * we need to seek to the end so that ftell() gets the right + * answer. If the user then alters the seek pointer, or + * the file extends, this will fail, but there is not much + * we can do about this. (We could set __SAPP and check in + * fseek and ftell.) + */ + if (oflags & O_APPEND) + (void) __sseek((void *)fp, (fpos_t)0, SEEK_END); return (fp); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 01:56:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04381 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 01:56:10 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04374 for ; Sat, 31 Oct 1998 01:56:07 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA09361; Sat, 31 Oct 1998 09:57:05 GMT Date: Sat, 31 Oct 1998 09:57:05 +0000 (GMT) From: Doug Rabson To: Peter Wemm cc: Mike Smith , "Stephane E. Potvin" , Hackers@FreeBSD.ORG Subject: Re: FreeBSD arm port In-Reply-To: <199810301314.VAA11350@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Oct 1998, Peter Wemm wrote: > Doug Rabson wrote: > [..] > > I think that cloning the alpha port and hacking it is as good a way to > > start as any. Make sure you have current source trees for the NetBSD and > > Linux kernel too for cross reference. You have a steep learning curve > > ahead - good luck! > > But when doing this, make *damn sure* that all the necessary credits are > given and copyrights respected. Some people are really touchy about that > and have been known to flame if the lines are crossed. I thought of mentioning that, since I was the last one to make a mistake in that area. I am trying to forget about the incident... -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 05:16:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22980 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 05:16:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22975 for ; Sat, 31 Oct 1998 05:16:17 -0800 (PST) (envelope-from devet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.8.8/8.8.8) with IAEhv.nl id OAA23955; Sat, 31 Oct 1998 14:16:12 +0100 (MET) (envelope-from devet@adv.iae.nl) Received: (from devet@localhost) by adv.iae.nl (8.8.8/8.8.6) id OAA16022; Sat, 31 Oct 1998 14:15:57 +0100 (CET) From: Arjan de Vet Message-Id: <199810311315.OAA16022@adv.iae.nl> Subject: Re: Possible bug in freopen()? In-Reply-To: <17882.909826026@verdi.nethelp.no> from "sthaug@nethelp.no" at "Oct 31, 98 10:27:06 am" To: sthaug@nethelp.no Date: Sat, 31 Oct 1998 14:15:57 +0100 (CET) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no: >Your program needs to fclose() the FILE :-) Aside from that, I believe Oops :-). >you definitely have a point. > >The FreeBSD freopen() behavior may actually be correct according to the >standards. My copy of POSIX 1003.1 (First edition, 1990-12-07) says the >following about ftell(): [...] >So freopen() behaving differently than fopen() may be allowed by the >standards - but it certainly violates POLA, and probably also the FreeBSD This behavior may be allowed but the FreeBSD version printed "4" for the last ftell() call after the fprintf() all three times, whereas BSD/OS and Solaris printed both 4, 8 and 12 (which is what I would expect). >Here is a proposed patch - it simply consists of the relevant part of the >fopen() function, inserted at the appropriate place in freopen(). Thanks, your patch fixes the problem. I just submitted a PR, with a pointer to this discussion. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 06:13:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA29221 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 06:13:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isi.co.jp (ns [202.214.62.35] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA29214; Sat, 31 Oct 1998 06:13:10 -0800 (PST) (envelope-from john@isi.co.jp) Received: by ns.isi.co.jp id <21889>; Sat, 31 Oct 1998 23:12:01 +0900 Date: Sat, 31 Oct 1998 23:06:16 +0900 From: john cooper To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Request help with packet forwarding problem [2.2.7].. Cc: john@isi.co.jp, tfujii@isi.co.jp Message-Id: <98Oct31.231201jst.21889@ns.isi.co.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm trying to get a system configured as a gateway. The first step [which I thought would be simple] was to simply forward packets between interfaces: ------- | | default gateway: 203.168.62.35 | A | | | ------- | 203.168.62.58 (ed1) | | 203.168.62.35 (ed0) ------- | | default gateway: ISP router | FW | net.inet.ip.forwarding: 1 | | ------- | 202.214.62.40 (vx0) | -----|-----------------------------> ISP router + DNS server | | 202.214.62.62 ------- | | default gateway: ISP router | B | static route: 202.214.62.40 for net 203.168.62.0 | | ------- Using netstat and tcpdump I discovered the following. If I ping machine B from A, I can see the ICMP packets make this journey: ICMP request: A --> FW --> B ICMP reply: B --> FW --> land of no return If I ping machine A from B, I get this: ICMP request: B --> FW --> ISP router I seems that FW will only forward packets in one direction. However in the first case it appears the ICMP reply packets are silently dropped [netstat does not report dropped packets]. In the second case, FW is actively trying to forward the packets to the default gateway. I'm at a loss to explain why this is occuring. I've enabled packet forwarding in FW's kernel. Is something else required to get packets forwarded between network interfaces on the same machine??? Incidentally, IPFW is not built into machine FW's kernel. Any suggestions would be most appreciated. Thanks, -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 06:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00415 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 06:24:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fdy2.demon.co.uk (fdy2.demon.co.uk [194.222.102.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00408 for ; Sat, 31 Oct 1998 06:24:49 -0800 (PST) (envelope-from rjs@fdy2.demon.co.uk) Received: (from rjs@localhost) by fdy2.demon.co.uk (8.8.8/8.8.8) id OAA00539; Sat, 31 Oct 1998 14:20:45 GMT (envelope-from rjs) Date: Sat, 31 Oct 1998 14:20:45 GMT Message-Id: <199810311420.OAA00539@fdy2.demon.co.uk> From: Robert Swindells To: joelh@gnu.org CC: kline@thought.org, hackers@FreeBSD.ORG In-reply-to: <86u30lms4a.fsf@detlev.UUCP> (message from Joel Ray Holveck on 30 Oct 1998 19:34:29 -0600) Subject: Re: Memory leak location tool? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Are there any free tools to detect likely memory leaks? Tools >> like Purify aren't quite what I'm looking for. >> Anybody? >"more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the >following: > >* The Boehm-Weiser garbage collecting malloc (boehm-gc) includes a leak > detector. > >* Doug Lea's malloc (libdlmalloc) and libmalloc include hooks to add > leak detection. > >* S-Lang (libslang) says that it includes "a malloc debugging > package". I'm not sure whether they mean something to help debug > malloc, or a malloc that helps you debug your code. There is also a simple one as part of X11R6.3. It is in xc/utils/memleak. I can't tell if the 386 support came as standard, or with the XFree86 patches. Robert Swindells ------------------------------------- Robert Swindells - GenRad Ltd rjs@genrad.co.uk - Work rjs@fdy2.demon.co.uk - Home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 06:46:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02324 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 06:46:16 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02308; Sat, 31 Oct 1998 06:46:10 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id DAA16686; Sun, 1 Nov 1998 03:45:40 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id DAA16290; Sun, 1 Nov 1998 03:45:37 +1300 (NZDT) Message-ID: <19981101034536.B16248@clear.co.nz> Date: Sun, 1 Nov 1998 03:45:36 +1300 From: Joe Abley To: john cooper , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Cc: tfujii@isi.co.jp Subject: Re: Request help with packet forwarding problem [2.2.7].. References: <98Oct31.231201jst.21889@ns.isi.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98Oct31.231201jst.21889@ns.isi.co.jp>; from john cooper on Sat, Oct 31, 1998 at 11:06:16PM +0900 X-Files: the Truth is Out There Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, Could you do a "netstat -rn" on A, B and FW, and post the output? Where were you running tcpdump? Were you identifying the gateway for each ICMP request or response by looking at the destination ethernet address? Joe On Sat, Oct 31, 1998 at 11:06:16PM +0900, john cooper wrote: > I'm trying to get a system configured as a gateway. The > first step [which I thought would be simple] was to simply > forward packets between interfaces: > > > ------- > | | default gateway: 203.168.62.35 > | A | > | | > ------- > | 203.168.62.58 (ed1) > | > | 203.168.62.35 (ed0) > ------- > | | default gateway: ISP router > | FW | net.inet.ip.forwarding: 1 > | | > ------- > | 202.214.62.40 (vx0) > | > -----|-----------------------------> ISP router + DNS server > | > | 202.214.62.62 > ------- > | | default gateway: ISP router > | B | static route: 202.214.62.40 for net 203.168.62.0 > | | > ------- > > Using netstat and tcpdump I discovered the following. If I ping > machine B from A, I can see the ICMP packets make this journey: > > ICMP request: A --> FW --> B > ICMP reply: B --> FW --> land of no return > > If I ping machine A from B, I get this: > > ICMP request: B --> FW --> ISP router > > I seems that FW will only forward packets in one direction. > However in the first case it appears the ICMP reply packets > are silently dropped [netstat does not report dropped packets]. > > In the second case, FW is actively trying to forward the packets > to the default gateway. > > I'm at a loss to explain why this is occuring. I've enabled > packet forwarding in FW's kernel. Is something else required > to get packets forwarded between network interfaces on the same > machine??? > > Incidentally, IPFW is not built into machine FW's kernel. > > Any suggestions would be most appreciated. > > Thanks, > > -john -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Net http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 07:05:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04444 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 07:05:08 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04438 for ; Sat, 31 Oct 1998 07:05:06 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id KAA13436 for ; Sat, 31 Oct 1998 10:07:47 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Sat, 31 Oct 1998 10:07:47 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: hackers@FreeBSD.ORG Subject: copyin/copyout routines. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG someone showed me a driver they were working on that was getting errors using copyin and copyout.. the error was when they used copyin to copy from user land into the kernel they would get a bad adress error. the location they were copying to was on the kernel stack ie. int x; y = copyin(useraddr, &x, sizeof(x)); for some reason i think that copyin only works in/out of the kernel malloc error, basically he should be copying into malloc'd areas, not the stack. is this true? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 07:48:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09799 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 07:48:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from isi.co.jp (ns [202.214.62.35] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09792; Sat, 31 Oct 1998 07:48:16 -0800 (PST) (envelope-from john@isi.co.jp) Received: by ns.isi.co.jp id <21889>; Sun, 1 Nov 1998 00:47:13 +0900 Date: Sun, 1 Nov 1998 00:41:23 +0900 From: john cooper To: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jabley@clear.co.nz, john@isi.co.jp Subject: Re: Request help with packet forwarding problem [2.2.7].. Cc: tfujii@isi.co.jp Message-Id: <98Nov1.004713jst.21889@ns.isi.co.jp> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Sat, 31 Oct 1998 23:45:36 +0900 > From: Joe Abley > To: john cooper , freebsd-hackers@FreeBSD.org, > freebsd-questions@FreeBSD.org > Cc: tfujii@isi.co.jp > Subject: Re: Request help with packet forwarding problem [2.2.7].. > > > John, > > Could you do a "netstat -rn" on A, B and FW, and post the output? Machine A: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 203.168.62.35 UGSc 0 21183 ed1 127.0.0.1 127.0.0.1 UH 0 7 lo0 203.168.62 link#1 UC 0 0 203.168.62.35 0:0:f4:4a:ad:e8 UHLW 2 312 ed1 1125 203.168.62.58 0:20:18:71:be:2d UHLW 1 26 lo0 Machine FW: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 202.214.62.33 UGSc 4 530 vx0 127.0.0.1 127.0.0.1 UH 0 2 lo0 202.214.62 link#1 UC 0 0 202.214.62.33 0:a0:de:0:13:76 UHLW 4 0 vx0 15 202.214.62.35 0:a0:24:2a:9:24 UHLW 0 34 vx0 795 202.214.62.62 link#1 UHLW 1 8266 203.168.62 link#2 UC 0 0 203.168.62.35 0:0:f4:4a:ad:e8 UHLW 0 8 lo0 203.168.62.58 0:20:18:71:be:2d UHLW 0 2 ed0 1197 Machine B: Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 202.214.62.33 UGSc 2 87918 vx0 127.0.0.1 127.0.0.1 UH 0 180 lo0 202.214.62/25 link#1 UC 0 0 202.214.62.33 link#1 UHLW 3 0 202.214.62.35 0:a0:24:2a:9:24 UHLW 2 3142 vx0 1101 202.214.62.40 0:a0:24:7d:c6:7c UHLW 2 297 vx0 1038 202.214.62.62 0:a0:24:7d:c6:43 UHLW 0 0 lo0 203.214.62 202.214.62.40 UGSc 0 596 vx0 > Where were you running tcpdump? On machine FW. > Were you identifying the gateway for > each ICMP request or response by looking at the destination ethernet > address? No, I was referring to /etc/rc.conf: defaultrouter="..." Thanks for the response, -john > > Joe > > On Sat, Oct 31, 1998 at 11:06:16PM +0900, john cooper wrote: > > I'm trying to get a system configured as a gateway. The > > first step [which I thought would be simple] was to simply > > forward packets between interfaces: > > > > > > ------- > > | | default gateway: 203.168.62.35 > > | A | > > | | > > ------- > > | 203.168.62.58 (ed1) > > | > > | 203.168.62.35 (ed0) > > ------- > > | | default gateway: ISP router > > | FW | net.inet.ip.forwarding: 1 > > | | > > ------- > > | 202.214.62.40 (vx0) > > | > > -----|-----------------------------> ISP router + DNS server > > | > > | 202.214.62.62 > > ------- > > | | default gateway: ISP router > > | B | static route: 202.214.62.40 for net 203.168.62.0 > > | | > > ------- > > > > Using netstat and tcpdump I discovered the following. If I ping > > machine B from A, I can see the ICMP packets make this journey: > > > > ICMP request: A --> FW --> B > > ICMP reply: B --> FW --> land of no return > > > > If I ping machine A from B, I get this: > > > > ICMP request: B --> FW --> ISP router > > > > I seems that FW will only forward packets in one direction. > > However in the first case it appears the ICMP reply packets > > are silently dropped [netstat does not report dropped packets]. > > > > In the second case, FW is actively trying to forward the packets > > to the default gateway. > > > > I'm at a loss to explain why this is occuring. I've enabled > > packet forwarding in FW's kernel. Is something else required > > to get packets forwarded between network interfaces on the same > > machine??? > > > > Incidentally, IPFW is not built into machine FW's kernel. > > > > Any suggestions would be most appreciated. > > > > Thanks, > > > > -john > > -- > Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 > Network Architect, CLEAR Net http://www.clear.net.nz/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 11:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06825 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 11:47:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from ibm.net. (slip166-72-224-172.pa.us.ibm.net [166.72.224.172]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06794 for ; Sat, 31 Oct 1998 11:47:08 -0800 (PST) (envelope-from placej@ibm.net) Received: (from placej@localhost) by ibm.net. (8.8.8/8.8.8) id OAA00313; Sat, 31 Oct 1998 14:46:55 -0500 (EST) (envelope-from placej) Message-ID: <19981031144649.A278@ka3tis.com> Date: Sat, 31 Oct 1998 14:46:49 -0500 From: "John C. Place" To: hackers@freebsd.com Cc: hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? Reply-To: "John C. Place" Mail-Followup-To: hackers@freebsd.com, hackers@FreeBSD.ORG References: <199810300813.AAA01726@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Bill Fumerola on Fri, Oct 30, 1998 at 10:25:39AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Oct 30, 1998 at 10:25:39AM -0500, Bill Fumerola wrote: > I'm not a kernel-hacking kind of guy, but I know just from personal C > experiences that scanf makes things a lot easier to change later on and > easier to get a visual representation of. scanf and sprintf have become my > friend. > I am not one either but I thought the *printf commands are very expensive (to the processer) and something as low level as the kernel would one try to avoid these??? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 12:04:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09012 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 12:04:32 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles325.castles.com [208.214.167.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09005 for ; Sat, 31 Oct 1998 12:04:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA01039; Sat, 31 Oct 1998 12:04:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810312004.MAA01039@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John C. Place" cc: hackers@freebsd.com, hackers@FreeBSD.ORG Subject: Re: scanf in the kernel? In-reply-to: Your message of "Sat, 31 Oct 1998 14:46:49 EST." <19981031144649.A278@ka3tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 12:04:07 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Oct 30, 1998 at 10:25:39AM -0500, Bill Fumerola wrote: > > I'm not a kernel-hacking kind of guy, but I know just from personal C > > experiences that scanf makes things a lot easier to change later on and > > easier to get a visual representation of. scanf and sprintf have become my > > friend. > > > I am not one either but I thought the *printf commands are very > expensive (to the processer) and something as low level as the kernel > would one try to avoid these??? One would generally try to avoid having them anywhere in a critical path, certainly, but they're not actually that expensive, and there's always a tradeoff between speed and maintainability. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 12:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09929 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 12:15:26 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09924 for ; Sat, 31 Oct 1998 12:15:25 -0800 (PST) (envelope-from vanmaren@fast.cs.utah.edu) Received: from fast.cs.utah.edu (fast.cs.utah.edu [155.99.212.1]) by wrath.cs.utah.edu (8.8.8/8.8.8) with SMTP id NAA16842 for ; Sat, 31 Oct 1998 13:15:22 -0700 (MST) Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf) id NAA22131; Sat, 31 Oct 1998 13:15:21 -0700 Date: Sat, 31 Oct 1998 13:15:21 -0700 From: vanmaren@fast.cs.utah.edu (Kevin Van Maren) Message-Id: <199810312015.NAA22131@fast.cs.utah.edu> To: hackers@FreeBSD.ORG Subject: Re: nfs/amd hangs / getattr request flood problem Cc: danderse@cs.cs.utah.edu, mike@fast.cs.utah.edu, sclawson@cs.cs.utah.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I looked at this a bit more. I am currently wondering about the comment in nfs/nfs_subs.c nfs_getattrcache(), which says: "XXX n_mtime doesn't seem to be updated on a miss-and-reload". Peter added it in version 1.54, when he redid much of this function. Dumping the three numbers in the check, I get this: if ((time_second - np->n_attrstamp) >= timeo) { printf("%s: miss. time_second=%d, n_attrstamp=%d, timeo=%d\n", __FUNCTION__,time_second, np->n_attrstamp, timeo); nfsstats.attrcache_misses++; return (ENOENT); } nfs_getattrcache: miss. time_second=909863755, n_attrstamp=909863755, timeo=0 nfs_getattrcache: miss. time_second=909863755, n_attrstamp=909863755, timeo=0 nfs_getattrcache: miss. time_second=909863755, n_attrstamp=909863755, timeo=0 nfs_getattrcache: miss. time_second=909863755, n_attrstamp=909863755, timeo=0 nfs_getattrcache: miss. time_second=909863755, n_attrstamp=909863755, timeo=0 I then added a printf after the if(), and got a bunch of these: nfs_getattrcache: hit. time_second=909864329, n_attrstamp=909864319, timeo=60 nfs_getattrcache: hit. time_second=909864329, n_attrstamp=909864319, timeo=60 nfs_getattrcache: hit. time_second=909864329, n_attrstamp=909864319, timeo=60 So, the question then becomes, "why is the timeout set to 0"? On all the file/directories in the filesystem, it is set to 60. However, the mount point itself is being set to 0. This results in a UDP message from the kernel to amd, which then sends a UDP reply back to the kernel using its info. However, that brings us back to the comment... Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 12:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10709 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 12:21:57 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10702 for ; Sat, 31 Oct 1998 12:21:55 -0800 (PST) (envelope-from vanmaren@fast.cs.utah.edu) Received: from fast.cs.utah.edu (fast.cs.utah.edu [155.99.212.1]) by wrath.cs.utah.edu (8.8.8/8.8.8) with SMTP id NAA16971 for ; Sat, 31 Oct 1998 13:21:52 -0700 (MST) Received: by fast.cs.utah.edu (8.6.10/utah-2.15-leaf) id NAA22251; Sat, 31 Oct 1998 13:21:50 -0700 Date: Sat, 31 Oct 1998 13:21:50 -0700 From: vanmaren@fast.cs.utah.edu (Kevin Van Maren) Message-Id: <199810312021.NAA22251@fast.cs.utah.edu> To: hackers@FreeBSD.ORG Subject: Re: nfs/amd hangs / getattr request flood problem Cc: danderse@cs.cs.utah.edu, mike@fast.cs.utah.edu, sclawson@cs.cs.utah.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, this is probably a more represenative sample of the output I was seeing: nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=60 nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=60 nfs_getattrcache: miss. time_second=909865074, n_attrstamp=0, timeo=30 nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=30 nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=3 nfs_getattrcache: miss. time_second=909865074, n_attrstamp=0, timeo=3 nfs_getattrcache: miss. time_second=909865074, n_attrstamp=909865074, timeo=0 nfs_getattrcache: miss. time_second=909865074, n_attrstamp=909865074, timeo=0 nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=60 nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=60 nfs_getattrcache: hit. time_second=909865074, n_attrstamp=909865074, timeo=60 Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 13:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21730 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 13:49:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA21725 for ; Sat, 31 Oct 1998 13:48:59 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 13588 invoked from network); 31 Oct 1998 21:48:55 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (root@206.109.2.48) by mushi.colo.neosoft.com with SMTP; 31 Oct 1998 21:48:55 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id PAA17428; Sat, 31 Oct 1998 15:48:54 -0600 Date: Sat, 31 Oct 1998 15:48:54 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199810312148.PAA17428@bonkers.taronga.com> To: hackers@FreeBSD.ORG Subject: Re: Memory leak location tool? Newsgroups: taronga.freebsd.hackers In-Reply-To: <86u30lms4a.fsf@detlev.UUCP> References: <19981030141624.A1244@thought.org> Organization: none Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Lehenbauer wrote one which should be in TclX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 14:17:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24074 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 14:17:19 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24069 for ; Sat, 31 Oct 1998 14:17:17 -0800 (PST) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id OAA29002; Sat, 31 Oct 1998 14:17:10 -0800 (PST) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id OAA13904; Sat, 31 Oct 1998 14:16:59 -0800 (PST) From: Gary Kline Message-Id: <199810312216.OAA13904@tao.thought.org> Subject: Re: Memory leak location tool? In-Reply-To: <199810312148.PAA17428@bonkers.taronga.com> from Peter da Silva at "Oct 31, 98 03:48:54 pm" To: peter@taronga.com (Peter da Silva) Date: Sat, 31 Oct 1998 14:16:59 -0800 (PST) Cc: hackers@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Peter da Silva: > Karl Lehenbauer wrote one which should be in TclX. > I've found a few others, two in the devel tree. Don't see the tcl one. gary > -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 17:49:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17734 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 17:49:01 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17729 for ; Sat, 31 Oct 1998 17:48:59 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01547; Sat, 31 Oct 1998 16:16:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811010016.QAA01547@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm cc: Peter Jeremy , hackers@FreeBSD.ORG, gallatin@cs.duke.edu Subject: Re: sync writes with softupdates enabled In-reply-to: Your message of "Sat, 31 Oct 1998 15:46:39 +0800." <199810310746.PAA18872@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 16:16:51 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that this has been committed, can we have some feedback from people using mmap heavily on -current? This should make an enormous difference to mmap's performance there if it's a real fix... Andrew, how does this affect that nasty machine-pegging test program you showed me a while back? > > That's almost certainly correct. Try running without mmap. It used to > > be faster that way; maybe it is again? > > > Hmm, from vm_object.c: > > void > vm_object_page_clean(object, start, end, flags) > > pagerflags = (flags & (OBJPC_SYNC | OBJPC_INVAL)) ? VM_PAGER_PUT_SYNC : > 0; > pagerflags |= (flags & OBJPC_INVAL) ? VM_PAGER_PUT_INVAL : 0; > VOP_FSYNC(vp, NULL, (pagerflags & VM_PAGER_PUT_SYNC)?MNT_WAIT:0, curproc); > > vm_object.h: > #define OBJPC_SYNC 0x1 /* sync I/O */ > #define OBJPC_INVAL 0x2 /* invalidate */ > > Yet, we have: > > vfs_subr.c: vm_object_page_clean(vp->v_object, 0, 0, TRUE); > vfs_syscalls.c: vm_object_page_clean(vp->v_object, 0, 0, FALSE); > > param.h:#define TRUE 1 > param.h:#define FALSE 0 > > The sync_fsync() writes are calling vfs_msync() with MNT_NOWAIT, but > vfs_msync() is turning dirty mmap pages into sync writes. This behavior > is needed prior to unmount (obviously) but doesn't seem useful for the > periodic sync. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 17:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17804 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 17:49:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles215.castles.com [208.214.165.215]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17792 for ; Sat, 31 Oct 1998 17:49:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01372; Sat, 31 Oct 1998 15:50:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810312350.PAA01372@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: hackers@FreeBSD.ORG Subject: Re: copyin/copyout routines. In-reply-to: Your message of "Sat, 31 Oct 1998 10:07:47 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Oct 1998 15:50:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > someone showed me a driver they were working on that was getting errors > using copyin and copyout.. the error was when they used copyin to copy > from user land into the kernel they would get a bad adress error. > > the location they were copying to was on the kernel stack ie. > > int x; > > y = copyin(useraddr, &x, sizeof(x)); > > for some reason i think that copyin only works in/out of the kernel malloc > error, basically he should be copying into malloc'd areas, not the stack. > > is this true? No. Getting EFAULT from copyin/out means that the user address is bad. In most cases, it's wrong to use copyin/out in a driver anyway; you should be using uiomove. Typically you will get this problem if you are making a mistake about the semantics of the data arg to your ioctl handler, either indirecting one time too many or one time too few (copying from the address of the kernel copy of the value, or copying from the address value at the location in userspace that the copied value points to). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 18:02:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19016 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 18:02:30 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19011 for ; Sat, 31 Oct 1998 18:02:29 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id VAA13977; Sat, 31 Oct 1998 21:04:58 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Sat, 31 Oct 1998 21:04:58 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Mike Smith cc: hackers@FreeBSD.ORG Subject: Re: copyin/copyout routines. In-Reply-To: <199810312350.PAA01372@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG that seems to make sense, and looks like the problem i'm forwarding this to the driver author. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Sat, 31 Oct 1998, Mike Smith wrote: > > > > someone showed me a driver they were working on that was getting errors > > using copyin and copyout.. the error was when they used copyin to copy > > from user land into the kernel they would get a bad adress error. > > > > the location they were copying to was on the kernel stack ie. > > > > int x; > > > > y = copyin(useraddr, &x, sizeof(x)); > > > > for some reason i think that copyin only works in/out of the kernel malloc > > error, basically he should be copying into malloc'd areas, not the stack. > > > > is this true? > > No. Getting EFAULT from copyin/out means that the user address is bad. > > In most cases, it's wrong to use copyin/out in a driver anyway; you > should be using uiomove. > > Typically you will get this problem if you are making a mistake about > the semantics of the data arg to your ioctl handler, either indirecting > one time too many or one time too few (copying from the address of the > kernel copy of the value, or copying from the address value at the > location in userspace that the copied value points to). > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 18:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23012 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 18:31:48 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23007 for ; Sat, 31 Oct 1998 18:31:46 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.9.1/8.9.1) with ESMTP id SAA24573; Sat, 31 Oct 1998 18:31:40 -0800 (PST) (envelope-from jdp) Message-Id: <199811010231.SAA24573@austin.polstra.com> To: joelh@gnu.org Subject: Re: Memory leak location tool? In-Reply-To: <86u30lms4a.fsf@detlev.UUCP> References: <19981030141624.A1244@thought.org> <86u30lms4a.fsf@detlev.UUCP> Organization: Polstra & Co., Seattle, WA Cc: hackers@FreeBSD.ORG Date: Sat, 31 Oct 1998 18:31:40 -0800 From: John Polstra Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <86u30lms4a.fsf@detlev.UUCP>, Joel Ray Holveck wrote: > > Are there any free tools to detect likely memory leaks? Tools > > like Purify aren't quite what I'm looking for. > > Anybody? > > "more `grep -l malloc /usr/ports/devel/*/pkg/DESCR`" will turn up the > following: > > * The Boehm-Weiser garbage collecting malloc (boehm-gc) includes a leak > detector. And I'll just add that it works very nicely indeed. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 18:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23398 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 18:34:39 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA23342 for ; Sat, 31 Oct 1998 18:34:33 -0800 (PST) (envelope-from rabtter@aye.net) Received: (qmail 15856 invoked by uid 2784); 1 Nov 1998 02:26:22 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Nov 1998 02:26:22 -0000 Date: Sat, 31 Oct 1998 21:26:22 -0500 (EST) From: Barrett Richardson To: john cooper cc: freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jabley@clear.co.nz, tfujii@isi.co.jp Subject: Re: Request help with packet forwarding problem [2.2.7].. In-Reply-To: <98Nov1.004713jst.21889@ns.isi.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look at this route on machine B: 203.214.62 202.214.62.40 UGSc 0 596 vx0 ^^^ I think it probably should be 203.168.62 202.214.62.40 UGSc 0 596 vx0 Are you sure you were running the tcpdump on FW and not B? With no route to 203.168.62 on B, the ISP router and B should have played ping pong with the echo request until it died. Also check the netmask on vx0 on FW. It is not showing a 202.214.62/25 route like B is. On Sun, 1 Nov 1998, john cooper wrote: > > > Date: Sat, 31 Oct 1998 23:45:36 +0900 > > From: Joe Abley > > To: john cooper , freebsd-hackers@FreeBSD.org, > > freebsd-questions@FreeBSD.org > > Cc: tfujii@isi.co.jp > > Subject: Re: Request help with packet forwarding problem [2.2.7].. > > > > > > John, > > > > Could you do a "netstat -rn" on A, B and FW, and post the output? > > Machine A: > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 203.168.62.35 UGSc 0 21183 ed1 > 127.0.0.1 127.0.0.1 UH 0 7 lo0 > 203.168.62 link#1 UC 0 0 > 203.168.62.35 0:0:f4:4a:ad:e8 UHLW 2 312 ed1 1125 > 203.168.62.58 0:20:18:71:be:2d UHLW 1 26 lo0 > > Machine FW: > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 202.214.62.33 UGSc 4 530 vx0 > 127.0.0.1 127.0.0.1 UH 0 2 lo0 > 202.214.62 link#1 UC 0 0 > 202.214.62.33 0:a0:de:0:13:76 UHLW 4 0 vx0 15 > 202.214.62.35 0:a0:24:2a:9:24 UHLW 0 34 vx0 795 > 202.214.62.62 link#1 UHLW 1 8266 > 203.168.62 link#2 UC 0 0 > 203.168.62.35 0:0:f4:4a:ad:e8 UHLW 0 8 lo0 > 203.168.62.58 0:20:18:71:be:2d UHLW 0 2 ed0 1197 > > Machine B: > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 202.214.62.33 UGSc 2 87918 vx0 > 127.0.0.1 127.0.0.1 UH 0 180 lo0 > 202.214.62/25 link#1 UC 0 0 > 202.214.62.33 link#1 UHLW 3 0 > 202.214.62.35 0:a0:24:2a:9:24 UHLW 2 3142 vx0 1101 > 202.214.62.40 0:a0:24:7d:c6:7c UHLW 2 297 vx0 1038 > 202.214.62.62 0:a0:24:7d:c6:43 UHLW 0 0 lo0 > 203.214.62 202.214.62.40 UGSc 0 596 vx0 > > > Where were you running tcpdump? > > On machine FW. > > > Were you identifying the gateway for > > each ICMP request or response by looking at the destination ethernet > > address? > > No, I was referring to /etc/rc.conf: defaultrouter="..." > > Thanks for the response, > > -john > > > > > > Joe > > > > On Sat, Oct 31, 1998 at 11:06:16PM +0900, john cooper wrote: > > > I'm trying to get a system configured as a gateway. The > > > first step [which I thought would be simple] was to simply > > > forward packets between interfaces: > > > > > > > > > ------- > > > | | default gateway: 203.168.62.35 > > > | A | > > > | | > > > ------- > > > | 203.168.62.58 (ed1) > > > | > > > | 203.168.62.35 (ed0) > > > ------- > > > | | default gateway: ISP router > > > | FW | net.inet.ip.forwarding: 1 > > > | | > > > ------- > > > | 202.214.62.40 (vx0) > > > | > > > -----|-----------------------------> ISP router + DNS server > > > | > > > | 202.214.62.62 > > > ------- > > > | | default gateway: ISP router > > > | B | static route: 202.214.62.40 for net 203.168.62.0 > > > | | > > > ------- > > > > > > Using netstat and tcpdump I discovered the following. If I ping > > > machine B from A, I can see the ICMP packets make this journey: > > > > > > ICMP request: A --> FW --> B > > > ICMP reply: B --> FW --> land of no return > > > > > > If I ping machine A from B, I get this: > > > > > > ICMP request: B --> FW --> ISP router > > > > > > I seems that FW will only forward packets in one direction. > > > However in the first case it appears the ICMP reply packets > > > are silently dropped [netstat does not report dropped packets]. > > > > > > In the second case, FW is actively trying to forward the packets > > > to the default gateway. > > > > > > I'm at a loss to explain why this is occuring. I've enabled > > > packet forwarding in FW's kernel. Is something else required > > > to get packets forwarded between network interfaces on the same > > > machine??? > > > > > > Incidentally, IPFW is not built into machine FW's kernel. > > > > > > Any suggestions would be most appreciated. > > > > > > Thanks, > > > > > > -john > > > > -- > > Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 > > Network Architect, CLEAR Net http://www.clear.net.nz/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 31 20:18:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05204 for freebsd-hackers-outgoing; Sat, 31 Oct 1998 20:18:20 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA05197 for ; Sat, 31 Oct 1998 20:18:15 -0800 (PST) (envelope-from rabtter@aye.net) Received: (qmail 2185 invoked by uid 2784); 1 Nov 1998 04:16:26 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Nov 1998 04:16:26 -0000 Date: Sat, 31 Oct 1998 23:16:26 -0500 (EST) From: Barrett Richardson To: hackers@FreeBSD.ORG Subject: multistack compiler and VM_MAXUSER_ADDRESS Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A gentleman recently posted a patch to bugtraq for the egcs compiler from cygnus (actually a linux patch) that allocates a separate stack for each locally declared array. One of the items needed is the address of the stack top. The only thing I could find that looks it may fill the bill is VM_MAXUSER_ADDRESS in vmparam.h. Any hints tips? Also his notes say that there is unaccessable pages between stacks to prevent one stack for overflowing on to another. What exactly happens when you write to an unaccessable page, and what exactly is an "unaccessable" page? - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message