Kernel

HTT/ACPI problem resolved

Now beastie.frontfree.net is running with HTT enabled.

最新注册的会员是 davidxu

From FreeBSDChina’s forum:

论坛共有 62426 个文章
论坛共有 4513 位注册会员
最新注册的会员是 davidxu

cvs updated again

I think FreeBSD will soon release a new advisory. Simply put, cvs updated again and is vulnerable to some potential security risks.

kern_thread.c repocopyed to kern_kse.c...

I have noticed that today’s cvsup brings this to my local repo: src/sys/kern/kern_kse.c. From the version it seems to be from kern_thread.c. Waiting commitmail to explain this.

delphijfork to release first snapshot ISO

This is an experimental release which tend to exhibit the latest -CURRENT technologies, maintaining stablity and incorporating my improvements which has not been integrated into FreeBSD’s central repository.

Bigger bin patch accepted by FreeBSD

It seems that FreeBSD community has reviewed and committed one of my bigger patch on sbin/syslogd, which was primarily obtained from OpenBSD. These changes are more or less “sync with OpenBSD”, which will increase security performance of FreeBSD.

MAXUSERS=0意味着什么？

自从01年dillon commit之后一直就用着MAXUSERS 0。今天alu提到说MAXUSERS不合适的时候有可能会造成系统负荷能力下降，于是看了代码，发现MAXUSERS是根据内存大小算出来的，32-512之间。另外，实践证明MAXUSERS看来不能设置为2048(起不来)……

FreeBSD 4.10-RELEASE released

Scott Long has named 4.10-RELEASE yesterday and now the source tree has been tagged. The long awaited release has included the lastest FreeBSD -STABLE improvements, security updates, stablity improvements, and so on.

OpenBSD to adopt gdb 6.1

It seems (still can’t access to the Internet right now, however, HTTP and cvsup works) that OpenBSD has imported gdb 6.1 into their source tree. I am not sure whether they did some hacks to the source repository (from cvsup result, there is not), but the result is really strange. It seems that the last import was done by using a “cvs add -rCYGNUS” and not “cvs import”…

I hope FreeBSD can import a newer gdb ASAP, as well as gcc 3.4 series.

How to debug a live FreeBSD kernel?

To quote Matthew Dillon:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14

    You can actually run gdb on a live kernel like this:

    gdb -k /dev/mem /path/to/kernel.debug

    You can then use the 'proc' command to switch to a process (give it a
    pid), and do a stack backtrace.  That part only really works if the
    process is blocked on something (i.e. not running).

    But you can also dig around kernel globals and various data structures
    and that can be quite useful on a live system.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

• ← 上一页
• 下一页 →