[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] writes:
> }> I didn't know if you were talking about "not incrementing" when the
> }> process exits or when it rforked. If you rfork(RFMEM), you'd want to
> }> increment the vm_refcnt I'm pretty sure (and it does).
> }
> }No, you really don't.
>
> I do
On Mon, Apr 15, 2002 at 07:53:01PM +0300, [EMAIL PROTECTED] wrote:
> Hi.
>
> I have network interface rl0
>
> rl0: flags=8843 mtu 1500
> inet 192.168.10.22 netmask 0xff00 broadcast 192.168.10.255
> inet 192.168.10.26 netmask 0x broadcast 192.168.10.26
> ether
[EMAIL PROTECTED] writes:
}> I didn't know if you were talking about "not incrementing" when the
}> process exits or when it rforked. If you rfork(RFMEM), you'd want to
}> increment the vm_refcnt I'm pretty sure (and it does).
}
}No, you really don't.
I don't know or we don't want to increment th
[EMAIL PROTECTED] wrote:
> I didn't know if you were talking about "not incrementing" when the
> process exits or when it rforked. If you rfork(RFMEM), you'd want to
> increment the vm_refcnt I'm pretty sure (and it does).
No, you really don't.
You have a number of references on the vm (one per
[EMAIL PROTECTED] writes:
}] You'd actually think that not incrementing in the RFMEM case, but
}] then decrementing if the RFMEM reference goes from 1->0 would be
}] the correct thing to do.
I didn't know if you were talking about "not incrementing" when the
process exits or when it rforked. If y
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] writes:
> }Heh. That's a Biiig snip. I had a huge caveat on the code
> }doing what it did where it did it, if you'll remember. 8-).
>
> Sorry, Terry it was no slight on you (and it looked fine to me too). I just
> wanted to get something in the
[EMAIL PROTECTED] writes:
}Heh. That's a Biiig snip. I had a huge caveat on the code
}doing what it did where it did it, if you'll remember. 8-).
Sorry, Terry it was no slight on you (and it looked fine to me too). I just
wanted to get something in the list archives in case some poor sod d
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] writes:
> [ suggested fix ]
> [ snip ]
> }This looks right, to me.
>
> Sigh. With the fix as in current (decrement the vm_refcnt in the if statement)
> the system panics on boot with a "vmspace already free" message.
> With my version of the fix (only
[EMAIL PROTECTED] writes:
[ suggested fix ]
[ snip ]
}This looks right, to me.
Sigh. With the fix as in current (decrement the vm_refcnt in the if statement)
the system panics on boot with a "vmspace already free" message.
With my version of the fix (only decrement if vm_refcnt) not 1 by calling
On Tue, 16 Apr 2002, Surfer wrote:
>
> Sir:
>
> Our latest driver is ready and tested. It's support our 3 network chips.
>
> MTD800Fast NIC
> MTD803Fast NIC with integrated PHY
> MTD891Gigabit NIC
>
> Should I release it at this time?? Or I can re
De Lay-out van het scherm
Nadat Cruise-A-Way Streets is opgestart, verschijnt het volgende op het scherm:
de menubalk
de werkbalk met verscheidene pictogrammen
het hoofdscherm met een standaardkaart
de statusregel
3) Beschrijving van de pictogrammen in de werkbalk
Cruise-A-Way Streets maakt g
Christian Flügel wrote:
>
> Hi,
Welcome,
>
> I use FreeBSD regularly for over 4 years now (since I have read an Article
> about 3.0 in the c't magazine) and since I deem it such a great product I'd
> very much like to contribute to it to help make it even better.
this is clearly how FreeBSD h
On 2002-04-16 11:27, Christian Fl?gel wrote:
> I use FreeBSD regularly for over 4 years now (since I have read an Article
> about 3.0 in the c't magazine) and since I deem it such a great product I'd
> very much like to contribute to it to help make it even better.
>
> I just don't know where to s
On Fri, Apr 12, 2002 at 01:05:15PM -0400, PSI, Mike Smith wrote:
> It may be the correct operation, but if it isn't, having a filesystem
> change unknowingly (unintentionally) from read only to read/write could
> be a bit dangerous I would think.
"mount -u /filesys" applies the *default* set of f
Hey all,
Made a mistake and ran across what may be a bug in mount but am not
sure. Now this happened on FreeBSD 3.2 (no comments please, I've already
given the powers that be plenty of comments about this).
Our password files became corrupted so we entered single user mode to
try to repair the s
Hi,
I use FreeBSD regularly for over 4 years now (since I have read an Article
about 3.0 in the c't magazine) and since I deem it such a great product I'd
very much like to contribute to it to help make it even better.
I just don't know where to start. I am a Comp. Sci. Major with not much
exper
> >do you have a loopback route at the host environment like:
> >192.168.10.26 127.0.0.1 UGHS3 4497lo0
>
> sorry,... wrong ip... i meant the ip of the jailed host 192.168.10.22
> should go to the loopback.
192.168.10.26 is a jailed ip. But anyway its alias.
> do you have a loopback route at the host environment like:
> 192.168.10.26 127.0.0.1 UGHS3 4497lo0
>
> at my side that was the problem (and this route is never mentioned at the
> jail-man page...( )
it didn't help. As i've told, i can ``dig -p 2053 ...'',
18 matches
Mail list logo
