On Fri, 26 Jan 2001 14:13:42 -0800 (PST)
John Baldwin [EMAIL PROTECTED] wrote:
JB 1) All parsing of /etc/shells should move off into libutil under a
JBsuitable API.
There is one in libc/gen that would do fine. The catch is that it
is not used everywhere and some of the code that
Here's a first step.
I've broken the proc structure into 4 structures. At this moment the proc
structure includes
the other three, so there is no problem with allocation, and there is always
a 1:1 correlation between them at this time so this is safe.
SOme of the fields are probably in the
In message [EMAIL PROTECTED], Root Dude writes:
Here's a first step.
I've broken the proc structure into 4 structures. [...]
Uhm Julian,
You are aware that other people are working on this stuff too ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP
Please test the code at
http://www.freebsd.org/~kris/openssl-0.9.6-stable.tgz - it's the
latest snapshot of the OpenSSL 0.9.6-STABLE branch, containing lots of
bugfixes against 0.9.6 etc. Just blat it over the top of your existing
files from /usr/src.
I especially want people to test it for
On Sat, 27 Jan 2001 00:27:13 -0800 (PST)
John Baldwin [EMAIL PROTECTED] wrote:
JB How many contrib'd apps need to look at /etc/shells? The biggest one I think
JB is sendmail, and Greg Shapiro is a very reasonable fellow, and can probably
JB assist in getting sendmail at least to use the API as
On Sat, Jan 27, 2001 at 12:33:23AM -0800, Root Dude wrote:
Here's a first step.
This is very disappointing, Julian. You've duplicated work that I've
already done, and if you've been paying attention at all, you know that it
was already done. Even if you haven't been paying attention, I find
On Sat, 27 Jan 2001 00:27:13 -0800 (PST)
John Baldwin [EMAIL PROTECTED] wrote:
JB How many contrib'd apps need to look at /etc/shells? The biggest one I think
JB is sendmail, and Greg Shapiro is a very reasonable fellow, and can probably
JB assist in getting sendmail at least to use the API as
# dmesg
...
xl0 XXX: driver didn't initialize queue mtx
lo0 XXX: driver didn't initialize queue mtx
isp0 XXX: driver didn't initialize queue mtx
isp1 XXX: driver didn't initialize queue mtx
isp2 XXX: driver didn't initialize queue mtx
isp3 XXX: driver didn't initialize queue mtx
...
Anything to
Blaz Zupan [EMAIL PROTECTED] writes:
xl0 XXX: driver didn't initialize queue mtx
[...]
Nothing to worry about, it's just a reminder for us kernel jocks.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
Oh, yeah- can someone say *which* queue mtx it's referring to?
On 27 Jan 2001, Dag-Erling Smorgrav wrote:
Blaz Zupan [EMAIL PROTECTED] writes:
xl0 XXX: driver didn't initialize queue mtx
[...]
Nothing to worry about, it's just a reminder for us kernel jocks.
DES
--
Dag-Erling
Hi,
cvsup at Sat Jan 27 04:04:26 GMT 2001
While booting, just after the message:
faith0 XXX: driver didn't initialize queue mtx
panic: malloc(M_WAITOK) in interrupt context
DDB gives:
panic()
malloc()
exit1()
kthread_suspend()
ithd_loop()
fork_exit()
fork_trampoline()
--
Bob Bishop
I just rebuilt my -current system yesterday, and now LyX is throwing up
all over itself. It starts up fine, but if I try to load a document or
create a new one, it immediately dumps core. The problem seems to be
occuring the the xforms library. I have a fresh copy of the compat3x
distribution
Matthew Jacob [EMAIL PROTECTED] writes:
Oh, yeah- can someone say *which* queue mtx it's referring to?
des@des ~% current "driver didn.t initialize"
src/sys/net/if.c: printf("%s%d XXX: driver didn't initialize
queue mtx\n",
des@des ~% grep -C "driver didn.t initialize"
On Sat, Jan 27, 2001 at 01:57:40PM +0100, Steve O'Hara-Smith wrote:
Life is better than I thought the crypto stuff just has it as a fallback
conditional on HAVE_GETUSERSHELL so that uses the one from libc. Which leaves
only sendmail which is similar but for some reason does not have
On Sat, 27 Jan 2001 13:17:22 -0600
"Jacques A. Vidrine" [EMAIL PROTECTED] wrote:
JV You could just use the nsdispatch() API that is in -CURRENT, and that
JV getusershell() uses.
I'm not sure what for, the changes I've made fit just as smoothly
into _local_initshells as they do into
Oh, I suppose, I did find that... well, mainly I wanted the person who made
the change to actually broadcast to NIC maintainers what the expectations
were...
Matthew Jacob [EMAIL PROTECTED] writes:
Oh, yeah- can someone say *which* queue mtx it's referring to?
des@des ~% current "driver
On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
Oh, I suppose, I did find that... well, mainly I wanted the person who made
the change to actually broadcast to NIC maintainers what the expectations
were...
The code that prints these warnings out has existed for a while.
Shouldn't ether_ifattach initialize the mutex? Or do expect all drivers to
initialize these prior to calling ether_ifattach?
Look- I just want to know what the people who put the check in *want*.
On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
Oh, I suppose, I did
This is weird; the bridge appears to be clearly misconfigured, and unless
there's something funky in the datasheet (looking for it now) I'm not
quite sure what the "right" thing to do is here. 8(
Please let me know if you need anything more from me to help debug this.
This is enough for
On Sat, Jan 27, 2001 at 12:48:36PM -0800, Matthew Jacob wrote:
Somewhere in between, Jason Evans wrote:
On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
Oh, I suppose, I did find that... well, mainly I wanted the person who made
the change to actually broadcast to NIC
cvs annotate is your friend. The code was added in revision 1.95 of
src/sys/net/if.c by Jonathan Lemon. Please talk to him about what should
be done to fix the drivers.
Yes, and I shall... but this came up in a public forum. I'm making a point
here (that apparently you and others don't
In article local.mail.freebsd-current/[EMAIL PROTECTED] you write:
On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
Oh, I suppose, I did find that... well, mainly I wanted the person who made
the change to actually broadcast to NIC maintainers what the expectations
were...
The
On Sat, Jan 27, 2001 at 01:05:58PM -0800, Jason Evans wrote:
On Sat, Jan 27, 2001 at 12:48:36PM -0800, Matthew Jacob wrote:
Somewhere in between, Jason Evans wrote:
On Sat, Jan 27, 2001 at 12:36:41PM -0800, Matthew Jacob wrote:
Oh, I suppose, I did find that... well, mainly I
Patrick Hartling [EMAIL PROTECTED] wrote:
} I just rebuilt my -current system yesterday, and now LyX is throwing up
} all over itself. It starts up fine, but if I try to load a document or
} create a new one, it immediately dumps core. The problem seems to be
} occuring the the xforms library.
Hi,
I'm tracking -CURRENT and build a kernel yesterday with the following
options (edited):
device sbc # Soundblaster Bridge-Code to pcm
device pcm # PnP/PCI Sound Cards
#device midi# Midi interfaces
#device seq #
On Sat, Jan 27, 2001 at 08:48:59PM +0100, Steve O'Hara-Smith wrote:
On Sat, 27 Jan 2001 13:17:22 -0600
"Jacques A. Vidrine" [EMAIL PROTECTED] wrote:
JV You could just use the nsdispatch() API that is in -CURRENT, and that
JV getusershell() uses.
I'm not sure what for, the changes
On 27-Jan-01 Matthew Jacob wrote:
Oh, yeah- can someone say *which* queue mtx it's referring to?
The if queues. Ones with the IFQ_ENQUEUE() etc. macros.
On 27 Jan 2001, Dag-Erling Smorgrav wrote:
Blaz Zupan [EMAIL PROTECTED] writes:
xl0 XXX: driver didn't initialize queue mtx
[...]
Hi.
I've found that -current kernel couldn't mount CD-Extra disks on
ATAPI CD drives.
For example:
Starting track = 1, ending track = 14, TOC size = 122 bytes
track start duration block length type
-
1 0:02.00 0:11.52 0
On Mon, Jan 22, 2001 at 03:46:51PM -0500, Benjamin Lewis wrote:
Robert,
You wrote:
For the last few days (not sure when it started) I've been unable to build
-STABLE on a -CURRENT machine. This has proven a problem for recent
RELENG_3 MFC's of security fixes; I've tried upgrading to
Boris reminded me of someething I had forgotten to mention: currently unloading
a module that uses mutexes with WITNESS enabled in the kernel will panic the
kernel, cause witness tries to look at the string of the mutex name which is
usually a constant in the module later on. This leads to a
On Sat, Jan 27, 2001 at 03:19:04PM -0600, Jonathan Lemon wrote:
Actually, the new check appears to be incorrect, as seen by the code
fragments below:
Whoops. I obviously looked at the wrong #define when making the change.
Thanks for pointing out the mistake.
Jason
To Unsubscribe: send mail
On Sat, 27 Jan 2001 16:59:41 -0600
"Jacques A. Vidrine" [EMAIL PROTECTED] wrote:
JV I thought you might add it as a different source, so that it need not be
JV the default.
As I read it that is still a complementary possibility. The nsdispatch
stuff could move the start point from
Steve O'Hara-Smith wrote:
On Fri, 26 Jan 2001 16:21:01 -0500 (EST)
Garrett Wollman [EMAIL PROTECTED] wrote:
GW On Fri, 26 Jan 2001 22:08:20 +0100, "Steve O'Hara-Smith" [EMAIL PROTECTED]
said:
GW
GWThe patch below (against 4-stable but it will probably apply easily
GW to -current)
33 matches
Mail list logo
