Hi. This is good topic. I am no body. But I want to mention things.
I've use RCS, CVS, SVN, Hg and Git. To me, first three are really
much one in same. Of later two still learning, Hg can be slightly
easier, but Git has simple analogs too, not much hard to get. We
all learn new thing. But overall,
Is this work part of what's needed to enable the FreeBSD
equivalent of TNAPI?
I know we've got polling. And probably MSI-X in a couple drivers.
Pretty sure there is still one CPU doing the interrupt work?
And none of the multiple queue thread spreading tech exists?
http://www.ntop.org/blog
http:/
Perhaps some similar work here. And maybe a card vendor
with docs and an affinity to open source. Just news, that's all.
http://www.ntop.org/blog/pf_ring/introducing-the-10-gbit-pf_ring-dna-driver/
bcc: hackers, isp. reply to net.
___
freebsd-hackers@fr
Would be nice to be able to set different times in different jails.
All jails would tick in step with the system.
But each jail could have it's birthtime set specifically via jail(8),
jail(2), etc. Either by specification of a specific time, or an offset
from the current true system time. ie:
jail
> possibly achievable in libc?
I don't know. Where else would it be done?
stat, utimes, gettimeofday, clock_gettime,
adjtime, etc and their variations.
I've not checked what currently happens, but I
don't think root in a jail should be able to set
any kernel time parameters, absent a syscall
that
> Why on earth would you want this?
Hi. Since your quote of my note was not to the original,
I'll repost it here. Kurt Lidl also posted useful situations
on these lists. Also, being able to have time tick backwards
in jails could be interesting fuzzing too :-) Enjoy.
Would be nice to be able to
Found some datasheets (programming docs) and board schematics for
Silicon Image storage controllers. Since they don't seem to be
publicly available, perhaps some of these docs will be useful.
Bcc'd relevant fs and hackers lists. Reply to hardware I guess.
# Overview
http://www.siliconimage.com/pr
Realized my earlier related post was a bit misplaced in questions@.
So I just refer to it here by link, ok then that is all.
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=968504+0+current/freebsd-questions
___
freebsd-hackers@freebsd.org mailing list
http
http://www.freebsd.org/news/2012-compromise.html
http://it.slashdot.org/story/12/11/17/143219/freebsd-project-discloses-security-breach-via-stolen-ssh-key
This is not about this incident, but about why major opensource
projects need to be using a repository that has traceable, verifiable,
built-in
On Sun, Nov 18, 2012 at 1:57 AM, Garrett Wollman wrote:
>> the various good uses for nyms.
>
> There are no such uses on the FreeBSD mailing-lists; if you wish for
> anyone to pay attention to you, then use a real name. Otherwise,
> FOAD.
>
> -GAWollman
It appears you have not reviewed the maili
>> grarpamp
>> the various good uses for nyms.
> cpgh...@cordula.ws
> I hope you realize whom you're trying to lecture here!
> Joerg Wunsch is a highly appreciated long-time FreeBSD contributor
Of course. No one here has any question as to anyone's FreeBSD
particip
> I won't fail to defend general anti-nym opinion or guidance
d-oh, s/defend/defend against/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr
This exit should not be 0, regardless of msdosfs or not.
Same for if the '.' dir entries do in fact have B/M/A/C times,
operations on those entries should update those times
accordingly, as subdirs do. RELENG_8. Thanks.
# newfs_msdos /dev/fd0
/dev/fd0: 2829 sectors in 2829 FAT12 clusters (512 byte
ZFS version list [was ETA for ZFS ver: n]
I needed raw, bit reliable, stable, encrypted storage. ZFS gave all
but the last part so far. None of the features since v6 were useful
to me. And as with most software, there are surely tons of fixes
and optimizations being handled silently that are usefu
Is this telling me I should be able to set kmem_size to around
740MiB before the kernel panics during boot? Any runtime issues
with doing that?
# sysctl hw.physmem hw.realmem vm.kvm_size vm.kvm_free vm.kmem_size
hw.physmem: 1055293440
hw.realmem: 1072627712
vm.kvm_size: 1073737728
vm.kvm_free: 205
15 matches
Mail list logo
