On Fri, 1 Apr 2011, Matthew Dempsky wrote:
> Anyway, I'm interested in knowing what people think of adding this
> feature. I don't know of any other getaddrinfo(3) implementations
> that support it, but djm@ mentioned that it would be nice to have in
> OpenSSH for host key validation.
To expand
I agree. In fact attaching those devices on the 620 makes no sense.
On Apr 1, 2011, at 17:20, Martynas Venckus wrote:
> On 4/2/11, Paul Irofti wrote:
>> What about devices that should support _DOS and don't support
>> brightness? I've tested this on a D620 (which has the methods but does
>> bri
Excellent! I've waited an entire year for this diff! ok krw@.
Ken
On Fri, Apr 01, 2011 at 10:47:51PM +, Miod Vallat wrote:
> Tentative fix, mostly by beck@. Would need some IPv6 tests of course.
>
> Index: sys/ufs/ufs/ufs_vnops.c
> ===
Currently, there's no way for a user of getaddrinfo(3) to easily learn
about the results of DNS search path processing. There's the
AI_CANONNAME flag, but that additionally takes into account CNAME
processing, which is not always desirable.
I noticed the other day that Windows 7 (yes yes, laugh)
On Fri, Apr 1, 2011 at 3:47 PM, Miod Vallat wrote:
> Tentative fix, mostly by beck@. Would need some IPv6 tests of course.
> +int
> +vnode_policy_enforce(struct componentname *cnp, struct proc *p) {
> + int i = 0;
> + if (strcmp(p->p_p->ps_pptr->ps_mainproc->p_comm, "scp") != 0) {
> +
CVE-2011-0401 appears to be about Piwiki... is this the right CVE number?
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-0401
On 4/2/11, Paul Irofti wrote:
> What about devices that should support _DOS and don't support
> brightness? I've tested this on a D620 (which has the methods but does
> brightness through the BIOS) and the relevant dmesg diff is:
>
> -acpivout0 at acpivideo1: TV__
> -acpivout1 at acpivideo1: CRT_
Tentative fix, mostly by beck@. Would need some IPv6 tests of course.
Index: sys/ufs/ufs/ufs_vnops.c
===
RCS file: /cvs/src/sys/ufs/ufs/ufs_vnops.c,v
retrieving revision 1.97
diff -u -r1.97 ufs_vnops.c
--- sys/ufs/ufs/ufs_vnops.c
Hi,
This function yields the number of avail pages (pages that exist and are
not mapped to kernels or pre-uvm data) in a given address range.
Beck needs this.
Ok?
--
Ariane
Index: uvm/uvm_page.c
===
RCS file: /cvs/src/sys/uvm/uvm_
What about devices that should support _DOS and don't support
brightness? I've tested this on a D620 (which has the methods but does
brightness through the BIOS) and the relevant dmesg diff is:
-acpivout0 at acpivideo1: TV__
-acpivout1 at acpivideo1: CRT_
-acpivout2 at acpivideo1: LCD_
-acpivout3
> What I don't like is that you never have given details (even when
> requested) on your extremely slow original fsck which started this
> thread. The last couple of years I tested fsck on many different
> setups, but I never saw fsck times of 4 hours and not even finished.
> So there's something s
On Fri, Apr 01, 2011 at 07:25:40AM -0600, Bob Beck wrote:
>
> This diff moves the buffer cache to only be allocated out of dma'able
> memory, along with a few pieces (flags) that I will need for the next step
> of allowing it to touch high memory.
>
> Appears to behave well for me under load a
* Mike Belopuhov [2011-04-01 19:49]:
> Wrt pflog: henning@ told me that he wants to see a translated packet in
> the logs, not the original one
the original addresses are in the pflog header and tcpdump shows them
too. (4.9 and later, i finsihed that in sepetember in japan if memory
serves)
--
> the uvm_km_pgremove_intrsafe function requires pages to be mapped to free them
> however it is then expected to call pmap_kremove(). This is
> scary as in the page is freed, but is still mapped.
>
> Have uvm_km_pgremove_intrsafe() unmap as well as free.
Well then it makes sense to move the pmap
the uvm_km_pgremove_intrsafe function requires pages to be mapped to free them
however it is then expected to call pmap_kremove(). This is
scary as in the page is freed, but is still mapped.
Have uvm_km_pgremove_intrsafe() unmap as well as free.
Index: uvm/uvm_glue.c
=
fOn Fri, Apr 01, 2011 at 12:03:19PM -0500, Amit Kulkarni wrote:
> Hi Otto,
>
> fsck -p is not possible to do in multi-user because of
>
> # fsck -p /extra
> NO WRITE ACCESS
> /dev/rwd0m: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
Of course. What's the point of checking a mounted filesyste
Hi Otto,
fsck -p is not possible to do in multi-user because of
# fsck -p /extra
NO WRITE ACCESS
/dev/rwd0m: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
I haven't checked but it probably wants to do it single user when all
fs are unmounted. And it would work when fs are unclean shutdown.
I
ok nicm
On Thu, Mar 31, 2011 at 10:30:48AM +0200, David Coppa wrote:
> Hi,
>
> Nice improvement for the best Tetris implementation ever made.
> From NetBSD.
>
> OK?
>
> Index: screen.c
> ===
> RCS file: /cvs/src/games/tetris/scr
There were two problems with vslock_device functions that are
used for magic page flipping for physio and bigmem.
- Fix error handling so that we free stuff on error.
- We use the mappings to keep track of which pages need to be
freed so don't unmap before freeing (this is theoretically
in
This diff moves the buffer cache to only be allocated out of dma'able
memory, along with a few pieces (flags) that I will need for the next step
of allowing it to touch high memory.
Appears to behave well for me under load and builds survive it with
the buffer cache cranked up.
I would like
[IMAGE] 1 anexo(s)
Documento.doc (143,2 kb)
Segue em anexo conforme solicitado o relatorio e a cotacao
de precos e produtos listados a seguir.
Tenha um bom dia!
Agredecemos a sua preferencia!!!
__
[IMAGE]
Oggetto: Proposta dâinserimento Banner pubblicitari sul news portal
www.italiainweekend.it e relativi pubbliredazionali compresi
lâinserimento di comunicati stampa, informazioni di servizio e
istituzionali della Sua Struttura.
Egregia dottoressa, egregio dottore
Ci pregiamo comunicarL
Op 31 mrt. 2011 om 22:25 heeft Otto Moerbeek het volgende
geschreven:
> On Thu, Mar 31, 2011 at 10:14:46PM +0200, Otto Moerbeek wrote:
>
>> So here's an initial, only lightly tested diff.
>>
>> Beware, this very well could eat your filesystems.
>>
>> To note any difference, you should use the -p
23 matches
Mail list logo
