In case anyone else hasn't figured out why you're seeing a few old
messages, it looks like there's a mailer at bestweb.net that's
re-sending the mails it has queued up but using the `To:' header
field for the new recipient, so that mails from several days ago
are appearing again. It's not me and
I just wrote
> In case anyone else hasn't figured out why you're seeing a few old
> I read this list via usenet, so here's relevant headers from a post
Murphy's law. The news swerver I read from has stopped getting any
new articles after about three bestweb regurgitations, which I didn't
reali
I hadn't seen this reported in the archives yet, but the recent change
to sys/sys/proc.h removed the kg_pri struct member. This member is
still referenced in lib/libkvm/kvm_proc.c at line 331, and
sys/kern/kern_poll.c. I assume the fix for kvm_proc.c and kern_poll.c
would be something like the a
> > You are reflecting messages back to a mailing list with
> > thousands of subscribers.
> >
> > Cut it out.
> >
> > -- Terry
>
> Peter has applied the Big Hammer of Death to the problem for now, so
> it should be stopping soon if not already.
Thanks Peter
Nate
To Unsubscribe: send ma
Nate Williams wrote:
> > > You are reflecting messages back to a mailing list with
> > > thousands of subscribers.
> > >
> > > Cut it out.
> > Peter has applied the Big Hammer of Death to the problem for now, so
> > it should be stopping soon if not already.
> Thanks Peter
Peter is my hero.
In message: <[EMAIL PROTECTED]>
j mckitrick <[EMAIL PROTECTED]> writes:
: On Mon, Feb 11, 2002 at 03:56:00PM -0700, M. Warner Losh wrote:
: | NEWCARD is up and running, but has issues for some cards, bridges and
: | lacks some useful features.
:
: That reminds me, there was something
On 12-Feb-02 Terry Lambert wrote:
> You are reflecting messages back to a mailing list with
> thousands of subscribers.
>
> Cut it out.
>
> -- Terry
Peter has applied the Big Hammer of Death to the problem for now, so it should
be stopping soon if not already.
--
John Baldwin <[EMAIL PROTEC
On Sun, 10 Feb 2002, Andrey A. Chernov wrote:
> On Sun, Feb 10, 2002 at 12:13:05 -0800, Gregory Neil Shapiro wrote:
> >
> > http://people.freebsd.org/~gshapiro/CURRENT-8.12.2
>
> --- lib/libmilter/Makefile~orig Sun Jan 20 13:58:03 2002
> +++ lib/libmilter/MakefileSun Jan 20 13:05:02 20
On 12-Feb-02 Terry Lambert wrote:
> John Baldwin wrote:
>> Yes, calling free() without Giant is about as good as calling fdrop()
>> without
>> Giant Alfred. :)
>
> Alfred would be right, for per processor memory pools. 8-).
>
>> >> And on the way into the system it does:
>> >> lock process
>>
On 12-Feb-02 Terry Lambert wrote:
> Then the combination of calls fails. There is no case where
> it will succeed when previously it would not. I would argue
> that the failure is a lost race condition that exists in the
> code anyway, and that this approach merely makes the race
> failure more
On Tue, Feb 05, 2002 at 08:14:22PM +0100, Thomas Quinot wrote:
> > Is there a place where I can find this updated patch which will work for
> > me in the current -current? Thanks.
>
> I put up updated patches at
> http://www.cuivre.fr.eu.org/~thomas/atapicam/
>
> For -CURRENT, you should be
On 12-Feb-02 Terry Lambert wrote:
> Julian Elischer wrote:
>> > The "multiple threads" argument is bogus, since the calls
>> > to [gs]et[ug]id() are on a per process, not a per thread
>> > basis.
>>
>> there is no such thing as a per process syscall.
>> Two threads can always do the same syscall
On 12-Feb-02 Julian Elischer wrote:
>
>
> On Mon, 11 Feb 2002, John Baldwin wrote:
>
>>
>> On 12-Feb-02 Julian Elischer wrote:
>> > The proclock is needed to get the reference,
>> > guarding against other threads, and giant is needed fo rnot to free it
>> > because if it reaches a refcount o
John Baldwin wrote:
> > The "multiple threads" argument is bogus, since the calls
> > to [gs]et[ug]id() are on a per process, not a per thread
> > basis.
>
> Thread 1 makes a syscall that blocks. Say it blocks in one of 3 VOP's all of
> which need a credential. Thread 2 changes the credentials
Quit reflecting old messages back to the losts. Thanks.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
You are reflecting messages back to a mailing list with
thousands of subscribers.
Cut it out.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Julian Elischer wrote:
> > The "multiple threads" argument is bogus, since the calls
> > to [gs]et[ug]id() are on a per process, not a per thread
> > basis.
>
> there is no such thing as a per process syscall.
> Two threads can always do the same syscall at the same time.
> there needs to be a pr
John Baldwin wrote:
> Yes, calling free() without Giant is about as good as calling fdrop() without
> Giant Alfred. :)
Alfred would be right, for per processor memory pools. 8-).
> >> And on the way into the system it does:
> >> lock process
> >> crhold() (which includes mutex ops)
> >> unlock
On Mon, 11 Feb 2002, John Baldwin wrote:
>
> On 12-Feb-02 Julian Elischer wrote:
> > The proclock is needed to get the reference,
> > guarding against other threads, and giant is needed fo rnot to free it
> > because if it reaches a refcount of 0 it needs to call free(). (which john
> > assur
--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Feb 08, 2002 at 03:56:21PM -0800, Julian Elischer wrote:
>
> In your case we need totrace proc 1 I think..
>
I got the `reboot' process at this session, so I traced that process.
Before I had use
yes,, this exactly fits the symptoms!
I've committed it.
(it's definitly wrong)
assume this will solv ethe problem.
now why doesn't MINE fail?
On Sat, 9 Feb 2002 [EMAIL PROTECTED] wrote:
> > h so what is the difference between your kernel and mine that works?
> >
> > just out of curiosity
I get the following error when running mtree(1) in a jail:
root@p4 /usr/src# gdb =mtree
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 conditi
Is it possible to make devices enumerated by acpi to take notice of the
flags given to them in device.hints?
for example if I allow acpi then I get:
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A, console
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
despite the fact that I hav
David O'Brien wrote:
> > Ports does the same thing: hand tweaks stuff instead of
> > pushing the patches back to the projects that originated
> > it.
>
> *sigh* Terry I respect your programming knowledge, but you are wrong
> here. I send out a *LOT* of patches to the authors of ports I maintain
On Sun, 10 Feb 2002, Mikhail Teterin wrote:
> On 10 Feb, Bruce Evans wrote:
> > This is a well known bug in the device layer. I reported it on
> > 2001/12/26 and fixed it locally a little later. See the thread in
> > -current about "panic during fdisk'ing a md(4) device" for patches.
On Sun, 10 Feb 2002, Kevin Day wrote:
>
> I'm the maintainer for ports/editors/joe, and just tried compiling it under
> -CURRENT.
>
> includes which includes ucontext.h
>
> > cc -O -pipe -c umath.c
> > In file included from b.h:6,
> > from bw.h:23,
> > from
On 10 Feb, Bruce Evans wrote:
> On Sat, 9 Feb 2002, John Baldwin wrote:
>
>> On 09-Feb-02 Mikhail Teterin wrote:
>> > While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
>> > ``newfs_msdos fd0.1440'' with or without the floppy inside :-\ With
>> > todays or Jan 3rd kernel (my prev
This is a multi-part message in MIME format.
--Boundary_(ID_TA6w1McSahPHMx8+rAaDoQ)
Content-type: text/plain; charset=iso-8859-2
Content-transfer-encoding: 7BIT
After comments by jhb and bde
--
++ __ _ __
| __--_|\ Julian Elischer |
I'm the maintainer for ports/editors/joe, and just tried compiling it under
-CURRENT.
includes which includes ucontext.h
> cc -O -pipe -c umath.c
> In file included from b.h:6,
> from bw.h:23,
> from umath.c:5:
> rc.h:41: conflicting types for `getcontext'
>
--=-c5mu7fd8+iIeadXPJgcR
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Thu, 2002-02-07 at 08:01, Julian Elischer wrote:
>=20
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>=20
> these patches SHOULD NOT EFFECT your system except to do some
> slight
I'm not particularly good at reading the lock-related output, but it
doesn't have other lines than the one that says about the Giant lock, so
it seems there isn't any other locks being held by anyone.
Eugene
On Fri, Feb 08, 2002 at 04:55:42PM -0800, Julian Elischer wrote:
>
>
> I tlooks as if
This is a note for someone upgrading from 4.4 stable to current 5.0
comes right out of my experience in doing so the file
/usr/src/UPGRADE doesnt detail the following step
I didnt see ne 1 post this before may be it will help
some newbie like myself and perhaps somebody will add
it to the UPGRA
On 2002-02-08 06:57, Alfred Perlstein wrote:
> * Andrea Campi <[EMAIL PROTECTED]> [020208 03:51] wrote:
> > On Wed, Feb 06, 2002 at 12:35:39PM -0800, Alfred Perlstein wrote:
> > > * David W. Chapman Jr. <[EMAIL PROTECTED]> [020206 12:33] wrote:
> > > > Does anyone know if the problem with kde and
Serwoas!
%s wrote on %.3s, %lld Sep 1993
> > Could it be due to the DDB, INVARIANTS & WITNESS options in the
> > kernel? If it is that's fine with me, I'm just wondering where
> > that magnitude of a slowdown would be coming from.
> WITNESS can really hurt. Quite possibly I should turn it off
Yesterday I tried to use SWAT for the first time since the PAM configs were
moved from /etc/pam.conf and I'm getting the following error:
Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open
/etc/pam.conf
What do I need to do to fix this?
TIA,
Beech
--
> Yesterday I tried to use SWAT for the first time since the PAM configs were
> moved from /etc/pam.conf and I'm getting the following error:
>
> Feb 6 22:54:05 galaxy swat: PAM _pam_init_handlers: could not open
> /etc/pam.conf
>
> What do I need to do to fix this?
Recompile the app. I'm gue
It seems Gerhard Sittig wrote:
> On Thu, Feb 07, 2002 at 12:38 +0100, Søren Schmidt wrote:
> >
> > [ snipped ATAPI -> SCSI conversion ]
> >
> > Doesn't burncd work for you on -current ?
>
> Well, since you asked about it ... :)
I asked for *problems* not cosmetic issues :)
> The bug (talking
OK; I got today's -CURRENT built & running on each of my build
machine (freebeast) & my laptop. (Got today's -STABLE built
earlier; I mention this as a reference point/comparison. I
similarly note that I've been tracking each daily on each machine
for several months, and that today is the first
On Wed, 6 Feb 2002, Jacob Frelinger wrote:
> On Wed, Feb 06, 2002 at 01:08:10PM -0800, Doug White wrote:
> > On Tue, 5 Feb 2002, Jacob Frelinger wrote:
> >
> > You aren't using a Linux version of vi, are you? It so happens a common
> > freebsd system call maps to linux reboot()
> >
>
> it s
On Thu, 7 Feb 2002, Julian Elischer wrote:
> As part of the KSe stuff I ended up changing ht ebehaviour of threads with
> respect to their ucreds. Previously, they freed their ucred reference when
> they entered user space and picked them up again when they re-entered the
> kernel. It there was a
As part of the KSe stuff I ended up changing ht ebehaviour of threads with
respect to their ucreds. Previously, they freed their ucred reference when
they entered user space and picked them up again when they re-entered the
kernel. It there was an AST then they re-loaded teh already freed ucred t
Terry Lambert writes:
> I don't think Joe is debating; I think he wants to have a
> meta-discussion about what the problem space looks like,
> before submitting patches that light up his little corner,
> and dark up everything else.
Thank you, Terry. Maybe I need to bring up the issue on -ar
* Nat Lanza <[EMAIL PROTECTED]> [020207 10:30] wrote:
> On Thu, 2002-02-07 at 12:59, Alfred Perlstein wrote:
> > These comments are not useless, most committers have day jobs that
> > unfortunetly preclude them from having time to work on every little
> > feature request. Furthermore asking for p
David O'Brien writes:
> On Wed, Feb 06, 2002 at 05:47:07PM -0800, Joe Kelsey wrote:
> > What is so hard about allowing someone to specify the list of frontends
> > to provide at system build time? I thought that gcc was supposed to be
> > a modular compiler system, and that all we are asking
On Mon, 11 Feb 2002, Alfred Perlstein wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [020211 15:00] wrote:
> > In the current world, when the thread enters userland, it does:
> >
> > lock giant
> > crfree() (which includes mutexes)
> > unlock giant
>
> This isn't needed afaik.
Argue with jhb
> I know this is probably offtopic but is there any problem with
> current.freebsd.org at the moment?
Hmm...
galtvalion % ftp current.freebsd.org
Connected to usw2.freebsd.org.
220 usw2.freebsd.org FTP server (Version 6.00LS) ready.
Name (current.freebsd.org:matusita): ftp
331 Guest login ok, s
* Julian Elischer <[EMAIL PROTECTED]> [020211 15:00] wrote:
> In the current world, when the thread enters userland, it does:
>
> lock giant
> crfree() (which includes mutexes)
> unlock giant
This isn't needed afaik.
> if there are ASTs it does this once again for each AST waiting as well.
>
>
Anyone making the usual plans or should I just look for the terminal room?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
will> Jordan announced recently that Qwest is upgrading the hardware
will> and that there would be intermittent problems with the server for
will> a certain period (a few days as I recall).
It would be:
> From: Jordan Hubbard <[EMAIL PROTECTED]>
> Subject: stable.freebsd.org AKA releng4.freebsd
On 11-Feb-02 Alfred Perlstein wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [020211 15:00] wrote:
>> In the current world, when the thread enters userland, it does:
>>
>> lock giant
>> crfree() (which includes mutexes)
>> unlock giant
>
> This isn't needed afaik.
Yes, calling free() without G
Hi,
I know this is probably offtopic but is there any problem with
current.freebsd.org at the moment? I've been unable to log in for almost an
hour, the ftp daemon is up, it just doesn't allow me in and I was about to
load -CURRENT on my laptop.
Any idea?
Cheers,
--
Miguel Mendez -
On 12-Feb-02 Julian Elischer wrote:
> The proclock is needed to get the reference,
> guarding against other threads, and giant is needed fo rnot to free it
> because if it reaches a refcount of 0 it needs to call free(). (which john
> assures me needs Giant at this time).
> We could avoid the pr
On Mon, 11 Feb 2002, Garrett Wollman wrote:
> <<[EMAIL PROTECTED]> said:
>
> > How do you easily forward declare something that is a typedef?
>
> There is a reason style(9) says not to use such typedefs.
> Unfortunately, this one it written into a standard. Since We Are The
> Implementation, th
On 11-Feb-02 Julian Elischer wrote:
> here is the BDE version ready to commit.
> Extended to other architectures.
>
> Bruce, John, comments?
>
> As I was adding a prototype to ucred.h I stripped the __Ps of the others in
> that
> section
> (in the spirit of "change it when editing it anyhow"
H
On Sat, 9 Feb 2002, Julian Elischer wrote:
> On Sun, 10 Feb 2002, Bruce Evans wrote:
> >
> > Yes, anything that reaches doreti checks for ASTs and runs userret() if
> > necessary and possible (only for returns to user mode).
> >
> > Hmm, this check seems to be inadequate for fast interrupts. The
Thanks
On Sun, 10 Feb 2002, Bruce Evans wrote:
>
> Yes, anything that reaches doreti checks for ASTs and runs userret() if
> necessary and possible (only for returns to user mode).
>
> Hmm, this check seems to be inadequate for fast interrupts. There is
> no check for rescheduling if the retu
On Fri, 8 Feb 2002, Julian Elischer wrote:
> Bruce, for the low-level impared such as myself, can you give a quick
> precis on teh difference between "fast" interrupt handlers in -current
> and 'normal' interrupt handlers.
"Fast" interrupt handlers are harder to program and should rarely be used
On Tue, 5 Feb 2002, John Baldwin wrote:
...
> > Its the loader after showing:
> > ...
> > loader Revision...
> > (root@nihil, ...)
> > ...
> > And then a few rotating -\|/ (serching or loading loader.conf, kernel, ?)
> > Then silence.
>
> Hmm. Is your loader completely up to date? Does it have a
Mikhail Teterin wrote:
> That's the thing. gcc30 port, essentially, installs a copy of the
> compiler already available as part of the base. But the base is missing
> gcj (the port does too for now), so one would be forced to add the port.
Compilers from ports suck.
If you set DESTDIR, i
> The real question here is: why is the RCSid changing when the file
> isn't?
Sometimes things get changed and then backed out to their original state,
but you cannot keep the original RCSID
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
I don't know the alpha at all but
how about
leaq t0, thread0
or some similar thing
or even..
ldq t0,$thread0
or something similar..
who's assembler is being used?
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, t
> On Wed, Feb 06, 2002 at 11:12:38AM +, Mark Murray wrote:
> > IMO, this is a good reason to not have WARNS contain -Werror at this
> > time. NO_WERROR is a good way to fix this (again IMO). I see a great
> > need to let warnings "hang out", and in an ideal world I see an need
> > for (new) wa
On 09-Feb-02 Julian Elischer wrote:
> yes,, this exactly fits the symptoms!
>
> I've committed it.
> (it's definitly wrong)
> assume this will solv ethe problem.
> now why doesn't MINE fail?
Probably cause you are running your other tree that makes mi_switch() auto do
the setrunqueue? :)
--
>Date: Tue, 5 Feb 2002 06:21:34 -0800
>From: Edwin Culp <[EMAIL PROTECTED]>
>World is breaking for me at:
>===> usr.sbin/rpc.yppasswdd
>...
Following patch got through it for me:
Index: usr.sbin/rpc.yppasswdd/pw_util.c
===
RCS fi
Julian Elischer writes:
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
Today's alpha kernel, plus those changes results in a ksp not valid
halt with the P
The following files under sys/ still use MFREE():
alpha/tc/am7990.c
netatm/port.h
security/lomac/kernel_socket.c
Please fix.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251
>Date: Fri, 8 Feb 2002 17:34:45 -0800 (PST)
>From: Julian Elischer <[EMAIL PROTECTED]>
>Thats it for sure!
>committing now..
>On Sat, 9 Feb 2002 [EMAIL PROTECTED] wrote:
>> It looks like a call to setrunqueue() was incorrectly dropped in
>> the latest version of kern_shutdown.c.
Applying tha
On Fri, 8 Feb 2002, Julian Elischer wrote:
> I'd like to commit the code to keep the ucred across userland,
> with the code to clear it to NULL kept under DEBUG ifdefs.
>
> i.e.
>
> > in trap(), ast() and syscall()
> >
> > if (td->td_ucred != p->p_ucred) {
> > PROC_LOCK(p
I'm a little worried about invariants because the behaviour when
INVARIANTS is set wil be different to teh behaviour when it is off, which
is 'strange' to say the least. Normally the behaviour si the same but you
just check for invariant conditions.
On Fri, 8 Feb 2002, John Baldwin wrote:
>
>
John, (peter? others?)
How is it that getting a ucred reference is guarded by PROC_LOCK(p)
but freeing it is guarded by mtx_lock(&Giant);
?
Call me naive, but shouldn't they be guarded by the same thing?
Julian
On Fri, 8 Feb 2002, Julian Elischer wrote:
> I'm a little worried about invarian
<
said:
> How do you easily forward declare something that is a typedef?
There is a reason style(9) says not to use such typedefs.
Unfortunately, this one it written into a standard. Since We Are The
Implementation, there is no difficulty in simply writing the
appropriate structure type into t
No, I just never went into that particular clause of code
But is has made me rethink the whole issue.
On Fri, 8 Feb 2002, John Baldwin wrote:
>
> On 09-Feb-02 Julian Elischer wrote:
> > yes,, this exactly fits the symptoms!
> >
> > I've committed it.
> > (it's definitly wrong)
> > assume thi
Hi,
I can't get my PCMCIA card to work on my HP Omnibook 6100. -current
is from Feb 6.
During boot I get:
Feb 7 10:14:04 hunter kernel: pcic0: irq 5 at
device 5.0 on pci2
Feb 7 10:14:04 hunter kernel: pcic0: PCI Memory allocated: 0xd020
Feb 7 10:14:04 hunter kernel: pcic0:
Apparently, On Wed, Feb 06, 2002 at 12:01:44PM -0800,
Julian Elischer said words to the effect of;
>
> for the set of patches at:
> http://www.freebsd.org/~julian/adiff
>
> these patches SHOULD NOT EFFECT your system except to do some
> slight re-aranging of stuff in the kernel.
>
> TH
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> Same thing happens when I run it outside the jail, but pointing to the
> jail's root directory. Seems like an fts bug, but I was unable to
> discover the exact cause.
FWIW, I unmounted the jail's /proc and the problem went away. Perhaps
fts make
On 6 Feb, David O'Brien wrote:
>> http://www.gnu.org/manual/bfd-2.9.1/
>>
>> for example, seems to imply, that there was, in fact, at some point a
>> release 2.9.1 of bfd... It does not quite match the bfd,
> No, that document describes the BFD that was included with Binutils
> 2.9.1.
Apparently, On Wed, Feb 06, 2002 at 06:17:38PM -0500,
Andrew Gallatin said words to the effect of;
>
> Andrew Gallatin writes:
> >
> > Since thread0 is no longer a pointer, this looks suspicious in locore.s:
> >
> > /*
> > * Switch to proc0's PCB.
> > */
It's an UP kernel running on an UP box.
Eugene
On Fri, Feb 08, 2002 at 04:53:28PM -0800, Julian Elischer wrote:
>
>
> yes but is it a SMP or UP kernel? (SMP kernel can run on some UP h/w)
>
> thanks!
>
>
> On Fri, 8 Feb 2002, Eugene M. Kim wrote:
>
> > On Fri, Feb 08, 2002 at 03:56:21PM -0
On 6 Feb, David O'Brien wrote:
> On Wed, Feb 06, 2002 at 03:46:22PM -0500, Mikhail Teterin wrote:
>> > dynamically linked libiberty would be a nightmare.
>>
>> > libbfd and libiberty do not have version numbers, are not
>> > maintained (i.e. there is no official releases). every p
On Tue, 5 Feb 2002, Jacob Frelinger wrote:
> I have a new current system that is having the strangest problem.
> using vi or its clones often abruptly powers the system down, no panics,
> no syslog messages. the computer is an ABIT BP6 w/ 2 500 mhz cellerons
> (NOT OVERCLOCKED), two harddrives,
World is breaking for me at:
===> usr.sbin/rpc.yppasswdd
cc -nostdinc -O -pipe -I/usr/src/usr.sbin/rpc.yppasswdd/../../usr.sbin/vipw
-I/usr/src/usr.sbin/rpc.yppasswdd/../../usr.sbin/ypserv
-I/usr/src/usr.sbin/rpc.yppasswdd/../../libexec/ypxfr
-I/usr/src/usr.sbin/rpc.yppasswdd/../../usr.bin/chp
I'd like to commit the code to keep the ucred across userland,
with the code to clear it to NULL kept under DEBUG ifdefs.
i.e.
> in trap(), ast() and syscall()
>
> if (td->td_ucred != p->p_ucred) {
> PROC_LOCK(p);
> if (td->td_ucred) {
>
On Fri, 8 Feb 2002, Bruce Evans wrote:
[...]
> >
> > if (td->td_ucred != p->p_ucred) {
> > PROC_LOCK(p);
> > if (td->td_ucred) {
> > crfree(td->td_ucred);
> > td->td_ucred = NULL;
> > }
> >
can you try a kernel from JUST BEFORE I did the KSE commit yesterday?
I heard someone else complain of thisyesterday afternoon. At that time I
wascertain it was too soon after my commit for him to already have got it,
but it would be nice tio know if I screwed something...
On Fri, 8 Feb 2002, D
Ok so since I don't know alpha assembly.
can it be changed to teh address of the thread0 structure?
(I'll bet the same thing needs to be done on the other
architectures)
THANKS!
On Wed, 6 Feb 2002, Andrew Gallatin wrote:
>
> Julian Elischer writes:
> >
> > for the set of patches at:
> >
In the current world, when the thread enters userland, it does:
lock giant
crfree() (which includes mutexes)
unlock giant
if there are ASTs it does this once again for each AST waiting as well.
And on the way into the system it does:
lock process
crhold() (which includes mutex ops)
unlock proce
While attempting to ``fdisk fd0.1440''. Or ``fdisk fd0''. Or
``newfs_msdos fd0.1440'' with or without the floppy inside :-\
With todays or Jan 3rd kernel (my previous upgrade).
IdlePTD at phsyical address 0x004ed000
initial pcb at physical address 0x00411560
panicstr: bdwrite: buffer is not busy
On Sat, 09 Feb 2002 10:54:06 -0800
Jason Nordwick <[EMAIL PROTECTED]> wrote:
>
> I am trying to install one of the -current snapshots, but
> current.freebsd.org doesn't seem to want to let me log in as anonymous
> (some problem saying it cannot set guest access). Has the procedure
> changed to
On 09-Feb-02 Julian Elischer wrote:
> I'm a little worried about invariants because the behaviour when
> INVARIANTS is set wil be different to teh behaviour when it is off, which
> is 'strange' to say the least. Normally the behaviour si the same but you
> just check for invariant conditions.
I
On 09-Feb-02 Eugene M. Kim wrote:
> I'm not particularly good at reading the lock-related output, but it
> doesn't have other lines than the one that says about the Giant lock, so
> it seems there isn't any other locks being held by anyone.
show locks only shows the locks held by a single threa
In your case we need totrace proc 1 I think..
On Fri, 8 Feb 2002, Eugene M. Kim wrote:
> Attached is the requested DDB log (I guessed pid 7 `syncer' is the
> process doing the sync; if this is wrong let me know).
>
> Eugene
>
> PS. I used the serial console, so don't feel sorry to ask. =)
>
>
> Eh; I suspect that's showing the entry to ddb.
>
> Hmmm... gow about:
>
> db> show witness
> Sleep locks:
> 0 Giant -- last acquired @ /usr/src/sys/kern/kern_intr.c:532
> 1 eventhandler -- last acquired @ /usr/src/sys/kern/subr_eventhandler.c:162
> 3lockmgr -- last acquired @ /usr/sr
david,
On Fri, 8 Feb 2002, Julian Elischer wrote:
> cool..
> ok, how about adding "show witness"
[...]
can you do a cvs diff -D{time1] -D[time2] /sys
where time2 is the earliest kernel that has the problem and time1 is the
last kernel that doesn't?
there may be some other diffs in there I'm n
On Wed, Feb 06, 2002 at 12:32:18PM -0800, Alfred Perlstein wrote:
> * Julian Elischer <[EMAIL PROTECTED]> [020206 12:20] wrote:
> >
> > for the set of patches at:
> > http://www.freebsd.org/~julian/adiff
> >
> > these patches SHOULD NOT EFFECT your system except to do some
> > slight re-aranging
hi, there!
On Wed, Feb 06, 2002 at 05:47:07PM -0800, Joe Kelsey wrote:
> So what? Just because it wasn't part of 4.2 BSD, does that mean that we
> should never support it?
>
> > 2. What is so hard with installing the port. No one has answered *THAT*
> > question yet.
>
> Ports are ins
>Date: Fri, 8 Feb 2002 10:54:55 -0800 (PST)
>From: Julian Elischer <[EMAIL PROTECTED]>
>can you try a kernel from JUST BEFORE I did the KSE commit yesterday?
OK; results below
>I heard someone else complain of thisyesterday afternoon. At that time I
>wascertain it was too soon after my comm
On Wed, Feb 06, 2002 at 05:47:07PM -0800, Joe Kelsey wrote:
> What is so hard about allowing someone to specify the list of frontends
> to provide at system build time? I thought that gcc was supposed to be
> a modular compiler system, and that all we are asking for is the ability
> to add to the
On 6 Feb, David O'Brien wrote:
> Yes it comes as part of binutils.
Ok.
> No we should not go down this path. You've already been told that
> there is no official libiberty or bfd release.
Well, the following URL
http://www.gnu.org/manual/bfd-2.9.1/
for example, seems to imply,
cool..
ok, how about adding "show witness"
(we need to figure out which process SHOULD be doing the reboot, but it's
not obvious from this ps, which one we should be looking at.)
if you have it compiled in, show ktr (a couple of pages of it anyhow)
MIGHT show something.
On Fri, 8 Feb 2002, Euge
Joe Kelsey wrote:
> David O'Brien writes:
> > 3. Are you going to maintain them? If we did do this work and allowed
> > people to optinally install gjc and Ada, I bet only 5% would do so
> > (other than the initial turning it on just to see what the compilers
> > looked like).
>
1 - 100 of 220 matches
Mail list logo
