On Fri, 22 Sep 2000, Julian Elischer wrote:
> Throwing a lock in every structure is
> one
> thing but then to tie the whole bundle up together is a completely
> different ballgame.
Yes, that's the hard part. It can be potentially dangerous to, for
example, call the mbuf resource alloc
Bosko Milekic wrote:
>
> I don't believe so. There are several external resources, such as
> on-line papers, and so on. There is also a man page (which I've found
> from jasone's web space) which has been prepared by Sheldon Hearn and
> which should be at ~jake/mutex.9
> As
I see.. just cvs update src/sys/dev/ata or something like that I
guess.. :-) I'll probably do that then.
=
| Kenneth Culver | FreeBSD: The best NT upgrade|
| Unix Systems Administrator | ICQ #: 24767726
I don't believe so. There are several external resources, such as
on-line papers, and so on. There is also a man page (which I've found
from jasone's web space) which has been prepared by Sheldon Hearn and
which should be at ~jake/mutex.9
As far "standard way to do it" docum
On Friday, 22 September 2000 at 19:50:11 -0700, Julian Elischer wrote:
> Do we have a document that descibes in great detail the
> locking policy that the SMPng code should follow?
>
> I've seen several descriptionms as to how it might be done,
> but I haven't seen a "Ok we've decided that this is
Do we have a document that descibes in great detail the
locking policy that the SMPng code should follow?
I've seen several descriptionms as to how it might be done,
but I haven't seen a "Ok we've decided that this is the strategy
we are using" document.
--
__--_|\ Julian Elischer
Leif Neland([EMAIL PROTECTED])@Sat, Sep 23, 2000 at 12:15:31AM +0200:
> Pine 4.21 complains that /var/mail is vulnerable, that the perms should be
> 1777
>
> Would this be less vulnerable than 775 which make world restores it to?
>
> Leif
since when does qmail write to /var/mail???
*evilgrin*
/k
Vivek Khera([EMAIL PROTECTED])@Fri, Sep 08, 2000 at 09:56:07AM -0400:
[...]
> That last sentence makes me think that the person who decided this
> does not use a network to update that machine, ie NFS mounting
> /usr/src. It is a royal PITA to get networking up and going after a
> single-user reb
Kris Kennaway([EMAIL PROTECTED])@Mon, Sep 04, 2000 at 08:09:59PM -0700:
> On Mon, 4 Sep 2000, Warner Losh wrote:
>
> > In message <[EMAIL PROTECTED]> Jordan Hubbard writes:
> > : Well, it's at least one step closer - all they have to do now (the US
> > : people) is install the rsaref port to have
> On Sat, 12 Aug 2000, Brian Somers wrote:
>
> > > Is ppp.linkdown executed before or after the link is down?
> > >
> > > I'd like to change a dyndns, but will link activity done in linkdown defeat
> > > the timeout, or start a new call?
> >
> > It'll start a new call in auto mode.
> >
> So an
In message <[EMAIL PROTECTED]> Garrett
Wollman writes:
: (I certainly wouldn't accept security advice from the Pine
: developers)
Maybe we should fix the pine port to not whine like that.
Oh wait, we do...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cur
Howdy gang,
I recently upgraded my home and work workstation machines to X
Free 4.0.1 so that I could test the possibility of using the i810 video
card. Surprisingly enough for me, everything works as expected, with the
exception of mouse stuff.
Previously I had X + moused worki
Hi,
While compiling the aha module ( buildkernel ) on current i
get the following errors from the include src/sys/sys/buf.h:
--
===> aha
cc -O2 -pipe -D_KERNEL -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
-Wpointer-arith -Winline -Wcast-qual -fformat-exten
< said:
> Pine 4.21 complains that /var/mail is vulnerable, that the perms should be
> 1777
Pine is a steaming, festering pile of
Let's try that again. The developers of Pine have certain erroneous
ideas about how mail systems work; this is one of them. Ignore Pine's
plaints and things should
Pine 4.21 complains that /var/mail is vulnerable, that the perms should be
1777
Would this be less vulnerable than 775 which make world restores it to?
Leif
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 12 Aug 2000, Brian Somers wrote:
> > Is ppp.linkdown executed before or after the link is down?
> >
> > I'd like to change a dyndns, but will link activity done in linkdown defeat
> > the timeout, or start a new call?
>
> It'll start a new call in auto mode.
>
So any ideas how to use
On Fri, Sep 22, 2000 at 09:48:42AM -0500, Mark Hittinger wrote:
>
> I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
I am also seeing this with a kernel and world from today... also, are there
any issues with mount_cd9660? When I issue the following command:
# mount -t c
It seems Kenneth Wayne Culver wrote:
> Alright, I think I may just do that too... I was going to try to tough it
> out... but it looks like that just won't work I wish there was some
> way to get the other changes without getting the SMP stuff though.
You update the ata driver to the lastest
Alright, I think I may just do that too... I was going to try to tough it
out... but it looks like that just won't work I wish there was some
way to get the other changes without getting the SMP stuff though.
=
| Kenneth Culver
On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote:
...
> To: [EMAIL PROTECTED]
> Subject: -CURRENT crashes under heavy disk activity
This is a well known issue.
See the -current archive for more information.
Search for "vmstat" and "FFS".
Bye!
Michael Reifenberger
^.*Plaut.*$, IT, R/3 Basis, G
It seems Kenneth Wayne Culver wrote:
> I will try to build a debug kernel, and get a backtrace of what's
> happening to send to the list, but basically what happened is that I was
> running a cvsup of the cvs source repository and the ports repository and
> it just crashed and rebooted (I'm doing
On Sat, Sep 23, 2000, Bruce Evans wrote:
> On Sat, 23 Dec 2000, Adrian Chadd wrote:
>
> > Here's the patch:
> >
> > --- fsck.c.orig Sat Dec 23 11:13:30 2000
> > +++ fsck.c Sat Dec 23 11:13:34 2000
> > @@ -501,7 +501,7 @@
> > errx(1, "partition `%s' is not of a legal vfstype"
I will try to build a debug kernel, and get a backtrace of what's
happening to send to the list, but basically what happened is that I was
running a cvsup of the cvs source repository and the ports repository and
it just crashed and rebooted (I'm doing this remotely, so I can't really
catch any me
On Sat, 23 Sep 2000 [EMAIL PROTECTED] wrote:
> Bruce Evans <[EMAIL PROTECTED]> wrote:
> >It needs locking changes to be exportable:
> >
> >1) splhigh()/splx(), at least in RELENG_4 where there is no giant lock
> > and spl*() has a non-null effect, so that callers don't need to know
> > that i
On Sat, 23 Dec 2000, Adrian Chadd wrote:
> Here's the patch:
>
> --- fsck.c.orig Sat Dec 23 11:13:30 2000
> +++ fsck.c Sat Dec 23 11:13:34 2000
> @@ -501,7 +501,7 @@
> errx(1, "partition `%s' is not of a legal vfstype",
> str);
> - if ((vfstype = dk
Bruce Evans <[EMAIL PROTECTED]> wrote:
>On Sun, 17 Sep 2000, Warner Losh wrote:
>
>> I've seen these patches many times and think that it is a good idea.
>> This interface needs to be exported so that the pccard system sounds
>> don't interfere with normal systme sounds.
>
>It needs locking change
I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
The same kernel that I began to see the fdc0 problems I also lost the ability
to use devices on ata1. Ata1 seems to probe OK but I get I/O errors on the
ata1 drives all of a sudden. A kernel from a week ago is OK.
Later
after doing a CVSup this morning and make buildworld, kernel, installkernel,
installworld again i have the following status:
fdc0 doesnt get recogniced (conflict with pccard at 3f0). need to find how to
change the I/O of the pccard controller. sometimes fdc0 writes cannot reserve
I/O range.
r
as of a few days ago, for some reason my floppy drive controller does not
probe right with -CURRENT... I've attached a dmesg, a kernel config, and
my hints file as kernstuff.tar
Please let me know if I've made some dumb mistake or something in my
configs...
Kenneth Culver
kernstuff.tar
On Fri, 22 Sep 2000, Takaya Ogawa wrote:
> Attached patch adds back the HLT in i386 UP case and
> seems to fix my problem, although I'm totally
> unfamiliar with SMP nor alpha.
This has the race bug that was fixed in rev.1.88 of swtch.s.
I use the folowing fix. It also fixes the loss of page c
On Fri, Sep 22, 2000, Boris Popov wrote:
> On Sat, 23 Dec 2000, Adrian Chadd wrote:
>
> > On Fri, Sep 22, 2000, Boris Popov wrote:
> > > On Sat, 23 Dec 2000, Adrian Chadd wrote:
> > >
> > > > So now is a problem which I'm sure the NetBSD people came up against.
> > > > The fstypenames are names
On Sat, 23 Dec 2000, Adrian Chadd wrote:
> On Fri, Sep 22, 2000, Boris Popov wrote:
> > On Sat, 23 Dec 2000, Adrian Chadd wrote:
> >
> > > So now is a problem which I'm sure the NetBSD people came up against.
> > > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
> > > th
On Fri, Dec 22, 2000, Adrian Chadd wrote:
>
>
> I've updated my fsck wrappers patchset to the latest netbsd and freebsd
> fsck patches. I'd appreciate some feedback on them before I run off
> and commit them (with my mentor, of course.)
>
> For those who aren't in the know, the general idea is
On Fri, Sep 22, 2000, Boris Popov wrote:
> On Sat, 23 Dec 2000, Adrian Chadd wrote:
>
> > So now is a problem which I'm sure the NetBSD people came up against.
> > The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
> > this by creating a new list 'mountnames[]', which maps t
On Sat, 23 Dec 2000, Adrian Chadd wrote:
> So now is a problem which I'm sure the NetBSD people came up against.
> The fstypenames are names like 4.2BSD, vinum, ISO9660, etc. NetBSD fixed
> this by creating a new list 'mountnames[]', which maps the fs type to
> a string.
Probably a hard
On Fri, Dec 22, 2000, Adrian Chadd wrote:
>
>
> I've updated my fsck wrappers patchset to the latest netbsd and freebsd
> fsck patches. I'd appreciate some feedback on them before I run off
> and commit them (with my mentor, of course.)
>
> For those who aren't in the know, the general idea is
John Baldwin wrote:
>
> Yes. This is a FAQ. The accounting is screwed up, and some of the
> statistics are wrong. Your system is scheduling processes close enough
> to normal that you shouldn't have any problems.
>
Ah, I am sorry. I searched the -current archives but I didn't find
anything r
On 21-Sep-00 Daniel J. O'Connor wrote:
> Hi,
>
> When I boot an SMP kernel (updated 2 days ago) I get the following panic
> message ->
>
> panic: cpu_switch: chooseproc returned NULL
> cpuid = 0; lapic_id =
>
> db> tr
> Debugger(..)
> panic(..)
> sw0_3(2,c03876f8,0,0,0) at sw0_3
> msl
> Most procedures works well, except one warnings. When CD-ROM is
> initialized to use (after all installation option was selected),
> sysinstall complains as follows:
Thanks for reminding me to go look at that code - you're right, the
check is incorrectly done and insufficiently general. Fixed
39 matches
Mail list logo
