How to dump the stack trace for other CPU
Hi, How does one go about dumping the stack trace for the other cpu while in ddb or gdb? This is on current. Thanks, Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netscape
[EMAIL PROTECTED] wrote: > Kris Kennaway wrote: > > > On Sun, 23 Jul 2000 [EMAIL PROTECTED] wrote: > > > > > Netscape 4.74 is already out but FreeBSD 4.1-RC2 contains 4.73 version > > > yet. Will FreeBSD 4.1-RELEASE contains the last version (4.74) of > > > Netscape Communicator and Navigator? > > > > No. The ports tree has been frozen. > > If there will be "FreeBSD 4.1-RC3+" will it contains the newer version of > Netscape? Are the fixed in Netscape 4.74 bugs not critical for release? > Thanks. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message One of the big things they fixed is LDAP. You can now use the ldap search facility in the address book. Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Anyone able to extract Apple Airport Firmare from the 1.3 software?
Hi, Anyone out there able to extract the firmware for the apple airport that is embedded in the 1.3 version of the software? Perhaps someone with a MAC could send me the file? Thanks, Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gdb -k not able to access BSS?
Hi, I was trying to debug a problem where sound card is not working because it ends up with a irq that is shared with the VGA card. So I figured I'd use gdb to look at the interrupt handler vector to see what was there and to find out what is going on. However gdb is unable to dump the data : munin# gdb -k -wcore -s ./kernel.debug 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) print intr_handler Cannot access memory at address 0xc0395b80. (kgdb) x/20x 0xc0395b80 0xc0395b80 : Cannot access memory at address 0xc0395b80. Anyone got an idea? Nm on the running kernel agrees with the above address. munin# nm /boot/kernel/kernel | fgrep intr_handler c0395b80 B intr_handler Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Compaq wl100 driver?
Hi, Has anyone ported the prism2 driver from linux to FreeBSD to run the Compaq/Samsung etc wl100 wireless ethernet cards? Anyone writing a new driver for it? Thanks, Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
environment variable for resolv.conf anyone?
Hi, I find myself connected to multiple networks and domains all the time, and was wondering if anyone has solved (without using a chroot environment) using a different resolv.conf for different shells? One solution I thought off was to change the resolver library to look for an environment variable and if that was set, to use the file it pointed to instead of being hardcoded to /etc/resolv.conf as it is today. Anyone have an opinion on the general usefulness of this idea, and whether it poses a security risk? Thanks, Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: environment variable for resolv.conf anyone?
Hi, Yes I have thought of that. I ran into a few issues that I thought made the solution cumbersome. Perhaps you solved these in a way that makes them dissapear? 1) Need to always use fully qualified names (only a problem when there are duplicates) 2) Need to bounce named a lot to avoid having records for networks that are not currently connected to. (perhaps sufficient to edit search line in resolv.conf each time a network gets added/deleted.) 3) If the remote network consists of lots of subdomains the named config becomes rather large. Lars Andrea Campi wrote: > This is my only message in this thread, it's out of topic. > > On Thu, Nov 30, 2000 at 01:58:59PM -0600, Lars Fredriksen wrote: > > Hi, > > > > I find myself connected to multiple networks and domains all the time, > > and was wondering if anyone has solved (without using a chroot > > environment) using a different resolv.conf for different shells? > > Have you thought about running your own non-authoritative DNS? If you use > djbdns, this gives you the added benefit of being able to easily specify > which DNS is authoritative for special, local domains. In general, having > your local, caching-only (in bind parlance) DNS gives you better security > and flexibility, and it's very easy to maintain. All of my machines, clients > and servers, run like that, and I never had any problem. > > Bye, > Andrea > > -- >Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
default route not set up??
Hi, I must be missing something If you set "defaultrouter" in /etc/rc.conf to an ip address, I expected that rc.network would do a route add default ..., but instead I find that rc.network doesn't do anything with the defaultrouter variable except to pass it on to the route_default variable, which doesn't seem to be used at all. What am I missing here??? Lars To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: default route not set up??
Hi,
There are two things going on with the route setup.
if [ "x$defaultrouter" != "xNO" ] ; then
static_routes="default ${static_routes}"
route_default="default ${defaultrouter}"
fi
1) since route_default is never used, it should be deleted, ignore that
line above.
2) if you set defaultrouter to anything other than "NO", the
static_route variable gets a "default" route
route label added, and this label will get evaled later on.
So rc.conf should read: (example from my setup)
defaultrouter="YES" # Set to default gateway (or NO).
static_routes="local" # Set to static route list (or leave
empty).
route_local=" -net "
route_default=" default "
So, two actions are needed. The route_default line from rc.network should
get deleted, and the comment
in rc.conf for the defaultrouter variable should be clearer.
If others agree, I can go and commit the fixes for that
Lars
Andreas Braukmann wrote:
> Hi,
>
> On Sat, May 01, 1999 at 03:18:23PM +0200, Dag-Erling Smorgrav wrote:
> > "Daniel C. Sobral" writes:
> > > Dag-Erling Smorgrav wrote:
> > > > # Configure routing
> interesting code deleted ... [..]
> > > Looking there, it *does* seem that there is a problem. defaultrouter
> > > is only used to set route_default, which is *not* used. At least on
> > > the code you quoted.
> > This is getting fun :) Look closer at the first line I commented, then
> > at the loop, and especially the eval.
>
> since I've stumbled over the same 'what the the hell is going on
> here?'-piece of shell script once upon a time, I've foreseen the
> further development of this after having read the first two
> messages.
> I had to set a few static routes, saw the empty 'static_routes'
> configuration variable and just didn't grasped "what to do know"
> with that variable.
> I considered, that there has to be some underlying 'magic' similar
> to the method used for the interface configuration.
> Despite of this cognition I had to jump head first into the
> rc.network script to investigate on 'how to use' the core variable
> (static_routes) and the supplementary variables the right way.
>
> It would be very nice, if 'somebody' (TM) would document the
> various 'dark magic' parts of the rc scripts.
>
> But, ... a person priviledged to setup the routing for
> a system (aka system administrator aka 'root') should really be
> able to parse 'sh'-code, shouldn't he?
>
> -Andreas
>
> --
> : TSE TeleService GmbH : Gsf: Arne Reuter: :
> : Hovestrasse 14: Andreas Braukmann : We do it with :
> : D-48351 Everswinkel : HRB: 1430, AG WAF : FreeBSD/SMP:
> ::
> : Anti-Spam Petition: http://www.politik-digital.de/spam/:
> : PGP-Key: http://www.tse-online.de/~ab/public-key:
> : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B :
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: default route not set up??
Thanks for setting me straight! I am backtracking trying to find out what I
did wrong initially when I tried to set it up. I certainly botched the
debugging part :-(
Lars
Stefan Bethke wrote:
> Don't!
>
> --On Son, 2. Mai 1999 12:44 Uhr -0500 Lars Fredriksen
> wrote:
>
> > So rc.conf should read: (example from my setup)
> >
> >
> > defaultrouter="YES" # Set to default gateway (or NO).
> > static_routes="local" # Set to static route list (or leave
> > empty).
> > route_local=" -net "
> > route_default=" default "
> >
> > So, two actions are needed. The route_default line from rc.network should
> > get deleted, and the comment
> > in rc.conf for the defaultrouter variable should be clearer.
> >
> > If others agree, I can go and commit the fixes for that
>
> Don't! Look at rc.network again. If you don't get it, run the code with
> set -vx, and see what happens.
> The correct entry still is:
>
> defaultrouter="1.2.3.4"
>
> For your convenience, I'm posting the complete snipped again:
>
> # Configure routing
>
> if [ "x$defaultrouter" != "xNO" ] ; then
> static_routes="default ${static_routes}"
> route_default="default ${defaultrouter}"
> fi
>
> # Set up any static routes. This should be done before router
> discovery.
> if [ "x${static_routes}" != "x" ]; then
> for i in ${static_routes}; do
> eval route_args=\$route_${i}
> route add ${route_args}
> done
> fi
>
> Stefan
>
> --
> Stefan Bethke
> Muehlendamm 12Phone: +49-40-256848, +49-177-3504009
> D-22087 Hamburg
> Hamburg, Germany
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
