on 24/10/2011 20:55 Russell Cattelan said the following:
> So it has been a while and a lot of hair pulling but kload is sorta alive
> and kicking. It can now load the kernel from userspace, copy it over the
> running kernel and jump the the kernel entry point.
>
> I'm still having problems gettin
On Sat, 5 Nov 2011 15:58:01 +0200 Kostik Belousov wrote:
KB> procfs_doproccmdline() can benefit from your work.
Patch for procfs:
http://people.freebsd.org/~trociny/procfs.patch
--
Mikolaj Golub
___
freebsd-hackers@freebsd.org mailing list
http://l
Hi,
After change in:
http://svnweb.freebsd.org/base/head/usr.bin/vmstat/vmstat.c?r1=151417&r2=151416&pathrev=151417
I see that X_BOOTTIME is still kept in the namelist in vmstat.c, and I
would like to know if there's any reason for that.
Cheers,
Antonio Huete
___
On Sat, Nov 05, 2011 at 10:37:46PM +0200, Mikolaj Golub wrote:
>
> On Sat, 5 Nov 2011 21:45:53 +0200 Kostik Belousov wrote:
>
> KB> On Sat, Nov 05, 2011 at 08:59:21PM +0200, Mikolaj Golub wrote:
> >>
> >> On Sat, 5 Nov 2011 17:44:43 +0200 Kostik Belousov wrote:
> >>
> >> >> KB> I think t
Hi.
Are you running FreeBSD 9.0? If yes, it seems that cdparanoia is
broken because of some changes inside kernel, specifically, changes in
scsi interfaces. If you have your system upgraded to 9.0, but not
recompiled cdparanoia, you might run into some problems.
Regards.
--
Life is lik
On Mon, Nov 07, 2011 at 04:58:53AM +0800, Denise H. G. wrote:
>
> Hi.
>
> Are you running FreeBSD 9.0? If yes, it seems that cdparanoia is
> broken because of some changes inside kernel, specifically, changes in
> scsi interfaces. If you have your system upgraded to 9.0, but not
> recompi
Hackers. I am hitting a panic on 8.1 in the softclock() code. Anyone seen this?
PANIC : mutex Giant not owned at ../../../../sys/kern/kern_mutex.c:185
(kgdb-amd64-6.8-71) bt
#0 breakpoint () at ./machine/cpufunc.h:64
#1 0x803d8b82 in kdb_enter (why=0x806ca339 "panic",
msg=0xfff
At system startup, the init script is run with limits calculated on the
basis of the core MAXFILES.
After you run sysctl limits of the system may be altered, for example
"kern.maxfilesperproc", but the script will continue to work with the old
values.
This is bad in two ways:
1. When using the
On 2011-Nov-05 22:30:21 +, Alexander Best wrote:
>wouldn't it be possible to somehow spawn N gcc or clang instances
>(make -jN buildkernel) and then pipe the src to one of those N instances?
>just like with something like multics N processes were started and then people
>used the job control l
9 matches
Mail list logo