No Subject

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

No Subject

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

Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH))

Hi, From: Cy Schubert - ITSD Open Systems Group <[EMAIL PROTECTED]> > > I was not talking about things that constitute the "real" core of the > > distribution (kernel, basic libraries etc.). I was more thinking about > > "userland" stuff that is included in the distribution but might not be > > r

k4 in current

anyone out there using kerberos4 in current? i am not succeeding in a mixed current/stable/bsdi/... environment. o the current systen is the keyserver o anyone of the systems can get a tgt o given a tgt, the stable/bsdi systems can all rlogin/rsh to eachother just fine o a user on th

Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH))

< said: > This is going in the right direction, but here is a question (and I don't > have the answer). Is it so much more easier to create new compile time > directive than to go the extra step and use packages where they are > available ? For example "bind8" is available as a package. Why not h

k4 in current

< said: > anyone out there using kerberos4 in current? i am not succeeding in a mixed > current/stable/bsdi/... environment. > o the current systen is the keyserver You mean KDC, of course. > o a user on the current system rlogging in to a stable or bsdi system > succeeds with the rlo

No Subject

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

Re: Weak symbols (Was: World breakage in libc_r?)

In article , <[EMAIL PROTECTED]> wrote: > On 15-Oct-99 at 15:05, John Birrell ([EMAIL PROTECTED]) wrote: > > > A weak symbol is like an alias for another (strong) symbol. The > > linker will link to strong symbols first, then, for any unresolved > > references, i

-current problems with the lates pccard changes?

Hi, after upgrading my Tecra-8000 to -current as of -now I get the attached output during boot. And the ep0 driver doesnt get attached with the following message: Cannot allocate ports 0x240-0x24f Does the output look normal? Particularly the muliple attaches worries me. Does anyone else see thi

Re: -current problems with the lates pccard changes?

Michael Reifenberger wrote: > Hi, > after upgrading my Tecra-8000 to -current as of -now I get the attached output > during boot. > And the ep0 driver doesnt get attached with the following message: > Cannot allocate ports 0x240-0x24f I have been getting the same with yesterday's and today's wor

make world failing on current

I've been trying a make world for the last few days. I finally removed my src tree and CVSup'ed the complete tree again but it i still failing in the same place. I don't know how to get past this. Can anyone offer some enlightenment? :) Thanks. Output of make world: ===> f77doc /usr/obj/us

duplicate filenames under Linux emulation

I noticed that I often get duplicate filenames when running programs under Linux emulation. Attached below is a directory listing, in which the file bxutils-c.c is listed twice under Linux. I don't think the problem is ls(1) related, as I remember seeing duplicate names in file selection boxes a

Signal 12 during build of -current

I'm installing -current on a FreeBSD-3.3-stable system. I've done the sup (which succeeded with no problems). When I try the "make buildworld" I get "signal 12" crashes during the gcc lib build. In specific: -- echo '#include ' > config.h echo '#include ' >> config.h echo '#include "i386/xm-i3

-current crash

Hi, I got the following crash since a couple of time since upgrading one machine to -current as of today. It seems to occurs during somewhat heavier diskaccess. Sorry no detailed backtrace for now because I deleted my kernel.debug since the last crash and dumping 256MB takes a long time... Does

Re: -current crash

Well, a DDB traceback would help. Failing that, at least what does 0xc101891b correspond to otherwise, it's all ENOGUESS On Sun, 17 Oct 1999, Michael Reifenberger wrote: > Hi, > I got the following crash since a couple of time since upgrading one machine to > -current as of today. It s

Re: make.conf options (was Re: package-like feature for the basedistrib (was Re: FreeSSH))

On Sun, 17 Oct 1999, Garrett Wollman wrote: ;->< said: ;-> ;->> This is going in the right direction, but here is a question (and I don't ;->> have the answer). Is it so much more easier to create new compile time ;->> directive than to go the extra step and use packages where they are ;->> avail

Re: -current crash

On Sun, 17 Oct 1999, Matthew Jacob wrote: ... > Well, a DDB traceback would help. Failing that, at least what does > 0xc101891b correspond to otherwise, it's all ENOGUESS Next try, next crash. No problem. Easy crashing :-) I tried to find the address 0xc101891b using nm(1) but can't seem

Re: -current crash

On Sun, Oct 17, 1999 at 10:42:51PM +0200, Michael Reifenberger wrote: [...] > #3 0xc02117b1 in trap_pfault () > #4 0xc0211313 in trap () > #5 0xc101891b in ?? () > #6 0xc1018752 in ?? () > #7 0xc101854e in ?? () > #8 0xc0186a66 in spec_strategy () > #9 0xc018601d in spec_vnoperate () [...]

Re: -current crash

Doesn't tell *me* a lot maybe a broken driver that's a KLD? It looks like something from spec_strategy is being called that's not in the /kernel space- could be a KLD- are your KLDs up to date for the new kernel? Like, is this vinum perhaps? > On Sun, 17 Oct 1999, Matthew Jacob wrote: > ...

Re: -current crash

On Mon, 18 Oct 1999, Bernd Walter wrote: ... > What kind of modules were you running? (nullum)(root)# kldstat Id Refs AddressSize Name 17 0xc010 1eb518 kernel 21 0xc02ec000 cdbc bktr.ko 31 0xc1011000 c3000vinum.ko 41 0xc000 6000 procfs.ko 51 0

Re: -current crash

Try it w/o vinum, procfs and nfs kernel objects. On Mon, 18 Oct 1999, Michael Reifenberger wrote: > On Mon, 18 Oct 1999, Bernd Walter wrote: > ... > > What kind of modules were you running? > (nullum)(root)# kldstat > Id Refs AddressSize Name > 17 0xc010 1eb518 kernel > 2

Re: -current crash

On Sun, 17 Oct 1999, Matthew Jacob wrote: > Date: Sun, 17 Oct 1999 15:08:10 -0700 (PDT) > From: Matthew Jacob <[EMAIL PROTECTED]> > To: Michael Reifenberger <[EMAIL PROTECTED]> > Cc: FreeBSD-Current <[EMAIL PROTECTED]> > Subject: Re: -current crash > > > Doesn't tell *me* a lot maybe a brok

Re: -current crash

On Mon, 18 Oct 1999, Greg Lehey wrote: > Date: Mon, 18 Oct 1999 12:16:19 +1300 > From: Greg Lehey <[EMAIL PROTECTED]> > To: Michael Reifenberger <[EMAIL PROTECTED]>, Matthew Jacob <[EMAIL PROTECTED]> > Cc: FreeBSD-Current <[EMAIL PROTECTED]> > Subject: Re: -current crash ... > Have you rebui

Re: -current crash

On Mon, Oct 18, 1999 at 12:16:08AM +0200, Michael Reifenberger wrote: The combination of vinum raid5 and softupdates is known to trigger a bug which may look just as you described. I might help if you disable softupdates on the vinum volumes. -- B.Walter COSMO-Project

Re: -current crash

On Mon, 18 Oct 1999, Bernd Walter wrote: ... > On Mon, Oct 18, 1999 at 12:16:08AM +0200, Michael Reifenberger wrote: > The combination of vinum raid5 and softupdates is known to trigger a bug > which may look just as you described. > I might help if you disable softupdates on the vinum volumes. Ri

Re: -current crash

On Mon, 18 Oct 1999, Greg Lehey wrote: > Date: Mon, 18 Oct 1999 12:50:04 +1300 > From: Greg Lehey <[EMAIL PROTECTED]> > To: Michael Reifenberger <[EMAIL PROTECTED]> > Cc: Matthew Jacob <[EMAIL PROTECTED]>, FreeBSD-Current <[EMAIL PROTECTED]> > Subject: Re: -current crash ... > OK, this is what I

-CURRENT `make world` fails.. (ucontext.h?)

Hi, On a fresh cvsup of the -CURRENT sources, I've been trying to do a `make world`. I've gotten all the way through (past signal 12 errors, which were fixed by reading the -CURRENT archives and recompiling an up-to-date kernel) to the boot loader. Since the errors are on another box (whi

Re: -current crash

the vinum module looks to have been the problem.. not ethat you had stack elements at 0xc101exxx vinum starts at 0c1011000, On Mon, 18 Oct 1999, Michael Reifenberger wrote: > On Mon, 18 Oct 1999, Bernd Walter wrote: > ... > > What kind of modules were you running? > (nullum)(root)# kldstat > Id

Re: -current crash

On Mon, 18 Oct 1999, Greg Lehey wrote: > Date: Mon, 18 Oct 1999 13:40:27 +1300 > From: Greg Lehey <[EMAIL PROTECTED]> > To: Michael Reifenberger <[EMAIL PROTECTED]> > Subject: Re: -current crash Ok, seems to be fixed. A few stress tests which paniced reliable before do new work. Thanks for the fa

Re: -current crash

On Sun, 17 Oct 1999, Julian Elischer wrote: ... > the vinum module looks to have been the problem.. > not ethat you had stack elements at 0xc101exxx > vinum starts at 0c1011000, Yes. But you are too late :-) The fix is allready commited. Bye! Michael Reifenberger Plaut Software GmbH, R/3 Bas

Re: duplicate filenames under Linux emulation

"Kurt D. Zeilenga" wrote: > > might be informative to provide output of "ls -li" to the list. Sure... it doesn't change one thing, but here goes: current:~/prog/motif/GUITests/Test2$ ls -li total 237 444972 -rw-r--r-- 1 ak users5626 Oct 17 20:38 #uil.uil# 444961 -rw-r--r-- 1 ak

Re: duplicate filenames under Linux emulation

Alex wrote: > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c For what it's worth, I have this bug in the to-do list for the SVR4 emulator too. It's caused by the fact that dirent st

Is it just me or is sys/signal.h just completely screwed up now?

I've got a box running yesterday's -current and it can't compile or install things like XFree86 or ImageMagik due to syntax errors in this file. Investigating further, I find that the trouble begins around line 127, where we see: #if defined(_P1003_1B_VISIBLE) || defined(KERNEL) ..

Re: duplicate filenames under Linux emulation

On Mon, Oct 18, 1999, Alex wrote: > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 Two different versions of ls. You seem to have

Re: -current problem: Network cards doesn't run

On Sun, 17 Oct 1999, Andreas Klemm wrote: > See ed0 > When running a current kernel of some days ago, no problems. > Were there perhaps changes in the last days that introduce > this, that some NICs doesn't run ? > Even the xl0 interface didn't run (DMZ). Ping to hosts in > internet didn't su

pcic.ko & recent changes to sys/pccard/*

Hi, I'm running FreeBSD 4.0-CURRENT on my laptop, a Dell Inspiron 7000. I successfully got my 3Com Megahertz 3C574B Ethernet PC-Card to work under 4.0-CURRENT (sources as of September 29, 1999 @ 10AM EDT, before marcel's infamous signal.h commits). CVSup'ing recently and finally

how to allocate a resource at new-bus architecture?

Hi, all. I have a question about a resource allocation at a child device of PCI device. I'm thinking about to write a CardBud device driver. CardBus is attached at PCI bus. So I think CardBus is a child device of PCI device. Before revision 1.122 of @src/sys/pci/pci.c, I can allocate a resouce