From owner-freebsd-hackers Sun Jul 29 1:16:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id CB37137B403 for ; Sun, 29 Jul 2001 01:16:36 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: by sharmas.dhs.org (Postfix, from userid 500) id 5A1955E2C8; Sun, 29 Jul 2001 01:16:56 -0700 (PDT) Date: Sun, 29 Jul 2001 01:16:56 -0700 From: Arun Sharma To: Daniel Eischen Cc: hackers@FreeBSD.ORG Subject: Re: libc_r, signals and modifying sigcontext Message-ID: <20010729011656.A11337@sharmas.dhs.org> References: <20010721191747.A32529@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from eischen@vigrid.com on Sun, Jul 22, 2001 at 10:50:01AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 22, 2001 at 10:50:01AM -0400, Daniel Eischen wrote: Dan, I tried this patch against 4.3-STABLE (had to substitute _get_curthread() with _thread_run), without success. After the sigreturn, EIP remains the same. Should I be testing against -current ? -Arun > Try this patch: > > -- > Dan Eischen > > Index: uthread/pthread_private.h > =================================================================== > RCS file: /opt/b/CVS/src/lib/libc_r/uthread/pthread_private.h,v > retrieving revision 1.59 > diff -u -r1.59 pthread_private.h > --- uthread/pthread_private.h 2001/07/20 04:23:10 1.59 > +++ uthread/pthread_private.h 2001/07/22 04:29:10 > @@ -654,6 +654,7 @@ > int sig_has_args; /* use signal args if true */ > ucontext_t uc; > siginfo_t siginfo; > + int restore_context; > }; > > /* > Index: uthread/uthread_sig.c > =================================================================== > RCS file: /opt/b/CVS/src/lib/libc_r/uthread/uthread_sig.c,v > retrieving revision 1.38 > diff -u -r1.38 uthread_sig.c > --- uthread/uthread_sig.c 2001/06/29 17:09:07 1.38 > +++ uthread/uthread_sig.c 2001/07/22 04:28:02 > @@ -1004,6 +1004,10 @@ > else > (*(sigfunc))(psf->signo, > (siginfo_t *)psf->siginfo.si_code, &psf->uc); > + if (psf->restore_context != 0) { > + memcpy(&thread->ctx.uc, &psf->uc, sizeof(psf->uc)); > + thread->ctxtype = CTX_UC; > + } > } > /* > * Call the kernel scheduler to safely restore the frame and > @@ -1046,6 +1050,7 @@ > stackp -= sizeof(struct pthread_signal_frame); > > psf = (struct pthread_signal_frame *) stackp; > + psf->restore_context = 0; > > /* Save the current context in the signal frame: */ > thread_sigframe_save(thread, psf); > @@ -1059,6 +1064,8 @@ > sizeof(psf->uc)); > memcpy(&psf->siginfo, &_thread_sigq[psf->signo - 1].siginfo, > sizeof(psf->siginfo)); > + psf->restore_context = ((thread == _get_curthread()) && > + (thread->ctxtype == CTX_UC)); > } > > /* Setup the signal mask: */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 6:44:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from warrior-outbound.services.quay.plus.net (unknown [212.159.14.227]) by hub.freebsd.org (Postfix) with SMTP id 9DD2E37B401 for ; Sun, 29 Jul 2001 06:44:33 -0700 (PDT) (envelope-from wcp@pelissero.org) Received: (qmail 14629 invoked from network); 29 Jul 2001 13:44:28 -0000 Received: from unknown (HELO daemon.lpds.sublink.org) (212.159.32.211) by warrior with SMTP; 29 Jul 2001 13:44:28 -0000 Received: from pelissero.org (hyde.lpds.sublink.org [10.0.0.2]) by daemon.lpds.sublink.org (8.11.4/8.9.3) with ESMTP id f6TDgjA30985 for ; Sun, 29 Jul 2001 14:42:45 +0100 (BST) (envelope-from wcp@pelissero.org) Received: (from wcp@localhost) by pelissero.org (8.11.4/8.9.3) id f6TDgiq08161 for freebsd-hackers@freebsd.org; Sun, 29 Jul 2001 14:42:44 +0100 (BST) (envelope-from wcp) Date: Sun, 29 Jul 2001 14:42:44 +0100 (BST) Message-Id: <200107291342.f6TDgiq08161@pelissero.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: "Walter C. Pelissero" Reply-To: walter@pelissero.org To: freebsd-hackers@freebsd.org Subject: PCMCIA hot swap X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid X-Attribution: WP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Having recently upgraded from 4.0 to 4.3 on my laptop I've noticed that PCMCIA insertion and extraction doesn't work as it used to. The system (Vaio PCG-XG9) just freezes. Some time I'm able to rescue the situation inserting and extracting several times the offending card. Some time I have to power off and reboot. Normally, if a card is insert before the bootstrap it's correctly detected and configured. My question is: "Has the hot swap feature been somehow dropped from the PCCARD code?" -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 6:49:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 171F037B401 for ; Sun, 29 Jul 2001 06:49:20 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id JAA18056; Sun, 29 Jul 2001 09:48:31 -0400 (EDT) Date: Sun, 29 Jul 2001 09:48:30 -0400 (EDT) From: Daniel Eischen To: Arun Sharma Cc: hackers@FreeBSD.ORG Subject: Re: libc_r, signals and modifying sigcontext In-Reply-To: <20010729011656.A11337@sharmas.dhs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 29 Jul 2001, Arun Sharma wrote: > On Sun, Jul 22, 2001 at 10:50:01AM -0400, Daniel Eischen wrote: > > Dan, > > I tried this patch against 4.3-STABLE (had to substitute > _get_curthread() with _thread_run), without success. After > the sigreturn, EIP remains the same. Can you breakpoint or add a print statement to see if the thread chosen to handle the signal is the current thread (_thread_run == thread) in the patched section below? > > @@ -1059,6 +1064,8 @@ > > sizeof(psf->uc)); > > memcpy(&psf->siginfo, &_thread_sigq[psf->signo - 1].siginfo, > > sizeof(psf->siginfo)); > > + psf->restore_context = ((thread == _get_curthread()) && > > + (thread->ctxtype == CTX_UC)); > Should I be testing against -current ? No, -stable should be fine (other than the _get_curthread() vs _thread_run diff) -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 10:23:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 6875437B401 for ; Sun, 29 Jul 2001 10:23:51 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15QuJ8-000LNb-00 for hackers@FreeBSD.org; Sun, 29 Jul 2001 19:24:50 +0200 From: Sheldon Hearn To: hackers@FreeBSD.org Subject: Why objcopy --strip-debug instead of strip? Date: Sun, 29 Jul 2001 19:24:49 +0200 Message-ID: <82186.996427489@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi folks, When the kernel is built as kernel.debug, why is it passed through objcopy --strip-debug before being installed, instead of being passed through strip? Background: I recently found that the Handbook instructions for "Debugging Loadable Modules Using GDB" is mostly useless for post-mortem crash dump analysis, because buildkernel doesn't build modules with debugging support, even when CONFIGARGS=-g. The attached patch (for the i386 only) fixes this so that, if kernel.debug is built, foo.ko.debug etc. are built. For each foo.ko.debug, we produce foo.ko with objcopy --strip-debug and install foo.ko. What I'm unsure of is why it's worth going to all this trouble. Why not simply build all the modules with debugging support compiled in (assuming debugging support was requested for the kernel), and strip them at install time (install -s)? Ciao, Sheldon. Index: /usr/src/sys/conf/Makefile.i386 =================================================================== RCS file: /home/ncvs/src/sys/conf/Makefile.i386,v retrieving revision 1.240 diff -u -d -r1.240 Makefile.i386 --- /usr/src/sys/conf/Makefile.i386 2001/07/26 23:04:46 1.240 +++ /usr/src/sys/conf/Makefile.i386 2001/07/29 16:51:56 @@ -272,6 +272,9 @@ .if defined(MODULES_OVERRIDE) MKMODULESENV+= MODULES_OVERRIDE="${MODULES_OVERRIDE}" .endif +.if defined(DEBUG) +MKMODULESENV+= DEBUG="${DEBUG}" DEBUG_FLAGS="${DEBUG}" +.endif modules: @mkdir -p ${.OBJDIR}/modules Index: /usr/src/sys/conf/kmod.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kmod.mk,v retrieving revision 1.104 diff -u -d -r1.104 kmod.mk --- /usr/src/sys/conf/kmod.mk 2001/07/18 09:59:55 1.104 +++ /usr/src/sys/conf/kmod.mk 2001/07/29 17:15:59 @@ -77,6 +77,7 @@ KMODLOAD?= /sbin/kldload KMODUNLOAD?= /sbin/kldunload +OBJCOPY?= objcopy TARGET_ARCH?= ${MACHINE_ARCH} @@ -131,7 +132,15 @@ PROG= ${KMOD}.ko .endif -${PROG}: ${KMOD}.kld +.if !defined(DEBUG) +FULLPROG= ${PROG} +.else +FULLPROG= ${PROG}.debug +${PROG}: ${FULLPROG} + ${OBJCOPY} --strip-debug ${FULLPROG} ${PROG} +.endif + +${FULLPROG}: ${KMOD}.kld ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${KMOD}.kld ${KMOD}.kld: ${OBJS} @@ -188,7 +197,7 @@ ${ECHO} ${.TARGET} "->" $$path ; \ ln -s $$path ${.TARGET} -CLEANFILES+= ${PROG} ${KMOD}.kld ${OBJS} ${_ILINKS} symb.tmp tmp.o +CLEANFILES+= ${PROG} ${FULLPROG} ${KMOD}.kld ${OBJS} ${_ILINKS} symb.tmp tmp.o .if !target(install) .if !target(beforeinstall) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 13:20:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 1513837B401; Sun, 29 Jul 2001 13:20:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA23285; Sun, 29 Jul 2001 13:19:59 -0700 (PDT) Message-ID: <3B64647E.85BAE179@mindspring.com> Date: Sun, 29 Jul 2001 12:31:10 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Julian Elischer , "Eugene L. Vorokov" , Soren Kristensen , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Why two cards on the same segment... References: <20010727164602.46DBC380B@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > Have you seen Bill Paul's FEC stuff? It works very nicely, but using the > cisco Fast EtherChannel instead of VRRP. While it isn't the same, we have > used it with four interfaces merged into one virtual interface quite > happily. I haven't played with it... does it handle one of the four dropping out, and do the right thing? Say I have four boxes, and I want to have four virtual interfaces; can you define more than one virtual interface for the group at the same time, and keep four virtual interfaces going with only three boxes? That seems like the most useful configuration (to me, anyway...). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 13:20:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 75B0237B403; Sun, 29 Jul 2001 13:20:51 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA24092; Sun, 29 Jul 2001 13:20:12 -0700 (PDT) Message-ID: <3B646B72.813A46DC@mindspring.com> Date: Sun, 29 Jul 2001 13:00:50 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Eischen Cc: y-carden@uniandes.edu.co, jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: KNOTE() References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Daniel Eischen wrote: > Why are you trying to push so much into the kernel? > Rethink the problem you are trying to solve. See his other posting; he's living inside the constraints of an existing library and API. In retrospect, and given the information he has subsequently provided, kevent's are probably not the correct approach for him, since it would mean unrolling part of the RTPSchedule() code into the main loop of any application he built on top of the library. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 13:21:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 39FCB37B401 for ; Sun, 29 Jul 2001 13:21:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA23806; Sun, 29 Jul 2001 13:20:08 -0700 (PDT) Message-ID: <3B646AAB.688669C5@mindspring.com> Date: Sun, 29 Jul 2001 12:57:31 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: y-carden@uniandes.edu.co Cc: hackers@FreeBSD.ORG Subject: Re: Invoking a userland function from kerne References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG y-carden@uniandes.edu.co wrote: > Now, I need manage Timed Events: > > Two RTP related events must occur which are timed. They are: > > 1.RTCP (control RTP packages) reports must be sent periodically. > 2.BYE (a control RTP package) packets may be reconsidered for transmission. > > To support scheduling, timed events are handled by two functions, > RTPSchedule() and RTPExecute(). > > The first of these functions is written by the user(user process). > It is called by the RTP kernel module (originally the library) > to request scheduling of events at some predetermined time. Called, or invoked? If it's invoked (no parameters needed), then you can implement a kevent that occurs at the right time. The main look of your program listens for kevents, including this one, and then it dispatches the event to the RTPSchedule() function. If, on the other hand, you need to pass parameters, then you should implement it differently. My suggestion would be to implement a system call/ioctl that takes the address of a parameter block structure as an argument, and then sleeps on a well known address (tsleep for 4.x, msleep for -current), waiting for a request from the kernel. When the kernel wants to make the request to user space, it copies out the request parameters into the parameter block structure, and then wakes up the sleeping process (via wakeup). When that process runs in user space, it calls RTPSchedule() with the results of the system call, which are really the parameters for the schedule call. Once this has completed, it makes the same system call again, goes back to sleep, and waits for the next schedule request from the kernel. THe call back down _could_ provide the results of the RTPSchedule() function to the kernel module, if necessary (via copyin; you would need to set up a flag field so that the first call down ends up doing nothing, since it will have no "results" to give the kernel module). This is backward from the way that people normally use a system call interface, but there is a lot of precedent, including a lot of NFS implementations, which do this sort of thing. If you need to do user space processing on top of that, then you should look at the sfork system call man page. It will tell you how to get another process context into your single process, so that you can have a blocking context on which to make your call. If you modify scheduling parameters in user space from the other part of your process, you will need to actually protect your data structures. You can implement a light weight lock to do this using the cmpxchgl (compare and exchange, locked) instruction (assuming this is x86; other architectures will have other instructions). You should not hold this lock over system calls, etc.. If you need help with the lock, you should look at the code in atomic.h in -current, which has implementations of these operations (most are much more complicated than they need to be). > void RTPSchedule(int id, void* opaque, struct timeval *tp); > > rtperror RTPExecute(int id, void* opaque); > > The RTP kernel module will call RTPSchedule, and pass it the context cid > and an opaque piece of data, opaque. It will also pass the time for > which the scheduled event is to occur, tp. At the appropriate time, > tp, the application should call RTPExecute, and pass it the opaque > token provided in the call to RTPSchedule, in addition to the identifier > id. IMO, you would be much better off implementing most of this in the kernel, using the existing timer functions; the policy could still live in user space. Realize that this will not be true Real Time, since your process will have to get a quantum in order to be able to run the scheduler. > This general mechanism allows for the RTP kernel module to schedule > arbitrary timed events. All information about the nature of the > events is kept internal. The opaque data is used internally to > identify particular events. You may want to check out "setitimer", and do the minor work needed to manage the deltas from one event to another in order to achieve minimal latency. Realize, again, that anything you end up doing will actually fire at "the next quantum following the even expiration", rather than "immediately, at the event expiration; hopefully this is high enough granularity for you, though I suspect you will want to decrease the size of the quantum using sysctl, to ensure things run faster, and may also want to use rtprio to set the priority on the process (to make sure no other process gets the quantum before your, which could lead to a multiqiantum lag, if your system is at all loaded). If you use the sfork approach (above), then you will need to remember to set it on both the parent and the child (sfork'ed) process. > So, my original question was: > Into my kernel code, How I can call to > RTPSchedule() userland function? > > You say me that I can do with kevent() facility. > > How I can do it exactly? You send an event to user space, and the user space code is built around an event processing loop (I'm surprised that the user space threads implementation has not be rebuilt around kevent, actually). This is the same as the system call "completing" actually being a call back into user space (per above), but the request and the completion are asynchronous, and, unlike non-blocking fd's, they are not required to be retried in the event that they can not go through immediately. > I apologize perhaps the following is stupid, > but from the user process I can call kevent() > for a file descriptor and into kernel when I need > call to RTPSchedule() instead I would try for example to write > to file descriptor to trigger the event. Can I do this? > I don't sure but into kernel it can't write to file descriptor. You can send events using KNOTE(). These have to be noted on a file descriptor, yes, but you can do that using a pseudo device for your kernel module, which KNOTE()'s when it wants the user space program to make a policy decision. Again, this only works if your main program loop is a kevent loop waiting for events. If your main program is more traditional, which is probable, given the library description you have provided, then the sfork() and inverted system call interface is probably your best bet. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 13:42:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 04E2637B401; Sun, 29 Jul 2001 13:42:13 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.4/8.11.4) with ESMTP id f6TKfxn41502; Sun, 29 Jul 2001 16:41:59 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200107292041.f6TKfxn41502@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: tlambert2@mindspring.com Cc: Daniel Eischen , y-carden@uniandes.edu.co, jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: KNOTE() References: <3B646B72.813A46DC@mindspring.com> In-reply-to: Your message of "Sun, 29 Jul 2001 13:00:50 PDT." <3B646B72.813A46DC@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Jul 2001 16:41:59 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Daniel Eischen wrote: > > Why are you trying to push so much into the kernel? > > Rethink the problem you are trying to solve. > > See his other posting; he's living inside the constraints > of an existing library and API. Yes, except these are problems of his own making because the library and API were originally user-mode code and not in the kernel. Somewhere along the way a decision was made to push that function into the kernel, and all these bizzaro "problems" of calling back user-mode code from the kernel, etc. follow from that decision. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14: 2: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id E570A37B401 for ; Sun, 29 Jul 2001 14:00:37 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA06616; Sun, 29 Jul 2001 13:52:09 -0700 (PDT) Message-ID: <3B6477A0.5270E5F8@mindspring.com> Date: Sun, 29 Jul 2001 13:52:48 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bosko Milekic Cc: Zhihui Zhang , Alfred Perlstein , vishwanath pargaonkar , freebsd-hackers@FreeBSD.ORG Subject: Re: cluster size References: <3B632429.D3FA2EB0@mindspring.com> <20010728194727.A54256@technokratis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bosko Milekic wrote: > > So, in general: > > > > 1) Only some allocators can be used at interrupt time > > 2) If they can, they must precommit kernel address space > > to the task > > 3) Once memory is allocated from one of these pools, it > > is never returned to the system for reuse > > This (3) only applies to the zone allocator. With maps, > you *can* free back to the map and unwire the wired pages > (freeing physical memory). FWIW, I am allocating my mbuf's in machdep.c, very in on the kernel life cycle, out of real physical memory. I have a real problem with the way it currently works in 4.3 (which is what I am using; I dislike -current, mostly because it is going in the wrong direction), and with the way the 5.x code works. In both cases, the code will permit a map allocation without the underlying pages being allocated (indeed, you point to this as a "feature" of the -current code). The problem with this is when you go to get a backing page, and there is nothing there. The allocation fails, but it returns the map entry location, and when an attempt is subsequently made to access the memory in extreme low memeory conditions, the wiring of a free backing page fails, with the inevitable consequences. The allocation should be falied because of the unavailability of a backing page. As my system currently exists, I don't have these problems -- but I do have the issue of the memory being allocated. Realize that when the page map is not sparse -- say on a system with 4G of physical RAM -- there are a lot of basic assumptions in both the 4.3 and -current schemes which simply are not true. This includes the overallocation of page tables for the kernel on the assumption that the relative size of physical RAM is small, compared to the kernel virtual address space. > > 4) The general malloc() code _can not_ be used at interrupt > > time in FreeBSD (but SVR4's allocator can). > > Huh? Do you realize that in much much earlier versions > of FreeBSD (not long after the import from 4.4BSD, or whatever > it was uipc_mbuf.c was initially imported from) all _MBUFS_ were > allocated directly with malloc()? Obviously, mbufs are allocatable > at interrupt time (and always were, afaic remember). All that you > have to make sure to do, when allocating at interrupt time is to > allocate with the M_NOWAIT flag. Yes, I realize this. I also realize why it was changed: because you are unlikely to be able to malloc at interrupt, unless you have a sufficient fre reserve to be able to do so. This approach was inferior, in that it tended to result in quick failure in receiver livelock cases, which was then aggravated by the lack of acknoldegements by the server. The current approach is a tiny bit better, in that it permits allocation at interrupt, which means that you buffer up the data, but you still have all of the issues which Jeff Mogul pointed out in his landmark paper. As far as SMP allocators go, you need to get rid of all locks in the common code path, period. This isn't really something you can negotiate on. The additional locks in your and Alfred's allocators are the direct result of not having a second level coelescing cache, per the Dynix allocator (see Uresh VAhalia's book, in particular, chapter 12. As far as interrupt allcoation goes, there are two things: 1) The available kernel virtual address space needs to be mapped so it can be allocated 2) The allocations need to be failed, even if mapping space is available, if backing space is not Addressing these issues would permit all kernel memory allocations to occur at interrupt. I'm not sure if Steve Baumel (the person largely responsible for the SVR4 VM system) ever wrote a paper on his approach, or not, but with the Solaris source code available, his code is now available for study. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14: 4:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 49F1E37B401 for ; Sun, 29 Jul 2001 14:04:05 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id NAA00702; Sun, 29 Jul 2001 13:58:52 -0700 (PDT) Message-ID: <3B647933.86F7FBA0@mindspring.com> Date: Sun, 29 Jul 2001 13:59:31 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Zhihui Zhang Cc: Bosko Milekic , Alfred Perlstein , vishwanath pargaonkar , freebsd-hackers@FreeBSD.ORG Subject: Re: cluster size References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Zhihui Zhang wrote: > > Excellent answer! I looked at the zone allocator code almost two years > back and I wondered at that time why FreeBSD cannot allocate KVM at > interrupt time but CAN allocate physical memory at interrupt time. It > turns out there is a physical memory reserve for interrupt time. By the > way, for the zone allocator stuff, I tried to use it in a KLD but > failed. Because if you use zone allocator in a KLD, you can not release > memory used by it cleanly when you do a kld unload. Thanks! There was a recent patch to add a "zdestroy" function, so that there would be no problems using zone from a loadable module. Note that you will not be able to do a ziniti, onlt a zinit, if you are loading as a module, unless you are very, very lucky, and your kernel memory map has not been fragged (this is unlikely, given FreeBSD's agressive caching policy: this is also the reason that the zalloci's get called so early). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14: 7: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nyc.rr.com (nycsmtp2fb.rdc-nyc.rr.com [24.29.99.78]) by hub.freebsd.org (Postfix) with ESMTP id 439B137B401 for ; Sun, 29 Jul 2001 14:07:03 -0700 (PDT) (envelope-from jslivko@blinx.net) Received: from equinox ([24.168.44.136]) by nyc.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Sun, 29 Jul 2001 17:06:38 -0400 From: "Jonathan M. Slivko" To: , "'Bosko Milekic'" Cc: "'Zhihui Zhang'" , "'Alfred Perlstein'" , "'vishwanath pargaonkar'" , Subject: RE: cluster size Date: Sun, 29 Jul 2001 17:06:47 -0400 Message-ID: <000401c11872$60f34aa0$6401a8c0@equinox> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-reply-to: <3B6477A0.5270E5F8@mindspring.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I'm not sure if Steve Baumel (the person largely responsible for >the SVR4 VM system) ever wrote a paper on his approach, or not, >but with the Solaris source code available, his code is now >available for study. Isn't that just the binary version, you still have to buy the source? -- Jonathan -- Jonathan M. Slivko Blinx Networks http://www.blinx.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14: 9:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.121.49]) by hub.freebsd.org (Postfix) with ESMTP id 91FA237B401 for ; Sun, 29 Jul 2001 14:09:23 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.234.Dial1.SanJose1.Level3.net [209.245.140.234]) by scaup.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id OAA11625; Sun, 29 Jul 2001 14:08:56 -0700 (PDT) Message-ID: <3B647B90.615BB07@mindspring.com> Date: Sun, 29 Jul 2001 14:09:36 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jonathan M. Slivko" Cc: "'Bosko Milekic'" , "'Zhihui Zhang'" , "'Alfred Perlstein'" , "'vishwanath pargaonkar'" , freebsd-hackers@FreeBSD.ORG Subject: Re: cluster size References: <000401c11872$60f34aa0$6401a8c0@equinox> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Jonathan M. Slivko" wrote: > > >I'm not sure if Steve Baumel (the person largely responsible for > >the SVR4 VM system) ever wrote a paper on his approach, or not, > >but with the Solaris source code available, his code is now > >available for study. > > Isn't that just the binary version, you still have to buy the source? $30 for the media (CDROM), last time I looked. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14:26:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 7A90C37B401 for ; Sun, 29 Jul 2001 14:26:48 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f6TLQgq51101; Sun, 29 Jul 2001 14:26:42 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f6TLQfa15379; Sun, 29 Jul 2001 14:26:41 -0700 (PDT) (envelope-from jdp) Date: Sun, 29 Jul 2001 14:26:41 -0700 (PDT) Message-Id: <200107292126.f6TLQfa15379@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: sheldonh@starjuice.net Subject: Re: Why objcopy --strip-debug instead of strip? In-Reply-To: <82186.996427489@axl.seasidesoftware.co.za> References: <82186.996427489@axl.seasidesoftware.co.za> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <82186.996427489@axl.seasidesoftware.co.za>, Sheldon Hearn wrote: > > When the kernel is built as kernel.debug, why is it passed through > objcopy --strip-debug before being installed, instead of being passed > through strip? If you strip all of the symbols from the kernel then nothing that uses libkvm will work. > Background: I recently found that the Handbook instructions for > "Debugging Loadable Modules Using GDB" is mostly useless for post-mortem > crash dump analysis, because buildkernel doesn't build modules with > debugging support, even when CONFIGARGS=-g. > > The attached patch (for the i386 only) fixes this so that, if kernel.debug > is built, foo.ko.debug etc. are built. For each foo.ko.debug, we > produce foo.ko with objcopy --strip-debug and install foo.ko. > > What I'm unsure of is why it's worth going to all this trouble. > > Why not simply build all the modules with debugging support compiled in > (assuming debugging support was requested for the kernel), and strip > them at install time (install -s)? I don't understand what this has to do with how the kernel is stripped. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14:51:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 26A1D37B401 for ; Sun, 29 Jul 2001 14:51:40 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15QyU2-0000bn-00; Sun, 29 Jul 2001 23:52:22 +0200 From: Sheldon Hearn To: John Polstra Cc: hackers@freebsd.org Subject: Re: Why objcopy --strip-debug instead of strip? In-reply-to: Your message of "Sun, 29 Jul 2001 14:26:41 MST." <200107292126.f6TLQfa15379@vashon.polstra.com> Date: Sun, 29 Jul 2001 23:52:22 +0200 Message-ID: <2342.996443542@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 29 Jul 2001 14:26:41 MST, John Polstra wrote: > I don't understand what this has to do with how the kernel is > stripped. The current modules build attached to buildkernel doesn't generate modules with debugging symbols, regardless of whether CONFIGARGS='-g' was specified. I want to fix that. The patches I sent are working well for me at the moment. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 14:59:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-149.dsl.lsan03.pacbell.net [64.169.104.149]) by hub.freebsd.org (Postfix) with ESMTP id 4B4E937B401; Sun, 29 Jul 2001 14:59:18 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6BBD966B25; Sun, 29 Jul 2001 14:59:17 -0700 (PDT) Date: Sun, 29 Jul 2001 14:59:17 -0700 From: Kris Kennaway To: David O'Brien Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [PATCH] reduce text(code) size and improve clarity of pkg_add Message-ID: <20010729145916.D94563@xor.obsecurity.org> References: <20010727214412.A91434@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="IMjqdzrDRly81ofr" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010727214412.A91434@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Fri, Jul 27, 2001 at 09:44:12PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --IMjqdzrDRly81ofr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 27, 2001 at 09:44:12PM -0700, David O'Brien wrote: > I'd like to apply this patch to pkg_add which reduces the amount of code > the compiler generates, and improves the clarity of the code. >=20 > 1. s_strl* is obvious some form of "safe" strl{cpy,cat}. But *WHAT* > does it make "safe"? Isn't obvious w/o having to track down the > s_strl{cat,cpy} function definitions. >=20 > 2. The current code has more function call overhead than is needed. And > it reduces the size of the basic block for the optimizer to work on. > It also potentially has cache miss penalties. I now think these should be macros which do the if() test and the errx. Kris --IMjqdzrDRly81ofr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7ZIc0Wry0BWjoQKURAqy2AKDGw4Aokoqb+9GwJIBvtRTwKSA/lgCgztHu hz8Ki8NtiKQ+3wDb015cJiI= =w8eC -----END PGP SIGNATURE----- --IMjqdzrDRly81ofr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 16:39:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id D1FBE37B401; Sun, 29 Jul 2001 16:39:28 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id TAA28466; Sun, 29 Jul 2001 19:38:45 -0400 (EDT) Date: Sun, 29 Jul 2001 19:38:45 -0400 (EDT) From: Daniel Eischen To: "Louis A. Mamakos" Cc: tlambert2@mindspring.com, y-carden@uniandes.edu.co, jlemon@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: KNOTE() In-Reply-To: <200107292041.f6TKfxn41502@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 29 Jul 2001, Louis A. Mamakos wrote: > > Daniel Eischen wrote: > > > Why are you trying to push so much into the kernel? > > > Rethink the problem you are trying to solve. > > > > See his other posting; he's living inside the constraints > > of an existing library and API. > > Yes, except these are problems of his own making because the library > and API were originally user-mode code and not in the kernel. Somewhere > along the way a decision was made to push that function into the kernel, > and all these bizzaro "problems" of calling back user-mode code from > the kernel, etc. follow from that decision. Yeah, exactly. FWIW, I think he really wants timer_create() and friends. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 16:46:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (softweyr.com [208.247.99.111]) by hub.freebsd.org (Postfix) with ESMTP id D145437B401 for ; Sun, 29 Jul 2001 16:46:11 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from localhost.softweyr.com ([127.0.0.1] helo=softweyr.com ident=e09f9931b85b1fe9bad610d77d0c2c4e) by softweyr.com with esmtp (Exim 3.16 #1) id 15R0N3-0000dd-00; Sun, 29 Jul 2001 17:53:17 -0600 Message-ID: <3B64A1EC.1A4CF3C3@softweyr.com> Date: Sun, 29 Jul 2001 17:53:16 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Ron Chen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Fwd: Sun Grid Engine 5.2.3 Available. Now Open Source References: <20010728190909.60077.qmail@web14703.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ron Chen wrote: > > It's weekend, it's time for hacking. > > I downloaded the SGE 5.3 source code. Played with it > for a while, the 50+MB of source does have some > goodies, it is not as simple as NQS: > > 1. Master fail-over: you can set up several shadow > masters in one cluster. When the qmaster fails, one of > the shadow masters will take over. > > 2. Project base fairshare: you can have project A > using 30% of your cluster resource, project B using > the other 30%, and project C using the rest. > > 3. User base fairshare: same, but users instead of > projects. > > 4. deadline scheduling > > 5. distributed make: qmake > > 6. security: krb, dce, ssl, etc > > 7. NT execution engine > > 8. Java interface > > 9. COBRA interface > > 10. Perl interface > > 11. preemptive seheduling > > 12. job scheduler: calender based job scheduler > > 13. Parallel interface > > 14. checkpointing interface > > I am still hacking. There are more interesting > features that are in the source. Oooh, sounds good. Will we have a FreeBSD port kit when you're done? qmake sounds quite interesting. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 17: 2:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from k7.locore.ca (k7.locore.ca [198.96.117.169]) by hub.freebsd.org (Postfix) with ESMTP id 9407837B401; Sun, 29 Jul 2001 17:02:45 -0700 (PDT) (envelope-from jake@k7.locore.ca) Received: from k7.locore.ca (localhost [127.0.0.1]) by k7.locore.ca (8.11.4/8.11.4) with ESMTP id f6U0Ac366279; Sun, 29 Jul 2001 20:10:39 -0400 (EDT) (envelope-from jake@k7.locore.ca) Message-Id: <200107300010.f6U0Ac366279@k7.locore.ca> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Ade Lovett Cc: hackers@FreeBSD.org, sparc@FreeBSD.org Subject: Re: review: sparc64 port commit candidate In-Reply-To: Message from Ade Lovett of "Sun, 29 Jul 2001 18:19:47 CDT." <20010729181947.F92318@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Jul 2001 20:10:38 -0400 From: Jake Burkholder Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > On Tue, Jul 24, 2001 at 01:41:24AM -0400, Jake Burkholder wrote: > > and here is a dump of how far it gets: > > http://people.freebsd.org/~jake/tip.record > > One thing I did notice here was the OpenBoot prom version (3.15) which, > to be blunt, is something Noah had installed on his navigation systems. > > OpenBoot 3.29 is the latest, and did solve a few weird booting issues > for NetBSD/sparc64 for me. Solaris patch number is 106121-14 (which > needs Solaris to install). I can provide if necessary. Hmm. Its not my machine, so I'm not in a position to upgrade it, but thanks for the info. > > > > This isn't really ready for mass consumption yet, as there's no > > official loader and you need to build a cross compiler yourself, > > but its a start. > > On the subject of cross-compilers, I've been looking at the various > toolchains that NetBSD/sparc64, which are all 2.95.* based, and seem > to have major issues with C++ -- perhaps such a port (which I can > certainly help with) should be based around 3.0? I may be wrong, but its my understanding that sparc64 is not officially supported in 3.0. The files are there but I've had no luck building it so far; we may have to wait for 3.1 :-/ > > Cool work, BTW.. depending on RealJob constraints, I may be able > to ship you a U5 so that you can work on it locally if you're > interested. Semi-permanent loan until it boots single user :) That would be excellent. There's just enough lag to the box I work on now to be highly annoying (almost the entire port was written over ssh). There are quite a few ultra 10s available locally on ebay which I've been looking at, I just haven't been at my current job long enough to save up. > > And again, once things have settled down in RealWorld, I'll should > very well be able to organize remote access to E450's and E4500's > (got a couple of them lying around spare -- too big to be shipped). That would also be excellent. I wouldn't want to try to ship one to Canada from the US :). Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jul 29 17: 3:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id D1FD737B403 for ; Sun, 29 Jul 2001 17:03:41 -0700 (PDT) (envelope-from adsharma@sharmas.dhs.org) Received: by sharmas.dhs.org (Postfix, from userid 500) id E19A75E2C8; Sun, 29 Jul 2001 17:04:02 -0700 (PDT) Date: Sun, 29 Jul 2001 17:04:02 -0700 From: Arun Sharma To: Daniel Eischen Cc: hackers@FreeBSD.ORG Subject: Re: libc_r, signals and modifying sigcontext Message-ID: <20010729170402.A18538@sharmas.dhs.org> References: <20010729011656.A11337@sharmas.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: ; from eischen@vigrid.com on Sun, Jul 29, 2001 at 09:48:30AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 29, 2001 at 09:48:30AM -0400, Daniel Eischen wrote: > Can you breakpoint or add a print statement to see if the thread > chosen to handle the signal is the current thread (_thread_run > == thread) in the patched section below? Yes, the following condition was true according to my printfs: _thread_run == thread -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 0:34:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AA20A37B401 for ; Mon, 30 Jul 2001 00:34:13 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6U7YCF82129; Mon, 30 Jul 2001 01:34:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6U7YCw34002; Mon, 30 Jul 2001 01:34:12 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107300734.f6U7YCw34002@harmony.village.org> To: walter@pelissero.org Subject: Re: PCMCIA hot swap Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 29 Jul 2001 14:42:44 BST." <200107291342.f6TDgiq08161@pelissero.org> References: <200107291342.f6TDgiq08161@pelissero.org> Date: Mon, 30 Jul 2001 01:34:12 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200107291342.f6TDgiq08161@pelissero.org> "Walter C. Pelissero" writes: : Having recently upgraded from 4.0 to 4.3 on my laptop I've noticed : that PCMCIA insertion and extraction doesn't work as it used to. It should. : The system (Vaio PCG-XG9) just freezes. Some time I'm able to rescue : the situation inserting and extracting several times the offending : card. Some time I have to power off and reboot. Ah. We switched from assigning an interrupt to the card status change interrupts (aka management interrupts) to using polling mode. Unfortunately, this hangs many recent sony vaio systems. You will need to assign an irq to the pcic device. I think it is 11, but I'm not totally sure. : My question is: "Has the hot swap feature been somehow dropped from : the PCCARD code?" No. Just a simple mistake on our part that requires a config change on yours. Wanrer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 6:41: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from murphys-outbound.services.quay.plus.net (unknown [212.159.14.225]) by hub.freebsd.org (Postfix) with SMTP id 896B237B401 for ; Mon, 30 Jul 2001 06:41:05 -0700 (PDT) (envelope-from wcp@pelissero.org) Received: (qmail 28614 invoked from network); 30 Jul 2001 13:40:56 -0000 Received: from unknown (HELO daemon.lpds.sublink.org) (212.159.37.242) by murphys with SMTP; 30 Jul 2001 13:40:56 -0000 Received: from pelissero.org (hyde.lpds.sublink.org [10.0.0.2]) by daemon.lpds.sublink.org (8.11.4/8.9.3) with ESMTP id f6UDFbA32581 for ; Mon, 30 Jul 2001 14:15:37 +0100 (BST) (envelope-from wcp@pelissero.org) Received: (from wcp@localhost) by pelissero.org (8.11.4/8.9.3) id f6UDFao09571; Mon, 30 Jul 2001 14:15:36 +0100 (BST) (envelope-from wcp) From: "Walter C. Pelissero" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15205.24056.495297.830771@hyde.lpds.sublink.org> Date: Mon, 30 Jul 2001 14:15:36 +0100 To: freebsd-hackers@FreeBSD.ORG Subject: Re: PCMCIA hot swap In-Reply-To: <200107300734.f6U7YCw34002@harmony.village.org> References: <200107291342.f6TDgiq08161@pelissero.org> <200107300734.f6U7YCw34002@harmony.village.org> X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid Reply-To: walter@pelissero.org X-Attribution: WP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As suggested it was a problem with the new polling mode. Assigning an interrupt to the pcic0 controller solved the problem. Thanks to Warner Losh and Ian Dowse. -- walter pelissero http://www.pelissero.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 6:45:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dominozh.minick.ch (unknown [62.65.140.70]) by hub.freebsd.org (Postfix) with ESMTP id 03F3137B401 for ; Mon, 30 Jul 2001 06:45:28 -0700 (PDT) (envelope-from alessandro.magnani@distefora.com) Subject: Making RXTX v.1.5.4 compile with linux-jdk1.3.1 To: FreeBSD-hackers@freebsd.org X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: From: alessandro.magnani@distefora.com Date: Mon, 30 Jul 2001 15:51:33 +0200 X-MIMETrack: Serialize by Router on dominozh/zuerich/minick(Release 5.0.4 |June 8, 2000) at 07/30/2001 03:51:36 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello- Has anyone succeded in compiling the RXTX package v1.5.4 with the linux-jdk1.3.1 installed on a FreeBSD 4.3-Stable system ? This is the output I receive, after running ./configure --- snip --- adjusted java.home is /usr/local/linux-jdk1.3.1 checking os.name Linux checking os.arch i386 checking java.vendor Sun Microsystems Inc. checking java.version 1.3.1 checking os.version 4.3-STABLE ------------------------------------------------------ WARNING: A comm.jar file is alread installed make install will overwrite it /usr/local/linux-jdk1.3.1/jre/lib/ext/comm.jar ------------------------------------------------------ conftest.c:2: linux/version.h: No such file or directory ./configure: ./conftest: not found test: !=: argument expected conftest.c:1: features.h: No such file or directory ./configure: ./conftest: not found test: 2: unexpected operator updating cache ./config.cache creating ./config.status creating Makefile creating config.h config.h is unchanged --- snip --- Of course, after this, a gmake fails with following errors: --- snip --- gcc -I /usr/home/bmc/tini/tmp/rxtx-1.5-4 -I i386-unknown-freebsdelf4.3 -I . -I /usr/local/linux-jdk1.3.1/include -I /usr/local/linux-jdk1.3.1/./include/linux/ -g -O2 -D_BSD_SOURCE -DLOCKFILES -c .././src/ParallelImp.c -fPIC -DPIC -o /usr/home/bmc/tini/tmp/rxtx-1.5-4/i386-unknown-freebsdelf4.3/ParallelImp.lo .././src/ParallelImp.c:67: machine/lpt.h: No such file or directory .././src/ParallelImp.c:580: #error Trent never looked at this. .././src/ParallelImp.c:610: #error Trent never looked at this. rm -fr .libs/libParallel.la .libs/libParallel.* .libs/libParallel.* (cd /usr/home/bmc/tini/tmp/rxtx-1.5-4/i386-unknown-freebsdelf4.3 && ln -s ParallelImp.lo ParallelImp.o) ln: ParallelImp.o: File exists gmake: *** [i386-unknown-freebsdelf4.3/libParallel.la] Error 1 --- snip --- Any help is greatly appreciated. regards, Magnani A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 7:15:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.t0.or.at (ns1.t0.or.at [62.116.70.34]) by hub.freebsd.org (Postfix) with ESMTP id 11CAF37B403 for ; Mon, 30 Jul 2001 07:15:23 -0700 (PDT) (envelope-from mic@mail.t0.or.at) Received: (from mic@localhost) by mail.t0.or.at (8.11.4/8.11.4) id f6UEFrK38987; Mon, 30 Jul 2001 16:15:53 +0200 (CEST) Date: Mon, 30 Jul 2001 16:15:53 +0200 From: Michael Dosser To: "Walter C. Pelissero" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCMCIA hot swap Message-ID: <20010730161553.A38095@t0.or.at> References: <200107291342.f6TDgiq08161@pelissero.org> <200107300734.f6U7YCw34002@harmony.village.org> <15205.24056.495297.830771@hyde.lpds.sublink.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15205.24056.495297.830771@hyde.lpds.sublink.org>; from walter@pelissero.org on Mon, Jul 30, 2001 at 02:15:36PM +0100 Organization: Public Netbase X-Url: X-sig-random-gen: http://cfml.sourceforge.net/perl/chsig.tar.gz Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Walter C. Pelissero [010730 15:15]: > As suggested it was a problem with the new polling mode. > Assigning an interrupt to the pcic0 controller solved the problem. > Thanks to Warner Losh and Ian Dowse. Worked for my picturebook as well. Even the problem with [(null)] [(null)] on reconnecting my 3Com OfficeConnect 572BT is now solved. Thanks a lot,mic -- /"\ ASCII Ribbon Campaign | \ / Against HTML Mail/RTF in e-mail | Michael Dosser X NO Word docs in e-mail | http://org.netbase.org / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 7:59:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from blackcomb.panasas.com (gw2.panasas.com [65.194.124.178]) by hub.freebsd.org (Postfix) with ESMTP id 335DE37B401 for ; Mon, 30 Jul 2001 07:59:21 -0700 (PDT) (envelope-from rgrover@panasas.com) Received: from tiltill.panasas.com (IDENT:rgrover@tiltill.panasas.com [172.17.132.191]) by blackcomb.panasas.com (8.9.3/8.9.3) with SMTP id KAA09858 for ; Mon, 30 Jul 2001 10:59:19 -0400 From: Rohit Grover Organization: Panasas Inc. To: freebsd-hackers@freebsd.org Subject: messed up /etc/rc.conf Date: Mon, 30 Jul 2001 07:55:44 -0700 X-Mailer: KMail [version 1.0.29] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <01073007591802.01042@tiltill.panasas.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I made a mistake while modifying my /etc/rc.conf. I forgot to put the terminating quote for a string. Now, my machine fails to boot correctly. Upon boot, it gives me an option to launch a shell to correct the problem. Interestingly, / is mounted as read-only and so I cannot correct /etc/rc.conf. Please help. regards, Rohit Grover. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8: 6:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from thought.adamantsys.com (w120.z064002057.sjc-ca.dsl.cnc.net [64.2.57.120]) by hub.freebsd.org (Postfix) with ESMTP id 6756237B405 for ; Mon, 30 Jul 2001 08:06:23 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost.adamantsys.com [127.0.0.1]) by thought.adamantsys.com (8.11.4/8.11.2) with ESMTP id f6UF6H974530; Mon, 30 Jul 2001 08:06:18 -0700 (PDT) (envelope-from brian@CSUA.Berkeley.EDU) Date: Mon, 30 Jul 2001 08:06:17 -0700 (PDT) From: "Brian W. Buchanan" X-X-Sender: To: Rohit Grover Cc: Subject: Re: messed up /etc/rc.conf In-Reply-To: <01073007591802.01042@tiltill.panasas.com> Message-ID: <20010730080426.U66530-100000@thought.adamantsys.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rohit, "mount -a" will mount your filesystems read-write. Or just "mount /" to remount the / filesystem read-write, if you prefer. In the future, please send questions like this to freebsd-questions@freebsd.org. Brian -- Brian Buchanan brian@CSUA.Berkeley.EDU -------------------------------------------------------------------------- FreeBSD - The Power to Serve! http://www.freebsd.org On Mon, 30 Jul 2001, Rohit Grover wrote: > Hello, > > I made a mistake while modifying my /etc/rc.conf. I forgot to > put the terminating quote for a string. Now, my machine fails to boot > correctly. Upon boot, it gives me an option to launch a shell to > correct the problem. Interestingly, / is mounted as read-only and so > I cannot correct /etc/rc.conf. Please help. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8: 7:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix.sekt7.org (209-6-248-16.c3-0.lex-ubr1.sbo-lex.ma.cable.rcn.com [209.6.248.16]) by hub.freebsd.org (Postfix) with ESMTP id F060F37B401 for ; Mon, 30 Jul 2001 08:07:38 -0700 (PDT) (envelope-from ems@open-root.org) Received: from postfix (unknown [169.69.6.38]) by postfix.sekt7.org (Postfix) with SMTP id 81A733A07A; Mon, 30 Jul 2001 15:07:51 +0000 (GMT) From: Evan Sarmiento To: rgrover@panasas.com Cc: freebsd-hackers@freebsd.org In-reply-to: <01073007591802.01042@tiltill.panasas.com> (message from Rohit Grover on Mon, 30 Jul 2001 07:55:44 -0700) Subject: Re: messed up /etc/rc.conf Message-Id: <20010730150751.81A733A07A@postfix.sekt7.org> Date: Mon, 30 Jul 2001 15:07:51 +0000 (GMT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I don't think this is the right mailing list for your question, direct it to -questions, But, here's how to fix it anyway: 1. mount -ahw >Delivered-To: kaworu@sektor7.ath.cx >Delivered-To: freebsd-hackers@freebsd.org >From: Rohit Grover >Organization: Panasas Inc. >Date: Mon, 30 Jul 2001 07:55:44 -0700 >X-Mailer: KMail [version 1.0.29] >Content-Type: text/plain >MIME-Version: 1.0 >Content-Transfer-Encoding: 8bit >Sender: owner-freebsd-hackers@FreeBSD.ORG >List-ID: >List-Archive: (Web Archive) >List-Help: (List Instructions) >List-Subscribe: >List-Unsubscribe: >X-Loop: FreeBSD.ORG >Precedence: bulk > >Hello, > >I made a mistake while modifying my /etc/rc.conf. I forgot to >put the terminating quote for a string. Now, my machine fails to boot >correctly. Upon boot, it gives me an option to launch a shell to >correct the problem. Interestingly, / is mounted as read-only and so >I cannot correct /etc/rc.conf. Please help. > >regards, >Rohit Grover. > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > -- ----------------------------------- Evan Sarmiento | www.open-root.org ems@sekt7.org | www.sekt7.org/~ems/ ----------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8:16:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mydomain.com (1Cust57.tnt2.cph3.da.uu.net [213.116.21.57]) by hub.freebsd.org (Postfix) with ESMTP id 7186937B40A; Mon, 30 Jul 2001 08:16:38 -0700 (PDT) (envelope-from xxxsensation@funkytimes.com) Date: Mon, 30 Jul 2001 17:16:37 +0100 From: XXXSENSATION To: XXXSENSATION@FreeBSD.ORG Subject: THE GREATEST NO.1 SHOWS ON THE NET ! Message-Id: <20010730151638.7186937B40A@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Ladies & Gentlemen, Welcome to the GREATEST SEX SHOW on the ENTIRE NET ! We now offer you to ENTER to worldŽs No.1 voted SEX-SERVER on the WEB ! By far the largest and most incredible content of LIVE SEX is now served to users WORLDWIDE! EVERYTHING is offered 100% ANONOMOUSLY & you donŽt need to sign-up or have a creditcard ... The way it should be ! PLUGIN RIGHT HERE AT: http://siam.to/worldclass ... If this Site does not open properly ... please try http://cyberu.to/worldclass Or this one, if you just love true LESBIAN SEX, CHAT and MORE from Sunny Ibiza in Spain: http://siam.to/classbabes ... If this Site does not open properly ... please try http://cyberu.to/hotbabes and get access to something you with guarantee NEVER have seen before ! Yours truly, XXXSENSATION Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8:17:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mydomain.com (1Cust57.tnt2.cph3.da.uu.net [213.116.21.57]) by hub.freebsd.org (Postfix) with ESMTP id 6E95737B435; Mon, 30 Jul 2001 08:16:58 -0700 (PDT) (envelope-from xxxsensation@funkytimes.com) Date: Mon, 30 Jul 2001 17:16:55 +0100 From: XXXSENSATION To: XXXSENSATION@FreeBSD.ORG Subject: THE GREATEST NO.1 SHOWS ON THE NET ! Message-Id: <20010730151658.6E95737B435@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Ladies & Gentlemen, Welcome to the GREATEST SEX SHOW on the ENTIRE NET ! We now offer you to ENTER to worldŽs No.1 voted SEX-SERVER on the WEB ! By far the largest and most incredible content of LIVE SEX is now served to users WORLDWIDE! EVERYTHING is offered 100% ANONOMOUSLY & you donŽt need to sign-up or have a creditcard ... The way it should be ! PLUGIN RIGHT HERE AT: http://siam.to/worldclass ... If this Site does not open properly ... please try http://cyberu.to/worldclass Or this one, if you just love true LESBIAN SEX, CHAT and MORE from Sunny Ibiza in Spain: http://siam.to/classbabes ... If this Site does not open properly ... please try http://cyberu.to/hotbabes and get access to something you with guarantee NEVER have seen before ! Yours truly, XXXSENSATION Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8:18: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 4DA1937B401 for ; Mon, 30 Jul 2001 08:17:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6UFHoF83676; Mon, 30 Jul 2001 09:17:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6UFHow36692; Mon, 30 Jul 2001 09:17:50 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107301517.f6UFHow36692@harmony.village.org> To: Rohit Grover Subject: Re: messed up /etc/rc.conf Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 30 Jul 2001 07:55:44 PDT." <01073007591802.01042@tiltill.panasas.com> References: <01073007591802.01042@tiltill.panasas.com> Date: Mon, 30 Jul 2001 09:17:50 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <01073007591802.01042@tiltill.panasas.com> Rohit Grover writes: : I made a mistake while modifying my /etc/rc.conf. I forgot to : put the terminating quote for a string. Now, my machine fails to boot : correctly. Upon boot, it gives me an option to launch a shell to : correct the problem. Interestingly, / is mounted as read-only and so : I cannot correct /etc/rc.conf. Please help. Your best bet is to boot singlue user, then do fsck -p /; mount -uw /; mv /etc/rc.conf /etcrc.conf-; reboot; correct the problem; reboot Or fsck -p / mount -uw / fsck -p /var mount /var fcsk -p /usr mount /usr vi /etc/rc.copnf Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8:35:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from greatbabes.gz.ee (adsl2145.estpak.ee [195.250.169.246]) by hub.freebsd.org (Postfix) with SMTP id 749AF37B403 for ; Mon, 30 Jul 2001 08:35:11 -0700 (PDT) (envelope-from free@greatbabes.gz.ee) From: free@greatbabes.gz.ee To: freebsd-hackers@FreeBSD.ORG Subject: Special Deal This Week Only !!! Date: 30 Jul 2001 13:52:10 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_e9eBMfqU_oy1iNE37_MA" Message-Id: <20010730153511.749AF37B403@hub.freebsd.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------=_e9eBMfqU_oy1iNE37_MA Content-Type: text/plain Content-Transfer-Encoding: 8bit -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- (This safeguard is not inserted when using the registered version) -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- (This safeguard is not inserted when using the registered version) -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- -------------------------------------------------------------------- ------=_e9eBMfqU_oy1iNE37_MA Content-Type: text/html Content-Transfer-Encoding: 8bit Get Acceess to 10 Sites For $1.99 Only !!!

Do not miss out on the opportunity to get a full week of access to 8 websites for the amazing low price of only $1.99,
including Big Tit Fantasies - The Ultimate Tit Lover's Paradise!
You could search the internet for months and you wouldn't find a better deal anywhere!

$1.99 SPECIAL DEAL
THIS WEEK ONLY!

 

 

8 Sites for the Price of One!
Do you really think you're gonna find a better deal somewhere else!?
Click here now and stop wasting valuable jerk-off time!

Powered by GREAT BABES - the best free pics here.


FastCounter by bCentral

------=_e9eBMfqU_oy1iNE37_MA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 8:46:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 192BC37B403; Mon, 30 Jul 2001 08:46:51 -0700 (PDT) (envelope-from jkh@freebsd.org) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.4/8.11.4) with ESMTP id f6UFk1t32478; Mon, 30 Jul 2001 08:46:02 -0700 (PDT) (envelope-from jkh@freebsd.org) To: obrien@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] reduce text(code) size and improve clarity of pkg_add In-Reply-To: <20010727214412.A91434@dragon.nuxi.com> References: <20010727214412.A91434@dragon.nuxi.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010730084601N.jkh@freebsd.org> Date: Mon, 30 Jul 2001 08:46:01 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 19 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "David O'Brien" Subject: [PATCH] reduce text(code) size and improve clarity of pkg_add Date: Fri, 27 Jul 2001 21:44:12 -0700 > I'd like to apply this patch to pkg_add which reduces the amount of code > the compiler generates, and improves the clarity of the code. As the original author of this code, I'll just say that I favor clarity over speed. As long as you can achieve reasonable security with whatever approach is used, I vote for the shortest one which has the least number of private or otherwise "lesser known" functions since that also obscures clarity. Everybody knows [or should] what strncpy() and friends do and the intention of code which uses them is therefore pretty clear. If we're lacking the appropriate functions for doing safe string copies (which I find hard to believe) then we ought to be arguing for extending the appropriate base library, not adding them as private functions to pkg_install. My two cents. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 9: 1: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id CCF5537B40B for ; Mon, 30 Jul 2001 09:00:47 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.4/8.11.1) id f6UG0aN59233; Mon, 30 Jul 2001 09:00:36 -0700 (PDT) (envelope-from obrien) Date: Mon, 30 Jul 2001 09:00:36 -0700 From: "David O'Brien" To: Kris Kennaway Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [PATCH] reduce text(code) size and improve clarity of pkg_add Message-ID: <20010730090036.A59209@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20010727214412.A91434@dragon.nuxi.com> <20010729145916.D94563@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010729145916.D94563@xor.obsecurity.org>; from kris@obsecurity.org on Sun, Jul 29, 2001 at 02:59:17PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 29, 2001 at 02:59:17PM -0700, Kris Kennaway wrote: > > 1. s_strl* is obvious some form of "safe" strl{cpy,cat}. But *WHAT* > > does it make "safe"? Isn't obvious w/o having to track down the > > s_strl{cat,cpy} function definitions. > > I now think these should be macros which do the if() test and the errx. Can you post a proposed diff? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 9: 4:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id D6ACE37B401 for ; Mon, 30 Jul 2001 09:04:09 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.1) with ESMTP id f6UG47q57227; Mon, 30 Jul 2001 09:04:07 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.3/8.11.0) id f6UG46q16768; Mon, 30 Jul 2001 09:04:06 -0700 (PDT) (envelope-from jdp) Date: Mon, 30 Jul 2001 09:04:06 -0700 (PDT) Message-Id: <200107301604.f6UG46q16768@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: sheldonh@starjuice.net Subject: Re: Why objcopy --strip-debug instead of strip? In-Reply-To: <2342.996443542@axl.seasidesoftware.co.za> References: <2342.996443542@axl.seasidesoftware.co.za> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <2342.996443542@axl.seasidesoftware.co.za>, Sheldon Hearn wrote: > On Sun, 29 Jul 2001 14:26:41 MST, John Polstra wrote: > > > I don't understand what this has to do with how the kernel is > > stripped. > > The current modules build attached to buildkernel doesn't generate > modules with debugging symbols, regardless of whether CONFIGARGS='-g' > was specified. I want to fix that. OK, sounds good to me. In your private mail you seemed to be asking why only the debugging symbols are stripped from the kernel instead of stripping all symbols. I think the modules should be stripped the same way as the kernel: with --strip-debug. That way you end up with the same set of symbols as if they were statically linked into the kernel. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 9: 4:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 06F1837B401; Mon, 30 Jul 2001 09:04:47 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA16831; Mon, 30 Jul 2001 09:04:46 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010727214412.A91434@dragon.nuxi.com> Date: Mon, 30 Jul 2001 09:04:47 -0700 (PDT) From: John Baldwin To: "David O'Brien" Subject: RE: [PATCH] reduce text(code) size and improve clarity of pkg_ad Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 28-Jul-01 David O'Brien wrote: > I'd like to apply this patch to pkg_add which reduces the amount of code > the compiler generates, and improves the clarity of the code. > > 1. s_strl* is obvious some form of "safe" strl{cpy,cat}. But *WHAT* > does it make "safe"? Isn't obvious w/o having to track down the > s_strl{cat,cpy} function definitions. > > 2. The current code has more function call overhead than is needed. And > it reduces the size of the basic block for the optimizer to work on. > It also potentially has cache miss penalties. static __inline int s_strlcpy(char *dst, const char *src, size_t size) { return (strlcpy(dst, src, size) >= size); } and the same for s_strlcat() is a much shorter patch :) while still being slightly more readable. Not to mention your patch broke one case by using '>' instead of '>=' for the test, while just making the functions inline wouldn't have this problem. :) > - if (s_strlcpy(FirstPen, optarg, sizeof(FirstPen))) > + if (strlcpy(FirstPen, optarg, sizeof(FirstPen)) > sizeof(FirstPen)) Should be >=. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Jul 30 9:24:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id AB25837B401; Mon, 30 Jul 2001 09:24:22 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.4/8.11.1) id f6UGOMP59589; Mon, 30 Jul 2001 09:24:22 -0700 (PDT) (envelope-from obrien) Date: Mon, 30 Jul 2001 09:24:22 -0700 From: "David O'Brien" To: Jordan Hubbard Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] reduce text(code) size and improve clarity of pkg_add Message-ID: <20010730092422.B59209@dragon.nuxi.com> Reply-To: freebsd-hackers@freebsd.org References: <20010727214412.A91434@dragon.nuxi.com> <20010730084601N.jkh@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730084601N.jkh@freebsd.org>; from jkh@freebsd.org on Mon, Jul 30, 2001 at 08:46:01AM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 30, 2001 at 08:46:01AM -0700, Jordan Hubbard wrote: > From: "David O'Brien" > Subject: [PATCH] reduce text(code) size and improve clarity of pkg_add > Date: Fri, 27 Jul 2001 21:44:12 -0700 > > > I'd like to apply this patch to pkg_add which reduces the amount of code > > the compiler generates, and improves the clarity of the code. > > As the original author of this code, I'll just say that I favor > clarity over speed. Actually, it was the clarity issue that started this for me. When I saw s_strl*, I had to think "OK, what's *this* version of safe strl* doing?". A "grep s_strl *" didn't answer my question, so I had to go grepping over a larger area than just `.'. It was only after finding the definitions of s_strl* that I felt the extra abstraction was not justified from either a clarity or speed/efficiency position. I have had four private response to this diff (no one wants to open themselves to being flamed): 1. s_strl*() is an oversimplification. I agree with this diff. 2. if "size" ended up being a complex expression, I would rather the s_ version, but it wasn't complex 3. the extra layering is not warranted, I agree with the patch 4. in this specific case, it looked like Kris had some other agenda [referring Kris's objection to my original commit of this patch] And now one public one :-) 5. > I vote for the shortest one which has > the least number of private or otherwise "lesser known" functions > since that also obscures clarity. -- -- David (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 Mon Jul 30 9:44:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 8C33D37B401 for ; Mon, 30 Jul 2001 09:44:18 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15RGAL-0000Rt-00; Mon, 30 Jul 2001 18:45:13 +0200 From: Sheldon Hearn To: John Polstra Cc: hackers@freebsd.org Subject: Re: Why objcopy --strip-debug instead of strip? In-reply-to: Your message of "Mon, 30 Jul 2001 09:04:06 MST." <200107301604.f6UG46q16768@vashon.polstra.com> Date: Mon, 30 Jul 2001 18:45:13 +0200 Message-ID: <1728.996511513@axl.seasidesoftware.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 30 Jul 2001 09:04:06 MST, John Polstra wrote: > OK, sounds good to me. In your private mail you seemed to be asking > why only the debugging symbols are stripped from the kernel instead > of stripping all symbols. In that case, any objections to the patch I posted? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 11:50:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web12807.mail.yahoo.com (web12807.mail.yahoo.com [216.136.174.42]) by hub.freebsd.org (Postfix) with SMTP id 7A60A37B401 for ; Mon, 30 Jul 2001 11:50:18 -0700 (PDT) (envelope-from zaunere@yahoo.com) Message-ID: <20010730185018.10922.qmail@web12807.mail.yahoo.com> Received: from [128.122.155.151] by web12807.mail.yahoo.com; Mon, 30 Jul 2001 11:50:18 PDT Date: Mon, 30 Jul 2001 11:50:18 -0700 (PDT) From: Hans Zaunere Subject: Accessing /dev/klog and similar To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I'm looking to access kernel messages directly from the kernel, and not through syslog if I can help it. When I try to open("/dev/klog", O_RDONLY); I get the error "Device busy". How can I open this file? Or are there any other ways of getting at this data? When I try to open /dev/log or /var/run/log I get the error "Operation not supported." Basically what I want to do is "intercept" kernel messages before they get to syslog, avoiding having to open the disk file that syslog writes to. Any ideas or help on how to do this would be great. Thank you, Hans zaunere@yahoo.com __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 12:46:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id C9AB737B401; Mon, 30 Jul 2001 12:46:06 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id MAA27832; Mon, 30 Jul 2001 12:46:05 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 30 Jul 2001 12:46:06 -0700 (PDT) From: John Baldwin To: hackers@FreeBSD.org Subject: PATCH: Make ast's loop Cc: bde@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a patch to close some races with receiving AST's while handling other AST's. Unfortunately due to my office being moved all my test machines are unavailable at the moment, so I'd like people to test it for me on SMP machines and alpha. I'll include it below, but my mailer may mangle it, so here is a URL as well: http://www.FreeBSD.org/~jhb/patches/ast.patch Index: kern/subr_trap.c =================================================================== RCS file: /usr/cvs/src/sys/kern/subr_trap.c,v retrieving revision 1.196 diff -u -r1.196 subr_trap.c --- kern/subr_trap.c 2001/07/04 15:36:30 1.196 +++ kern/subr_trap.c 2001/07/17 22:54:42 @@ -72,9 +72,9 @@ while ((sig = CURSIG(p)) != 0) postsig(sig); mtx_unlock(&Giant); + PROC_UNLOCK(p); mtx_lock_spin(&sched_lock); - PROC_UNLOCK_NOSWITCH(p); p->p_pri.pri_level = p->p_pri.pri_user; if (resched_wanted(p)) { /* @@ -96,24 +96,22 @@ while ((sig = CURSIG(p)) != 0) postsig(sig); mtx_unlock(&Giant); - mtx_lock_spin(&sched_lock); - PROC_UNLOCK_NOSWITCH(p); - } + PROC_UNLOCK(p); + } else + mtx_unlock_spin(&sched_lock); /* * Charge system time if profiling. */ - if (p->p_sflag & PS_PROFIL) { - mtx_unlock_spin(&sched_lock); + if (p->p_sflag & PS_PROFIL) addupc_task(p, TRAPF_PC(frame), (u_int)(p->p_sticks - oticks) * psratio); - } else - mtx_unlock_spin(&sched_lock); } /* * Process an asynchronous software trap. * This is relatively easy. + * This function will return with interrupts disabled. */ void ast(framep) @@ -121,67 +119,54 @@ { struct proc *p = CURPROC; u_quad_t sticks; + critical_t s; #if defined(DEV_NPX) && !defined(SMP) int ucode; #endif KASSERT(TRAPF_USERMODE(framep), ("ast in kernel mode")); - - /* - * We check for a pending AST here rather than in the assembly as - * acquiring and releasing mutexes in assembly is not fun. - */ - mtx_lock_spin(&sched_lock); - if (!(astpending(p) || resched_wanted(p))) { - mtx_unlock_spin(&sched_lock); - return; - } - - sticks = p->p_sticks; - p->p_frame = framep; - - astoff(p); - cnt.v_soft++; - mtx_intr_enable(&sched_lock); - if (p->p_sflag & PS_OWEUPC) { - p->p_sflag &= ~PS_OWEUPC; - mtx_unlock_spin(&sched_lock); - mtx_lock(&Giant); - addupc_task(p, p->p_stats->p_prof.pr_addr, - p->p_stats->p_prof.pr_ticks); + s = critical_enter(); + while (astpending(p) || resched_wanted(p)) { + critical_exit(s); + sticks = p->p_sticks; + p->p_frame = framep; mtx_lock_spin(&sched_lock); - } - if (p->p_sflag & PS_ALRMPEND) { - p->p_sflag &= ~PS_ALRMPEND; + astoff(p); + cnt.v_soft++; mtx_unlock_spin(&sched_lock); - PROC_LOCK(p); - psignal(p, SIGVTALRM); - PROC_UNLOCK(p); - mtx_lock_spin(&sched_lock); - } + if (p->p_sflag & PS_OWEUPC) + addupc_task(p, p->p_stats->p_prof.pr_addr, + p->p_stats->p_prof.pr_ticks); + if (p->p_sflag & PS_ALRMPEND) { + PROC_LOCK(p); + psignal(p, SIGVTALRM); + PROC_UNLOCK(p); + } #if defined(DEV_NPX) && !defined(SMP) - if (PCPU_GET(curpcb)->pcb_flags & PCB_NPXTRAP) { - PCPU_GET(curpcb)->pcb_flags &= ~PCB_NPXTRAP; - mtx_unlock_spin(&sched_lock); - ucode = npxtrap(); - if (ucode != -1) { - if (!mtx_owned(&Giant)) - mtx_lock(&Giant); - trapsignal(p, SIGFPE, ucode); + if (PCPU_GET(curpcb)->pcb_flags & PCB_NPXTRAP) { + ucode = npxtrap(); + if (ucode != -1) { + if (!mtx_owned(&Giant)) + mtx_lock(&Giant); + trapsignal(p, SIGFPE, ucode); + } + } +#endif + if (p->p_sflag & PS_PROFPEND) { + PROC_LOCK(p); + psignal(p, SIGPROF); + PROC_UNLOCK(p); } mtx_lock_spin(&sched_lock); - } + p->p_sflag &= ~(PS_OWEUPC | PS_ALRMPEND | PS_PROFPEND); +#if defined(DEV_NPX) && !defined(SMP) + PCPU_GET(curpcb)->pcb_flags &= ~PCB_NPXTRAP; #endif - if (p->p_sflag & PS_PROFPEND) { - p->p_sflag &= ~PS_PROFPEND; mtx_unlock_spin(&sched_lock); - PROC_LOCK(p); - psignal(p, SIGPROF); - PROC_UNLOCK(p); - } else - mtx_unlock_spin(&sched_lock); - userret(p, framep, sticks); + userret(p, framep, sticks); + s = critical_enter(); + } if (mtx_owned(&Giant)) mtx_unlock(&Giant); -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Jul 30 13:21:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from apocalypse.cdsnet.net (apocalypse.cdsnet.net [63.163.68.5]) by hub.freebsd.org (Postfix) with SMTP id 79F6337B401 for ; Mon, 30 Jul 2001 13:21:28 -0700 (PDT) (envelope-from mrcpu@apocalypse.cdsnet.net) Received: (qmail 74562 invoked by uid 29999); 30 Jul 2001 20:21:22 -0000 Date: Mon, 30 Jul 2001 13:21:22 -0700 From: Jaye Mathisen To: hackers@freebsd.org Subject: Softupdate gripe... Message-ID: <20010730132122.C548@apocalypse.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 2 500+GB FS's, both filled completely. Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/twed3d 524698116 524697730 386 100% /d/d0 /dev/twed4d 524698116 524502226 195890 100% /d/d1 newsfeed-inn# rm -f /d/d?/* newsfeed-inn# ls -lR /d total 4 drwxr-xr-x 2 news news 512 Jul 30 13:13 d0 drwxr-xr-x 2 news news 512 Jul 30 13:13 d1 /d/d0: /d/d1: newsfeed-inn# df ; sleep 30 ; df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/twed3d 524698116 524697730 386 100% /d/d0 /dev/twed4d 524698116 524446754 251362 100% /d/d1 Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/twed3d 524698116 524697730 386 100% /d/d0 /dev/twed4d 524698116 522361778 2336338 100% /d/d1 I realize that one of the issues with softupdates is that freed space isn't returned immediately, but *none* of the freed up space is being returned on d0, while d1 is seeing it. Seems like these should be more equal, otherwise, if you had a lot of SU mounted FS's, you could possibly deny service for a long time. It's been another minute now, and still no blocks freed up on /d/d0. newsfeed-inn# df ; sleep 120 ; df /dev/twed3d 524698116 524697730 386 100% /d/d0 /dev/twed4d 524698116 503964018 20734098 96% /d/d1 ... /dev/twed3d 524698116 524697730 386 100% /d/d0 /dev/twed4d 524698116 493186018 31512098 94% /d/d1 Seems like it should round-robin them or something. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 13:50:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 6B24B37B406 for ; Mon, 30 Jul 2001 13:50:08 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA30839; Mon, 30 Jul 2001 15:51:00 -0700 (PDT) Date: Mon, 30 Jul 2001 15:51:00 -0700 (PDT) From: Julian Elischer To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Softupdate gripe... In-Reply-To: <20010730132122.C548@apocalypse.cdsnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG are you sure you actually deleted anything in /d/d0? dot files? On Mon, 30 Jul 2001, Jaye Mathisen wrote: > > 2 500+GB FS's, both filled completely. > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 524502226 195890 100% /d/d1 > newsfeed-inn# rm -f /d/d?/* > newsfeed-inn# ls -lR /d > total 4 > drwxr-xr-x 2 news news 512 Jul 30 13:13 d0 > drwxr-xr-x 2 news news 512 Jul 30 13:13 d1 > > /d/d0: > > /d/d1: > newsfeed-inn# df ; sleep 30 ; df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 524446754 251362 100% /d/d1 > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 522361778 2336338 100% /d/d1 > > I realize that one of the issues with softupdates is that freed space isn't > returned immediately, but *none* of the freed up space is being returned on d0, > while d1 is seeing it. > > Seems like these should be more equal, otherwise, if you had a lot of SU mounted > FS's, you could possibly deny service for a long time. > > It's been another minute now, and still no blocks freed up on /d/d0. > newsfeed-inn# df ; sleep 120 ; df > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 503964018 20734098 96% /d/d1 > ... > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 493186018 31512098 94% /d/d1 > > Seems like it should round-robin them or something. As far as I know it should be.. Kirk may have other ideas though. > > 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 Mon Jul 30 14: 0:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 5A6A337B401 for ; Mon, 30 Jul 2001 14:00:53 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 5140581D05; Mon, 30 Jul 2001 16:00:43 -0500 (CDT) Date: Mon, 30 Jul 2001 16:00:43 -0500 From: Alfred Perlstein To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Softupdate gripe... Message-ID: <20010730160043.Q26571@elvis.mu.org> References: <20010730132122.C548@apocalypse.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730132122.C548@apocalypse.cdsnet.net>; from mrcpu@internetcds.com on Mon, Jul 30, 2001 at 01:21:22PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Jaye Mathisen [010730 15:21] wrote: > > 2 500+GB FS's, both filled completely. > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 524502226 195890 100% /d/d1 > newsfeed-inn# rm -f /d/d?/* > newsfeed-inn# ls -lR /d > total 4 > drwxr-xr-x 2 news news 512 Jul 30 13:13 d0 > drwxr-xr-x 2 news news 512 Jul 30 13:13 d1 > > /d/d0: > > /d/d1: > newsfeed-inn# df ; sleep 30 ; df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 524446754 251362 100% /d/d1 > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 522361778 2336338 100% /d/d1 > > I realize that one of the issues with softupdates is that freed space isn't > returned immediately, but *none* of the freed up space is being returned on d0, > while d1 is seeing it. > > Seems like these should be more equal, otherwise, if you had a lot of SU mounted > FS's, you could possibly deny service for a long time. > > It's been another minute now, and still no blocks freed up on /d/d0. > newsfeed-inn# df ; sleep 120 ; df [snip] > > Seems like it should round-robin them or something. I hope you're not expecting that 'rm' command to somehow realize that it's operating on two seperate FS's. If you want to see deletions happen at the same time you want to do this: rm -f /d/d0/* & ; rm -f /d/d1/* & ; Otherwise your rm is only going to process one directory tree at a time. If you want to accellerate the release of blocks issue a couple of sync(1) commands: sync;sync;sync; which will 'accelerate' the free'ing of space, actually it will accellerate the writing of the meta data that will actually free up the space. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 14: 4:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 16FC737B405 for ; Mon, 30 Jul 2001 14:04:48 -0700 (PDT) (envelope-from steve@virtual-voodoo.com) Received: from inlafrec (bdsl.66.12.217.40.gte.net [66.12.217.40]) (authenticated) by virtual-voodoo.com (8.11.4/8.11.4) with ESMTP id f6UL4cQ41781; Mon, 30 Jul 2001 16:04:38 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <023001c1193a$d1de9f30$28d90c42@eservoffice.com> From: "Steven Ames" To: "Alfred Perlstein" , "Jaye Mathisen" Cc: References: <20010730132122.C548@apocalypse.cdsnet.net> <20010730160043.Q26571@elvis.mu.org> Subject: Re: Softupdate gripe... Date: Mon, 30 Jul 2001 16:01:31 -0500 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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Alfred Perlstein" > * Jaye Mathisen [010730 15:21] wrote: > > > > 2 500+GB FS's, both filled completely. > > > > Filesystem 1K-blocks Used Avail Capacity Mounted on > > /dev/twed3d 524698116 524697730 386 100% /d/d0 > > /dev/twed4d 524698116 524502226 195890 100% /d/d1 > > newsfeed-inn# rm -f /d/d?/* > > newsfeed-inn# ls -lR /d > > total 4 > I hope you're not expecting that 'rm' command to somehow realize that > it's operating on two seperate FS's. If you want to see deletions > happen at the same time you want to do this: The lack of an ampersand on this command: 'newsfeed-inn# rm -f /d/d?/*' rather had me believe he waited for it to complete before starting to do his 'df' and was suprised at how long it was taking softupdates to release diskspace and at the order in which it was doing it. -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 14: 7:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id EF35737B401 for ; Mon, 30 Jul 2001 14:07:17 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id DEF2481D05; Mon, 30 Jul 2001 16:07:17 -0500 (CDT) Date: Mon, 30 Jul 2001 16:07:17 -0500 From: Alfred Perlstein To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Softupdate gripe... Message-ID: <20010730160717.R26571@elvis.mu.org> References: <20010730132122.C548@apocalypse.cdsnet.net> <20010730160043.Q26571@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730160043.Q26571@elvis.mu.org>; from bright@mu.org on Mon, Jul 30, 2001 at 04:00:43PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Alfred Perlstein [010730 16:01] wrote: [re: speeding up freeing of space when using softupdates] > > If you want to accellerate the release of blocks issue a couple > of sync(1) commands: > > sync;sync;sync; > > which will 'accelerate' the free'ing of space, actually it will > accellerate the writing of the meta data that will actually free > up the space. Let me add that this will not _really_ accelerate the process, it may give you instant gratification where you'll see a bunch of space, but by issuing a sync you're actually going to slow down the removal of files in the long run. Basically for speed you don't want to issue a sync until the rm command completes, if at all since the sync will also muck with other disk activity. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 14: 9:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 0E3F937B401 for ; Mon, 30 Jul 2001 14:09:44 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E155A81D05; Mon, 30 Jul 2001 16:09:43 -0500 (CDT) Date: Mon, 30 Jul 2001 16:09:43 -0500 From: Alfred Perlstein To: Steven Ames Cc: Jaye Mathisen , hackers@FreeBSD.ORG Subject: Re: Softupdate gripe... Message-ID: <20010730160943.S26571@elvis.mu.org> References: <20010730132122.C548@apocalypse.cdsnet.net> <20010730160043.Q26571@elvis.mu.org> <023001c1193a$d1de9f30$28d90c42@eservoffice.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <023001c1193a$d1de9f30$28d90c42@eservoffice.com>; from steve@virtual-voodoo.com on Mon, Jul 30, 2001 at 04:01:31PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Steven Ames [010730 16:04] wrote: > > ----- Original Message ----- > From: "Alfred Perlstein" > > * Jaye Mathisen [010730 15:21] wrote: > > > > > > 2 500+GB FS's, both filled completely. > > > > > > Filesystem 1K-blocks Used Avail Capacity > Mounted on > > > /dev/twed3d 524698116 524697730 386 100% > /d/d0 > > > /dev/twed4d 524698116 524502226 195890 100% > /d/d1 > > > newsfeed-inn# rm -f /d/d?/* > > > newsfeed-inn# ls -lR /d > > > total 4 > > > I hope you're not expecting that 'rm' command to somehow realize that > > it's operating on two seperate FS's. If you want to see deletions > > happen at the same time you want to do this: > > The lack of an ampersand on this command: 'newsfeed-inn# rm -f /d/d?/*' > rather had me believe he waited for it to complete before starting to do > his 'df' and was suprised at how long it was taking softupdates to release > diskspace and at the order in which it was doing it. Oh, then he just needs to issue a 'sync'. Enough pressure on the memory/disk subsystem (or false pressure from sync(1)) should cause it round robin, thing is that since the intial removal was serialized normal LRU behavior is to process whatever was removed first. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 14:35:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-69.dsl.lsan03.pacbell.net [63.207.60.69]) by hub.freebsd.org (Postfix) with ESMTP id C7B5337B401 for ; Mon, 30 Jul 2001 14:35:24 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 200B766BF7; Mon, 30 Jul 2001 14:35:22 -0700 (PDT) Date: Mon, 30 Jul 2001 14:35:21 -0700 From: Kris Kennaway To: Hans Zaunere Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Accessing /dev/klog and similar Message-ID: <20010730143521.A69771@xor.obsecurity.org> References: <20010730185018.10922.qmail@web12807.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730185018.10922.qmail@web12807.mail.yahoo.com>; from zaunere@yahoo.com on Mon, Jul 30, 2001 at 11:50:18AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 30, 2001 at 11:50:18AM -0700, Hans Zaunere wrote: > Hello, >=20 > I'm looking to access kernel messages directly from > the kernel, and not through syslog if I can help it. Look at how syslogd does it. Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7ZdMYWry0BWjoQKURAg+TAKC0qmbQVUG48w3lRV2t8Xelm58/egCfcW3W RN4kHBKVs5hbCiAnzXuZBxU= =cTVB -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 14:43:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guinness.fnal.gov (hadrian-00044704-dp.dhcp.fnal.gov [131.225.133.2]) by hub.freebsd.org (Postfix) with ESMTP id 45FF837B401 for ; Mon, 30 Jul 2001 14:43:38 -0700 (PDT) (envelope-from neswold@guinness.fnal.gov) Received: (from neswold@localhost) by guinness.fnal.gov (8.11.3/8.11.3) id f6ULhRl73757 for freebsd-hackers@freebsd.org; Mon, 30 Jul 2001 16:43:27 -0500 (CDT) (envelope-from neswold) Date: Mon, 30 Jul 2001 16:43:27 -0500 From: Rich Neswold To: freebsd-hackers@freebsd.org Subject: CardBus support... Message-ID: <20010730164327.A73740@spiv.fnal.gov> Reply-To: neswold@fnal.gov Mail-Followup-To: Rich Neswold , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Fermi National Accelerator Laboratory X-PGP-RSAfprint: 0A C8 A5 76 DF 8E E1 B3 F3 97 BE 73 DA CD 4B C9 X-PGP-RSAkey: ftp://ftp.mcs.net/mcsnet.users/rneswold/pub.key X-Operating-System: FreeBSD 4.3-RELEASE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, We have a few Dell laptops that came with the 3C-575BT ethernet cards. I was curious about the status of cardbus support under FreeBSD. I couldn't find a CardBus project page from the Home Page. There are CardBus-related files in our 4.3 source tree, but they don't seem to be included in our kernel builds. Is CardBus supported? Or close to supported? Is there a web page that shows the status of the progress? Any information would be appreciated. -- Rich ------------------------------------------------------------------------ Richard Neswold, Beams Division / Controls Dept | neswold@fnal.gov Fermilab, PO Box 500, MS 360, Batavia, IL 60510 | voice 1.630.840.3454 | fax 1.630.840.3093 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 14:57: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id C447037B403 for ; Mon, 30 Jul 2001 14:57:00 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac5.wam.umd.edu (IDENT:root@rac5.wam.umd.edu [128.8.10.145]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA23110; Mon, 30 Jul 2001 17:56:58 -0400 (EDT) Received: from rac5.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac5.wam.umd.edu (8.9.3/8.9.3) with SMTP id RAA23803; Mon, 30 Jul 2001 17:56:58 -0400 (EDT) Received: from localhost (culverk@localhost) by rac5.wam.umd.edu (8.9.3/8.9.3) with ESMTP id RAA23799; Mon, 30 Jul 2001 17:56:58 -0400 (EDT) X-Authentication-Warning: rac5.wam.umd.edu: culverk owned process doing -bs Date: Mon, 30 Jul 2001 17:56:57 -0400 (EDT) From: Kenneth Wayne Culver To: Rich Neswold Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: CardBus support... In-Reply-To: <20010730164327.A73740@spiv.fnal.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cardbus is only supported in FreeBSD-CURRENT. It may never be ported to 4.x Ken On Mon, 30 Jul 2001, Rich Neswold wrote: > Hello, > > We have a few Dell laptops that came with the 3C-575BT ethernet cards. I > was curious about the status of cardbus support under FreeBSD. I couldn't > find a CardBus project page from the Home Page. > > There are CardBus-related files in our 4.3 source tree, but they don't seem > to be included in our kernel builds. > > Is CardBus supported? Or close to supported? Is there a web page that shows > the status of the progress? > > Any information would be appreciated. > > -- > Rich > > ------------------------------------------------------------------------ > Richard Neswold, Beams Division / Controls Dept | neswold@fnal.gov > Fermilab, PO Box 500, MS 360, Batavia, IL 60510 | voice 1.630.840.3454 > | fax 1.630.840.3093 > > 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 Mon Jul 30 15:40:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id E5FFC37B401; Mon, 30 Jul 2001 15:40:53 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA10524; Mon, 30 Jul 2001 15:40:53 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 30 Jul 2001 15:40:40 -0700 (PDT) From: John Baldwin To: hackers@FreeBSD.org Subject: RE: PATCH: Make ast's loop Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 30-Jul-01 John Baldwin wrote: > I have a patch to close some races with receiving AST's while handling other > AST's. Unfortunately due to my office being moved all my test machines are > unavailable at the moment, so I'd like people to test it for me on SMP > machines > and alpha. I'll include it below, but my mailer may mangle it, so here is a > URL as well: http://www.FreeBSD.org/~jhb/patches/ast.patch Doh, that is an older version of the patch and has a few bugs. :/ The version at the URL has been updated. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Jul 30 15:53: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 4933337B403; Mon, 30 Jul 2001 15:52:08 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6UMq7721055; Mon, 30 Jul 2001 15:52:07 -0700 Date: Mon, 30 Jul 2001 15:52:07 -0700 From: Brooks Davis To: net@freebsd.org, hackers@freebsd.org Subject: review request: vlan cloning and modularization patch Message-ID: <20010730155207.A19629@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Please review and test the following patch. It adds cloning support to vlan devices and allows loading and unloading of VLAN support. The downside of the this loadability is that it currently appears to require enabling VLAN support on NICs that support it all the time which I am concerned may have performance issues. Can anyone confirm or deny this? If there are performance issues, I believe changes will need to be made to provide a machanism by which arbitrary ethernet interfaces may be notified of VLAN attachments so they can enable support only if there is someone there to use it. The patch should be applied as follows: cd /usr/src mkdir sys/modules/if_vlan patch < vlan.diff The patch may also be obtained from: http://people.freebsd.org/~brooks/patches/vlan.diff -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 Index: share/man/man4/vlan.4 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/share/man/man4/vlan.4,v retrieving revision 1.1 diff -u -r1.1 vlan.4 --- share/man/man4/vlan.4 2001/07/28 12:27:06 1.1 +++ share/man/man4/vlan.4 2001/07/30 22:38:49 @@ -33,7 +33,7 @@ .Nd IEEE 802.1Q VLAN network interface .Sh SYNOPSIS .\" In -stable: .Cd pseudo-device vlan Op Ar count -.Cd device vlan Op Ar count +.Cd device vlan .\" .Sh DESCRIPTION The Index: sys/conf/files =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/conf/files,v retrieving revision 1.555 diff -u -r1.555 files --- sys/conf/files 2001/07/26 23:04:46 1.555 +++ sys/conf/files 2001/07/30 22:33:18 @@ -907,7 +907,7 @@ net/if_stf.c optional stf net/if_tun.c optional tun net/if_tap.c optional tap -net/if_vlan.c count vlan +net/if_vlan.c optional vlan net/intrq.c standard net/net_osdep.c standard net/ppp_deflate.c optional ppp_deflate Index: sys/dev/nge/if_nge.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/nge/if_nge.c,v retrieving revision 1.19 diff -u -r1.19 if_nge.c --- sys/dev/nge/if_nge.c 2001/07/25 00:19:55 1.19 +++ sys/dev/nge/if_nge.c 2001/07/27 20:42:20 @@ -87,8 +87,6 @@ * if the user selects an MTU larger than 8152 (8170 - 18). */ =20 -#include "vlan.h" - #include #include #include @@ -102,11 +100,8 @@ #include #include #include - -#if NVLAN > 0 #include #include -#endif =20 #include =20 @@ -1335,16 +1330,19 @@ m->m_pkthdr.csum_data =3D 0xffff; } =20 -#if NVLAN > 0 /* * If we received a packet with a vlan tag, pass it * to vlan_input() instead of ether_input(). */ if (extsts & NGE_RXEXTSTS_VLANPKT) { - vlan_input_tag(eh, m, extsts & NGE_RXEXTSTS_VTCI); + if (vlan_input_tag_p !=3D NULL) { + (*vlan_input_tag_p)(eh, m, + extsts & NGE_RXEXTSTS_VTCI); + } else { + m_free(m); + } continue; } -#endif =20 ether_input(ifp, eh, m); } @@ -1539,14 +1537,12 @@ struct nge_desc *f =3D NULL; struct mbuf *m; int frag, cur, cnt =3D 0; -#if NVLAN > 0 struct ifvlan *ifv =3D NULL; =20 if ((m_head->m_flags & (M_PROTO1|M_PKTHDR)) =3D=3D (M_PROTO1|M_PKTHDR) && m_head->m_pkthdr.rcvif !=3D NULL && m_head->m_pkthdr.rcvif->if_type =3D=3D IFT_L2VLAN) ifv =3D m_head->m_pkthdr.rcvif->if_softc; -#endif =20 /* * Start packing the mbufs in this chain into @@ -1588,12 +1584,10 @@ NGE_TXEXTSTS_UDPCSUM; } =20 -#if NVLAN > 0 if (ifv !=3D NULL) { sc->nge_ldata->nge_tx_list[cur].nge_extsts |=3D (NGE_TXEXTSTS_VLANPKT|ifv->ifv_tag); } -#endif =20 sc->nge_ldata->nge_tx_list[cur].nge_mbuf =3D m_head; sc->nge_ldata->nge_tx_list[cur].nge_ctl &=3D ~NGE_CMDSTS_MORE; @@ -1754,7 +1748,6 @@ */ CSR_WRITE_4(sc, NGE_VLAN_IP_RXCTL, NGE_VIPRXCTL_IPCSUM_ENB); =20 -#if NVLAN > 0 /* * If VLAN support is enabled, tell the chip to detect * and strip VLAN tag info from received frames. The tag @@ -1762,7 +1755,6 @@ */ NGE_SETBIT(sc, NGE_VLAN_IP_RXCTL, NGE_VIPRXCTL_TAG_DETECT_ENB|NGE_VIPRXCTL_TAG_STRIP_ENB); -#endif =20 /* Set TX configuration */ CSR_WRITE_4(sc, NGE_TX_CFG, NGE_TXCFG); @@ -1772,14 +1764,12 @@ */ CSR_WRITE_4(sc, NGE_VLAN_IP_TXCTL, NGE_VIPTXCTL_CSUM_PER_PKT); =20 -#if NVLAN > 0 /* * If VLAN support is enabled, tell the chip to insert * VLAN tags on a per-packet basis as dictated by the * code in the frame encapsulation routine. */ NGE_SETBIT(sc, NGE_VLAN_IP_TXCTL, NGE_VIPTXCTL_TAG_PER_PKT); -#endif =20 /* Set full/half duplex mode. */ if ((mii->mii_media_active & IFM_GMASK) =3D=3D IFM_FDX) { Index: sys/dev/txp/if_txp.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/txp/if_txp.c,v retrieving revision 1.4 diff -u -r1.4 if_txp.c --- sys/dev/txp/if_txp.c 2001/07/27 19:38:56 1.4 +++ sys/dev/txp/if_txp.c 2001/07/27 21:49:57 @@ -39,8 +39,6 @@ * Driver for 3c990 (Typhoon) Ethernet ASIC */ =20 -#include "vlan.h" - #include #include #include @@ -54,6 +52,7 @@ #include #include #include +#include =20 #include #include @@ -66,10 +65,6 @@ =20 #include =20 -#if NVLAN > 0 -#include -#endif - #include /* for vtophys */ #include /* for vtophys */ #include /* for DELAY */ @@ -805,14 +800,17 @@ m->m_pkthdr.csum_data =3D 0xffff; } =20 -#if NVLAN > 0 if (rxd->rx_stat & RX_STAT_VLAN) { - if (vlan_input_tag(eh, m, - htons(rxd->rx_vlan >> 16)) < 0) + if (vlan_input_tag_p !=3D NULL) { + if ((*vlan_input_tag_p)(eh, m, + htons(rxd->rx_vlan >> 16)) < 0) + ifp->if_noproto++; + } else { + m_free(m); ifp->if_noproto++; + } goto next; } -#endif =20 eh =3D mtod(m, struct ether_header *); /* Remove header from mbuf and pass it on. */ @@ -1318,9 +1316,7 @@ struct mbuf *m, *m0; struct txp_swdesc *sd; u_int32_t firstprod, firstcnt, prod, cnt; -#if NVLAN > 0 struct ifvlan *ifv; -#endif =20 if ((ifp->if_flags & (IFF_RUNNING | IFF_OACTIVE)) !=3D IFF_RUNNING) return; @@ -1357,14 +1353,13 @@ if (++cnt >=3D (TX_ENTRIES - 4)) goto oactive; =20 -#if NVLAN > 0 if ((m->m_flags & (M_PROTO1|M_PKTHDR)) =3D=3D (M_PROTO1|M_PKTHDR) && m->m_pkthdr.rcvif !=3D NULL) { ifv =3D m->m_pkthdr.rcvif->if_softc; txd->tx_pflags =3D TX_PFLAGS_VLAN | (htons(ifv->ifv_tag) << TX_PFLAGS_VLANTAG_S); } -#endif + if (m->m_pkthdr.csum_flags & CSUM_IP) txd->tx_pflags |=3D TX_PFLAGS_IPCKSUM; =20 @@ -1880,12 +1875,10 @@ sc->sc_tx_capability =3D ext->ext_1 & OFFLOAD_MASK; sc->sc_rx_capability =3D ext->ext_2 & OFFLOAD_MASK; =20 -#if NVLAN > 0 if (rsp->rsp_par2 & rsp->rsp_par3 & OFFLOAD_VLAN) { sc->sc_tx_capability |=3D OFFLOAD_VLAN; sc->sc_rx_capability |=3D OFFLOAD_VLAN; } -#endif =20 #if 0 /* not ready yet */ Index: sys/i386/conf/NOTES =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/i386/conf/NOTES,v retrieving revision 1.942 diff -u -r1.942 NOTES --- sys/i386/conf/NOTES 2001/07/25 00:15:02 1.942 +++ sys/i386/conf/NOTES 2001/07/30 22:36:29 @@ -517,7 +517,7 @@ # See pppd(8) for more details. # device ether #Generic Ethernet -device vlan 1 #VLAN support +device vlan #VLAN support device token #Generic TokenRing device fddi #Generic FDDI device sppp #Generic Synchronous PPP Index: sys/net/ethernet.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/ethernet.h,v retrieving revision 1.16 diff -u -r1.16 ethernet.h --- sys/net/ethernet.h 2000/07/18 22:44:52 1.16 +++ sys/net/ethernet.h 2001/07/27 00:15:29 @@ -99,6 +99,10 @@ extern void (*ng_ether_attach_p)(struct ifnet *ifp); extern void (*ng_ether_detach_p)(struct ifnet *ifp); =20 +extern int (*vlan_input_p)(struct ether_header *eh, struct mbuf *m); +extern int (*vlan_input_tag_p)(struct ether_header *eh, struct mbuf *m, + u_int16_t t); + #else /* _KERNEL */ =20 #include Index: sys/net/if_ethersubr.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/if_ethersubr.c,v retrieving revision 1.94 diff -u -r1.94 if_ethersubr.c --- sys/net/if_ethersubr.c 2001/06/15 21:00:32 1.94 +++ sys/net/if_ethersubr.c 2001/07/27 00:16:04 @@ -39,7 +39,6 @@ #include "opt_inet6.h" #include "opt_ipx.h" #include "opt_bdg.h" -#include "opt_netgraph.h" =20 #include #include @@ -101,11 +100,6 @@ #include #endif =20 -#include "vlan.h" -#if NVLAN > 0 -#include -#endif /* NVLAN > 0 */ - /* netgraph node hooks for ng_ether(4) */ void (*ng_ether_input_p)(struct ifnet *ifp, struct mbuf **mp, struct ether_header *eh); @@ -115,6 +109,10 @@ void (*ng_ether_attach_p)(struct ifnet *ifp); void (*ng_ether_detach_p)(struct ifnet *ifp); =20 +int (*vlan_input_p)(struct ether_header *eh, struct mbuf *m); +int (*vlan_input_tag_p)(struct ether_header *eh, struct mbuf *m, + u_int16_t t); + static int ether_resolvemulti __P((struct ifnet *, struct sockaddr **, struct sockaddr *)); u_char etherbroadcastaddr[6] =3D { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff }; @@ -524,13 +522,11 @@ =20 ether_type =3D ntohs(eh->ether_type); =20 -#if NVLAN > 0 - if (ether_type =3D=3D vlan_proto) { - if (vlan_input(eh, m) < 0) + if (ether_type =3D=3D ETHERTYPE_VLAN) { + if (vlan_input_p !=3D NULL && (*vlan_input_p)(eh, m) < 0) ifp->if_data.ifi_noproto++; return; } -#endif /* NVLAN > 0 */ =20 switch (ether_type) { #ifdef INET Index: sys/net/if_vlan.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/if_vlan.c,v retrieving revision 1.30 diff -u -r1.30 if_vlan.c --- sys/net/if_vlan.c 2001/07/24 17:14:37 1.30 +++ sys/net/if_vlan.c 2001/07/27 00:19:01 @@ -54,7 +54,6 @@ * tag value that goes with it. */ =20 -#include "vlan.h" #include "opt_inet.h" =20 #include @@ -67,6 +66,8 @@ #include #include #include +#include /* XXX: Shouldn't really be required! */ +#include =20 #include #include @@ -81,23 +82,32 @@ #include #endif =20 +#define VLANNAME "vlan" +#define VLAN_MAXUNIT 0x7fff /* ifp->if_unit is only 15 bits */ + SYSCTL_DECL(_net_link); SYSCTL_NODE(_net_link, IFT_L2VLAN, vlan, CTLFLAG_RW, 0, "IEEE 802.1Q VLAN"= ); SYSCTL_NODE(_net_link_vlan, PF_LINK, link, CTLFLAG_RW, 0, "for consistency= "); - -u_int vlan_proto =3D ETHERTYPE_VLAN; -SYSCTL_INT(_net_link_vlan_link, VLANCTL_PROTO, proto, CTLFLAG_RW, &vlan_pr= oto, - 0, "Ethernet protocol used for VLAN encapsulation"); =20 -static struct ifvlan ifv_softc[NVLAN]; +static MALLOC_DEFINE(M_VLAN, "vlan", "802.1Q Virtual LAN Interface"); +static struct rman vlanunits[1]; +static LIST_HEAD(, ifvlan) ifv_list; =20 +static int vlan_clone_create(struct if_clone *, int *); +static void vlan_clone_destroy(struct ifnet *); static void vlan_start(struct ifnet *ifp); static void vlan_ifinit(void *foo); +static int vlan_input(struct ether_header *eh, struct mbuf *m); +static int vlan_input_tag(struct ether_header *eh, struct mbuf *m, + u_int16_t t); static int vlan_ioctl(struct ifnet *ifp, u_long cmd, caddr_t addr); static int vlan_setmulti(struct ifnet *ifp); static int vlan_unconfig(struct ifnet *ifp); static int vlan_config(struct ifvlan *ifv, struct ifnet *p); =20 +struct if_clone vlan_cloner =3D + IF_CLONE_INITIALIZER("vlan", vlan_clone_create, vlan_clone_destroy); + /* * Program our multicast filter. What we're actually doing is * programming the multicast filter of the parent. This has the @@ -142,14 +152,14 @@ if (error) return(error); SLIST_REMOVE_HEAD(&sc->vlan_mc_listhead, mc_entries); - free(mc, M_DEVBUF); + free(mc, M_VLAN); } =20 /* Now program new ones. */ TAILQ_FOREACH(ifma, &ifp->if_multiaddrs, ifma_link) { if (ifma->ifma_addr->sa_family !=3D AF_LINK) continue; - mc =3D malloc(sizeof(struct vlan_mc_entry), M_DEVBUF, M_WAITOK); + mc =3D malloc(sizeof(struct vlan_mc_entry), M_VLAN, M_WAITOK); bcopy(LLADDR((struct sockaddr_dl *)ifma->ifma_addr), (char *)&mc->mc_addr, ETHER_ADDR_LEN); SLIST_INSERT_HEAD(&sc->vlan_mc_listhead, mc, mc_entries); @@ -163,44 +173,40 @@ return(0); } =20 -static void -vlaninit(void) -{ - int i; - - for (i =3D 0; i < NVLAN; i++) { - struct ifnet *ifp =3D &ifv_softc[i].ifv_if; - - ifp->if_softc =3D &ifv_softc[i]; - ifp->if_name =3D "vlan"; - ifp->if_unit =3D i; - /* NB: flags are not set here */ - ifp->if_linkmib =3D &ifv_softc[i].ifv_mib; - ifp->if_linkmiblen =3D sizeof ifv_softc[i].ifv_mib; - /* NB: mtu is not set here */ - - ifp->if_init =3D vlan_ifinit; - ifp->if_start =3D vlan_start; - ifp->if_ioctl =3D vlan_ioctl; - ifp->if_output =3D ether_output; - ifp->if_snd.ifq_maxlen =3D ifqmaxlen; - ether_ifattach(ifp, ETHER_BPF_SUPPORTED); - /* Now undo some of the damage... */ - ifp->if_data.ifi_type =3D IFT_L2VLAN; - ifp->if_data.ifi_hdrlen =3D EVL_ENCAPLEN; - } -} - static int vlan_modevent(module_t mod, int type, void *data)=20 {=20 + int err; + switch (type) {=20 case MOD_LOAD:=20 - vlaninit(); + vlanunits->rm_type =3D RMAN_ARRAY; + vlanunits->rm_descr =3D "configurable if_vlan units"; + err =3D rman_init(vlanunits); + if (err !=3D 0) + return (err); + err =3D rman_manage_region(vlanunits, 0, VLAN_MAXUNIT); + if (err !=3D 0) { + printf("%s: vlanunits: rman_manage_region: Failed %d\n", + VLANNAME, err); + rman_fini(vlanunits); + return (err); + } + LIST_INIT(&ifv_list); + vlan_input_p =3D vlan_input; + vlan_input_tag_p =3D vlan_input_tag; + if_clone_attach(&vlan_cloner); break;=20 case MOD_UNLOAD:=20 - printf("if_vlan module unload - not possible for this module type\n");= =20 - return EINVAL;=20 + if_clone_detach(&vlan_cloner); + vlan_input_p =3D NULL; + vlan_input_tag_p =3D NULL; + while (!LIST_EMPTY(&ifv_list)) + vlan_clone_destroy(&LIST_FIRST(&ifv_list)->ifv_if); + err =3D rman_fini(vlanunits); + if (err !=3D 0) + return (err); + break; }=20 return 0;=20 }=20 @@ -213,7 +219,81 @@ =20 DECLARE_MODULE(if_vlan, vlan_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); =20 +static int +vlan_clone_create(struct if_clone *ifc, int *unit) +{ + struct resource *r; + struct ifvlan *ifv; + struct ifnet *ifp; + int s; + + if (*unit > VLAN_MAXUNIT) + return (ENXIO); + + if (*unit < 0) { + r =3D rman_reserve_resource(vlanunits, 0, VLAN_MAXUNIT, 1, + RF_ALLOCATED | RF_ACTIVE, NULL); + if (r =3D=3D NULL) + return (ENOSPC); + *unit =3D rman_get_start(r); + } else { + r =3D rman_reserve_resource(vlanunits, *unit, *unit, 1, + RF_ALLOCATED | RF_ACTIVE, NULL); + if (r =3D=3D NULL) + return (EEXIST); + } + + ifv =3D malloc(sizeof(struct ifvlan), M_VLAN, M_WAITOK); + memset(ifv, 0, sizeof(struct ifvlan)); + ifp =3D &ifv->ifv_if; + SLIST_INIT(&ifv->vlan_mc_listhead); + + s =3D splnet(); + LIST_INSERT_HEAD(&ifv_list, ifv, ifv_list); + splx(s); + + ifp->if_softc =3D ifv; + ifp->if_name =3D "vlan"; + ifp->if_unit =3D *unit; + ifv->r_unit =3D r; + /* NB: flags are not set here */ + ifp->if_linkmib =3D &ifv->ifv_mib; + ifp->if_linkmiblen =3D sizeof ifv->ifv_mib; + /* NB: mtu is not set here */ + + ifp->if_init =3D vlan_ifinit; + ifp->if_start =3D vlan_start; + ifp->if_ioctl =3D vlan_ioctl; + ifp->if_output =3D ether_output; + ifp->if_snd.ifq_maxlen =3D ifqmaxlen; + ether_ifattach(ifp, ETHER_BPF_SUPPORTED); + /* Now undo some of the damage... */ + ifp->if_data.ifi_type =3D IFT_L2VLAN; + ifp->if_data.ifi_hdrlen =3D EVL_ENCAPLEN; + + return (0); +} + static void +vlan_clone_destroy(struct ifnet *ifp) +{ + struct ifvlan *ifv =3D ifp->if_softc; + int s; + int err; + + s =3D splnet(); + LIST_REMOVE(ifv, ifv_list); + vlan_unconfig(ifp); + splx(s); + + ether_ifdetach(ifp, ETHER_BPF_SUPPORTED); + + err =3D rman_release_resource(ifv->r_unit); + KASSERT(err =3D=3D 0, ("Unexpected error freeing resource")); + free(ifv, M_VLAN); +} + +static void vlan_ifinit(void *foo) { return; @@ -294,7 +374,7 @@ sizeof(struct ether_header)); evl =3D mtod(m, struct ether_vlan_header *); evl->evl_proto =3D evl->evl_encap_proto; - evl->evl_encap_proto =3D htons(vlan_proto); + evl->evl_encap_proto =3D htons(ETHERTYPE_VLAN); evl->evl_tag =3D htons(ifv->ifv_tag); #ifdef DEBUG printf("vlan_start: %*D\n", sizeof *evl, @@ -316,19 +396,18 @@ return; } =20 -int +static int vlan_input_tag(struct ether_header *eh, struct mbuf *m, u_int16_t t) { - int i; struct ifvlan *ifv; =20 - for (i =3D 0; i < NVLAN; i++) { - ifv =3D &ifv_softc[i]; + for (ifv =3D LIST_FIRST(&ifv_list); ifv !=3D NULL; + ifv =3D LIST_NEXT(ifv, ifv_list)) { if (ifv->ifv_tag =3D=3D t) break; } =20 - if (i >=3D NVLAN || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { + if (ifv !=3DNULL || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { m_free(m); return -1; /* So the parent can take note */ } @@ -345,21 +424,20 @@ return 0; } =20 -int +static int vlan_input(struct ether_header *eh, struct mbuf *m) { - int i; struct ifvlan *ifv; =20 - for (i =3D 0; i < NVLAN; i++) { - ifv =3D &ifv_softc[i]; + for (ifv =3D LIST_FIRST(&ifv_list); ifv !=3D NULL; + ifv =3D LIST_NEXT(ifv, ifv_list)) { if (m->m_pkthdr.rcvif =3D=3D ifv->ifv_p && (EVL_VLANOFTAG(ntohs(*mtod(m, u_int16_t *))) =3D=3D ifv->ifv_tag)) break; } =20 - if (i >=3D NVLAN || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { + if (ifv !=3D NULL || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { m_freem(m); return -1; /* so ether_input can take note */ } @@ -462,7 +540,7 @@ if (error) return(error); SLIST_REMOVE_HEAD(&ifv->vlan_mc_listhead, mc_entries); - free(mc, M_DEVBUF); + free(mc, M_VLAN); } } =20 Index: sys/net/if_vlan_var.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/if_vlan_var.h,v retrieving revision 1.9 diff -u -r1.9 if_vlan_var.h --- sys/net/if_vlan_var.h 2001/07/24 00:03:51 1.9 +++ sys/net/if_vlan_var.h 2001/07/27 21:01:48 @@ -47,6 +47,8 @@ u_int16_t ifvm_tag; /* tag to apply on packets leaving if */ } ifv_mib; SLIST_HEAD(__vlan_mchead, vlan_mc_entry) vlan_mc_listhead; + LIST_ENTRY(ifvlan) ifv_list; + struct resource *r_unit; /* resource allocated for this unit */ }; #define ifv_if ifv_ac.ac_if #define ifv_tag ifv_mib.ifvm_tag @@ -77,13 +79,5 @@ }; #define SIOCSETVLAN SIOCSIFGENERIC #define SIOCGETVLAN SIOCGIFGENERIC - -#ifdef _KERNEL -/* shared with if_ethersubr.c: */ -extern u_int vlan_proto; -extern int vlan_input(struct ether_header *eh, struct mbuf *m); -extern int vlan_input_tag(struct ether_header *eh, - struct mbuf *m, u_int16_t t); -#endif =20 #endif /* _NET_IF_VLAN_VAR_H_ */ Index: sys/pci/if_ti.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/pci/if_ti.c,v retrieving revision 1.51 diff -u -r1.51 if_ti.c --- sys/pci/if_ti.c 2001/07/25 00:19:59 1.51 +++ sys/pci/if_ti.c 2001/07/27 20:42:41 @@ -78,8 +78,6 @@ * - Andrew Gallatin for providing FreeBSD/Alpha support. */ =20 -#include "vlan.h" - #include #include #include @@ -94,14 +92,11 @@ #include #include #include - -#include - -#if NVLAN > 0 #include #include -#endif =20 +#include + #include #include #include @@ -1334,9 +1329,7 @@ if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif =20 /* Set up the jumbo receive ring. */ rcb =3D &sc->ti_rdata->ti_info.ti_jumbo_rx_rcb; @@ -1347,9 +1340,7 @@ if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif =20 /* * Set up the mini ring. Only activated on the @@ -1367,9 +1358,7 @@ if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif =20 /* * Set up the receive return ring. @@ -1403,9 +1392,7 @@ rcb->ti_flags =3D 0; else rcb->ti_flags =3D TI_RCB_FLAG_HOST_RING; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; @@ -1738,22 +1725,18 @@ u_int32_t rxidx; struct ether_header *eh; struct mbuf *m =3D NULL; -#if NVLAN > 0 u_int16_t vlan_tag =3D 0; int have_tag =3D 0; -#endif =20 cur_rx =3D &sc->ti_rdata->ti_rx_return_ring[sc->ti_rx_saved_considx]; rxidx =3D cur_rx->ti_idx; TI_INC(sc->ti_rx_saved_considx, TI_RETURN_RING_CNT); =20 -#if NVLAN > 0 if (cur_rx->ti_flags & TI_BDFLAG_VLAN_TAG) { have_tag =3D 1; vlan_tag =3D cur_rx->ti_vlan_tag & 0xfff; } -#endif =20 if (cur_rx->ti_flags & TI_BDFLAG_JUMBO_RING) { TI_INC(sc->ti_jumbo, TI_JUMBO_RX_RING_CNT); @@ -1815,17 +1798,19 @@ m->m_pkthdr.csum_data =3D cur_rx->ti_tcp_udp_cksum; } =20 -#if NVLAN > 0 /* * If we received a packet with a vlan tag, pass it * to vlan_input() instead of ether_input(). */ if (have_tag) { - vlan_input_tag(eh, m, vlan_tag); + if (vlan_input_tag_p !=3D NULL) { + (*vlan_input_tag_p)(eh, m, vlan_tag); + } else { + m_free(m); + } have_tag =3D vlan_tag =3D 0; continue; } -#endif ether_input(ifp, eh, m); } =20 @@ -1963,14 +1948,12 @@ struct mbuf *m; u_int32_t frag, cur, cnt =3D 0; u_int16_t csum_flags =3D 0; -#if NVLAN > 0 struct ifvlan *ifv =3D NULL; =20 if ((m_head->m_flags & (M_PROTO1|M_PKTHDR)) =3D=3D (M_PROTO1|M_PKTHDR) && m_head->m_pkthdr.rcvif !=3D NULL && m_head->m_pkthdr.rcvif->if_type =3D=3D IFT_L2VLAN) ifv =3D m_head->m_pkthdr.rcvif->if_softc; -#endif =20 m =3D m_head; cur =3D frag =3D *txidx; @@ -2013,14 +1996,14 @@ TI_HOSTADDR(f->ti_addr) =3D vtophys(mtod(m, vm_offset_t)); f->ti_len =3D m->m_len; f->ti_flags =3D csum_flags; -#if NVLAN > 0 + if (ifv !=3D NULL) { f->ti_flags |=3D TI_BDFLAG_VLAN_TAG; f->ti_vlan_tag =3D ifv->ifv_tag & 0xfff; } else { f->ti_vlan_tag =3D 0; } -#endif + /* * Sanity check: avoid coming within 16 descriptors * of the end of the ring. --- sys/modules/if_vlan/Makefile.orig Fri Jul 13 17:14:21 2001 +++ sys/modules/if_vlan/Makefile Fri Jul 27 14:00:14 2001 @@ -0,0 +1,12 @@ +# $FreeBSD$ + +.PATH: ${.CURDIR}/../../net + +KMOD=3D if_vlan +SRCS=3D if_vlan.c opt_inet.h +NOMAN=3D + +opt_inet.h: + echo "#define INET 1" > ${.TARGET} + +.include --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ZeUWXY6L6fI4GtQRAgL+AKCM49r/UFCHvriO3uagKvFtO3Zk3wCfSOLE Hmr8m5Yajymonr4MmKgmEO0= =92jk -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 16:24:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from witch.iiclub.co.il (shells.help-me.co.il [212.25.125.64]) by hub.freebsd.org (Postfix) with ESMTP id 1614837B403 for ; Mon, 30 Jul 2001 16:24:39 -0700 (PDT) (envelope-from vadik@vygo.net) Received: from vadik by witch.iiclub.co.il with local (Exim 3.22 #27) id 15RLLl-0004Fh-00 for freebsd-hackers@FreeBSD.ORG; Tue, 31 Jul 2001 01:17:21 +0300 Date: Tue, 31 Jul 2001 01:17:20 +0300 From: Vadim Vygonets To: freebsd-hackers@FreeBSD.ORG Subject: Re: Backup file formats: tar, cpio, pax, yadda, yadda, yadda Message-ID: <20010731011720.B16087@vygo.net> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <3B6212B5.FDFEB694@bellatlantic.net> <200107270444.f6R4iBw09131@harmony.village.org> <200107280307.f6S37Yw16631@harmony.village.org> <3B625232.CAF39600@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B625232.CAF39600@yahoo.com>; from kc5vdj@yahoo.com on Sat, Jul 28, 2001 at 12:48:34AM -0500 X-Operating-System: yes Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Quoth Jim Bryant on Sat, Jul 28, 2001: > FreeBSD and GNU tar will not restore correctly to HP-UX, but dump/restore does work fine. But POSIX tar (pax -x ustar) and GNU tar will not restore each other's archives correctly, if said archives have long filenames. However, dump and tar should be used for different purposes. Vadik. -- Taunt not the sysadmin, for he can become you and make your life interesting. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 20: 2:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail9.wlv.netzero.net (mail9.wlv.netzero.net [209.247.163.66]) by hub.freebsd.org (Postfix) with SMTP id C139937B401 for ; Mon, 30 Jul 2001 20:02:45 -0700 (PDT) (envelope-from jac_0o@netzero.net) Received: (qmail 26193 invoked from network); 31 Jul 2001 02:55:23 -0000 Received: from dialup-64.156.96.139.dial1.orlando1.level3.net (HELO computer) (64.156.96.139) by mail9.wlv.netzero.net with SMTP; 31 Jul 2001 02:55:23 -0000 Message-ID: <000801c11974$fc6717c0$8b609c40@computer> From: "jac0b br00ks" To: Subject: questions on the install Date: Mon, 30 Jul 2001 22:57:55 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C1194B.11D507E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C1194B.11D507E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable when i try to install bsd it will never install "bin\directory" it says = like error writing=20 bin\directory (-0 bytes of 26""""" bytes) ------=_NextPart_000_0005_01C1194B.11D507E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
when i try to install bsd it will never = install=20 "bin\directory" it says like error writing
bin\directory (-0 bytes of 26"""""=20 bytes)
------=_NextPart_000_0005_01C1194B.11D507E0-- ---------------------------------------------------- NetZero Platinum Sign Up Today - Only $9.95 per month! http://my.netzero.net/s/signup?r=platinum&refcd=PT97 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 20:41:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailout3-0 (mailout3-1.nyroc.rr.com [24.92.226.168]) by hub.freebsd.org (Postfix) with ESMTP id DD63237B405 for ; Mon, 30 Jul 2001 20:41:20 -0700 (PDT) (envelope-from James_Bond_79@yahoo.com) Received: from halstead007 (roc-24-161-78-218.rochester.rr.com [24.161.78.218]) by mailout3-0 (8.11.2/RoadRunner 1.03) with SMTP id f6V3e3a00830 for ; Mon, 30 Jul 2001 23:40:03 -0400 (EDT) Content-Type: text/plain; charset="iso-8859-1" From: James Halstead To: freebsd-hackers@freebsd.org Subject: kern/26563 setting sample rate Date: Mon, 30 Jul 2001 23:48:56 -0400 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01073023485600.00361@halstead007> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just wanted to see if this can get committed. I have been using it with no problems and it makes some programs work a little nicer for those of us with ac'97 cards (notably xmms) It is a simple one line patch. Would be nice if this could make it to 4.4-RELEASE... James To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 22:15:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id CA19B37B403 for ; Mon, 30 Jul 2001 22:15:26 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6V5FQI95039 for ; Mon, 30 Jul 2001 22:15:26 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 30 Jul 2001 22:15:08 -0700 (PDT) From: Matthew Jacob Reply-To: To: Subject: wierdness with CVS dates... Message-ID: <20010730221443.A57563-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a file on freefall, I see: ---------------------------- revision 1.6 date: 2001/04/07 23:48:46; author: gallatin; state: Exp; lines: +5 -4 fix cd9660 to work on files larger than ISO_DEFAULT_BLOCK_SIZE and unbreak cdboot on alphas (which has been broken since just after 4.0-RELEASE) submitted by: jlemon ---------------------------- revision 1.5 date: 2000/04/29 20:47:07; author: jlemon; state: Exp; lines: +111 -146 Add a readdir function to the loader fsops vector, and implement the functionality for some of the filesystesms. How can this heappen? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 22:17:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.newgold.net (aphex.newgold.net [209.42.222.44]) by hub.freebsd.org (Postfix) with SMTP id 5B0D337B401 for ; Mon, 30 Jul 2001 22:17:10 -0700 (PDT) (envelope-from jmallett@mail.newgold.net) Received: (qmail 76874 invoked by uid 1000); 31 Jul 2001 05:16:58 -0000 Date: Tue, 31 Jul 2001 05:16:58 +0000 From: Joseph Mallett To: Matthew Jacob Cc: hackers@freebsd.org Subject: Re: wierdness with CVS dates... Message-ID: <20010731051658.A76739@NewGold.NET> References: <20010730221443.A57563-100000@wonky.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010730221443.A57563-100000@wonky.feral.com> User-Agent: Mutt/1.3.19i Organisation: New Gold Technology Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG How can what happen? looks fine to me. On Mon, Jul 30, 2001 at 10:15:08PM -0700, Matthew Jacob wrote: > > > In a file on freefall, I see: > > ---------------------------- > revision 1.6 > date: 2001/04/07 23:48:46; author: gallatin; state: Exp; lines: +5 -4 > fix cd9660 to work on files larger than ISO_DEFAULT_BLOCK_SIZE and unbreak > cdboot on alphas (which has been broken since just after 4.0-RELEASE) > > submitted by: jlemon > ---------------------------- > revision 1.5 > date: 2000/04/29 20:47:07; author: jlemon; state: Exp; lines: +111 -146 > Add a readdir function to the loader fsops vector, and implement the > functionality for some of the filesystesms. > > > How can this heappen? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- -- Joseph A. Mallett http://srcsys.org xMach Core Team, www.xMach.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jul 30 22:22:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 6DB6437B401 for ; Mon, 30 Jul 2001 22:22:10 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6V5M7I95144; Mon, 30 Jul 2001 22:22:07 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 30 Jul 2001 22:21:50 -0700 (PDT) From: Matthew Jacob Reply-To: To: Joseph Mallett Cc: Subject: Re: wierdness with CVS dates... In-Reply-To: <20010731051658.A76739@NewGold.NET> Message-ID: <20010730222111.Q57563-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG *SMACK* (sorry, whimper) my eyes are going bad on me... I saw this as a checkin 4/29 of this year followed by a checkin of 4/7... sorry... On Tue, 31 Jul 2001, Joseph Mallett wrote: > How can what happen? looks fine to me. > > On Mon, Jul 30, 2001 at 10:15:08PM -0700, Matthew Jacob wrote: > > > > > > In a file on freefall, I see: > > > > ---------------------------- > > revision 1.6 > > date: 2001/04/07 23:48:46; author: gallatin; state: Exp; lines: +5 -4 > > fix cd9660 to work on files larger than ISO_DEFAULT_BLOCK_SIZE and unbreak > > cdboot on alphas (which has been broken since just after 4.0-RELEASE) > > > > submitted by: jlemon > > ---------------------------- > > revision 1.5 > > date: 2000/04/29 20:47:07; author: jlemon; state: Exp; lines: +111 -146 > > Add a readdir function to the loader fsops vector, and implement the > > functionality for some of the filesystesms. > > > > > > How can this heappen? > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > -- > Joseph A. Mallett > http://srcsys.org > > xMach Core Team, www.xMach.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 0:14:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 77A0E37B401 for ; Tue, 31 Jul 2001 00:14:40 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6V7EcF87186; Tue, 31 Jul 2001 01:14:39 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6V7Ecw46692; Tue, 31 Jul 2001 01:14:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107310714.f6V7Ecw46692@harmony.village.org> To: mjacob@feral.com Subject: Re: wierdness with CVS dates... Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 30 Jul 2001 22:15:08 PDT." <20010730221443.A57563-100000@wonky.feral.com> References: <20010730221443.A57563-100000@wonky.feral.com> Date: Tue, 31 Jul 2001 01:14:38 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010730221443.A57563-100000@wonky.feral.com> Matthew Jacob writes: : date: 2001/04/07 23:48:46; author: gallatin; state: Exp; lines: +5 -4 : date: 2000/04/29 20:47:07; author: jlemon; state: Exp; lines: +111 -146 : : How can this heappen? By staggering the commits by 1 year. Wanrer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 1:19:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ip.eth.net (mail.ip.eth.net [202.9.128.18]) by hub.freebsd.org (Postfix) with ESMTP id 127A237B401; Tue, 31 Jul 2001 01:19:29 -0700 (PDT) (envelope-from anjali@indranetworks.com) Received: (apparently) from anjali ([61.11.16.239]) by ip.eth.net with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 31 Jul 2001 13:49:24 +0530 Message-ID: <007601c11999$865df600$0a00a8c0@indranet> From: "Anjali Kulkarni" To: "Mike Smith" Cc: References: <200107282022.f6SKMhJ01990@mass.dis.org> Subject: Re: inet_aton Date: Tue, 31 Jul 2001 13:49:27 +0530 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Thanks for your response. The reason I am trying to use inet_aton is because I am writing a kernel proxy which connects to a webserver etc. etc. So, I need to convert the server's ip address to the network byte address, and hence I need to use this function. I do not see how else I can get the network address from the ip address I have, except by using inet_aton??? Thanks, Anjali ----- Original Message ----- From: Mike Smith To: Anjali Kulkarni Cc: Sent: Sunday, July 29, 2001 1:52 AM Subject: Re: inet_aton > > I want to use the function inet_aton() in the kernel code. However, I = > > found no kernel equivalent of this function int the freebsd sources. I = > > could find inet_ntoa(), but not inet_aton(). Is it named by some other = > > name or how can I locate it? > > If you are trying to parse an ascii internet address in the kernel, > you're quite possibly making a bad design mistake - why is it still in > text format? If you're passing it in from another program, you should be > passing a sockaddr struct. > > Failing that, you'll just have to steal the code from libc and bring it > in yourself. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 1:41:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ip.eth.net (mail.ip.eth.net [202.9.128.18]) by hub.freebsd.org (Postfix) with ESMTP id 5579037B401 for ; Tue, 31 Jul 2001 01:41:27 -0700 (PDT) (envelope-from anjali@indranetworks.com) Received: (apparently) from anjali ([61.11.16.239]) by ip.eth.net with Microsoft SMTPSVC(5.5.1877.467.46); Tue, 31 Jul 2001 14:11:23 +0530 Message-ID: <008701c1199c$98684f50$0a00a8c0@indranet> From: "Anjali Kulkarni" To: Cc: References: <002d01c11728$d34723b0$0a00a8c0@indranet> <3B6325B7.D6CBC67A@mindspring.com> Subject: Re: inet_aton Date: Tue, 31 Jul 2001 14:11:27 +0530 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 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Terry, Thanks for your response. I am new to kernel programming, and so cud u tell me why it is a bad idea to pass strings to the kernel? Is it due to static memory is used etc.? Actually, I am not passing strings to the kernel, I am writing code in kernel which has a remote server's ip-address string, and I need to connect to the remote server, so I need to use inet_aton..... Anjali ----- Original Message ----- From: Terry Lambert To: Anjali Kulkarni Cc: Sent: Sunday, July 29, 2001 2:21 AM Subject: Re: inet_aton > > Anjali Kulkarni wrote: > > > > Hi, > > > > I want to use the function inet_aton() in the kernel code. > > However, I found no kernel equivalent of this function int > > the freebsd sources. I could find inet_ntoa(), but not > > inet_aton(). Is it named by some other name or how can I > > locate it? > > The kernel is not linked against the resolver library, > which is where the network address manipulation functions > come from (in FreeBSD, the resolver library has been rolled > into libc; this is traditional, but makes it very hard to > upgrade to newer versions when needed. In FreeBSD, the > kernel isn't linked against the C library, either). > > You should pass in sockaddr structures, not strings, to the > kernel, if you wish to pass network addresses to the kernel. > > As a general policy issue, I think that passing strings into > the kernel for any reason is a bad idea. We tolerate it > where we must (path name lookups), but any place else that > takes a string is bad news (e.g. we will eventually get > around to fixing mount at some point in the future). > > -- Terry > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 3:35: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id ABC0C37B401 for ; Tue, 31 Jul 2001 03:34:56 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.247.141.186.Dial1.SanJose1.Level3.net [209.247.141.186]) by robin.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id DAA15743; Tue, 31 Jul 2001 03:32:51 -0700 (PDT) Message-ID: <3B66896F.7E0300EF@mindspring.com> Date: Tue, 31 Jul 2001 03:33:19 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Anjali Kulkarni Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: inet_aton References: <002d01c11728$d34723b0$0a00a8c0@indranet> <3B6325B7.D6CBC67A@mindspring.com> <008701c1199c$98684f50$0a00a8c0@indranet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Anjali Kulkarni wrote: > Thanks for your response. I am new to kernel programming, and so cud u tell > me why it is a bad idea to pass strings to the kernel? Is it due to static > memory is used etc.? > Actually, I am not passing strings to the kernel, I am writing code in > kernel which has a remote server's ip-address string, and I need to connect > to the remote server, so I need to use inet_aton..... In general, string manipulation in the kernel is a bad idea. The problem is that C strings are subject to buffer overflows, etc., and dragging them into the kernel makes the kernel vulnerable to similar attacks. To copy the string in, you will call a "copyinstr()" function with arguments, including the address of the kernel buffer in which to copy, and the size of that buffer. If your string length exceeds the buffer size, it is up to you to properly NUL terminate the string: if you don't, you risk running off into memory when iterating the string for length, etc.. A failure there can result in a panic. The other issue here is that inet_aton() is IPv4 specific, so your code will fail with IPv6. In addition, the coversion functions turn out to be fairly heavy weight. Finally, the idea of dragging a lot of new string manipulation functions into the kernel is really, really bad: it will encourage more prople to use them, or, worse, do the same, with their own string manipulation functions. The real question, I guess, is that you say "...kernel which has a remote server's ip-address string...": how did it get this string, if you didn't provide it the information? Even if it got the information from its peer, the most correct thing to do would be to pass the address to a user space process for the translation, and get it passed back into the kernel as a struct sockaddr *. Really, you are only ever going to need this information to do connection setup or teardown, and amortizing the cost of doing this over the lifetime of the connection is going to make the overall costs very, very low; it will also give your kernel access to the DNS services in user space, which you will have a very hard time jamming into the kernel, should you decide that you need to translate not only IP addresses, but names, as well. If you get the information from user space, then the answer is trivial: push it into the kernel as a struct sockaddr * and do a copyin on it based on the type (see the "bind" and "connect" code on how this is done). This means you will have a control program in user space, but still do theheavy lifting in the kernel. There's a great tendency these days to jam much user space functionality into the kernel, on the theory that it will make that functionality faster; in general, though, it tends to bloat the kernel with non-swappable pages (e.g. kernel code and data), which then steals memory from your primary application. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 4:23:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ceeyes.com (mail.in.ceeyes.com [65.192.85.133]) by hub.freebsd.org (Postfix) with ESMTP id 3A2C837B401 for ; Tue, 31 Jul 2001 04:23:01 -0700 (PDT) (envelope-from srinivass@in.ceeyes.com) Received: from ssrao.in.ceeyes.com (Shobana [10.1.9.11]) by mail.ceeyes.com (8.9.1b+Sun/8.9.3) with SMTP id QAA13659 for ; Tue, 31 Jul 2001 16:52:44 +0530 (INST) Message-ID: <003601c119b3$2f06cde0$0b09010a@ssrao.in.ceeyes.com> From: "srinivasarao" To: Subject: help me !!!!!! Date: Tue, 31 Jul 2001 16:53:08 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0033_01C119E1.46D0A760" 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0033_01C119E1.46D0A760 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, By the chance is there any possibility to build the kernel without VGA = card serially either for newly building of kernel or for exisiting = kernel after modifications? if any chance please guide me ? what are = all steps to be taken care? Please help me. thank u, with regards=20 S.Srinivasa Rao Ceeyes Software Technologies Pvt. Ltd, Behind Govt Mint, Cherlapalli, Hyderabad-51, ph 040-7261093/93/95/96,extn 1267, mobile :- 919848130891 ------=_NextPart_000_0033_01C119E1.46D0A760 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
By the chance is there any possibility to build the = kernel=20 without VGA card serially  either for newly building of kernel or = for=20 exisiting kernel after modifications?  if any chance please guide = me ? what=20 are all steps to be taken care?
 Please help me.
 
thank u,
 
with regards 
 
S.Srinivasa Rao
Ceeyes Software = Technologies=20 Pvt. Ltd,
Behind Govt Mint, Cherlapalli,
Hyderabad-51, ph=20 040-7261093/93/95/96,extn 1267, mobile :-=20 919848130891
------=_NextPart_000_0033_01C119E1.46D0A760-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 4:48:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id A32F837B403; Tue, 31 Jul 2001 04:48:46 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 42FA73E2F; Tue, 31 Jul 2001 04:48:46 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 387D93C12B; Tue, 31 Jul 2001 04:48:46 -0700 (PDT) To: hackers@freebsd.org Cc: alfred@freebsd.org Subject: portmap_enable vs. rpcbind_enable Date: Tue, 31 Jul 2001 04:48:41 -0700 From: Dima Dorfman Message-Id: <20010731114846.42FA73E2F@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anybody know (remember?) why portmap_enable (the rc.conf knob) wasn't renamed to rpcbind_enable when portmap became rpcbind? It seems odd to have a knob called portmap_enable that actually starts something called rpcbind (not to mention violating POLA). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 8:26:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 8FBEB37B405; Tue, 31 Jul 2001 08:26:10 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.11.4/8.11.4) id f6VFQ7l08813; Tue, 31 Jul 2001 10:26:07 -0500 (CDT) (envelope-from dan) Date: Tue, 31 Jul 2001 10:26:06 -0500 From: Dan Nelson To: Dima Dorfman Cc: hackers@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable Message-ID: <20010731102606.A26323@dan.emsphone.com> References: <20010731114846.42FA73E2F@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010731114846.42FA73E2F@bazooka.unixfreak.org> User-Agent: Mutt/1.3.20i X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Jul 31), Dima Dorfman said: > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > seems odd to have a knob called portmap_enable that actually starts > something called rpcbind (not to mention violating POLA). Probably to keep existing rc.conf's from breaking. Same reason we've still got xntpd_enable. -- 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 Jul 31 8:34: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id BCEC337B401; Tue, 31 Jul 2001 08:34:05 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 2CF803E28; Tue, 31 Jul 2001 08:34:04 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 238EE3C12B; Tue, 31 Jul 2001 08:34:04 -0700 (PDT) To: Dan Nelson Cc: hackers@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable In-Reply-To: <20010731102606.A26323@dan.emsphone.com>; from dnelson@emsphone.com on "Tue, 31 Jul 2001 10:26:06 -0500" Date: Tue, 31 Jul 2001 08:33:59 -0700 From: Dima Dorfman Message-Id: <20010731153404.2CF803E28@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan Nelson writes: > In the last episode (Jul 31), Dima Dorfman said: > > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > > seems odd to have a knob called portmap_enable that actually starts > > something called rpcbind (not to mention violating POLA). > > Probably to keep existing rc.conf's from breaking. Same reason we've > still got xntpd_enable. Why not change the names now, but keep the old ones working until, say, 5.0 is branched? People moving from 4.x will have enough hurdles to jump through as it is, and those using -current will have half a year to change it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 8:38:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id A93D937B405; Tue, 31 Jul 2001 08:38:33 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 31 Jul 2001 16:38:32 +0100 (BST) Date: Tue, 31 Jul 2001 16:38:32 +0100 From: David Malone To: Dima Dorfman Cc: Dan Nelson , hackers@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable Message-ID: <20010731163832.A91014@walton.maths.tcd.ie> References: <20010731102606.A26323@dan.emsphone.com> <20010731153404.2CF803E28@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010731153404.2CF803E28@bazooka.unixfreak.org>; from dima@unixfreak.org on Tue, Jul 31, 2001 at 08:33:59AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 31, 2001 at 08:33:59AM -0700, Dima Dorfman wrote: > Dan Nelson writes: > > In the last episode (Jul 31), Dima Dorfman said: > > > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > > > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > > > seems odd to have a knob called portmap_enable that actually starts > > > something called rpcbind (not to mention violating POLA). > > > > Probably to keep existing rc.conf's from breaking. Same reason we've > > still got xntpd_enable. > > Why not change the names now, but keep the old ones working until, > say, 5.0 is branched? People moving from 4.x will have enough hurdles > to jump through as it is, and those using -current will have half a > year to change it. It still is an extra change for people updating from 4.X to 5.0. Maybe we should just make a portmap_program variable which is set to portmap in -stable and rpcbind in -current. At least things would be orthogonal then. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 8:45:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id BAFF537B409; Tue, 31 Jul 2001 08:45:38 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id IAA27187; Tue, 31 Jul 2001 08:45:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010731114846.42FA73E2F@bazooka.unixfreak.org> Date: Tue, 31 Jul 2001 08:45:23 -0700 (PDT) From: John Baldwin To: Dima Dorfman Subject: RE: portmap_enable vs. rpcbind_enable Cc: alfred@FreeBSD.org, hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 31-Jul-01 Dima Dorfman wrote: > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > seems odd to have a knob called portmap_enable that actually starts > something called rpcbind (not to mention violating POLA). Actually, it was for POLA reasons. (I'm not arguing for or against said reason, mind you.) It was thought that changing the name of the portmap_enable knob might throw some people for a loop. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jul 31 8:46:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id B2E0137B43E; Tue, 31 Jul 2001 08:45:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id IAA27304; Tue, 31 Jul 2001 08:45:44 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010731163832.A91014@walton.maths.tcd.ie> Date: Tue, 31 Jul 2001 08:45:32 -0700 (PDT) From: John Baldwin To: David Malone Subject: Re: portmap_enable vs. rpcbind_enable Cc: alfred@FreeBSD.org, hackers@FreeBSD.org, Dan Nelson , Dima Dorfman Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 31-Jul-01 David Malone wrote: > On Tue, Jul 31, 2001 at 08:33:59AM -0700, Dima Dorfman wrote: >> Dan Nelson writes: >> > In the last episode (Jul 31), Dima Dorfman said: >> > > Does anybody know (remember?) why portmap_enable (the rc.conf knob) >> > > wasn't renamed to rpcbind_enable when portmap became rpcbind? It >> > > seems odd to have a knob called portmap_enable that actually starts >> > > something called rpcbind (not to mention violating POLA). >> > >> > Probably to keep existing rc.conf's from breaking. Same reason we've >> > still got xntpd_enable. >> >> Why not change the names now, but keep the old ones working until, >> say, 5.0 is branched? People moving from 4.x will have enough hurdles >> to jump through as it is, and those using -current will have half a >> year to change it. > > It still is an extra change for people updating from 4.X to 5.0. > Maybe we should just make a portmap_program variable which is set > to portmap in -stable and rpcbind in -current. At least things > would be orthogonal then. > grep portmap_program /etc/defaults/rc.conf portmap_program="/usr/sbin/rpcbind" # path to portmap, if you want a different one. > uname -r 5.0-CURRENT From cvs annotate: 1.71 (eivind 28-Jul-00): portmap_enable="NO" # Run the portmapper service (YES/NO). 1.96 (alfred 19-Mar-01): portmap_program="/usr/sbin/rpcbind" # path to portmap, if you want a different one. 1.1 (jkh 09-Feb-99): portmap_flags="" # Flags to portmap (if enabled). From cvs annotate of rev 1.95: 1.71 (eivind 28-Jul-00): portmap_enable="NO" # Run the portmapper service (YES/NO). 1.3 (jfitz 11-Mar-99): portmap_program="/usr/sbin/portmap" # path to portmap, if you want a different one. 1.1 (jkh 09-Feb-99): portmap_flags="" # Flags to portmap (if enabled). As you can see, we've had the portmap_program knob for 2.5 years now. :) Right now there is no change related to portmap for a 4.x -> 5.0 upgrade. (None that is visible to the user at least.) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jul 31 8:46:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id C2C8B37B640; Tue, 31 Jul 2001 08:46:37 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 68EBB3E35; Tue, 31 Jul 2001 08:46:33 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 5D25F3C12C; Tue, 31 Jul 2001 08:46:33 -0700 (PDT) To: David Malone Cc: Dan Nelson , hackers@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable In-Reply-To: <20010731163832.A91014@walton.maths.tcd.ie>; from dwmalone@maths.tcd.ie on "Tue, 31 Jul 2001 16:38:32 +0100" Date: Tue, 31 Jul 2001 08:46:28 -0700 From: Dima Dorfman Message-Id: <20010731154633.68EBB3E35@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Malone writes: > On Tue, Jul 31, 2001 at 08:33:59AM -0700, Dima Dorfman wrote: > > Dan Nelson writes: > > > In the last episode (Jul 31), Dima Dorfman said: > > > > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > > > > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > > > > seems odd to have a knob called portmap_enable that actually starts > > > > something called rpcbind (not to mention violating POLA). > > > > > > Probably to keep existing rc.conf's from breaking. Same reason we've > > > still got xntpd_enable. > > > > Why not change the names now, but keep the old ones working until, > > say, 5.0 is branched? People moving from 4.x will have enough hurdles > > to jump through as it is, and those using -current will have half a > > year to change it. > > It still is an extra change for people updating from 4.X to 5.0. > Maybe we should just make a portmap_program variable which is set > to portmap in -stable and rpcbind in -current. At least things > would be orthogonal then. That's what we already have, but we still have a knob that says it will start 'portmap' starting something called 'rpcbind', and the user didn't explicitly ask for that. If people think it's too much trouble, though, I'm not going to press the issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 9: 1:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id 11F2937B413 for ; Tue, 31 Jul 2001 09:01:08 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 95657 invoked by uid 1000); 31 Jul 2001 16:01:28 -0000 Date: Tue, 31 Jul 2001 18:01:28 +0200 From: "Karsten W. Rohrbach" To: Alfred Perlstein Cc: Jaye Mathisen , hackers@freebsd.org Subject: Re: Softupdate gripe... Message-ID: <20010731180128.H92506@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , Alfred Perlstein , Jaye Mathisen , hackers@freebsd.org References: <20010730132122.C548@apocalypse.cdsnet.net> <20010730160043.Q26571@elvis.mu.org> <20010730160717.R26571@elvis.mu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="JI+G0+mN8WmwPnOn" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730160717.R26571@elvis.mu.org>; from bright@mu.org on Mon, Jul 30, 2001 at 04:07:17PM -0500 X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --JI+G0+mN8WmwPnOn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Alfred Perlstein(bright@mu.org)@2001.07.30 16:07:17 +0000: > * Alfred Perlstein [010730 16:01] wrote: > [re: speeding up freeing of space when using softupdates] > >=20 > > If you want to accellerate the release of blocks issue a couple > > of sync(1) commands: > >=20 > > sync;sync;sync; > >=20 > > which will 'accelerate' the free'ing of space, actually it will=20 > > accellerate the writing of the meta data that will actually free > > up the space. >=20 > Let me add that this will not _really_ accelerate the process, it > may give you instant gratification where you'll see a bunch of > space, but by issuing a sync you're actually going to slow down > the removal of files in the long run. Basically for speed you > don't want to issue a sync until the rm command completes, if at > all since the sync will also muck with other disk activity. >=20 isn't all this behaviour controlled by vfs.ffs.doasyncfree ? root@nGENn:defiler[/sys]28# grep -rsi doasyncfree ./ufs =2E/ufs/ffs/ffs_alloc.c:static int doasyncfree =3D 1; =2E/ufs/ffs/ffs_alloc.c:SYSCTL_INT(_vfs_ffs, FFS_ASYNCFREE, doasyncfree, CTLFLAG_RW, &doasyncfree, 0, ""); =2E/ufs/ffs/ffs_alloc.c: * strict correctness, the `doasyncfree' flag should be set to zero. =2E/ufs/ffs/ffs_alloc.c: * The test on `doasyncfree' should be changed to test a flag =2E/ufs/ffs/ffs_alloc.c: if (doasyncfree) =2E/ufs/ffs/ffs_alloc.c: if (!doasyncfree) =2E/ufs/ffs/ffs_alloc.c: if (doasyncfree) =2E/ufs/ffs/ffs_extern.h: { "doasyncfree", CTLTYPE_INT }, from ffs_alloc.c: /* * Next we must write out the modified inode and indirect blocks. * For strict correctness, the writes should be synchronous since * the old block values may have been written to disk. In practise * they are almost never written, but if we are concerned about * strict correctness, the `doasyncfree' flag should be set to zero. * * The test on `doasyncfree' should be changed to test a flag * that shows whether the associated buffers and inodes have * been written. The flag should be set when the cluster is * started and cleared whenever the buffer or inode is flushed. * We can then check below to see if it is set, and do the * synchronous write only when it has been cleared. */ cheers, /k --=20 > MCSE: Minesweeper Consultant & Solitaire Engineer KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --JI+G0+mN8WmwPnOn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7ZtZYM0BPTilkv0YRAgxeAJ9E/DYSrAfeaVjZGYZV2p/KZbAkZgCeI4xS wXFAmg/7AD/hBrWwmxMAK3g= =nFA5 -----END PGP SIGNATURE----- --JI+G0+mN8WmwPnOn-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 9: 1:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3F25837B401; Tue, 31 Jul 2001 09:01:51 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6VG1iF88897; Tue, 31 Jul 2001 10:01:45 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6VG1iw49778; Tue, 31 Jul 2001 10:01:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107311601.f6VG1iw49778@harmony.village.org> To: Dima Dorfman Subject: Re: portmap_enable vs. rpcbind_enable Cc: hackers@FreeBSD.ORG, alfred@FreeBSD.ORG In-reply-to: Your message of "Tue, 31 Jul 2001 04:48:41 PDT." <20010731114846.42FA73E2F@bazooka.unixfreak.org> References: <20010731114846.42FA73E2F@bazooka.unixfreak.org> Date: Tue, 31 Jul 2001 10:01:44 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010731114846.42FA73E2F@bazooka.unixfreak.org> Dima Dorfman writes: : Does anybody know (remember?) why portmap_enable (the rc.conf knob) : wasn't renamed to rpcbind_enable when portmap became rpcbind? It : seems odd to have a knob called portmap_enable that actually starts : something called rpcbind (not to mention violating POLA). Because we didn't want to break old people's config files. Also, the rpcbind rename was stupid and there were people at the time that had hoped it be renamed portmap since that was a bigger pola :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 9: 6:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 0FBBE37B403 for ; Tue, 31 Jul 2001 09:06:50 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E59A481D05; Tue, 31 Jul 2001 11:06:49 -0500 (CDT) Date: Tue, 31 Jul 2001 11:06:49 -0500 From: Alfred Perlstein To: Dima Dorfman Cc: David Malone , Dan Nelson , hackers@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable Message-ID: <20010731110649.Z26571@elvis.mu.org> References: <20010731163832.A91014@walton.maths.tcd.ie> <20010731154633.68EBB3E35@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010731154633.68EBB3E35@bazooka.unixfreak.org>; from dima@unixfreak.org on Tue, Jul 31, 2001 at 08:46:28AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Dima Dorfman [010731 10:53] wrote: > David Malone writes: > > On Tue, Jul 31, 2001 at 08:33:59AM -0700, Dima Dorfman wrote: > > > Dan Nelson writes: > > > > In the last episode (Jul 31), Dima Dorfman said: > > > > > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > > > > > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > > > > > seems odd to have a knob called portmap_enable that actually starts > > > > > something called rpcbind (not to mention violating POLA). > > > > > > > > Probably to keep existing rc.conf's from breaking. Same reason we've > > > > still got xntpd_enable. > > > > > > Why not change the names now, but keep the old ones working until, > > > say, 5.0 is branched? People moving from 4.x will have enough hurdles > > > to jump through as it is, and those using -current will have half a > > > year to change it. > > > > It still is an extra change for people updating from 4.X to 5.0. > > Maybe we should just make a portmap_program variable which is set > > to portmap in -stable and rpcbind in -current. At least things > > would be orthogonal then. > > That's what we already have, but we still have a knob that says it > will start 'portmap' starting something called 'rpcbind', and the user > didn't explicitly ask for that. If people think it's too much > trouble, though, I'm not going to press the issue. I think the main issue was to protect those that specifically turned portmap off from having rpc_bind turn it on. Since portmap and rpcbind are pretty much the same program it made sense at the time to at least keep the old name valid in absence of a specific rpcbind_enable flag. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 9:29:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 16B6A37B401; Tue, 31 Jul 2001 09:29:38 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA34991; Tue, 31 Jul 2001 11:21:59 -0700 (PDT) Date: Tue, 31 Jul 2001 11:21:58 -0700 (PDT) From: Julian Elischer To: Anjali Kulkarni Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: inet_aton In-Reply-To: <007601c11999$865df600$0a00a8c0@indranet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I think Warner Losh may have already done this.... On Tue, 31 Jul 2001, Anjali Kulkarni wrote: > Hi, > > Thanks for your response. > The reason I am trying to use inet_aton is because I am writing a kernel > proxy which connects to a webserver etc. etc. > So, I need to convert the server's ip address to the network byte address, > and hence I need to use this function. I do not see how else I can get the > network address from the ip address I have, except by using inet_aton??? > > Thanks, > Anjali > > ----- Original Message ----- > From: Mike Smith > To: Anjali Kulkarni > Cc: > Sent: Sunday, July 29, 2001 1:52 AM > Subject: Re: inet_aton > > > > > I want to use the function inet_aton() in the kernel code. However, I = > > > found no kernel equivalent of this function int the freebsd sources. I = > > > could find inet_ntoa(), but not inet_aton(). Is it named by some other = > > > name or how can I locate it? > > > > If you are trying to parse an ascii internet address in the kernel, > > you're quite possibly making a bad design mistake - why is it still in > > text format? If you're passing it in from another program, you should be > > passing a sockaddr struct. > > > > Failing that, you'll just have to steal the code from libc and bring it > > in yourself. > > > > -- > > ... every activity meets with opposition, everyone who acts has his > > rivals and unfortunately opponents also. But not because people want > > to be opponents, rather because the tasks and relationships force > > people to take different points of view. [Dr. Fritz Todt] > > V I C T O R Y N O T V E N G E A N C E > > > > > > > > > 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 Jul 31 9:38:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 4094637B401; Tue, 31 Jul 2001 09:38:22 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6VGcGr72889; Tue, 31 Jul 2001 17:38:16 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6VGcFc56314; Tue, 31 Jul 2001 17:38:15 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200107311638.f6VGcFc56314@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Warner Losh Cc: Dima Dorfman , hackers@FreeBSD.ORG, alfred@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: portmap_enable vs. rpcbind_enable In-Reply-To: Message from Warner Losh of "Tue, 31 Jul 2001 10:01:44 MDT." <200107311601.f6VG1iw49778@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 31 Jul 2001 17:38:15 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message <20010731114846.42FA73E2F@bazooka.unixfreak.org> Dima Dorfman writes: > : Does anybody know (remember?) why portmap_enable (the rc.conf knob) > : wasn't renamed to rpcbind_enable when portmap became rpcbind? It > : seems odd to have a knob called portmap_enable that actually starts > : something called rpcbind (not to mention violating POLA). > > Because we didn't want to break old people's config files. Also, the > rpcbind rename was stupid and there were people at the time that had > hoped it be renamed portmap since that was a bigger pola :-) Are you referring to grog & bde only ? > Warner -- Brian http://www.freebsd-services.com/ 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 Tue Jul 31 9:47:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 80DEA37B401; Tue, 31 Jul 2001 09:47:53 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6VGlpF89086; Tue, 31 Jul 2001 10:47:52 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6VGlpw50279; Tue, 31 Jul 2001 10:47:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107311647.f6VGlpw50279@harmony.village.org> To: Brian Somers Subject: Re: portmap_enable vs. rpcbind_enable Cc: Dima Dorfman , hackers@FreeBSD.ORG, alfred@FreeBSD.ORG In-reply-to: Your message of "Tue, 31 Jul 2001 17:38:15 BST." <200107311638.f6VGcFc56314@hak.lan.Awfulhak.org> References: <200107311638.f6VGcFc56314@hak.lan.Awfulhak.org> Date: Tue, 31 Jul 2001 10:47:51 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200107311638.f6VGcFc56314@hak.lan.Awfulhak.org> Brian Somers writes: : > In message <20010731114846.42FA73E2F@bazooka.unixfreak.org> Dima Dorfman writes: : > : Does anybody know (remember?) why portmap_enable (the rc.conf knob) : > : wasn't renamed to rpcbind_enable when portmap became rpcbind? It : > : seems odd to have a knob called portmap_enable that actually starts : > : something called rpcbind (not to mention violating POLA). : > : > Because we didn't want to break old people's config files. Also, the : > rpcbind rename was stupid and there were people at the time that had : > hoped it be renamed portmap since that was a bigger pola :-) : : Are you referring to grog & bde only ? There were a fair number of people that wanted the name to remain the same... I want it to remaint he same, but I don't care enough to fight. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 9:56:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id F2ABB37B401; Tue, 31 Jul 2001 09:56:30 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6VGuQF89132; Tue, 31 Jul 2001 10:56:26 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6VGuPw50434; Tue, 31 Jul 2001 10:56:25 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107311656.f6VGuPw50434@harmony.village.org> To: Julian Elischer Subject: Re: inet_aton Cc: Anjali Kulkarni , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 31 Jul 2001 11:21:58 PDT." References: Date: Tue, 31 Jul 2001 10:56:25 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Julian Elischer writes: : I think Warner Losh may have already done this.... I don't think I've done this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 10:14:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 8D31137B403; Tue, 31 Jul 2001 10:14:24 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6VHEMr73111; Tue, 31 Jul 2001 18:14:22 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f6VHELc56967; Tue, 31 Jul 2001 18:14:21 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200107311714.f6VHELc56967@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Warner Losh Cc: Brian Somers , Dima Dorfman , hackers@FreeBSD.ORG, alfred@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: portmap_enable vs. rpcbind_enable In-Reply-To: Message from Warner Losh of "Tue, 31 Jul 2001 10:47:51 MDT." <200107311647.f6VGlpw50279@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 31 Jul 2001 18:14:21 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message <200107311638.f6VGcFc56314@hak.lan.Awfulhak.org> Brian Somers writes: > : > In message <20010731114846.42FA73E2F@bazooka.unixfreak.org> Dima Dorfman writes: > : > : Does anybody know (remember?) why portmap_enable (the rc.conf knob) > : > : wasn't renamed to rpcbind_enable when portmap became rpcbind? It > : > : seems odd to have a knob called portmap_enable that actually starts > : > : something called rpcbind (not to mention violating POLA). > : > > : > Because we didn't want to break old people's config files. Also, the ^^^^^^^^^^ > : > rpcbind rename was stupid and there were people at the time that had > : > hoped it be renamed portmap since that was a bigger pola :-) > : > : Are you referring to grog & bde only ? > > There were a fair number of people that wanted the name to remain the > same... I want it to remaint he same, but I don't care enough to > fight. I was actually making a smart arse comment about your wording :*) > Warner -- Brian http://www.freebsd-services.com/ 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 Tue Jul 31 10:58:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4D06937B401; Tue, 31 Jul 2001 10:58:35 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.4/8.11.4) with SMTP id f6VHwWf47779; Tue, 31 Jul 2001 13:58:32 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 31 Jul 2001 13:58:32 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org Cc: hackers@FreeBSD.org Subject: REMINDER: FreeBSD Monthly Development Status Report -- Request For Submissions (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG First of (n) reminders, where the value of (n) will depend on how many reports are submitted :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Sat, 28 Jul 2001 18:26:31 -0400 (EDT) From: Robert Watson To: freebsd-hackers@FreeBSD.org, developers@FreeBSD.org Subject: FreeBSD Monthly Development Status Report -- Request For Submissions It's that time again! The last FreeBSD Development Status report was over a month ago, and given its success, we'll try it again this month. As with the previous edition, I'm interested in seeing about one paragraph per on-going project (or for major projects, a paragraph for each major component of the project) describing work that has happened since the last report. If no prior report has been given for the project, a general overview paragraph as well as status is acceptable. If more than one person is working on a project, only a single report should be submitted (although if there are reports for components, they might be seperately submitted by the relevant developers). Take a look at the previous month's report for a sense of how this works (in particular, see how TrustedBSD and SMPng reports were broken out). Developers should feel free to submit more than one report, if they are working on more than one project. Reports should relate to the FreeBSD Project, but are not limited to software development: they could include documentation work, web work, FreeBSD.org cluster management, cooperation with application developers, public relations activities, partnering with companies, funding announcements for new projects, etc. In the past report the primary focus was development, and that will remain important to the status report, of course, but other parts of the FreeBSD Project are welcome to submit status! Please submit reports in the following format: Project: (name here -- required) URL: (URL, if any, here -- omit line if none) Contact: (name and e-mail address of a contact point -- required) One paragraph on the topic of the project status since the last report, indented two spaces, and wrapped before column 78. Plain text only, please. Please send submissions to: robert+freebsd.monthly@cyrus.watson.org The deadline for submissions is Friday August 3, 2001, at 3:00pm EST. The report will be released soon thereafter. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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 Jul 31 11:47: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id E24CD37B403; Tue, 31 Jul 2001 11:46:09 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f6VIk9q16945; Tue, 31 Jul 2001 11:46:09 -0700 Date: Tue, 31 Jul 2001 11:46:09 -0700 From: Brooks Davis To: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: review request: vlan cloning and modularization patch Message-ID: <20010731114609.A16327@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730155207.A19629@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Mon, Jul 30, 2001 at 03:52:07PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've updated the patch to fix a bug in ether_input and wrap vlan_input(_tag) in marcos to enable locking later. This patch also reflects the latest fixes to the txp driver. I've included it below or you can find it at: http://people.freebsd.org/~brooks/patches/vlan.diff Apply the patch as before. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 Index: share/man/man4/vlan.4 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/share/man/man4/vlan.4,v retrieving revision 1.1 diff -u -r1.1 vlan.4 --- share/man/man4/vlan.4 2001/07/28 12:27:06 1.1 +++ share/man/man4/vlan.4 2001/07/30 22:38:49 @@ -33,7 +33,7 @@ .Nd IEEE 802.1Q VLAN network interface .Sh SYNOPSIS .\" In -stable: .Cd pseudo-device vlan Op Ar count -.Cd device vlan Op Ar count +.Cd device vlan .\" .Sh DESCRIPTION The Index: sys/conf/files =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/conf/files,v retrieving revision 1.555 diff -u -r1.555 files --- sys/conf/files 2001/07/26 23:04:46 1.555 +++ sys/conf/files 2001/07/30 22:33:18 @@ -907,7 +907,7 @@ net/if_stf.c optional stf net/if_tun.c optional tun net/if_tap.c optional tap -net/if_vlan.c count vlan +net/if_vlan.c optional vlan net/intrq.c standard net/net_osdep.c standard net/ppp_deflate.c optional ppp_deflate @@ -1020,8 +1020,11 @@ netgraph/ng_echo.c optional netgraph_echo netgraph/ng_ether.c optional netgraph_ether netgraph/ng_frame_relay.c optional netgraph_frame_relay +netgraph/ng_gif.c optional netgraph_gif +netgraph/ng_gif_demux.c optional netgraph_gif_demux netgraph/ng_hole.c optional netgraph_hole netgraph/ng_iface.c optional netgraph_iface +netgraph/ng_ip_input.c optional netgraph_ip_input netgraph/ng_ksocket.c optional netgraph_ksocket netgraph/ng_lmi.c optional netgraph_lmi netgraph/ng_mppc.c optional netgraph_mppc_compression Index: sys/dev/nge/if_nge.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/nge/if_nge.c,v retrieving revision 1.19 diff -u -r1.19 if_nge.c --- sys/dev/nge/if_nge.c 2001/07/25 00:19:55 1.19 +++ sys/dev/nge/if_nge.c 2001/07/31 00:23:42 @@ -87,8 +87,6 @@ * if the user selects an MTU larger than 8152 (8170 - 18). */ =20 -#include "vlan.h" - #include #include #include @@ -102,11 +100,8 @@ #include #include #include - -#if NVLAN > 0 #include #include -#endif =20 #include =20 @@ -1335,16 +1330,14 @@ m->m_pkthdr.csum_data =3D 0xffff; } =20 -#if NVLAN > 0 /* * If we received a packet with a vlan tag, pass it * to vlan_input() instead of ether_input(). */ if (extsts & NGE_RXEXTSTS_VLANPKT) { - vlan_input_tag(eh, m, extsts & NGE_RXEXTSTS_VTCI); + VLAN_INPUT_TAG(ifp, eh, m, extsts & NGE_RXEXTSTS_VTCI); continue; } -#endif =20 ether_input(ifp, eh, m); } @@ -1539,14 +1532,12 @@ struct nge_desc *f =3D NULL; struct mbuf *m; int frag, cur, cnt =3D 0; -#if NVLAN > 0 struct ifvlan *ifv =3D NULL; =20 if ((m_head->m_flags & (M_PROTO1|M_PKTHDR)) =3D=3D (M_PROTO1|M_PKTHDR) && m_head->m_pkthdr.rcvif !=3D NULL && m_head->m_pkthdr.rcvif->if_type =3D=3D IFT_L2VLAN) ifv =3D m_head->m_pkthdr.rcvif->if_softc; -#endif =20 /* * Start packing the mbufs in this chain into @@ -1588,12 +1579,10 @@ NGE_TXEXTSTS_UDPCSUM; } =20 -#if NVLAN > 0 if (ifv !=3D NULL) { sc->nge_ldata->nge_tx_list[cur].nge_extsts |=3D (NGE_TXEXTSTS_VLANPKT|ifv->ifv_tag); } -#endif =20 sc->nge_ldata->nge_tx_list[cur].nge_mbuf =3D m_head; sc->nge_ldata->nge_tx_list[cur].nge_ctl &=3D ~NGE_CMDSTS_MORE; @@ -1754,7 +1743,6 @@ */ CSR_WRITE_4(sc, NGE_VLAN_IP_RXCTL, NGE_VIPRXCTL_IPCSUM_ENB); =20 -#if NVLAN > 0 /* * If VLAN support is enabled, tell the chip to detect * and strip VLAN tag info from received frames. The tag @@ -1762,7 +1750,6 @@ */ NGE_SETBIT(sc, NGE_VLAN_IP_RXCTL, NGE_VIPRXCTL_TAG_DETECT_ENB|NGE_VIPRXCTL_TAG_STRIP_ENB); -#endif =20 /* Set TX configuration */ CSR_WRITE_4(sc, NGE_TX_CFG, NGE_TXCFG); @@ -1772,14 +1759,12 @@ */ CSR_WRITE_4(sc, NGE_VLAN_IP_TXCTL, NGE_VIPTXCTL_CSUM_PER_PKT); =20 -#if NVLAN > 0 /* * If VLAN support is enabled, tell the chip to insert * VLAN tags on a per-packet basis as dictated by the * code in the frame encapsulation routine. */ NGE_SETBIT(sc, NGE_VLAN_IP_TXCTL, NGE_VIPTXCTL_TAG_PER_PKT); -#endif =20 /* Set full/half duplex mode. */ if ((mii->mii_media_active & IFM_GMASK) =3D=3D IFM_FDX) { Index: sys/dev/txp/if_txp.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/txp/if_txp.c,v retrieving revision 1.5 diff -u -r1.5 if_txp.c --- sys/dev/txp/if_txp.c 2001/07/31 16:38:58 1.5 +++ sys/dev/txp/if_txp.c 2001/07/31 18:27:57 @@ -39,8 +39,6 @@ * Driver for 3c990 (Typhoon) Ethernet ASIC */ =20 -#include "vlan.h" - #include #include #include @@ -54,6 +52,7 @@ #include #include #include +#include =20 #include #include @@ -66,10 +65,6 @@ =20 #include =20 -#if NVLAN > 0 -#include -#endif - #include /* for vtophys */ #include /* for vtophys */ #include /* for DELAY */ @@ -809,14 +804,11 @@ /* Remove header from mbuf and pass it on. */ m_adj(m, sizeof(struct ether_header)); =20 -#if NVLAN > 0 if (rxd->rx_stat & RX_STAT_VLAN) { - if (vlan_input_tag(eh, m, - htons(rxd->rx_vlan >> 16)) < 0) - ifp->if_noproto++; + VLAN_INPUT_TAG(ifp, eh, m, htons(rxd->rx_vlan >> 16)); goto next; } -#endif + ether_input(ifp, eh, m); =20 next: @@ -1317,9 +1309,7 @@ struct mbuf *m, *m0; struct txp_swdesc *sd; u_int32_t firstprod, firstcnt, prod, cnt; -#if NVLAN > 0 struct ifvlan *ifv; -#endif =20 if ((ifp->if_flags & (IFF_RUNNING | IFF_OACTIVE)) !=3D IFF_RUNNING) return; @@ -1356,14 +1346,13 @@ if (++cnt >=3D (TX_ENTRIES - 4)) goto oactive; =20 -#if NVLAN > 0 if ((m->m_flags & (M_PROTO1|M_PKTHDR)) =3D=3D (M_PROTO1|M_PKTHDR) && m->m_pkthdr.rcvif !=3D NULL) { ifv =3D m->m_pkthdr.rcvif->if_softc; txd->tx_pflags =3D TX_PFLAGS_VLAN | (htons(ifv->ifv_tag) << TX_PFLAGS_VLANTAG_S); } -#endif + if (m->m_pkthdr.csum_flags & CSUM_IP) txd->tx_pflags |=3D TX_PFLAGS_IPCKSUM; =20 @@ -1879,12 +1868,10 @@ sc->sc_tx_capability =3D ext->ext_1 & OFFLOAD_MASK; sc->sc_rx_capability =3D ext->ext_2 & OFFLOAD_MASK; =20 -#if NVLAN > 0 if (rsp->rsp_par2 & rsp->rsp_par3 & OFFLOAD_VLAN) { sc->sc_tx_capability |=3D OFFLOAD_VLAN; sc->sc_rx_capability |=3D OFFLOAD_VLAN; } -#endif =20 #if 0 /* not ready yet */ Index: sys/i386/conf/NOTES =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/i386/conf/NOTES,v retrieving revision 1.942 diff -u -r1.942 NOTES --- sys/i386/conf/NOTES 2001/07/25 00:15:02 1.942 +++ sys/i386/conf/NOTES 2001/07/31 00:48:01 @@ -517,7 +517,7 @@ # See pppd(8) for more details. # device ether #Generic Ethernet -device vlan 1 #VLAN support +device vlan #VLAN support device token #Generic TokenRing device fddi #Generic FDDI device sppp #Generic Synchronous PPP Index: sys/net/ethernet.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/ethernet.h,v retrieving revision 1.16 diff -u -r1.16 ethernet.h --- sys/net/ethernet.h 2000/07/18 22:44:52 1.16 +++ sys/net/ethernet.h 2001/07/31 00:45:51 @@ -99,6 +99,41 @@ extern void (*ng_ether_attach_p)(struct ifnet *ifp); extern void (*ng_ether_detach_p)(struct ifnet *ifp); =20 +extern int (*vlan_input_p)(struct ether_header *eh, struct mbuf *m); +extern int (*vlan_input_tag_p)(struct ether_header *eh, struct mbuf *m, + u_int16_t t); +#define _VLAN_INPUT(ifp, eh, m) do { \ + if (vlan_input_p !=3D NULL) { \ + if ((*vlan_input_p)(eh, m) =3D=3D -1) \ + (ifp)->if_noproto++; \ + } else { \ + m_free(m); \ + (ifp)->if_noproto++; \ + } \ +} while (0) + +#define VLAN_INPUT(ifp, eh, m) do { \ + /* XXX: lock */ \ + _VLAN_INPUT(ifp, eh, m); \ + /* XXX: unlock */ \ +} while (0) + +#define _VLAN_INPUT_TAG(ifp, eh, m, t) do { \ + if (vlan_input_tag_p !=3D NULL) { \ + if ((*vlan_input_tag_p)(eh, m, t) =3D=3D -1) \ + (ifp)->if_noproto++; \ + } else { \ + m_free(m); \ + (ifp)->if_noproto++; \ + } \ +} while (0) + +#define VLAN_INPUT_TAG(ifp, eh, m, t) do { \ + /* XXX: lock */ \ + _VLAN_INPUT_TAG(ifp, eh, m, t); \ + /* XXX: unlock */ \ +} while (0) + #else /* _KERNEL */ =20 #include Index: sys/net/if_ethersubr.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/if_ethersubr.c,v retrieving revision 1.94 diff -u -r1.94 if_ethersubr.c --- sys/net/if_ethersubr.c 2001/06/15 21:00:32 1.94 +++ sys/net/if_ethersubr.c 2001/07/31 00:18:02 @@ -39,7 +39,6 @@ #include "opt_inet6.h" #include "opt_ipx.h" #include "opt_bdg.h" -#include "opt_netgraph.h" =20 #include #include @@ -101,11 +100,6 @@ #include #endif =20 -#include "vlan.h" -#if NVLAN > 0 -#include -#endif /* NVLAN > 0 */ - /* netgraph node hooks for ng_ether(4) */ void (*ng_ether_input_p)(struct ifnet *ifp, struct mbuf **mp, struct ether_header *eh); @@ -115,6 +109,10 @@ void (*ng_ether_attach_p)(struct ifnet *ifp); void (*ng_ether_detach_p)(struct ifnet *ifp); =20 +int (*vlan_input_p)(struct ether_header *eh, struct mbuf *m); +int (*vlan_input_tag_p)(struct ether_header *eh, struct mbuf *m, + u_int16_t t); + static int ether_resolvemulti __P((struct ifnet *, struct sockaddr **, struct sockaddr *)); u_char etherbroadcastaddr[6] =3D { 0xff, 0xff, 0xff, 0xff, 0xff, 0xff }; @@ -524,14 +522,6 @@ =20 ether_type =3D ntohs(eh->ether_type); =20 -#if NVLAN > 0 - if (ether_type =3D=3D vlan_proto) { - if (vlan_input(eh, m) < 0) - ifp->if_data.ifi_noproto++; - return; - } -#endif /* NVLAN > 0 */ - switch (ether_type) { #ifdef INET case ETHERTYPE_IP: @@ -582,6 +572,9 @@ aarpinput(IFP2AC(ifp), m); /* XXX */ return; #endif NETATALK + case ETHERTYPE_VLAN: + VLAN_INPUT(ifp, eh, m); + return; default: #ifdef IPX if (ef_inputp && ef_inputp(ifp, eh, m) =3D=3D 0) Index: sys/net/if_vlan.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/if_vlan.c,v retrieving revision 1.30 diff -u -r1.30 if_vlan.c --- sys/net/if_vlan.c 2001/07/24 17:14:37 1.30 +++ sys/net/if_vlan.c 2001/07/27 00:19:01 @@ -54,7 +54,6 @@ * tag value that goes with it. */ =20 -#include "vlan.h" #include "opt_inet.h" =20 #include @@ -67,6 +66,8 @@ #include #include #include +#include /* XXX: Shouldn't really be required! */ +#include =20 #include #include @@ -81,23 +82,32 @@ #include #endif =20 +#define VLANNAME "vlan" +#define VLAN_MAXUNIT 0x7fff /* ifp->if_unit is only 15 bits */ + SYSCTL_DECL(_net_link); SYSCTL_NODE(_net_link, IFT_L2VLAN, vlan, CTLFLAG_RW, 0, "IEEE 802.1Q VLAN"= ); SYSCTL_NODE(_net_link_vlan, PF_LINK, link, CTLFLAG_RW, 0, "for consistency= "); - -u_int vlan_proto =3D ETHERTYPE_VLAN; -SYSCTL_INT(_net_link_vlan_link, VLANCTL_PROTO, proto, CTLFLAG_RW, &vlan_pr= oto, - 0, "Ethernet protocol used for VLAN encapsulation"); =20 -static struct ifvlan ifv_softc[NVLAN]; +static MALLOC_DEFINE(M_VLAN, "vlan", "802.1Q Virtual LAN Interface"); +static struct rman vlanunits[1]; +static LIST_HEAD(, ifvlan) ifv_list; =20 +static int vlan_clone_create(struct if_clone *, int *); +static void vlan_clone_destroy(struct ifnet *); static void vlan_start(struct ifnet *ifp); static void vlan_ifinit(void *foo); +static int vlan_input(struct ether_header *eh, struct mbuf *m); +static int vlan_input_tag(struct ether_header *eh, struct mbuf *m, + u_int16_t t); static int vlan_ioctl(struct ifnet *ifp, u_long cmd, caddr_t addr); static int vlan_setmulti(struct ifnet *ifp); static int vlan_unconfig(struct ifnet *ifp); static int vlan_config(struct ifvlan *ifv, struct ifnet *p); =20 +struct if_clone vlan_cloner =3D + IF_CLONE_INITIALIZER("vlan", vlan_clone_create, vlan_clone_destroy); + /* * Program our multicast filter. What we're actually doing is * programming the multicast filter of the parent. This has the @@ -142,14 +152,14 @@ if (error) return(error); SLIST_REMOVE_HEAD(&sc->vlan_mc_listhead, mc_entries); - free(mc, M_DEVBUF); + free(mc, M_VLAN); } =20 /* Now program new ones. */ TAILQ_FOREACH(ifma, &ifp->if_multiaddrs, ifma_link) { if (ifma->ifma_addr->sa_family !=3D AF_LINK) continue; - mc =3D malloc(sizeof(struct vlan_mc_entry), M_DEVBUF, M_WAITOK); + mc =3D malloc(sizeof(struct vlan_mc_entry), M_VLAN, M_WAITOK); bcopy(LLADDR((struct sockaddr_dl *)ifma->ifma_addr), (char *)&mc->mc_addr, ETHER_ADDR_LEN); SLIST_INSERT_HEAD(&sc->vlan_mc_listhead, mc, mc_entries); @@ -163,44 +173,40 @@ return(0); } =20 -static void -vlaninit(void) -{ - int i; - - for (i =3D 0; i < NVLAN; i++) { - struct ifnet *ifp =3D &ifv_softc[i].ifv_if; - - ifp->if_softc =3D &ifv_softc[i]; - ifp->if_name =3D "vlan"; - ifp->if_unit =3D i; - /* NB: flags are not set here */ - ifp->if_linkmib =3D &ifv_softc[i].ifv_mib; - ifp->if_linkmiblen =3D sizeof ifv_softc[i].ifv_mib; - /* NB: mtu is not set here */ - - ifp->if_init =3D vlan_ifinit; - ifp->if_start =3D vlan_start; - ifp->if_ioctl =3D vlan_ioctl; - ifp->if_output =3D ether_output; - ifp->if_snd.ifq_maxlen =3D ifqmaxlen; - ether_ifattach(ifp, ETHER_BPF_SUPPORTED); - /* Now undo some of the damage... */ - ifp->if_data.ifi_type =3D IFT_L2VLAN; - ifp->if_data.ifi_hdrlen =3D EVL_ENCAPLEN; - } -} - static int vlan_modevent(module_t mod, int type, void *data)=20 {=20 + int err; + switch (type) {=20 case MOD_LOAD:=20 - vlaninit(); + vlanunits->rm_type =3D RMAN_ARRAY; + vlanunits->rm_descr =3D "configurable if_vlan units"; + err =3D rman_init(vlanunits); + if (err !=3D 0) + return (err); + err =3D rman_manage_region(vlanunits, 0, VLAN_MAXUNIT); + if (err !=3D 0) { + printf("%s: vlanunits: rman_manage_region: Failed %d\n", + VLANNAME, err); + rman_fini(vlanunits); + return (err); + } + LIST_INIT(&ifv_list); + vlan_input_p =3D vlan_input; + vlan_input_tag_p =3D vlan_input_tag; + if_clone_attach(&vlan_cloner); break;=20 case MOD_UNLOAD:=20 - printf("if_vlan module unload - not possible for this module type\n");= =20 - return EINVAL;=20 + if_clone_detach(&vlan_cloner); + vlan_input_p =3D NULL; + vlan_input_tag_p =3D NULL; + while (!LIST_EMPTY(&ifv_list)) + vlan_clone_destroy(&LIST_FIRST(&ifv_list)->ifv_if); + err =3D rman_fini(vlanunits); + if (err !=3D 0) + return (err); + break; }=20 return 0;=20 }=20 @@ -213,7 +219,81 @@ =20 DECLARE_MODULE(if_vlan, vlan_mod, SI_SUB_PSEUDO, SI_ORDER_ANY); =20 +static int +vlan_clone_create(struct if_clone *ifc, int *unit) +{ + struct resource *r; + struct ifvlan *ifv; + struct ifnet *ifp; + int s; + + if (*unit > VLAN_MAXUNIT) + return (ENXIO); + + if (*unit < 0) { + r =3D rman_reserve_resource(vlanunits, 0, VLAN_MAXUNIT, 1, + RF_ALLOCATED | RF_ACTIVE, NULL); + if (r =3D=3D NULL) + return (ENOSPC); + *unit =3D rman_get_start(r); + } else { + r =3D rman_reserve_resource(vlanunits, *unit, *unit, 1, + RF_ALLOCATED | RF_ACTIVE, NULL); + if (r =3D=3D NULL) + return (EEXIST); + } + + ifv =3D malloc(sizeof(struct ifvlan), M_VLAN, M_WAITOK); + memset(ifv, 0, sizeof(struct ifvlan)); + ifp =3D &ifv->ifv_if; + SLIST_INIT(&ifv->vlan_mc_listhead); + + s =3D splnet(); + LIST_INSERT_HEAD(&ifv_list, ifv, ifv_list); + splx(s); + + ifp->if_softc =3D ifv; + ifp->if_name =3D "vlan"; + ifp->if_unit =3D *unit; + ifv->r_unit =3D r; + /* NB: flags are not set here */ + ifp->if_linkmib =3D &ifv->ifv_mib; + ifp->if_linkmiblen =3D sizeof ifv->ifv_mib; + /* NB: mtu is not set here */ + + ifp->if_init =3D vlan_ifinit; + ifp->if_start =3D vlan_start; + ifp->if_ioctl =3D vlan_ioctl; + ifp->if_output =3D ether_output; + ifp->if_snd.ifq_maxlen =3D ifqmaxlen; + ether_ifattach(ifp, ETHER_BPF_SUPPORTED); + /* Now undo some of the damage... */ + ifp->if_data.ifi_type =3D IFT_L2VLAN; + ifp->if_data.ifi_hdrlen =3D EVL_ENCAPLEN; + + return (0); +} + static void +vlan_clone_destroy(struct ifnet *ifp) +{ + struct ifvlan *ifv =3D ifp->if_softc; + int s; + int err; + + s =3D splnet(); + LIST_REMOVE(ifv, ifv_list); + vlan_unconfig(ifp); + splx(s); + + ether_ifdetach(ifp, ETHER_BPF_SUPPORTED); + + err =3D rman_release_resource(ifv->r_unit); + KASSERT(err =3D=3D 0, ("Unexpected error freeing resource")); + free(ifv, M_VLAN); +} + +static void vlan_ifinit(void *foo) { return; @@ -294,7 +374,7 @@ sizeof(struct ether_header)); evl =3D mtod(m, struct ether_vlan_header *); evl->evl_proto =3D evl->evl_encap_proto; - evl->evl_encap_proto =3D htons(vlan_proto); + evl->evl_encap_proto =3D htons(ETHERTYPE_VLAN); evl->evl_tag =3D htons(ifv->ifv_tag); #ifdef DEBUG printf("vlan_start: %*D\n", sizeof *evl, @@ -316,19 +396,18 @@ return; } =20 -int +static int vlan_input_tag(struct ether_header *eh, struct mbuf *m, u_int16_t t) { - int i; struct ifvlan *ifv; =20 - for (i =3D 0; i < NVLAN; i++) { - ifv =3D &ifv_softc[i]; + for (ifv =3D LIST_FIRST(&ifv_list); ifv !=3D NULL; + ifv =3D LIST_NEXT(ifv, ifv_list)) { if (ifv->ifv_tag =3D=3D t) break; } =20 - if (i >=3D NVLAN || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { + if (ifv !=3DNULL || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { m_free(m); return -1; /* So the parent can take note */ } @@ -345,21 +424,20 @@ return 0; } =20 -int +static int vlan_input(struct ether_header *eh, struct mbuf *m) { - int i; struct ifvlan *ifv; =20 - for (i =3D 0; i < NVLAN; i++) { - ifv =3D &ifv_softc[i]; + for (ifv =3D LIST_FIRST(&ifv_list); ifv !=3D NULL; + ifv =3D LIST_NEXT(ifv, ifv_list)) { if (m->m_pkthdr.rcvif =3D=3D ifv->ifv_p && (EVL_VLANOFTAG(ntohs(*mtod(m, u_int16_t *))) =3D=3D ifv->ifv_tag)) break; } =20 - if (i >=3D NVLAN || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { + if (ifv !=3D NULL || (ifv->ifv_if.if_flags & IFF_UP) =3D=3D 0) { m_freem(m); return -1; /* so ether_input can take note */ } @@ -462,7 +540,7 @@ if (error) return(error); SLIST_REMOVE_HEAD(&ifv->vlan_mc_listhead, mc_entries); - free(mc, M_DEVBUF); + free(mc, M_VLAN); } } =20 Index: sys/net/if_vlan_var.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/net/if_vlan_var.h,v retrieving revision 1.9 diff -u -r1.9 if_vlan_var.h --- sys/net/if_vlan_var.h 2001/07/24 00:03:51 1.9 +++ sys/net/if_vlan_var.h 2001/07/27 21:01:48 @@ -47,6 +47,8 @@ u_int16_t ifvm_tag; /* tag to apply on packets leaving if */ } ifv_mib; SLIST_HEAD(__vlan_mchead, vlan_mc_entry) vlan_mc_listhead; + LIST_ENTRY(ifvlan) ifv_list; + struct resource *r_unit; /* resource allocated for this unit */ }; #define ifv_if ifv_ac.ac_if #define ifv_tag ifv_mib.ifvm_tag @@ -77,13 +79,5 @@ }; #define SIOCSETVLAN SIOCSIFGENERIC #define SIOCGETVLAN SIOCGIFGENERIC - -#ifdef _KERNEL -/* shared with if_ethersubr.c: */ -extern u_int vlan_proto; -extern int vlan_input(struct ether_header *eh, struct mbuf *m); -extern int vlan_input_tag(struct ether_header *eh, - struct mbuf *m, u_int16_t t); -#endif =20 #endif /* _NET_IF_VLAN_VAR_H_ */ Index: sys/pci/if_ti.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/pci/if_ti.c,v retrieving revision 1.51 diff -u -r1.51 if_ti.c --- sys/pci/if_ti.c 2001/07/25 00:19:59 1.51 +++ sys/pci/if_ti.c 2001/07/31 00:21:47 @@ -78,8 +78,6 @@ * - Andrew Gallatin for providing FreeBSD/Alpha support. */ =20 -#include "vlan.h" - #include #include #include @@ -94,14 +92,11 @@ #include #include #include - -#include - -#if NVLAN > 0 #include #include -#endif =20 +#include + #include #include #include @@ -1334,9 +1329,7 @@ if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif =20 /* Set up the jumbo receive ring. */ rcb =3D &sc->ti_rdata->ti_info.ti_jumbo_rx_rcb; @@ -1347,9 +1340,7 @@ if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif =20 /* * Set up the mini ring. Only activated on the @@ -1367,9 +1358,7 @@ if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif =20 /* * Set up the receive return ring. @@ -1403,9 +1392,7 @@ rcb->ti_flags =3D 0; else rcb->ti_flags =3D TI_RCB_FLAG_HOST_RING; -#if NVLAN > 0 rcb->ti_flags |=3D TI_RCB_FLAG_VLAN_ASSIST; -#endif if (sc->arpcom.ac_if.if_hwassist) rcb->ti_flags |=3D TI_RCB_FLAG_TCP_UDP_CKSUM | TI_RCB_FLAG_IP_CKSUM | TI_RCB_FLAG_NO_PHDR_CKSUM; @@ -1738,22 +1725,18 @@ u_int32_t rxidx; struct ether_header *eh; struct mbuf *m =3D NULL; -#if NVLAN > 0 u_int16_t vlan_tag =3D 0; int have_tag =3D 0; -#endif =20 cur_rx =3D &sc->ti_rdata->ti_rx_return_ring[sc->ti_rx_saved_considx]; rxidx =3D cur_rx->ti_idx; TI_INC(sc->ti_rx_saved_considx, TI_RETURN_RING_CNT); =20 -#if NVLAN > 0 if (cur_rx->ti_flags & TI_BDFLAG_VLAN_TAG) { have_tag =3D 1; vlan_tag =3D cur_rx->ti_vlan_tag & 0xfff; } -#endif =20 if (cur_rx->ti_flags & TI_BDFLAG_JUMBO_RING) { TI_INC(sc->ti_jumbo, TI_JUMBO_RX_RING_CNT); @@ -1815,17 +1798,15 @@ m->m_pkthdr.csum_data =3D cur_rx->ti_tcp_udp_cksum; } =20 -#if NVLAN > 0 /* * If we received a packet with a vlan tag, pass it * to vlan_input() instead of ether_input(). */ if (have_tag) { - vlan_input_tag(eh, m, vlan_tag); + VLAN_INPUT_TAG(ifp, eh, m, vlan_tag); have_tag =3D vlan_tag =3D 0; continue; } -#endif ether_input(ifp, eh, m); } =20 @@ -1963,14 +1944,12 @@ struct mbuf *m; u_int32_t frag, cur, cnt =3D 0; u_int16_t csum_flags =3D 0; -#if NVLAN > 0 struct ifvlan *ifv =3D NULL; =20 if ((m_head->m_flags & (M_PROTO1|M_PKTHDR)) =3D=3D (M_PROTO1|M_PKTHDR) && m_head->m_pkthdr.rcvif !=3D NULL && m_head->m_pkthdr.rcvif->if_type =3D=3D IFT_L2VLAN) ifv =3D m_head->m_pkthdr.rcvif->if_softc; -#endif =20 m =3D m_head; cur =3D frag =3D *txidx; @@ -2013,14 +1992,14 @@ TI_HOSTADDR(f->ti_addr) =3D vtophys(mtod(m, vm_offset_t)); f->ti_len =3D m->m_len; f->ti_flags =3D csum_flags; -#if NVLAN > 0 + if (ifv !=3D NULL) { f->ti_flags |=3D TI_BDFLAG_VLAN_TAG; f->ti_vlan_tag =3D ifv->ifv_tag & 0xfff; } else { f->ti_vlan_tag =3D 0; } -#endif + /* * Sanity check: avoid coming within 16 descriptors * of the end of the ring. --- sys/modules/if_vlan/Makefile.orig Fri Jul 13 17:14:21 2001 +++ sys/modules/if_vlan/Makefile Fri Jul 27 14:00:14 2001 @@ -0,0 +1,12 @@ +# $FreeBSD$ + +.PATH: ${.CURDIR}/../../net + +KMOD=3D if_vlan +SRCS=3D if_vlan.c opt_inet.h +NOMAN=3D + +opt_inet.h: + echo "#define INET 1" > ${.TARGET} + +.include --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7ZvztXY6L6fI4GtQRAitUAKDCzY6h29Ka3WO/r+skpOM1VguFaQCePNri NcTwIVt7wdfInWrkZaOdkAs= =gm7s -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 12:49:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 761EE37B401; Tue, 31 Jul 2001 12:49:39 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA35791; Tue, 31 Jul 2001 14:41:41 -0700 (PDT) Date: Tue, 31 Jul 2001 14:41:39 -0700 (PDT) From: Julian Elischer To: Warner Losh Cc: Anjali Kulkarni , Mike Smith , freebsd-hackers@FreeBSD.ORG Subject: Re: inet_aton In-Reply-To: <200107311656.f6VGuPw50434@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hmm I thought it was you doing an in-kernel proxy? ah no wait it was an in-kernel server? (wasn't it?) On Tue, 31 Jul 2001, Warner Losh wrote: > In message Julian Elischer writes: > : I think Warner Losh may have already done this.... > > I don't think I've done this. > > Warner > > 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 Jul 31 12:55:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0CEEE37B401; Tue, 31 Jul 2001 12:55:18 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f6VJtFF89898; Tue, 31 Jul 2001 13:55:16 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f6VJtFw51934; Tue, 31 Jul 2001 13:55:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200107311955.f6VJtFw51934@harmony.village.org> To: Julian Elischer Subject: Re: inet_aton Cc: Anjali Kulkarni , Mike Smith , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 31 Jul 2001 14:41:39 PDT." References: Date: Tue, 31 Jul 2001 13:55:15 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Julian Elischer writes: : hmm I thought it was you doing an in-kernel proxy? : ah no wait it was an in-kernel server? : (wasn't it?) Neither. You have me confused with someone else. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 13:42:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f42.law10.hotmail.com [64.4.15.42]) by hub.freebsd.org (Postfix) with ESMTP id 3BBE437B401 for ; Tue, 31 Jul 2001 13:42:11 -0700 (PDT) (envelope-from bsd_mike@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 31 Jul 2001 13:42:10 -0700 Received: from 206.196.56.237 by lw10fd.law10.hotmail.msn.com with HTTP; Tue, 31 Jul 2001 20:42:10 GMT X-Originating-IP: [206.196.56.237] From: "Mike Dorin" To: freebsd-hackers@freebsd.org Subject: New to this Date: Tue, 31 Jul 2001 20:42:10 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 31 Jul 2001 20:42:10.0548 (UTC) FILETIME=[45721B40:01C11A01] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a freebsd system that locks up from time to time. Is it possible to recompile the kernel with gdb support and figure out where the lockup is occurring? Is there a better way to do that? Thanks, Mike _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 13:42:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from damgwp01.corp.sprint.com (parker2.sprint.com [199.14.91.106]) by hub.freebsd.org (Postfix) with ESMTP id 0E4B537B401 for ; Tue, 31 Jul 2001 13:42:37 -0700 (PDT) (envelope-from steve.d.meacham@mail.sprint.com) Received: from kcmgwp02.corp.sprint.com (kcmgwp02 [10.185.6.93]) by damgwp01.corp.sprint.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f6VKuWm06170 for ; Tue, 31 Jul 2001 15:56:32 -0500 (CDT) Received: from kcopmp01.corp.sprint.com (kcopmp01m.corp.sprint.com [10.74.2.72]) by kcmgwp02.corp.sprint.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f6VKgZf16739 for ; Tue, 31 Jul 2001 15:42:35 -0500 (CDT) Received: from localhost (root@localhost) by kcopmp01.corp.sprint.com (8.8.6 (PHNE_17190)/8.8.6) with ESMTP id PAA08544 for ; Tue, 31 Jul 2001 15:42:34 -0500 (CDT) From: steve.d.meacham@mail.sprint.com X-OpenMail-Hops: 1 Date: Tue, 31 Jul 2001 15:42:33 -0500 Message-Id: Subject: ie ethernet device fix needs to be committed MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline ;Creation-Date="Tue, 31 Jul 2001 15:42:33 -0500" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have machines which still use the ie ethernet driver. It no longer auto-detects without the following fix. Is it possible to get this fix commited? Having it MFC'd for the 4.4-RELEASE would be even better. This fix has been running on two machines still in production since sometime during 4.2-STABLE and works like a champ. Here's the fix: http://www.jfitz.com/tips/freebsd_etherexpress16.html Regards, Steven To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 14:38:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f195.pav2.hotmail.com [64.4.37.195]) by hub.freebsd.org (Postfix) with ESMTP id 9CB8037B406 for ; Tue, 31 Jul 2001 14:38:55 -0700 (PDT) (envelope-from weiguang_shi@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 31 Jul 2001 14:38:55 -0700 Received: from 129.128.29.128 by pv2fd.pav2.hotmail.msn.com with HTTP; Tue, 31 Jul 2001 21:38:54 GMT X-Originating-IP: [129.128.29.128] From: "Weiguang SHI" To: freebsd-hackers@freebsd.org Subject: address resolution question Date: Tue, 31 Jul 2001 15:38:54 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 31 Jul 2001 21:38:55.0196 (UTC) FILETIME=[32C629C0:01C11A09] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I need your help to understand this. In machdep.c, 1451 /* 1452 * map page 1 R/W into the kernel page table so we can use it 1453 * as a buffer. The kernel will unmap this page later. 1454 */ 1455 pte = (pt_entry_t)vtopte(KERNBASE + (1 <; Tue, 31 Jul 2001 15:50:29 -0700 (PDT) (envelope-from MichaelV@EDIFECS.COM) Received: from ecx1.edifecs.com (mail.edifecs.com [207.153.149.131]) by postal.edifecs.com (8.11.0/8.11.0) with ESMTP id f6VMwkT17026 for ; Tue, 31 Jul 2001 15:58:46 -0700 Received: by ecx1.edifecs.com with Internet Mail Service (5.5.2653.19) id ; Tue, 31 Jul 2001 15:56:43 -0700 Message-ID: <36F7B20351634E4FBFFE6C6A216B30D54C7F@ecx1.edifecs.com> From: Michael VanLoon To: "'hackers@freebsd.org'" Subject: Finding MAC address of interface - programming question Date: Tue, 31 Jul 2001 15:56:40 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Please point me to a more appropriate forum if there is one. I'm kinda out of my depth on this question. Pseudo code is fine. :-) What I'm looking for is how to enumerate the network interfaces and get the Ethernet MAC address of one programmatically. Can anyone point me in the right direction? Thanks much! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 15:56: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 4358137B403 for ; Tue, 31 Jul 2001 15:55:53 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by peitho.fxp.org (Postfix, from userid 1501) id B53ED13618; Tue, 31 Jul 2001 18:55:52 -0400 (EDT) Date: Tue, 31 Jul 2001 18:55:52 -0400 From: Chris Faulhaber To: Michael VanLoon Cc: "'hackers@freebsd.org'" Subject: Re: Finding MAC address of interface - programming question Message-ID: <20010731185552.A61247@peitho.fxp.org> References: <36F7B20351634E4FBFFE6C6A216B30D54C7F@ecx1.edifecs.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <36F7B20351634E4FBFFE6C6A216B30D54C7F@ecx1.edifecs.com> User-Agent: Mutt/1.3.20i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > Please point me to a more appropriate forum if there is one. I'm kinda o= ut > of my depth on this question. Pseudo code is fine. :-) >=20 > What I'm looking for is how to enumerate the network interfaces and get t= he > Ethernet MAC address of one programmatically. Can anyone point me in the > right direction? >=20 /usr/src/sbin/ifconfig --=20 Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: FreeBSD: The Power To Serve iEYEARECAAYFAjtnN3gACgkQObaG4P6BelAc6wCePgdeyZdr5Q37i3Zwex4hdWzQ daYAn1qobTPMW2k5W1l+kGbC2pVaHq45 =RBMv -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 15:57:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from forbidden.dough.net (forbidden.dough.net [24.219.84.23]) by hub.freebsd.org (Postfix) with ESMTP id 9F63437B403 for ; Tue, 31 Jul 2001 15:57:23 -0700 (PDT) (envelope-from archon@forbidden.dough.net) Received: (from archon@localhost) by forbidden.dough.net (8.11.4/8.9.3) id f6VMvML20134 for hackers@freebsd.org; Tue, 31 Jul 2001 17:57:22 -0500 (CDT) (envelope-from archon) Date: Tue, 31 Jul 2001 17:57:22 -0500 From: Dennis Moore To: hackers@freebsd.org Subject: crash dump output Message-ID: <20010731175722.A20105@forbidden.dough.net> Mail-Followup-To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i don't know if this yields any useful information.. the machine crashed a few times under heavy disk i/o the other day so i set up a crash device. then today it crashed while i was compiling something. FreeBSD 4.3-STABLE #0: Thu Jun 21 22:43:18 CDT 2001 SMP 2 cpus IdlePTD 3403776 initial pcb at 2aa9e0 panicstr: general protection fault panic messages: --- Fatal trap 9: general protection fault while in kernel mode mp_lock =3D 00000002; cpuid =3D 0; lapic.id =3D 00000000 instruction pointer =3D 0x8:0xc0239bfe stack pointer =3D 0x10:0xff806f78 frame pointer =3D 0x10:0xff806f88 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D Idle interrupt mask =3D net tty bio cam <- SMP: XXX trap number =3D 9 panic: general protection fault mp_lock =3D 00000002; cpuid =3D 0; lapic.id =3D 00000000 boot() called on cpu#0 syncing disks... 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 49 giving up on 48 buffers Uptime: 4d15h26m12s dumping to dev #da/0x20007, offset 270336 dump 768 767 766 765 764 763 762 761 760 759 758 757 756 755 754 753 752 75= 1 750 749 748 747 746 745 744 743 742 741 740 739 738 737 736 735 734 733 7= 32 731 730 729 728 727 726 725 724 723 722 721 720 719 718 717 716 715 714 = 713 712 711 710 709 708 707 706 705 704 703 702 701 700 699 698 697 696 695= 694 693 692 691 690 689 688 687 686 685 684 683 682 681 680 679 678 677 67= 6 675 674 673 672 671 670 669 668 667 666 665 664 663 662 661 660 659 658 6= 57 656 655 654 653 652 651 650 649 648 647 646 645 644 643 642 641 640 639 = 638 637 636 635 634 633 632 631 630 629 628 627 626 625 624 623 622 621 620= 619 618 617 616 615 614 613 612 611 610 609 608 607 606 605 604 603 602 60= 1 600 599 598 597 596 595 594 593 592 591 590 589 588 587 586 585 584 583 5= 82 581 580 579 578 577 576 575 574 573 572 571 570 569 568 567 566 565 564 = 563 562 561 560 559 558 557 556 555 554 553 552 551 550 549 548 547 546 545= 544 543 542 541 540 539 538 537 536 535 534 533 532 531 530 529 528 527 52= 6 525 524 523 522 521 520 519 518 517 516 515 514 513 512 511 510 509 508 5= 07 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 = 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470= 469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 45= 1 450 449 448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 4= 32 431 430 429 428 427 426 425 424 423 422 421 420 419 418 417 416 415 414 = 413 412 411 410 409 408 407 406 405 404 403 402 401 400 399 398 397 396 395= 394 393 392 391 390 389 388 387 386 385 384 383 382 381 380 379 378 377 37= 6 375 374 373 372 371 370 369 368 367 366 365 364 363 362 361 360 359 358 3= 57 356 355 354 353 352 351 350 349 348 347 346 345 344 343 342 341 340 339 = 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 323 322 321 320= 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 304 303 302 30= 1 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 285 284 283 2= 82 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 266 265 264 = 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 247 246 245= 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 228 227 22= 6 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208 2= 07 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 189 = 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170= 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 15= 1 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 1= 32 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 = 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 9= 3 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 6= 8 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 4= 3 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 1= 8 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xc015dd16 in dumpsys () (kgdb) where #0 0xc015dd16 in dumpsys () #1 0xc015db37 in boot () #2 0xc015dee8 in poweroff_wait () #3 0xc023f39b in trap_fatal () #4 0xc023ed17 in trap () #5 0xc0239bfe in forward_hardclock () #6 0xc01516cf in hardclock () #7 0xc0243e0d in clkintr () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 16: 2:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 96BB937B401 for ; Tue, 31 Jul 2001 16:02:23 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id QAA05939; Tue, 31 Jul 2001 16:02:11 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010731175722.A20105@forbidden.dough.net> Date: Tue, 31 Jul 2001 16:02:12 -0700 (PDT) From: John Baldwin To: Dennis Moore Subject: RE: crash dump output Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 31-Jul-01 Dennis Moore wrote: > i don't know if this yields any useful information.. the machine crashed a > few times under heavy disk i/o the other day so i set up a crash device. > then today it crashed while i was compiling something. Can you compile a debug kernel please and repeat this? That way you will have debug symbols so that you can get more useful information out of gdb. You'll have to get a new crashdump with the debug kernel running however. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Tue Jul 31 16: 6:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postal.edifecs.com (unknown [207.149.212.48]) by hub.freebsd.org (Postfix) with ESMTP id BD21A37B401 for ; Tue, 31 Jul 2001 16:06:42 -0700 (PDT) (envelope-from MichaelV@EDIFECS.COM) Received: from ecx1.edifecs.com (mail.edifecs.com [207.153.149.131]) by postal.edifecs.com (8.11.0/8.11.0) with ESMTP id f6VNEbT17070; Tue, 31 Jul 2001 16:14:38 -0700 Received: by ecx1.edifecs.com with Internet Mail Service (5.5.2653.19) id ; Tue, 31 Jul 2001 16:12:35 -0700 Message-ID: <36F7B20351634E4FBFFE6C6A216B30D54C80@ecx1.edifecs.com> From: Michael VanLoon To: "'Chris Faulhaber'" Cc: "'hackers@freebsd.org'" Subject: RE: Finding MAC address of interface - programming question Date: Tue, 31 Jul 2001 16:12:31 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: Chris Faulhaber [mailto:jedgar@fxp.org] > Sent: Tuesday, July 31, 2001 3:56 PM > > On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > > Please point me to a more appropriate forum if there is > one. I'm kinda out > > of my depth on this question. Pseudo code is fine. :-) > > > > What I'm looking for is how to enumerate the network > interfaces and get the > > Ethernet MAC address of one programmatically. Can anyone > point me in the > > right direction? > > > > /usr/src/sbin/ifconfig Thanks, I've already been looking at that. :-) The problem is, ifconfig does a lot of other stuff, and it's very poorly documented. I was hoping someone could give me some hints to speed my research. Such as recommended places to look in the code, ioctl's used and/or sysctl's called. I'm happy to do most of the work myself, I'm just asking for some hints. :-) Much appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 16:20:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from EX1.midstream.com (unknown [63.113.127.186]) by hub.freebsd.org (Postfix) with ESMTP id B59EA37B406; Tue, 31 Jul 2001 16:20:48 -0700 (PDT) (envelope-from Jag@midstream.com) Received: by EX1.midstream.com with Internet Mail Service (5.5.2653.19) id ; Tue, 31 Jul 2001 16:20:47 -0700 Message-ID: From: Jag Johal To: "'hackers@freebsd.org'" , Michael VanLoon Cc: "'hackers@freebsd.org'" Subject: RE: Finding MAC address of interface - programming question Date: Tue, 31 Jul 2001 16:20:43 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Use sysctl(3), basically, its something like this. mib[0] = CTL_NET; mib[1] = AF_ROUTE; mib[2] = 0; mib[3] = AF_INET; mib[4] = NET_RT_IFLIST; mib[5] = 0; sysctl(mib, 6, buf, &len, NULL, 0); buf will contain for each interface, an if_msghdr followed by a sockaddr_dl, the sockaddr_dl will contain the interface name and mac addr. Following that will be a ifa_msghdr for each ip address on the interface. You may want to check out UNPv1. Jag -----Original Message----- From: Chris Faulhaber [mailto:jedgar@fxp.org] Sent: Tuesday, July 31, 2001 3:56 PM To: Michael VanLoon Cc: 'hackers@freebsd.org' Subject: Re: Finding MAC address of interface - programming question On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > Please point me to a more appropriate forum if there is one. I'm kinda out > of my depth on this question. Pseudo code is fine. :-) > > What I'm looking for is how to enumerate the network interfaces and get the > Ethernet MAC address of one programmatically. Can anyone point me in the > right direction? > /usr/src/sbin/ifconfig -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - 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 Tue Jul 31 16:28:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postal.edifecs.com (unknown [207.149.212.48]) by hub.freebsd.org (Postfix) with ESMTP id 76DE537B403 for ; Tue, 31 Jul 2001 16:28:12 -0700 (PDT) (envelope-from MichaelV@EDIFECS.COM) Received: from ecx1.edifecs.com (mail.edifecs.com [207.153.149.131]) by postal.edifecs.com (8.11.0/8.11.0) with ESMTP id f6VNaRT17113; Tue, 31 Jul 2001 16:36:28 -0700 Received: by ecx1.edifecs.com with Internet Mail Service (5.5.2653.19) id ; Tue, 31 Jul 2001 16:34:25 -0700 Message-ID: <36F7B20351634E4FBFFE6C6A216B30D54C81@ecx1.edifecs.com> From: Michael VanLoon To: "'Jag Johal'" , "'hackers@freebsd.org'" Cc: "'hackers@freebsd.org'" Subject: RE: Finding MAC address of interface - programming question Date: Tue, 31 Jul 2001 16:34:17 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks that's just exactly the information I was looking for. :-) I'm slow grunging through the code and man pages that take this apart. As far as UNPv1 I assume you're referring to Stevens' "Unix Network Programming"? If I'm not mistaken he doesn't go much below the socket level. A quick glance through didn't reveal anything of this nature. Thanks for the info. > -----Original Message----- > From: Jag Johal [mailto:Jag@midstream.com] > Sent: Tuesday, July 31, 2001 4:21 PM > To: 'hackers@freebsd.org'; Michael VanLoon > Cc: 'hackers@freebsd.org' > Subject: RE: Finding MAC address of interface - programming question > > > Use sysctl(3), basically, its something like this. > mib[0] = CTL_NET; > mib[1] = AF_ROUTE; > mib[2] = 0; > mib[3] = AF_INET; > mib[4] = NET_RT_IFLIST; > mib[5] = 0; > > sysctl(mib, 6, buf, &len, NULL, 0); > buf will contain for each interface, an if_msghdr followed by > a sockaddr_dl, > the sockaddr_dl will contain the interface name and mac addr. > Following that > will be a ifa_msghdr for each ip address on the interface. > You may want to > check out UNPv1. > > Jag > > -----Original Message----- > From: Chris Faulhaber [mailto:jedgar@fxp.org] > Sent: Tuesday, July 31, 2001 3:56 PM > To: Michael VanLoon > Cc: 'hackers@freebsd.org' > Subject: Re: Finding MAC address of interface - programming question > > > On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > > Please point me to a more appropriate forum if there is > one. I'm kinda > out > > of my depth on this question. Pseudo code is fine. :-) > > > > What I'm looking for is how to enumerate the network > interfaces and get > the > > Ethernet MAC address of one programmatically. Can anyone > point me in the > > right direction? > > > > /usr/src/sbin/ifconfig > > -- > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > -------------------------------------------------------- > FreeBSD: The Power To Serve - 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 Tue Jul 31 17: 1: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 6E75D37B403 for ; Tue, 31 Jul 2001 17:01:06 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.4/8.11.1) id f6VNwM293520; Tue, 31 Jul 2001 16:58:22 -0700 (PDT) (envelope-from obrien) Date: Tue, 31 Jul 2001 16:57:01 -0700 From: "David O'Brien" To: steve.d.meacham@mail.sprint.com Cc: freebsd-hackers@freebsd.org Subject: Re: ie ethernet device fix needs to be committed Message-ID: <20010731165701.B93196@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from steve.d.meacham@mail.sprint.com on Tue, Jul 31, 2001 at 03:42:33PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 31, 2001 at 03:42:33PM -0500, steve.d.meacham@mail.sprint.com wrote: > I have machines which still use the ie ethernet driver. It no longer > auto-detects without the following fix. > > Is it possible to get this fix commited? Having it MFC'd for the > 4.4-RELEASE would be even better. This fix has been running on two It does not build on -CURRENT, so it is hard to commit it and MFC it. -- -- David (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 Tue Jul 31 17: 8:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id C13B637B403; Tue, 31 Jul 2001 17:08:37 -0700 (PDT) Date: Tue, 31 Jul 2001 17:08:37 -0700 From: David O'Brien To: Dan Nelson Cc: Dima Dorfman , hackers@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: portmap_enable vs. rpcbind_enable Message-ID: <20010731170837.A10378@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <20010731114846.42FA73E2F@bazooka.unixfreak.org> <20010731102606.A26323@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010731102606.A26323@dan.emsphone.com>; from dnelson@emsphone.com on Tue, Jul 31, 2001 at 10:26:06AM -0500 X-Operating-System: FreeBSD 4.3-STABLE Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 31, 2001 at 10:26:06AM -0500, Dan Nelson wrote: > In the last episode (Jul 31), Dima Dorfman said: > > Does anybody know (remember?) why portmap_enable (the rc.conf knob) > > wasn't renamed to rpcbind_enable when portmap became rpcbind? It > > seems odd to have a knob called portmap_enable that actually starts > > something called rpcbind (not to mention violating POLA). > > Probably to keep existing rc.conf's from breaking. Same reason we've > still got xntpd_enable. Would this work (untested, need advice on exact syntax): Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.272 diff -u -r1.272 rc --- rc 2001/07/17 14:33:50 1.272 +++ rc 2001/08/01 00:01:53 @@ -102,10 +102,11 @@ esac } -chkdepend amd amd_enable portmap portmap_enable -chkdepend NFS nfs_server_enable portmap portmap_enable -chkdepend NIS nis_server_enable portmap portmap_enable -chkdepend NIS nis_client_enable portmap portmap_enable +chkdepend amd amd_enable rpcbind rpcbind_enable +chkdepend NFS nfs_server_enable rpcbind rpcbind_enable +chkdepend NIS nis_server_enable rpcbind rpcbind_enable +chkdepend NIS nis_client_enable rpcbind rpcbind_enable +chkdepend portmapper portmap_enable rpcbind rcpbind_enable # Enable harvesting of entropy via devices. The sooner this happens the # better so that we can take advantage of the boot process. Index: rc.network =================================================================== RCS file: /home/ncvs/src/etc/rc.network,v retrieving revision 1.102 diff -u -r1.102 rc.network --- rc.network 2001/07/30 23:12:02 1.102 +++ rc.network 2001/08/01 00:06:29 @@ -521,10 +521,11 @@ ;; esac - case ${portmap_enable} in + case ${rpcbind_enable} in [Yy][Ee][Ss]) - echo -n ' rpcbind'; ${portmap_program:-/usr/sbin/rpcbind} \ - ${portmap_flags} + echo -n ' rpcbind' + ${rpcbind_program:-${portmap_program:-/usr/sbin/rpcbind}} \ + ${rpcbind_flags:-${portmap_flags:-""}} # Start ypserv if we're an NIS server. # Run rpc.ypxfrd and rpc.yppasswdd only on the NIS master server. @@ -593,7 +594,7 @@ network_pass3() { echo -n 'Starting final network daemons:' - case ${portmap_enable} in + case ${rpcbind_enable} in [Yy][Ee][Ss]) case ${nfs_server_enable} in [Yy][Ee][Ss]) Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.119 diff -u -r1.119 rc.conf --- defaults/rc.conf 2001/07/28 19:57:57 1.119 +++ defaults/rc.conf 2001/08/01 00:04:06 @@ -167,9 +167,9 @@ nfs_bufpackets="DEFAULT" # bufspace (in packets) for client (or DEFAULT) rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. rpc_statd_enable="NO" # Run NFS rpc.statd if nfs_server (or NO). -portmap_enable="NO" # Run the portmapper service (YES/NO). -portmap_program="/usr/sbin/rpcbind" # path to portmap, if you want a different one. -portmap_flags="" # Flags to portmap (if enabled). +rpcbind_enable="NO" # Run the portmapper service (YES/NO). +rpcbind_program="/usr/sbin/rpcbind" # path to portmap, if you want a different one. +rpcbind_flags="" # Flags to portmap (if enabled). rpc_ypupdated_enable="NO" # Run if NIS master and SecureRPC (or NO). keyserv_enable="NO" # Run the SecureRPC keyserver (or NO). keyserv_flags="" # Flags to keyserv (if enabled). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 19:42:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 2D25337B401; Tue, 31 Jul 2001 19:42:18 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f712gIU12586; Tue, 31 Jul 2001 19:42:18 -0700 Date: Tue, 31 Jul 2001 19:42:17 -0700 From: Brooks Davis To: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: review request: vlan cloning and modularization patch Message-ID: <20010731194217.A12426@Odin.AC.HMC.Edu> References: <20010730155207.A19629@Odin.AC.HMC.Edu> <20010731114609.A16327@Odin.AC.HMC.Edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010731114609.A16327@Odin.AC.HMC.Edu>; from brooks@one-eyed-alien.net on Tue, Jul 31, 2001 at 11:46:09AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 31, 2001 at 11:46:09AM -0700, Brooks Davis wrote: > I've updated the patch to fix a bug in ether_input and wrap > vlan_input(_tag) in marcos to enable locking later. This patch also > reflects the latest fixes to the txp driver. I've included it below or > you can find it at: >=20 > http://people.freebsd.org/~brooks/patches/vlan.diff >=20 > Apply the patch as before. One last follow up. I'm going to be offline until around Monday the 6th so if you do find bugs or issues, I'm not ignoring you. :-) -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7Z2yJXY6L6fI4GtQRAvNfAKDDTaP8yb3Y3LlB4rchCnzpmMmcoQCePR9j 9svljSU8zRcPek9GmvBkJtw= =68hC -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 20:49:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 9EB7C37B409 for ; Tue, 31 Jul 2001 20:49:04 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id WAA37546; Tue, 31 Jul 2001 22:44:41 -0700 (PDT) Message-ID: <3B67779B.3DAEE6B5@elischer.org> Date: Tue, 31 Jul 2001 20:29:31 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Michael VanLoon Cc: "'hackers@freebsd.org'" Subject: Re: Finding MAC address of interface - programming question References: <36F7B20351634E4FBFFE6C6A216B30D54C7F@ecx1.edifecs.com> Content-Type: multipart/mixed; boundary="------------885B4547E9E7435AD8E18A16" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------885B4547E9E7435AD8E18A16 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Michael VanLoon wrote: > > Please point me to a more appropriate forum if there is one. I'm kinda out > of my depth on this question. Pseudo code is fine. :-) > > What I'm looking for is how to enumerate the network interfaces and get the > Ethernet MAC address of one programmatically. Can anyone point me in the > right direction? > > Thanks much! here's a little routine that probably does what you want: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v --------------885B4547E9E7435AD8E18A16 Content-Type: text/plain; charset=iso-8859-2; name="dumpifs.c" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dumpifs.c" #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include void showbytes(unsigned char *cptr,int len) { int i,j; for (j = 0 ;len > 0 ;j++) { for ( i = 0; i < 16; i++) { printf("0x%x ",*cptr++); if (--len == 0) break; } printf("\n"); } } void print_sa (struct sockaddr *sap) { char buf[128]; printf("len=%d,",sap->sa_len); switch(sap->sa_family) { case AF_LINK: printf(" family=LINK\n"); { char *cptr; struct sockaddr_dl *sdl = (struct sockaddr_dl *)sap; cptr = sdl->sdl_data; printf("index=%u, type=%u ", sdl->sdl_index, sdl->sdl_type); printf("nlen=%u, alen=%u, slen=%u\n", sdl->sdl_nlen, sdl->sdl_alen, sdl->sdl_slen); if(sdl->sdl_nlen) { bcopy(cptr,buf,sdl->sdl_nlen); buf[sdl->sdl_nlen] = 0; printf(" name = %s\n",buf); cptr += sdl->sdl_nlen; } if(sdl->sdl_alen) { printf(" address = "); showbytes(cptr,sdl->sdl_alen); cptr += sdl->sdl_alen; } if(sdl->sdl_slen) { printf(" selector = "); showbytes(cptr,sdl->sdl_slen); cptr += sdl->sdl_slen; } } break; case AF_INET: printf(" family=INET\n"); printf("[%s]", inet_ntoa(((struct sockaddr_in *)sap)->sin_addr)); printf(".%hu\n",((struct sockaddr_in *)sap)->sin_port); break; default: printf(" family=%d\n",sap->sa_family); showbytes(sap->sa_data,sap->sa_len-2); } } /* * Get the configuration from the kernel. */ void getifconf( void ) { struct ifconf ifc; struct ifreq ifrs[ 64 ], *ifr, *nextifr; struct interface *iface, *niface; int s; struct sockaddr *sa_p; int ifrsize = 0; u_char proto; bzero(&ifc,sizeof(struct ifconf)); bzero(ifrs,sizeof(struct ifreq) * 64); if (( s = socket( AF_INET, SOCK_DGRAM, 0 )) < 0 ) { perror( "socket" ); exit( 1 ); } ifc.ifc_len = sizeof( ifrs ); ifc.ifc_buf = (caddr_t)ifrs; if ( ioctl( s, SIOCGIFCONF, &ifc ) < 0 ) { perror( "getifconf" ); exit( 1 ); } for ( ifr = ifc.ifc_req; ifc.ifc_len >= sizeof( struct ifreq ); ifr = nextifr, ifc.ifc_len -= ifrsize) { /* * in BSD4.4, this returns an entry for every address * Associated with the if. including physical.. they * include a sockaddr which is VARIABLE LENGTH! * * Calculate the length of this entry. */ sa_p = &(ifr->ifr_addr); print_sa(&(ifr->ifr_addr)); /*print_sa(&(ifr->ifr_dstaddr)); print_sa(&(ifr->ifr_broadaddr));*/ ifrsize = IFNAMSIZ + sa_p->sa_len; nextifr = (struct ifreq *)((caddr_t)ifr + ifrsize); proto = ifr->ifr_addr.sa_family; /* * Now get it's Netmask */ if ( ioctl( s, SIOCGIFNETMASK, ifr ) < 0 ) { fprintf( stderr, "netmask not available from SIOCGIFNETMASK\n" ); } else { if(proto == AF_INET) ifr->ifr_addr.sa_family = proto; printf("netmask: "); print_sa(&(ifr->ifr_addr)); } /* * Now get it's flags */ if ( ioctl( s, SIOCGIFFLAGS, ifr ) < 0 ) { perror( ifr->ifr_name ); } printf("FLAGS = 0x%x\n",(unsigned short)ifr->ifr_flags); printf("\n"); } if ( ifc.ifc_len != 0 ) { fprintf( stderr, "Funky gifconf return.\n" ); exit( 1 ); } (void)close( s ); return; } main() { getifconf(); exit(0); } --------------885B4547E9E7435AD8E18A16-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 22:13: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tambora.parokinet.org (unknown [133.30.168.119]) by hub.freebsd.org (Postfix) with ESMTP id 682FD37B405; Tue, 31 Jul 2001 22:13:00 -0700 (PDT) (envelope-from rachmat@canada.com) Received: from localhost (rachmat@localhost) by tambora.parokinet.org (8.11.3/8.11.1) with ESMTP id f715EW761826; Wed, 1 Aug 2001 14:14:33 +0900 (JST) (envelope-from rachmat@canada.com) X-Authentication-Warning: tambora.parokinet.org: rachmat owned process doing -bs Date: Wed, 1 Aug 2001 14:14:21 +0900 (JST) From: Rachmat Hidajat X-Sender: rachmat@tambora.parokinet.org To: hackers@freebsd.org Cc: bugs@freebsd.org, sos@freebsd.org Subject: wd and burncd Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, I have a Sony CRX140E/1.0s CD-RW installed in my computer running FreeBSD(98) 4.3-STABLE. It is recognized as /dev/wcd1c, and working fine for reading. However, I fail to run burncd on this drive, as I always get: burncd: ioctl(CDRIOCWRITESPEED): Inappropriate ioctl for device I tried to add device ata in the kernel but it seems that the source doesn't allow me to do that. Is there any patch for wd.c or burncd.c so I can run burncd with wd driver? TIA, Rachmat Hidajat Kobe, JAPAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 22:39: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.ceeyes.com (mail.in.ceeyes.com [65.192.85.133]) by hub.freebsd.org (Postfix) with ESMTP id 3ADBD37B403 for ; Tue, 31 Jul 2001 22:38:57 -0700 (PDT) (envelope-from srinivass@in.ceeyes.com) Received: from ssrao.in.ceeyes.com (Shobana [10.1.9.11]) by mail.ceeyes.com (8.9.1b+Sun/8.9.3) with SMTP id LAA28146 for ; Wed, 1 Aug 2001 11:08:52 +0530 (INST) Message-ID: <003801c11a4c$5382c400$0b09010a@ssrao.in.ceeyes.com> From: "srinivasarao" To: Subject: help me !!!!!!! Date: Wed, 1 Aug 2001 11:09:24 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0035_01C11A7A.6C69F460" 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0035_01C11A7A.6C69F460 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, By the chance is there any possibility to build the kernel without VGA = card serially either for newly building of kernel or for exisiting = kernel after modifications in FreeBSD? if any chance please guide me ? = what are all steps to be taken care? Please help me. =20 thank u, S.Srinivasa Rao Group Leader Ceeyes Software Technologies Pvt. Ltd, Behind Govt Mint, Cherlapalli, Hyderabad-51, ph 040-7261093/93/95/96,extn 1267, mobile :- 919848130891 ------=_NextPart_000_0035_01C11A7A.6C69F460 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
By the chance is there any possibility to build the = kernel=20 without VGA card serially  either for newly building of kernel or = for=20 exisiting kernel after modifications in FreeBSD?  if any chance = please=20 guide me ? what are all steps to be taken care?
 Please help me.
 
thank u,
S.Srinivasa=20 Rao
           =      =20 Group Leader
Ceeyes Software Technologies Pvt. Ltd,
Behind Govt = Mint,=20 Cherlapalli,
Hyderabad-51, ph 040-7261093/93/95/96,extn 1267, mobile = :-=20 919848130891
------=_NextPart_000_0035_01C11A7A.6C69F460-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jul 31 23:42:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 4477137B40B; Tue, 31 Jul 2001 23:41:19 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f716ucZ02371; Wed, 1 Aug 2001 10:56:38 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108010656.f716ucZ02371@bugz.infotecs.ru> Subject: Re: crash dump output In-Reply-To: "from John Baldwin at Jul 31, 2001 04:02:12 pm" To: John Baldwin Date: Wed, 1 Aug 2001 10:56:38 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Can you compile a debug kernel please and repeat this? That way you will have > debug symbols so that you can get more useful information out of gdb. You'll > have to get a new crashdump with the debug kernel running however. Maybe it's offtopic a bit, but can you please give exact instructions of how to compile debug kernel ? My machine crashes sometimes too, I tried to compile debug kernel, but it seemed not so easy and I gave up due to lack of time. Or is there any URL with a good explanation ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 0:27:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id D7DD337B40A for ; Wed, 1 Aug 2001 00:27:06 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f717fXs06699; Wed, 1 Aug 2001 11:41:33 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108010741.f717fXs06699@bugz.infotecs.ru> Subject: Re: crash dump output In-Reply-To: "from Mohana Krishna Penumetcha at Aug 1, 2001 12:21:15 pm" To: Mohana Krishna Penumetcha Date: Wed, 1 Aug 2001 11:41:33 +0400 (MSD) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Maybe it's offtopic a bit, but can you please give exact instructions of how > > to compile debug kernel ? My machine crashes sometimes too, I tried to compile > > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or > > is there any URL with a good explanation ? > > you just call config with '-g' option. and compile the kernel in normal > way. The freebsd handbook discusses this in more detail. Hmm. It seems like I need spare swap device for crashdump ? What can I do if I have no room on disk for this ? Can normal swap device be used, and if yes, how to save core on panic ? I think swap device contents will be lost on the next reboot ... Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 0:42:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id CDD2E37B406 for ; Wed, 1 Aug 2001 00:42:28 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.188.Dial1.SanJose1.Level3.net [209.244.104.188]) by robin.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id AAA20351; Wed, 1 Aug 2001 00:42:23 -0700 (PDT) Message-ID: <3B67B306.4243AD5D@mindspring.com> Date: Wed, 01 Aug 2001 00:43:02 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Weiguang SHI Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: address resolution question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Weiguang SHI wrote: > I need your help to understand this. > In machdep.c, > > 1451 /* > 1452 * map page 1 R/W into the kernel page table so we can use > it > 1453 * as a buffer. The kernel will unmap this page later. > 1454 */ > 1455 pte = (pt_entry_t)vtopte(KERNBASE + (1 < 1456 *pte = (1 << PAGE_SHIFT) | PG_RW | PG_V; > > According to my calculation, pte=0xbfcc0001 and *pte will yield > 0x2FF,0xC0,0x1 as indexes to the page directory table, page table and > an offset. My page directory table is like this (starting at physical > address 0x2C2000): > > index page_table_base_address; prot > ---------- ----------------------------- > 0,0x1D 0x2A4,0x2C1 ; RW > 0x2FF 0x2C2 ; RW > 0x300,0x31D 0x2A4,0x2C1 ; RW > > The entries that are not listed are all zeros. This table was created > by "create_pagetable" in locore.s > > I know there is a recursive reference, i.e., the 0x2ff entry. But I > need more (authoritative) explanation on how the triple > (0x2ff,0xc0,0x1) is going to be resolved. > > Would you shed some light? It gets resolved as the address 0x0C001000. It is a page address for a 4k page (hint: 0x1000 * 0xc001). The reason it is mapped is to give a scratchpad area for the VM86() call(s) to get the memory size information from the BIOS. The lower area of memory is a 16MB region, when trapping to virtual 8086 mode. The kernel is loaded starting at 1MB in the virtual address space. For all intents and purposes, the kernel is loaded at 1MB, as far as it is concerned, and as far as the VM86() code is concerned, and up to 16MB of RAM is mapped into the VM86() real mode address space. Remember that by the time you are running the getmemsize() code, you are well into the startup code, and have virtual memory enabled. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 0:47:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-1.enteract.com (smtp-1.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id CA79937B409 for ; Wed, 1 Aug 2001 00:47:31 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-1.enteract.com (shell-1.enteract.com [207.229.143.40]) by smtp-1.enteract.com (Postfix) with ESMTP id 2067A6771; Wed, 1 Aug 2001 02:47:26 -0500 (CDT) Date: Wed, 1 Aug 2001 02:47:26 -0500 (CDT) From: David Scheidt X-X-Sender: To: "Eugene L. Vorokov" Cc: Mohana Krishna Penumetcha , Subject: Re: crash dump output In-Reply-To: <200108010741.f717fXs06699@bugz.infotecs.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 1 Aug 2001, Eugene L. Vorokov wrote: :> > Maybe it's offtopic a bit, but can you please give exact instructions of how :> > to compile debug kernel ? My machine crashes sometimes too, I tried to compile :> > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or :> > is there any URL with a good explanation ? :> :> you just call config with '-g' option. and compile the kernel in normal :> way. The freebsd handbook discusses this in more detail. : :Hmm. It seems like I need spare swap device for crashdump ? What can I do :if I have no room on disk for this ? Can normal swap device be used, and :if yes, how to save core on panic ? I think swap device contents will be :lost on the next reboot ... You can use swap for dump, as long as you have a swap device that's slightly larger (64Kb, I think?) than your physical memory. set the rc.conf variable to point to your swap partion dumpon="/dev/da0s1b", or whatever. savecore(8) will save the dump at system startup. It runs from /etc/rc, so it should run soon enough to prevent your dump from having been overwritten by swapping, unless you're seriously pressed for memory. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 0:50:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C470A37B403; Wed, 1 Aug 2001 00:50:29 -0700 (PDT) (envelope-from julian@elischer.org) Received: from elischer.org (InterJet.elischer.org [192.168.1.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id CAA38593; Wed, 1 Aug 2001 02:42:33 -0700 (PDT) Message-ID: <3B67AF4F.F129861B@elischer.org> Date: Wed, 01 Aug 2001 00:27:11 -0700 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: "Eugene L. Vorokov" Cc: John Baldwin , freebsd-hackers@FreeBSD.ORG Subject: Re: crash dump output References: <200108010656.f716ucZ02371@bugz.infotecs.ru> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Eugene L. Vorokov" wrote: > > > Can you compile a debug kernel please and repeat this? That way you will have > > debug symbols so that you can get more useful information out of gdb. You'll > > have to get a new crashdump with the debug kernel running however. > > Maybe it's offtopic a bit, but can you please give exact instructions of how > to compile debug kernel ? My machine crashes sometimes too, I tried to compile > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or > is there any URL with a good explanation ? > > Regards, > Eugene > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message instead of typing "config MYKERNEL" type "config -g MYKERNEL" (then don't forget to turn on dumps in rc.conf) -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 0:51:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mailer2.webgiro.com [213.162.131.18]) by hub.freebsd.org (Postfix) with ESMTP id 942F037B403 for ; Wed, 1 Aug 2001 00:51:19 -0700 (PDT) (envelope-from abial@webgiro.com) Received: from webgiro.com (mailer2.webgiro.com [213.162.131.18]) by mimer.webgiro.com (Postfix) with ESMTP id 10AE768469; Wed, 1 Aug 2001 10:13:56 +0200 (CEST) Message-ID: <3B67B425.40D6FE0E@webgiro.com> Date: Wed, 01 Aug 2001 09:47:50 +0200 From: Andrzej Bialecki Organization: WebGiro AB X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Michael VanLoon Cc: 'Chris Faulhaber' , "'hackers@freebsd.org'" Subject: Re: Finding MAC address of interface - programming question References: <36F7B20351634E4FBFFE6C6A216B30D54C80@ecx1.edifecs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Michael VanLoon wrote: > > > From: Chris Faulhaber [mailto:jedgar@fxp.org] > > Sent: Tuesday, July 31, 2001 3:56 PM > > > > On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > > > Please point me to a more appropriate forum if there is > > one. I'm kinda out > > > of my depth on this question. Pseudo code is fine. :-) > > > > > > What I'm looking for is how to enumerate the network > > interfaces and get the > > > Ethernet MAC address of one programmatically. Can anyone > > point me in the > > > right direction? > > > > > > > /usr/src/sbin/ifconfig > > Thanks, I've already been looking at that. :-) > > The problem is, ifconfig does a lot of other stuff, and it's very poorly > documented. > > I was hoping someone could give me some hints to speed my research. Such as > recommended places to look in the code, ioctl's used and/or sysctl's called. > > I'm happy to do most of the work myself, I'm just asking for some hints. :-) > Much appreciated. Take a look at /usr/src/release/picobsd/tinyware/ns. I went through the same hoops some time ago... :-) -- Andrzej // ---------------------------------------------------------------- // Andrzej Bialecki , Chief System Architect // WebGiro AB, Sweden (http://www.webgiro.com) // ---------------------------------------------------------------- // FreeBSD developer (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 Wed Aug 1 0:57:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.tecc.co.uk (luggage.tecc.co.uk [193.128.6.129]) by hub.freebsd.org (Postfix) with SMTP id AC77037B403 for ; Wed, 1 Aug 2001 00:57:16 -0700 (PDT) (envelope-from andy@tecc.co.uk) Received: from southampton [195.217.37.155] by relay.tecc.co.uk with smtp (Exim 1.70 #1) id 15RqsV-0002bE-00; Wed, 1 Aug 2001 08:57:15 +0100 From: "Andy" To: Subject: FW: ioctl and fxp/tl drivers Date: Wed, 1 Aug 2001 08:57:15 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Originally posted to -net but no replies, maybe some here could help me out? tia, Andy -----Original Message----- To: freebsd-net@freebsd.org Subject: ioctl and fxp/tl drivers Hi all This maybe a dumb question but a bit stumped at the mo. When I make an ioctl call to the fxp or tl drivers thus: if ((ret=ioctl(s, SIOCSIFLLADDR, (caddr_t)&ifr)) < 0) syslog(LOG_ERR, "ioctl (set lladdr): %m"); I get:- ioctl (set lladdr): Inappropriate ioctl for device Also, :- ret = ioctl(fd, addF ? SIOCADDMULTI : SIOCDELMULTI, (char *) &ifr); if (ret) { syslog( LOG_ERR, "Can't %s on %s: %m" ,addF ? "SIOCADDMULTI" : "SIOCDELMULTI" ,ifname); } I get:- Can't SIOCADDMULTI on fxp0: Can't assign requested address Also, when the call is SIOCDELMULTI (rather than ADD) I get Can't SIOCDELMULTI on fxp0: No such file or directory Same on the tl device. I've had a look in the driver source and those calls appear to be supported. Can supply some debug info if required but maybe the combined brains out there can spot the obvious I'm missing? tia, regards Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" 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 Aug 1 0:59:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cyclone.eis.ru (for.spb.ru [195.201.69.16]) by hub.freebsd.org (Postfix) with SMTP id DA22637B406 for ; Wed, 1 Aug 2001 00:59:34 -0700 (PDT) (envelope-from diwil@eis.ru) Received: (qmail 31066 invoked from network); 1 Aug 2001 08:07:12 -0000 Received: from good.for.spb.ru (HELO wild.eis.ru) (195.201.69.80) by for.spb.ru with SMTP; 1 Aug 2001 08:07:12 -0000 Content-Type: text/plain; charset="koi8-r" From: Dmitry Diky Reply-To: diwil@eis.ru To: hackers@freebsd.org Subject: Re: Finding MAC address of interface - programming question Date: Wed, 1 Aug 2001 11:51:52 +0400 X-Mailer: KMail [version 1.2] References: <36F7B20351634E4FBFFE6C6A216B30D54C80@ecx1.edifecs.com> <3B67B425.40D6FE0E@webgiro.com> In-Reply-To: <3B67B425.40D6FE0E@webgiro.com> MIME-Version: 1.0 Message-Id: <01080111515200.13229@wild.eis.ru> Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG the code as follows (at least it works in my case) : #include #include #include #include #include #include #include #include #include #include /* IP */ #include #include #include #include /* OSI */ #include #include #include #include #include #include #include #include #include #include #define NO_OF_IFS=092 char mac[NO_OF_IFS][6]; /* sdlr must be provided */ /* MAC will be filled */ /* number of IFs returned */ int get_ifs(struct sockaddr_dl *sdlr) { size_t=09=09needed; /* prepare params for sysctl */ int=09=09=09mib[6] =3D { CTL_NET, PF_ROUTE, 0, 0, NET_RT_IFLIST, 0 }; char=09 =09=09*buf, *lim, *next; struct if_msghdr=09*ifm, *nextifm; struct ifa_msghdr=09*ifam; struct sockaddr_dl=09*sdl; int =09=09=09flags, addrcount=3D0, etheraddrcount=3D0; char=09=09=09name[16]; /* cannot be more */ char=09=09=09*cp; int=09=09=09n; if (sysctl(mib, 6, NULL, &needed, NULL, 0) < 0) perror("iflist-sysctl-estimate"); if ((buf =3D malloc(needed)) =3D=3D NULL) perror("malloc"); if (sysctl(mib, 6, buf, &needed, NULL, 0) < 0) perror("actual retrieval of interface table"); lim =3D buf + needed; next =3D buf; while (next < lim) { ifm =3D (struct if_msghdr *)next; if (ifm->ifm_type =3D=3D RTM_IFINFO) { sdl =3D (struct sockaddr_dl *)(ifm + 1); flags =3D ifm->ifm_flags; } else { exit (1); } next +=3D ifm->ifm_msglen; ifam =3D NULL; addrcount =3D 0; while (next < lim) { nextifm =3D (struct if_msghdr *)next; if (nextifm->ifm_type !=3D RTM_NEWADDR) break; if (ifam =3D=3D NULL) ifam =3D (struct ifa_msghdr *)nextifm; addrcount++; next +=3D nextifm->ifm_msglen; } /* * Ok, the interface is found * Save it if it is an ethernet. */ if(sdl->sdl_type =3D=3D IFT_ETHER) { memcpy((void *)&sdlr[etheraddrcount],sdl, sizeof(struct sockaddr_dl= )); etheraddrcount++; strncpy(name, sdl->sdl_data, sdl->sdl_nlen); name[sdl->sdl_nlen] =3D '\0'; cp =3D (char *)LLADDR(sdl); if ((n =3D sdl->sdl_alen) > 0) { /* if (sdl->sdl_type =3D=3D IFT_ETHER) errMsg("\tEthernet %s:\tMAC - %s\n", name, macPrt(cp)); else errMsg("\tlladdr %s:\tMAC - %s\n", name, macPrt(cp)); */ memcpy(mac[etheraddrcount-1],cp,6); } } } if( etheraddrcount =3D=3D 0 ) printf("\tNone"); free(buf); return etheraddrcount; } =08=A0=864=08 On Wednesday 01 August 2001 11:47, Andrzej Bialecki wrote: > Michael VanLoon wrote: > > > From: Chris Faulhaber [mailto:jedgar@fxp.org] > > > Sent: Tuesday, July 31, 2001 3:56 PM > > > > > > On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > > > > Please point me to a more appropriate forum if there is > > > > > > one. I'm kinda out > > > > > > > of my depth on this question. Pseudo code is fine. :-) > > > > > > > > What I'm looking for is how to enumerate the network > > > > > > interfaces and get the > > > > > > > Ethernet MAC address of one programmatically. Can anyone > > > > > > point me in the > > > > > > > right direction? > > > > > > /usr/src/sbin/ifconfig > > > > Thanks, I've already been looking at that. :-) > > > > The problem is, ifconfig does a lot of other stuff, and it's very poo= rly > > documented. > > > > I was hoping someone could give me some hints to speed my research. = Such > > as recommended places to look in the code, ioctl's used and/or sysctl= 's > > called. > > > > I'm happy to do most of the work myself, I'm just asking for some hin= ts. > > :-) Much appreciated. > > Take a look at /usr/src/release/picobsd/tinyware/ns. I went through the > same hoops some time ago... :-) --=20 ********************************************************************* ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ `6_ 6 ) `-. ( ).`-.__.`) Enterprise Information Sys=20 (_Y_.)' ._ ) `._ `. ``-..-' Nevsky prospekt, 20 / 44 _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia (il),-'' (li),' ((!.-' +7 (812) 3148860, 5585314 ********************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 1:17: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 6D36837B403 for ; Wed, 1 Aug 2001 01:16:14 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f718VCj16040; Wed, 1 Aug 2001 12:31:12 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108010831.f718VCj16040@bugz.infotecs.ru> Subject: Re: crash dump output In-Reply-To: "from Mohana Krishna Penumetcha at Aug 1, 2001 12:21:15 pm" To: Mohana Krishna Penumetcha Date: Wed, 1 Aug 2001 12:31:12 +0400 (MSD) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > you just call config with '-g' option. and compile the kernel in normal > way. The freebsd handbook discusses this in more detail. Yet another issue, I have run config -g, then make depend, make and make install.debug. But my /kernel is still about 2mb long, which probably means it's not really debug kernel. However I see kernel.debug in the compile directory which is about 8mb long. Should I copy it manually to the / and boot this one ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 1:26:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elm.phenome.org (elm.phenome.org [194.153.169.3]) by hub.freebsd.org (Postfix) with ESMTP id 4464637B403 for ; Wed, 1 Aug 2001 01:26:18 -0700 (PDT) (envelope-from joshua@roughtrade.net) Received: from localhost (joshua@localhost [127.0.0.1]) by localhost (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) with ESMTP id f717pICC028880 for ; Wed, 1 Aug 2001 08:51:18 +0100 Date: Wed, 1 Aug 2001 08:51:18 +0100 (BST) From: Joshua Goodall X-X-Sender: To: Subject: patch review request: lchflags Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As previously discussed. This is the conservative route, of course. I did not want to get into creating new VOP_SETATTR interfaces. PR kern/29355 http://www.freebsd.org/cgi/query-pr.cgi?pr=29355 J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 2:10:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from samar.sasken.com (samar.sasken.com [164.164.56.2]) by hub.freebsd.org (Postfix) with ESMTP id 0211D37B406 for ; Wed, 1 Aug 2001 02:10:33 -0700 (PDT) (envelope-from pmk@sasken.com) Received: from samar (localhost [127.0.0.1]) by samar.sasken.com (8.11.3/8.11.3) with SMTP id f719AFg25359; Wed, 1 Aug 2001 14:40:17 +0530 (IST) Received: from localhost (pmk@localhost) by sunk2.sasi.com (8.9.3/8.9.3) with ESMTP id OAA03512; Wed, 1 Aug 2001 14:40:12 +0530 (IST) Date: Wed, 1 Aug 2001 14:40:12 +0530 (IST) From: Mohana Krishna Penumetcha X-Sender: To: "Eugene L. Vorokov" Cc: Subject: Re: crash dump output In-Reply-To: <200108010831.f718VCj16040@bugz.infotecs.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 1 Aug 2001, Eugene L. Vorokov wrote: > Yet another issue, I have run config -g, then make depend, make and > make install.debug. But my /kernel is still about 2mb long, which probably > means it's not really debug kernel. However I see kernel.debug in the > compile directory which is about 8mb long. Should I copy it manually to the > / and boot this one ? The kernel.debug is the kernel with all debug symbol information. The symbol information is removed from this file and installed as /kernel. The difference in file sizes should make it obvious why the symbol information is removed. you can see this in the make output, all object files are linked to kernel.debug and after that 'objcopy' strips of all symbols. once you have the core file, invoke the gdb(with -k option), specify the kernel.debug as symbol file and /kernel as exec file. all this is explained more clearly in the handbook (/usr/share/doc/handbook/book.txt) regards, mohan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 2:50:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chrobd01.vailsys.com (chrobd01.vailsys.com [63.210.102.138]) by hub.freebsd.org (Postfix) with ESMTP id 4C09237B406 for ; Wed, 1 Aug 2001 02:50:24 -0700 (PDT) (envelope-from hal@vailsys.com) Received: from area51.vail (area51.vail [192.168.129.30]) by chrobd01.vailsys.com (Postfix) with ESMTP id E22494963 for ; Wed, 1 Aug 2001 04:50:18 -0500 (CDT) Received: from gamera.vail (root@gamera.vail [172.16.15.1]) by area51.vail (8.9.3/8.9.3) with ESMTP id EAA74602 for ; Wed, 1 Aug 2001 04:50:18 -0500 (CDT) (envelope-from hal@vailsys.com) Received: (from hal@localhost) by gamera.vail (8.11.4/8.11.3) id f719oCx20321; Wed, 1 Aug 2001 04:50:12 -0500 (CDT) X-Authentication-Warning: gamera.vail: hal set sender to hal@vailsys.com using -f To: Subject: Re: Finding MAC address of interface - programming question References: <36F7B20351634E4FBFFE6C6A216B30D54C81@ecx1.edifecs.com> From: Hal Snyder Date: 01 Aug 2001 04:50:11 -0500 In-Reply-To: <36F7B20351634E4FBFFE6C6A216B30D54C81@ecx1.edifecs.com> (Michael VanLoon's message of "Tue, 31 Jul 2001 16:34:17 -0700") Message-ID: <873d7c9kj0.fsf@gamera.vail> Lines: 58 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Michael VanLoon writes: > Thanks that's just exactly the information I was looking for. :-) > > I'm slow grunging through the code and man pages that take this apart. > > As far as UNPv1 I assume you're referring to Stevens' "Unix Network > Programming"? If I'm not mistaken he doesn't go much below the > socket level. A quick glance through didn't reveal anything of this > nature. See UNIX Network Programming 2ed, Vol.1, pp434-435 for SIOCGIFCONF explanation. But nowadays getifaddrs(3) is easier: /* hacked from netbsd ifconfig.c */ #include #include #include #include #include int main (void) { struct ifaddrs *ifap, *ifaphead; int rtnerr; const struct sockaddr_dl *sdl; caddr_t ap; int alen; rtnerr = getifaddrs(&ifaphead); if (rtnerr) { perror(NULL); return 1; } for (ifap = ifaphead; ifap; ifap = ifap->ifa_next) { if (ifap->ifa_addr->sa_family == AF_LINK) { sdl = (const struct sockaddr_dl *) ifap->ifa_addr; ap = ((caddr_t)((sdl)->sdl_data + (sdl)->sdl_nlen)); alen = sdl->sdl_alen; if (ap && alen > 0) { int i; printf ("%s:", ifap->ifa_name); for (i = 0; i < alen; i++, ap++) printf("%c%02x", i > 0 ? ':' : ' ', 0xff&*ap); putchar('\n'); } } } putchar('\n'); freeifaddrs(ifaphead); return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 3:16:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from maila.telia.com (maila.telia.com [194.22.194.231]) by hub.freebsd.org (Postfix) with ESMTP id 065CE37B401 for ; Wed, 1 Aug 2001 03:16:56 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: from d1o913.telia.com (d1o913.telia.com [195.252.44.241]) by maila.telia.com (8.11.2/8.11.0) with ESMTP id f71AGs303441 for ; Wed, 1 Aug 2001 12:16:54 +0200 (CEST) Received: from ertr1013.student.uu.se (h185n2fls20o913.telia.com [212.181.163.185]) by d1o913.telia.com (8.8.8/8.8.8) with SMTP id MAA25037 for ; Wed, 1 Aug 2001 12:16:53 +0200 (CEST) Received: (qmail 95140 invoked by uid 1001); 1 Aug 2001 10:15:57 -0000 Date: Wed, 1 Aug 2001 12:15:56 +0200 From: Erik Trulsson To: "Eugene L. Vorokov" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: crash dump output Message-ID: <20010801121556.A95117@student.uu.se> Mail-Followup-To: "Eugene L. Vorokov" , freebsd-hackers@FreeBSD.ORG References: <200108010831.f718VCj16040@bugz.infotecs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200108010831.f718VCj16040@bugz.infotecs.ru> User-Agent: Mutt/1.3.20i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 12:31:12PM +0400, Eugene L. Vorokov wrote: > > you just call config with '-g' option. and compile the kernel in normal > > way. The freebsd handbook discusses this in more detail. > > Yet another issue, I have run config -g, then make depend, make and > make install.debug. But my /kernel is still about 2mb long, which probably > means it's not really debug kernel. However I see kernel.debug in the > compile directory which is about 8mb long. Should I copy it manually to the > / and boot this one ? No. You boot the normal /kernel as usual. The debug kernel is used when analyzing a crashdump with gdb. The FAQ has more information about this. (14.12 "How can I make the most of the data I see when my kernel panics?") -- Erik Trulsson ertr1013@student.uu.se To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 6:25: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 5702D37B405 for ; Wed, 1 Aug 2001 06:25:01 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f71DfAO00453 for freebsd-hackers@freebsd.org; Wed, 1 Aug 2001 17:41:10 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108011341.f71DfAO00453@bugz.infotecs.ru> Subject: crash report To: freebsd-hackers@freebsd.org Date: Wed, 1 Aug 2001 17:41:09 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM996673269-424-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ELM996673269-424-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hello, here's my crash dump, something related to mbufs. If more information is needed, tell me what to do, I'll provide it. This usually happens (but not always) when someone is downloading something huge from ftp server on this machine. Regards, Eugene --ELM996673269-424-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=crashdump vel@bugz:/home/vel # uname -r 4.2-RELEASE vel@bugz:/home/vel # gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol-file /kernel.debug Reading symbols from /kernel.debug...done. (kgdb) exec-file /kernel (kgdb) core-file /var/crash/vmcore.0 IdlePTD 3186688 initial pcb at 291a40 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x60c0ff00 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015b230 stack pointer = 0x10:0xc0271908 frame pointer = 0x10:0xc0271924 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = net tty panic: from debugger panic: from debugger Uptime: 3h11m4s dumping to dev #ad/0x20001, offset 131072 dump ata0: resetting devices .. done 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 dumpsys () at ../../kern/kern_shutdown.c:469 469 if (dumping++) { (kgdb) where #0 dumpsys () at ../../kern/kern_shutdown.c:469 #1 0xc014038b in boot (howto=260) at ../../kern/kern_shutdown.c:309 #2 0xc0140721 in panic (fmt=0xc02477d4 "from debugger") at ../../kern/kern_shutdown.c:556 #3 0xc011d879 in db_panic (addr=-1072319952, have_addr=0, count=1, modif=0xc0271774 "") at ../../ddb/db_command.c:433 #4 0xc011d819 in db_command (last_cmdp=0xc0272b38, cmd_table=0xc0272998, aux_cmd_tablep=0xc028df30) at ../../ddb/db_command.c:333 #5 0xc011d8de in db_command_loop () at ../../ddb/db_command.c:455 #6 0xc011f9eb in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #7 0xc022643a in kdb_trap (type=12, code=0, regs=0xc02718c8) at ../../i386/i386/db_interface.c:158 #8 0xc0234d0c in trap_fatal (frame=0xc02718c8, eva=1623260928) at ../../i386/i386/trap.c:946 #9 0xc02349e5 in trap_pfault (frame=0xc02718c8, usermode=0, eva=1623260928) at ../../i386/i386/trap.c:844 #10 0xc0234587 in trap (frame={tf_fs = -970522608, tf_es = -1061421040, tf_ds = -970522608, tf_edi = -1067662336, tf_esi = 6423552, tf_ebp = -1071179484, tf_isp = -1071179532, tf_ebx = 1, tf_edx = 1623260928, tf_ecx = 949, tf_eax = 6423552, tf_trapno = 12, tf_err = 0, tf_eip = -1072319952, tf_cs = 8, tf_eflags = 66054, tf_esp = -970499232, tf_ss = -971330368}) at ../../i386/i386/trap.c:443 #11 0xc015b230 in m_copym (m=0xc0627000, off0=7693, len=150, wait=1) at ../../kern/uipc_mbuf.c:621 #12 0xc019a521 in tcp_output (tp=0xc6275b60) at ../../netinet/tcp_output.c:590 #13 0xc0199719 in tcp_input (m=0xc059f100, off0=20, proto=6) at ../../netinet/tcp_input.c:2220 #14 0xc0194717 in ip_input (m=0xc059f100) at ../../netinet/ip_input.c:731 #15 0xc0194777 in ipintr () at ../../netinet/ip_input.c:759 #16 0xc02281e5 in swi_net_next () (kgdb) frame 11 #11 0xc015b230 in m_copym (m=0xc0627000, off0=7693, len=150, wait=1) at ../../kern/uipc_mbuf.c:621 621 n->m_pkthdr.len -= off0; (kgdb) p n->m_pkthdr.len There is no member named m_pkthdr. (kgdb) p n $1 = (struct mbuf *) 0x67063a (kgdb) p off0 $2 = 7693 (kgdb) up #12 0xc019a521 in tcp_output (tp=0xc6275b60) at ../../netinet/tcp_output.c:590 590 m->m_next = m_copy(so->so_snd.sb_mb, off, (int) len); (kgdb) p so->so_snd.sb_mb $3 = (struct mbuf *) 0xc0623c00 (kgdb) p off $4 = 7693 (kgdb) p len $5 = 1099 (kgdb) up #13 0xc0199719 in tcp_input (m=0xc059f100, off0=20, proto=6) at ../../netinet/tcp_input.c:2220 2220 (void) tcp_output(tp); (kgdb) p tp $6 = (struct tcpcb *) 0xc6275b60 (kgdb) --ELM996673269-424-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 6:59:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from support.euronet.nl (support.euronet.nl [194.134.32.134]) by hub.freebsd.org (Postfix) with ESMTP id C127C37B401 for ; Wed, 1 Aug 2001 06:59:35 -0700 (PDT) (envelope-from free@support.euronet.nl) Received: (from free@localhost) by support.euronet.nl (8.11.3/8.11.0) id f71DxYq38360 for freebsd-hackers@freebsd.org; Wed, 1 Aug 2001 15:59:34 +0200 (CEST) Date: Wed, 1 Aug 2001 15:59:34 +0200 From: Frederique Rijsdijk To: freebsd-hackers@freebsd.org Subject: connecting a FujiFinePix1400 (USB) ? Message-ID: <20010801155934.B36262@support.euronet.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Uptime: 3:51PM up 15 days, 18 hrs, 131 users, load averages: 0.91, 0.76, 0.62 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is it possible to connect a digital camera with a USB interface (FujiFinePix1400 in this case) to a FreeBSD (3.4-S) host to download the images? Thanks, -- Frederique To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 7: 6:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m04.mx.aol.com (imo-m04.mx.aol.com [64.12.136.7]) by hub.freebsd.org (Postfix) with ESMTP id 6154237B401 for ; Wed, 1 Aug 2001 07:06:47 -0700 (PDT) (envelope-from oldcpgmr@netscape.net) Received: from oldcpgmr@netscape.net by imo-m04.mx.aol.com (mail_out_v31.9.) id n.10b.54f161 (16244) for ; Wed, 1 Aug 2001 10:06:41 -0400 (EDT) Received: from netscape.com (mow-m03.webmail.aol.com [64.12.184.131]) by air-in03.mail.aol.com (v79.27) with ESMTP id MAILININ38-0801100640; Wed, 01 Aug 2001 10:06:40 -0400 Date: Wed, 01 Aug 2001 10:06:40 -0400 From: oldcpgmr@netscape.net To: freebsd-hackers@freebsd.org Subject: FreeBSD 4.3 and windows 98 don't play well together Message-ID: <7FF44286.641420F8.00A40C08@netscape.net> X-Mailer: Atlas Mailer 1.0 Content-Type: text/plain; charset=iso-8859-1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I was wondering whether someone could shed some light on this for me: I've installed FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everything is fine except that after using FreeBSD if I try to go into windows, the system locks up. If I turn the power off and back on after attempting to boot windows once, it works fine. I realize several things: 1) The 4 gigs occupied by windows would make a dandy filesystem for BSD (but I need windows for work). 2) The computer may be recoiling at the prospect of going from an OS which is a Good Thing to one that is the quintissential Bad Thing. 3) It isn't FreeBSD's job to make M$ products work. Any ideas? Thanks! Mark Van Tuyl __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 7:23:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailgate.imagination.co.uk (mailgate.imagination.co.uk [212.140.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 0CB9337B403 for ; Wed, 1 Aug 2001 07:23:52 -0700 (PDT) (envelope-from aledm@qix.co.uk) Received: from qix.co.uk (dhcp-76-157.imagination.co.uk [192.168.76.157]) by mailgate.imagination.co.uk (8.9.3/8.9.3) with ESMTP id OAA02157; Wed, 1 Aug 2001 14:23:48 GMT Message-ID: <3B68114E.FBBC0F13@qix.co.uk> Date: Wed, 01 Aug 2001 15:25:18 +0100 From: Aled Morris X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: oldcpgmr@netscape.net Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 4.3 and windows 98 don't play well together Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I was wondering whether someone could shed some light on this for me: I've installed >FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everything is fine except >that after using FreeBSD if I try to go into windows, the system locks up. If I turn >the power off and back on after attempting to boot windows once, it works fine. I have the same kind of problem with my Toshiba Portege 3440CT laptop. After using FreeBSD and XFree86, if I reboot into Windows without turning the power off completely (i.e. if I type "reboot") Windows 98 gets very confused about the state of the video card, and comes up in 640x480 mode. Only a cold boot fixes it. It seems that there is more to a "reboot" than simply reloading the software, there must some procedure for resetting the hardware to its power-on state that FreeBSD isn't implementing. Aled -- ++ Amazingly cheap server hosting in Telehouse, London ++ ++ http://www.qix.co.uk/colo/ ++ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 7:47:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from naboo.ethz.ch (naboo.ethz.ch [129.132.17.66]) by hub.freebsd.org (Postfix) with ESMTP id 91BA737B401 for ; Wed, 1 Aug 2001 07:47:51 -0700 (PDT) (envelope-from carlo@vis.ethz.ch) Received: by naboo.ethz.ch (Postfix, from userid 224) id 3438A275B6; Wed, 1 Aug 2001 16:47:45 +0200 (CEST) Subject: Re: FreeBSD 4.3 and windows 98 don't play well together To: aledm@qix.co.uk (Aled Morris) Date: Wed, 1 Aug 2001 16:47:45 +0200 (CEST) Cc: oldcpgmr@netscape.net, freebsd-hackers@FreeBSD.ORG In-Reply-To: <3B68114E.FBBC0F13@qix.co.uk> from "Aled Morris" at Aug 01, 2001 03:25:18 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010801144745.3438A275B6@naboo.ethz.ch> From: carlo@vis.ethz.ch (Carlo Dapor) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My laptop, a Toshiba Tecra 8100 with a 12 GB, evenly divided in two partitions runs with none of the problems described. I run Windows 98 on the first partition (dev/ad0s) and FreeBSD on the second (dev/ad0s2*). Could it be a version problem ? XFree 4.0.1 and FreeBSD 5.0 (current) is what I have. It could also be the X graphic card driver. This question goes to the original poster: dO You see the same behaviour after X11 on Linux and rebooting ? Which versions of XFree are You running ? Ciao, derweil, -- Carlo > >I was wondering whether someone could shed some light on this for me: I've installed > >FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everything is fine except > >that after using FreeBSD if I try to go into windows, the system locks up. If I turn > >the power off and back on after attempting to boot windows once, it works fine. > > I have the same kind of problem with my Toshiba Portege 3440CT laptop. After > using FreeBSD and XFree86, if I reboot into Windows without turning the power > off completely (i.e. if I type "reboot") Windows 98 gets very confused about the > state of the video card, and comes up in 640x480 mode. Only a cold boot fixes it. > > It seems that there is more to a "reboot" than simply reloading the software, > there must some procedure for resetting the hardware to its power-on state that > FreeBSD isn't implementing. > > Aled > -- > ++ Amazingly cheap server hosting in Telehouse, London ++ > ++ http://www.qix.co.uk/colo/ ++ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 8:32:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 3788C37B403 for ; Wed, 1 Aug 2001 08:32:35 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f71FWY410330 for ; Wed, 1 Aug 2001 11:32:34 -0400 (EDT) Date: Wed, 1 Aug 2001 11:32:15 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: Allocate a page at interrupt time Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD can not allocate from the PQ_CACHE queue in an interrupt context. Can anyone explain it to me why this is the case? Thanks, -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 8:34:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f34.pav2.hotmail.com [64.4.37.34]) by hub.freebsd.org (Postfix) with ESMTP id CBD1837B403 for ; Wed, 1 Aug 2001 08:34:26 -0700 (PDT) (envelope-from weiguang_shi@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 1 Aug 2001 08:34:26 -0700 Received: from 129.128.29.128 by pv2fd.pav2.hotmail.msn.com with HTTP; Wed, 01 Aug 2001 15:34:26 GMT X-Originating-IP: [129.128.29.128] From: "Weiguang SHI" To: tlambert2@mindspring.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: address resolution question Date: Wed, 01 Aug 2001 09:34:26 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 01 Aug 2001 15:34:26.0754 (UTC) FILETIME=[72947A20:01C11A9F] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ... > > According to my calculation, pte=0xbfcc0001 and *pte will yield > > 0x2FF,0xC0,0x1 as indexes to the page directory table, page table and > > an offset. My page directory table is like this (starting at physical > > address 0x2C2000): > > > > index page_table_base_address; prot > > ---------- ----------------------------- > > 0,0x1D 0x2A4,0x2C1 ; RW > > 0x2FF 0x2C2 ; RW > > 0x300,0x31D 0x2A4,0x2C1 ; RW > > > > The entries that are not listed are all zeros. This table was created > > by "create_pagetable" in locore.s > > > > I know there is a recursive reference, i.e., the 0x2ff entry. But I > > need more (authoritative) explanation on how the triple > > (0x2ff,0xc0,0x1) is going to be resolved. > > > > Would you shed some light? > >It gets resolved as the address 0x0C001000. It is a page address >for a 4k page (hint: 0x1000 * 0xc001). Thanks but I don't get it yet. You see 0x2ff is the index to the PTD (page table directory) here, which refers to 0x2c2000 (physical address of the page table) and this address is where the PTD itself starts (a recursive reference). So the second index, 0xc0, is applied again to this very PTD, though now used as a PD (Page Table), to get an entry. However, the entry it indexes to is all zero. Does this cause a page fault? (the idt has been set up till now.) >The lower area of memory is a 16MB region, when trapping to virtual >8086 mode. The kernel is loaded starting at 1MB in the virtual I think it is loaded starting 0xc0000000 in virtual address space though it is loaded physically just above 1M. Weiguang _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 10:13: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (unknown [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 2594137B407 for ; Wed, 1 Aug 2001 10:12:50 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 4599 invoked by uid 1000); 1 Aug 2001 17:11:46 -0000 Date: Wed, 1 Aug 2001 20:11:46 +0300 From: Peter Pentchev To: Kris Kennaway Cc: Hans Zaunere , freebsd-hackers@FreeBSD.ORG Subject: Re: Accessing /dev/klog and similar Message-ID: <20010801201146.C4274@ringworld.oblivion.bg> Mail-Followup-To: Kris Kennaway , Hans Zaunere , freebsd-hackers@FreeBSD.ORG References: <20010730185018.10922.qmail@web12807.mail.yahoo.com> <20010730143521.A69771@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730143521.A69771@xor.obsecurity.org>; from kris@obsecurity.org on Mon, Jul 30, 2001 at 02:35:21PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 30, 2001 at 02:35:21PM -0700, Kris Kennaway wrote: > On Mon, Jul 30, 2001 at 11:50:18AM -0700, Hans Zaunere wrote: > > Hello, > > > > I'm looking to access kernel messages directly from > > the kernel, and not through syslog if I can help it. > > Look at how syslogd does it. Or rather, do not try this while syslogd is running. src/sys/kern/subr_log.c defines the operation of the /dev/klog device, and there is an upper limit on the number of processes that can simultaneously open the log device - the limit is one. That is, while syslogd is running, no other process can open the klog device for reading. This seems to have been the case ever since rev. 1.1 of src/sys/kern/subr_log.c; that is, this has been the case in 4.4BSD and earlier. Anybody have any recollection on why the kernel won't let more than one process intercept log messages (aside from the obvious fact that stacked syslogd's could easily DoS a machine)? G'luck, Peter -- because I didn't think of a good beginning of it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 10:28:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 2415F37B401 for ; Wed, 1 Aug 2001 10:28:21 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA40859; Wed, 1 Aug 2001 12:30:49 -0700 (PDT) Date: Wed, 1 Aug 2001 12:30:47 -0700 (PDT) From: Julian Elischer To: "Eugene L. Vorokov" Cc: Mohana Krishna Penumetcha , freebsd-hackers@freebsd.org Subject: Re: crash dump output In-Reply-To: <200108010741.f717fXs06699@bugz.infotecs.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG no, as long as your swap device is big enough to hold all of RAM it will work.. you are supposed to use your normal swap device. it reads it off and saves it elsewhere as teh first thing it does after booting, before you've had a chance to start swapping.. On Wed, 1 Aug 2001, Eugene L. Vorokov wrote: > > > Maybe it's offtopic a bit, but can you please give exact instructions of how > > > to compile debug kernel ? My machine crashes sometimes too, I tried to compile > > > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or > > > is there any URL with a good explanation ? > > > > you just call config with '-g' option. and compile the kernel in normal > > way. The freebsd handbook discusses this in more detail. > > Hmm. It seems like I need spare swap device for crashdump ? What can I do > if I have no room on disk for this ? Can normal swap device be used, and > if yes, how to save core on panic ? I think swap device contents will be > lost on the next reboot ... > > Regards, > Eugene > > > 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 Aug 1 10:49:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (sat.dis.org [216.240.44.14]) by hub.freebsd.org (Postfix) with ESMTP id 8AB9D37B406 for ; Wed, 1 Aug 2001 10:49:29 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f71HpdJ01717; Wed, 1 Aug 2001 10:51:39 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108011751.f71HpdJ01717@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: oldcpgmr@netscape.net Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD 4.3 and windows 98 don't play well together In-reply-to: Your message of "Wed, 01 Aug 2001 10:06:40 EDT." <7FF44286.641420F8.00A40C08@netscape.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Aug 2001 10:51:39 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I was wondering whether someone could shed some light on this for me: I've i > nstalled FreeBSD 4.3, Debian Linux 2.2r2 and windows 98 on my laptop. Everyt > hing is fine except that after using FreeBSD if I try to go into windows, the > system locks up. If I turn the power off and back on after attempting to bo > ot windows once, it works fine. I realize several things: > 1) The 4 gigs occupied by windows would make a dandy filesystem for BSD > (but I need windows for work). > 2) The computer may be recoiling at the prospect of going from an OS > which is a Good Thing to one that is the quintissential Bad Thing. > 3) It isn't FreeBSD's job to make M$ products work. > Any ideas? Windows/BIOS bug; some of your hardware isn't being reset correctly. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 11:59:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138]) by hub.freebsd.org (Postfix) with ESMTP id CA03F37B401 for ; Wed, 1 Aug 2001 11:59:07 -0700 (PDT) (envelope-from dima@unixfreak.org) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 7D5BE3E31; Wed, 1 Aug 2001 11:58:57 -0700 (PDT) Received: from bazooka.unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 723503C12B; Wed, 1 Aug 2001 11:58:57 -0700 (PDT) To: Peter Pentchev Cc: Kris Kennaway , Hans Zaunere , freebsd-hackers@FreeBSD.ORG Subject: Re: Accessing /dev/klog and similar In-Reply-To: <20010801201146.C4274@ringworld.oblivion.bg>; from roam@orbitel.bg on "Wed, 1 Aug 2001 20:11:46 +0300" Date: Wed, 01 Aug 2001 11:58:52 -0700 From: Dima Dorfman Message-Id: <20010801185857.7D5BE3E31@bazooka.unixfreak.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev writes: > Or rather, do not try this while syslogd is running. > > src/sys/kern/subr_log.c defines the operation of the /dev/klog > device, and there is an upper limit on the number of processes > that can simultaneously open the log device - the limit is one. > That is, while syslogd is running, no other process can open > the klog device for reading. > > This seems to have been the case ever since rev. 1.1 of > src/sys/kern/subr_log.c; that is, this has been the case > in 4.4BSD and earlier. Anybody have any recollection > on why the kernel won't let more than one process intercept > log messages (aside from the obvious fact that stacked syslogd's > could easily DoS a machine)? Take a look at how it spits out those messages and you'll see why. In short, if you have two processes reading them, neither will get the full set because a read advances the read pointer (msgbufp->bufp, IIRC). This can't easily be fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 13:32: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id EAC7637B618 for ; Wed, 1 Aug 2001 13:31:57 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id NAA29108; Wed, 1 Aug 2001 13:31:42 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200108010656.f716ucZ02371@bugz.infotecs.ru> Date: Wed, 01 Aug 2001 13:23:05 -0700 (PDT) From: John Baldwin To: "Eugene L. Vorokov" Subject: Re: crash dump output Cc: freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 01-Aug-01 Eugene L. Vorokov wrote: >> Can you compile a debug kernel please and repeat this? That way you will >> have >> debug symbols so that you can get more useful information out of gdb. >> You'll >> have to get a new crashdump with the debug kernel running however. > > Maybe it's offtopic a bit, but can you please give exact instructions of how > to compile debug kernel ? My machine crashes sometimes too, I tried to > compile > debug kernel, but it seemed not so easy and I gave up due to lack of time. Or > is there any URL with a good explanation ? Check the kernel debugging chapter of the handbook. Passing the '-g' flag to config should do the trick for 4.x IIRC. That is instead of doing 'config FOO' you do 'config -g FOO' while building your kernel. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Wed Aug 1 14: 3:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52]) by hub.freebsd.org (Postfix) with ESMTP id 7586737B401 for ; Wed, 1 Aug 2001 14:03:17 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([65.92.113.104]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010801210316.GQTP27217.tomts8-srv.bellnexxia.net@penix.org>; Wed, 1 Aug 2001 17:03:16 -0400 Message-ID: <3B6839F0.5080906@penix.org> Date: Wed, 01 Aug 2001 17:18:40 +0000 From: Paul Halliday User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.2) Gecko/20010722 X-Accept-Language: en-us MIME-Version: 1.0 To: Frederique Rijsdijk Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: connecting a FujiFinePix1400 (USB) ? References: <20010801155934.B36262@support.euronet.nl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Frederique Rijsdijk wrote: > Is it possible to connect a digital camera with a USB interface > (FujiFinePix1400 in this case) to a FreeBSD (3.4-S) host to download > the images? > > Thanks, > heh.. freebsd usb sucks. I have a handspring and a fujifilm finepix40i that are just sitting here collecting dust. From 3.4 - 4.3 S I have tried every available means, packages, patches to get either of them working with 0 luck. If you do happen to get it up and running, please let me know how you achieved such a miraculous feat. > > -- Frederique > -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 18:16:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.tgegroup.com (unknown [202.108.126.66]) by hub.freebsd.org (Postfix) with ESMTP id 9930337B406 for ; Wed, 1 Aug 2001 18:16:11 -0700 (PDT) (envelope-from craiglei@pasia.com.cn) Received: from fdsaf ([10.10.26.5]) by mail.tgegroup.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id QDBKSH2H; Thu, 2 Aug 2001 08:41:08 +0800 Message-ID: <002701c11aed$ae1b98a0$051a0a0a@fd.com> From: "craig" To: Cc: Subject: How to visit physical memory above 4G? Date: Thu, 2 Aug 2001 08:53:38 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0022_01C11B30.9F1331E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0022_01C11B30.9F1331E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 IA0KSSBrbm93IFBJSUkgY2FuIHN1cHBvcnQgNjRHIHBoeXNpY2FsIG1lbW9yeS4gSW4gRnJlZUJT RCBob3cgY2FuIEkgdmlzaXQgc3VjaCByYW5nZSBtZW1vcnkoNEctNjRHKSA/DQoNCg0KY3JhaWds ZWlAcGFzaWEuY29tLmNuDQo= ------=_NextPart_000_0022_01C11B30.9F1331E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4yNjE0LjM1MDAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9E SVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIGtub3cgUElJSSBjYW4gc3VwcG9ydCA2NEcgcGh5c2lj YWwgbWVtb3J5LiBJbiBGcmVlQlNEIGhvdyANCmNhbiBJIHZpc2l0IHN1Y2ggcmFuZ2UgbWVtb3J5 KDRHLTY0RykgPzwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwv RElWPg0KPERJVj48Rk9OVCBzaXplPTI+Y3JhaWdsZWlAcGFzaWEuY29tLmNuPC9GT05UPjwvRElW PjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_0022_01C11B30.9F1331E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 18:34:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 7D64937B401 for ; Wed, 1 Aug 2001 18:34:48 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f721YjK52828 for ; Wed, 1 Aug 2001 21:34:46 -0400 (EDT) Message-ID: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> From: "Joseph Gleason" To: Subject: Finding filesizes in C++ for files greater than 4gb Date: Wed, 1 Aug 2001 21:34:43 -0400 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 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In FreeBSD, how can I determine the size of a file in C++ when the file is greater than 4gb? Currently, I use stat() and use st_size. That is limited to 4gb (32bit unsigned int) I could use st_blocks, but that wouldn't give me the exact size. (st_blocks -1) * 512 + (st_size % 512) This would make sense, but in tests st_blocks is larger than I would expect. I assume it means that st_blocks is how many blocks the file takes up on the filesystem, and does not directly translate to how large the file is. Backgound: I have some C++ utilities for manipulating files. I have recently (and not supprisingly) discovered that my program has issues with file sizes greater than 4gb because I use an unsigned int for something. I guess I will have to switch to unsigned long long, which appears to be a 64bit int. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 18:41:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 188A837B401 for ; Wed, 1 Aug 2001 18:41:43 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id EB21181D06; Wed, 1 Aug 2001 20:41:32 -0500 (CDT) Date: Wed, 1 Aug 2001 20:41:32 -0500 From: Alfred Perlstein To: Joseph Gleason Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Finding filesizes in C++ for files greater than 4gb Message-ID: <20010801204132.K26571@elvis.mu.org> References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00b201c11af3$4fef1c10$0a2d2d0a@battleship>; from clash@tasam.com on Wed, Aug 01, 2001 at 09:34:43PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Joseph Gleason [010801 20:35] wrote: > In FreeBSD, how can I determine the size of a file in C++ when the file is > greater than 4gb? > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > unsigned int) No it's not: struct stat { dev_t st_dev; /* inode's device */ ... off_t st_size; /* file size, in bytes */ off_t is 64 bits under FreeBSD. A bunch of other unix systems have alternate system calls to get 64bit attributes for files. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 18:42:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with SMTP id 4EFBA37B401 for ; Wed, 1 Aug 2001 18:42:32 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 66840 invoked from network); 2 Aug 2001 01:42:31 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 2 Aug 2001 01:42:31 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> Date: Wed, 01 Aug 2001 18:42:32 -0700 (PDT) From: John Baldwin To: Joseph Gleason Subject: RE: Finding filesizes in C++ for files greater than 4gb Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Aug-01 Joseph Gleason wrote: > In FreeBSD, how can I determine the size of a file in C++ when the file is > greater than 4gb? > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > unsigned int) struct stat { ... off_t st_size; /* file size, in bytes */ ... } /usr/include/sys/types.h:typedef _BSD_OFF_T_ off_t; /* file offset */ /usr/include/machine/ansi.h:#define _BSD_OFF_T_ __int64_t /* file offset */ st_size is not 32 bits on any arch's FreeBSD runs on. However, you need to include and use off_t for file offsets rather than int or long, which should fix your problem. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Wed Aug 1 18:46:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 3DF8637B403 for ; Wed, 1 Aug 2001 18:46:09 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (root@spare0.gsoft.com.au [203.38.152.114]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA02208; Thu, 2 Aug 2001 11:15:57 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.7 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> Date: Thu, 02 Aug 2001 11:15:56 +0930 (CST) From: "Daniel O'Connor" To: Joseph Gleason Subject: RE: Finding filesizes in C++ for files greater than 4gb Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Aug-2001 Joseph Gleason wrote: > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > unsigned int) > > I could use st_blocks, but that wouldn't give me the exact size. > > (st_blocks -1) * 512 + (st_size % 512) > > This would make sense, but in tests st_blocks is larger than I would expect. > I assume it means that st_blocks is how many blocks the file takes up on the > filesystem, and does not directly translate to how large the file is. st_size is an off_t which is typedef'd to _BSD_OFF_T_ which is #define'd as __int64_t. So.. you're program should grok >4Gb files. > I have some C++ utilities for manipulating files. I have recently (and not > supprisingly) discovered that my program has issues with file sizes greater > than 4gb because I use an unsigned int for something. I guess I will have > to switch to unsigned long long, which appears to be a 64bit int. I would explicitly use off_t for file offsets/sizes which is what it is designed for. If you want an explicit bit width use it, eg u_int64_t etc. That way you get what you ask for rather than second guessing the implementor. --- 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 Wed Aug 1 18:47: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 5A03337B403 for ; Wed, 1 Aug 2001 18:46:58 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.mybox.zip ([207.214.149.105]) by mta5.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GHF00E583KQAV@mta5.snfc21.pbi.net> for hackers@freebsd.org; Wed, 01 Aug 2001 18:46:54 -0700 (PDT) Received: by zippy.mybox.zip (Postfix, from userid 1000) id 049D71844; Wed, 01 Aug 2001 18:45:31 -0700 (PDT) Date: Wed, 01 Aug 2001 18:45:31 -0700 From: Alex Zepeda Subject: Re: Finding filesizes in C++ for files greater than 4gb In-reply-to: <"from clash"@tasam.com> To: Joseph Gleason , hackers@freebsd.org Message-id: <20010801184531.A7725@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.2.5i References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: > In FreeBSD, how can I determine the size of a file in C++ when the file is > greater than 4gb? > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > unsigned int) You're wrong. Read the man page. No soup for you! Next! - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 19:31:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 4E3F037B401 for ; Wed, 1 Aug 2001 19:31:35 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f722VMq01091; Wed, 1 Aug 2001 22:31:28 -0400 (EDT) Message-ID: <003c01c11afb$3cdc7980$0a2d2d0a@battleship> From: "Joseph Gleason" To: "Alex Zepeda" , References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <20010801184531.A7725@zippy.mybox.zip> Subject: Re: Finding filesizes in C++ for files greater than 4gb Date: Wed, 1 Aug 2001 22:31:22 -0400 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 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Alex Zepeda" To: "Joseph Gleason" ; Sent: Wednesday, August 01, 2001 21:45 Subject: Re: Finding filesizes in C++ for files greater than 4gb > On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: > > > In FreeBSD, how can I determine the size of a file in C++ when the file is > > greater than 4gb? > > > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > > unsigned int) > > You're wrong. Read the man page. No soup for you! Next! > > - alex Alright, I made a mistake. But I did read the man page. Where does it say off_t is 64bits? My mistake was not digging through the include files enough to see what was going on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 19:34:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nipsi.home.net (dsl-213-023-032-171.arcor-ip.net [213.23.32.171]) by hub.freebsd.org (Postfix) with SMTP id B9EC737B403 for ; Wed, 1 Aug 2001 19:34:24 -0700 (PDT) (envelope-from HypnotiZer@gmx.net) Received: (qmail 20391 invoked from network); 2 Aug 2001 02:33:06 -0000 Received: from nachpolierer.home.net (HELO nachpolierer) (172.16.1.101) by nipsi.home.net with SMTP; 2 Aug 2001 02:33:06 -0000 Message-ID: <001c01c11afc$15bb1ef0$650110ac@nachpolierer> From: "Dennis Berger" To: Subject: somebody implement ppp nat punch-fw ? Date: Thu, 2 Aug 2001 04:37:34 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0019_01C11B0C.D9319F70" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0019_01C11B0C.D9319F70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, A function available from libalias, the PKT_ALIAS_PUNCH_FW one is = currently not implemented in ppp. Maybe somebody could implement it in = ppp. It's definitly not much work, so I request if somebody could do it. greets Dennis ------=_NextPart_000_0019_01C11B0C.D9319F70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
A function available from libalias, the = PKT_ALIAS_PUNCH_FW one is currently not implemented in ppp. Maybe = somebody could=20 implement it in ppp. It's definitly not much work, so I request if = somebody=20 could do it.
greets=20 Dennis
------=_NextPart_000_0019_01C11B0C.D9319F70-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 19:40: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-1.enteract.com (smtp-1.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 9CE6137B401 for ; Wed, 1 Aug 2001 19:40:02 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-1.enteract.com (shell-1.enteract.com [207.229.143.40]) by smtp-1.enteract.com (Postfix) with ESMTP id 1AF416A59; Wed, 1 Aug 2001 21:40:02 -0500 (CDT) Date: Wed, 1 Aug 2001 21:40:02 -0500 (CDT) From: David Scheidt X-X-Sender: To: Joseph Gleason Cc: Subject: Re: Finding filesizes in C++ for files greater than 4gb In-Reply-To: <003c01c11afb$3cdc7980$0a2d2d0a@battleship> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 1 Aug 2001, Joseph Gleason wrote: : :----- Original Message ----- :From: "Alex Zepeda" :> On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: :> :> > In FreeBSD, how can I determine the size of a file in C++ when the file :is :> > greater than 4gb? :> > :> > Currently, I use stat() and use st_size. That is limited to 4gb (32bit :> > unsigned int) :> :> You're wrong. Read the man page. No soup for you! Next! :> :> - alex : : :Alright, I made a mistake. But I did read the man page. Where does it say :off_t is 64bits? : :My mistake was not digging through the include files enough to see what was :going on. : The types(5) manpage will tell you this. -- dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 19:43:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 2859737B401 for ; Wed, 1 Aug 2001 19:43:20 -0700 (PDT) (envelope-from clash@tasam.com) Received: from battleship (zogbe.tasam.com [10.45.45.5] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f722hAq01350; Wed, 1 Aug 2001 22:43:11 -0400 (EDT) Message-ID: <002a01c11afc$e0e29130$0a2d2d0a@battleship> From: "Joseph Gleason" To: "David Scheidt" Cc: References: Subject: Re: Finding filesizes in C++ for files greater than 4gb Date: Wed, 1 Aug 2001 22:43:06 -0400 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 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > :Alright, I made a mistake. But I did read the man page. Where does it say > :off_t is 64bits? > : > :My mistake was not digging through the include files enough to see what was > :going on. > : > > The types(5) manpage will tell you this. > Ahh, thank you. I was not aware that existed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 19:56:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by hub.freebsd.org (Postfix) with SMTP id E1D7537B403 for ; Wed, 1 Aug 2001 19:56:54 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 2 Aug 2001 02:56:54 -0000 X-Apparently-From: Message-ID: <3B68C175.E8E8D444@yahoo.com> Date: Wed, 01 Aug 2001 21:56:53 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Joseph Gleason Cc: Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <20010801184531.A7725@zippy.mybox.zip> <003c01c11afb$3cdc7980$0a2d2d0a@battleship> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joseph Gleason wrote: > > ----- Original Message ----- > From: "Alex Zepeda" > To: "Joseph Gleason" ; > Sent: Wednesday, August 01, 2001 21:45 > Subject: Re: Finding filesizes in C++ for files greater than 4gb > > > On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: > > > > > In FreeBSD, how can I determine the size of a file in C++ when the file > is > > > greater than 4gb? > > > > > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > > > unsigned int) > > > > You're wrong. Read the man page. No soup for you! Next! > > > > - alex > > Alright, I made a mistake. But I did read the man page. Where does it say > off_t is 64bits? > > My mistake was not digging through the include files enough to see what was > going on. I think you got him on that, but [cut and paste of two consecutive lines from the manpage]... off_t st_size; /* file size, in bytes */ int64_t st_blocks; /* blocks allocated for file */ If the manpage specifies int64_t for the blocks, even though off_t isn't specified in the manpage, what does it lead you to assume? Although 64-bit file sizes have been part of FreeBSD since 2.0-RELEASE back in 1994 [as I recall], maybe the manpages should reflect this fact by means other than the deductive reasoning outlined above. Joseph has made a good point. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 20: 0:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.urx.com (mail.urx.com [63.170.19.36]) by hub.freebsd.org (Postfix) with ESMTP id 7BA8B37B401 for ; Wed, 1 Aug 2001 20:00:33 -0700 (PDT) (envelope-from kstewart@urx.com) Received: from urx.com [206.159.132.160] by mail.urx.com with ESMTP (SMTPD32-6.06) id A24433F02C0; Wed, 01 Aug 2001 20:00:20 -0700 Message-ID: <3B68C244.20A4E2C9@urx.com> Date: Wed, 01 Aug 2001 20:00:20 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: kc5vdj@yahoo.com Cc: Joseph Gleason , Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <20010801184531.A7725@zippy.mybox.zip> <003c01c11afb$3cdc7980$0a2d2d0a@battleship> <3B68C175.E8E8D444@yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jim Bryant wrote: > > Joseph Gleason wrote: > > > > ----- Original Message ----- > > From: "Alex Zepeda" > > To: "Joseph Gleason" ; > > Sent: Wednesday, August 01, 2001 21:45 > > Subject: Re: Finding filesizes in C++ for files greater than 4gb > > > > > On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: > > > > > > > In FreeBSD, how can I determine the size of a file in C++ when the file > > is > > > > greater than 4gb? > > > > > > > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > > > > unsigned int) > > > > > > You're wrong. Read the man page. No soup for you! Next! > > > > > > - alex > > > > Alright, I made a mistake. But I did read the man page. Where does it say > > off_t is 64bits? > > > > My mistake was not digging through the include files enough to see what was > > going on. > > I think you got him on that, but [cut and paste of two consecutive lines from the manpage]... > > off_t st_size; /* file size, in bytes */ > int64_t st_blocks; /* blocks allocated for file */ > > If the manpage specifies int64_t for the blocks, even though off_t isn't specified in the manpage, what does it lead you to assume? > > Although 64-bit file sizes have been part of FreeBSD since 2.0-RELEASE back in 1994 [as I recall], maybe the manpages should reflect > this fact by means other than the deductive reasoning outlined above. Joseph has made a good point. Just so someone can see it. coral# grep BSD_OFF *.h ansi.h:#define _BSD_OFF_T_ __int64_t /* file offset */ coral# pwd /usr/include/machine Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 20: 4:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id EABC837B405 for ; Wed, 1 Aug 2001 20:04:35 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id CA25081D06; Wed, 1 Aug 2001 22:04:25 -0500 (CDT) Date: Wed, 1 Aug 2001 22:04:25 -0500 From: Bill Fumerola To: Paul Halliday Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: connecting a FujiFinePix1400 (USB) ? Message-ID: <20010801220425.V2759@elvis.mu.org> References: <20010801155934.B36262@support.euronet.nl> <3B6839F0.5080906@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B6839F0.5080906@penix.org>; from dp@penix.org on Wed, Aug 01, 2001 at 05:18:40PM +0000 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 05:18:40PM +0000, Paul Halliday wrote: > heh.. freebsd usb sucks. > I have a handspring and a fujifilm finepix40i that are just sitting here > collecting dust. > > > From 3.4 - 4.3 S I have tried every available means, packages, patches > to get either of them working with 0 luck. > > If you do happen to get it up and running, please let me know how you > achieved such a miraculous feat. freebsd usb sucks? no. application support sucks. I've found freebsd's usb drivers present applications everything they need to support hardware such as this and normally its the available applications (gphoto, in this case) that fall short. -- Bill Fumerola / billf@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 Aug 1 20:29:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by hub.freebsd.org (Postfix) with SMTP id 2D6F337B401 for ; Wed, 1 Aug 2001 20:29:41 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 2 Aug 2001 03:29:40 -0000 X-Apparently-From: Message-ID: <3B68C923.9C175779@yahoo.com> Date: Wed, 01 Aug 2001 22:29:39 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: kstewart@urx.com Cc: Joseph Gleason , Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <20010801184531.A7725@zippy.mybox.zip> <003c01c11afb$3cdc7980$0a2d2d0a@battleship> <3B68C175.E8E8D444@yahoo.com> <3B68C244.20A4E2C9@urx.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kent Stewart wrote: > > Jim Bryant wrote: > > > > Joseph Gleason wrote: > > > > > > ----- Original Message ----- > > > From: "Alex Zepeda" > > > To: "Joseph Gleason" ; > > > Sent: Wednesday, August 01, 2001 21:45 > > > Subject: Re: Finding filesizes in C++ for files greater than 4gb > > > > > > > On Wed, Aug 01, 2001 at 09:34:43PM -0400, Joseph Gleason wrote: > > > > > > > > > In FreeBSD, how can I determine the size of a file in C++ when the file > > > is > > > > > greater than 4gb? > > > > > > > > > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > > > > > unsigned int) > > > > > > > > You're wrong. Read the man page. No soup for you! Next! > > > > > > > > - alex > > > > > > Alright, I made a mistake. But I did read the man page. Where does it say > > > off_t is 64bits? > > > > > > My mistake was not digging through the include files enough to see what was > > > going on. > > > > I think you got him on that, but [cut and paste of two consecutive lines from the manpage]... > > > > off_t st_size; /* file size, in bytes */ > > int64_t st_blocks; /* blocks allocated for file */ > > > > If the manpage specifies int64_t for the blocks, even though off_t isn't specified in the manpage, what does it lead you to assume? > > > > Although 64-bit file sizes have been part of FreeBSD since 2.0-RELEASE back in 1994 [as I recall], maybe the manpages should reflect > > this fact by means other than the deductive reasoning outlined above. Joseph has made a good point. > > Just so someone can see it. > > coral# grep BSD_OFF *.h > ansi.h:#define _BSD_OFF_T_ __int64_t /* file offset */ > coral# pwd > /usr/include/machine > > Kent Kent, my point is that the manual page should specify this. I think that's the point the original poster was trying to make once he was told. You should not have to grep ansi.h to determine the type for off_t, if anything, maybe adding BSD_OFF_T to types(5). types(5) states the following for off_t: typedef _BSD_OFF_T_ off_t; /* file offset */ Where does that say 64 bits? Let's see what the references are: SEE ALSO gdb(1), lseek(2), time(3), fs(5) hmmm... maybe lseek? Nope.. The only reference to off_t there is: SYNOPSIS #include off_t lseek(int fildes, off_t offset, int whence); IMHO, the definition of BSD_* belongs in types(5), where it is referenced. But, in fs(5), I see a bit of a deviation from FreeBSD coding practice... u_int64_t fs_maxfilesize;/* maximum representable file size */ Why isn't that defined as off_t or BSD_OFF_T? Bottom line, he went to stat(2) to find this info. stat(2) gives this: SEE ALSO access(2), chmod(2), chown(2), utimes(2), symlink(7) In other words, I went on a hunch that it would be in types(5), but someone not knowing the manpage for types(5) was there would have never found this, nor would it have answered his question, as types(5) only lists BSD_OFF_T as the size, and for the life of me, I'm not sure which manpage specifies that, of course, I'm only an amateur, only having had running FBSD systems since 1.1.5.1-RELEASE. To go off on another tangent... In fs(5), I find this, which directly conflicts with the stat structure listed in stat(2) [quoted from my last post]: int32_t fs_size; /* number of blocks in fs */ So.... Which is it? I can see how someone could get confused, especially the newly initiated. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 22:47:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 2643A37B401 for ; Wed, 1 Aug 2001 22:47:46 -0700 (PDT) (envelope-from jazepeda@pacbell.net) Received: from zippy.mybox.zip ([207.214.149.104]) by mta6.snfc21.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GHF0013SERFRP@mta6.snfc21.pbi.net> for hackers@freebsd.org; Wed, 01 Aug 2001 22:47:42 -0700 (PDT) Received: by zippy.mybox.zip (Postfix, from userid 1000) id C215D182C; Wed, 01 Aug 2001 22:47:37 -0700 (PDT) Date: Wed, 01 Aug 2001 22:47:37 -0700 From: Alex Zepeda Subject: Re: Finding filesizes in C++ for files greater than 4gb In-reply-to: <"from clash"@tasam.com> To: Joseph Gleason , hackers@freebsd.org Message-id: <20010801224737.A608@zippy.mybox.zip> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.2.5i References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <20010801184531.A7725@zippy.mybox.zip> <003c01c11afb$3cdc7980$0a2d2d0a@battleship> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 10:31:22PM -0400, Joseph Gleason wrote: > Alright, I made a mistake. But I did read the man page. Where does it say > off_t is 64bits? > > My mistake was not digging through the include files enough to see what was > going on. off_t st_size; /* file size, in bytes */ All it takes is a printf("%d\n", sizeof(off_t)); to figure out how large that is. :^) Or, sure, you could dig thru the headers. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 22:55:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-80.dsl.lsan03.pacbell.net [63.207.60.80]) by hub.freebsd.org (Postfix) with ESMTP id A7F6437B403 for ; Wed, 1 Aug 2001 22:55:50 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6EFAC66D16; Wed, 1 Aug 2001 22:55:49 -0700 (PDT) Date: Wed, 1 Aug 2001 22:55:49 -0700 From: Kris Kennaway To: craig Cc: tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? Message-ID: <20010801225548.A90084@xor.obsecurity.org> References: <002701c11aed$ae1b98a0$051a0a0a@fd.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <002701c11aed$ae1b98a0$051a0a0a@fd.com>; from craiglei@pasia.com.cn on Thu, Aug 02, 2001 at 08:53:38AM +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 02, 2001 at 08:53:38AM +0800, craig wrote: > =20 > I know PIII can support 64G physical memory. In FreeBSD how can I > visit such range memory(4G-64G) ? You can't, right now. Kris --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7aOtkWry0BWjoQKURAqCtAKCm60PVNTchVjtvDGCBvE8It4+u5gCg3+wc 1v1HmeV28QgepLcNu7O4uTQ= =F9K1 -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:25: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 7CB5637B403 for ; Wed, 1 Aug 2001 23:25:03 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.131.20.Dial1.SanJose1.Level3.net [209.245.131.20]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA21927; Wed, 1 Aug 2001 23:25:00 -0700 (PDT) Message-ID: <3B68F264.BC1FEE21@mindspring.com> Date: Wed, 01 Aug 2001 23:25:40 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Joseph Gleason Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joseph Gleason wrote: > > In FreeBSD, how can I determine the size of a file in C++ when the file is > greater than 4gb? > > Currently, I use stat() and use st_size. That is limited to 4gb (32bit > unsigned int) Uh, st_size is an off_t, which is a signed 64 bit value, not an unsigned 32 bit vale... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:25:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 3600437B401 for ; Wed, 1 Aug 2001 23:25:29 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.131.20.Dial1.SanJose1.Level3.net [209.245.131.20]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA19605; Wed, 1 Aug 2001 23:24:06 -0700 (PDT) Message-ID: <3B68F190.AB04ACB3@mindspring.com> Date: Wed, 01 Aug 2001 23:22:08 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: craig Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: <002701c11aed$ae1b98a0$051a0a0a@fd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > craig wrote: > > > I know PIII can support 64G physical memory. In FreeBSD how can I visit such > range memory(4G-64G) ? The short answer is "you can't". The longer answer is that you end up having to window it using segmentation; if you are familiar with the 4k window on video memory in the TI 99/4A, or the bank select on the 6510 (e.g. the ability to select between 32K of RAM, and 32K of ROM, but not both at the same time, on the Commodore C-64 and the similar arrangement on the C-128, etc.), then you;ll have an idea of how the thing works... assuming you can find a motherboard that can handle it. This basically means that the memory is useless as a DMA target or source for disk controllers or gigabit ethernet cards, and is pretty useless for swap, if you ever have to copy from one section to another (e.g. for IPC, SYSV shared memory, mmap'ed files, VM, or buffer cache, etc.). So for limited uses in data intensive applications, it might be usable, but in general, it's nothing more than a hack so that they can claim to "support" more than 4G, for some extremely limited definition of "support". But to directly answer your question: by rewriting much of the low core virtual memory and page mapping handling code to know about segmentation. Have fun doing this, since by the time you are done, you will probably be able to get IA64 machines for something less than the $7000/unit that you have to pay today, and they will likely have PCI/X, so you have enough bus bandwidth to actually make the RAM halfway usable. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:26:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id D7CC237B401 for ; Wed, 1 Aug 2001 23:26:18 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f726gG202330; Thu, 2 Aug 2001 10:42:16 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108020642.f726gG202330@bugz.infotecs.ru> Subject: Re: crash report In-Reply-To: <200108011709.aa79360@salmon.maths.tcd.ie> "from Ian Dowse at Aug 1, 2001 05:09:46 pm" To: Ian Dowse Date: Thu, 2 Aug 2001 10:42:16 +0400 (MSD) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > In message <200108011341.f71DfAO00453@bugz.infotecs.ru>, "Eugene L. Vorokov" wr > ites: > >fault virtual address = 0x60c0ff00 > > I missed the beginning of this thread, but this looks like a problem > that was fixed just before 4.3-RELEASE. What version of FreeBSD > are you running? It's 4.2-RELEASE. But I had similar problems with 4.3 I think, it was crashing even more frequently (maybe for another reason, I don't know, but panic messages looked the same), that's why I downgraded to 4.2. If that was fixed in 4.3, is there any chance to get the patch that would fix it for 4.2 ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:31: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gull.mail.pas.earthlink.net (gull.mail.pas.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id 670B737B401 for ; Wed, 1 Aug 2001 23:31:04 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.131.20.Dial1.SanJose1.Level3.net [209.245.131.20]) by gull.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA06880; Wed, 1 Aug 2001 23:31:01 -0700 (PDT) Message-ID: <3B68F3CD.DBE3A4FA@mindspring.com> Date: Wed, 01 Aug 2001 23:31:41 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Joseph Gleason Cc: Alex Zepeda , hackers@FreeBSD.ORG Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <20010801184531.A7725@zippy.mybox.zip> <003c01c11afb$3cdc7980$0a2d2d0a@battleship> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joseph Gleason wrote: > Alright, I made a mistake. But I did read the man page. Where does it say > off_t is 64bits? The same place it says char is 8 bits, short is 16 bits, and int and long are 32 bits: in your assumptions. It might be useful (for some definitions of "useful") to have a man page which tells you the size of these things, but FreeBSD runs on architectures where these are different, so you would not be able to have one man page that does it. The correct thing to do is to use off_t when speaking of file lengths/offsets, and then let the machine support what it can support. If you simply "must" know, there's always "sizeof(off_t)". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:34:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from slashetc.net (unknown [61.11.40.63]) by hub.freebsd.org (Postfix) with ESMTP id 865C437B407 for ; Wed, 1 Aug 2001 23:34:39 -0700 (PDT) (envelope-from chirag@slashetc.net) Received: (from chirag@localhost) by slashetc.net (8.11.2/8.11.2) id f726Sid29068; Thu, 2 Aug 2001 11:58:44 +0530 Date: Thu, 2 Aug 2001 11:58:44 +0530 From: Chirag Kantharia To: Terry Lambert Cc: freebsd-hackers@freebsd.org Subject: Re: Finding filesizes in C++ for files greater than 4gb Message-ID: <20010802115844.A29064@epigonaudio.com> Reply-To: Chirag Kantharia References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <3B68F264.BC1FEE21@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B68F264.BC1FEE21@mindspring.com>; from tlambert2@mindspring.com on Wed, Aug 01, 2001 at 11:25:40PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 11:25:40PM -0700, Terry Lambert wrote: | Uh, st_size is an off_t, which is a signed 64 bit value, | not an unsigned 32 bit vale... why should it be `signed' 64 bit and not unsigned? chyrag. -- Chirag Kantharia, slashetc.net/chyrag/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:37: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from maxim.gbch.net (gw.gbch.net [203.24.22.66]) by hub.freebsd.org (Postfix) with SMTP id B441F37B403 for ; Wed, 1 Aug 2001 23:37:03 -0700 (PDT) (envelope-from gjb@gbch.net) Received: (qmail 6662 invoked by uid 1001); 2 Aug 2001 16:36:59 +1000 Message-ID: X-Posted-By: GJB-Post 2.21 16-Jun-2001 X-Operating-System: FreeBSD 4.2-RELEASE i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.gbch.net/gjb.html X-Image-URL: http://www.gbch.net/gjb/gjb-auug048.gif X-GPG-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-PGP-Public-Keys: http://www.gbch.net/keys.html Date: Thu, 02 Aug 2001 16:36:59 +1000 From: Greg Black To: Chirag Kantharia Cc: Terry Lambert , freebsd-hackers@freebsd.org Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <3B68F264.BC1FEE21@mindspring.com> <20010802115844.A29064@epigonaudio.com> In-reply-to: <20010802115844.A29064@epigonaudio.com> of Thu, 02 Aug 2001 11:58:44 +0530 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chirag Kantharia wrote: | On Wed, Aug 01, 2001 at 11:25:40PM -0700, Terry Lambert wrote: | | Uh, st_size is an off_t, which is a signed 64 bit value, | | not an unsigned 32 bit vale... | | why should it be `signed' 64 bit and not unsigned? So that things like lseek(2) can return -1 as an error value. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:44:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id B4B8337B41C for ; Wed, 1 Aug 2001 23:44:48 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.131.20.Dial1.SanJose1.Level3.net [209.245.131.20]) by snipe.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA21569; Wed, 1 Aug 2001 23:44:45 -0700 (PDT) Message-ID: <3B68F705.9815A930@mindspring.com> Date: Wed, 01 Aug 2001 23:45:25 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Chirag Kantharia Cc: freebsd-hackers@freebsd.org Subject: Re: Finding filesizes in C++ for files greater than 4gb References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> <3B68F264.BC1FEE21@mindspring.com> <20010802115844.A29064@epigonaudio.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chirag Kantharia wrote: > > On Wed, Aug 01, 2001 at 11:25:40PM -0700, Terry Lambert wrote: > | Uh, st_size is an off_t, which is a signed 64 bit value, > | not an unsigned 32 bit vale... > > why should it be `signed' 64 bit and not unsigned? Return value for lseek is off_t. -1 indicates error, therefore the sign bit is reserved. This is a historical UNIX-ism, having to do with functions not taking the addresses of their return values as parameters, so that the actual return value could be a pure success/failure code (e.g. like VMS, where you will get SYS$SUCCESS on success, and the actual error code on an error -- this also does away with the need for an errno, which has historically been a huge pain, particularly in threaded programs). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:44:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id C4A4F37B41A for ; Wed, 1 Aug 2001 23:44:35 -0700 (PDT) (envelope-from geoff@hangdog.is.co.za) Received: from hermwas.is.co.za (hermwas.is.co.za [196.23.0.8]) by mercury.is.co.za (Postfix) with ESMTP id DE8573ED2 for ; Thu, 2 Aug 2001 08:44:32 +0200 (SAST) Received: from hangdog.is.co.za (hangdog.is.co.za [196.14.169.128]) by hermwas.is.co.za (8.9.3/8.9.3) with ESMTP id IAA16705 for ; Thu, 2 Aug 2001 08:44:32 +0200 (SAT) Received: (from geoff@localhost) by hangdog.is.co.za (8.11.4/8.11.1) id f726i2K21978 for hackers@freebsd.org; Thu, 2 Aug 2001 08:44:02 +0200 (SAST) (envelope-from geoff) Date: Thu, 2 Aug 2001 08:44:02 +0200 From: Geoff Rehmet To: hackers@freebsd.org Subject: A long way down the road - 3.1 vs 4.3 Message-ID: <20010802084402.A21737@hangdog.is.co.za> Reply-To: Geoff Rehmet Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What may be interesting as a comparison - We are starting the process of upgrading our nameservers, which were installed approximately 2 years ago. Their OS has not been touched, except for a few security patches since then, and they are still running 3.1-STABLE. We have recently brought a third name server on line (as the start of the upgrade process) and it is running 4.3-STABLE. The hardware configs of the machines are identical (Dell Poweredsge 2300, dual 400MHz PII, 256M RAM). However, the 4.3 machine runs have the CPU of the 3.1 machine, using an identical version of BIND. The 3.1 machines started paging to disk after a short while. After a week of operation, and with named growing to 165M, the 4.3 machine hasn't used any of its swap space. This is a good sign of progress. Just for interest, here is the output of top from both machines. The machines are being load-balanced behind a layer 4 switch, so they are getting fairly even request loads. Especially, this shows us that the kernel has become a lot more efficient. (Both machines are running SMP kernels.) 3.1-STABLE: last pid: 91073; load averages: 1.01, 0.88, 0.90 up 73+01:25:21 08:32:19 18 processes: 1 running, 17 sleeping CPU states: 7.6% user, 0.0% nice, 22.0% system, 0.4% interrupt, 70.0% idle Mem: 157M Active, 48M Inact, 34M Wired, 9048K Cache, 8346K Buf, 1704K Free Swap: 1024M Total, 59M Used, 965M Free, 6% Inuse PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 25750 root 2 0 147M 70736K select 1 425:11 41.75% 41.75% named 105 root 2 0 820K 288K select 0 164:04 0.00% 0.00% syslogd 205 root 2 0 1420K 260K select 0 2:50 0.00% 0.00% sshd1 199 root 2 0 1884K 0K select 0 1:57 0.00% 0.00% 161 root 10 0 988K 204K nanslp 0 1:03 0.00% 0.00% cron 58518 root 2 0 896K 140K select 1 0:13 0.00% 0.00% inetd 165 root 18 0 1260K 288K pause 1 0:09 0.00% 0.00% sendmail 1 root 10 0 496K 96K wait 1 0:00 0.00% 0.00% init 91065 geoff 28 0 1556K 800K CPU1 1 0:00 0.00% 0.00% top 91048 geoff 18 0 1280K 904K pause 0 0:00 0.00% 0.00% tcsh 91040 root 2 0 1456K 812K select 0 0:00 0.00% 0.00% sshd1 233 root 3 0 824K 0K ttyin 1 0:00 0.00% 0.00% 234 root 3 0 824K 0K ttyin 1 0:00 0.00% 0.00% 236 root 3 0 820K 0K siodcd 1 0:00 0.00% 0.00% 235 root 3 0 824K 0K ttyin 1 0:00 0.00% 0.00% 237 root 3 0 820K 0K siodcd 1 0:00 0.00% 0.00% 41 root 18 0 204K 0K pause 1 0:00 0.00% 0.00% 4.3-STABLE: last pid: 85896; load averages: 0.11, 0.13, 0.11 up 7+07:30:41 08:32:21 18 processes: 1 running, 17 sleeping CPU states: 3.7% user, 0.0% nice, 1.7% system, 0.6% interrupt, 94.0% idle Mem: 173M Active, 28M Inact, 35M Wired, 12M Cache, 35M Buf, 1488K Free Swap: 1024M Total, 1024M Free PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 7109 root 2 -10 165M 163M select 0 954:14 13.09% 13.09% named 85895 geoff 28 0 1880K 1148K CPU1 0 0:00 0.95% 0.59% top 124 root 2 0 932K 564K select 0 43:11 0.00% 0.00% syslogd 43974 root 2 -12 1264K 784K select 1 0:50 0.00% 0.00% ntpd 153 root 2 0 2548K 1380K select 0 0:17 0.00% 0.00% sshd 94748 root 2 0 1048K 724K select 1 0:14 0.00% 0.00% inetd 146 root 10 0 968K 672K nanslp 0 0:05 0.00% 0.00% cron 85821 root 2 0 2676K 1712K select 1 0:01 0.00% 0.00% sshd 85823 geoff 10 0 1040K 724K wait 1 0:00 0.00% 0.00% bash 185 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 188 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 186 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 191 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 192 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 190 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 189 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty 187 root 3 0 944K 580K ttyin 1 0:00 0.00% 0.00% getty -- Geoff Rehmet, Internet Solutions tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800 email: geoffr@is.co.za URL: http://www.is.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 1 23:48:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (sat.dis.org [216.240.44.14]) by hub.freebsd.org (Postfix) with ESMTP id 874A037B401 for ; Wed, 1 Aug 2001 23:48:34 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f721NNo03244; Wed, 1 Aug 2001 18:23:49 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108020123.f721NNo03244@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "craig" Cc: tlambert2@mindspring.com, freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? In-reply-to: Your message of "Thu, 02 Aug 2001 08:53:38 +0800." <002701c11aed$ae1b98a0$051a0a0a@fd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Aug 2001 18:23:23 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You should format your messages in ascii to send to this list. > I know PIII can support 64G physical memory. In FreeBSD how can I visit > such range memory(4G-64G) ? You can't. Those memory ranges are strictly off-limits to non-US citizens. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 0:23:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id B93C437B401; Thu, 2 Aug 2001 00:23:23 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f727dbY02620; Thu, 2 Aug 2001 11:39:37 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108020739.f727dbY02620@bugz.infotecs.ru> Subject: ipfw "established" option To: freebsd-net@freebsd.org Date: Thu, 2 Aug 2001 11:39:37 +0400 (MSD) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I've found some strange issue regarding ipfw. I have freebsd 4.2-RELEASE. Guess I have rules: 1 allow tcp from any to 195.210.139.22 established 2 deny tcp from any to 195.210.139.22 2 allow all from any to any The intention is to allow the machine itself connect outside and accept responces once connection is established, but deny attepmts to connect to this machine from outside. I was thinking that first packet which tries to establish TCP connection should never match rule 1. However, I've found that it depends on which operating system tries to connect in ! When I try this from machine with freebsd 4.3-RELEASE, it gets dropped as expected. tcpdump on my machine says: 11:15:01.841594 195.222.16.243.1117 > 195.210.139.22.21: S 3910802910:3910802910(0) win 16384 (DF) [tos 0x10] 11:15:04.911908 195.222.16.243.1117 > 195.210.139.22.21: S 3910802910:3910802910(0) win 16384 (DF) [tos 0x10] 11:15:07.804934 195.222.16.243.1117 > 195.210.139.22.21: S 3910802910:3910802910(0) win 16384 (DF) [tos 0x10] Okay, that's fine. But then I try the same from Linux machine (2.4.5). I am able to successfully telnet in ! tcpdump says: 11:15:51.479203 195.230.76.28.39925 > 195.210.139.22.21: S [ECN-Echo,CWR] 4162184178:4162184178(0) win 5840 (DF) [tos 0x10] 11:15:51.479466 195.210.139.22.21 > 195.230.76.28.39925: S 2404031587:2404031587(0) ack 4162184179 win 17520 (DF) 11:15:51.565124 195.230.76.28.39925 > 195.210.139.22.21: . ack 1 win 5840 (DF) [tos 0x10] 11:15:51.590818 195.210.139.22.21 > 195.230.76.28.39925: P 1:58(57) ack 1 win 17520 (DF) [tos 0x10] 11:15:51.648107 195.230.76.28.39925 > 195.210.139.22.21: . ack 58 win 5840 (DF) [tos 0x10] Firewall logs also say that the initial packet matched the rule 1 and was passed. Why is it like that ? Am I missing something ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 0:31: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 0C11537B401; Thu, 2 Aug 2001 00:30:57 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id CF3D181D06; Thu, 2 Aug 2001 02:30:46 -0500 (CDT) Date: Thu, 2 Aug 2001 02:30:46 -0500 From: Bill Fumerola To: "Eugene L. Vorokov" Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ipfw "established" option Message-ID: <20010802023046.X2759@elvis.mu.org> References: <200108020739.f727dbY02620@bugz.infotecs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108020739.f727dbY02620@bugz.infotecs.ru>; from vel@bugz.infotecs.ru on Thu, Aug 02, 2001 at 11:39:37AM +0400 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 02, 2001 at 11:39:37AM +0400, Eugene L. Vorokov wrote: > Hello, > > I've found some strange issue regarding ipfw. I have freebsd 4.2-RELEASE. this was fixed in more recent versions of freebsd. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@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 Aug 2 0:37: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id D5FF137B401 for ; Thu, 2 Aug 2001 00:37:03 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f727b1I88855 for ; Thu, 2 Aug 2001 09:37:01 +0200 (SAST) (envelope-from lists@security.za.net) Date: Thu, 2 Aug 2001 09:37:01 +0200 (SAST) From: lists To: freebsd-hackers@freebsd.org Subject: wi0 problems? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, hoping someone can help me out here. With the changes to FreeBSD 5-CURRENT to support pci->pcmcia bridges, does anyone know if there is still a problem with the wi0 (wavelan) pcmcia cards on one of those bridges? The machine picks up the card fine, assigns it an IRQ the whole trip, wicontrol can also see the interface fine, even picks up my radio signal on it, but the moment I try and push packets through it, I get wi0 watchdog timeouts, anyone got a fix for this? Many thanks Andrew Alston To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 0:45:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 76B5B37B401 for ; Thu, 2 Aug 2001 00:45:22 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f727jKF97472; Thu, 2 Aug 2001 01:45:21 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f727jJH12112; Thu, 2 Aug 2001 01:45:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108020745.f727jJH12112@harmony.village.org> To: "Joseph Gleason" Subject: Re: Finding filesizes in C++ for files greater than 4gb Cc: freebsd-hackers@FreeBSD.org In-reply-to: Your message of "Wed, 01 Aug 2001 21:34:43 EDT." <00b201c11af3$4fef1c10$0a2d2d0a@battleship> References: <00b201c11af3$4fef1c10$0a2d2d0a@battleship> Date: Thu, 02 Aug 2001 01:45:19 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <00b201c11af3$4fef1c10$0a2d2d0a@battleship> "Joseph Gleason" writes: : In FreeBSD, how can I determine the size of a file in C++ when the file is : greater than 4gb? stat(2). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 0:50: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8521437B401 for ; Thu, 2 Aug 2001 00:49:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f727nuF97486; Thu, 2 Aug 2001 01:49:57 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f727nuH12143; Thu, 2 Aug 2001 01:49:56 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108020749.f727nuH12143@harmony.village.org> To: lists Subject: Re: wi0 problems? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Aug 2001 09:37:01 +0200." References: Date: Thu, 02 Aug 2001 01:49:56 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message lists writes: : With the changes to FreeBSD 5-CURRENT to support pci->pcmcia bridges, does : anyone know if there is still a problem with the wi0 (wavelan) pcmcia : cards on one of those bridges? I know of none, except that for the lucent single slot cards that were improperly manufacturered you need to add hw.pcic.ignore_function_1=1. : The machine picks up the card fine, assigns it an IRQ the whole trip, : wicontrol can also see the interface fine, even picks up my radio signal : on it, but the moment I try and push packets through it, I get wi0 : watchdog timeouts, anyone got a fix for this? Without a dmesg, it is impossible to know what the deal here is. I suspect it may be an interrupt routing issue with pci bridges.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 1:51:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 8C8EE37B403 for ; Thu, 2 Aug 2001 01:51:39 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 3820F38C99 for ; Thu, 2 Aug 2001 05:51:37 -0300 (EST) Received: (qmail 10580 invoked by uid 0); 2 Aug 2001 08:50:41 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 08:50:41 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f728pZD12614; Thu, 2 Aug 2001 05:51:35 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 05:51:35 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B68F190.AB04ACB3@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 1 Aug 2001, Terry Lambert wrote: > > craig wrote: > > > > > > I know PIII can support 64G physical memory. In FreeBSD how can I visit such > > range memory(4G-64G) ? > > The short answer is "you can't". > > The longer answer is that you end up having to window it using > segmentation; Only if you want to use it all within one process. You can have multiple 2 GB (that's the maximum process size in FreeBSD, right?) programs at the same time, happily using all physical memory. Only the FreeBSD memory management subsystem doesn't support it (yet?). > This basically means that the memory is useless as a DMA target > or source for disk controllers or gigabit ethernet cards, and is > pretty useless for swap, ... > So for limited uses in data intensive applications, it might be > usable, And for those data intensive applications, it is very useful indeed... > But to directly answer your question: by rewriting much of the > low core virtual memory and page mapping handling code to know > about segmentation. Not just that. There is a more insidious problem with the FreeBSD VM code and support of huge machines. The part of handling the PAE extended page table format and mapping high memory pages in and out of KVA (kernel virtual address) memory to copy stuff is easy. Problem is that you'll have to fit all of FreeBSD's VM data structures in the 2GB of KVA. This just isn't going to fit with the size the data structures have today ... So in order to support huge memory machines "right", you'd have to put a number of FreeBSD's VM data structures on a rather strict diet. regards, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 1:53:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id D057737B401 for ; Thu, 2 Aug 2001 01:53:24 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 4446B38C99 for ; Thu, 2 Aug 2001 05:53:23 -0300 (EST) Received: (qmail 10668 invoked by uid 0); 2 Aug 2001 08:52:27 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 08:52:27 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f728rM412687; Thu, 2 Aug 2001 05:53:22 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 05:53:22 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Mike Smith Cc: craig , , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <200108020123.f721NNo03244@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 1 Aug 2001, Mike Smith wrote: > > I know PIII can support 64G physical memory. In FreeBSD how can I visit > > such range memory(4G-64G) ? > > You can't. Those memory ranges are strictly off-limits to > non-US citizens. And under the DMCA, US citizens aren't allowed to build or distribute PAE36 circumvention devices. Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 2:57:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (unknown [217.75.135.246]) by hub.freebsd.org (Postfix) with SMTP id 76E9B37B401 for ; Thu, 2 Aug 2001 02:57:06 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 11685 invoked by uid 1000); 2 Aug 2001 09:55:01 -0000 Date: Thu, 2 Aug 2001 12:55:01 +0300 From: Peter Pentchev To: Dima Dorfman Cc: Kris Kennaway , Hans Zaunere , freebsd-hackers@FreeBSD.ORG Subject: Re: Accessing /dev/klog and similar Message-ID: <20010802125501.C11273@ringworld.oblivion.bg> Mail-Followup-To: Dima Dorfman , Kris Kennaway , Hans Zaunere , freebsd-hackers@FreeBSD.ORG References: <20010801201146.C4274@ringworld.oblivion.bg> <20010801185857.7D5BE3E31@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010801185857.7D5BE3E31@bazooka.unixfreak.org>; from dima@unixfreak.org on Wed, Aug 01, 2001 at 11:58:52AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 11:58:52AM -0700, Dima Dorfman wrote: > Peter Pentchev writes: > > Or rather, do not try this while syslogd is running. > > > > src/sys/kern/subr_log.c defines the operation of the /dev/klog > > device, and there is an upper limit on the number of processes > > that can simultaneously open the log device - the limit is one. > > That is, while syslogd is running, no other process can open > > the klog device for reading. > > > > This seems to have been the case ever since rev. 1.1 of > > src/sys/kern/subr_log.c; that is, this has been the case > > in 4.4BSD and earlier. Anybody have any recollection > > on why the kernel won't let more than one process intercept > > log messages (aside from the obvious fact that stacked syslogd's > > could easily DoS a machine)? > > Take a look at how it spits out those messages and you'll see why. In > short, if you have two processes reading them, neither will get the > full set because a read advances the read pointer (msgbufp->bufp, > IIRC). This can't easily be fixed. Oh, ok. Makes sense. To answer the original poster once again: currently, there is no way to have more than one process reading from the klog device. Enabling this kind of functionality would require major (not really needed) changes to the kernel logging routines. G'luck, Peter -- If you think this sentence is confusing, then change one pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 3:17:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id 93CC237B401 for ; Thu, 2 Aug 2001 03:17:37 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f72AHZs09538; Thu, 2 Aug 2001 11:17:35 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f72AHY860417; Thu, 2 Aug 2001 11:17:34 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200108021017.f72AHY860417@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: "Dennis Berger" Cc: freebsd-hackers@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: somebody implement ppp nat punch-fw ? In-Reply-To: Message from "Dennis Berger" of "Thu, 02 Aug 2001 04:37:34 +0200." <001c01c11afc$15bb1ef0$650110ac@nachpolierer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Aug 2001 11:17:34 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > A function available from libalias, the PKT_ALIAS_PUNCH_FW one is = > currently not implemented in ppp. Maybe somebody could implement it in = > ppp. It's definitly not much work, so I request if somebody could do it. > greets Dennis Done. -- Brian http://www.freebsd-services.com/ 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 Thu Aug 2 3:17:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 660BF37B401 for ; Thu, 2 Aug 2001 03:17:51 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: (from jhs@localhost) by jhs.muc.de (8.11.0/8.11.0) id f71BZWP01453; Wed, 1 Aug 2001 11:35:32 GMT (envelope-from jhs) Date: Wed, 1 Aug 2001 11:35:32 GMT Message-Id: <200108011135.f71BZWP01453@jhs.muc.de> To: hackers@freebsd.org Subject: vnconfig + mount removes permission for a second From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here's a bug in Mount ( or Kernel or NFS or Vnconfig support ? ) but I'm not clear enough to file a send-pr. Comments please... I'm using NFS + AMD but I think that just detects the problem, rather than being the cause of the problem. On Host=rain: cp /host/flip/usr2/ew/cdrom.iso cdrom.cd while the CDROM image is copying across my home 10Mbps ether ((ready for later burning) & while nothing else is causing ethernet disruption) On Host=flip vnconfig vn0 /usr2/ew/cdrom.iso mount -t cd9660 -r /dev/vn0c /mnt As soon as I push return on the host=Flip mount command, on Host=rain I see the error message: cp: /host/flip/usr2/ew/cdrom.iso: Permission denied Yet starting the cp again just after succeeds ... So something is momentarily making the image unreadable. Should FreeBSD [mount/kernel ?] be changed to avoid denying access ? I tried again using ftp get on Rain, & ftpd on Flip. That works, & md5 says copy is OK, no big suprise, ftp of course copes better with transient interruption / non availability. Julian J.Stacey Munich Unix (FreeBSD, Linux etc) Consultant http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 3:27:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 76A2B37B403 for ; Thu, 2 Aug 2001 03:27:06 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.131.20.Dial1.SanJose1.Level3.net [209.245.131.20]) by robin.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id DAA25776; Thu, 2 Aug 2001 03:26:06 -0700 (PDT) Message-ID: <3B692AE3.4B119794@mindspring.com> Date: Thu, 02 Aug 2001 03:26:43 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: [ ... > 4G on 32 bit macines ... ] > > The short answer is "you can't". > > > > The longer answer is that you end up having to window it using > > segmentation; > > Only if you want to use it all within one process. No. It still bites you if you want to do IPC, etc., since you can not guarantee the structures used for this are all within the non-segmented region of memory. > You can have multiple 2 GB (that's the maximum > process size in FreeBSD, right?) programs at the > same time, happily using all physical memory. The default maximum size for FreeBSD is 3G. You can tune this up or down, with the limit being that the larger the user space, the smaller the KVA space, and vice versa. > Only the FreeBSD memory management subsystem doesn't > support it (yet?). It's not a question of "supporting it", it's a question of whether or not it's a useful idea at all. > > This basically means that the memory is useless as a DMA target > > or source for disk controllers or gigabit ethernet cards, and is > > pretty useless for swap, ... > > > So for limited uses in data intensive applications, it might be > > usable, > > And for those data intensive applications, it is very > useful indeed... I have yet to see one person using it for anything. So far, it is nothing more than marketing fodder: I haven't seen one motherboard capable of more than 4G worth of SIMMs. > > But to directly answer your question: by rewriting much of the > > low core virtual memory and page mapping handling code to know > > about segmentation. > > Not just that. There is a more insidious problem with > the FreeBSD VM code and support of huge machines. Not really. > The part of handling the PAE extended page table format > and mapping high memory pages in and out of KVA (kernel > virtual address) memory to copy stuff is easy. Yes. > Problem is that you'll have to fit all of FreeBSD's VM > data structures in the 2GB of KVA. This just isn't going > to fit with the size the data structures have today ... I currently run with 3G+ of KVA; it would be simple to invert this, but this leaves me a 1G user space window, with 3G available for kernel structures, etc.. It takes about 1G for all of the kernel support stuff for 4G, with an allowance for 1/8th million open network connections. So it's not unreasonable to think of putting 8G or 16G in a box, and being able to map it all. > So in order to support huge memory machines "right", > you'd have to put a number of FreeBSD's VM data structures > on a rather strict diet. Not really. There's always 4M pages. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 3:35:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 3F11F37B406 for ; Thu, 2 Aug 2001 03:35:08 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 99EEF38D08 for ; Thu, 2 Aug 2001 07:35:06 -0300 (EST) Received: (qmail 16528 invoked by uid 0); 2 Aug 2001 10:34:11 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 10:34:11 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72AZ5515645; Thu, 2 Aug 2001 07:35:06 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 07:35:05 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B692AE3.4B119794@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Terry Lambert wrote: > Rik van Riel wrote: > [ ... > 4G on 32 bit macines ... ] > > > The short answer is "you can't". > > > > > > The longer answer is that you end up having to window it using > > > segmentation; > > > > Only if you want to use it all within one process. > > No. It still bites you if you want to do IPC, etc., since you > can not guarantee the structures used for this are all within > the non-segmented region of memory. Wrong. Your process can have pages from all over the 64 GB mapped into its page tables. Each process has 3 GB of virtual memory mapped to any of the pages of the 64 GB of physical space. > > Only the FreeBSD memory management subsystem doesn't > > support it (yet?). > > It's not a question of "supporting it", it's a question of > whether or not it's a useful idea at all. > I have yet to see one person using it for anything. So far, > it is nothing more than marketing fodder: I haven't seen one > motherboard capable of more than 4G worth of SIMMs. I've seen a bunch of the machines. They're rather popular with the database folks. > > Problem is that you'll have to fit all of FreeBSD's VM > > data structures in the 2GB of KVA. This just isn't going > > to fit with the size the data structures have today ... > So it's not unreasonable to think of putting 8G or 16G in > a box, and being able to map it all. You can never map it all, since your virtual address space is limited to 4GB... > > So in order to support huge memory machines "right", > > you'd have to put a number of FreeBSD's VM data structures > > on a rather strict diet. > > Not really. There's always 4M pages. Hmm, indeed. I guess I should sleep more since I've been planning this solution for Linux, too ;) Basically the database folks are really keen on keeping their 3GB user addressable memory, so the kernel will remain limited to 1GB of KVA. On the really large machines, this can lead to the situation where even the page tables hardly fit into KVA. 4MB pages seem like the only solution ... (well, there's also the mess of shared page tables, but nobody is keen on the locking issues those imply) regards, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 3:48:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1270537B401 for ; Thu, 2 Aug 2001 03:48:38 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Aug 2001 11:48:35 +0100 (BST) Date: Thu, 2 Aug 2001 11:48:35 +0100 From: David Malone To: Julian Stacey Cc: hackers@freebsd.org Subject: Re: vnconfig + mount removes permission for a second Message-ID: <20010802114835.A92803@walton.maths.tcd.ie> References: <200108011135.f71BZWP01453@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108011135.f71BZWP01453@jhs.muc.de>; from jhs@jhs.muc.de on Wed, Aug 01, 2001 at 11:35:32AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 01, 2001 at 11:35:32AM +0000, Julian Stacey wrote: > So something is momentarily making the image unreadable. > Should FreeBSD [mount/kernel ?] be changed to avoid denying access ? When you do a mount it automatically HUP's mountd which then re-exports NFS filesystems. I suspect what is happening is that the the filesystem mountlist is being cleared for a moment and that is upsetting the cp. You could try moving /var/run/mountd.pid out of the way and running the mount command. That should stop mount HUPing mountd, which would let you test this theory. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 4: 5:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id CB05637B401 for ; Thu, 2 Aug 2001 04:05:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.131.20.Dial1.SanJose1.Level3.net [209.245.131.20]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id EAA23856; Thu, 2 Aug 2001 04:04:46 -0700 (PDT) Message-ID: <3B6933F0.FC88449A@mindspring.com> Date: Thu, 02 Aug 2001 04:05:20 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: > > > Only if you want to use it all within one process. > > > > No. It still bites you if you want to do IPC, etc., since you > > can not guarantee the structures used for this are all within > > the non-segmented region of memory. > > Wrong. Your process can have pages from all over the > 64 GB mapped into its page tables. Try doing this with code pages in one segment, the stack in another, and the data being referenced in a third. It will not work. > Each process has 3 GB of virtual memory mapped to any > of the pages of the 64 GB of physical space. Like I said before, this is not useful. The only marginal use for such a thing is for implementing an L3 cache in software, or for implementing multiple virtual machines on one box. > > > Only the FreeBSD memory management subsystem doesn't > > > support it (yet?). > > > > It's not a question of "supporting it", it's a question of > > whether or not it's a useful idea at all. > > > I have yet to see one person using it for anything. So far, > > it is nothing more than marketing fodder: I haven't seen one > > motherboard capable of more than 4G worth of SIMMs. > > I've seen a bunch of the machines. They're rather > popular with the database folks. Name an OS that supports this; more than likely, you will have to appeal to a purpose built embedded system. > > > Problem is that you'll have to fit all of FreeBSD's VM > > > data structures in the 2GB of KVA. This just isn't going > > > to fit with the size the data structures have today ... > > > > So it's not unreasonable to think of putting 8G or 16G in > > a box, and being able to map it all. > > You can never map it all, since your virtual address space > is limited to 4GB... Overlays. A technology from the dawn of time, I know, but so are segment registers. > Basically the database folks are really keen on keeping > their 3GB user addressable memory, so the kernel will > remain limited to 1GB of KVA. They shouldn't care, since they are getting more memory. > On the really large machines, this can lead to the > situation where even the page tables hardly fit into > KVA. 4MB pages seem like the only solution ... This is why we use 64 bit processors for really large machines, and we say that 36 bit address spaces are really pretty useless, and will be obsolete by the time the code is complete, because of ia64 being a cheaper and faster soloution. 8-p. 36 bits only gives you 2^4 * 4G, or 64G, anyway, and it is hardly worth the segment thrashing and instruction and data cache shootdowns to be able to handle it. You are better off throwing 16 machines at the problem: your major cost item is going to be memory, anyway, and getting 64G in one box is going to cost you significantly more than just putting together multiple boxes. If the locality is such that 2G per process is OK, you might as well be on seperate boxes with non-segmenet swapped memory. > (well, there's also the mess of shared page tables, > but nobody is keen on the locking issues those imply) It's much, much worse than that. Like I said before, you could do it pretty trivially, but the expense of doing it will be so high, relatively, that you might as well buy an Alpha or PA-RISC box and call it a day, if you need it now, or just wait for IA64, rather than throwing developement effort into something that will end up in a scrap heap before it gets reasonable performance, or perhaps before it's even deployed. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 4: 6: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id EA5CD37B401 for ; Thu, 2 Aug 2001 04:06:04 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Aug 2001 12:06:02 +0100 (BST) To: David Malone Cc: Julian Stacey , hackers@freebsd.org Subject: Re: vnconfig + mount removes permission for a second In-Reply-To: Your message of "Thu, 02 Aug 2001 11:48:35 BST." <20010802114835.A92803@walton.maths.tcd.ie> Date: Thu, 02 Aug 2001 12:06:02 +0100 From: Ian Dowse Message-ID: <200108021206.aa93171@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20010802114835.A92803@walton.maths.tcd.ie>, David Malone writes: > >When you do a mount it automatically HUP's mountd which then >re-exports NFS filesystems. I suspect what is happening is that >the the filesystem mountlist is being cleared for a moment and that >is upsetting the cp. Yes, the mountd-kernel interface for updating export lists is a bit stupid; you have to clear all exports and then add each allowed host/net one by one. Any NFS requests that come in after the exports have been deleted but before the entries have been re-added will get rejected. See PRs misc/3980 and kern/9619 for more details. I think NetBSD tried at one point to make mountd incrementally change the export list, but it turned out to be quite hard to get the logic right to keep the mountd and kernel lists in sync. I think they reverted that change eventually. This is certainly a bug that needs to be fixed; mountd should be able to build up a list of all exports for a filesystem and pass them into the kernel in one "replace export list" operation. Maybe nice'ing mountd to run at a higher priority, and/or specifying only IP addresses in /etc/exports would help things a bit now. Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 4:14:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 9529037B403 for ; Thu, 2 Aug 2001 04:14:26 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 3A64438D0C for ; Thu, 2 Aug 2001 08:14:24 -0300 (EST) Received: (qmail 374 invoked by uid 0); 2 Aug 2001 11:13:28 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 11:13:28 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72BENM17155; Thu, 2 Aug 2001 08:14:23 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 08:14:23 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B6933F0.FC88449A@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Terry Lambert wrote: > Rik van Riel wrote: > > > > Only if you want to use it all within one process. > > > > > > No. It still bites you if you want to do IPC, etc., since you > > > can not guarantee the structures used for this are all within > > > the non-segmented region of memory. > > > > Wrong. Your process can have pages from all over the > > 64 GB mapped into its page tables. > > Try doing this with code pages in one segment, the stack in > another, and the data being referenced in a third. It will > not work. Of course it cannot work. The segments you refer to will map to the linear 4GB space represented by the page tables. Those page tables can map, in their 4GB virtual space, pages from all over the 64GB physical space. > > I've seen a bunch of the machines. They're rather > > popular with the database folks. > > Name an OS that supports this; more than likely, you will > have to appeal to a purpose built embedded system. Linux SCO Unix NT *cough* > > > So it's not unreasonable to think of putting 8G or 16G in > > > a box, and being able to map it all. > > > > You can never map it all, since your virtual address space > > is limited to 4GB... > > Overlays. A technology from the dawn of time, I know, but > so are segment registers. s/You can never map it all/You can never map it all at once/ Happy now? ;) > > Basically the database folks are really keen on keeping > > their 3GB user addressable memory, so the kernel will > > remain limited to 1GB of KVA. > > They shouldn't care, since they are getting more memory. You're telling the people working with 50GB datasets that they shouldn't care about how many of their 512MB segments they can map in at once? ;) > or just wait for IA64, rather than throwing developement > effort into something that will end up in a scrap heap before > it gets reasonable performance, or perhaps before it's even > deployed. Ssssh, don't tell that to the folks who are using such machines today ;) cheers, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 5:53:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 309C537B401 for ; Thu, 2 Aug 2001 05:53:24 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f72CrKS01184 for ; Thu, 2 Aug 2001 14:53:20 +0200 (SAST) (envelope-from lists@security.za.net) Date: Thu, 2 Aug 2001 14:53:20 +0200 (SAST) From: lists To: freebsd-hackers@freebsd.org Subject: NewCard / pccbb Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, Im hoping someone can help me in clarifying some issues, Im attempting to find the problem with my orinoco wavelan card. Currently I have the card plugged into a pci -> pcmcia bridge. As mentioned in a previous email, the card detects fine, (both under oldcard and newcard), I can use wicontrol on it, and all the rest of it, but the moment I try and ifconfig it or alternatively the moment I try and put packets through it, I get watchdog timeouts. Now my question is this, should I have the same irq on both the bridge device and the card, or could this be causing my problem. In a verbose boot mode I see the following: pccbb0: at device 9.0 on pci0 pccbb0: PCI Memory allocated: 44000000 pci_cfgintr_virgin: using routable interrupt 3 pci_cfgintr: 0:9 INTA routed to irq 3 cardbus0: on pccbb0 pccard0: <16-bit PCCard bus> on pccbb0 Further down I see this wi0: at port 0x100-0x13f irq 3 function 0 config 1 on pccard0 Could that irq sharing be breaking something? Thanks Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 6:38:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 670F237B401 for ; Thu, 2 Aug 2001 06:38:39 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA20566; Thu, 2 Aug 2001 09:38:00 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id JAA21576; Thu, 2 Aug 2001 09:38:00 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id JAA21572; Thu, 2 Aug 2001 09:38:00 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 2 Aug 2001 09:38:00 -0400 (EDT) From: Kenneth Wayne Culver To: Rik van Riel Cc: Terry Lambert , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Also, the PIII CAN'T natively support more than 4GB of ram. If a particular PIII motherboard supports this, then it's using some kind of wierd chipset that allows this to happen. 4GB is the limit with a 32 bit chip I believe; and the PIII is a 32-bit chip. Ken On Thu, 2 Aug 2001, Rik van Riel wrote: > On Wed, 1 Aug 2001, Terry Lambert wrote: > > > craig wrote: > > > > > > > > > I know PIII can support 64G physical memory. In FreeBSD how can I visit such > > > range memory(4G-64G) ? > > > > The short answer is "you can't". > > > > The longer answer is that you end up having to window it using > > segmentation; > > Only if you want to use it all within one process. > > You can have multiple 2 GB (that's the maximum > process size in FreeBSD, right?) programs at the > same time, happily using all physical memory. > > Only the FreeBSD memory management subsystem doesn't > support it (yet?). > > > This basically means that the memory is useless as a DMA target > > or source for disk controllers or gigabit ethernet cards, and is > > pretty useless for swap, ... > > > So for limited uses in data intensive applications, it might be > > usable, > > And for those data intensive applications, it is very > useful indeed... > > > But to directly answer your question: by rewriting much of the > > low core virtual memory and page mapping handling code to know > > about segmentation. > > Not just that. There is a more insidious problem with > the FreeBSD VM code and support of huge machines. > > The part of handling the PAE extended page table format > and mapping high memory pages in and out of KVA (kernel > virtual address) memory to copy stuff is easy. > > Problem is that you'll have to fit all of FreeBSD's VM > data structures in the 2GB of KVA. This just isn't going > to fit with the size the data structures have today ... > > So in order to support huge memory machines "right", > you'd have to put a number of FreeBSD's VM data structures > on a rather strict diet. > > regards, > > Rik > -- > Executive summary of a recent Microsoft press release: > "we are concerned about the GNU General Public License (GPL)" > > > http://www.surriel.com/ > http://www.conectiva.com/ http://distro.conectiva.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 Aug 2 6:44:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 6908737B403 for ; Thu, 2 Aug 2001 06:44:33 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 09FAD38D22 for ; Thu, 2 Aug 2001 10:44:07 -0300 (EST) Received: (qmail 19300 invoked by uid 0); 2 Aug 2001 13:43:11 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 13:43:11 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72Di4n22595; Thu, 2 Aug 2001 10:44:05 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 10:44:04 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Kenneth Wayne Culver Cc: Terry Lambert , craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Kenneth Wayne Culver wrote: > Also, the PIII CAN'T natively support more than 4GB of ram. If a > particular PIII motherboard supports this, then it's using some > kind of wierd chipset that allows this to happen. 4GB is the > limit with a 32 bit chip I believe; and the PIII is a 32-bit > chip. The Xeon series have 32 bits of virtual address space and 36 bits of physical address space. Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 7: 5:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id C027937B401 for ; Thu, 2 Aug 2001 07:05:27 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA23998; Thu, 2 Aug 2001 10:05:08 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA26488; Thu, 2 Aug 2001 10:05:07 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA26484; Thu, 2 Aug 2001 10:05:07 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 2 Aug 2001 10:05:07 -0400 (EDT) From: Kenneth Wayne Culver To: Rik van Riel Cc: Terry Lambert , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Oh ok, I knew that regular PIII's only had 32 bits... but it's still obviously a pain in the butt to use above 4GB. Ken On Thu, 2 Aug 2001, Rik van Riel wrote: > On Thu, 2 Aug 2001, Kenneth Wayne Culver wrote: > > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > particular PIII motherboard supports this, then it's using some > > kind of wierd chipset that allows this to happen. 4GB is the > > limit with a 32 bit chip I believe; and the PIII is a 32-bit > > chip. > > The Xeon series have 32 bits of virtual address space > and 36 bits of physical address space. > > Rik > -- > Executive summary of a recent Microsoft press release: > "we are concerned about the GNU General Public License (GPL)" > > > http://www.surriel.com/ > http://www.conectiva.com/ http://distro.conectiva.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 7:14:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id AD41737B401 for ; Thu, 2 Aug 2001 07:14:21 -0700 (PDT) (envelope-from tinguely@web.cs.ndsu.nodak.edu) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f72EEBS78044; Thu, 2 Aug 2001 09:14:11 -0500 (CDT) (envelope-from tinguely) Date: Thu, 2 Aug 2001 09:14:11 -0500 (CDT) From: mark tinguely Message-Id: <200108021414.f72EEBS78044@web.cs.ndsu.nodak.edu> To: culverk@wam.umd.edu, riel@conectiva.com.br Subject: Re: How to visit physical memory above 4G? Cc: craiglei@pasia.com.cn, freebsd-hackers@FreeBSD.ORG, tlambert2@mindspring.com In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2 Aug 2001, Kenneth Wayne Culver said: > Also, the PIII CAN'T natively support more than 4GB of ram. If a > particular PIII motherboard supports this, then it's using some kind of > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > chip I believe; and the PIII is a 32-bit chip. Since the Pentium Pro processor, the Intel chipsets support a physical address extension (PAE) which has 4 extra addressing bits, and a third level of page table indirection called the page-directory-pointer-table base address field. The addressing use 64 bits for a memory pointer and the additional page indirection add to the overhead. The stickler is the MMU is still 32 bits. This means the PAE must segment the 64GB space into 4GB segments or 4 1GB segments. The OS must manage which pages are viewable to the process at this time. There is a third mode of addressing using 2MB pages (simular to the 4MB page addressing mode for the 32 bit addressing scheme) that will only give a process access to 4GB of memory (not segmentable to a larger space, but can address physical memory located above the 4GB address). --mark tinguely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 7:28:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id D461837B406 for ; Thu, 2 Aug 2001 07:28:18 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id DFBCF38D11 for ; Thu, 2 Aug 2001 11:28:14 -0300 (EST) Received: (qmail 31003 invoked by uid 0); 2 Aug 2001 14:27:19 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 14:27:19 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72ESDl24314; Thu, 2 Aug 2001 11:28:13 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 11:28:13 -0300 (BRST) From: Rik van Riel X-X-Sender: To: mark tinguely Cc: , , , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <200108021414.f72EEBS78044@web.cs.ndsu.nodak.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, mark tinguely wrote: > The addressing use 64 bits for a memory pointer and the additional > page indirection add to the overhead. The stickler is the MMU is > still 32 bits. This means the PAE must segment the 64GB space into > 4GB segments or 4 1GB segments. The OS must manage which pages are > viewable to the process at this time. There's a better option. The application does this stuff itself, by mapping and unmapping SHM segments. This needs to be done anyway, since the application wouldn't be happy if the OS randomly remapped its address space to different pages ;)) > There is a third mode of addressing using 2MB pages (simular to the > 4MB page addressing mode for the 32 bit addressing scheme) that will > only give a process access to 4GB of memory (not segmentable to > a larger space, but can address physical memory located above the 4GB > address). You can do that with 4kB pages too. Both the middle page directory and page table have 512 64-bit entries, so you can simply map 4kB pages from above the 4GB physical boundary... regards, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 8: 7:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (Postfix) with SMTP id B7CB137B420 for ; Thu, 2 Aug 2001 08:07:42 -0700 (PDT) (envelope-from pmckenna@otto.oss.uswest.net) Received: (qmail 14701 invoked by uid 1001); 2 Aug 2001 15:02:33 -0000 Date: Thu, 2 Aug 2001 10:02:33 -0500 From: Pete McKenna To: Paul Halliday Cc: Frederique Rijsdijk , freebsd-hackers@FreeBSD.ORG Subject: Re: connecting a FujiFinePix1400 (USB) ? Message-ID: <20010802100233.A8323@otto.oss.qwest.net> References: <20010801155934.B36262@support.euronet.nl> <3B6839F0.5080906@penix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B6839F0.5080906@penix.org>; from dp@penix.org on Wed, Aug 01, 2001 at 05:18:40PM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I can't speak to the camera, but I've found that coldsync works for my visor. It's in the palm ports. pmckenna:more coldsync/pkg-descr ColdSync is a robust, extensible, portable tool for synchronizing PalmOS devices (PalmPilot et al.) with a Unix workstation. It also supports USB connections to a Visor, under FreeBSD 4.0. It runs without a GUI, and therefore allows you to sync without running X. ColdSync is extensible through the use of conduits, which allow it to share information with other applications. For more information, see WWW: http://www.ooblick.com/software/coldsync/ - Andrew Arensburger arensb@ooblick.com Pete On Wed, Aug 01, 2001 at 05:18:40PM +0000, Paul Halliday wrote: > Frederique Rijsdijk wrote: > > > Is it possible to connect a digital camera with a USB interface > > (FujiFinePix1400 in this case) to a FreeBSD (3.4-S) host to download > > the images? > > > > Thanks, > > > > heh.. freebsd usb sucks. > I have a handspring and a fujifilm finepix40i that are just sitting here > collecting dust. > > > From 3.4 - 4.3 S I have tried every available means, packages, patches > to get either of them working with 0 luck. > > If you do happen to get it up and running, please let me know how you > achieved such a miraculous feat. > > > > > -- Frederique > > > > > -- > Paul H. > ___________________ > http://dp.penix.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Peter McKenna Qwest Internet Solutions pmckenna@qwest.net Main 612-664-4000 FAX 612-664-4770 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 8: 9: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id B21AC37B403 for ; Thu, 2 Aug 2001 08:09:02 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [204.138.45.2]) by sabre.velocet.net (Postfix) with ESMTP id CC366137FD2 for ; Thu, 2 Aug 2001 11:09:01 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.11.4/8.9.3) id f72F91a90635; Thu, 2 Aug 2001 11:09:01 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15209.27917.107643.631181@trooper.velocet.net> Date: Thu, 2 Aug 2001 11:09:01 -0400 To: freebsd-hackers@freebsd.org Subject: 6G memory disks? X-Mailer: VM 6.92 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I suppose a 6G "md" memory disk is impossible? I recently applied all the patches recomended here and even got a 6G memory disk "newfs'd" and "mount'd" ... but when I ran bonnie (with size 100M) on it, it failed. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 8:16:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Kasan.su (unknown [209.5.222.98]) by hub.freebsd.org (Postfix) with SMTP id 4C66437B409 for ; Thu, 2 Aug 2001 08:16:01 -0700 (PDT) (envelope-from zdanie@dr.com) Message-ID: <72382001842145720605@dr.com> X-EM-Version: 5, 0, 0, 21 X-EM-Registration: #01B0530810E603002D00 X-Priority: 3 Reply-To: zdanie@europe.com X-MSMail-Priority: Normal From: "=?windows-1251?Q?=CF=EE=F0=F2=EE=E2=E0=FF,_19?=" To: freebsd-hackers@freebsd.org Subject: =?windows-1251?Q?=CF=F0=EE=E4=E0=E5=F2=F1=FF_=E0=E4=EC=E8=ED=E8=F1=F2=F0=E0=F2=E8=E2=ED=EE=E5_=E7=E4=E0=ED=E8=E5_=E2_=CA=E0=E7=E0=ED=E8?= Date: Thu, 2 Aug 2001 18:57:20 +0400 MIME-Version: 1.0 Content-type: text/plain; charset="windows-1251" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ïðåäëàãàåì ïðèîáðåñòè â ñîáñòâåííîñòü àäìèíèñòðàòèâíîå çäàíèå â Êàçàíè (Òàòàðñòàí, Ðîññèÿ): - Îáùàÿ ïëîùàäü 910 êâ. ì; - 2 ýòàæà; - Áîëüøîå êîëè÷åñòâî ïîìåùåíèé îò 7 äî 200 êâ.ì; - Ñîáñòâåííàÿ òåððèòîðèÿ - çåìåëüíûé ó÷àñòîê 0,101 Ãà. Çäàíèå - áûâøàÿ ñòîëîâàÿ ðå÷íîãî ïîðòà. Èìååò âûãîäíîå ðàñïîëîæåíèå: - íàïðîòèâ çäàíèÿ - âòîðîé ïî âåëè÷èíå îïòîâûé ïðîäóêòîâûé ãîðîäñêîé ðûíîê; - óäîáíûå ïîäúåçäíûå ïóòè; - áëèçêî ê öåíòðó ãîðîäà - 5 ìèí. åçäû; - áëèçêî ê æ/ä âîêçàëó - 5 ìèí. åçäû; - ðÿäîì ðå÷íîé ïîðò; - ðÿäîì æ/ä ïóòè. Çäàíèå èäåàëüíî ïîäõîäèò äëÿ ðàçìåùåíèÿ îôèñà ïðåäñòàâèòåëüñòâà Âàøåé êîìïàíèè â Òàòàðñòàíå èëè Ïîâîëæüå. Âîçìîæíà êîìïîíîâêà "îôèñ/ñêëàä". Âñå êîììóíèêàöèè ïîäâåäåíû. Çäàíèå òðåáóåò ðåìîíòà (ïîëíàÿ âíóòðåííÿÿ îòäåëêà, âêëþ÷àÿ íîâûå îêîííûå è äâåðíûå áëîêè). Çäàíèå íàõîäèòñÿ â ÷àñòíîé ñîáñòâåííîñòè. Çåìëÿ - â áåññðî÷íîì ïîëüçîâàíèè. Öåíà çäàíèÿ - ÁÎËÅÅ ×ÅÌ ÄÎÑÒÓÏÍÀ. Åñëè âû çàèíòåðåñîâàíû â ïîëó÷åíèè îò íàñ áîëåå ïîäðîáíîé èíôîðìàöèè î äàííîì îáúåêòå, îòïðàâüòå ïóñòîå ïèñüìî ïî àäðåñó: zdanie@europe.com. Ïðè ýòîì â "Òåìå" ñîîáùåíèÿ ÎÁßÇÀÒÅËÜÍÎ óêàæèòå: "Ïðèøëèòå ïîäðîáíóþ èíôîðìàöèþ". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 8:19:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nipsi.home.net (dsl-213-023-032-088.arcor-ip.net [213.23.32.88]) by hub.freebsd.org (Postfix) with SMTP id A418B37B403 for ; Thu, 2 Aug 2001 08:19:25 -0700 (PDT) (envelope-from HypnotiZer@gmx.net) Received: (qmail 35807 invoked from network); 2 Aug 2001 15:18:11 -0000 Received: from nachpolierer.home.net (HELO nachpolierer) (172.16.1.101) by nipsi.home.net with SMTP; 2 Aug 2001 15:18:11 -0000 Message-ID: <000801c11b66$f57452e0$650110ac@nachpolierer> From: "Dennis Berger" To: Subject: keep-state rule for icmp, really stateful ??? Date: Thu, 2 Aug 2001 17:22:36 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C11B77.B8F581C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C11B77.B8F581C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi I have the following rule allowing traceroute and ping to my server. "200 allow icmp from any to any keep-state in recv tun0 icmptype 8" Now I would assume that this rule generate two dynamic rules back. The fire one is a rule that initiates ping to work properly it's just a = dynamic ICMP rule 00200 2623 220332 (T 30, # 43) ty 0 icmp, 134.100.58.115 0 <-> = 213.23.32.88 0 and the second that the traceroute UDP taffic from port 33434-33960 can = pass in. But what happans ... the rule 200 doesn't open a second dynamic rule to = allow udp traffic to specific ports back in, the traceroute UDP traffic = will be blocked. To keep the icmp packetfiltering stateful it would be = nice to implement this clean. Or maybe it is already implemented in = CURRENT tree. What's the current state ? greets Dennis=20 ------=_NextPart_000_0005_01C11B77.B8F581C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi
I have the following rule allowing = traceroute and=20 ping to my server.
"200 allow icmp from any to any = keep-state in recv=20 tun0 icmptype 8"
Now I would assume that this rule = generate two=20 dynamic rules back.
The fire one is a rule that initiates = ping to work=20 properly it's just a dynamic ICMP rule
00200 2623 220332 (T 30, # 43) ty 0 = icmp,=20 134.100.58.115 0 <-> 213.23.32.88 0
and the second that the traceroute UDP=20 taffic from port 33434-33960 can pass=20 in.
But what happans ... the rule 200 = doesn't=20 open a second dynamic rule to allow udp traffic to specific ports = back=20 in, the traceroute UDP traffic will = be blocked.=20 To keep the icmp packetfiltering stateful it would be nice to implement=20 this clean. Or maybe it is already = implemented in=20 CURRENT tree. What's the current state ?
greets Dennis 
 
------=_NextPart_000_0005_01C11B77.B8F581C0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 8:46:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id C1DD537B405 for ; Thu, 2 Aug 2001 08:46:29 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id RAA28383; Thu, 2 Aug 2001 17:54:55 +0200 Message-ID: <3B697645.500487A1@i-clue.de> Date: Thu, 02 Aug 2001 17:48:21 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.78 [en] (WinNT; U) X-Accept-Language: de,en MIME-Version: 1.0 To: David Gilbert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 6G memory disks? References: <15209.27917.107643.631181@trooper.velocet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Gilbert wrote: > > I suppose a 6G "md" memory disk is impossible? I recently applied all > the patches recomended here and even got a 6G memory disk "newfs'd" > and "mount'd" ... but when I ran bonnie (with size 100M) on it, it > failed. AFAIR FreeBSD will address ony 4G of RAM, which is typically split into 3G user and 1 G kernel area. HTH -Christoph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 9:33:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id EEED437B401 for ; Thu, 2 Aug 2001 09:33:42 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA25274; Thu, 2 Aug 2001 09:33:40 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B68F190.AB04ACB3@mindspring.com> Date: Thu, 02 Aug 2001 09:33:40 -0700 (PDT) From: John Baldwin To: Terry Lambert Subject: Re: How to visit physical memory above 4G? Cc: freebsd-hackers@FreeBSD.org, craig Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Aug-01 Terry Lambert wrote: >> craig wrote: >> >> >> I know PIII can support 64G physical memory. In FreeBSD how can I visit such >> range memory(4G-64G) ? > > The short answer is "you can't". > > The longer answer is that you end up having to window it using > segmentation; if you are familiar with the 4k window on video > memory in the TI 99/4A, or the bank select on the 6510 (e.g. > the ability to select between 32K of RAM, and 32K of ROM, but > not both at the same time, on the Commodore C-64 and the similar > arrangement on the C-128, etc.), then you;ll have an idea of how > the thing works... assuming you can find a motherboard that can > handle it. Err. hang on. This has zero to do with segmentation. Zip, nada. PAE is completely in the paging side of things. No matter what fun games you play with segmentation, you still end up with a 32-bit linear address that gets handed off to the paging translations. PAE just allows you to use more backing store across multiple processes, but you are still stuck with a 4gb virtual address space for processes. (Including KVM) > But to directly answer your question: by rewriting much of the > low core virtual memory and page mapping handling code to know > about segmentation. No, to rewrite said code to handle a different type of page table structure. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Aug 2 9:34:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 54EBA37B401 for ; Thu, 2 Aug 2001 09:34:12 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA25236; Thu, 2 Aug 2001 09:33:34 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 02 Aug 2001 09:33:34 -0700 (PDT) From: John Baldwin To: Kenneth Wayne Culver Subject: Re: How to visit physical memory above 4G? Cc: freebsd-hackers@FreeBSD.org, craig , Terry Lambert , Rik van Riel Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Aug-01 Kenneth Wayne Culver wrote: > Also, the PIII CAN'T natively support more than 4GB of ram. If a > particular PIII motherboard supports this, then it's using some kind of > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > chip I believe; and the PIII is a 32-bit chip. > > Ken Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before Pentium II) have supported PAE which allows for a 36-bit physical address. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Aug 2 10:19:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 3B5DB37B401 for ; Thu, 2 Aug 2001 10:19:42 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.4/8.11.4) with SMTP id f72HJNf73274; Thu, 2 Aug 2001 13:19:24 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 2 Aug 2001 13:19:23 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jag Johal Cc: "'hackers@freebsd.org'" , Michael VanLoon Subject: RE: Finding MAC address of interface - programming question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I actually prefer the API call getifaddrs(3), which does much the same thing, but hides the MIB management interface behind a fairly well-defined API, which also does the memory management. You can just pull out the link layer addresses along with interface description. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Tue, 31 Jul 2001, Jag Johal wrote: > Use sysctl(3), basically, its something like this. > mib[0] = CTL_NET; > mib[1] = AF_ROUTE; > mib[2] = 0; > mib[3] = AF_INET; > mib[4] = NET_RT_IFLIST; > mib[5] = 0; > > sysctl(mib, 6, buf, &len, NULL, 0); > buf will contain for each interface, an if_msghdr followed by a sockaddr_dl, > the sockaddr_dl will contain the interface name and mac addr. Following that > will be a ifa_msghdr for each ip address on the interface. You may want to > check out UNPv1. > > Jag > > -----Original Message----- > From: Chris Faulhaber [mailto:jedgar@fxp.org] > Sent: Tuesday, July 31, 2001 3:56 PM > To: Michael VanLoon > Cc: 'hackers@freebsd.org' > Subject: Re: Finding MAC address of interface - programming question > > > On Tue, Jul 31, 2001 at 03:56:40PM -0700, Michael VanLoon wrote: > > Please point me to a more appropriate forum if there is one. I'm kinda > out > > of my depth on this question. Pseudo code is fine. :-) > > > > What I'm looking for is how to enumerate the network interfaces and get > the > > Ethernet MAC address of one programmatically. Can anyone point me in the > > right direction? > > > > /usr/src/sbin/ifconfig > > -- > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > -------------------------------------------------------- > FreeBSD: The Power To Serve - http://www.FreeBSD.org > > 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 Aug 2 10:25: 9 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id CE09E37B401; Thu, 2 Aug 2001 10:24:59 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.4/8.11.4) with SMTP id f72HOjf73349; Thu, 2 Aug 2001 13:24:45 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 2 Aug 2001 13:24:44 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Eugene L. Vorokov" Cc: freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ipfw "established" option In-Reply-To: <200108020739.f727dbY02620@bugz.infotecs.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As Bill Fumerola has indicated, and I thought I'd follow up in with a bit more detail, the behavior you're seeing is the result of a bug in the FreeBSD IPFW code. FreeBSD did a direct comparison of the TCP header flag field with an internal field in the IPFW rule description structure. Unfortunately, at some point, someone decided to overload the IPFW rule description structure field to add a flag representing "ESTABLISHED". They used a flag value that was previously unused by the TCP protocol (which doesn't make it safer, just less noticeable). Later, when that flag was allocated for ECN (Endpoint Congestion Notification) in TCP, and Linux began using ECN by default, the packets began to match ESTABLISHED rules regardless of the other TCP header flags. This bug was corrected on the RELENG_4 branch, and security advisory for the bug was released. This was, needless to say, a pretty serious bug, and good example of why you should be very careful to compare only the bits you really mean to, and should seperate packet state from protocol state in management structures, as well as make use of extensive testing to make sure rules actually have the effect you describe. I understand a number of such tests are available for the ipfilter firewall module--it might make sense to modify them to test similar functionality in IPFW. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Thu, 2 Aug 2001, Eugene L. Vorokov wrote: > Hello, > > I've found some strange issue regarding ipfw. I have freebsd 4.2-RELEASE. > Guess I have rules: > > 1 allow tcp from any to 195.210.139.22 established > 2 deny tcp from any to 195.210.139.22 > 2 allow all from any to any > > The intention is to allow the machine itself connect outside and accept > responces once connection is established, but deny attepmts to connect > to this machine from outside. I was thinking that first packet which tries > to establish TCP connection should never match rule 1. > > However, I've found that it depends on which operating system tries to > connect in ! When I try this from machine with freebsd 4.3-RELEASE, it gets > dropped as expected. tcpdump on my machine says: > > 11:15:01.841594 195.222.16.243.1117 > 195.210.139.22.21: S 3910802910:3910802910(0) win 16384 (DF) [tos 0x10] > 11:15:04.911908 195.222.16.243.1117 > 195.210.139.22.21: S 3910802910:3910802910(0) win 16384 (DF) [tos 0x10] > 11:15:07.804934 195.222.16.243.1117 > 195.210.139.22.21: S 3910802910:3910802910(0) win 16384 (DF) [tos 0x10] > > Okay, that's fine. But then I try the same from Linux machine (2.4.5). > I am able to successfully telnet in ! tcpdump says: > > 11:15:51.479203 195.230.76.28.39925 > 195.210.139.22.21: S [ECN-Echo,CWR] 4162184178:4162184178(0) win 5840 (DF) [tos 0x10] > 11:15:51.479466 195.210.139.22.21 > 195.230.76.28.39925: S 2404031587:2404031587(0) ack 4162184179 win 17520 (DF) > 11:15:51.565124 195.230.76.28.39925 > 195.210.139.22.21: . ack 1 win 5840 (DF) [tos 0x10] > 11:15:51.590818 195.210.139.22.21 > 195.230.76.28.39925: P 1:58(57) ack 1 win 17520 (DF) [tos 0x10] > 11:15:51.648107 195.230.76.28.39925 > 195.210.139.22.21: . ack 58 win 5840 (DF) [tos 0x10] > > Firewall logs also say that the initial packet matched the rule 1 > and was passed. > > Why is it like that ? Am I missing something ? > > Regards, > Eugene > > > 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 Aug 2 10:27:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (unknown [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id EDEAB37B401 for ; Thu, 2 Aug 2001 10:27:30 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 30454 invoked by uid 1000); 2 Aug 2001 17:26:19 -0000 Date: Thu, 2 Aug 2001 20:26:19 +0300 From: Peter Pentchev To: Dennis Berger Cc: freebsd-hackers@freebsd.org Subject: Re: keep-state rule for icmp, really stateful ??? Message-ID: <20010802202618.A11105@ringworld.oblivion.bg> Mail-Followup-To: Dennis Berger , freebsd-hackers@freebsd.org References: <000801c11b66$f57452e0$650110ac@nachpolierer> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000801c11b66$f57452e0$650110ac@nachpolierer>; from HypnotiZer@gmx.net on Thu, Aug 02, 2001 at 05:22:36PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 02, 2001 at 05:22:36PM +0200, Dennis Berger wrote: > Hi > I have the following rule allowing traceroute and ping to my server. > "200 allow icmp from any to any keep-state in recv tun0 icmptype 8" > Now I would assume that this rule generate two dynamic rules back. > The fire one is a rule that initiates ping to work properly it's just a dynamic ICMP rule > 00200 2623 220332 (T 30, # 43) ty 0 icmp, 134.100.58.115 0 <-> 213.23.32.88 0 > and the second that the traceroute UDP taffic from port 33434-33960 can pass in. > But what happans ... the rule 200 doesn't open a second dynamic rule to allow udp traffic to specific ports back in, the traceroute UDP traffic will be blocked. To keep the icmp packetfiltering stateful it would be nice to implement this clean. Or maybe it is already implemented in CURRENT tree. What's the current state ? Errrr.. maybe it's just me, but I just can't see how a rule that says 'allow icmp' should allow UDP traffic to pass through.. Maybe you haven't shown us all the rules? (And I don't necessarily mean 'all the rules pertaining to icmp and traceroute'.. it might as well be that some other rule, which you do not consider relevant, is blocking your traceroute packets.) G'luck, Peter -- I am jealous of the first word in this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 10:28:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bdr-xcon.matchlogic.com (mail.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 0775737B403 for ; Thu, 2 Aug 2001 10:28:44 -0700 (PDT) (envelope-from crandall@matchlogic.com) Received: by mail.matchlogic.com with Internet Mail Service (5.5.2653.19) id ; Thu, 2 Aug 2001 11:28:34 -0600 Message-ID: <5FE9B713CCCDD311A03400508B8B30130828F234@bdr-xcln.corp.matchlogic.com> From: Charles Randall To: "'tlambert2@mindspring.com'" , Rik van Riel Cc: craig , freebsd-hackers@FreeBSD.ORG Subject: RE: How to visit physical memory above 4G? Date: Thu, 2 Aug 2001 11:26:31 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: Terry Lambert [mailto:tlambert2@mindspring.com] >I have yet to see one person using it for anything. So far, >it is nothing more than marketing fodder: I haven't seen one >motherboard capable of more than 4G worth of SIMMs. The Dell PowerEdge 6450 supports 8 GB of RAM. http://www.dell.com/us/en/biz/products/model_pedge_pedge_6400.htm If I understand your comments in a few follow-up messages correctly you're saying that this effort may be better spent by working on an IA-64 port and making it support large memory configurations? Can you elaborate? -Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 10:30:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id B9E3437B405 for ; Thu, 2 Aug 2001 10:30:13 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 0B2FF38D17 for ; Thu, 2 Aug 2001 14:30:12 -0300 (EST) Received: (qmail 4367 invoked by uid 0); 2 Aug 2001 17:29:16 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 17:29:16 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72HUB401729; Thu, 2 Aug 2001 14:30:11 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 14:30:11 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Charles Randall Cc: "'tlambert2@mindspring.com'" , craig , Subject: RE: How to visit physical memory above 4G? In-Reply-To: <5FE9B713CCCDD311A03400508B8B30130828F234@bdr-xcln.corp.matchlogic.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Charles Randall wrote: > From: Terry Lambert [mailto:tlambert2@mindspring.com] > >I have yet to see one person using it for anything. So far, > >it is nothing more than marketing fodder: I haven't seen one > >motherboard capable of more than 4G worth of SIMMs. > > The Dell PowerEdge 6450 supports 8 GB of RAM. > > http://www.dell.com/us/en/biz/products/model_pedge_pedge_6400.htm It's all a trick, they don't really exist. After all, why would people ever shell out the money for one of these useless beasts that won't be running until ia64 has gotten cheaper than these machines ? Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 10:36: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id E203437B405 for ; Thu, 2 Aug 2001 10:35:57 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [204.138.45.2]) by sabre.velocet.net (Postfix) with ESMTP id 7E44B137F33 for ; Thu, 2 Aug 2001 13:35:51 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.11.4/8.9.3) id f72HZpW28352; Thu, 2 Aug 2001 13:35:51 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15209.36726.676011.413494@trooper.velocet.net> Date: Thu, 2 Aug 2001 13:35:50 -0400 To: Freebsd-hackers@freebsd.org Subject: _real_ ram disk needed ... X-Mailer: VM 6.92 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It would seem that the semantics of mfs and md differ signifcantly. If I write data to mfs, it is only sent to swap if it absolutely must --- I chalk this upto the allocations it uses operating like process memory. If I write to md, the speed at which I write to md (swap backed) is limited by the speed of the swap device. It would appear that only a very limited amount of write buffering is going on. Now... I'm dealing with a very poorly designed _binary_ application. It writes out very large sparse matrices to disk (as much as 6G, but randomly between a few hundred meg and 6 gig). It is desireable for the system to _not_ write the blocks in question to disk unless absolutely necessary. Is there any way to make this request to the vm system? For something that fits in memory, the performance of mfs is many dozens of times faster than md. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 10:55:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 62D8C37B403 for ; Thu, 2 Aug 2001 10:55:32 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f72HmmE05676; Thu, 2 Aug 2001 17:48:48 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200108021748.f72HmmE05676@jhs.muc.de> To: freebsd-hackers@freebsd.org Cc: David Malone , Ian Dowse Subject: Re: vnconfig + mount removes permission for a second From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Thu, 02 Aug 2001 11:48:35 BST." <20010802114835.A92803@walton.maths.tcd.ie> Date: Thu, 02 Aug 2001 19:48:48 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Malone wrote: > On Wed, Aug 01, 2001 at 11:35:32AM +0000, Julian Stacey wrote: > > So something is momentarily making the image unreadable. > > Should FreeBSD [mount/kernel ?] be changed to avoid denying access ? > > When you do a mount it automatically HUP's mountd which then > re-exports NFS filesystems. I suspect what is happening is that > the the filesystem mountlist is being cleared for a moment and that > is upsetting the cp. > > You could try moving /var/run/mountd.pid out of the way and running > the mount command. That should stop mount HUPing mountd, which > would let you test this theory. Thanks, I tried your suggestion, it works ! so Mountd is the problem then ! Cp does not fail on Umount, I guess Umount happens quicker. ( One reason might have been that Umount is silent, whereas Mount caused 7 lines of complaint to console EG mountd[96]: bad exports list line /cdrom -alldirs -ro -mapall (20 years ago Unix console errs came out under polling not interrupt, so that might have been a lengthy time window, but I expect things on FreeBSD & xconsole are now improved :-) But I commented out /cdrom in /etc/exports, & still see Mount breaking Cp. ) I can also reproduce this behaviour on just one host as both amd/nfs host & target (thus avoiding ethernet, except possibly for named via ethernet) > Ian Dowse wrote: > > See PRs misc/3980 and kern/9619 for more details. I think NetBSD > tried at one point to make mountd incrementally change the export > list, but it turned out to be quite hard to get the logic right to > keep the mountd and kernel lists in sync. I think they reverted > that change eventually. I haven't seen PRs misc/3980 and kern/9619, is there any info is this thread that should be added to one of those ? > This is certainly a bug that needs to be fixed; mountd should be > able to build up a list of all exports for a filesystem and pass > them into the kernel in one "replace export list" operation. > > Maybe nice'ing mountd to run at a higher priority, Question is how high ? With Nice or Rtprio or something else ? > and/or specifying > only IP addresses in /etc/exports would help things a bit now. I converted my /etc/exports to entirely numeric, threw a sighup at named & mountd, but that did not stop the problem. Killed mountd -r & restarted with numeric exports, still did not help. Julian J.Stacey Munich Unix (FreeBSD, Linux etc) Consultant http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11: 3:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from colnta.acns.ab.ca (h24-68-206-125.sbm.shawcable.net [24.68.206.125]) by hub.freebsd.org (Postfix) with ESMTP id 98A6537B42C for ; Thu, 2 Aug 2001 11:03:40 -0700 (PDT) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.11.4/8.11.3) id f72I3Zg11539 for freebsd-hackers@freebsd.org; Thu, 2 Aug 2001 12:03:35 -0600 (MDT) (envelope-from davidc) Date: Thu, 2 Aug 2001 12:03:35 -0600 From: Chad David To: freebsd-hackers@freebsd.org Subject: Page Coloring Message-ID: <20010802120335.A11520@colnta.acns.ab.ca> Mail-Followup-To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If I added this to a man page would I be telling the truth :). Note, these are my notes and not the exact text that I would add, and I have not bother with anything to do with object coloring etc. I just want to make sure I've got this part down. Chad page coloring ------------------------------------------- The general idea behind page color is to prevent the L2 cache from dumping pages in use for any given object when it loads the next required page. To start with you have to consider how the L2 addresses pages. If the L2 is 64k, to choose an easy number, then it can address at most 16 pages. If each page is 4096 bytes, then the first twelve bits of the address do not affect the page, but instead the contents of the page. The next four bits specifiy the page number, and the remaining sixteen bits can be ignored. u - unused. p - page number. b - page bytes. b11111111111111111111111111111111 or 0x0000FBBB uuuuuuuuuuuuuuuuppppbbbbbbbbbbbb uuuupbbb Note: only bits 13 - 16 affect L2 page addressing (256k L2). If the first page of an object is at 0x0A00F000 then the L2 will see page number 16 (0xF or b1111xxxxxxxxxxxx). If the second page of an object is at 0x0B00F000 the the page number will colide with the first page, and the first page will be removed from the L2 cache. If on the other hand the second page was allocated at 0xB00A000 then its page number would be 0xA and the first page would remain in the cache. FreeBSD creates as many colors as there are pages in the L2 cache, and then breaks up the physical memory as vm_pages are added into the various colors. When a object requests a new page, it asks for a pages of the color of the pages index into the object (there is a little more to it, but in general that is what it does). So page 1 would ask for color 1, page 2 would ask for color 2 and so on. Page coloring is calculated as follows: m->pc = (pa >> PAGE_SHIFT) & PQ_L2_MASK pa = physical address PAGE_SHIFT = 12 (LOG2 page size = 4096) PQ_L2_MASK = PQ_L2_SIZE - 1 (let PQ_L2_SIZE = 64) let pa = 0x00FF0000 m->pc = (0x00FF0000 >> 12) & 0x0000003F m->pc = 0x00000FF0 & 0x0000003F m->pc = 0x00000030 The page queue that a page is on is the queue number plus the page color. If the page is on the free queue then m->queue = PQ_FREE + m->pc. To determine the base queue you simple subtract the page color. The following is often seen in the code: if ((m->queue - m->pc) == PQ_FREE) {..}. A given page color will be used every PQ_L2_SIZE pages where PQ_L2_SIZE is the PQ_CACHESIZE (L2 cache size) divided by the page size (4096). So on a machine with a 256K L2 cache PQ_L2_SIZE would be 64. vm_page_queue cnt initializations (vm_page.h, vm_pageq.c) ------------------------------------------- For a 64k L2 Cache (PQ_L2_SIZE = 16) 0 N 16 F 32 C 1 F 17 I 33 C 2 F 18 A 34 C 3 F 19 C 4 F 20 C 5 F 21 C 6 F 22 C 7 F 23 C 8 F 24 C 9 F 25 C 10 F 26 C 11 F 27 C 12 F 28 C 13 F 29 C 14 F 30 C 15 F 31 C Note: As this is layed out any reference to PQ_FREE or PQ_CACHE must be relative to the page color, while PQ_ACTIVE, PQ_INACTIVE, and PQ_NONE must not be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:18:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nipsi.home.net (dsl-213-023-032-244.arcor-ip.net [213.23.32.244]) by hub.freebsd.org (Postfix) with SMTP id B4A3C37B403 for ; Thu, 2 Aug 2001 11:18:07 -0700 (PDT) (envelope-from HypnotiZer@gmx.net) Received: (qmail 1089 invoked from network); 2 Aug 2001 18:16:45 -0000 Received: from nachpolierer.home.net (HELO nachpolierer) (172.16.1.101) by nipsi.home.net with SMTP; 2 Aug 2001 18:16:45 -0000 Message-ID: <000a01c11b7f$ec5a4520$650110ac@nachpolierer> From: "Dennis Berger" To: "Peter Pentchev" Cc: References: <000801c11b66$f57452e0$650110ac@nachpolierer> <20010802202618.A11105@ringworld.oblivion.bg> Subject: Re: keep-state rule for icmp, really stateful ??? Date: Thu, 2 Aug 2001 20:21:18 +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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry I missed something ... forget ----- Original Message ----- From: "Peter Pentchev" To: "Dennis Berger" Cc: Sent: Thursday, August 02, 2001 7:26 PM Subject: Re: keep-state rule for icmp, really stateful ??? > On Thu, Aug 02, 2001 at 05:22:36PM +0200, Dennis Berger wrote: > > Hi > > I have the following rule allowing traceroute and ping to my server. > > "200 allow icmp from any to any keep-state in recv tun0 icmptype 8" > > Now I would assume that this rule generate two dynamic rules back. > > The fire one is a rule that initiates ping to work properly it's just a dynamic ICMP rule > > 00200 2623 220332 (T 30, # 43) ty 0 icmp, 134.100.58.115 0 <-> 213.23.32.88 0 > > and the second that the traceroute UDP taffic from port 33434-33960 can pass in. > > But what happans ... the rule 200 doesn't open a second dynamic rule to allow udp traffic to specific ports back in, the traceroute UDP traffic will be blocked. To keep the icmp packetfiltering stateful it would be nice to implement this clean. Or maybe it is already implemented in CURRENT tree. What's the current state ? > > Errrr.. maybe it's just me, but I just can't see how a rule that says > 'allow icmp' should allow UDP traffic to pass through.. > Maybe you haven't shown us all the rules? (And I don't necessarily > mean 'all the rules pertaining to icmp and traceroute'.. it might > as well be that some other rule, which you do not consider relevant, > is blocking your traceroute packets.) > > G'luck, > Peter > > -- > I am jealous of the first word in this sentence. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:27:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id F334637B401 for ; Thu, 2 Aug 2001 11:27:33 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA46900; Thu, 2 Aug 2001 13:33:33 -0700 (PDT) Date: Thu, 2 Aug 2001 13:33:33 -0700 (PDT) From: Julian Elischer To: Terry Lambert Cc: Rik van Riel , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B6933F0.FC88449A@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Terry Lambert wrote: > > Name an OS that supports this; more than likely, you will > have to appeal to a purpose built embedded system. errr, linux? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:28:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 5C3C437B405 for ; Thu, 2 Aug 2001 11:28:11 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA46898; Thu, 2 Aug 2001 13:30:55 -0700 (PDT) Date: Thu, 2 Aug 2001 13:30:54 -0700 (PDT) From: Julian Elischer To: Rik van Riel Cc: Terry Lambert , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Rik van Riel wrote: > > On the really large machines, this can lead to the > situation where even the page tables hardly fit into > KVA. 4MB pages seem like the only solution ... There is no reason why we need to keep the kernel and the user process in the same 4GB map except for efficiency. There have been many UNIX machines in the past which put them in separate virtual spaces and we have kept those interfaces exactly so that we have the option of doing it one day.. e.g. copyin and copyout could copy to a totally different VM space. The kernel would haev 4GB for itself and each process would have 4BG. System calls would be come more expensive as each would require a full page-table swap and a TLB flush. However it might be worth it for some people. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:31:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 5A66437B405 for ; Thu, 2 Aug 2001 11:30:27 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id C51A938D18 for ; Thu, 2 Aug 2001 15:30:18 -0300 (EST) Received: (qmail 13833 invoked by uid 0); 2 Aug 2001 18:29:23 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 18:29:23 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72IUHI05323; Thu, 2 Aug 2001 15:30:17 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 15:30:17 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Julian Elischer Cc: Terry Lambert , craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Julian Elischer wrote: > On Thu, 2 Aug 2001, Rik van Riel wrote: > > > > On the really large machines, this can lead to the > > situation where even the page tables hardly fit into > > KVA. 4MB pages seem like the only solution ... > > There is no reason why we need to keep the kernel and the user > process in the same 4GB map except for efficiency. > > There have been many UNIX machines in the past which put them in > separate virtual spaces That was on machines where the CPU could actually address two separate spaces at once, right ? (like eg. m68k) > The kernel would haev 4GB for itself and each process would have 4BG. > > System calls would be come more expensive as each would require > a full page-table swap and a TLB flush. > However it might be worth it for some people. Interrupt handling would also require a full page table swap and TLB flush. Considering that, I think the number of people for whom this will be worth it has probably dropped a bit ;) Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:37: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 4B4CF37B405; Thu, 2 Aug 2001 11:37:00 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA14035; Thu, 2 Aug 2001 14:36:52 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA26724; Thu, 2 Aug 2001 14:36:52 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA26720; Thu, 2 Aug 2001 14:36:52 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 2 Aug 2001 14:36:52 -0400 (EDT) From: Kenneth Wayne Culver To: John Baldwin Cc: freebsd-hackers@FreeBSD.org, craig , Terry Lambert , Rik van Riel Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG BUT, don't the motherboards also have to support this? And isn't it only supported through some wierd segmentation thing? KEn On Thu, 2 Aug 2001, John Baldwin wrote: > > On 02-Aug-01 Kenneth Wayne Culver wrote: > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > particular PIII motherboard supports this, then it's using some kind of > > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > > chip I believe; and the PIII is a 32-bit chip. > > > > Ken > > Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before > Pentium II) have supported PAE which allows for a 36-bit physical address. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - 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 Thu Aug 2 11:46:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 550D637B401 for ; Thu, 2 Aug 2001 11:46:43 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f72Ikc622564 for ; Thu, 2 Aug 2001 14:46:38 -0400 (EDT) Date: Thu, 2 Aug 2001 14:46:19 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: Allocate a page at interrupt time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG FreeBSD can not allocate from the PQ_CACHE queue in an interrupt context. Can anyone explain it to me why this is the case? Thanks, -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:46:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 930A237B401 for ; Thu, 2 Aug 2001 11:46:50 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA47000; Thu, 2 Aug 2001 13:48:22 -0700 (PDT) Date: Thu, 2 Aug 2001 13:48:21 -0700 (PDT) From: Julian Elischer To: David Gilbert Cc: Freebsd-hackers@freebsd.org Subject: Re: _real_ ram disk needed ... In-Reply-To: <15209.36726.676011.413494@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It might be possible to make a device that could acces > 4GB using the new paging methods available in PIII but it might require suspending th erest of the OS while you do it, and having a 4MB 'window' into which you COPY data to and from the extended space. (still it may be faster than disk) On Thu, 2 Aug 2001, David Gilbert wrote: > It would seem that the semantics of mfs and md differ signifcantly. > If I write data to mfs, it is only sent to swap if it absolutely must > --- I chalk this upto the allocations it uses operating like process > memory. If I write to md, the speed at which I write to md (swap > backed) is limited by the speed of the swap device. It would appear > that only a very limited amount of write buffering is going on. > > Now... I'm dealing with a very poorly designed _binary_ application. > It writes out very large sparse matrices to disk (as much as 6G, but > randomly between a few hundred meg and 6 gig). It is desireable for > the system to _not_ write the blocks in question to disk unless > absolutely necessary. > > Is there any way to make this request to the vm system? > > For something that fits in memory, the performance of mfs is many > dozens of times faster than md. > > Dave. > > -- > ============================================================================ > |David Gilbert, Velocet Communications. | Two things can only be | > |Mail: dgilbert@velocet.net | equal if and only if they | > |http://www.velocet.net/~dgilbert | are precisely opposite. | > =========================================================GLO================ > > 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 Aug 2 11:49:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id B0AAC37B401 for ; Thu, 2 Aug 2001 11:49:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA47015; Thu, 2 Aug 2001 13:52:26 -0700 (PDT) Date: Thu, 2 Aug 2001 13:52:25 -0700 (PDT) From: Julian Elischer To: Rik van Riel Cc: Terry Lambert , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Rik van Riel wrote: > On Thu, 2 Aug 2001, Julian Elischer wrote: > > On Thu, 2 Aug 2001, Rik van Riel wrote: > > > > > > On the really large machines, this can lead to the > > > situation where even the page tables hardly fit into > > > KVA. 4MB pages seem like the only solution ... > > > > There is no reason why we need to keep the kernel and the user > > process in the same 4GB map except for efficiency. > > > > There have been many UNIX machines in the past which put them in > > separate virtual spaces > > That was on machines where the CPU could actually > address two separate spaces at once, right ? > (like eg. m68k) > > > The kernel would haev 4GB for itself and each process would have 4BG. > > > > System calls would be come more expensive as each would require > > a full page-table swap and a TLB flush. > > However it might be worth it for some people. > > Interrupt handling would also require a full page table > swap and TLB flush. > > Considering that, I think the number of people for whom > this will be worth it has probably dropped a bit ;) True, but it might still be worth it for some people (but not the project as a whole). At one stage I heard that they were thinking of having a separate set of page tables for different security 'rings' but obviously that didn't happen.. > > Rik > -- > Executive summary of a recent Microsoft press release: > "we are concerned about the GNU General Public License (GPL)" > > > http://www.surriel.com/ > http://www.conectiva.com/ http://distro.conectiva.com/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:49:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 8DF1B37B403; Thu, 2 Aug 2001 11:49:15 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id NAA47023; Thu, 2 Aug 2001 13:55:11 -0700 (PDT) Date: Thu, 2 Aug 2001 13:55:10 -0700 (PDT) From: Julian Elischer To: Kenneth Wayne Culver Cc: John Baldwin , freebsd-hackers@FreeBSD.org, craig , Terry Lambert , Rik van Riel Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No The space is linear in physical space and if you have PCI/64 capable devices they can access it all too. (In fact 64 bit addresses have been supported even in 32 bit wide PCI since day 1). On Thu, 2 Aug 2001, Kenneth Wayne Culver wrote: > BUT, don't the motherboards also have to support this? And isn't it only > supported through some wierd segmentation thing? > > KEn > > On Thu, 2 Aug 2001, John Baldwin wrote: > > > > > On 02-Aug-01 Kenneth Wayne Culver wrote: > > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > > particular PIII motherboard supports this, then it's using some kind of > > > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > > > chip I believe; and the PIII is a 32-bit chip. > > > > > > Ken > > > > Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before > > Pentium II) have supported PAE which allows for a 36-bit physical address. > > > > -- > > > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > > > 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 Aug 2 11:49:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id F1FD037B403 for ; Thu, 2 Aug 2001 11:49:46 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [204.138.45.2]) by sabre.velocet.net (Postfix) with ESMTP id 24DBF137FCA; Thu, 2 Aug 2001 14:49:46 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.11.4/8.9.3) id f72Injc46720; Thu, 2 Aug 2001 14:49:45 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15209.41161.658146.175559@trooper.velocet.net> Date: Thu, 2 Aug 2001 14:49:45 -0400 To: Julian Elischer Cc: David Gilbert , Freebsd-hackers@freebsd.org Subject: Re: _real_ ram disk needed ... In-Reply-To: References: <15209.36726.676011.413494@trooper.velocet.net> X-Mailer: VM 6.92 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "Julian" == Julian Elischer writes: Julian> It might be possible to make a device that could acces > 4GB Julian> using the new paging methods available in PIII but it might Julian> require suspending th erest of the OS while you do it, and Julian> having a 4MB 'window' into which you COPY data to and from the Julian> extended space. (still it may be faster than disk) Well... I also suspect that you could "hack" something up that split the address space among several processes, but the requirement that writing not block is more important than absoutely getting to 6 gig. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 11:55:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 609FF37B401 for ; Thu, 2 Aug 2001 11:55:17 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id LAA05857; Thu, 2 Aug 2001 11:54:26 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 02 Aug 2001 11:54:25 -0700 (PDT) From: John Baldwin To: Kenneth Wayne Culver Subject: Re: How to visit physical memory above 4G? Cc: Rik van Riel Cc: Rik van Riel , Terry Lambert , craig , freebsd-hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Aug-01 Kenneth Wayne Culver wrote: > BUT, don't the motherboards also have to support this? And isn't it only > supported through some wierd segmentation thing? > > KEn The motherboards do, yes, and they have. It's not segmentation. It's only in the paging that this is done. Go to developer.intel.com and get the IA32 manuals, specifially volume 3: system programming, then look for 'Physical Address Extensions' and start reading. > On Thu, 2 Aug 2001, John Baldwin wrote: > >> >> On 02-Aug-01 Kenneth Wayne Culver wrote: >> > Also, the PIII CAN'T natively support more than 4GB of ram. If a >> > particular PIII motherboard supports this, then it's using some kind of >> > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit >> > chip I believe; and the PIII is a 32-bit chip. >> > >> > Ken >> >> Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before >> Pentium II) have supported PAE which allows for a 36-bit physical address. >> >> -- >> >> John Baldwin -- http://www.FreeBSD.org/~jhb/ >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ >> > -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Aug 2 11:57:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 4AA3A37B403; Thu, 2 Aug 2001 11:57:17 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA17413; Thu, 2 Aug 2001 14:57:13 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA01385; Thu, 2 Aug 2001 14:55:28 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA01381; Thu, 2 Aug 2001 14:55:28 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 2 Aug 2001 14:55:28 -0400 (EDT) From: Kenneth Wayne Culver To: Julian Elischer Cc: John Baldwin , freebsd-hackers@FreeBSD.org, craig , Terry Lambert , Rik van Riel Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > No > The space is linear in physical space and if you have PCI/64 > capable devices they can access it all too. > > (In fact 64 bit addresses have been supported even in 32 bit wide PCI > since day 1). OK, then what was that whole paging thing everyone was talking about, I thought that was partially done in hardware on the chipset of the motherboard... or was that completely in the operating system? Ken > > On Thu, 2 Aug 2001, Kenneth Wayne Culver wrote: > > > BUT, don't the motherboards also have to support this? And isn't it only > > supported through some wierd segmentation thing? > > > > KEn > > > > On Thu, 2 Aug 2001, John Baldwin wrote: > > > > > > > > On 02-Aug-01 Kenneth Wayne Culver wrote: > > > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > > > particular PIII motherboard supports this, then it's using some kind of > > > > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > > > > chip I believe; and the PIII is a 32-bit chip. > > > > > > > > Ken > > > > > > Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before > > > Pentium II) have supported PAE which allows for a 36-bit physical address. > > > > > > -- > > > > > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > > > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > > > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > > > > > > > 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 Aug 2 11:57:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id B6DF737B401; Thu, 2 Aug 2001 11:57:17 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA17428; Thu, 2 Aug 2001 14:57:16 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id OAA01739; Thu, 2 Aug 2001 14:57:15 -0400 (EDT) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id OAA01735; Thu, 2 Aug 2001 14:57:15 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Thu, 2 Aug 2001 14:57:15 -0400 (EDT) From: Kenneth Wayne Culver To: John Baldwin Cc: Rik van Riel , Rik van Riel , Terry Lambert , craig , freebsd-hackers@FreeBSD.org Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, John Baldwin wrote: > > On 02-Aug-01 Kenneth Wayne Culver wrote: > > BUT, don't the motherboards also have to support this? And isn't it only > > supported through some wierd segmentation thing? > > > > KEn > > The motherboards do, yes, and they have. It's not segmentation. It's only in > the paging that this is done. Go to developer.intel.com and get the IA32 > manuals, specifially volume 3: system programming, then look for 'Physical > Address Extensions' and start reading. > Alright, I guess I will later, although I doubt I'll be able to make much use of it. I usually only read the docs for hardware I'm going to write a driver for. :-) Ken > > On Thu, 2 Aug 2001, John Baldwin wrote: > > > >> > >> On 02-Aug-01 Kenneth Wayne Culver wrote: > >> > Also, the PIII CAN'T natively support more than 4GB of ram. If a > >> > particular PIII motherboard supports this, then it's using some kind of > >> > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > >> > chip I believe; and the PIII is a 32-bit chip. > >> > > >> > Ken > >> > >> Go look at some Intel docs. P6 chips since the Pentium Pro (yes, before > >> Pentium II) have supported PAE which allows for a 36-bit physical address. > >> > >> -- > >> > >> John Baldwin -- http://www.FreeBSD.org/~jhb/ > >> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > >> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > >> > > > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - 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 Thu Aug 2 12:14:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from romeo.unimessage.net (cbrtmx01.unimessage.net [212.6.90.199]) by hub.freebsd.org (Postfix) with ESMTP id 6AB0037B401 for ; Thu, 2 Aug 2001 12:14:19 -0700 (PDT) (envelope-from thenamelessone@abacho.de) Received: from shakespeare.unimessage.net (shakespeare.unimessage.net [10.20.1.70]) by romeo.unimessage.net (8.11.2/8.11.2/Debian 8.11.0-6) with ESMTP id f72JEHK27059 for ; Thu, 2 Aug 2001 21:14:17 +0200 Received: from aaron.unimessage.net (aaron [10.20.1.20]) by shakespeare.unimessage.net (Postfix) with ESMTP id 73F1C78 for ; Thu, 2 Aug 2001 21:14:18 +0200 (MET DST) Message-ID: <-1092334714.996778934042.JavaMail.root@aaron.unimessage.net> From: thenamelessone@abacho.de To: freebsd-hackers@FreeBSD.org Subject: Re: How to visit physical memory above 4G? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Canbox-Sender: thenamelessone@abacho.de X-Canbox-MsgType: email X-Canbox-SendDate: 996779652660 X-Canbox-UserName: thenamelessone X-Canbox-ServiceGroup: abachode Date: Thu, 2 Aug 2001 21:14:18 +0200 (MET DST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG why is nobody trying to read the intel documentation??? 1.page adress extension is available since pentium pro. 2.you can only adress the 36 bit adress space when paging is enable 3.a flag has to be set 4.the linear adresses are a bit different without PAX: bits 31 thru 22 are an offset into the page directory bit 21 thru 12 are an offset into the page table bit 11 thru 0 are an offset into the page with PAX: bits 31 thru 30 are an offset into the page directory pointer table bits 29 thru 21 are an offset into the page directory bits 20 thru 12 are an offset into the page table bits 11 thru 0 are an offset into the page sometimes its very useful if you did some low-level (REAL low-level) coding To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 12:19:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from perninha.conectiva.com.br (perninha.conectiva.com.br [200.250.58.156]) by hub.freebsd.org (Postfix) with ESMTP id 2268B37B401 for ; Thu, 2 Aug 2001 12:19:03 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from burns.conectiva (burns.conectiva [10.0.0.4]) by perninha.conectiva.com.br (Postfix) with SMTP id 2163038D2B for ; Thu, 2 Aug 2001 15:39:57 -0300 (EST) Received: (qmail 16247 invoked by uid 0); 2 Aug 2001 18:39:01 -0000 Received: from duckman.distro.conectiva (HELO duckman.conectiva.com.br) (root@10.0.17.2) by burns.conectiva with SMTP; 2 Aug 2001 18:39:01 -0000 Received: from localhost (riel@localhost) by duckman.conectiva.com.br (8.11.4/8.11.3) with ESMTP id f72Idr005952; Thu, 2 Aug 2001 15:39:54 -0300 X-Authentication-Warning: duckman.distro.conectiva: riel owned process doing -bs Date: Thu, 2 Aug 2001 15:39:52 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Kenneth Wayne Culver Cc: John Baldwin , , craig , Terry Lambert Subject: Re: How to visit physical memory above 4G? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Kenneth Wayne Culver wrote: "Replying above an email because the curser is there is like shitting in your pants because your ass is there when you need to go to the toilet." > BUT, don't the motherboards also have to support this? And isn't > it only supported through some wierd segmentation thing? Yes, the mainboard needs to support the memory. No, there is no weird segmentation thing, at least not visible from software. regards, Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 13: 1:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 6970537B403 for ; Thu, 2 Aug 2001 13:01:35 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f72K1Pn19909 for ; Thu, 2 Aug 2001 22:01:31 +0200 (SAST) (envelope-from lists@security.za.net) Date: Thu, 2 Aug 2001 22:01:25 +0200 (SAST) From: lists To: freebsd-hackers@freebsd.org Subject: Wierd IRQ Routing issues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, hoping someone can help me out with something here, because Ive got a very strange problem. On my one pc, when assigning an IRQ to my PCIC device, it assigns an IRQ and continues, works 100% now that I changed device.hints to look for pcic on pci instead of isa, card works everything. However, on my other pc with an identical setup, when trying to assign pcic irq it does this: (from dmesg): pci_cfgintr_search: linked (3) to configured irq 10 at 0:9:0 pci_cfgintr: 0:10 INTA routed to irq 10 Now for some reason I have it in my head that that irq routing is broken, because its the only difference I can find between the non-working box and the working box. Is there any way that I can force that card to not use a routed interrupt like that. Ive already tried fiddling in my bios with the IRQ settings to reserve things etc, no luck there either. I know for a fact that irq 5/7/9/10/11 are all available on my box, with nothing taking them. Any ideas would be MUCH appreciated Thanks Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 13: 6:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id E928037B405 for ; Thu, 2 Aug 2001 13:06:49 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 699 invoked by uid 1000); 2 Aug 2001 20:05:40 -0000 Date: Thu, 2 Aug 2001 23:05:40 +0300 From: Peter Pentchev To: lists Cc: freebsd-hackers@freebsd.org Subject: Re: Wierd IRQ Routing issues Message-ID: <20010802230540.B480@ringworld.oblivion.bg> Mail-Followup-To: lists , freebsd-hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from lists@security.za.net on Thu, Aug 02, 2001 at 10:01:25PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 02, 2001 at 10:01:25PM +0200, lists wrote: > Hi, hoping someone can help me out with something here, because Ive got a > very strange problem. > > On my one pc, when assigning an IRQ to my PCIC device, it assigns an IRQ > and continues, works 100% now that I changed device.hints to look for pcic > on pci instead of isa, card works everything. > > However, on my other pc with an identical setup, when trying to assign > pcic irq it does this: (from dmesg): > > pci_cfgintr_search: linked (3) to configured irq 10 at 0:9:0 > pci_cfgintr: 0:10 INTA routed to irq 10 > > Now for some reason I have it in my head that that irq routing is broken, > because its the only difference I can find between the non-working box and > the working box. Is there any way that I can force that card to not use a > routed interrupt like that. Ive already tried fiddling in my bios with > the IRQ settings to reserve things etc, no luck there either. I know for > a fact that irq 5/7/9/10/11 are all available on my box, with nothing > taking them. > > Any ideas would be MUCH appreciated The second box wouldn't be a -stable machine, would it now? I think PCIC IRQ routing was absolutely not working in -stable as of a few weeks ago, when Warner Losh started MFC'ing the PCIC bits. That MFC might not be complete yet. If both boxes are running -current, I'll just shut up :) G'luck, Peter -- This would easier understand fewer had omitted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 13: 8:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 5CA0337B401 for ; Thu, 2 Aug 2001 13:08:46 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f72K8Vt20125; Thu, 2 Aug 2001 22:08:34 +0200 (SAST) (envelope-from lists@security.za.net) Date: Thu, 2 Aug 2001 22:08:31 +0200 (SAST) From: lists To: Peter Pentchev Cc: freebsd-hackers@freebsd.org Subject: Re: Wierd IRQ Routing issues In-Reply-To: <20010802230540.B480@ringworld.oblivion.bg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Both boxes are -current :) Thanks Andrew On Thu, 2 Aug 2001, Peter Pentchev wrote: > On Thu, Aug 02, 2001 at 10:01:25PM +0200, lists wrote: > > Hi, hoping someone can help me out with something here, because Ive got a > > very strange problem. > > > > On my one pc, when assigning an IRQ to my PCIC device, it assigns an IRQ > > and continues, works 100% now that I changed device.hints to look for pcic > > on pci instead of isa, card works everything. > > > > However, on my other pc with an identical setup, when trying to assign > > pcic irq it does this: (from dmesg): > > > > pci_cfgintr_search: linked (3) to configured irq 10 at 0:9:0 > > pci_cfgintr: 0:10 INTA routed to irq 10 > > > > Now for some reason I have it in my head that that irq routing is broken, > > because its the only difference I can find between the non-working box and > > the working box. Is there any way that I can force that card to not use a > > routed interrupt like that. Ive already tried fiddling in my bios with > > the IRQ settings to reserve things etc, no luck there either. I know for > > a fact that irq 5/7/9/10/11 are all available on my box, with nothing > > taking them. > > > > Any ideas would be MUCH appreciated > > The second box wouldn't be a -stable machine, would it now? > I think PCIC IRQ routing was absolutely not working in -stable as of > a few weeks ago, when Warner Losh started MFC'ing the PCIC bits. > That MFC might not be complete yet. > > If both boxes are running -current, I'll just shut up :) > > G'luck, > Peter > > -- > This would easier understand fewer had omitted. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 13:14:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns2.myway.com.br (ns2.myway.com.br [200.186.239.2]) by hub.freebsd.org (Postfix) with SMTP id BA8FE37B403; Thu, 2 Aug 2001 13:14:14 -0700 (PDT) (envelope-from leal@myway.com.br) Received: from myway.com.br (unverified [200.186.239.10]) by ns2.myway.com.br (EMWAC SMTPRS 0.83) with SMTP id ; Thu, 02 Aug 2001 17:13:10 -0300 Message-ID: <3B69B553.FE5F0C@myway.com.br> Date: Thu, 02 Aug 2001 17:17:23 -0300 From: Marcelo Leal Organization: webcom X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-RELEASE i386) X-Accept-Language: pt-BR, en MIME-Version: 1.0 To: Chris Dillon Cc: Terry Lambert , Julian Elischer , "Eugene L. Vorokov" , Soren Kristensen , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: arp References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Antirelay: Good relay from local net2 200.186.239.0/24 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG thanks!!! sorry but just now i see your message... the problem is alive... i will look what you sugest... but this problem don't would be the switch ports??? switch arp tables??? the linux machines (clients) don't loose the arp address of my dhcp server... but the windows machines and freebsd boxes do. do ipfnat nat for icmp requests??? when two or more machines ping the same host in internet, just one receive the reply. these two problems are drive me crazy! the linux box (dhcp server) did not had these problems... i trust in freebsd... if i add more time to leases... when the time go out the problem will come back... right??? why the linux boxes (clients) work fine???? thanks Chris Dillon wrote: > > On Fri, 27 Jul 2001, Marcelo Leal wrote: > > > folks... > > sorry, but i trust in you :O) > > i have a problem, and don't know where find the answers... and that list > > is for net problems... > > my desktop freebsd give me a message: arp moved from: xxx to xxx... ARP > > MOVED???? > > when i look in arp table.... the arp address of my dhcpd server is > > wrong!!! i put the right there... and reboot... look and.... the > > wrong!!!! > > this mac address is not from my network... (machines) .. > > maybe arp of the switch ports... > > thanks!!! > > and sorry by the english... :O) > > i'm brazilian. > > You have more than one machine on the network that is attempting to > use the same IP address and/or your DHCP server is handing out leases > that are shorter than the ARP cache life and you are recycling DHCP > leases quickly. > > I suggest you set your DHCP lease times to at least an hour or more > (my DHCP leases are one week), and make sure there are no > manually-configured machines that are attempting to use an address > from the DHCP address pool, or two manually-configured machines trying > to use the same address. > > -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > FreeBSD: The fastest and most stable server OS on the planet > - Available for IA32 (Intel x86) and Alpha architectures > - IA64 (Itanium), PowerPC, and ARM architectures under development > - http://www.freebsd.org > > 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 Aug 2 13:47:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D4C6537B403; Thu, 2 Aug 2001 13:47:30 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.4/8.11.4) with SMTP id f72KlRf78473; Thu, 2 Aug 2001 16:47:27 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 2 Aug 2001 16:47:26 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: REMINDER: FreeBSD Monthly Development Status Report -- Request For Submissions (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a final reminder that status reports are due tomorrow afternoon, please submit your reports ASAP so as to make sure they get included. Just as a reminder, this is a request for status for on-going and completed projects since the last status report, and can include both raw software development and other things that might be going on. Things don't have to be merged into -STABLE for it to count, it can be "shoot yourself in the foot"-style status from -CURRENT. Things I haven't received status reports on: - KSE - SMPng - OpenSSL - OpenSSH - KerberosV work - KAME - The kernel summit at USENIX These are all important things that are going on in the project, and we'd like to let the world that we're doing this cool stuff. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services ---------- Forwarded message ---------- Date: Sat, 28 Jul 2001 18:26:31 -0400 (EDT) From: Robert Watson To: freebsd-hackers@FreeBSD.org, developers@FreeBSD.org Subject: FreeBSD Monthly Development Status Report -- Request For Submissions It's that time again! The last FreeBSD Development Status report was over a month ago, and given its success, we'll try it again this month. As with the previous edition, I'm interested in seeing about one paragraph per on-going project (or for major projects, a paragraph for each major component of the project) describing work that has happened since the last report. If no prior report has been given for the project, a general overview paragraph as well as status is acceptable. If more than one person is working on a project, only a single report should be submitted (although if there are reports for components, they might be seperately submitted by the relevant developers). Take a look at the previous month's report for a sense of how this works (in particular, see how TrustedBSD and SMPng reports were broken out). Developers should feel free to submit more than one report, if they are working on more than one project. Reports should relate to the FreeBSD Project, but are not limited to software development: they could include documentation work, web work, FreeBSD.org cluster management, cooperation with application developers, public relations activities, partnering with companies, funding announcements for new projects, etc. In the past report the primary focus was development, and that will remain important to the status report, of course, but other parts of the FreeBSD Project are welcome to submit status! Please submit reports in the following format: Project: (name here -- required) URL: (URL, if any, here -- omit line if none) Contact: (name and e-mail address of a contact point -- required) One paragraph on the topic of the project status since the last report, indented two spaces, and wrapped before column 78. Plain text only, please. Please send submissions to: robert+freebsd.monthly@cyrus.watson.org The deadline for submissions is Friday August 3, 2001, at 3:00pm EST. The report will be released soon thereafter. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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 Aug 2 13:50:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9E34837B401; Thu, 2 Aug 2001 13:50:48 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.4/8.11.4) with SMTP id f72Koif78506; Thu, 2 Aug 2001 16:50:44 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 2 Aug 2001 16:50:44 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: developers@FreeBSD.org, hackers@FreeBSD.org Subject: Re: REMINDER: FreeBSD Monthly Development Status Report -- Request For Submissions (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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG To be honest, I unfairly singled out KSE in the last message -- Julian has submitted a status report, and I overlooked it in my mailbox. Sorry, Julian. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 14:39:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id AFCA337B401 for ; Thu, 2 Aug 2001 14:39:32 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA23224; Thu, 2 Aug 2001 14:39:30 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 02 Aug 2001 14:39:29 -0700 (PDT) From: John Baldwin To: natedac@kscable.com Subject: PR 25958 Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nate, Can you try out the patch at http://www.freebsd.org/~jhb/patches/mtrr.patch? It's similar to the patch in the PR with a slight cleanup. The patch is against current, but hopefully it applies ok to stable. (It should I think). The patch is also included below for other people to look at in case they have gripes. The basic issue is that the MTRR's on Nate's box don't work in a way that XFree86 wants them to, so XFree86 causes his kernel to panic. :( The patch adds a new loader tunable 'machdep.disable_mtrrs' that can be set to a non-zero value to disable probing and use of MTRR's. I realize that being able to automatically disable MTRR's for known bad AMD chips would be nice, but until we know what chips are bad, this is at least a functional workaround. Index: i686_mem.c =================================================================== RCS file: /usr/cvs/src/sys/i386/i386/i686_mem.c,v retrieving revision 1.13 diff -u -r1.13 i686_mem.c --- i686_mem.c 2001/04/27 19:28:19 1.13 +++ i686_mem.c 2001/08/02 21:38:08 @@ -60,6 +60,9 @@ #define mrcopyflags(curr, new) (((curr) & ~MDF_ATTRMASK) | ((new) & MDF_ATTRMASK)) +static int mtrrs_disabled; +TUNABLE_INT("machdep.disable_mtrrs", &mtrrs_disabled); + static void i686_mrinit(struct mem_range_softc *sc); static int i686_mrset(struct mem_range_softc *sc, struct mem_range_desc *mrd, @@ -569,7 +572,7 @@ i686_mem_drvinit(void *unused) { /* Try for i686 MTRRs */ - if ((cpu_feature & CPUID_MTRR) && + if (!mtrrs_disabled && (cpu_feature & CPUID_MTRR) && ((cpu_id & 0xf00) == 0x600) && ((strcmp(cpu_vendor, "GenuineIntel") == 0) || (strcmp(cpu_vendor, "AuthenticAMD") == 0))) { -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Thu Aug 2 15: 4:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 6964D37B403 for ; Thu, 2 Aug 2001 15:04:09 -0700 (PDT) (envelope-from oppermann@telehouse.ch) Received: (qmail 41034 invoked from network); 2 Aug 2001 22:03:37 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.21.178]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Aug 2001 22:03:37 -0000 Message-ID: <3B69CE3F.1BCCB280@telehouse.ch> Date: Fri, 03 Aug 2001 00:03:43 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: freebsd-net@freebsd.org Subject: 303,000 routes in kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello guys have got a small problem. I'm running a secondary DNS server for the ccTLD .ch here in Switzerland. The box is a Intel ISP2150 with a PIII-750 and 512MB RAM plus 18GB SCSI disk. Two fxp cards inside. This machine is running FreeBSD 4.3-RELEASE and tinydns as DNS server. It answering approximatly 100 dns requests per second for the .ch ccTLD zone. These DNS requests come from all over the world so I see basically the whole allocated IP address space here. The problem I've got now is that for every packet I get the kernel is making one host entry in the routing table. Because of the many UDP DNS requests from all over the world I've got 303'000 (yes, three- hundredthreethousand) entries in the kernel routing table which have not expired yet. So I'm getting error messages like this now: Aug 2 23:57:14 ccTLD /kernel: arpresolve: can't allocate llinfo for 194.42.48.126 rt Aug 2 23:57:14 ccTLD /kernel: arplookup 194.42.48.126 failed: could not allocate llinfo # netstat -m 149/640/6144 mbufs in use (current/peak/max): 146 mbufs allocated to data 3 mbufs allocated to packet headers 128/304/1536 mbuf clusters in use (current/peak/max) 768 Kbytes allocated to network (16% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines # netstat -rn | wc -l 303875 # vmstat -m Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ... routetbl607857 85480K 85480K 85480K 2420956 0 0 16,32,64,128,256 ... Memory Totals: In Use Free Requests 91073K 2948K 786316696 So many routing entries are total overkill, all I would need in reality are the default route plus some other, or in worst case a full view of the Internet prefixes (approx. 105,000 at the moment) but definatly not a host route for every UDP packet I get. The network route would be absolutely sufficient for delivering the packet back to it's origin. Any ideas on how to deal with this? TIA -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 15: 9:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 8474B37B401; Thu, 2 Aug 2001 15:09:38 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.4/8.11.4) with ESMTP id f72M9Qx93102; Fri, 3 Aug 2001 00:09:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Andre Oppermann Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel In-Reply-To: Your message of "Fri, 03 Aug 2001 00:03:43 +0200." <3B69CE3F.1BCCB280@telehouse.ch> Date: Fri, 03 Aug 2001 00:09:26 +0200 Message-ID: <93100.996790166@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B69CE3F.1BCCB280@telehouse.ch>, Andre Oppermann writes: >The problem I've got now is that for every packet I get the kernel is >making one host entry in the routing table. Because of the many UDP >DNS requests from all over the world I've got 303'000 (yes, three- >hundredthreethousand) entries in the kernel routing table which have >not expired yet. So I'm getting error messages like this now: Hmm, I wasn't aware that we cloned routes for UDP packets, are you sure that is what is causing the routes to exists ? (Just to mention the obvious: it's not CodeRed probes ?) You can tweak the route behaviour with some sysctls: Notably: net.inet.ip.rtexpire: 473 net.inet.ip.rtminexpire: 10 net.inet.ip.rtmaxcache: 128 There's probably also a detailed explanation what they do somewhere... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 15:27:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 0278037B403 for ; Thu, 2 Aug 2001 15:27:38 -0700 (PDT) (envelope-from oppermann@telehouse.ch) Received: (qmail 41895 invoked from network); 2 Aug 2001 22:27:11 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.21.178]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 2 Aug 2001 22:27:11 -0000 Message-ID: <3B69D3C5.3562B7C4@telehouse.ch> Date: Fri, 03 Aug 2001 00:27:17 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel References: <93100.996790166@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > > In message <3B69CE3F.1BCCB280@telehouse.ch>, Andre Oppermann writes: > > >The problem I've got now is that for every packet I get the kernel is > >making one host entry in the routing table. Because of the many UDP > >DNS requests from all over the world I've got 303'000 (yes, three- > >hundredthreethousand) entries in the kernel routing table which have > >not expired yet. So I'm getting error messages like this now: > > Hmm, I wasn't aware that we cloned routes for UDP packets, are you sure > that is what is causing the routes to exists ? (Just to mention the > obvious: it's not CodeRed probes ?) No, it's not code red probes. My apache log is only 3 Meg in size and has not been rotated in the past 2 month. So, yes, it looks like UDP packets are also generating cloned routes. > You can tweak the route behaviour with some sysctls: > > Notably: > net.inet.ip.rtexpire: 473 > net.inet.ip.rtminexpire: 10 > net.inet.ip.rtmaxcache: 128 Isn't this for fastforwarding? > There's probably also a detailed explanation what they do somewhere... Is there any knob to turn route cloning off? Would that hurt? -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 15:46:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id B7EC137B401 for ; Thu, 2 Aug 2001 15:46:34 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA48007 for ; Thu, 2 Aug 2001 17:57:53 -0700 (PDT) Date: Thu, 2 Aug 2001 17:57:53 -0700 (PDT) From: Julian Elischer To: hackers@freebsd.org Subject: a little O/T, but D.V.D. drives&freeBSD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG anyone had success watching a dvd? (Anyone have the correct components saved away somewhere?) just got a drive and would like to test it.. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 15:47:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.kscable.com (fe4.rdc-kc.rr.com [24.94.163.51]) by hub.freebsd.org (Postfix) with ESMTP id 6435637B401; Thu, 2 Aug 2001 15:47:07 -0700 (PDT) (envelope-from natedac@kscable.com) Received: from wks-166-131-9.kscable.com ([24.166.131.9]) by mail4.kscable.com with Microsoft SMTPSVC(5.5.1877.537.53); Thu, 2 Aug 2001 17:47:04 -0500 Date: Thu, 2 Aug 2001 17:44:54 -0500 (CDT) From: Nate Dannenberg X-X-Sender: To: John Baldwin Cc: Subject: Re: PR 25958 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, John Baldwin wrote: > Nate, > > Can you try out the patch at http://www.freebsd.org/~jhb/patches/mtrr.patch? I'd be glad to, however I no longer run FreeBSD. I have since switched to Linux. While FreeBSD was stable and reliable on my machine, I found that support for it was lacking in things like multimedia (playing movies, watching TV, and so on). I can say though that the MTRR problem is definitely a bug - under Linux MTRR's cause no trouble at all. I now use Linux Mandrake 8 with the default 2.4.3 kernel. > It's similar to the patch in the PR with a slight cleanup. The patch is > against current, but hopefully it applies ok to stable. (It should I think). The patch below looks like it should work. Not being much of a C programmer anymore I can't really say for certain though :) It might be adviseable to close this PR if no one else can verify the patch. -- _________________________ ___ ___ | natedac@kscable.com //ZZ]__ | | C64/C128/SCPU |'/ |Z/ | | What's *YOUR* Hobby!? | \__|_\ | |_________________________\___]___| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 16:14:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by hub.freebsd.org (Postfix) with ESMTP id 1A0A337B401 for ; Thu, 2 Aug 2001 16:14:45 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([65.92.121.134]) by tomts13-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010802231444.WVWN4521.tomts13-srv.bellnexxia.net@penix.org>; Thu, 2 Aug 2001 19:14:44 -0400 Message-ID: <3B69AA49.6050605@penix.org> Date: Thu, 02 Aug 2001 19:30:17 +0000 From: Paul Halliday User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.2) Gecko/20010722 X-Accept-Language: en-us MIME-Version: 1.0 To: Bill Fumerola Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: connecting a FujiFinePix1400 (USB) ? References: <20010801155934.B36262@support.euronet.nl> <3B6839F0.5080906@penix.org> <20010801220425.V2759@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bill Fumerola wrote: > On Wed, Aug 01, 2001 at 05:18:40PM +0000, Paul Halliday wrote: > > >>heh.. freebsd usb sucks. >>I have a handspring and a fujifilm finepix40i that are just sitting here >>collecting dust. >> >> >> From 3.4 - 4.3 S I have tried every available means, packages, patches >>to get either of them working with 0 luck. >> >>If you do happen to get it up and running, please let me know how you >>achieved such a miraculous feat. >> > > freebsd usb sucks? no. application support sucks. I've found freebsd's > usb drivers present applications everything they need to support hardware > such as this and normally its the available applications (gphoto, in > this case) that fall short. Actually, it was fujiplay that I had tried. But yes, gphoto 0.4.3 wasn't much help either. They say that their beta release, I think 2.0, is supposed to work. However, repeated attempts at compiling fell a little short of my expectations. As for the PDA, according to mailing list sputterings some have had success. Others have not. I have tried coldsync, gpilot,jpilot etc with little luck.. oH, cept for mad core dumps and a system freeze that can be duplicated on both the desktop and the lappy. Stupid gnome. -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 16:39: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from vulcans.dynamic.spock.org (pcd231215.netvigator.com [203.198.243.215]) by hub.freebsd.org (Postfix) with ESMTP id A4F8B37B401 for ; Thu, 2 Aug 2001 16:39:04 -0700 (PDT) (envelope-from jon@vulcans.dynamic.spock.org) Received: (from jon@localhost) by vulcans.dynamic.spock.org (8.11.4/8.11.4) id f72Ncu017920 for hackers@freebsd.org; Thu, 2 Aug 2001 19:38:56 -0400 (EDT) (envelope-from jon) Date: Thu, 2 Aug 2001 19:38:55 -0400 From: Jonathan Chen To: hackers@freebsd.org Subject: mtree exit code [pr:28424] Message-ID: <20010802193855.A17850@vulcans.dynamic.spock.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Been trying to close some PR's, but I'm not so sure about this one. According to the man page, mtree is supposed to return an exit code of 2 when "the file hierarchy did not match the specification". However, mtree does not return an exit code of 2 when a file/directory is missing. OpenBSD exhibits the same behavior. My question -- is the man page or the program wrong? Is there some standard (POSIX perhaps?) that specifies how mtree should behave? And if its behavior us indeed changed, would anything break? -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 16:43: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ualjuarez.elrancho.com.mx (unknown [200.23.18.58]) by hub.freebsd.org (Postfix) with ESMTP id 4AACF37B406 for ; Thu, 2 Aug 2001 16:40:50 -0700 (PDT) (envelope-from promo@elrancho.com.mx) Received: from 200 [148.243.115.100] by ualjuarez.elrancho.com.mx (SMTPD32-6.05) id A0B6DA0216; Thu, 02 Aug 2001 18:41:10 +0100 From: Fre nights for you. To: Subject: You have WON your FREE nights!!! Mime-Version: 1.0 Content-Type: text/html; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Reply-To: promo@elrancho.com.mx X-Mailer: MailList Express 3.70, Internet-Soft.Com Message-Id: <200108021825.23w9r9A@www.elrancho.com.mx> Date: Thu, 2 Aug 2001 18:41:17 +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG =0D=0A=0D=0A=0D=0A=0D=0A=20=20= =0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20

=0D=0A=20=20=20=20=20=20=  

=0D=0A=20=20=20=20=20=20English =0D=0A=20=20= =20=20=20=20Espa=F1ol=0D=0A=20= =20=0D=0A=0D=0A

=0D=0A=0D=0A=20=20
=0D=0A=20=20=0D=0A=20=20= =20=20=0D=0A=20=20=20=20=20=20
=0D=0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20<= span=20style=3D"background-color:=20#FFFFFF">=0D=0A=20=20=20=20=20=20=20=20Escape=0D=0A=20= =20=20=20=20=20=20=20to=20Paradise...!=0D=0A=20=20=20=20=20=20= =20=20

=0D=0A=20=20=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20= =20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20El=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20=20= =20Rancho=20Villas=0D=0A=20=20=20=20=20=20=20=20=20=20<= /center>=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20= =20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20
=0D=0A=20=20=20= =20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20= =20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20<= font=20color=3D"#FFFFFF"=20face=3D"Arial"=20size=3D"2">Mazatlan,=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20Mexico

=0D=0A=20=20=20=20= =20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=  =0D=0A=20=20=20=20=20= =20
=0D=0A=20=20
=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20= =20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20= =20=0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Dear=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20Friend:

=0D=0A=20=20=20=20=20= =20=20=20=20=20=20=20You've=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20been=20= selected=20to=20take=201=20night=20free=20for=20each=20one=20you=20pay=20= in=20our=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20resort=20at=20Mazatla= n,=20Mexico.

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20That's=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20right=20!!

=0D=0A=20=20=20= =20=20=20=20=20=20=20=20=20Pay=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=201=20night=20and=20get=20another=20one=20F= REE!!

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20This=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20opportunity=20goes=20to=20only=20selec= ted=20people,=20so=20take=20advantage=20of=20this=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20unique=20offer=20you'll=20never=20see=20again=20a=20l= odging=20offer=20like=20this=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20o= ne. =20Your=20next=20vacation=20half=20the=20price!!

=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Why=0D=0A=20=20=20= =20=20=20=20=20=20=20=20=20don't=20you=20take=20a=20rest=20in=20the=20w= onderful=20beach=20of=20Mazatlan,=0D=0A=20=20=20=20=20=20=20=20=20=20=20= =20Mexico. =20This=20is=20your=20opportunity. =20Make=20it=20= possible=20for=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20you.

= =0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20If=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20you=20use=20this=20wonderful=20opportunit= y,=20I'll=20also=20give=20you=20a=2020%=0D=0A=20=20=20=20=20=20=20=20= =20=20=20=20discount=20over=20drinks=20and=20food=20in=20our=20rest= aurant. =20The=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20delicious=20= flavors=20you're=20will=20taste=20there=20are=20going=20to=20be=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20unforgettable,=20believe=20me!<= /p>=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20I=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20send=20you=20our=20addresses=20for=20m= ore=20information,=20just=20in=20case=20you=20are=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20interested=20in=20the=20offer=20I'm=20sending=20you.<= /font>

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20= If=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20you=20want=20to=20use=20this=20b= enefit,=20please=20refer=20the=20code=20below=20to=20make=0D=0A=20=20=20= =20=20=20=20=20=20=20=20=20this=20offer=20valid:

=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20fRpromo0802

=0D=0A=20=20=20=20=20=20=20=20= =20=20=20=20Promotion=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Validity: =20= from=20Aug=2015=20to=20Dec.=2015,=202001;=20excluding=20Thanksgiving=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20week.

=0D=0A=20=20=
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Web=20Sites:
=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20www.elrancho.com.mx

=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20<= a=20href=3D"http://www.elranchovillas.com">www.elranchovillas.com

=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20e-mail:<= font=20color=3D"#0000FF">
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20= info@elrancho.com.mx=0D=0A=20=20=20=20=20=20=20=20= =20=20=0D=0A=20= =20=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20= =20=20=0D=0A=20=20=20=20=20=20= =20=20=20=20=20=20=0D=0A=20=20= =20=20=20=20=20=20=20=20=20=20=0D=0A=20=20
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Reservations:=
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20Tel:=20(1)716-0606
=0D= =0A=20=20=20=20=20=20=20=20=20=20=20=20Fax: =20(1)716-9777
=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20= =20=20=20=20US=20&=20Canada:
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20= 1-888-596-5760
=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20=0D=0A= =20=20=20=20=20=20=20=20=20=20=20=20Mexico:
=0D=0A=20=20=20=20=20=20=20=20=20= =20=20=2001-800-717-1991=0D=0A=20=20=20=20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20
=0D=0A=20=20=20= =20=20=20To=20be=20removed=20= from=20our=20mailing=20list,=0D=0A=20=20=20=20=20=20please=20send=20us=20= a=20blank=20email=20to=20pro= mo@elrancho.com.mx=0D=0A=20=20=20=20=20=20with=20the=20word=20REMOV= E=20in=20the=20subject=20line.

=0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=0D=0A=20=20=0D=0A=20=20
=0D=0A=0D=0A 

=0D=0A&= nbsp;

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A 

=0D=0A=

=0D=0A=0D=0A= =20=20=0D=0A=20=20=20=20
=0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20Escapa=0D=0A=20=20=20=20=20=20al=20pa= ra=EDso...!=0D=0A=20=20=20=20=20=20

= =0D=0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=0D=0A= =20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20 =0D=0A= =20=20=20=20=20=20=20=20=20=20Villas=0D=0A=20=20=20=20=20=20=20= =20=20=20=20=20El=20Rancho=0D=0A=20=20=20=20=20=20=20=20=
=0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20&nbs= p;

=0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20
=0D=0A=20=20=20=20=20=20=0D=0A=20=20=20= =20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20Maz= atl=E1n,=0D=0A=20=20=20=20=20=20=20=20=20=20M=E9xico

=0D=0A= =20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20=20 =0D=0A=20=20=20=20=20=20=20= =20=0D=0A=20=20=20=20=20=20=20= =20=20=20=20=20Hola=0D=0A=20=20=20=20=20=20=20=20=20=20=20=20amigo:=

=0D=0A=20=20=20=20=20=20=20=20=20=20Haz=0D=0A=20=20=20=20=20=20=20= =20=20=20sido=20seleccionado=20para=20llevarte=20una=20noche=20gratis=20= por=20cada=20una=20que=0D=0A=20=20=20=20=20=20=20=20=20=20pagues=20a=20= nuestro=20hotel=20en=20Mazatl=E1n,=20M=E9xico.

=0D=0A=20=20=20= =20=20=20=20=20=20=20Es=0D=0A=20=20=20=20=20=20=20=20=20=20en=20serio=20!!=

=0D=0A=20=20=20=20=20=20=20=20=20=20Paga=0D=0A=20=20=20=20=20=20=20=20=20=201=20noche=20y=20te=20llev= as=20otra=20totalmente=20GRATIS!!

=0D=0A=20=20=20=20=20=20= =20=20=20=20Esta=0D=0A=20=20=20=20=20=20=20=20=20=20oportunidad=20se=20da=20= s=F3lo=20a=20personas=20muy=20selectas,=20asi=20que=20aproveche=0D=0A=20= =20=20=20=20=20=20=20=20=20esta=20=FAnica=20oferta.  =20Jam=E1= s=20vera=20una=20oferta=20igual=20en=20lo=20que=0D=0A=20=20=20=20=20=20= =20=20=20=20a=20alojamiento=20se=20refiere. =20Sus=20pr=F3ximas=20= vacaciones=20por=20la=20mitad=0D=0A=20=20=20=20=20=20=20=20=20=20de=20p= recio!!

=0D=0A=20=20=20=20=20=20=20=20=20=20Por=0D=0A=20=20=20=20=20= =20=20=20=20=20qu=E9=20no=20tomar=20un=20descansito=20en=20las=20maravi= llosas=20playas=20de=20Mazatl=E1n,=0D=0A=20=20=20=20=20=20=20=20=20=20M= =E9xico. =20Esta=20es=20su=20oportunidad. =20H=E1gala=20posib= le=20por=20usted.

=0D=0A=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20= =20=20Es=0D=0A=20=20=20=20=20=20=20=20=20=20m=E1s,=20si=20usted=20hace=20u= so=20de=20esta=20incre=EDble=20oportunidad,=20adem=E1s=20le=0D=0A=20=20= =20=20=20=20=20=20=20=20regalo=20un=2020%=20de=20descuento=20en=20al= imentos=20y=20bebidas=20en=20nuestro=0D=0A=20=20=20=20=20=20=20=20=20= =20restaurante. =20Los=20sabores=20delicios=20que=20probara=20ah=ED= ,=20ser=E1n=0D=0A=20=20=20=20=20=20=20=20=20=20inolvidables,=20cr=E9ame= !

=0D=0A=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20=20=20Para=0D=0A=20=20= =20=20=20=20=20=20=20=20m=E1s=20informaci=F3n,=20le=20mando=20nuestras=20= direcciones=20electr=F3nicas,=20s=F3lo=0D=0A=20=20=20=20=20=20=20=20=20= =20en=20el=20caso=20de=20que=20se=20interese=20por=20la=20oferta=20que=20= le=20he=20hecho.

=0D=0A=20=20=20=20=20=20=20=20=20=20 

=0D=0A=20=20=20=20=20=20=20=20= =20=20Si=0D=0A=20=20=20=20=20=20=20=20=20=20quiere=20usar=20el=20beneficio= ,=20por=20favor=20indique=20el=20codigo=20que=20sigue=20para=0D=0A=20=20= =20=20=20=20=20=20=20=20hacer=20v=E1lida=20esta=20oferta:

=0D= =0A=20=20=20=20=20=20=20=20=20=20<= font=20=0D=0Asize=3D"2">fRpromo0802

=0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20Vigencia=20de=20la=20promoci=F3n:=20de=20Agosto=0D=0A=20=20=20=20=20= =20=20=2015=20a=20Diciembre=2015=20del=202001;=20se=20excluye=20la=20se= mana=20de=20Thanksgiving=20(Festividad=0D=0A=20=20=20=20=20=20=20=20en=20= EE.UU.)

=0D=0A=20=20=20=20=20=20
=0D=0A=20=20=20=20= =20=20=20=20=20=20Web=20Sites:
=0D=0A=20=20=20=20=20=20=20=20=20=20ww= w.elrancho.com.mx

=0D=0A=20=20=20=20=20=20=20=20=20= =20www.elranchovillas.com<= /p>=0D=0A=20=20=20=20=20=20=20=20=20=20e-mail:
=0D=0A=20=20=20=20=20= =20=20=20=20=20info@elrancho.com.mx=0D=0A=20=20=20= =20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=20= =20=0D=0A=20=20=20=20=20=20=20=20= =20=20=0D=0A=20=20=20=20=0D=0A=20=20=20=20=20=20=20=20=20=20Reservaciones:
=0D=0A=20=20=20=20=20= =20=20=20=20=20Tel:=20(1)716-0606
=0D=0A=20=20=20=20=20=20=20=20=20=20= Fax: =20(1)716-9777
=0D=0A=20=20=20=20=20=20=20=20=20=20= =0D=0A=20=20=20=20=20=20=20=20=20=20M=E9xico:
=0D=0A=20=20=20=20=20=20=20=20= =20=2001-800-717-1991
=0D=0A=20=20=20=20=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=20=20=20=20US=20&=20Canada:
=0D=0A=20=20=20=20=20=20=20= =20=20=201-888-596-5760=0D=0A=20=20=20=20=20=20=0D= =0A=20=20=20=20=20=20=0D=0A=20=20=20=20<= font=20size=3D"1">Para=20ser=20removido=20de=20nuestra=20lista=20de=0D=0A= =20=20=20=20correo,=20por=20favor=20env=EDenos=20un=20email=20en=20blan= co=20a=20la=20siguiente=20direcci=F3n=0D=0A=20=20=20=20electr=F3nica=20= :=20promo@elrancho.com.mx,=0D=0A=20=20=20=20con=20la=20palabra=20REMOVE=20en=20la=20linea=20de=20= Asunto=20(subject).

=0D=0A=20=20=20=20=0D=0A=20=20=0D= =0A=0D=0A=0D=0A=0D=0A=0D=0AThe=20message=20sent=20= by=20MailList=20Express=203.70=20=20=20Registered=20Version=20(Download= =20from=20http://Internet-Soft.com)=0D=0A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 17:34:40 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id 5ECFB37B401 for ; Thu, 2 Aug 2001 17:34:36 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 26A5A4B3; Fri, 3 Aug 2001 01:34:32 +0100 (BST) Date: Fri, 3 Aug 2001 01:34:32 +0100 From: Josef Karthauser To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: a little O/T, but D.V.D. drives&freeBSD Message-ID: <20010803013432.D733@tao.org.uk> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="hoZxPH4CaxYzWscb" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Thu, Aug 02, 2001 at 05:57:53PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --hoZxPH4CaxYzWscb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 02, 2001 at 05:57:53PM -0700, Julian Elischer wrote: > anyone had success watching a dvd? > (Anyone have the correct components saved away somewhere?) >=20 > just got a drive and would like to test it.. >=20 > :-) With that Matrix DVD that you produced at FreeBSDCon? :) Joe --hoZxPH4CaxYzWscb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjtp8ZcACgkQXVIcjOaxUBa6IwCfXTamfkVYnTsYUPPHKLWQIU7x PkEAnj8EFrJz3upx3SBBqAoTgJ5ajyrp =dm1G -----END PGP SIGNATURE----- --hoZxPH4CaxYzWscb-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 17:35:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp4ve.mailsrvcs.net (smtp4vepub.gte.net [206.46.170.25]) by hub.freebsd.org (Postfix) with ESMTP id 0461537B401 for ; Thu, 2 Aug 2001 17:35:38 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-40.nnj.dialup.bellatlantic.net [151.198.135.40]) by smtp4ve.mailsrvcs.net (8.9.1/8.9.1) with ESMTP id AAA61216444; Fri, 3 Aug 2001 00:35:26 GMT Message-ID: <3B69F1CD.F8798A3E@bellatlantic.net> Date: Thu, 02 Aug 2001 20:35:25 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: tlambert2@mindspring.com Cc: craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: <002701c11aed$ae1b98a0$051a0a0a@fd.com> <3B68F190.AB04ACB3@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > This basically means that the memory is useless as a DMA target > or source for disk controllers or gigabit ethernet cards, and is > pretty useless for swap, if you ever have to copy from one section > to another (e.g. for IPC, SYSV shared memory, mmap'ed files, VM, > or buffer cache, etc.). For the PCI cards supporting the 64-bit addresses you can. (Note that in PCI support of the 64-bit bus is independent of the 64-bit address space, the 64-bit addresses can be multiplexed over a physically 32-bit bus). -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 17:43:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts6-srv.bellnexxia.net (tomts6.bellnexxia.net [209.226.175.26]) by hub.freebsd.org (Postfix) with ESMTP id BEC4537B406 for ; Thu, 2 Aug 2001 17:43:01 -0700 (PDT) (envelope-from dp@penix.org) Received: from penix.org ([65.92.121.134]) by tomts6-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010803004300.BVE20780.tomts6-srv.bellnexxia.net@penix.org>; Thu, 2 Aug 2001 20:43:00 -0400 Message-ID: <3B69BEF9.2010605@penix.org> Date: Thu, 02 Aug 2001 20:58:33 +0000 From: Paul Halliday User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.2) Gecko/20010722 X-Accept-Language: en-us MIME-Version: 1.0 To: Julian Elischer Cc: hackers@FreeBSD.ORG Subject: Re: a little O/T, but D.V.D. drives&freeBSD References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > anyone had success watching a dvd? > (Anyone have the correct components saved away somewhere?) > > just got a drive and would like to test it.. > > :-) > Xine appears to work ok for me. /usr/ports/graphics/xine > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > > -- Paul H. ___________________ http://dp.penix.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 17:46:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id AA18337B401 for ; Thu, 2 Aug 2001 17:46:38 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id TAA48446; Thu, 2 Aug 2001 19:58:44 -0700 (PDT) Date: Thu, 2 Aug 2001 19:58:43 -0700 (PDT) From: Julian Elischer To: Josef Karthauser Cc: hackers@freebsd.org Subject: Re: a little O/T, but D.V.D. drives&freeBSD In-Reply-To: <20010803013432.D733@tao.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ha! no, I just got my first DVD drive for my dell and I want to see if I can look at a dvd on it.. but All the DVD howto's for FreeBSD seem to be dead links. One just says "The ioctls are now in -current" and seems to assume that that is all the information I need to play a DVD (!?) Other information such as "how to play the video stream" and how to plug the descrambler into the stream etc. might be more useful.. On Fri, 3 Aug 2001, Josef Karthauser wrote: > On Thu, Aug 02, 2001 at 05:57:53PM -0700, Julian Elischer wrote: > > anyone had success watching a dvd? > > (Anyone have the correct components saved away somewhere?) > > > > just got a drive and would like to test it.. > > > > :-) > > With that Matrix DVD that you produced at FreeBSDCon? :) > > Joe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 17:56:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id B33EB37B401 for ; Thu, 2 Aug 2001 17:56:48 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id 2E23F571; Fri, 3 Aug 2001 01:56:44 +0100 (BST) Date: Fri, 3 Aug 2001 01:56:44 +0100 From: Josef Karthauser To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: a little O/T, but D.V.D. drives&freeBSD Message-ID: <20010803015643.E733@tao.org.uk> References: <20010803013432.D733@tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wTWi5aaYRw9ix9vO" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from julian@elischer.org on Thu, Aug 02, 2001 at 07:58:43PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wTWi5aaYRw9ix9vO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 02, 2001 at 07:58:43PM -0700, Julian Elischer wrote: > ha! >=20 > no, I just got my first DVD drive for my dell and I=20 > want to see if I can look at a dvd on it.. > but All the DVD howto's for FreeBSD seem to be dead links. >=20 > One just says "The ioctls are now in -current" > and seems to assume that that is all the information I need > to play a DVD (!?) >=20 > Other information such as > "how to play the video stream" > and how to plug the descrambler into the stream > etc. might be more useful.. There was a thread on the -stable list about this just recently. The first post was on the 28th July, subject line: 'Re: Watching DVD's in -stable' Joe --wTWi5aaYRw9ix9vO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjtp9ssACgkQXVIcjOaxUBbctwCgxBjOYIaoAUWMbNeZli2cTKUn GRgAoLR1YmJmUWpLP5n4j3CB5fITa/rB =DSo6 -----END PGP SIGNATURE----- --wTWi5aaYRw9ix9vO-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 18: 4:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp6ve.mailsrvcs.net (smtp6vepub.gte.net [206.46.170.27]) by hub.freebsd.org (Postfix) with ESMTP id 9BA1437B401 for ; Thu, 2 Aug 2001 18:04:39 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-104.nnj.dialup.bellatlantic.net [151.198.135.104]) by smtp6ve.mailsrvcs.net (8.9.1/8.9.1) with ESMTP id BAA53503907; Fri, 3 Aug 2001 01:04:18 GMT Message-ID: <3B69F891.3492FA21@bellatlantic.net> Date: Thu, 02 Aug 2001 21:04:17 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: en, ru MIME-Version: 1.0 To: tlambert2@mindspring.com Cc: Rik van Riel , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: <3B6933F0.FC88449A@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > > Rik van Riel wrote: > > > > > Only the FreeBSD memory management subsystem doesn't > > > > support it (yet?). > > > > > > It's not a question of "supporting it", it's a question of > > > whether or not it's a useful idea at all. > > > > > I have yet to see one person using it for anything. So far, > > > it is nothing more than marketing fodder: I haven't seen one > > > motherboard capable of more than 4G worth of SIMMs. Every box based on the Intel Saber board is capable of up to 16G. > > I've seen a bunch of the machines. They're rather > > popular with the database folks. > > Name an OS that supports this; more than likely, you will > have to appeal to a purpose built embedded system. UnixWare (A.K.A. OpenUNIX). As far as I understand, Oracle maps in the pieces of SGA as it needs them, keeping the total mapped size under 3G. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 19:35:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by hub.freebsd.org (Postfix) with ESMTP id 793FB37B405 for ; Thu, 2 Aug 2001 19:35:08 -0700 (PDT) (envelope-from bicknell@ussenterprise.ufp.org) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.11.1/8.11.1) id f732Z7g28382 for freebsd-hackers@FreeBSD.ORG; Thu, 2 Aug 2001 22:35:07 -0400 (EDT) (envelope-from bicknell) Date: Thu, 2 Aug 2001 22:34:16 -0400 From: Leo Bicknell To: freebsd-hackers@FreeBSD.ORG Subject: Re: 303,000 routes in kernel Message-ID: <20010802223416.B27772@ussenterprise.ufp.org> Mail-Followup-To: Leo Bicknell , freebsd-hackers@FreeBSD.ORG References: <3B69CE3F.1BCCB280@telehouse.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B69CE3F.1BCCB280@telehouse.ch>; from oppermann@telehouse.ch on Fri, Aug 03, 2001 at 12:03:43AM +0200 Organization: United Federation of Planets Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The box does have a default route, and is not getting proxy arps from the next hop router, right? -- Leo Bicknell - bicknell@ufp.org Systems Engineer - Internetworking Engineer - CCIE 3440 Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 19:40:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.mediadesign.nl (md2.mediadesign.nl [212.19.205.67]) by hub.freebsd.org (Postfix) with SMTP id EE97A37B416 for ; Thu, 2 Aug 2001 19:40:47 -0700 (PDT) (envelope-from alson@mediadesign.nl) Received: (qmail 30044 invoked by uid 1002); 3 Aug 2001 02:40:31 -0000 Date: Fri, 3 Aug 2001 04:40:31 +0200 From: Alson van der Meulen To: freebsd-hackers@FreeBSD.ORG Subject: Re: 303,000 routes in kernel Message-ID: <20010803044031.A21267@md2.mediadesign.nl> Mail-Followup-To: freebsd-hackers@FreeBSD.ORG References: <3B69CE3F.1BCCB280@telehouse.ch> <20010802223416.B27772@ussenterprise.ufp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010802223416.B27772@ussenterprise.ufp.org> User-Agent: Mutt/1.3.18i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 02, 2001 at 10:34:16PM -0400, Leo Bicknell wrote: > > The box does have a default route, and is not getting proxy > arps from the next hop router, right? route add default -cloning would also cause this behavior, guess you don't do that either :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 19:43:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dandelion.geeksimplex.org (cc53440-a.catv1.md.home.com [24.18.90.197]) by hub.freebsd.org (Postfix) with ESMTP id BD33137B403 for ; Thu, 2 Aug 2001 19:43:33 -0700 (PDT) (envelope-from icognito@geeksimplex.org) Received: from icognito by dandelion.geeksimplex.org with local (Exim 3.31 #1 (Debian)) id 15SUw0-00060m-00 for ; Thu, 02 Aug 2001 22:43:32 -0400 Date: Thu, 2 Aug 2001 22:43:31 -0400 From: Gabriel Rocha To: hackers@freebsd.org Subject: Re: a little O/T, but D.V.D. drives&freeBSD Message-ID: <20010802224331.A22714@geeksimplex.org> Mail-Followup-To: hackers@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.20i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ,----[ On Thu, Aug 02, at 05:57PM, Julian Elischer wrote: ]-------------- | anyone had success watching a dvd? `----[ End Quote ]--------------------------- ok, first and foremost, please, anyone else replying, reply to the list and not to me and please dont cc me, i am on the list. (i have to, i got a LOT of replies far after my answer was achieved last time) anyway, vlc is what you want, it works decently if you have a good video card, it simply reboots my -current laptop, so your milleage may vary, but there are numerous reports of successful usage. good luck. --gabe -- "It's not brave if you're not scared." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 21:57:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id DF0A337B403 for ; Thu, 2 Aug 2001 21:57:13 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id VAA11736; Thu, 2 Aug 2001 21:56:43 -0700 (PDT) Message-ID: <3B6A2F33.88499A73@mindspring.com> Date: Thu, 02 Aug 2001 21:57:23 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: mark tinguely Cc: culverk@wam.umd.edu, riel@conectiva.com.br, craiglei@pasia.com.cn, freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: <200108021414.f72EEBS78044@web.cs.ndsu.nodak.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG mark tinguely wrote: > > Also, the PIII CAN'T natively support more than 4GB of ram. If a > > particular PIII motherboard supports this, then it's using some kind of > > wierd chipset that allows this to happen. 4GB is the limit with a 32 bit > > chip I believe; and the PIII is a 32-bit chip. > > Since the Pentium Pro processor, the Intel chipsets support a > physical address extension (PAE) which has 4 extra addressing > bits, and a third level of page table indirection called the > page-directory-pointer-table base address field. Bit 5 of control register 4, and then it uses the top 27 bits of control register 3 to select a 32 byte aligned region in the lower 4G. It also changes the PSE bit to refer to 2M instead of 4M pages, so your would needto DISABLE_PSE, or the FreeBSD kernel would freak when it enabled the "4M" page on the kernel itself. Then the high 4 bits are used to pick a pointer entry (which is effectively a software segment register select, for all practical purposes), giving you 64G of addressable space, in chunks of 4G at a time. Practically, you end up having to overlap this, which tends to cut you down to 32G. > The addressing use 64 bits for a memory pointer and the additional > page indirection add to the overhead. The stickler is the MMU is > still 32 bits. This means the PAE must segment the 64GB space into > 4GB segments or 4 1GB segments. The OS must manage which pages are > viewable to the process at this time. Not only that: you reload CR3, and none of these pages are really global, so you can't set the PG_G bit, and so you get the full TLB shootdown on everything, so a segment switch ends up shooting _everything_ down. > There is a third mode of addressing using 2MB pages (simular to the > 4MB page addressing mode for the 32 bit addressing scheme) that will > only give a process access to 4GB of memory (not segmentable to > a larger space, but can address physical memory located above the 4GB > address). Not really useful, unless you go back to a task gate, which itself will limit you to 1024 things; with code + data, you end up halving that to 512, minus overhead drops it to 510, so you end up with a limitation on number of processes. You could do all the switching manually, but it is very, very hard. Further, you can write off shared memory and shared libraries, and some types of IPC (e.g. descriptor passing), unless you want to rework everything. IMO, the resulting kernel would be so slow as to prevent the changes from being useful, due to their expense. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 21:59:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 6662A37B405 for ; Thu, 2 Aug 2001 21:59:45 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id VAA18167; Thu, 2 Aug 2001 21:58:44 -0700 (PDT) Message-ID: <3B6A2FAC.28F2F959@mindspring.com> Date: Thu, 02 Aug 2001 21:59:24 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: mark tinguely , culverk@wam.umd.edu, craiglei@pasia.com.cn, freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: > > The addressing use 64 bits for a memory pointer and the additional > > page indirection add to the overhead. The stickler is the MMU is > > still 32 bits. This means the PAE must segment the 64GB space into > > 4GB segments or 4 1GB segments. The OS must manage which pages are > > viewable to the process at this time. > > There's a better option. The application does this stuff > itself, by mapping and unmapping SHM segments. Not surprisingly, this doesn't work if your application is the kernel, and the data is mbufs, open file structures, sockets, tcpcb's, or inpcb's. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22: 8:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 3BC6537B401; Thu, 2 Aug 2001 22:08:18 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA20649; Thu, 2 Aug 2001 22:08:16 -0700 (PDT) Message-ID: <3B6A31E8.836122DA@mindspring.com> Date: Thu, 02 Aug 2001 22:08:56 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: freebsd-hackers@FreeBSD.org, craig Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > Err. hang on. This has zero to do with segmentation. Zip, nada. > PAE is completely in the paging side of things. No matter what > fun games you play with segmentation, you still end up with a > 32-bit linear address that gets handed off to the paging translations. > PAE just allows you to use more backing store across multiple > processes, but you are still stuck with a 4gb virtual address > space for processes. (Including KVM) IMO, the 4 bit selector "register" is the moral equivalent of a segment register. Personally, I think it's much less useful to run the kernel out of KVA space, than it is to have more memory available to the kernel for things like mbufs, so I'm not really very interested in trying to raise the per process address space limits this way. You could actually get 4G for the kernel and 4G for processes using this, but you would only need two "segments" to make this happen; mapping the other stuff at the same time makes little sense: you just map a window on it to implement region overlays for user or kernel data paging. Given the compiler tools we have, this still limits you to using only 4G in a given VA space, unless you did something evil, like add "HLOCK/HUNLOCK", etc.. > > But to directly answer your question: by rewriting much of the > > low core virtual memory and page mapping handling code to know > > about segmentation. > > No, to rewrite said code to handle a different type of page table > structure. Virtual table structure/segements: same difference: I'm now wdoing in software what I bought hardware to get away from having to do in software. Given the vastly simplified page management in Linux, I could see how there wouldn't really be a big performance loss over the way Linux does things without this, so it might be OK, so long as there were no shared memory regions, semaphores, etc.. That really makes it pretty useless. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:15:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 2A42237B401 for ; Thu, 2 Aug 2001 22:15:47 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA11216; Thu, 2 Aug 2001 22:15:00 -0700 (PDT) Message-ID: <3B6A337B.5A81232B@mindspring.com> Date: Thu, 02 Aug 2001 22:15:39 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Charles Randall Cc: Rik van Riel , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: <5FE9B713CCCDD311A03400508B8B30130828F234@bdr-xcln.corp.matchlogic.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Charles Randall wrote: > > From: Terry Lambert [mailto:tlambert2@mindspring.com] > >I have yet to see one person using it for anything. So far, > >it is nothing more than marketing fodder: I haven't seen one > >motherboard capable of more than 4G worth of SIMMs. > > The Dell PowerEdge 6450 supports 8 GB of RAM. > > http://www.dell.com/us/en/biz/products/model_pedge_pedge_6400.htm > > If I understand your comments in a few follow-up messages > correctly you're saying that this effort may be better spent > by working on an IA-64 port and making it support large memory > configurations? The IA64 intrinsically supports a physical address space of 2^64, so an address space of 2^36 vs. 2^32 is spectacularly unimpressive. > Can you elaborate? Yeah, the overhead in doing this will up the CPU utilization to the point where it becomes fairly useless to do the swapping to and from above 4G, vs. just swapping normally. The costs involved in doing DMA to/from the memory region above 4G will be incredible, unless the address space is both exported, and known, to the PCI bus; even then, it could only work for 64 bit cards, since 32 bith cards will only be able to address the first 4G of physical memory. I can think of one or two uses for the memory, assuming the ability to DMA into and out of it with a 64 bit card, and the ability to shove a 1G or 2G window around in it so the kernel can get at the memory when it needs to, but the overhead seems to me to be high enough that you are better off buying a Sibytes card, running NetBSD on the MIPS processors on the thing, plugging in 16G of RAM, and calling your PC a "control processor". -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:19:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 00C2137B401 for ; Thu, 2 Aug 2001 22:19:34 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA21148; Thu, 2 Aug 2001 22:18:23 -0700 (PDT) Message-ID: <3B6A3447.BCA49795@mindspring.com> Date: Thu, 02 Aug 2001 22:19:03 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: Charles Randall , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: > > >I have yet to see one person using it for anything. So far, > > >it is nothing more than marketing fodder: I haven't seen one > > >motherboard capable of more than 4G worth of SIMMs. > > > > The Dell PowerEdge 6450 supports 8 GB of RAM. > > > > http://www.dell.com/us/en/biz/products/model_pedge_pedge_6400.htm > > It's all a trick, they don't really exist. After all, > why would people ever shell out the money for one of > these useless beasts that won't be running until ia64 > has gotten cheaper than these machines ? I can buy an IA64 box for US$7000; it can address much more memory than this thing, and the overall cost is probably less. In IA32 mode, it can operate with the PAE, so you can keep your crufty "32 bit using 36 bit" around, too, if you are too lazy to do the port. This is seeming more and more like a boondoggle to get FreeBSD to waste its time slowing its default behaviour down so that some small number of incredibly bizarre applications can pretend their address space is bigger than it really is... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:21: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id B61C637B401; Thu, 2 Aug 2001 22:21:05 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by avocet.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA28890; Thu, 2 Aug 2001 22:20:58 -0700 (PDT) Message-ID: <3B6A34E2.96498938@mindspring.com> Date: Thu, 02 Aug 2001 22:21:38 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: Kenneth Wayne Culver , John Baldwin , freebsd-hackers@FreeBSD.org, craig Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: > > BUT, don't the motherboards also have to support this? And isn't > > it only supported through some wierd segmentation thing? > > Yes, the mainboard needs to support the memory. > > No, there is no weird segmentation thing, at least > not visible from software. Last time I looked, the kernel was software... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:26: 6 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 3F91B37B405 for ; Thu, 2 Aug 2001 22:26:04 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA00525; Thu, 2 Aug 2001 22:25:17 -0700 (PDT) Message-ID: <3B6A35E4.626983E@mindspring.com> Date: Thu, 02 Aug 2001 22:25:56 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Rik van Riel , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > Name an OS that supports this; more than likely, you will > > have to appeal to a purpose built embedded system. > > errr, linux? Original poster said he was working on it for Linux, which means it's not done, which means "not Linux". FWIW, on the "Linux has it, so FreeBSD should have it" arguments: "If all your friends jumped off a cliff..." -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:28:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id B17FF37B401; Thu, 2 Aug 2001 22:28:47 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA10534; Thu, 2 Aug 2001 22:28:23 -0700 (PDT) Message-ID: <3B6A369F.C35B7B03@mindspring.com> Date: Thu, 02 Aug 2001 22:29:03 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Kenneth Wayne Culver , John Baldwin , freebsd-hackers@FreeBSD.org, craig , Rik van Riel Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > No > The space is linear in physical space and if you have PCI/64 > capable devices they can access it all too. > > (In fact 64 bit addresses have been supported even in 32 bit wide PCI > since day 1). It's been my experience that the TIGON cards take a 32 bit DMA target address, not a 64 bit DMA target address, and that the 54 bit width was only used for the data transfer, not for the address offset. Correct me if I'm wrong, and 64 bit PCI cards can in fact DMA at offsets above 4G, in the physical address space... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:34: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 968A737B405; Thu, 2 Aug 2001 22:34:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.244.104.136.Dial1.SanJose1.Level3.net [209.244.104.136]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA26931; Thu, 2 Aug 2001 22:33:41 -0700 (PDT) Message-ID: <3B6A37DC.7F9171BB@mindspring.com> Date: Thu, 02 Aug 2001 22:34:20 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Nate Dannenberg Cc: John Baldwin , hackers@FreeBSD.ORG Subject: Re: PR 25958 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Nate Dannenberg wrote: > I'd be glad to, however I no longer run FreeBSD. I have since switched to > Linux. [ ... ] > Not being much of a C programmer > anymore I can't really say for certain though :) Are these two statements related by cause and effect? 8-) 8-) -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 2 22:51:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from randallkunkee.com (adsl-65-65-19-145.dsl.hstntx.swbell.net [65.65.19.145]) by hub.freebsd.org (Postfix) with ESMTP id C7F9237B405 for ; Thu, 2 Aug 2001 22:51:34 -0700 (PDT) (envelope-from randy@randallkunkee.com) Received: from randallkunkee.com (localhost [127.0.0.1]) by randallkunkee.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id f735pfmu025642 for ; Fri, 3 Aug 2001 00:51:41 -0500 (CDT) Message-ID: <3B6A3BEC.831D0D56@randallkunkee.com> Date: Fri, 03 Aug 2001 00:51:41 -0500 From: Randy Kunkee X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: cvsup updater failed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Updating collection ports-all/cvs Updater failed: /usr/ports/www/jakarta-tomcat/files/#cvs.cvsup-25588.1: Cannot create: Not a directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 0:18: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gekko.i-clue.de (server.ms-agentur.de [62.153.134.194]) by hub.freebsd.org (Postfix) with ESMTP id 06E8B37B403 for ; Fri, 3 Aug 2001 00:18:02 -0700 (PDT) (envelope-from so@server.i-clue.de) Received: from i-clue.de (automatix.i-clue.de [192.168.0.112]) by gekko.i-clue.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id JAA32124; Fri, 3 Aug 2001 09:26:15 +0200 Message-ID: <3B6A508D.2FCBB24F@i-clue.de> Date: Fri, 03 Aug 2001 09:19:41 +0200 From: Christoph Sold Reply-To: so@server.i-clue.de X-Mailer: Mozilla 4.78 [en] (WinNT; U) X-Accept-Language: de,en MIME-Version: 1.0 To: Randy Kunkee Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: cvsup updater failed References: <3B6A3BEC.831D0D56@randallkunkee.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Randy Kunkee wrote: > > Updating collection ports-all/cvs > Updater failed: /usr/ports/www/jakarta-tomcat/files/#cvs.cvsup-25588.1: > Cannot create: Not a directory - Delete the /usr/ports/www/jakarta-tomcat directory - Either delete /usr/sup/ports-*, or remove all references to jakarta-tomcat from all the checkouts.cvs:. files. - CVSup again - update the CVSup port (not the CVSup-bin port!) This was a bug in CVSup triggered by some obscure change in the tomcat port. It has been fixed, after updating CVSup and following the above procedure, the problem will be gone for good. HTH -Chrisotph Sold To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 0:25:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 28DA637B405 for ; Fri, 3 Aug 2001 00:25:34 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f737PWF02314; Fri, 3 Aug 2001 01:25:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f737PWH62521; Fri, 3 Aug 2001 01:25:32 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108030725.f737PWH62521@harmony.village.org> To: lists Subject: Re: Wierd IRQ Routing issues Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Aug 2001 22:01:25 +0200." References: Date: Fri, 03 Aug 2001 01:25:32 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message lists writes: : However, on my other pc with an identical setup, when trying to assign : pcic irq it does this: (from dmesg): How identical? Is the BIOS the same? : pci_cfgintr_search: linked (3) to configured irq 10 at 0:9:0 : pci_cfgintr: 0:10 INTA routed to irq 10 Looks good to me. : Now for some reason I have it in my head that that irq routing is broken, Maybe. Is this the wi0 timeout machine? : Any ideas would be MUCH appreciated I'm not sure what's going on here. :-( Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 0:30:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 840FE37B406 for ; Fri, 3 Aug 2001 00:30:42 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f737UfF02331; Fri, 3 Aug 2001 01:30:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f737UfH62560; Fri, 3 Aug 2001 01:30:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108030730.f737UfH62560@harmony.village.org> To: lists Subject: Re: NewCard / pccbb Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Aug 2001 14:53:20 +0200." References: Date: Fri, 03 Aug 2001 01:30:41 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : wi0: at port 0x100-0x13f irq 3 function 0 config 1 on : pccard0 : : Could that irq sharing be breaking something? It could also be that the pccard interrupt routing code (in src/sys/dev/pccard/pccard.c) is busted. If you look at it: static void pccard_intr(void *arg) { struct pccard_softc *sc = (struct pccard_softc *) arg; struct pccard_function *pf; STAILQ_FOREACH(pf, &sc->card.pf_head, pf_list) { if (pf->intr_handler != NULL) { int reg = pccard_ccr_read(pf, PCCARD_CCR_STATUS); if (reg & PCCARD_CCR_STATUS_INTR) { pccard_ccr_write(pf, PCCARD_CCR_STATUS, reg & ~PCCARD_CCR_STATUS_INTR); pf->intr_handler(pf->intr_handler_arg); } } } } But if you look at the pccard stnadard, you'll find that the PCCARD_CCR_STATUS_INTR bit is only defined for MFC cards. So, try the following: static void pccard_intr(void *arg) { struct pccard_softc *sc = (struct pccard_softc *) arg; struct pccard_function *pf; STAILQ_FOREACH(pf, &sc->card.pf_head, pf_list) { if (pf->intr_handler != NULL) { pf->intr_handler(pf->intr_handler_arg); } } } in its place. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 0:33:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 458A637B403 for ; Fri, 3 Aug 2001 00:33:39 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f737XcF02342; Fri, 3 Aug 2001 01:33:38 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f737XbH62582; Fri, 3 Aug 2001 01:33:37 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108030733.f737XbH62582@harmony.village.org> To: Randy Kunkee Subject: Re: cvsup updater failed Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 03 Aug 2001 00:51:41 CDT." <3B6A3BEC.831D0D56@randallkunkee.com> References: <3B6A3BEC.831D0D56@randallkunkee.com> Date: Fri, 03 Aug 2001 01:33:37 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3B6A3BEC.831D0D56@randallkunkee.com> Randy Kunkee writes: : Updating collection ports-all/cvs : Updater failed: /usr/ports/www/jakarta-tomcat/files/#cvs.cvsup-25588.1: : Cannot create: Not a directory Read UPDATING. It contains useful information about this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 0:48:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 5D56D37B405 for ; Fri, 3 Aug 2001 00:48:07 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f737lsf42211; Fri, 3 Aug 2001 09:47:55 +0200 (SAST) (envelope-from lists@security.za.net) Date: Fri, 3 Aug 2001 09:47:54 +0200 (SAST) From: lists To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Wierd IRQ Routing issues In-Reply-To: <200108030725.f737PWH62521@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bios is different, everything else is the same, about to go and swap out the motherboard to something that does work due to desperation :) Yeah thats the wi0 timeout machine, the other machine doesnt do a pci_cfgintr_search or an irq routing, it does a hard assignment by the looks of things, not sure why that is Andrew On Fri, 3 Aug 2001, Warner Losh wrote: > In message lists writes: > : However, on my other pc with an identical setup, when trying to assign > : pcic irq it does this: (from dmesg): > > How identical? Is the BIOS the same? > > : pci_cfgintr_search: linked (3) to configured irq 10 at 0:9:0 > : pci_cfgintr: 0:10 INTA routed to irq 10 > > Looks good to me. > > : Now for some reason I have it in my head that that irq routing is broken, > > Maybe. Is this the wi0 timeout machine? > > : Any ideas would be MUCH appreciated > > I'm not sure what's going on here. :-( > > Warner > > 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 Aug 3 1: 8:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 690A137B405 for ; Fri, 3 Aug 2001 01:08:55 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f735P4C02496; Thu, 2 Aug 2001 22:25:14 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030525.f735P4C02496@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: tlambert2@mindspring.com Cc: Charles Randall , Rik van Riel , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? In-reply-to: Your message of "Thu, 02 Aug 2001 22:15:39 PDT." <3B6A337B.5A81232B@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Aug 2001 22:25:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > The costs involved in doing DMA to/from the memory region > above 4G will be incredible, unless the address space is > both exported, and known, to the PCI bus; even then, it > could only work for 64 bit cards, since 32 bith cards will > only be able to address the first 4G of physical memory. Actually, most server-class hardware these days will have no trouble with DMA above 4GB; even the 32-bit devices support DAC. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 1:10:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 25CBF37B406 for ; Fri, 3 Aug 2001 01:10:43 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f733lIC01436; Thu, 2 Aug 2001 20:47:38 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030347.f733lIC01436@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Page Coloring In-reply-to: Your message of "Thu, 02 Aug 2001 12:03:35 MDT." <20010802120335.A11520@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Aug 2001 20:47:18 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If I added this to a man page would I be telling the truth :). > > Note, these are my notes and not the exact text that I would > add, and I have not bother with anything to do with object > coloring etc. I just want to make sure I've got this part > down. It looks about right, but page colouring is pointless unless and until we can determine the processor cache characteristics at runtime. Which we can't. Plus the code hardcodes all the relevant numbers. The code needs fixing as well as documenting. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 1:11:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 177FB37B406; Fri, 3 Aug 2001 01:11:08 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f733q9C01482; Thu, 2 Aug 2001 20:52:10 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030352.f733q9C01482@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kenneth Wayne Culver Cc: Julian Elischer , John Baldwin , freebsd-hackers@FreeBSD.ORG, craig , Terry Lambert , Rik van Riel Subject: Re: How to visit physical memory above 4G? In-reply-to: Your message of "Thu, 02 Aug 2001 14:55:28 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Aug 2001 20:52:09 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > No > > The space is linear in physical space and if you have PCI/64 > > capable devices they can access it all too. > > > > (In fact 64 bit addresses have been supported even in 32 bit wide PCI > > since day 1). > > OK, then what was that whole paging thing everyone was talking about, I > thought that was partially done in hardware on the chipset of the > motherboard... or was that completely in the operating system? Julian is on crack. DAC (Double Address Cycle) is a relatively recent addition to PCI that allows 32-bit cards with 64-bit savvy logic to talk to host memory using 64-bit target addresses. Older systems used a scatter-gather mechanism to present a virtualised view of the system's physical address space to the PCI bus (typically you'll see this in Alpha systems). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 1:23:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id A254237B405 for ; Fri, 3 Aug 2001 01:23:31 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f738NLR43378; Fri, 3 Aug 2001 10:23:21 +0200 (SAST) (envelope-from lists@security.za.net) Date: Fri, 3 Aug 2001 10:23:21 +0200 (SAST) From: lists To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: NewCard / pccbb In-Reply-To: <200108030730.f737UfH62560@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tried the patch, interesting thing, for some reason or other its always routing the IRQ to the same IRQ as the realtek network card I have in here, and with the patch in (before nothing worked at all on the pccbb), now if the network card is in slot0 it doesnt work, and the wavelan does, if the wavelan comes first on the pcibus it doesnt work and the network card does. For some reason it always seems to be trying to share an IRQ between these 2, any reason for this? Andrew On Fri, 3 Aug 2001, Warner Losh wrote: > : wi0: at port 0x100-0x13f irq 3 function 0 config 1 on > : pccard0 > : > : Could that irq sharing be breaking something? > > It could also be that the pccard interrupt routing code (in > src/sys/dev/pccard/pccard.c) is busted. If you look at it: > > static void > pccard_intr(void *arg) > { > struct pccard_softc *sc = (struct pccard_softc *) arg; > struct pccard_function *pf; > STAILQ_FOREACH(pf, &sc->card.pf_head, pf_list) { > if (pf->intr_handler != NULL) { > int reg = pccard_ccr_read(pf, PCCARD_CCR_STATUS); > if (reg & PCCARD_CCR_STATUS_INTR) { > pccard_ccr_write(pf, PCCARD_CCR_STATUS, > reg & ~PCCARD_CCR_STATUS_INTR); > pf->intr_handler(pf->intr_handler_arg); > } > } > } > } > > But if you look at the pccard stnadard, you'll find that the > PCCARD_CCR_STATUS_INTR bit is only defined for MFC cards. So, try the > following: > > static void > pccard_intr(void *arg) > { > struct pccard_softc *sc = (struct pccard_softc *) arg; > struct pccard_function *pf; > STAILQ_FOREACH(pf, &sc->card.pf_head, pf_list) { > if (pf->intr_handler != NULL) { > pf->intr_handler(pf->intr_handler_arg); > } > } > } > > in its place. > > Warner > > 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 Aug 3 1:29:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web5304.mail.yahoo.com (web5304.mail.yahoo.com [216.115.106.113]) by hub.freebsd.org (Postfix) with SMTP id 0A8CE37B407 for ; Fri, 3 Aug 2001 01:29:22 -0700 (PDT) (envelope-from vishubp@yahoo.com) Message-ID: <20010803082921.4234.qmail@web5304.mail.yahoo.com> Received: from [203.200.20.3] by web5304.mail.yahoo.com via HTTP; Fri, 03 Aug 2001 09:29:21 BST Date: Fri, 3 Aug 2001 09:29:21 +0100 (BST) From: =?iso-8859-1?q?vishwanath=20pargaonkar?= Subject: malloc To: tlambert2@mindspring.com, Zhihui Zhang Cc: Bosko Milekic , Alfred Perlstein , vishwanath pargaonkar , freebsd-hackers@FreeBSD.ORG In-Reply-To: <3B632429.D3FA2EB0@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, can anybody tell me in malloc what does third parameter DONTWAIT ,NOWAIT and WAITOK mean? Bcoz i have function being called using timeout.in that function i need to malloc a buffer. can i use WAITOK? please tell me abt this. TIA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 1:29:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web5304.mail.yahoo.com (web5304.mail.yahoo.com [216.115.106.113]) by hub.freebsd.org (Postfix) with SMTP id 08CA837B406 for ; Fri, 3 Aug 2001 01:29:22 -0700 (PDT) (envelope-from vishubp@yahoo.com) Message-ID: <20010803082921.4234.qmail@web5304.mail.yahoo.com> Received: from [203.200.20.3] by web5304.mail.yahoo.com via HTTP; Fri, 03 Aug 2001 09:29:21 BST Date: Fri, 3 Aug 2001 09:29:21 +0100 (BST) From: =?iso-8859-1?q?vishwanath=20pargaonkar?= Subject: malloc To: tlambert2@mindspring.com, Zhihui Zhang Cc: Bosko Milekic , Alfred Perlstein , vishwanath pargaonkar , freebsd-hackers@FreeBSD.ORG In-Reply-To: <3B632429.D3FA2EB0@mindspring.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, can anybody tell me in malloc what does third parameter DONTWAIT ,NOWAIT and WAITOK mean? Bcoz i have function being called using timeout.in that function i need to malloc a buffer. can i use WAITOK? please tell me abt this. TIA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 1:43:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 86BCE37B401 for ; Fri, 3 Aug 2001 01:43:27 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f738jRk01199; Fri, 3 Aug 2001 01:45:31 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108030845.f738jRk01199@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: lists Cc: Warner Losh , freebsd-hackers@FreeBSD.ORG Subject: Re: NewCard / pccbb In-reply-to: Your message of "Fri, 03 Aug 2001 10:23:21 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 01:45:27 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Tried the patch, interesting thing, for some reason or other its always > routing the IRQ to the same IRQ as the realtek network card I have in > here, and with the patch in (before nothing worked at all on the pccbb), > now if the network card is in slot0 it doesnt work, and the wavelan does, > if the wavelan comes first on the pcibus it doesnt work and the network > card does. For some reason it always seems to be trying to share an IRQ > between these 2, any reason for this? Yeah; that seems to be the way your system's interrupt routing is set up. Get http://people.freebsd.org/~msmith/pir.c, build and run it and let's look at the output. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 2: 2:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 09C4437B403 for ; Fri, 3 Aug 2001 02:02:53 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f739J6t03377; Fri, 3 Aug 2001 13:19:06 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108030919.f739J6t03377@bugz.infotecs.ru> Subject: Re: malloc In-Reply-To: <20010803082921.4234.qmail@web5304.mail.yahoo.com> "from vishwanath pargaonkar at Aug 3, 2001 09:29:21 am" To: vishwanath pargaonkar Date: Fri, 3 Aug 2001 13:19:06 +0400 (MSD) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Hi, > can anybody tell me in malloc what does third > parameter > DONTWAIT ,NOWAIT and WAITOK mean? > Bcoz i have function being called using timeout.in > that function i need to malloc a buffer. > can i use WAITOK? > please tell me abt this. I think MALLOC(9) explains this pretty well. Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 2: 8:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dell.dannyland.org (dell.dannyland.org [64.81.36.13]) by hub.freebsd.org (Postfix) with ESMTP id 8A6A137B403 for ; Fri, 3 Aug 2001 02:08:47 -0700 (PDT) (envelope-from dannyman@toldme.com) Received: by dell.dannyland.org (Postfix, from userid 1001) id C31ED5C20; Fri, 3 Aug 2001 02:10:23 -0700 (PDT) Date: Fri, 3 Aug 2001 02:10:23 -0700 From: dannyman To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Softupdate gripe... Message-ID: <20010803021022.H28602@toldme.com> References: <20010730132122.C548@apocalypse.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010730132122.C548@apocalypse.cdsnet.net>; from mrcpu@internetcds.com on Mon, Jul 30, 2001 at 01:21:22PM -0700 X-Loop: djhoward@uiuc.edu Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 30, 2001 at 01:21:22PM -0700, Jaye Mathisen wrote: > > 2 500+GB FS's, both filled completely. > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 524502226 195890 100% /d/d1 > newsfeed-inn# rm -f /d/d?/* As noted elsewhere, this is an inefficient way to remove these files. > newsfeed-inn# ls -lR /d ls -lRa > newsfeed-inn# df ; sleep 30 ; df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 524446754 251362 100% /d/d1 > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 522361778 2336338 100% /d/d1 Two things to note: 1) Are there any open filehandles on these disks? If a process is writing a file, and you remove that file, the disk space is not cleared until the process that had that file open closes it. 2) As noted in other posts, use sync to force the OS to commit changes to the filesystem. > It's been another minute now, and still no blocks freed up on /d/d0. > newsfeed-inn# df ; sleep 120 ; df > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 503964018 20734098 96% /d/d1 > ... > /dev/twed3d 524698116 524697730 386 100% /d/d0 > /dev/twed4d 524698116 493186018 31512098 94% /d/d1 > > Seems like it should round-robin them or something. FWIW, I've noticed that .5TB filesystems can behave pretty slowly. -danny -- http://dannyman.toldme.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 2:33:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bugz.infotecs.ru (bugz.infotecs.ru [195.210.139.22]) by hub.freebsd.org (Postfix) with ESMTP id 1EFFC37B405 for ; Fri, 3 Aug 2001 02:33:38 -0700 (PDT) (envelope-from vel@bugz.infotecs.ru) Received: (from root@localhost) by bugz.infotecs.ru (8.11.1/8.11.1) id f739nrZ03446 for freebsd-hackers@freebsd.org; Fri, 3 Aug 2001 13:49:53 +0400 (MSD) (envelope-from vel) From: "Eugene L. Vorokov" Message-Id: <200108030949.f739nrZ03446@bugz.infotecs.ru> Subject: device i/o question To: freebsd-hackers@freebsd.org Date: Fri, 3 Aug 2001 13:49:53 +0400 (MSD) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I have a module which creates new device for data exchange between user program and a module. I was wondering, if I open the device in userspace and write() some piece of data to it, is it guaranteed that the driver will get this solid piece of data at once, or in certain circumstances it can be split into parts which are passed to the driver as several write events ? Regards, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 2:50: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id E303D37B406; Fri, 3 Aug 2001 02:49:55 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f739ktV45602; Fri, 3 Aug 2001 11:46:55 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f739koY02574; Fri, 3 Aug 2001 11:46:50 +0200 (CEST) Date: Fri, 3 Aug 2001 11:46:49 +0200 From: Bernd Walter To: Andre Oppermann Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel Message-ID: <20010803114648.A2565@cicely20.cicely.de> References: <3B69CE3F.1BCCB280@telehouse.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B69CE3F.1BCCB280@telehouse.ch>; from oppermann@telehouse.ch on Fri, Aug 03, 2001 at 12:03:43AM +0200 X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 03, 2001 at 12:03:43AM +0200, Andre Oppermann wrote: > The problem I've got now is that for every packet I get the kernel is > making one host entry in the routing table. Because of the many UDP > DNS requests from all over the world I've got 303'000 (yes, three- > hundredthreethousand) entries in the kernel routing table which have > not expired yet. So I'm getting error messages like this now: Are you shure that these are not created via redirects when sending the packet? You might try to disable acepting redirects via sysctl and/or setting the routes so that packets have a better chance to be send to the right router. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 4:23:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mtach2.zurich.com (chmail2.zurich.com [195.28.226.82]) by hub.freebsd.org (Postfix) with ESMTP id A849F37B407 for ; Fri, 3 Aug 2001 04:23:27 -0700 (PDT) (envelope-from ullasan.kottummal@uk.zurich.com) Subject: Select call gives EBADF To: freebsd-hackers@freebsd.org X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000 Message-ID: From: "Ullasan Kottummal" Date: Fri, 3 Aug 2001 12:21:42 +0100 X-MIMETrack: Serialize by Router on CHKNH021/Zurich-Internet(Release 5.0.8 |June 18, 2001) at 03.08.2001 13:22:06 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I am using select() call under HP-UX 10.20 for timing on socket. It throws the error EBADF. I don't understand why it happens. The socket is opened successfully before calling the select and the descriptor is valid. I will give the relevant code below. int mask; struct fd_set readmask ; readmask.fds_bits[0] = 0; struct fd_set readfds; int nfound, i; struct timeval timeout; mask = MASK(m_iSocket); readmask.fds_bits[0] |= mask; readfds.fds_bits[0] = readmask.fds_bits[0]; timeout.tv_sec = m_iSelectTimeout; timeout.tv_usec = 0; FD_ZERO(&readfds); if ((nfound = select (SOCKETS, &readfds, 0, 0, &timeout)) == -1) { cerr << "==>Select call failed : " << endl; //Errror checking done ....... ........ } Thanks in advance Regards Ullasan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 5:12:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id F391337B405 for ; Fri, 3 Aug 2001 05:12:29 -0700 (PDT) (envelope-from ticso@mail.cicely.de) Received: from mail.cicely.de (cicely20 [10.1.1.22]) by srv1.cosmo-project.de (8.11.0/8.11.0) with ESMTP id f73CCRV46321 for ; Fri, 3 Aug 2001 14:12:28 +0200 (CEST) Received: (from ticso@localhost) by mail.cicely.de (8.11.0/8.11.0) id f73CCQU03257 for freebsd-hackers@freebsd.org; Fri, 3 Aug 2001 14:12:26 +0200 (CEST) Date: Fri, 3 Aug 2001 14:12:25 +0200 From: Bernd Walter To: freebsd-hackers@freebsd.org Subject: linking WITH -lstdc++ makes executeables smaller? Message-ID: <20010803141225.A3246@cicely20.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: NetBSD cicely20.cicely.de 1.5 sparc Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I used a library which also needed -lstdc++. Now that I did not need them any more I removed them and was surprised that the resulting FreeBSD binary actually got bigger! On NetBSD the binary is slightly smaller as expected. Is there any logical explanation for this phaenomen? ticso@cicely8> cc -O -pipe -g -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type -Wswitch -o cbckd *.o -lm -lstdc++ ticso@cicely8> ls -al cbckd -rwxr-xr-x 1 ticso 1000 204628 Aug 3 14:02 cbckd ticso@cicely8> strip cbckd ticso@cicely8> ls -al cbckd -rwxr-xr-x 1 ticso 1000 41300 Aug 3 14:02 cbckd ticso@cicely8> cc -O -pipe -g -Wall -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Werror -Wreturn-type -Wswitch -o cbckd *.o -lm ticso@cicely8> ls -al cbckd -rwxr-xr-x 1 ticso 1000 228832 Aug 3 14:02 cbckd ticso@cicely8> strip cbckd ticso@cicely8> ls -al cbckd -rwxr-xr-x 1 ticso 1000 59636 Aug 3 14:02 cbckd -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 5:49:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 29CAB37B401; Fri, 3 Aug 2001 05:49:30 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f73CnRX53747; Fri, 3 Aug 2001 14:49:27 +0200 (SAST) (envelope-from lists@security.za.net) Date: Fri, 3 Aug 2001 14:49:27 +0200 (SAST) From: lists To: Mike Smith Cc: Warner Losh , freebsd-hackers@freebsd.org Subject: Re: NewCard / pccbb In-Reply-To: <200108030845.f738jRk01199@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here we go, the output as requested: $PIR table at 0x2812f7c0 version 1.0 PCI interrupt router at 0:3.8 vendor 0x1106 device 0x686 PCI-only interrupts [ ] entry bus slot device 00: 00 00 01 INTA 01 [ 3 4 5 7 9 10 11 12 14 15] INTB 02 [ 3 4 5 7 9 10 11 12 14 15] INTC 03 [ 3 4 5 7 9 10 11 12 14 15] INTD 05 [ 3 4 5 7 9 10 11 12 14 15] 01: 00 00 07 INTA fe [ 14 ] INTB ff [ 15] INTC 03 [ 3 4 5 7 9 10 11 12 14 15] INTD 05 [ 3 4 5 7 9 10 11 12 14 15] 02: 00 01 09 INTA 02 [ 3 4 5 7 9 10 11 12 14 15] INTB 03 [ 3 4 5 7 9 10 11 12 14 15] INTC 05 [ 3 4 5 7 9 10 11 12 14 15] INTD 01 [ 3 4 5 7 9 10 11 12 14 15] 03: 00 02 10 INTA 03 [ 3 4 5 7 9 10 11 12 14 15] INTB 05 [ 3 4 5 7 9 10 11 12 14 15] INTC 01 [ 3 4 5 7 9 10 11 12 14 15] INTD 02 [ 3 4 5 7 9 10 11 12 14 15] 04: 00 03 11 INTA 05 [ 3 4 5 7 9 10 11 12 14 15] INTB 01 [ 3 4 5 7 9 10 11 12 14 15] INTC 02 [ 3 4 5 7 9 10 11 12 14 15] INTD 03 [ 3 4 5 7 9 10 11 12 14 15] 05: 00 00 12 INTA 01 [ 3 4 5 7 9 10 11 12 14 15] INTB 00 [ ] INTC 00 [ ] INTD 00 [ ] Thanks Andrew On Fri, 3 Aug 2001, Mike Smith wrote: > > Tried the patch, interesting thing, for some reason or other its always > > routing the IRQ to the same IRQ as the realtek network card I have in > > here, and with the patch in (before nothing worked at all on the pccbb), > > now if the network card is in slot0 it doesnt work, and the wavelan does, > > if the wavelan comes first on the pcibus it doesnt work and the network > > card does. For some reason it always seems to be trying to share an IRQ > > between these 2, any reason for this? > > Yeah; that seems to be the way your system's interrupt routing is set up. > > Get http://people.freebsd.org/~msmith/pir.c, build and run it and let's > look at the output. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 6:29:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtpproxy1.mitre.org (mb-20-100.mitre.org [129.83.20.100]) by hub.freebsd.org (Postfix) with ESMTP id 7C25B37B405 for ; Fri, 3 Aug 2001 06:29:21 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id f73DSjD16843; Fri, 3 Aug 2001 09:28:45 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id f73DShX20586; Fri, 3 Aug 2001 09:28:44 -0400 (EDT) Received: from dhcp-105-164.mitre.org (128.29.105.164) by mailhub2.mitre.org with SMTP id 7350631; Fri, 03 Aug 2001 09:28:42 -0400 Message-ID: <3B6AA70B.A8F5EE6D@mitre.org> Date: Fri, 03 Aug 2001 09:28:43 -0400 From: Jason Andresen Organization: The MITRE Corporation X-Mailer: Mozilla 4.75 [en]C-20000818M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: a little O/T, but D.V.D. drives&freeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Julian Elischer wrote: > > anyone had success watching a dvd? > (Anyone have the correct components saved away somewhere?) > > just got a drive and would like to test it.. > > :-) I managed to get vlc working (http://www.videolan.org) and actually watched a few minutes of DVD with it. It's not a particularly good player (no working subtitle support, no input buffer) so it tends to skip a bit on my PII-400. Faster machines may be able to maintain full speed. Interestingly enough vlc only uses about 60-80% of my CPU when playing, but still cannot maintain full speed (due to the lack of input buffer). Your only other option under FreeBSD is to try xine+captain_css (google is your friend), but I've never actually managed to get that configuration working. I almost played the first frame of a DVD once though. -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 7:26: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from torb.pix.net (torb.pix.net [192.135.81.20]) by hub.freebsd.org (Postfix) with ESMTP id 3DB8D37B406 for ; Fri, 3 Aug 2001 07:26:06 -0700 (PDT) (envelope-from stripes@iamsofired.com) Received: (from stripes@localhost) by torb.pix.net (8.11.4/8.11.4) id f73EQfH11999 for hackers@FreeBSD.ORG; Fri, 3 Aug 2001 10:26:41 -0400 (EDT) (envelope-from stripes@iamsofired.com) X-Authentication-Warning: torb.pix.net: stripes set sender to stripes@iamsofired.com using -f Date: Fri, 3 Aug 2001 10:26:41 -0400 From: Josh M Osborne To: hackers@FreeBSD.ORG Subject: Does /dev/bpf work with kevent? Message-ID: <20010803102640.A11972@torb.pix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm attempting to use kevent with /dev/bpf to check to see if it is ready for reads, but it seems to always return ready to read, but the reads get EAGAIN. Does /dev/bpf not work with kevent? Or should I look elsewhere for my bug (like forgetting some random ioctl)? If you can't use /dev/bpf can ng_bpf and ng_socket somehow be used? Any examples of either, or both laying around somewhere? (I've never used the netgraph stuff before -- as cool as netgraph looks I haven't had the need) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 7:37:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ip.eth.net (mail.ip.eth.net [202.9.128.18]) by hub.freebsd.org (Postfix) with ESMTP id 4888737B406 for ; Fri, 3 Aug 2001 07:37:48 -0700 (PDT) (envelope-from anjali@indranetworks.com) Received: (apparently) from anjali ([61.11.16.239]) by ip.eth.net with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 3 Aug 2001 20:07:39 +0530 Message-ID: <001f01c11c29$dbb0abb0$0a00a8c0@indranet> From: "Anjali Kulkarni" To: Subject: Panic! Date: Fri, 3 Aug 2001 20:07:40 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C11C57.F2F7E7B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C11C57.F2F7E7B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I wrote some kernel code(a kernel proxy), which was giving problems ie = hanging after x no. of connections, and rebooting on its own saying = syncing disc, lost 97 buffers! Now, after booting, it shows all regiters = like eip, etc. and says System halted. Can someoen let me know if I can = recover the systam or will I have to reload the OS?:((( Thanks, Anjali ------=_NextPart_000_001C_01C11C57.F2F7E7B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I wrote some kernel code(a kernel = proxy), which was=20 giving problems ie hanging after x no. of connections, and rebooting on = its own=20 saying syncing disc, lost 97 buffers! Now, after booting, it shows all = regiters=20 like eip, etc. and says System halted. Can someoen let me know if I can = recover=20 the systam or will I have to reload the OS?:(((
 
Thanks,
Anjali
------=_NextPart_000_001C_01C11C57.F2F7E7B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 7:46:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (gw.Awfulhak.org [217.204.245.18]) by hub.freebsd.org (Postfix) with ESMTP id B94AC37B406 for ; Fri, 3 Aug 2001 07:46:35 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.4/8.11.4) with ESMTP id f73EkVs28240 for ; Fri, 3 Aug 2001 15:46:31 +0100 (BST) (envelope-from brian@lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.4/8.11.4) with ESMTP id f73EkUu33353 for ; Fri, 3 Aug 2001 15:46:30 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200108031446.f73EkUu33353@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: hackers@FreeBSD.ORG Subject: Re: a little O/T, but D.V.D. drives&freeBSD In-Reply-To: Message from Gabriel Rocha of "Thu, 02 Aug 2001 22:43:31 EDT." <20010802224331.A22714@geeksimplex.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 15:46:30 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > ,----[ On Thu, Aug 02, at 05:57PM, Julian Elischer wrote: ]-------------- > | anyone had success watching a dvd? > `----[ End Quote ]--------------------------- > > ok, first and foremost, please, anyone else replying, reply to the list > and not to me and please dont cc me, i am on the list. (i have to, i got > a LOT of replies far after my answer was achieved last time) anyway, vlc > is what you want, it works decently if you have a good video card, it > simply reboots my -current laptop, so your milleage may vary, but there > are numerous reports of successful usage. good luck. --gabe This program doesn't seem to work very well at all. It seems to create a thread and set p_vout to NULL on line 95 of vlc-0.2.81/src/video_decoder/vpar_synchro.c, then goes and dereferences it on line 228 of vlc-0.2.81/src/video_decoder/vpar_synchro.c. If anyone's interested in committing it as a port, you can find the necessary files at ftp://ftp.Awfulhak.org/pub/vlc-port. > -- > > "It's not brave if you're not scared." -- Brian http://www.freebsd-services.com/ 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 Fri Aug 3 7:49:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.webmonster.de (datasink.webmonster.de [194.162.162.209]) by hub.freebsd.org (Postfix) with SMTP id AD47037B401 for ; Fri, 3 Aug 2001 07:49:46 -0700 (PDT) (envelope-from karsten@rohrbach.de) Received: (qmail 16566 invoked by uid 1000); 3 Aug 2001 14:50:07 -0000 Date: Fri, 3 Aug 2001 16:50:07 +0200 From: "Karsten W. Rohrbach" To: freebsd-hackers@freebsd.org Subject: proprietary extensions to tcp/ip? Message-ID: <20010803165007.G15500@mail.webmonster.de> Mail-Followup-To: "Karsten W. Rohrbach" , freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="nhYGnrYv1PEJ5gA2" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.webmonster.de/ X-Disclaimer: My opinions do not necessarily represent those of my employer Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --nhYGnrYv1PEJ5gA2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable some paranoid but very interesting read: http://www.pbs.org/cringely/pulpit/pulpit20010802.html basically it's about m$ perhaps filling a niche to satisfy riaa/mpoa by implementing proprietary extensions to ip and pushing it into the market by force. /k --=20 > Worry is interest paid before a debt is due. KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.n= et/ karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- catch@spam.de GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 B= F46 Please do not remove my address from To: and Cc: fields in mailing lists. 1= 0x --nhYGnrYv1PEJ5gA2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7arofM0BPTilkv0YRAhLcAJ9SD30mst8pELhKThwuXlzE0EMNcwCglmpV ego+PlFE3p+dmfvlYnH9DC4= =qRWY -----END PGP SIGNATURE----- --nhYGnrYv1PEJ5gA2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 7:53:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by hub.freebsd.org (Postfix) with ESMTP id E629137B401 for ; Fri, 3 Aug 2001 07:53:25 -0700 (PDT) (envelope-from archer@whichever.org) Received: from 207-172-82-173.s46.as6.xnb.nj.dialup.rcn.com ([207.172.82.173] helo=unknown.whichever.org) by smtp03.mrf.mail.rcn.net with esmtp (Exim 3.32 #2) id 15SgKK-0002XJ-00 for freebsd-hackers@freebsd.org; Fri, 03 Aug 2001 10:53:24 -0400 Received: (from archer@localhost) by unknown.whichever.org (8.11.4/8.11.1) id f73ErMv38049 for freebsd-hackers@freebsd.org; Fri, 3 Aug 2001 10:53:22 -0400 (EDT) (envelope-from archer) Date: Fri, 3 Aug 2001 10:53:22 -0400 From: Alexander Litvin To: freebsd-hackers@freebsd.org Subject: gethostbyXXXX_r() Message-ID: <20010803105321.A37737@unknown.whichever.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Are there any plans of making gethostbyname_r() and gethostbyaddr_r() available in FreeBSD? May be somebody already has them almost ready to be commited? Or are there any considered wrong way to go? The reason I'm asking is that I actually have a local patch implementing them here (only for DNS for now). Is it good idea to put some effort to finalaze it and submit a PR? Or I'd better not waist time on that? --- Life would be so much easier if we could just look at the source code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8: 2:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id 1E64037B405 for ; Fri, 3 Aug 2001 08:02:17 -0700 (PDT) (envelope-from K.J.Koster@kpn.com) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Fri, 3 Aug 2001 17:02:15 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FD9E63@l04.research.kpn.com> From: "Koster, K.J." To: "'Karsten W. Rohrbach'" Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: proprietary extensions to tcp/ip? Date: Fri, 3 Aug 2001 17:02:08 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dear Karsten, > > some paranoid but very interesting read: > http://www.pbs.org/cringely/pulpit/pulpit20010802.html > > basically it's about m$ perhaps filling a niche to satisfy > riaa/mpoa by > implementing proprietary extensions to ip and pushing it into > the market by force. > It's being discussed on Slashdot too. That is perhaps a better place for this type of messages. Actually, http://daily.daemonnews.org/ is the very best place. :-) Kees Jan ===================================================== You can't have everything. Where would you put it? [Steven Wright] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8: 6: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ip.eth.net (mail.ip.eth.net [202.9.128.18]) by hub.freebsd.org (Postfix) with ESMTP id 89FB437B401 for ; Fri, 3 Aug 2001 08:05:55 -0700 (PDT) (envelope-from anjali@indranetworks.com) Received: (apparently) from anjali ([61.11.16.239]) by ip.eth.net with Microsoft SMTPSVC(5.5.1877.467.46); Fri, 3 Aug 2001 20:35:51 +0530 Message-ID: <002a01c11c2d$cbd82250$0a00a8c0@indranet> From: "Anjali Kulkarni" To: Subject: hi Date: Fri, 3 Aug 2001 20:35:53 +0530 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0027_01C11C5B.E40614D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0027_01C11C5B.E40614D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Thank god for small mercies! I loaded an older version of the kernel, = and it worked! Basically, I was too worried to think before I wrote that = last mail! Sorry for the trouble! Though any tips for my mistakes would be much = appreciated:)) Anjali ------=_NextPart_000_0027_01C11C5B.E40614D0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Thank god for small mercies! I loaded = an older=20 version of the kernel, and it worked! Basically, I was too worried to = think=20 before I wrote that last mail!
Sorry for the trouble! Though any tips = for my=20 mistakes would be much appreciated:))
 
Anjali
------=_NextPart_000_0027_01C11C5B.E40614D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8:33: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7FBBC37B403 for ; Fri, 3 Aug 2001 08:32:58 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f73FWhF03905; Fri, 3 Aug 2001 09:32:44 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.4) with ESMTP id f73FWgH65065; Fri, 3 Aug 2001 09:32:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200108031532.f73FWgH65065@harmony.village.org> To: lists Subject: Re: Wierd IRQ Routing issues Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 03 Aug 2001 09:47:54 +0200." References: Date: Fri, 03 Aug 2001 09:32:42 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message lists writes: : Yeah thats the wi0 timeout machine, the other machine doesnt do a : pci_cfgintr_search or an irq routing, it does a hard assignment by the : looks of things, not sure why that is PNP OS yes vs no? Wanrer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8:45:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-27-141-144.mmcable.com [24.27.141.144]) by hub.freebsd.org (Postfix) with SMTP id 1E50437B407 for ; Fri, 3 Aug 2001 08:45:36 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 46673 invoked by uid 100); 3 Aug 2001 15:45:35 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15210.50975.539753.727930@guru.mired.org> Date: Fri, 3 Aug 2001 10:45:35 -0500 To: so@server.i-clue.de Cc: Randy Kunkee , freebsd-hackers@FreeBSD.ORG Subject: Re: cvsup updater failed In-Reply-To: <3B6A508D.2FCBB24F@i-clue.de> References: <3B6A3BEC.831D0D56@randallkunkee.com> <3B6A508D.2FCBB24F@i-clue.de> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Christoph Sold types: > - update the CVSup port (not the CVSup-bin port!) Warning about this one: you should consider updating from the package, not the port. If you update the port, you'll wind up installing a modula compiler system to install it (which is why cvsup-bin existed in the first place). If you do build the port, you'll want to set STATIC=yes as otherwise you'll need to keep the modula runtime libraries as well. The package avoids that by building STATIC. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8:47:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 89CB137B407 for ; Fri, 3 Aug 2001 08:47:05 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (2-021.cwb-adsl.brasiltelecom.net.br [200.193.161.21]) by netbank.com.br (Postfix) with ESMTP id 6A60346805; Fri, 3 Aug 2001 12:46:33 -0300 (BRST) Received: from localhost (pgpazk@localhost [127.0.0.1]) by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f73FkBF23967; Fri, 3 Aug 2001 12:46:37 -0300 Date: Fri, 3 Aug 2001 12:46:10 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: Julian Elischer , craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B6A35E4.626983E@mindspring.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Terry Lambert wrote: > Original poster said he was working on it for Linux, which > means it's not done, which means "not Linux". It's been running for a while now, integrated in the 2.4 kernel. The way Linux manages to avoid the horrors you describe is by simply not letting the kernel use more than its 1GB (or 2GB) of KVA. No special tricks to make the kernel use more memory, let it go on a diet instead. > FWIW, on the "Linux has it, so FreeBSD should have it" > arguments: > > "If all your friends jumped off a cliff..." Fully agreed, but as long as you don't do any weird tricks trying to let the kernel itself use more memory, it's not at all like jumping from a cliff ... Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8:48:28 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 8091C37B407; Fri, 3 Aug 2001 08:48:23 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (2-021.cwb-adsl.brasiltelecom.net.br [200.193.161.21]) by netbank.com.br (Postfix) with ESMTP id 5C74646804; Fri, 3 Aug 2001 12:47:52 -0300 (BRST) Received: from localhost (pdtmyz@localhost [127.0.0.1]) by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f73FmKF24163; Fri, 3 Aug 2001 12:48:20 -0300 Date: Fri, 3 Aug 2001 12:48:20 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: Julian Elischer , Kenneth Wayne Culver , John Baldwin , , craig Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B6A369F.C35B7B03@mindspring.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Terry Lambert wrote: > Correct me if I'm wrong, and 64 bit PCI cards can in fact > DMA at offsets above 4G, in the physical address space... They can. And for 32 bit PCI cards you simply use bounce buffers in the same way you handle ISA bounce buffers. It's ugly, but if you have a huge dataset it's better than getting the data from disk. Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 8:53:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from romeo.unimessage.net (cbrtmx01.unimessage.net [212.6.90.199]) by hub.freebsd.org (Postfix) with ESMTP id 1F49737B401 for ; Fri, 3 Aug 2001 08:53:32 -0700 (PDT) (envelope-from thenamelessone@abacho.de) Received: from shakespeare.unimessage.net (shakespeare.unimessage.net [10.20.1.70]) by romeo.unimessage.net (8.11.2/8.11.2/Debian 8.11.0-6) with ESMTP id f73FrTK07776 for ; Fri, 3 Aug 2001 17:53:29 +0200 Received: from aaron.unimessage.net (aaron [10.20.1.20]) by shakespeare.unimessage.net (Postfix) with ESMTP id A5BCABA for ; Fri, 3 Aug 2001 17:53:30 +0200 (MET DST) Message-ID: <207113094.996853278794.JavaMail.root@aaron.unimessage.net> From: thenamelessone@abacho.de To: freebsd-hackers@FreeBSD.ORG Subject: RE: proprietary extensions to tcp/ip? In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9E63@l04.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Canbox-Sender: thenamelessone@abacho.de X-Canbox-MsgType: email X-Canbox-SendDate: 996854003276 X-Canbox-UserName: thenamelessone X-Canbox-ServiceGroup: abachode Date: Fri, 3 Aug 2001 17:53:30 +0200 (MET DST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG theres a problem if this should happen. most internet providers use unixes for login. since linux, bsd etc. wont be able to use tcp/ms microsoft would be used and i think that this could happen but there will stay some unix providers like in the old days with slip, and so the current internet would remain to the unixes or at least there will be some tunneling so the old unix driven ip internet will be connected to the microsoft driven "micronet". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 9:18:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id A3EE137B408; Fri, 3 Aug 2001 09:18:07 -0700 (PDT) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id CC3B21E019; Fri, 3 Aug 2001 12:18:06 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id MAA13736; Fri, 3 Aug 2001 12:18:05 -0400 (EDT) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id JAA18164; Fri, 3 Aug 2001 09:18:05 -0700 (PDT) Message-Id: <200108031618.JAA18164@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: oppermann@telehouse.ch Subject: Re: 303,000 routes in kernel Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Date: Fri, 3 Aug 2001 09:18:04 -0700 Versions: dmail (solaris) 2.2j/makemail 2.9b Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG What do the routes look like? Could they be a side effect of routing (e.g. default route pointing to the wrong router -> redirects, or default route pointing to the interface -> proxy arp for the whole world)? Can you send a sample few (don't need 303,000 =)? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 9:58:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avengers.ivision.co.uk (avengers.ivision.co.uk [212.25.225.7]) by hub.freebsd.org (Postfix) with ESMTP id D1FC937B405; Fri, 3 Aug 2001 09:58:27 -0700 (PDT) (envelope-from jasper@ivision.co.uk) Received: from [212.25.225.7] (helo=avengers) by avengers.ivision.co.uk with esmtp (Exim 2.04 #1) id 15SiHK-00049h-00; Fri, 3 Aug 2001 17:58:26 +0100 Date: Fri, 3 Aug 2001 17:58:26 +0100 (BST) From: Jasper Wallace X-Sender: To: Andre Oppermann Cc: , Subject: Re: 303,000 routes in kernel In-Reply-To: <3B69CE3F.1BCCB280@telehouse.ch> Message-ID: X-NCC-RegID: uk.instant-web MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 3 Aug 2001, Andre Oppermann wrote: > Hello guys > > have got a small problem. I'm running a secondary DNS server for the > ccTLD .ch here in Switzerland. > # vmstat -m > Memory statistics by type Type Kern > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > ... > routetbl607857 85480K 85480K 85480K 2420956 0 0 > 16,32,64,128,256 > ... > Memory Totals: In Use Free Requests > 91073K 2948K 786316696 If you want to wack up the amount of ram used for the routing table you can adjust the amount of ram the kernel uses for it's stuff with something like this in your kernel config file: # 1/2 RAM for the kernel - lets us have full routes. options VM_KMEM_SIZE_SCALE="(2)" If anyone knows a better way to persuade the kernel to use more space for the routing table i'd love to know. -- Internet Vision Internet Consultancy Tel: 020 7589 4500 60 Albert Court & Web development Fax: 020 7589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 10: 3:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id AF4B037B407 for ; Fri, 3 Aug 2001 10:03:20 -0700 (PDT) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (ns1.baynetworks.com [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id JAA00057 for ; Fri, 3 Aug 2001 09:52:35 -0700 (PDT) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id KAA12546 for ; Fri, 3 Aug 2001 10:01:09 -0700 (PDT) Received: from baynetworks.com (tuva [192.32.150.102]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id NAA06144; Fri, 3 Aug 2001 13:03:18 -0400 for Message-Id: <200108031703.NAA06144@pobox.engeast.BayNetworks.COM> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Freebsd-hackers@freebsd.org Subject: Ypbind and network flooding Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 13:03:18 -0400 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi: Has there been any resolution to the problem where ypbind whacks out and starts flooding the network, as described in the following message in questions? http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=741568+744589+/usr/local/www/db/text/2001/freebsd-questions/20010318.freebsd-questions -- Robert Withrow -- (+1 978 288 8256, ESN 248) BWithrow@NortelNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 10: 4:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from randallkunkee.com (adsl-65-65-19-145.dsl.hstntx.swbell.net [65.65.19.145]) by hub.freebsd.org (Postfix) with ESMTP id BC69237B407 for ; Fri, 3 Aug 2001 10:04:24 -0700 (PDT) (envelope-from randy@randallkunkee.com) Received: from randallkunkee.com (localhost [127.0.0.1]) by randallkunkee.com (8.12.0.Beta7/8.12.0.Beta7) with ESMTP id f73H4Tmu027307; Fri, 3 Aug 2001 12:04:29 -0500 (CDT) Message-ID: <3B6AD99C.FBC52770@randallkunkee.com> Date: Fri, 03 Aug 2001 12:04:29 -0500 From: Randy Kunkee X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: so@server.i-clue.de, freebsd-hackers@FreeBSD.ORG Subject: Re: cvsup updater failed References: <3B6A3BEC.831D0D56@randallkunkee.com> <3B6A508D.2FCBB24F@i-clue.de> <15210.50975.539753.727930@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Meyer wrote: > Christoph Sold types: > > - update the CVSup port (not the CVSup-bin port!) > > Warning about this one: you should consider updating from the package, > not the port. If you update the port, you'll wind up installing a > modula compiler system to install it (which is why cvsup-bin existed > in the first place). If you do build the port, you'll want to set > STATIC=yes as otherwise you'll need to keep the modula runtime > libraries as well. The package avoids that by building STATIC. > > -- > Mike Meyer http://www.mired.org/home/mwm/ > Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. I just recently installed the package cvsup-16.1_1.tgz, which I think is the latest. Perhaps I did not look carefully enough -- I thought the file with the strange name was on the mirror and not on my system. All is well now. Thanks to everyone for the help. Randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 10:20:50 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.kscable.com (fe4.rdc-kc.rr.com [24.94.163.51]) by hub.freebsd.org (Postfix) with ESMTP id 0328437B410; Fri, 3 Aug 2001 10:20:40 -0700 (PDT) (envelope-from natedac@kscable.com) Received: from wks-166-131-9.kscable.com ([24.166.131.9]) by mail4.kscable.com with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 3 Aug 2001 12:20:38 -0500 Date: Fri, 3 Aug 2001 12:18:25 -0500 (CDT) From: Nate Dannenberg X-X-Sender: To: Terry Lambert Cc: John Baldwin , Subject: Re: PR 25958 In-Reply-To: <3B6A37DC.7F9171BB@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Nate Dannenberg wrote: > > I'd be glad to, however I no longer run FreeBSD. I have since switched to > > Linux. > > [ ... ] > > > Not being much of a C programmer > > anymore I can't really say for certain though :) > > Are these two statements related by cause and effect? No :) When I put that patch together (as said in the original PR) most of the help came from others who knew C pretty well. I'd forgotten most of my own C skills long before I ever got my first PC :) (I learned C in college, but never managed to put that skill to any use, at the time all I had was a Commodore 128 as my only computer. On that platform, C wasn't a very viable choice against 6502 assembly :-) -- _________________________ ___ ___ | natedac@kscable.com //ZZ]__ | | C64/C128/SCPU |'/ |Z/ | | What's *YOUR* Hobby!? | \__|_\ | |_________________________\___]___| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 10:46:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id A202637B406 for ; Fri, 3 Aug 2001 10:46:27 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA51925; Fri, 3 Aug 2001 12:50:00 -0700 (PDT) Date: Fri, 3 Aug 2001 12:49:59 -0700 (PDT) From: Julian Elischer To: =?iso-8859-1?q?vishwanath=20pargaonkar?= Cc: tlambert2@mindspring.com, Zhihui Zhang , Bosko Milekic , Alfred Perlstein , freebsd-hackers@FreeBSD.ORG Subject: Re: malloc In-Reply-To: <20010803082921.4234.qmail@web5304.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 3 Aug 2001, [iso-8859-1] vishwanath pargaonkar wrote: > Hi, > can anybody tell me in malloc what does third > parameter > DONTWAIT ,NOWAIT and WAITOK mean? > Bcoz i have function being called using timeout.in > that function i need to malloc a buffer. > can i use WAITOK? > please tell me abt this. you must use NOWAIT, and you must handle the case where it may fail and return NULL. > > > TIA > > > > > 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 Aug 3 10:46:41 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 3DD4437B406; Fri, 3 Aug 2001 10:46:37 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id MAA51912; Fri, 3 Aug 2001 12:41:54 -0700 (PDT) Date: Fri, 3 Aug 2001 12:41:53 -0700 (PDT) From: Julian Elischer To: Mike Smith Cc: Kenneth Wayne Culver , John Baldwin , freebsd-hackers@FreeBSD.ORG, craig , Terry Lambert , Rik van Riel Subject: Re: How to visit physical memory above 4G? In-Reply-To: <200108030352.f733q9C01482@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 2 Aug 2001, Mike Smith wrote: > Julian is on crack. DAC (Double Address Cycle) is a relatively recent > addition to PCI that allows 32-bit cards with 64-bit savvy logic to talk > to host memory using 64-bit target addresses. well "day 1" was an exageration, but my 1995 PCI stuff already includes it. Crack? no.. optimism, maybe.. > Older systems used a scatter-gather mechanism to present a virtualised > view of the system's physical address space to the PCI bus (typically > you'll see this in Alpha systems). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 10:51:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 749CD37B407 for ; Fri, 3 Aug 2001 10:51:31 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id f73HpN472848; Fri, 3 Aug 2001 13:51:23 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010803102640.A11972@torb.pix.net> References: <20010803102640.A11972@torb.pix.net> Date: Fri, 3 Aug 2001 13:51:20 -0400 To: Josh M Osborne , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Does /dev/bpf work with kevent? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:26 AM -0400 8/3/01, Josh M Osborne wrote: >I'm attempting to use kevent with /dev/bpf to check to see if it >is ready for reads, but it seems to always return ready to read, >but the reads get EAGAIN. > >Does /dev/bpf not work with kevent? Or should I look elsewhere >for my bug (like forgetting some random ioctl)? > >If you can't use /dev/bpf can ng_bpf and ng_socket somehow be used? >Any examples of either, or both laying around somewhere? (I've >never used the netgraph stuff before -- as cool as netgraph looks >I haven't had the need) Are you trying this on current or stable? current has a bug fix to bpf which still hasn't been merged to stable. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11: 1: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from safety.net (ns3.safety.net [216.200.162.38]) by hub.freebsd.org (Postfix) with ESMTP id A608537B411 for ; Fri, 3 Aug 2001 11:00:45 -0700 (PDT) (envelope-from les@safety.net) Received: (from les@localhost) by safety.net (8.9.3/8.9.3) id LAA79737 for freebsd-hackers@freebsd.org; Fri, 3 Aug 2001 11:00:44 -0700 (MST) (envelope-from les) From: Les Biffle Message-Id: <200108031800.LAA79737@safety.net> Subject: dmesg behaviour To: freebsd-hackers@freebsd.org Date: Fri, 3 Aug 2001 11:00:44 -0700 (MST) Reply-To: les@safety.net X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi All, We have a product based on 3.5-stable, and use "dmesg" at startup time to generate an XML description of the hardware, create interface name aliases, etc., and it has worked just fine for a couple of years. We've just purchased a new platform based on the Supermicro 370SSR motherboard, and we're seeing anomolous behaviour on those systems, and ONLY on those systems. On every other system we've used, dmesg shows all the information from the most-recent boot. On the supermicro systems, we may see the information from the last 3 boots! I see the lines: syncing disks... done Rebooting... and then we go right into the next boot. At present, one of the machines shows all the detail from 2.75 reboots. How and why is it doing this, and how do I make it stop? Thanks in advance, -Les -- Les Biffle Community Service... Just Say NO! (480) 778-0177 les@safety.net http://www.networksafety.com/ Network Safety, PO Box 14461, Scottsdale, AZ 85267 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11: 2:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from isris.pair.com (isris.pair.com [209.68.2.39]) by hub.freebsd.org (Postfix) with SMTP id E651637B414 for ; Fri, 3 Aug 2001 11:02:18 -0700 (PDT) (envelope-from rooneg@isris.pair.com) Received: (qmail 4657 invoked by uid 3130); 3 Aug 2001 18:02:17 -0000 Date: Fri, 3 Aug 2001 14:02:17 -0400 From: Garrett Rooney To: Garance A Drosihn Cc: Josh M Osborne , hackers@FreeBSD.ORG Subject: Re: Does /dev/bpf work with kevent? Message-ID: <20010803140217.D51247@electricjellyfish.net> References: <20010803102640.A11972@torb.pix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Fri, Aug 03, 2001 at 01:51:20PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 03, 2001 at 01:51:20PM -0400, Garance A Drosihn wrote: > At 10:26 AM -0400 8/3/01, Josh M Osborne wrote: > >I'm attempting to use kevent with /dev/bpf to check to see if it > >is ready for reads, but it seems to always return ready to read, > >but the reads get EAGAIN. > > > >Does /dev/bpf not work with kevent? Or should I look elsewhere > >for my bug (like forgetting some random ioctl)? > > > >If you can't use /dev/bpf can ng_bpf and ng_socket somehow be used? > >Any examples of either, or both laying around somewhere? (I've > >never used the netgraph stuff before -- as cool as netgraph looks > >I haven't had the need) > > Are you trying this on current or stable? current has a bug fix > to bpf which still hasn't been merged to stable. sorry, i know i said i'd get you that patch, but my FreeBSD machines still aren't hooked up to the net, so i haven't had a chance to update to -STABLE in a long time... guess it'll have to wait until after 4.4 ;-( unfortunately, i don't think that'll effect kevent. it seemed to be pretty localized to select, although i must admit, i don't know all that much about how kevent works under the hood. -- garrett rooney Unix was not designed to stop you from rooneg@electricjellyfish.net doing stupid things, because that would http://electricjellyfish.net/ stop you from doing clever things. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11: 3:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 1116E37B403 for ; Fri, 3 Aug 2001 11:03:26 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 176C381D0A; Fri, 3 Aug 2001 13:03:26 -0500 (CDT) Date: Fri, 3 Aug 2001 13:03:26 -0500 From: Alfred Perlstein To: "Eugene L. Vorokov" Cc: freebsd-hackers@freebsd.org Subject: Re: device i/o question Message-ID: <20010803130326.C85642@elvis.mu.org> References: <200108030949.f739nrZ03446@bugz.infotecs.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200108030949.f739nrZ03446@bugz.infotecs.ru>; from vel@bugz.infotecs.ru on Fri, Aug 03, 2001 at 01:49:53PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Eugene L. Vorokov [010803 04:33] wrote: > Hello, > > I have a module which creates new device for data exchange between user > program and a module. I was wondering, if I open the device in userspace > and write() some piece of data to it, is it guaranteed that the driver > will get this solid piece of data at once, or in certain circumstances > it can be split into parts which are passed to the driver as several > write events ? I'm pretty sure a single user call of write(2) should translate into a single write to your device. There are limits on the size one can write(2) thought. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11: 7:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 3447A37B412 for ; Fri, 3 Aug 2001 11:07:22 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 226AB81D0C; Fri, 3 Aug 2001 13:07:22 -0500 (CDT) Date: Fri, 3 Aug 2001 13:07:22 -0500 From: Alfred Perlstein To: Ullasan Kottummal Cc: freebsd-hackers@freebsd.org Subject: Re: Select call gives EBADF Message-ID: <20010803130722.D85642@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ullasan.kottummal@uk.zurich.com on Fri, Aug 03, 2001 at 12:21:42PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Ullasan Kottummal [010803 06:23] wrote: > Hi, > I am using select() call under HP-UX 10.20 for timing on socket. It throws > the error EBADF. I don't understand why it happens. This isn't an HPUX support forum. Your problem is that: 1) you're using HPUX 2) you didn't read the select(2) manpage carefully enough 3) you didn't provide enough context for this code to be useful Here's what's probably wrong though: > The socket is opened successfully before calling the select and the > descriptor is valid. > > I will give the relevant code below. > > int mask; > struct fd_set readmask ; > readmask.fds_bits[0] = 0; > struct fd_set readfds; > int nfound, i; > struct timeval timeout; > > mask = MASK(m_iSocket); > readmask.fds_bits[0] |= mask; > readfds.fds_bits[0] = readmask.fds_bits[0]; > > timeout.tv_sec = m_iSelectTimeout; > timeout.tv_usec = 0; > FD_ZERO(&readfds); Shouldn't this be: FD_ZERO(&readfds); FD_SET(m_iSocket, &readfds); I mean how else is select supposed to know which file you're interested in??? > > if ((nfound = select (SOCKETS, &readfds, 0, 0, &timeout)) == -1) > { > cerr << "==>Select call failed : " << endl; > //Errror checking done > ....... > ........ > } -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11:11:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 630B837B405 for ; Fri, 3 Aug 2001 11:11:15 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 3BDCC81D0C; Fri, 3 Aug 2001 13:11:15 -0500 (CDT) Date: Fri, 3 Aug 2001 13:11:15 -0500 From: Alfred Perlstein To: Alexander Litvin Cc: freebsd-hackers@freebsd.org Subject: Re: gethostbyXXXX_r() Message-ID: <20010803131115.F85642@elvis.mu.org> References: <20010803105321.A37737@unknown.whichever.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010803105321.A37737@unknown.whichever.org>; from archer@whichever.org on Fri, Aug 03, 2001 at 10:53:22AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Alexander Litvin [010803 09:54] wrote: > Are there any plans of making gethostbyname_r() and gethostbyaddr_r() > available in FreeBSD? May be somebody already has them almost ready > to be commited? Or are there any considered wrong way to go? > > The reason I'm asking is that I actually have a local patch implementing > them here (only for DNS for now). Is it good idea to put some effort to > finalaze it and submit a PR? Or I'd better not waist time on that? Please complete it, let me know when you submit the PR i'll try to get it integrated. -- -Alfred Perlstein [alfred@freebsd.org] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11:13:39 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 0020537B403 for ; Fri, 3 Aug 2001 11:13:33 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f73IDHc65773; Fri, 3 Aug 2001 20:13:18 +0200 (SAST) (envelope-from lists@security.za.net) Date: Fri, 3 Aug 2001 20:13:17 +0200 (SAST) From: lists To: Warner Losh Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Wierd IRQ Routing issues In-Reply-To: <200108031532.f73FWgH65065@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG One machine (the working one) is set to pnp os, my machine doesnt have an option to set it in the bios (the machine that doesnt work) Cheers Andrew On Fri, 3 Aug 2001, Warner Losh wrote: > In message lists writes: > : Yeah thats the wi0 timeout machine, the other machine doesnt do a > : pci_cfgintr_search or an irq routing, it does a hard assignment by the > : looks of things, not sure why that is > > PNP OS yes vs no? > > Wanrer > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11:25:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id B980E37B403; Fri, 3 Aug 2001 11:25:43 -0700 (PDT) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id UAA09824; Fri, 3 Aug 2001 20:25:40 +0200 (CEST) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.3/8.8.8) with ESMTP id f73IOZH00817; Fri, 3 Aug 2001 20:24:35 +0200 (CEST) (envelope-from root@nihil) Date: Fri, 3 Aug 2001 20:24:33 +0200 (CEST) From: Michael Reifenberger To: Mike Smith Cc: lists , Warner Losh , Subject: Re: NewCard / pccbb In-Reply-To: <200108030845.f738jRk01199@mass.dis.org> Message-ID: <20010803202243.J796-100000@nihil> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, BTW the pir output for a TECRA8000 looks like: $PIR table at 0x3812a1e0 version 1.0 PCI interrupt router at 0:2.8 vendor 0x8086 device 0x122e PCI-only interrupts [ ] entry bus slot device 00: 00 00 11 INTA 60 [ 11 ] INTB 61 [ 11 ] INTC 00 [ ] INTD 00 [ ] 01: 00 00 09 INTA 62 [ 11 ] INTB 00 [ ] INTC 00 [ ] INTD 00 [ ] 02: 00 00 04 INTA 62 [ 11 ] INTB 63 [ 11 ] INTC 00 [ ] INTD 00 [ ] 03: 00 00 13 INTA 63 [ 11 ] INTB 00 [ ] INTC 00 [ ] INTD 00 [ ] 04: 00 00 05 INTA 00 [ ] INTB 00 [ ] INTC 00 [ ] INTD 63 [ 11 ] 05: 00 01 06 INTA 62 [ 11 ] INTB 63 [ 11 ] INTC 60 [ 11 ] INTD 61 [ 11 ] Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11:35:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 32B9E37B40F for ; Fri, 3 Aug 2001 11:34:51 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f73IYcs21840 for ; Fri, 3 Aug 2001 14:34:38 -0400 (EDT) Date: Fri, 3 Aug 2001 14:34:17 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@FreeBSD.ORG Subject: Re: Allocate a page at interrupt time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I should have guessed the reason. Matthew Dillon answered this question on Fri, 2 Jun 2000 as follows: The VM routines that manage pages associated with objects are not protected against interrupts, so interrupts aren't allowed to change page-object associations. Otherwise an interrupt at just the wrong time could corrupt the mainline kernel VM code. On Thu, 2 Aug 2001, Zhihui Zhang wrote: > > FreeBSD can not allocate from the PQ_CACHE queue in an interrupt context. > Can anyone explain it to me why this is the case? > > > Thanks, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11:48: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from torb.pix.net (torb.pix.net [192.135.81.20]) by hub.freebsd.org (Postfix) with ESMTP id 3963437B403 for ; Fri, 3 Aug 2001 11:48:00 -0700 (PDT) (envelope-from stripes@iamsofired.com) Received: (from stripes@localhost) by torb.pix.net (8.11.4/8.11.4) id f73ImbK12525; Fri, 3 Aug 2001 14:48:37 -0400 (EDT) (envelope-from stripes@iamsofired.com) X-Authentication-Warning: torb.pix.net: stripes set sender to stripes@iamsofired.com using -f Date: Fri, 3 Aug 2001 14:48:37 -0400 From: Josh M Osborne To: Garance A Drosihn Cc: hackers@FreeBSD.ORG Subject: Re: Does /dev/bpf work with kevent? Message-ID: <20010803144837.A12438@torb.pix.net> References: <20010803102640.A11972@torb.pix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Fri, Aug 03, 2001 at 01:51:20PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 03, 2001 at 01:51:20PM -0400, Garance A Drosihn wrote: [.../dev/bpf...kevent...EAGAIN...] > Are you trying this on current or stable? current has a bug fix > to bpf which still hasn't been merged to stable. 4.3-RELEASE, and 4.3-STABLE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 11:52:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with SMTP id 788EC37B405 for ; Fri, 3 Aug 2001 11:52:45 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10911 invoked from network); 3 Aug 2001 18:52:33 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 3 Aug 2001 18:52:33 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 03 Aug 2001 11:52:33 -0700 (PDT) From: John Baldwin To: Nate Dannenberg Subject: Re: PR 25958 Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 02-Aug-01 Nate Dannenberg wrote: > On Thu, 2 Aug 2001, John Baldwin wrote: > >> Nate, >> >> Can you try out the patch at http://www.freebsd.org/~jhb/patches/mtrr.patch? > > I'd be glad to, however I no longer run FreeBSD. I have since switched to > Linux. While FreeBSD was stable and reliable on my machine, I found that > support for it was lacking in things like multimedia (playing movies, > watching > TV, and so on). Ok. You do know that 'fxtv' is developed on FreeBSD, right? :) My TV _is_ my workstation. :) Granted, I don't think you can watch DVD's on FreeBSD very easily. > I can say though that the MTRR problem is definitely a bug - under Linux > MTRR's cause no trouble at all. Are you sure it's using them? :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Aug 3 12: 1: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id D8C8837B401; Fri, 3 Aug 2001 12:00:59 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f73J0xM91833; Fri, 3 Aug 2001 12:00:59 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A63933811; Fri, 3 Aug 2001 12:00:59 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: Poul-Henning Kamp Cc: Andre Oppermann , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel In-Reply-To: <93100.996790166@critter> Date: Fri, 03 Aug 2001 12:00:59 -0700 From: Peter Wemm Message-Id: <20010803190059.A63933811@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > In message <3B69CE3F.1BCCB280@telehouse.ch>, Andre Oppermann writes: > > >The problem I've got now is that for every packet I get the kernel is > >making one host entry in the routing table. Because of the many UDP > >DNS requests from all over the world I've got 303'000 (yes, three- > >hundredthreethousand) entries in the kernel routing table which have > >not expired yet. So I'm getting error messages like this now: > > Hmm, I wasn't aware that we cloned routes for UDP packets, are you sure > that is what is causing the routes to exists ? (Just to mention the > obvious: it's not CodeRed probes ?) Dont forget that DNS can query you over tcp as well.. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 12:27:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.kscable.com (fe4.rdc-kc.rr.com [24.94.163.51]) by hub.freebsd.org (Postfix) with ESMTP id 3AC6A37B406; Fri, 3 Aug 2001 12:27:49 -0700 (PDT) (envelope-from natedac@kscable.com) Received: from wks-166-131-9.kscable.com ([24.166.131.9]) by mail4.kscable.com with Microsoft SMTPSVC(5.5.1877.537.53); Fri, 3 Aug 2001 14:27:48 -0500 Date: Fri, 3 Aug 2001 14:25:35 -0500 (CDT) From: Nate Dannenberg X-X-Sender: To: John Baldwin Cc: Subject: Re: PR 25958 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Ok. You do know that 'fxtv' is developed on FreeBSD, right? :) My TV _is_ my > workstation. :) Granted, I don't think you can watch DVD's on FreeBSD very > easily. Actually I'd never heard of FxTV. I use XawTV, as buggy as it is. The problem isn't so much the application though, but rather, Xfree86 support for my video card. In order to use the TV tuner and video-in feautures of the ATI All-in-Wonder 128 Pro and related cards, you have to use the drivers provided by the GATOS project. (I guess at this point the XFree86 team has decided not to roll these drivers into the X source tree). > > I can say though that the MTRR problem is definitely a bug - under Linux > > MTRR's cause no trouble at all. > > Are you sure it's using them? :) I'm positive I've seen at least one program report that MTRR's were being used. Of course now I can't find the program that reported it. At any rate, they're enabled: natedac@daconcepts ~$ cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size= 64MB: write-back, count=1 reg01: base=0x04000000 ( 64MB), size= 32MB: write-back, count=1 reg02: base=0xf0000000 (3840MB), size= 16MB: write-combining, count=2 -- _________________________ ___ ___ | natedac@kscable.com //ZZ]__ | | C64/C128/SCPU |'/ |Z/ | | What's *YOUR* Hobby!? | \__|_\ | |_________________________\___]___| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 12:32:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with SMTP id 8EDF137B406 for ; Fri, 3 Aug 2001 12:32:18 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 98898 invoked from network); 3 Aug 2001 19:32:17 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 3 Aug 2001 19:32:17 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 03 Aug 2001 12:32:16 -0700 (PDT) From: John Baldwin To: hackers@FreeBSD.org Subject: [PATCH] [BIKESHED] Restarting from panic Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have the following simple and untested patch that I know a few people have asked for. It allows you to restart from a panic and continue executing rather than dumping to the disk and executing. This is remotely useful when doing kernel development when one adds an assertion that ends up being wrong or an assertion fails that isn't really critical in this case, thus, we want to continue executing. Granted, for some panics this can be quite dangerous as some assertions do things like make sure pointers aren't NULL before we dereference them. I'm aware that this is a very efficient foot-shooting implement with limited usefulness. To activate the feature, reset the panicstr variable to NULL from DDB and then do a continue. The panic function will then reset the panic state and bail out before calling boot(). The patch is at http://www.FreeBSD.org/~jhb/patches/panic.patch and included below: Index: kern_shutdown.c =================================================================== RCS file: /usr/cvs/src/sys/kern/kern_shutdown.c,v retrieving revision 1.102 diff -u -r1.102 kern_shutdown.c --- kern_shutdown.c 2001/06/25 18:30:42 1.102 +++ kern_shutdown.c 2001/08/03 19:20:54 @@ -565,12 +565,17 @@ static char buf[256]; #ifdef SMP - /* Only 1 CPU can panic at a time */ - if (panic_cpu != PCPU_GET(cpuid) && - atomic_cmpset_int(&panic_cpu, NOCPU, PCPU_GET(cpuid)) == 0) { - for (;;) - ; /* nothing */ - } + /* + * We don't want multiple CPU's to panic at the same time, so we + * use panic_cpu as a simple spinlock. We have to keep checking + * panic_cpu if we are spinning in case the panic on the first + * CPU is canceled. + */ + if (panic_cpu != PCPU_GET(cpuid)) + while (atomic_cmpset_int(&panic_cpu, NOCPU, + PCPU_GET(cpuid)) == 0) + while (panic_cpu != NOCPU) + ; /* nothing */ #endif bootopt = RB_AUTOBOOT | RB_DUMP; @@ -596,6 +601,13 @@ #if defined(DDB) if (debugger_on_panic) Debugger ("panic"); + /* See if the user aborted the panic, in which case we continue. */ + if (panicstr == NULL) { +#ifdef SMP + atomic_store_rel_int(&panic_cpu, NOCPU); +#endif + return; + } #endif boot(bootopt); } As Peter would say, *donning peril-sensitive sunglasses...* -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Aug 3 13:45:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id DDC8937B405; Fri, 3 Aug 2001 13:45:28 -0700 (PDT) (envelope-from julian@elischer.org) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id PAA52649; Fri, 3 Aug 2001 15:40:46 -0700 (PDT) Date: Fri, 3 Aug 2001 15:40:45 -0700 (PDT) From: Julian Elischer To: John Baldwin Cc: hackers@FreeBSD.org Subject: Re: [PATCH] [BIKESHED] Restarting from panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG seems fair, as it shold be dificult enough that only people who know can do it.. I have another request.... a compile time option that either puts intrrupts onto a separate stack, or leaves a large chunk of ram untouched in the kernel stack when you get a kernel page fault.... I hit the problem where I jump off into space because the stored address was corrupted by an interrupt routine but I cannot figure out what ran, because the page fault handler overwrote it all. I have a version that allocates 256 bytes on the stack in the case of a pagefault, but it's too late.. there's already too much written by the rest of teh trap handler. Also another wishlist item an async even log (maybe a rotating buffer) that logs the last 16 interrupts or whatever. (and maybe their microtimes) there are times you want to know what happenned BEFORE that crash.. :-) On Fri, 3 Aug 2001, John Baldwin wrote: > I have the following simple and untested patch that I know a few people have > asked for. It allows you to restart from a panic and continue executing rather > than dumping to the disk and executing. This is remotely useful when doing > kernel development when one adds an assertion that ends up being wrong or an > assertion fails that isn't really critical in this case, thus, we want to > continue executing. Granted, for some panics this can be quite dangerous as > some assertions do things like make sure pointers aren't NULL before we > dereference them. I'm aware that this is a very efficient foot-shooting > implement with limited usefulness. To activate the feature, reset the panicstr > variable to NULL from DDB and then do a continue. The panic function will then > reset the panic state and bail out before calling boot(). The patch is at > http://www.FreeBSD.org/~jhb/patches/panic.patch and included below: > > Index: kern_shutdown.c > =================================================================== > RCS file: /usr/cvs/src/sys/kern/kern_shutdown.c,v > retrieving revision 1.102 > diff -u -r1.102 kern_shutdown.c > --- kern_shutdown.c 2001/06/25 18:30:42 1.102 > +++ kern_shutdown.c 2001/08/03 19:20:54 > @@ -565,12 +565,17 @@ > static char buf[256]; > > #ifdef SMP > - /* Only 1 CPU can panic at a time */ > - if (panic_cpu != PCPU_GET(cpuid) && > - atomic_cmpset_int(&panic_cpu, NOCPU, PCPU_GET(cpuid)) == 0) { > - for (;;) > - ; /* nothing */ > - } > + /* > + * We don't want multiple CPU's to panic at the same time, so we > + * use panic_cpu as a simple spinlock. We have to keep checking > + * panic_cpu if we are spinning in case the panic on the first > + * CPU is canceled. > + */ > + if (panic_cpu != PCPU_GET(cpuid)) > + while (atomic_cmpset_int(&panic_cpu, NOCPU, > + PCPU_GET(cpuid)) == 0) > + while (panic_cpu != NOCPU) > + ; /* nothing */ > #endif > > bootopt = RB_AUTOBOOT | RB_DUMP; > @@ -596,6 +601,13 @@ > #if defined(DDB) > if (debugger_on_panic) > Debugger ("panic"); > + /* See if the user aborted the panic, in which case we continue. */ > + if (panicstr == NULL) { > +#ifdef SMP > + atomic_store_rel_int(&panic_cpu, NOCPU); > +#endif > + return; > + } > #endif > boot(bootopt); > } > > As Peter would say, *donning peril-sensitive sunglasses...* > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.baldwin.cx/~john/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > 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 Aug 3 13:53:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with SMTP id 93D4537B406 for ; Fri, 3 Aug 2001 13:53:26 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 60466 invoked from network); 3 Aug 2001 20:53:19 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 3 Aug 2001 20:53:19 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 03 Aug 2001 13:52:57 -0700 (PDT) From: John Baldwin To: Julian Elischer Subject: Re: [PATCH] [BIKESHED] Restarting from panic Cc: hackers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 03-Aug-01 Julian Elischer wrote: > Also another wishlist item > > an async even log (maybe a rotating buffer) > that logs the last 16 interrupts or whatever. (and maybe their microtimes) > there are times you want to know what happenned BEFORE that crash.. > >:-) man ktr :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Aug 3 14:16:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pdxpo.dsl-only.net (sub16-3.member.dsl-only.net [63.105.16.3]) by hub.freebsd.org (Postfix) with ESMTP id A6AEC37B401 for ; Fri, 3 Aug 2001 14:16:19 -0700 (PDT) (envelope-from pdxmax@dsl-only.net) Received: from tabor.office.archimedesoft.com (unverified [63.105.19.225]) by pdxpo.dsl-only.net (Rockliffe SMTPRA 4.5.4) with ESMTP id for ; Fri, 3 Aug 2001 14:12:03 -0700 Date: Fri, 3 Aug 2001 14:16:17 -0700 From: Tabor Kelly X-Mailer: The Bat! (v1.49) UNREG / CD5BF9353B3B7091 Reply-To: Tabor Kelly X-Priority: 3 (Normal) Message-ID: <146809363.20010803141617@dsl-only.net> To: freebsd-hackers@freebsd.org Subject: problems with kvm_nlist() Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----------CF1373321FB864C" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------------CF1373321FB864C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I am using kvm_nlist() in one of my programs. I have written a smaller test program for use here. Either kvm_nlist() has a bug or I am very confused. According to kvm_nlist(3), kvm_nlist should go through an array of nlist structures and fill out each structure with that symbol's information. Well, as far as I can tell, it fills out all of the structures with the information from the symbol in the first structure. Has anybody else seen this behavior? Attached is a file named test.cpp that should reproduce this behavior. If you want to play with this behavior, change what structure is pointed to when calling kvm_nlist on line 38 of the program source. Also, be aware that you will have to make the following modifications to the file permissions after you compile it (if you don't want to run it as root): # chown root:kmem a.out # chmod g+s a.out Thank You, Tabor Kelly ------------CF1373321FB864C Content-Type: application/octet-stream; name="test.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test.cpp" Ly90ZXN0LmNwcA0KLy9jb21waWxlIHdpdGggZ2NjIHRlc3QuY3BwIC1sc3RkYysrIC1sa3ZtDQoN CiNpbmNsdWRlIDxmY250bC5oPg0KI2luY2x1ZGUgPGlvc3RyZWFtPg0KI2luY2x1ZGUgPHB0aHJl YWQuaD4NCiNpbmNsdWRlIDxzdHJpbmcuaD4NCiNpbmNsdWRlIDx1bmlzdGQuaD4NCiNpbmNsdWRl IDxzeXMvZGtzdGF0Lmg+DQojaW5jbHVkZSA8a3ZtLmg+DQojaW5jbHVkZSA8bmxpc3QuaD4NCiNp bmNsdWRlIDxzdGRpby5oPg0KDQptYWluKCkNCnsNCiAgaW50IGkgPSBOVUxMOw0KICBpbnQgbyA9 IE5VTEw7DQogIGNoYXIgZXJyb3JCdWZmW19QT1NJWDJfTElORV9NQVhdOw0KICBrdm1fdCAqcEt2 bSA9IE5VTEw7DQogIHN0cnVjdCBubGlzdCBzdHJ1Y3RObGlzdFs3XTsNCiAgYnplcm8oJnN0cnVj dE5saXN0WzBdLCAoc2l6ZW9mKHN0cnVjdCBubGlzdCkgKiA3KSk7DQoNCiAgc3RydWN0Tmxpc3Rb MF0ubl9uYW1lID0gIl9jY3B1IjsNCiAgc3RydWN0Tmxpc3RbMV0ubl9uYW1lID0gIl9jcF90aW1l IjsNCiAgc3RydWN0Tmxpc3RbMl0ubl9uYW1lID0gIl9hdmVydW5uYWJsZSI7DQogIHN0cnVjdE5s aXN0WzNdLm5fbmFtZSA9ICJfYnVmc3BhY2UiOw0KICBzdHJ1Y3RObGlzdFs0XS5uX25hbWUgPSAi X2NudCI7DQogIHN0cnVjdE5saXN0WzVdLm5fbmFtZSA9ICJfbmV4dHBpZCI7DQoNCiAgcEt2bSA9 IGt2bV9vcGVuZmlsZXMoTlVMTCwgTlVMTCwgTlVMTCwgT19SRE9OTFksICZlcnJvckJ1ZmZbMF0p Ow0KICBpZiAocEt2bSA9PSBOVUxMKQ0KICB7DQoJY291dCA8PCAiRXJyb3I6IGt2bV9vcGVuZmls ZXMoKSBmYWlsZWQhXG4iOw0KCWNvdXQgPDwgIlx0XCIiIDw8IGVycm9yQnVmZiA8PCAiXCJcbiI7 DQoJcmV0dXJuIDE7DQogIH0NCg0KICBvID0ga3ZtX25saXN0KHBLdm0sICZzdHJ1Y3RObGlzdFsw XSk7IC8vY2hhbmdlIHdoaWNoIGl0ZW0gaXMgcG9pbnRlZCB0byBmb3IgaW50ZXJlc3RpbmcgcmVz dWx0cy4NCiAgaWYgKG8gPCAwKQ0KICB7DQoJY291dCA8PCAiRXJyb3I6IGt2bV9ubGlzdCgpIGZh aWxlZCFcbiI7DQoJY291dCA8PCAiXHRcIiIgPDwga3ZtX2dldGVycihwS3ZtKSA8PCAiXCJcbiI7 DQoJcmV0dXJuIDE7DQogIH0NCg0KICBjb3V0IDw8IG8gPDwgIiBpdGVtcyBpbiB0aGUgbGlzdCB3 ZXJlIGJhZFxuIjsNCg0KDQogIGZvcihpID0gMDsgaSA8IDY7IGkrKykNCiAgew0KCWNvdXQgPDwg InN0cnVjdE5saXN0WyIgPDwgaSA8PCAiXS5uX25hbWU6ICIgPDwgc3RydWN0Tmxpc3RbaV0ubl9u YW1lDQoJCSA8PCAiXG4iOw0KCWNvdXQgPDwgInN0cnVjdE5saXN0WyIgPDwgaSA8PCAiXS5uX3R5 cGU6ICIgPDwgc3RydWN0Tmxpc3RbaV0ubl90eXBlDQoJCSA8PCAiXG4iOw0KCWNvdXQgPDwgInN0 cnVjdE5saXN0WyIgPDwgaSA8PCAiXS5uX3ZhbHVlOiAiIDw8IHN0cnVjdE5saXN0WzBdLm5fdmFs dWUNCgkJIDw8ICJcbiI7DQogIH0NCg0KICBrdm1fY2xvc2UocEt2bSk7DQp9DQo= ------------CF1373321FB864C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 15:23:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pdxpo.dsl-only.net (sub16-3.member.dsl-only.net [63.105.16.3]) by hub.freebsd.org (Postfix) with ESMTP id C465B37B406 for ; Fri, 3 Aug 2001 15:23:23 -0700 (PDT) (envelope-from pdxmax@dsl-only.net) Received: from tabor.office.archimedesoft.com (unverified [63.105.19.225]) by pdxpo.dsl-only.net (Rockliffe SMTPRA 4.5.4) with ESMTP id ; Fri, 3 Aug 2001 15:19:07 -0700 Date: Fri, 3 Aug 2001 15:23:22 -0700 From: Tabor Kelly X-Mailer: The Bat! (v1.49) UNREG / CD5BF9353B3B7091 Reply-To: Tabor Kelly X-Priority: 3 (Normal) Message-ID: <137268305.20010803152322@dsl-only.net> To: Tabor Kelly Cc: freebsd-hackers@freebsd.org Subject: Re: problems with kvm_nlist() In-reply-To: <146809363.20010803141617@dsl-only.net> References: <146809363.20010803141617@dsl-only.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As Ian Dowse pointed out, it is not a problem with kvm_nlist(), but with my program (line 75, character 65 should be an "i", not a "0"). Sorry. Now that that is taken care of, would somebody mind explaining to me what n_value represents? Is it an offset in kernel memory to retrieve the actual data? Thank You, Tabor Kelly On Friday, August 03, 2001, 2:16:17 PM, Tabor wrote: I am using kvm_nlist() in one of my programs. I have written a smaller test program for use here. Either kvm_nlist() has a bug or I am very confused. According to kvm_nlist(3), kvm_nlist should go through an array of nlist structures and fill out each structure with that symbol's information. Well, as far as I can tell, it fills out all of the structures with the information from the symbol in the first structure. Has anybody else seen this behavior? Attached is a file named test.cpp that should reproduce this behavior. If you want to play with this behavior, change what structure is pointed to when calling kvm_nlist on line 38 of the program source. Also, be aware that you will have to make the following modifications to the file permissions after you compile it (if you don't want to run it as root): # chown root:kmem a.out # chmod g+s a.out Thank You, Tabor Kelly To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 15:40:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 1C79237B403 for ; Fri, 3 Aug 2001 15:40:51 -0700 (PDT) (envelope-from dphoenix@bravenet.com) Received: (qmail 18151 invoked by uid 1001); 3 Aug 2001 22:48:08 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Aug 2001 22:48:08 -0000 Date: Fri, 3 Aug 2001 15:48:08 -0700 (PDT) From: Dan To: Subject: kernel panics and ipfilter Message-ID: <20010803154143.C70957-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 1) Aug 3 15:41:15 www /kernel: panic: vm_page_remove(): page not found in hash Aug 3 15:41:15 www /kernel: seems box rebooted after that.... freebsd 4.3 release. 2) echo "starting firewall" kldload /modules/ipl.ko ipf -f /etc/ipf.rules another problems with this box is ipfilter.....currently i enable the rules at startup by just kldloading the module basically and installing the ruleset.....problem is when i take down ruleset and redo it, for some reason i cannot connect out anymore unless ruleset is completely removed. It is the exact same ruleset. THe only fix been this far is to just reboot the machine.....i am starting to wonder if there is to much traffic to a box when you enable it right away that ipfilter maybe does not read them all. GOing to try a couple more things but if anyone has experieced this , some input would be most appreciated. -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 15:41:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with SMTP id 772F637B403 for ; Fri, 3 Aug 2001 15:41:05 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6811 invoked from network); 3 Aug 2001 22:41:04 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 3 Aug 2001 22:41:04 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 03 Aug 2001 15:41:04 -0700 (PDT) From: John Baldwin To: hackers@FreeBSD.org Subject: Kernel Summit - Usenix 2001 Cc: developers@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ followups to -hackers only, please ] Yes, this is long overdue. I've collected various notes and IRC logs from the kernel summit at the Usenix 2001 Annual Technical Conference at http://www.FreeBSD.org/~jhb/summit/usenix01/ I still need to write up a summary of the meeting and post it to that site. I also do not have any details on the video tape taken by Jordan at this time. From the webpage: Kernel Summit - Usenix 2001 The first FreeBSD kernel summit meeting was held June 29-30, 2001 in Boston, MA at the Usenix 2001 Annual Technical Conference. Included below are links to various files related to this event. Note: I (jhb) am still working on writing up a general summary of the meeting. When that is completed it will be posted here and mailed to the -hackers mailing list. Document Description agenda.txt Agenda schedule.txt Schedule of Saturday Meeting dillon.txt Written Notes of Saturday's Meeting transcribed by Matt Dillon. dd_irclog.txt IRC Log of the EFNet/#kernelsummit channel covering Friday and Saturday up until the Usenix network connection died. phk_irclog.txt IRC Log of the EFNet/#kernelsummit channel covering Friday and Saturday up until the Usenix network connection died. This log starts later on Friday than the previos log, but it does not have a hole in between the two formal meetings and ends later. nik_irclog.txt IRC Log of the #kernelsummit channel on Peter Wemm's private IRC server setup after the Usenix network died. This covers the rest of the Saturday meeting after the lunch break. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - 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 Fri Aug 3 16:14:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id 543E437B403 for ; Fri, 3 Aug 2001 16:14:30 -0700 (PDT) (envelope-from dphoenix@bravenet.com) Received: (qmail 19849 invoked by uid 1001); 3 Aug 2001 23:21:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Aug 2001 23:21:47 -0000 Date: Fri, 3 Aug 2001 16:21:47 -0700 (PDT) From: Dan To: Subject: ncftpd Message-ID: <20010803162039.F70957-100000@gandalf.bravenet.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ncftpd-2.6.3 i found this to panic the kernel under freebsd latest releases. I simple killall ncftpd just crashed the machine....gonna try upgrading it see if that helps any. ---------- Forwarded message ---------- Date: Fri, 3 Aug 2001 15:48:08 -0700 (PDT) From: Dan To: freebsd-hackers@freebsd.org Subject: kernel panics and ipfilter 1) Aug 3 15:41:15 www /kernel: panic: vm_page_remove(): page not found in hash Aug 3 15:41:15 www /kernel: seems box rebooted after that.... freebsd 4.3 release. 2) echo "starting firewall" kldload /modules/ipl.ko ipf -f /etc/ipf.rules another problems with this box is ipfilter.....currently i enable the rules at startup by just kldloading the module basically and installing the ruleset.....problem is when i take down ruleset and redo it, for some reason i cannot connect out anymore unless ruleset is completely removed. It is the exact same ruleset. THe only fix been this far is to just reboot the machine.....i am starting to wonder if there is to much traffic to a box when you enable it right away that ipfilter maybe does not read them all. GOing to try a couple more things but if anyone has experieced this , some input would be most appreciated. -- Dan +------------------------------------------------------+ | BRAVENET WEB SERVICES | | dan@bravenet.com | | screen;cd /usr/src;make buildworld;cd ~ | | cp MYKERNEL /sys/i386/conf;cd /usr/src | | make buildkernel KERNCONF=MYKERNEL | |make installkernel KERNCONF=MYKERNEL;make installworld| +______________________________________________________+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 17:25: 4 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 41F1B37B401 for ; Fri, 3 Aug 2001 17:25:00 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 4 Aug 2001 01:24:59 +0100 (BST) To: Tabor Kelly Cc: freebsd-hackers@freebsd.org Subject: Re: problems with kvm_nlist() In-Reply-To: Your message of "Fri, 03 Aug 2001 15:23:22 PDT." <137268305.20010803152322@dsl-only.net> Date: Sat, 04 Aug 2001 01:24:59 +0100 From: Ian Dowse Message-ID: <200108040124.aa31753@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <137268305.20010803152322@dsl-only.net>, Tabor Kelly writes: >Now that that is taken care of, would somebody mind explaining to me >what n_value represents? Is it an offset in kernel memory to retrieve >the actual data? It is the kernel virtual address of the symbol that you specified in n_name, which will be the same as an in-kernel pointer value (e.g. something like 0xc0123456). This address has no meaning in userland, but libkvm provides a kvm_read() function that does all the magic necessary to read from the kernel memory at this address. There are lots of examples of code using the libkvm interface in the FreeBSD source tree (fstat, ps, vmstat, pstat etc.) although many of these now use sysctl to retrieve values instead. Briefly, you just kvm_read the value of the variable whose symbol address you have found, e.g. something like the code below, but you'll want to add code to deal with any errors that the kvm_* calls might return. struct nlist nl[] = { {"nextpid"}, {NULL}, }; int nextpid; kd = kvm_openfiles(...); kvm_nlist(kd, nl); kvm_read(kd, nl[0].n_value, &nextpid, sizeof(nextpid)); printf("nextpid is %d\n", nextpid); Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 18:23:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix.sekt7.org (209-6-248-16.c3-0.lex-ubr1.sbo-lex.ma.cable.rcn.com [209.6.248.16]) by hub.freebsd.org (Postfix) with ESMTP id 9BBBB37B407 for ; Fri, 3 Aug 2001 18:23:30 -0700 (PDT) (envelope-from ems@open-root.org) Received: from smtp.sekt7.org (postfix.sekt7.org [169.69.6.38]) by postfix.sekt7.org (Postfix) with SMTP id 97E293A07E for ; Fri, 3 Aug 2001 21:23:22 -0400 (EDT) From: Evan Sarmiento MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15211.20106.216833.788917@smtp.sekt7.org> Date: Fri, 3 Aug 2001 21:23:22 -0400 To: freebsd-hackers@freebsd.org Subject: Re: kern/29423: [PATCH] kernel security hooks implementation In-Reply-To: <200108040120.f741K0w36931@freefall.freebsd.org> References: <200108040115.f741FnO36727@freefall.freebsd.org> <200108040120.f741K0w36931@freefall.freebsd.org> X-Mailer: VM 6.95 under Emacs 19.34.1 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey, Just wanted to send a message to hackers about my project, to find any suggestions, etc. You can access the actual PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=29423 Description: Kernel Security Hooks provide a standard interface for programmers of kernel security extensions to intercept system calls and other functions. Before, programmers had to wrap the system call with their own system call, resulting in two copyins. PRFW, the kernel security hook patch I am addressing in this PR, provides a standard interface for these uses. It also provides per-pid restrictions, so process X might not be able to use setuid but process Y might, depending on what restrictions you write. I have also written a brief howto at http://www.sekt7.org/~ems/prfw.howto You can also download the patch at http://www.sekt7.org/~ems/patch Quick installation: cd /usr/src && patch -p < patch I'm pretty much a kernel newbie, but this is certanly a large achievement for me, to code all this, so take pity, I'm sure my code has problems, but I've tested it and it has worked beautifully. Note: this only works on i386 platform due to a change to i386/i386/trap.c Thanks, - Evan S System: 5.0-CURRENT Patch: diff -c -r --new-file /usr/src/sys/sys/jailuser.h src/sys/sys/jailuser.h *** /usr/src/sys/sys/jailuser.h Wed Dec 31 19:00:00 1969 --- src/sys/sys/jailuser.h Fri Aug 3 16:25:51 2001 *************** *** 0 **** --- 1,97 ---- + /* + * Copyright (c) 2001 Evan M. Sarmiento + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modifcation, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must maintain the above copyright + * notice, this list of conditions and the following disclaimer: + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * + * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ''AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE. EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + + #ifndef _SYS_JAUSR_H_ + #define _SYS_JAUSR_H_ + + #include + #include + #include + + + + struct prfw_usr { + pid_t pid; + int pr_securelevel; + }; + + #ifndef _KERNEL + int prfw_printstat __P((pid_t *, char *, struct prfw_usr *)); + + #else + + #ifdef MALLOC_DECLARE + MALLOC_DECLARE(M_USRJAIL); + MALLOC_DECLARE(M_PRFW); + #endif + + #define ALL 1 + #define ALLBR 2 + #define ALLPR 3 + #define prfw_sl p->p_ucred->cr_prfw->pr_securelevel + + #define IS_PRFW p->p_ucred->cr_prfw + #define IS_RES(x) (x)->p_ucred->cr_prfw + + #define prfw_operation(sl, synum) (p->p_ucred->cr_prfw->prfw_syscall_ind[synum]->operations[sl])(p, uap) + #define prfw_operation_a(sl, synum) (p->p_ucred->cr_prfw->prfw_syscall_ind[synum]->operations[sl])(p, args) + #define prfw_operation_p(sl, synum, p) ((p)->p_ucred->cr_prfw->prfw_syscall_ind[synum]->operations[sl])(p, NULL) + #define prfw_operation_all(sl, synum, rrp) ((rrp)->prfw_syscall_ind[synum]->operations[sl])(p, args) + + struct prfw_krn { + pid_t pr_uid; + int pr_securelevel; + struct prfw_syscall_r *prfw_syscall_ind[SYS_MAXSYSCALL]; + }; + + struct prfw_all_res { + int ex_root; + int sl; + struct prfw_syscall_r *prfw_syscall_ind[SYS_MAXSYSCALL]; + }; + + struct prfw_syscall_r { + int num; + int (*operations[3])(p, uap); + + }; + + + + int prfw_setflags __P((int , pid_t, int)); + int prfw_inject_fp __P((int , int, pid_t , int (*fp)(p, uap))); + int prfw_sy_initres __P((struct prfw_syscall_r *sy_index[])); + int prfw_default_handler __P((struct proc *, void* uap)); + pid_t prfw_chproc __P((struct proc *)); + struct prfw_all_res * prfw_ret_all __P((void)); + int prfw_free __P((pid_t, struct prfw_all_res *, int)); + #endif /* !_KERNEL */ + #endif /* !_SYS_JAUSR_H_ */ + + + + diff -c -r --new-file /usr/src/sys/sys/ucred.h src/sys/sys/ucred.h *** /usr/src/sys/sys/ucred.h Fri May 25 12:59:10 2001 --- src/sys/sys/ucred.h Fri Aug 3 16:26:00 2001 *************** *** 59,64 **** --- 59,65 ---- struct uidinfo *cr_uidinfo; /* per euid resource consumption */ struct uidinfo *cr_ruidinfo; /* per ruid resource consumption */ struct prison *cr_prison; /* jail(4) */ + struct prfw_krn *cr_prfw; struct mtx cr_mtx; /* protect refcount */ }; #define cr_gid cr_groups[0] diff -c -r --new-file /usr/src/sys/kern/kern_jailuser.c src/sys/kern/kern_jailuser.c *** /usr/src/sys/kern/kern_jailuser.c Wed Dec 31 19:00:00 1969 --- src/sys/kern/kern_jailuser.c Fri Aug 3 15:29:45 2001 *************** *** 0 **** --- 1,323 ---- + + /* + * Copyright (c) 2001 Evan M. Sarmiento + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modifcation, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must maintain the above copyright + * notice, this list of conditions and the following disclaimer: + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * + * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ''AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE. EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + */ + + #include + #include + #include + #include + #include + #include + #include + #include + #include + #include + #include + #include + #include + #include + + + /* Init routines. */ + MALLOC_DEFINE(M_PRFW, "process fw", "fw struct"); + + int prfw_queue_status; + int prfw_all_status; + struct prfw_all_res *prfw_allproc; + + /* prfw_setflags(p, uap) + Copies info to struct prfw_tbcp, then inserts it into a list. + when processes are forked(), executed(), or preform functions + they check against that list + */ + int + prfw_setflags(sl, pid, flags) + int sl; + pid_t pid; + int flags; + { + + int error; + int x; + pid_t id; + int p_pri; + + + struct prfw_krn *prfw_tbcp; /* to be copied into proc or list */ + struct prfw_krn *prfw_acc; /* prfw_acc for checking if already exists in list */ + struct prfw_syscall_r *prfw_syscall_ind[SYS_MAXSYSCALL]; + struct proc *nproc; /* used to check if process exists */ + + + p_pri = splvm(); + printf("prfw: Processor priority raised to %d \n", p_pri); + + + id = pid; + + if (id != NULL) + { + if((nproc = pfind(id)) == NULL) + return (0); + } + + + printf("prfw: Found PID %d. Copied PID's proc structure into nproc.\n", id); + + + if (!sl) + return (-2); + + + /* Allocating prfw_tbcp */ + MALLOC(prfw_tbcp, struct prfw_krn *, sizeof *prfw_tbcp, M_PRFW, M_WAITOK|M_ZERO); + + /* Malloc loop for allocating an array of pointers in prfw_syscall_ind + for restrictions */ + + for (x = 0; x < SYS_MAXSYSCALL; x++) + MALLOC(prfw_syscall_ind[x], struct prfw_syscall_r *, sizeof *prfw_syscall_ind * SYS_MAXSYSCALL, M_PRFW, M_WAITOK|M_ZERO); + printf("prfw: prfw_syscall_ind array, which is an array of pointers to prfw_syscall_r structures was malloc'd sucessfully. \n"); + + + prfw_sy_initres(prfw_syscall_ind); + + printf("prfw: prfw_sy_initres finished sucessfully, initalizing function pointers to default_handler \n"); + + if (flags) + { + if (!prfw_all_status) + { + printf("prfw: allproc specified, mallocing \n"); + MALLOC(prfw_allproc, struct prfw_all_res *, sizeof *prfw_allproc, M_PRFW, M_WAITOK|M_ZERO); + prfw_all_status = 1; + prfw_allproc->sl = sl; + printf("prfw: Set prfw_allproc->sl \n"); + + } + if (flags == ALLBR) + { + printf("prfw: setting exclude root bit \n"); + prfw_allproc->ex_root = 1; + } + printf("prfw: inserting prfw_syscall_ind into allproc \n"); + for (x = 0; x <= SYS_MAXSYSCALL; x++) + prfw_allproc->prfw_syscall_ind[x] = prfw_syscall_ind[x]; + printf("prfw: Copied into all. \n"); + splx(p_pri); + return (0); + } + + prfw_tbcp->pr_uid = pid; + prfw_tbcp->pr_securelevel = sl; + + + printf("prfw: Finished copying data to prfw_tbcp\n"); + + for (x = 0; x <= SYS_MAXSYSCALL; x++) + prfw_tbcp->prfw_syscall_ind[x] = prfw_syscall_ind[x]; + + + printf("prfw: Copied prfw_syscall_ind to prfw_tbcp"); + + PROC_UNLOCK(nproc); + PROC_LOCK(nproc); + nproc->p_ucred = crcopy(nproc->p_ucred); + nproc->p_ucred->cr_prfw = prfw_tbcp; + nproc->p_flag |= P_JAILED; + printf("prfw: Info from nproc, securelevel: %d, from default %d \n", nproc->p_ucred->cr_prfw->pr_securelevel, (nproc->p_ucred->cr_prfw->prfw_syscall_ind[3]->operations[sl])(NULL, NULL)); + PROC_UNLOCK(nproc); + printf("prfw_list: Entry: %d %d \n", id, nproc->p_pid); + printf("prfw_tbcp: Entered into its own proc structure. Program is done.\n"); + splx(p_pri); + return (0); + } + + + pid_t + prfw_chproc(p) + struct proc *p; + { + if (p->p_ucred->cr_prfw) + return (p->p_pid); + return (0); + } + + + /* int + prfw_printstat(p, uap) + struct proc *p; + struct prfw_printstat_args *uap; + + { + + struct prfw_usr *prfw_usr; + struct proc *nproc; + pid_t id; + + if (!SCARG(uap, id)) + return (-2); + + + copyin(SCARG(uap, id), &id, sizeof id); + + if((nproc = pfind(id)) == NULL) + return (-1); + + MALLOC(prfw_usr, struct prfw_usr *, sizeof *prfw_usr, M_PRFW, M_WAITOK|M_ZERO); + + prfw_usr->pid = nproc->p_pid; + prfw_usr->pr_securelevel = nproc->p_ucred->cr_prfw->pr_securelevel; + + return(copyout((caddr_t)prfw_usr, (caddr_t)SCARG(uap, prfw_usr), sizeof (prfw_usr))); + + return (0); + } + */ + + int prfw_default_handler(p, uap) + struct proc *p; + void* uap; + { + return (2); + } + + int prfw_sy_initres(sy_index) + struct prfw_syscall_r *sy_index[]; + { + int x; + for (x = 0; x < SYS_MAXSYSCALL; x++) + { + sy_index[x]->num = x; + sy_index[x]->operations[0] = &prfw_default_handler; + sy_index[x]->operations[1] = &prfw_default_handler; + sy_index[x]->operations[2] = &prfw_default_handler; + } + return (0); + } + + + int + prfw_inject_fp(sl, synum, pid, fp) + + int sl; + int synum; + pid_t pid; + int (*fp)(p, uap); + + + + + { + + struct proc *nproc; + int p_pri; + + if (!sl || !synum || !fp || sl > 3) + return (-2); + if (!pid && prfw_all_status) + { + + printf("prfw_inject_fp: Inserting rule into allproc"); + prfw_allproc->prfw_syscall_ind[synum]->operations[sl] = fp; + return (0); + } + else { + printf("prfw_inject_fp: All arguments were sent.\n"); + if ((nproc = pfind(pid)) == NULL) + return (-1); + printf("prfw_inject_fp: Found process. %d \n", pid); + if (!nproc->p_ucred->cr_prfw) + return (-3); + printf("prfw_inject_fp: Process %d is prfwd \n", pid); + + + printf("prfw_injet_fp: Injecting function ptr. \n"); + PROC_UNLOCK(nproc); + PROC_LOCK(nproc); + nproc->p_ucred->cr_prfw->prfw_syscall_ind[synum]->operations[sl] = fp; + PROC_UNLOCK(nproc); + + return (0); + } + return (-1); + } + + + struct prfw_all_res * + prfw_ret_all(void) + { + if (prfw_all_status) + return (prfw_allproc); + return (NULL); + } + + + int + prfw_free(pid, prfw_a, flags) + pid_t pid; + struct prfw_all_res *prfw_a; + int flags; + { + int error; + int x; + struct proc *nproc; + + if ((flags == ALL) && (!(prfw_a))) + return (EINVAL); + if ((flags == NULL) && (!(pid))) + return (EINVAL); + if ((flags == ALLPR) && (!(prfw_a))) + return (EINVAL); + + if ((flags == NULL)) + { + if ((nproc = pfind(pid)) == NULL) + return (ESRCH); + if (!(IS_RES(nproc))) + return (EINVAL); + PROC_UNLOCK(nproc); + PROC_LOCK(nproc); + FREE(nproc->p_ucred->cr_prfw, M_PRFW); + PROC_UNLOCK(nproc); + return (0); + } + if ((flags == ALLPR)) + { + if (!(prfw_all_status)) + return (EINTR); + prfw_all_status = 0; + FREE(prfw_a, M_PRFW); + return (0); + } + if ((flags == ALL)) + { + + return (0); + } + return (-1); + } *** /usr/src/sys/i386/i386/trap.c Wed Jul 18 22:16:24 2001 --- src/sys/i386/i386/trap.c Fri Aug 3 10:41:46 2001 *************** *** 68,74 **** #ifdef KTRACE #include #endif ! #include #include #include --- 68,74 ---- #ifdef KTRACE #include #endif ! #include #include #include #include *************** *** 1029,1036 **** --- 1029,1039 ---- { caddr_t params; int i; + int sysnum; struct sysent *callp; struct proc *p = curproc; + extern int prfw_all_status; + struct prfw_all_res *prfw_a; u_quad_t sticks; int error; int narg; *************** *** 1088,1096 **** if (code >= p->p_sysent->sv_size) callp = &p->p_sysent->sv_table[0]; ! else callp = &p->p_sysent->sv_table[code]; ! narg = callp->sy_narg & SYF_ARGMASK; /* --- 1091,1100 ---- if (code >= p->p_sysent->sv_size) callp = &p->p_sysent->sv_table[0]; ! else { callp = &p->p_sysent->sv_table[code]; ! sysnum = code; ! } narg = callp->sy_narg & SYF_ARGMASK; /* *************** *** 1105,1111 **** #endif goto bad; } ! /* * Try to run the syscall without the MP lock if the syscall * is MP safe. --- 1109,1139 ---- #endif goto bad; } ! ! if (prfw_all_status && ((prfw_a = prfw_ret_all()) != NULL)) ! { ! if (prfw_a->ex_root && (p->p_ucred->cr_ruid != 0)) ! { ! if ((error = prfw_operation_all(prfw_a->sl, sysnum, prfw_a)) < 2) ! return (error); ! } ! if (!(prfw_a->ex_root)) ! { ! if ((error = prfw_operation_all(prfw_a->sl, sysnum, prfw_a)) < 2) ! return (error); ! } ! if (prfw_a->ex_root && (p->p_ucred->cr_ruid == 0)) ! error = 0; ! ! } ! ! ! if (IS_PRFW) ! { ! if ((error = prfw_operation_a(prfw_sl, sysnum)) < 2) ! return (error); ! } ! /* * Try to run the syscall without the MP lock if the syscall * is MP safe. *** /usr/src/sys/conf/files Thu Jul 26 19:04:46 2001 --- src/sys/conf/files Fri Aug 3 10:41:46 2001 *************** *** 758,763 **** --- 758,764 ---- kern/kern_idle.c standard kern/kern_intr.c standard kern/kern_jail.c standard + kern/kern_jailuser.c standard kern/kern_kthread.c standard kern/kern_ktr.c optional ktr kern/kern_ktrace.c standard -- ----------------------------------- Evan Sarmiento | www.open-root.org ems@sekt7.org | www.sekt7.org/~ems/ ----------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 18:26:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 3C03937B401; Fri, 3 Aug 2001 18:26:28 -0700 (PDT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from localhost ([3ffe:501:100f:13ff::a]) by shuttle.wide.toshiba.co.jp (8.9.1+3.1W/8.9.1) with ESMTP id KAA01541; Sat, 4 Aug 2001 10:28:44 +0900 (JST) Date: Sat, 04 Aug 2001 08:11:34 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Poul-Henning Kamp Cc: Andre Oppermann , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel In-Reply-To: <93100.996790166@critter> References: <3B69CE3F.1BCCB280@telehouse.ch> <93100.996790166@critter> User-Agent: Wanderlust/2.5.8 (Smooth) Emacs/21.0 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII X-Dispatcher: imput version 980905(IM100) Lines: 29 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> On Fri, 03 Aug 2001 00:09:26 +0200, >>>>> Poul-Henning Kamp said: >> The problem I've got now is that for every packet I get the kernel is >> making one host entry in the routing table. Because of the many UDP >> DNS requests from all over the world I've got 303'000 (yes, three- >> hundredthreethousand) entries in the kernel routing table which have >> not expired yet. So I'm getting error messages like this now: > Hmm, I wasn't aware that we cloned routes for UDP packets, are you sure > that is what is causing the routes to exists ? (Just to mention the > obvious: it's not CodeRed probes ?) Since udp_output calls in_pcbconnect(), which is shared with TCP and makes cloned host routes, unbound UDP socket can have such routes. However, I guess DNS server implementations do bind(2) specific addresses to UDP sockets, because they have to ensure an query's destination equals to a corresponding reply's source. So, I'd like to see the result of % netstat -f inet -an | grep 53 on the server node to see if the DNS server binds specific addresses. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 21: 4:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web12807.mail.yahoo.com (web12807.mail.yahoo.com [216.136.174.42]) by hub.freebsd.org (Postfix) with SMTP id E907B37B406 for ; Fri, 3 Aug 2001 21:04:31 -0700 (PDT) (envelope-from zaunere@yahoo.com) Message-ID: <20010804040431.59151.qmail@web12807.mail.yahoo.com> Received: from [66.114.66.188] by web12807.mail.yahoo.com; Fri, 03 Aug 2001 21:04:31 PDT Date: Fri, 3 Aug 2001 21:04:31 -0700 (PDT) From: Hans Zaunere Subject: select kevent aio_read To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am new to this level of programming so please bare with me. I am curious as the differences between kevent and select and when to use either one. After reading the man pages, they seem to provide about the same functionality. What advantages do each have, and why would one choose one over the other? Also I am confused as to the purpose of aio_read and family. Any explanation, links or code samples would be great. Thank you, Hans zaunere@yahoo.com __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 22: 8:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 4A97537B406 for ; Fri, 3 Aug 2001 22:08:18 -0700 (PDT) (envelope-from billf@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1098) id 0501681D01; Sat, 4 Aug 2001 00:08:08 -0500 (CDT) Date: Sat, 4 Aug 2001 00:08:07 -0500 From: Bill Fumerola To: Hans Zaunere Cc: freebsd-hackers@freebsd.org Subject: Re: select kevent aio_read Message-ID: <20010804000807.Z2759@elvis.mu.org> References: <20010804040431.59151.qmail@web12807.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010804040431.59151.qmail@web12807.mail.yahoo.com>; from zaunere@yahoo.com on Fri, Aug 03, 2001 at 09:04:31PM -0700 X-Operating-System: FreeBSD 4.3-FEARSOME-20010712 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Aug 03, 2001 at 09:04:31PM -0700, Hans Zaunere wrote: > I am new to this level of programming so please bare > with me. I am curious as the differences between > kevent and select and when to use either one. After > reading the man pages, they seem to provide about the > same functionality. What advantages do each have, and > why would one choose one over the other? Also I am > confused as to the purpose of aio_read and family. > > Any explanation, links or code samples would be great. http://people.freebsd.org/~jlemon/ -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 22:19:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (softweyr.com [208.247.99.111]) by hub.freebsd.org (Postfix) with ESMTP id 5E19337B408 for ; Fri, 3 Aug 2001 22:19:19 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from blabber.softweyr.com ([204.68.178.36] helo=softweyr.com) by softweyr.com with esmtp (Exim 3.22 #1) id 15Su0F-000ADr-00; Fri, 03 Aug 2001 23:29:35 -0600 Message-ID: <3B6B86C5.AB3BAA67@softweyr.com> Date: Fri, 03 Aug 2001 23:23:17 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Pete McKenna Cc: Paul Halliday , Frederique Rijsdijk , freebsd-hackers@FreeBSD.ORG Subject: Re: connecting a FujiFinePix1400 (USB) ? References: <20010801155934.B36262@support.euronet.nl> <3B6839F0.5080906@penix.org> <20010802100233.A8323@otto.oss.qwest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Pete McKenna wrote: > > I can't speak to the camera, but I've found that coldsync > works for my visor. It's in the palm ports. > > pmckenna:more coldsync/pkg-descr > ColdSync is a robust, extensible, portable tool for > synchronizing PalmOS devices (PalmPilot et al.) with a Unix > workstation. It also supports USB connections to a Visor, under > FreeBSD 4.0. > It runs without a GUI, and therefore allows you to sync > without running X. > ColdSync is extensible through the use of conduits, which > allow it to share information with other applications. I've used coldsync under both FreeBSD and OpenBSD with my visor, and found it to work just fine on both systems. It comes with some sample code for developing your own conduits, which I will hopefully someday use to develope across-the-network conduits for the box I work on at work, to sync to our "Family Calendar" feature. Well worth looking into. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 22:26:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 2FEE837B403 for ; Fri, 3 Aug 2001 22:26:17 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.226.Dial1.SanJose1.Level3.net [209.245.140.226]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA08500; Fri, 3 Aug 2001 22:25:50 -0700 (PDT) Message-ID: <3B6B86F0.EAAA016@mindspring.com> Date: Fri, 03 Aug 2001 22:24:00 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: Julian Elischer , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: > > Original poster said he was working on it for Linux, which > > means it's not done, which means "not Linux". > > It's been running for a while now, integrated > in the 2.4 kernel. > > The way Linux manages to avoid the horrors you > describe is by simply not letting the kernel > use more than its 1GB (or 2GB) of KVA. No special > tricks to make the kernel use more memory, let it > go on a diet instead. This is a trivial implementation. I'm not very impressed. In particular, it is the kernel, not the user space, which needs access to more memory. User space is swappable (by the kernel, of course), while only a small fraction of the kernel memory is itself swappable. If the memory were accessible to the kernel, the kernel could swap programs to it, and not have to worry about going to disk. Further, making the RAM only available to user space is trivial; given access to the hardware, I think I could do this with less than a week of elapsed time; it is, IMO, about a days worth of real work. Personally, I'm not interested in a huge user space, so much as I am in supporting more TCP connections, or in supporting full TCP windows sizes for all connections. I've run FreeBSD at 1.6M simultaneous connections, and we are shipping product that can do 1M connections, and do caching and load balancing on top of that. Fully populating both the transmit and receive windows for 1M connections is 32G of RAM, right there... and it better be kernel RAM, or you're screwed. > > FWIW, on the "Linux has it, so FreeBSD should have it" > > arguments: > > > > "If all your friends jumped off a cliff..." > > Fully agreed, but as long as you don't do any > weird tricks trying to let the kernel itself use > more memory, it's not at all like jumping from a > cliff ... I still don't see it being useful, unless it applies to the kernel memory, and then you are basically stuck doing the virtual memory thing in software, like on the PPC or Alpha or MIPS chips, so that you can manage the full address space using descriptor structures for the memory you are accessing, using a fully-faulted address space. For the user space processes, it's not pretty, moving system call parameters from user space to kernel space, if you push the user space up to 4G. I admit that it _may_ be useful for large user spaces, even in the absence of massive amounts of RAM, but then I'm only using two descriptors -- one for the kernel, and one for the user space -- and I need to use a gate to talk between the two, or my kernel won't be there to take the call, so my system calls get more expensive by about a factor of 3. Doing the "graceful" expansion based on when the user space grows above a certain size is extremely problematic. IMO, it is not worth doing this: it complicates and makes more expensive the common case, and there is hardware that you can get that doesn't have this problem. I still haven't seen a useful user space application for this which would not be better handled by having the program in question mmap/munmap regions on its own, since it's guaranteed that the program would do a better job of picking what should or shouldn't be directly accessible without a fault than the kernel ever could... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 22:38:32 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 9927A37B405 for ; Fri, 3 Aug 2001 22:38:29 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (1-072.cwb-adsl.brasiltelecom.net.br [200.193.160.72]) by netbank.com.br (Postfix) with ESMTP id EDDC146805; Sat, 4 Aug 2001 02:37:50 -0300 (BRST) Received: from localhost (fdiuyk@localhost [127.0.0.1]) by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f745cOR18799; Sat, 4 Aug 2001 02:38:25 -0300 Date: Sat, 4 Aug 2001 02:38:23 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: Julian Elischer , craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B6B86F0.EAAA016@mindspring.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 3 Aug 2001, Terry Lambert wrote: > This is a trivial implementation. I'm not very impressed. > Personally, I'm not interested in a huge user space, Maybe not you, but I bet the database and scientific computing people will be interested in having 64 GB memory support in this simple way. > Fully populating both the transmit and receive windows for > 1M connections is 32G of RAM, right there... and it better > be kernel RAM, or you're screwed. Well, you _could_ store this memory in "files", which get mapped and unmapped by the same code the filesystem code uses to access file data in non-kernel-mapped RAM. *runs like hell* regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 22:59:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id B0ACD37B403 for ; Fri, 3 Aug 2001 22:59:33 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from mindspring.com (dialup-209.245.140.226.Dial1.SanJose1.Level3.net [209.245.140.226]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id WAA22992; Fri, 3 Aug 2001 22:56:21 -0700 (PDT) Message-ID: <3B6B8EAC.B4EBD5E8@mindspring.com> Date: Fri, 03 Aug 2001 22:57:00 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rik van Riel Cc: Julian Elischer , craig , freebsd-hackers@FreeBSD.ORG Subject: Re: How to visit physical memory above 4G? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rik van Riel wrote: > > This is a trivial implementation. I'm not very impressed. > > > Personally, I'm not interested in a huge user space, > > Maybe not you, but I bet the database and scientific > computing people will be interested in having 64 GB > memory support in this simple way. You mean 4G, of course, since the process address space remains limites to 32 bits... > > Fully populating both the transmit and receive windows for > > 1M connections is 32G of RAM, right there... and it better > > be kernel RAM, or you're screwed. > > Well, you _could_ store this memory in "files", which > get mapped and unmapped by the same code the filesystem > code uses to access file data in non-kernel-mapped RAM. > > *runs like hell* That's the entire problem: it has to be performant, or I'm just not interested in it. Using the memory as a software L3 would make a lot more sense to me... a 3G user space is pretty useless, from my point of view, and I'd much rather spend the space on the kernel. Cutting that to 2G/2G might be OK, with 1G in the user used for mapping regions in and out. You are still limited to how much RAM you have, but at least you aren't shooting yourself in the foot trying to make it work. You still haven't told me what Linux does for 2x4G processes and a 1G kernel with "only" 8G of physical RAM. I rather suspect that as soon as your usage exceeds real memory, it all goes to hell very quickly, since your L1 and L2 caches are effectively disabled by the frequent reloading of CR3 and CR4 on context switches... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 23: 0:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from netbank.com.br (garrincha.netbank.com.br [200.203.199.88]) by hub.freebsd.org (Postfix) with ESMTP id 8E3DA37B403 for ; Fri, 3 Aug 2001 23:00:04 -0700 (PDT) (envelope-from riel@conectiva.com.br) Received: from surriel.ddts.net (1-072.cwb-adsl.brasiltelecom.net.br [200.193.160.72]) by netbank.com.br (Postfix) with ESMTP id E20AE4680C; Sat, 4 Aug 2001 02:59:25 -0300 (BRST) Received: from localhost (ozbfdo@localhost [127.0.0.1]) by surriel.ddts.net (8.11.4/8.11.2) with ESMTP id f74602R20300; Sat, 4 Aug 2001 03:00:02 -0300 Date: Sat, 4 Aug 2001 03:00:02 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Terry Lambert Cc: Julian Elischer , craig , Subject: Re: How to visit physical memory above 4G? In-Reply-To: <3B6B8EAC.B4EBD5E8@mindspring.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 3 Aug 2001, Terry Lambert wrote: > You still haven't told me what Linux does for 2x4G processes > and a 1G kernel with "only" 8G of physical RAM. I rather > suspect that as soon as your usage exceeds real memory, it > all goes to hell very quickly, since your L1 and L2 caches > are effectively disabled by the frequent reloading of CR3 > and CR4 on context switches... Page tables can point to pages all over memory, there is no need to use stupid segment tricks for anything. regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://distro.conectiva.com/ Send all your spam to aardvark@nl.linux.org (spam digging piggy) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 23: 0:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from softweyr.com (softweyr.com [208.247.99.111]) by hub.freebsd.org (Postfix) with ESMTP id 44E6237B408 for ; Fri, 3 Aug 2001 23:00:07 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from blabber.softweyr.com ([204.68.178.36] helo=softweyr.com) by softweyr.com with esmtp (Exim 3.22 #1) id 15Sudi-000AKv-00; Sat, 04 Aug 2001 00:10:22 -0600 Message-ID: <3B6B9052.5FE460B7@softweyr.com> Date: Sat, 04 Aug 2001 00:04:02 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: Alexander Litvin , freebsd-hackers@freebsd.org Subject: Re: gethostbyXXXX_r() References: <20010803105321.A37737@unknown.whichever.org> <20010803131115.F85642@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Alexander Litvin [010803 09:54] wrote: > > Are there any plans of making gethostbyname_r() and gethostbyaddr_r() > > available in FreeBSD? May be somebody already has them almost ready > > to be commited? Or are there any considered wrong way to go? > > > > The reason I'm asking is that I actually have a local patch implementing > > them here (only for DNS for now). Is it good idea to put some effort to > > finalaze it and submit a PR? Or I'd better not waist time on that? > > Please complete it, let me know when you submit the PR i'll try > to get it integrated. I'll be happy to take a look at it too. I did a lot of the _r routines we have now, in some cases simply documenting ones that were there, but halted when I got to gethostbyX_r and the passwd and group variants, because they were too fugly to tackle at that time. I'll get back to the remainder "someday", when I have the time, unless you beat me to it. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Aug 3 23:23:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from femail42.sdc1.sfba.home.com (femail42.sdc1.sfba.home.com [24.254.60.36]) by hub.freebsd.org (Postfix) with ESMTP id CD0B037B403; Fri, 3 Aug 2001 23:23:22 -0700 (PDT) (envelope-from liquid@dqc.org) Received: from liquid.dqc.org ([24.22.23.246]) by femail42.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010804062322.QSXR374.femail42.sdc1.sfba.home.com@liquid.dqc.org>; Fri, 3 Aug 2001 23:23:22 -0700 Message-Id: <5.1.0.14.2.20010804011926.02fa9ff8@dqc.org> X-Sender: liquid@dqc.org X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 04 Aug 2001 01:23:15 -0500 To: freebsd-hackers@freebsd.org From: Tim Yardley Subject: promise ultra 100 tx2 on 4.3 Cc: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG anyone have plans or already ported the ata pci/dma work in 5.0 over to 4.3 for the tx2 card? rumor has it soren is swamped... anyone else out there brave enough to take on the ata dev tree? you can see the support at (if you dont have 5.0 tree): http://www.nendai.nagoya-u.ac.jp/global/sys/HTML/S/dev%20ata%20ata-pci.c.html http://www.nendai.nagoya-u.ac.jp/global/sys/HTML/S/dev%20ata%20ata-dma.c.html thanks. /tmy -- Diving into infinity my consciousness expands in inverse proportion to my distance from singularity +-------- ------- ------ ----- ---- --- -- --- ------ ------- -------- - --------------+ | Tim Yardley (liquid@dqc.org) | http://nmedia.net/~liquid/ +-------- ------- ------ ----- ---- --- -- --- ------ ------- -------- - --------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 4 1:21:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id AA57537B401; Sat, 4 Aug 2001 01:21:44 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f744UMg01709; Fri, 3 Aug 2001 21:30:49 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108040430.f744UMg01709@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: lists Cc: Mike Smith , Warner Losh , freebsd-hackers@freebsd.org Subject: Re: NewCard / pccbb In-reply-to: Your message of "Fri, 03 Aug 2001 14:49:27 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Aug 2001 21:30:22 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok, now I need your dmesg again, since it's been trimmed and I've lost it. I also need to know what slots you have things in. Please don't cut the $PIR output off this message when you reply. Note that your system is something of a pathalogical worst-case; no PCI recommended interrupts, all the 'major' interrupts available for each slot. It's not improbable that the table is wrong or buggy too. > Here we go, the output as requested: > > $PIR table at 0x2812f7c0 version 1.0 > PCI interrupt router at 0:3.8 vendor 0x1106 device 0x686 > PCI-only interrupts [ ] > entry bus slot device > 00: 00 00 01 INTA 01 [ 3 4 5 7 9 10 11 12 14 15] > INTB 02 [ 3 4 5 7 9 10 11 12 14 15] > INTC 03 [ 3 4 5 7 9 10 11 12 14 15] > INTD 05 [ 3 4 5 7 9 10 11 12 14 15] > 01: 00 00 07 INTA fe [ 14 ] > INTB ff [ 15] > INTC 03 [ 3 4 5 7 9 10 11 12 14 15] > INTD 05 [ 3 4 5 7 9 10 11 12 14 15] > 02: 00 01 09 INTA 02 [ 3 4 5 7 9 10 11 12 14 15] > INTB 03 [ 3 4 5 7 9 10 11 12 14 15] > INTC 05 [ 3 4 5 7 9 10 11 12 14 15] > INTD 01 [ 3 4 5 7 9 10 11 12 14 15] > 03: 00 02 10 INTA 03 [ 3 4 5 7 9 10 11 12 14 15] > INTB 05 [ 3 4 5 7 9 10 11 12 14 15] > INTC 01 [ 3 4 5 7 9 10 11 12 14 15] > INTD 02 [ 3 4 5 7 9 10 11 12 14 15] > 04: 00 03 11 INTA 05 [ 3 4 5 7 9 10 11 12 14 15] > INTB 01 [ 3 4 5 7 9 10 11 12 14 15] > INTC 02 [ 3 4 5 7 9 10 11 12 14 15] > INTD 03 [ 3 4 5 7 9 10 11 12 14 15] > 05: 00 00 12 INTA 01 [ 3 4 5 7 9 10 11 12 14 15] > INTB 00 [ ] > INTC 00 [ ] > INTD 00 [ ] > > > Thanks > > Andrew > On Fri, 3 Aug 2001, Mike Smith wrote: > > > > Tried the patch, interesting thing, for some reason or other its always > > > routing the IRQ to the same IRQ as the realtek network card I have in > > > here, and with the patch in (before nothing worked at all on the pccbb), > > > now if the network card is in slot0 it doesnt work, and the wavelan does, > > > if the wavelan comes first on the pcibus it doesnt work and the network > > > card does. For some reason it always seems to be trying to share an IRQ > > > between these 2, any reason for this? > > > > Yeah; that seems to be the way your system's interrupt routing is set up. > > > > Get http://people.freebsd.org/~msmith/pir.c, build and run it and let's > > look at the output. > > > > -- > > ... every activity meets with opposition, everyone who acts has his > > rivals and unfortunately opponents also. But not because people want > > to be opponents, rather because the tasks and relationships force > > people to take different points of view. [Dr. Fritz Todt] > > V I C T O R Y N O T V E N G E A N C E > > > > > > > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 4 2: 0:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 24A2837B415 for ; Sat, 4 Aug 2001 02:00:39 -0700 (PDT) (envelope-from oppermann@telehouse.ch) Received: (qmail 68362 invoked from network); 4 Aug 2001 09:00:06 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.21.234]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 4 Aug 2001 09:00:06 -0000 Message-ID: <3B6BB99C.ED16B804@telehouse.ch> Date: Sat, 04 Aug 2001 11:00:12 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: JINMEI@telehouse.ch, Tatuya@telehouse.ch, /@telehouse.ch, "$B?\"@L@C#:H"@FreeBSD.ORG Cc: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel References: <3B69CE3F.1BCCB280@telehouse.ch> <93100.996790166@critter> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JINMEI Tatuya / $B?@L@C#:H(B wrote: > > >>>>> On Fri, 03 Aug 2001 00:09:26 +0200, > >>>>> Poul-Henning Kamp said: > > >> The problem I've got now is that for every packet I get the kernel is > >> making one host entry in the routing table. Because of the many UDP > >> DNS requests from all over the world I've got 303'000 (yes, three- > >> hundredthreethousand) entries in the kernel routing table which have > >> not expired yet. So I'm getting error messages like this now: > > > Hmm, I wasn't aware that we cloned routes for UDP packets, are you sure > > that is what is causing the routes to exists ? (Just to mention the > > obvious: it's not CodeRed probes ?) > > Since udp_output calls in_pcbconnect(), which is shared with TCP and > makes cloned host routes, unbound UDP socket can have such routes. > > However, I guess DNS server implementations do bind(2) specific > addresses to UDP sockets, because they have to ensure an query's > destination equals to a corresponding reply's source. So, I'd like to > see the result of > > % netstat -f inet -an | grep 53 Ok, here is the output: # netstat -f inet -an | grep 53 udp4 0 0 194.42.48.120.53 *.* > on the server node to see if the DNS server binds specific addresses. Yes, it does. > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center, Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 4 2: 2: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id CF9EF37B403 for ; Sat, 4 Aug 2001 02:01:56 -0700 (PDT) (envelope-from oppermann@telehouse.ch) Received: (qmail 68388 invoked from network); 4 Aug 2001 09:01:28 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.21.234]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 4 Aug 2001 09:01:28 -0000 Message-ID: <3B6BB9EF.1922470@telehouse.ch> Date: Sat, 04 Aug 2001 11:01:35 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: 303,000 routes in kernel References: <20010803190059.A63933811@overcee.netplex.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm wrote: > > Poul-Henning Kamp wrote: > > In message <3B69CE3F.1BCCB280@telehouse.ch>, Andre Oppermann writes: > > > > >The problem I've got now is that for every packet I get the kernel is > > >making one host entry in the routing table. Because of the many UDP > > >DNS requests from all over the world I've got 303'000 (yes, three- > > >hundredthreethousand) entries in the kernel routing table which have > > >not expired yet. So I'm getting error messages like this now: > > > > Hmm, I wasn't aware that we cloned routes for UDP packets, are you sure > > that is what is causing the routes to exists ? (Just to mention the > > obvious: it's not CodeRed probes ?) > > Dont forget that DNS can query you over tcp as well.. This machine (with djb tinydns) does not have tcp queries enabled. So this can't be the source of the route entries. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 4 2: 6:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 6FD1A37B401 for ; Sat, 4 Aug 2001 02:06:05 -0700 (PDT) (envelope-from oppermann@telehouse.ch) Received: (qmail 68525 invoked from network); 4 Aug 2001 09:05:37 -0000 Received: from unknown (HELO telehouse.ch) ([62.48.21.234]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 4 Aug 2001 09:05:37 -0000 Message-ID: <3B6BBAE7.D572B4CB@telehouse.ch> Date: Sat, 04 Aug 2001 11:05:43 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jasper Wallace Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: 303,000 routes in kernel References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jasper Wallace wrote: > > On Fri, 3 Aug 2001, Andre Oppermann wrote: > > > Hello guys > > > > have got a small problem. I'm running a secondary DNS server for the > > ccTLD .ch here in Switzerland. > > > # vmstat -m > > Memory statistics by type Type Kern > > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > > ... > > routetbl607857 85480K 85480K 85480K 2420956 0 0 > > 16,32,64,128,256 > > ... > > Memory Totals: In Use Free Requests > > 91073K 2948K 786316696 > > If you want to wack up the amount of ram used for the routing table you can > adjust the amount of ram the kernel uses for it's stuff with something like > this in your kernel config file: > > # 1/2 RAM for the kernel - lets us have full routes. > options VM_KMEM_SIZE_SCALE="(2)" > > If anyone knows a better way to persuade the kernel to use more space for > the routing table i'd love to know. On some machines that do routing and have a full view in the kernel I do this is in /boot/loader.conf: kern.vm.kmem.size="128000000" # Sets the size of kernel memory (bytes) But this is not very optimal because only half of the kernel memory can be used for the routing table. The other half (64MB here) is mostly empty. I'l like to know if there is a way to adjust this ratio in the kernel so I get 96MB for the routing table and 32MB for the kernel itself. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Aug 4 2:33:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from security.za.net (security.za.net [196.2.146.22]) by hub.freebsd.org (Postfix) with ESMTP id 4894B37B403; Sat, 4 Aug 2001 02:33:00 -0700 (PDT) (envelope-from lists@security.za.net) Received: from localhost (lists@localhost) by security.za.net (8.11.4/8.11.4) with ESMTP id f749Wst97079; Sat, 4 Aug 2001 11:32:54 +0200 (SAST) (envelope-from lists@security.za.net) Date: Sat, 4 Aug 2001 11:32:54 +0200 (SAST) From: lists To: Mike Smith Cc: Warner Losh , freebsd-hackers@freebsd.org Subject: Re: NewCard / pccbb In-Reply-To: <200108040430.f744UMg01709@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Mike, ok my pci->pcmcia bridge is in slot 0, my network card is in slot 3, below are the dmesg outputs from both oldcard and newcard, Thanks Andrew Newcard dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #16: Sat Aug 4 11:09:22 SAST 2001 root@vortexia.orbtech.pvt:/usr/obj/usr/src/sys/VORTEXIA Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 851941527 Hz CPU: Pentium III/Pentium III Xeon/Celeron (851.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 125763584 (122816K bytes) avail memory = 116891648 (114152K bytes) Preloaded elf kernel "kernel" at 0xc046f000. Pentium Pro MTRR support enabled Using $PIR table, 6 entries at 0xc00f77c0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 (no driver attached) pci0: at 7.3 (no driver attached) pci0: at 7.4 (no driver attached) pci0: at 7.5 (no driver attached) pccbb0: at device 9.0 on pci0 pccbb0: PCI Memory allocated: 44000000 pci_cfgintr_virgin: using routable interrupt 3 pci_cfgintr: 0:9 INTA routed to irq 3 cardbus0: on pccbb0 pccard0: <16-bit PCCard bus> on pccbb0 rl0: port 0xc800-0xc8ff mem 0xdfffff00-0xdfffffff irq 12 at device 11.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:50:bf:3f:bb:9d miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0: