Is there an #include sys/types.h missing in pam_opieaccess.c?
Yes. Added now.
Thanks!
M
--
o Mark Murray
\_
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
In message: [EMAIL PROTECTED]
[EMAIL PROTECTED] (Nickolay Dudorov) writes:
: In article [EMAIL PROTECTED]
: Alfred Perlstein [EMAIL PROTECTED] wrote:
: alfred 2002/03/19 12:18:46 PST
:
: Modified files:
: sys/sys acct.h acl.h bio.h buf.h callout.h conf.h
:
On Fri, Mar 22, 2002 at 06:50:55AM -0700, M. Warner Losh wrote:
: At least in the case of 'ioccom.h' this commit breaks
: the XFree86-server building in the 'drm/kernel' directory.
:
: The problem is in the '#define ioctl(a,b,c) xf86ioctl(a,b,c)'
: which is used by the XFree86 and
It's been quite a while since I updated my -current box, but when I did,
I was surprised to find that my DE500 network card (21143 chip) had stopped
working. The switch showed no link. Ifconfig showed no carrier.
After some fiddling, I reverted revision 1.56 (removal of mii_pollstat call)
of
On Fri, Mar 22, 2002 at 01:01:57AM -0600, Eric Liedtke wrote:
While trying to build the XFree86-4-Server port this evening(cvsuped
today around 1PM CST)
the build died due to a redefinition of xf86ioctl. The file
In message: [EMAIL PROTECTED]
Will Andrews [EMAIL PROTECTED] writes:
: On Fri, Mar 22, 2002 at 06:50:55AM -0700, M. Warner Losh wrote:
: : At least in the case of 'ioccom.h' this commit breaks
: : the XFree86-server building in the 'drm/kernel' directory.
: :
: : The problem
On Fri, Mar 22, 2002 at 08:28:36AM -0700, M. Warner Losh wrote:
Ummm, I'm not going to be doing patches for X11 for at least a few
more days, if then. I don't have the time to do it until sometime
next week.
Well if someone else does it, they need to send me the patch. :)
Regards,
--
wca
On Sat, 23 Mar 2002, Stephen McKay wrote:
It's been quite a while since I updated my -current box, but when I did,
I was surprised to find that my DE500 network card (21143 chip) had stopped
working. The switch showed no link. Ifconfig showed no carrier.
I've had the simular problem. Now
On Tuesday 19 March 2002 14:26, you wrote:
For those that have problems with burncd or simply cannot live
without, I've put up the source for an ATAPI enabled cdrecord on:
ftp://freebsd.dk/pub/ATA/cdrtools-1.10-ATA.tgz
Is there a chance that this will find it's way into the ports-collection?
I'm building world/X11 this afternoon with the following fix to the
X11 problem. It isn't so much of a fix as a tactical retreat until a
real fix can happen.
Warner
Index: ioccom.h
===
RCS file: /cache/ncvs/src/sys/sys/ioccom.h,v
I think this patch unbreaks world.
Index: pam_opieaccess/pam_opieaccess.c
===
RCS file: /home/ncvs/src/lib/libpam/modules/pam_opieaccess/pam_opieaccess.c,v
retrieving revision 1.7
diff -u -r1.7 pam_opieaccess.c
---
On a 0 - 10 weirdness scale, this ranks about a 4, perhaps, so it's
hardly earth-shattering. But it's odd enough that I thought that a
small reality check might be in order, in case the effect(s) in question
were not expected. (And yes, I understand that a degree of uncertainty
with respect to
On 22-Mar-2002 David Wolfskill wrote:
On a 0 - 10 weirdness scale, this ranks about a 4, perhaps, so it's
hardly earth-shattering. But it's odd enough that I thought that a
small reality check might be in order, in case the effect(s) in question
were not expected. (And yes, I understand
Just did a fresh install of -CURRENT and noticed that MAKEDEV isn't
being installed. This intentional? -sc
--
Sean Chittenden
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Just did a fresh install of -CURRENT and noticed that MAKEDEV
isn't being installed. This intentional? -sc
MAKEDEV on -current is not needed, since devfs creates device nodes
automatically.
Alright, sounds good/believable, but how do I extend the number of
pty's on current then? I
Fresh (todays) -current not builds on current machine:
vbook#/sys/i386/compile/VBOOK 142_ make kernel-depend make kernel
rm -f .olddep
if [ -f .depend ]; then mv .depend .olddep; fi
make _kernel-depend
if [ -f .olddep ]; then mv .olddep .depend; fi
rm -f .newdep
make -V CFILES -V SYSTEM_CFILES
In the last episode (Mar 22), Sean Chittenden said:
Just did a fresh install of -CURRENT and noticed that MAKEDEV isn't
being installed. This intentional? -sc
MAKEDEV on -current is not needed, since devfs creates device nodes
automatically.
--
Dan Nelson
[EMAIL PROTECTED]
On 22:14+0300, Mar 22, 2002, Vladimir B. Grebenschikov wrote:
Fresh (todays) -current not builds on current machine:
vbook#/sys/i386/compile/VBOOK 142_ make kernel-depend make kernel
rm -f .olddep
if [ -f .depend ]; then mv .depend .olddep; fi
make _kernel-depend
if [ -f .olddep ];
On Fri, 2002-03-22 at 22:27, Maxim Konovalov wrote:
Fresh (todays) -current not builds on current machine:
...
Did you read
20020225:
Warnings are now errors in the kernel. Unless you are a developer,
you should add -DNO_WERROR to your make line.
No, It seems I have
On Fri, 22 Mar 2002, David Wolfskill wrote:
On a 0 - 10 weirdness scale, this ranks about a 4, perhaps, so it's
hardly earth-shattering. But it's odd enough that I thought that a
small reality check might be in order, in case the effect(s) in question
were not expected. (And yes, I
On Fri, 22 Mar 2002, Sean Chittenden wrote:
Just did a fresh install of -CURRENT and noticed that MAKEDEV
isn't being installed. This intentional? -sc
MAKEDEV on -current is not needed, since devfs creates device nodes
automatically.
Alright, sounds good/believable, but how do
Alfred Perlstein [EMAIL PROTECTED] writes:
I think this patch unbreaks world.
Mark, not me.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Robert Watson wrote:
On a 0 - 10 weirdness scale, this ranks about a 4, perhaps, so it's
hardly earth-shattering. But it's odd enough that I thought that a
small reality check might be in order, in case the effect(s) in question
were not expected. (And yes, I understand that a degree of
On Fri, 22 Mar 2002, Garrett Wollman wrote:
On Fri, 22 Mar 2002 10:08:05 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] said:
-intioctl(int, unsigned long, ...);
+intioctl __P((int, unsigned long, ...));
int (ioctl)(int, unsigned long, ...);
is the ISO-sanctioned
D J Printing Corporation
2564 Cochise Drive
Acworth, GA 30102
(V)770-974-8228
(F)770-974-7223
[EMAIL PROTECTED]
*WE ACCEPT GOVERNMENT, SCHOOL AND UNIVERSITY PURCHASE ORDERS*
--LASER, FAX AND COPIER PRINTER TONER CARTRIDGES--
*WE ACCEPT GOVERNMENT, SCHOOL AND UNIVERSITY PURCHASE ORDERS*
I saw some similar weirdness in my test machines last night where a dual
processor DS20 (Alpha 21264 500x2) beat out a PII Xeon 450x4. Normally
the
quad xeon beats the DS20. The quad xeon was using -j16 but was about 74%
idle.
The DS20 had used -j8. I didn't get a chacne to run top to
Date: Fri, 22 Mar 2002 20:43:03 -0500 (EST)
From: Jeff Roberson [EMAIL PROTECTED]
Are you both running with WITNESS and INVARIANTS? UMA is slightly slower
with these options on than the original malloc vm_zone code. I'm not
sure why it would be even worse for SMP machines though. So maybe it
On Fri, Mar 22, 2002 at 06:34:00PM -0800, David Wolfskill wrote:
Date: Fri, 22 Mar 2002 20:43:03 -0500 (EST)
From: Jeff Roberson [EMAIL PROTECTED]
Are you both running with WITNESS and INVARIANTS? UMA is slightly slower
with these options on than the original malloc vm_zone code. I'm not
Apologies if you will get this message twice. My ISP seems to be
blocked in hub.freebsd.org so I had to use temporary hotmail account.
I found the reason for crashes I was experiencing ever since UMA has
been committed into -CURRENT. Apparently UMA has nothing to do with the
breakage.
After having updated to the world past 2002-02-19, dhclient started
very fast cycle of acquiring and releasing leases every time it was
attached to the local network, like it's attacking the DHCP server.
After all, it was /sbin/dhclient-script that failed trying to update
/etc/resolv.conf which
* Alexander Kabaev [EMAIL PROTECTED] [020322 21:31] wrote:
I used the workaround below to get the system booting again, but it
does nothing to solve the real problem. We should probably either update
each and every vnode known to the system with the new v_op pointer when
needed, or simply
Hi,
Need to subscribe to the mailing list. Interested in development and
helping ot.
Ashish Gupta
--
/
\\ - - //
( @ @ )
-oOOo--(_)-oOOo---
Sincerly yours,
Ashish Gupta
---O--
( )
O ) /
( ) (_/
\ (
\_)
You could add one, it would be trivial to add a TAILQ_ENTRY to the
vnode strcture as well as add/remove the nodes from
the list in the vnode allocation and deallocation code.
I was thinking about mp-mnt_nvnodelist, unless there are compelling
reasons not to trust it.
Feel ambitious? :)
Feel like
Alfred Perlstein wrote:
Good work!
I was about to say:
why don't you just traverse the system wide list of vnodes
and fixup the pointers?
Then I realized that there doesn't seem to be a system wide list... :(
You could add one, it would be trivial to add a TAILQ_ENTRY to the
vnode
Matthew Dillon wrote:
Unless I am missing something, vnodes hang off their mount points.
So, effectively, there is a system-wide list.
The lock on a global traverasl will be pretty ugly...
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the
* Terry Lambert [EMAIL PROTECTED] [020322 23:13] wrote:
Matthew Dillon wrote:
Unless I am missing something, vnodes hang off their mount points.
So, effectively, there is a system-wide list.
The lock on a global traverasl will be pretty ugly...
Module loading doesn't occur often.
I just cvsupped about an hour ago, built world and built a kernel that was
GENERIC with 486/586 turned off and SMP and IOAPIC turned on. It crashed
while trying to mount root. Apologies for mistakes in the following since
I don't have a serial console and had to write it down:
normal da0 SCSI
:* Terry Lambert [EMAIL PROTECTED] [020322 23:13] wrote:
: Matthew Dillon wrote:
: Unless I am missing something, vnodes hang off their mount points.
: So, effectively, there is a system-wide list.
:
: The lock on a global traverasl will be pretty ugly...
:
:Module loading doesn't
Alfred Perlstein wrote:
* Terry Lambert [EMAIL PROTECTED] [020322 23:13] wrote:
Matthew Dillon wrote:
Unless I am missing something, vnodes hang off their mount points.
So, effectively, there is a system-wide list.
The lock on a global traverasl will be pretty ugly...
GENERIC works, so this looks like an SMP problem.
Its happening right after the CPU initializes. This is probably the first
SMP code the machine runs? Is hardware incompatibility a good guess? I
would have expected that if someone broke ffs_mountfs() that someone else
would have noticed by
40 matches
Mail list logo
