Re: Removal of netns

ubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-net" in the body of the message > > --=20 > Darcy Buskermolen > Wavefire Technologies Corp. > ph: 250.717.0200 &

Re: Removal of netns

IL PROTECTED] > > with "unsubscribe freebsd-net" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED

Re: HEADS UP: cvsup cvs-supfile users!

Stijn Hoop wrote: > On Tue, Mar 04, 2003 at 11:10:45AM -0800, Peter Wemm wrote: > > Anybody who uses the cvs-supfile example to get the repository should add > > "cvsroot-all" to their supfile. This is in addition to src-all, ports-al= > l, > > doc-all etc.

Re: Removal of netns

8:42:19; author: jkh; state: Exp; lines: +3 -1 branches: 1.7.2; Bring back netns so that Netcon can take over support for it, as agreed. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars

Re: Removal of netns - politically correct version

ng: function declaration isn't a prototype ../../../netns/spp_usrreq.c:1531: warning: return type defaults to `int' ../../../netns/spp_usrreq.c:1531: warning: function declaration isn't a prototype ../../../netns/spp_usrreq.c:1559: warning: function declaration isn't a prototype ../..

HEADS UP: cvsup cvs-supfile users!

ed by this. I have updated cvs-supfile in -current but not RELENG_4 yet. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with &qu

Re: Problem in /usr/src/sys/boot/i386/boot2

ient at doing 64 bit operations and this has blown boot2's code size through the roof. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [

Re: cvs commit: src/sys/alpha/alpha busdma_machdep.c src/sys/alpha/osf1 imgact_osf1.c osf1_misc.c src/sys/cam cam_periph.c cam_sim.c cam_xpt.c src/sys/cam/scsi scsi_cd.c scsi_ch.c scsi_da.c scsi_low.c scsi_sa.c scsi_target.c src/sys/coda cnode.h ...

cktrace(); > + flags |= M_WAITOK; > + } Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ACPI thermal panics ThinkPad 600X

have helped you. That's src developers only, not public. Do not cross-post src-committers with -current either. If you really want to have a public discussion, post to -current, and then a second "hey, look over on -current" to src-developers@. Or do a bcc: src-developers or somethin

Re: The cbus driver for pc98

things would get ugly very quickly. Personally, I would rather live with #ifdef PC98 than to have a duplicate set of isa/* and i386/* files that are nearly identical except for include file paths, #ifdef PC98 and s/isa/cbus/. I'm sure there are other ways to improve the situation without hav

ia64 tinderbox failure

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ia64 tinderbox failure

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ia64 tinderbox failure

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ia64 tinderbox failure

To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Hyperthreading and machdep.cpu_idle_hlt

tion that we're in right now. :-( Personally, I doubt that HTT will buy much on FreeBSD, apart from being buzzword compliant. I'd actually like a compile option or boot tunable so that it to be turned on or off (and treated like a regular Xeon SMP system). Single-physical-cpu systems

Re: Undefined symbol "__xuname"

see if it is using libc.so.4 or libc.so.5. If it is using libc.so.4, then that is your problem.. > > thanks, > scott > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > Cheers, -Peter -- Peter Wemm -

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: SMP hang at boot on Compaq Proliant ML370

this does not help, the server > >> still hangs. > >> > I also removed the ata driver, without success. :-( > >> > >> Is the ML370 a new box? I've heard rumors recently that one > >> of the recent Compaq boxes effectively doesn't generate clock > >> interrupts in SMP mode and there isn't a workaround for that > >> at the moment. > >> > >> -- > >> > >> John Baldwin <[EMAIL PROTECTED]> <>< > >> http://www.FreeBSD.org/~jhb/ "Power Users Use > the Power to > >> Serve!" - http://www.FreeBSD.org/ Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: Geom disklabel/fdisk issues?

roblems as it wouldn't have to parse GPT tables. Personally, unless EFI on i386 actually gets off the ground, if somebody is seriously considering this, I'd be inclined to suggest using a fairly loose gpt interpretation and using gpt as a replacement for disklabel inside a freebsd slice.

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: Serious issues with kqueue on sockets on CURRENT.

--- revision 1.136 date: 2002/11/05 18:48:46; author: kbyanc; state: Exp; lines: +1 -1 Fix filt_soread() to properly flag a kevent when a 0-byte datagram is received. Verified by:dougb, Manfred Antar <[EMAIL PROTECTED]> Sponsored by: NTT Multimedia Communications La

Re: Serious issues with kqueue on sockets on CURRENT.

ed then they need to know that too. But overflowing re@ with email is not a good way to get the release polished off. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: Rather verbose ACPI errors.

arding the ACPI code to enable the second serial port (pin header on motherboard). It will go away if/when tyan fix the bios. They broke this in a recent "upgrade". Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we do

Re: alpha tinderbox failure

Peter Wemm wrote: > Kris Kennaway wrote: > > > > --AhhlLboLdkugWU4S > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > > > Can someone please fix whereintheworld to grok the new make regression > > test output, so it d

Re: alpha tinderbox failure

: GnuPG v1.0.6 (GNU/Linux) > Comment: For info see http://www.gnupg.org > > iD8DBQE+Fs2IWry0BWjoQKURAjkGAKDHg95MMoekBGd8JE9YiLJ6yZGMzgCff6zU > 5p6oDcHQCz1j82XpAElV24w= > =DfCz > -END PGP SIGNATURE- > > --AhhlLboLdkugWU4S-- > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe f

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: 5.0 showstopper

/* 16K is an arbitrary buffer >* in case the swap part is >* the first part >*/ > printf("\nDump failed. Partition too small.\n"); > return; > } We use

Re: cvs(1) assertion failure

he cvs server, not our client. And it very clearly is not a freebsd cvs build, as that is something from the gcc/libstdc++ includes. (check out cstring etc) ie: the server that you are trying to use has been ported from C to C++ and most likely built with g++. Cheers, -Peter -- Peter Wemm - [EMAIL PROT

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: ata-dma.c missing from Makefile

ch': > /usr/src/sys/dev/ata/ata-all.c:264: undefined reference to `ata_dmafreetags' ata-dma.c is compiled when ata *and* pci are specified. Are you trying to build a pci-less system? If so, you probably need to add the 'options ATA_NOPCI' entry to your kernel. Cheers, -Pet

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: Can't resolve hosts via dns on the command line with latest -current

isted and 127.0.0.1 first, then I get a 10-20 second timeout before the resolver library switches to another server. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: __sF

lso need to do something about that so that you get the right #includes. libf96.so is a 4.x binary. Even if it wasn't for __sF, you should be compiling with 4.x libraries and (if needed) 4.x headers, because you have parts of the 4.x stdio.h embedded in libf96.so. Cheers, -Peter -- Peter W

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: libc size

Dan Nelson wrote: > In the last episode (Oct 30), Doug Rabson said: > > On Wed, 30 Oct 2002, Peter Wemm wrote: > > > We've been over this before. To make this work right, we need to > > > make /bin and /sbin dynamically linked. NetBSD's /rescue/* > > &

Re: libc size

Terry Lambert wrote: > Peter Wemm wrote: > > Terry Lambert wrote: > > > Nate Lawson wrote: > > > > Here is a link to the size of various components of libc, sorted by tex t > > > > size. If you can find some way to reduce or even remove s

Re: libc size

o this should avoid dragging in a lot of it. We've been over this before. To make this work right, we need to make /bin and /sbin dynamically linked. NetBSD's /rescue/* approach would solve the "oops!" and other foot shooting problems. Cheers, -Peter -- Peter Wemm - [EMA

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: HEADS UP: you need to install a new kernel before an installworld.

"M. Warner Losh" wrote: > In message: <[EMAIL PROTECTED]> > Tim Kientzle <[EMAIL PROTECTED]> writes: > : Peter Wemm wrote: > : > : > 'make installworld' without ... a new kernel would be rather messy. > : > : > ... a remin

Re: A success story, of sorts

another method that it calls to do this, and this is driven by the kthread acpi_fan or acpi_thermal, I dont remember exactly. ".tz0." is "thermal zone 0". There may be more than one zone, especially in larger servers. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL P

Re: options GEOM and NODEVFS

portability issues. Some of the folks on freebsd-emulation may be able to do it. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED]

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: Local DNS lookup by sshd?

mpty. This means, that it cannot see any /etc/nsswitch.conf and cannot see any /etc/resolv.conf or /etc/hosts. And the resolver client library defaults querying on the first interface, and in your case it used localhost. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMA

Re: alpha tinderbox failure

is because the kernel was old on beast (fixing now), but thats not the point. We're always going to get this, so the -static workaround probably needs to remain, or we are using the wrong groff binary or something. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [E

HEADS UP: you need to install a new kernel before an installworld.

ld 5.x binaries around in /usr/local etc. options COMPAT_43 is checked at compile time on the alpha now. It is still compulsory until somebody fixes longjmp in libc to use ucontext_t instead of struct osigcontext. This really needs to be done before 5.0 is released. Cheers, -Peter -- Peter Wemm -

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

mozilla vs linux emulation in -current?

t have installed and have never used. I removed pcm from this machine. It seems mozilla is trying to connect to port 16001, and for some reason it is going out on the wire now.. :-( Isn't tcp supposed to stop this sort of thing from going onto the wire? Cheers, -Peter -- Peter Wemm - [EMAIL PRO

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

ia64 tinderbox failure

-- >>> Rebuilding the temporary build tree -- >>> stage 1: bootstrap tools -- >>> stage 2: cleaning up the object tree

Re: alpha tinderbox failure

However, there are hundreds more failures after this. Fixing this one just gets us to the next failure. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: HEADS UP: Old port recompiles needed (Re: Unknown symbol "__sF")

going to be upgrading from 4.6-RELEASE and 4.7-RELEASE? Add COMPAT4X=true to your make.conf. We added __stdoutp etc to RELENG_4 and included it in the last two releases. -current's COMPAT4X stuff has the updated libc.so.4 with these symbols. If you want to run 4.x binaries, you need COMPAT4

Re: HEADS UP: Old port recompiles needed (Re: Unknown symbol "__sF")

/usr/lib/old] mv /usr/lib/lib*.so.* /usr/lib/compat mv /usr/lib/*.o /usr/lib/lib*.a /usr/lib/lib*.so /usr/lib/old make installworld This guarantees a clean /usr/include and /usr/lib after finishing. Dynamic binaries keep running because they find their libraries in /usr/lib/compat. But ld(1) will

Re: Rev. 1.48 of stdio.h breaks 3rd part software

bf96.a - lm > /usr/libexec/elf/ld: warning: cannot find entry symbol _start; defaulting to 08048d1c > /usr/lib/libc.so: undefined reference to `environ' > /usr/lib/libc.so: undefined reference to `__progname' > /usr/local/lib/NAGWare/libf96.so: undefined refere

Re: i386 tinderbox failure

build now works for me whereas it didn't before), but I > haven't yet finished a completed buildworld. Let me know if not and we > can tweak more. Gah! I cannot win today. :-( Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All

<    1   2   3   4   5   6   7   8   9   >